Unterschiede

Hier werden die Unterschiede zwischen zwei Versionen angezeigt.

--- esp8266_wifi_modules [2014/12/02 11:48]
karl [Documentation Sites]
+++ esp8266_wifi_modules [2017/04/04 06:42] (aktuell)
karl [Notes]
@@ Zeile 8: / Zeile 8: @@
 This module supports TCP and UDP, both as a server or a client, which is pretty awesome!
+Version 2 has an IPEX (U.FL) connector. A possible antenna coudl be this one from [[http://at.farnell.com/pulse-engineering/w1039b030/antenne-ext-2-4-5-5ghz-ipex-artic/dp/1900063?CMP=i-bf9f-00001000 |Farnell#1900063]]
 ===== Documentation Sites =====
 http://www.electrodragon.com/w/Wi07c \\
@@ Zeile 89: / Zeile 90: @@
   rtt min/avg/max/mdev = 32.722/188.055/482.747/127.476 ms
 As we can see, the average response time of 188ms is quite long. But hey, I don't want to use the module for high speed low latency applications. I want to measure temperature and switch on or off a heating system.
+==== Testing it as a TCP client ====
+<code>
+AT+RST
+OK
+?0\0xb8t\0xfe\0x08f\0xf4(\0x00\0x08\0xe3\0x9dn@h\0x15\0xca\0xff@
+\0xff
+[Vendor:www.ai-thinker.com Version:0.9.2.4]
+ready
+AT+CWJAP="ssid","key"
+OK
+AT+CIPSTART="TCP","www.zeilhofer.co.at",80
+OK
+Linked
+AT+CIPSEND=43
+> GET /php_learning/helloworld.php HTTP/1.1
+SEND OK
+AT+CIPSEND=30
+> Host: www.zeilhofer.co.at:80
+SEND OK
+AT+CIPSEND=2
+>
+SEND OK
++IPD,170:HTTP/1.1 200 OK
+Date: Tue, 02 Dec 2014 13:46:03 GMT
+Server: Apache
+Connection: close
+Transfer-Encoding: chunked
+Content-Type: text/html
+Hello World!<br>
+OK
++IPD,5:0
+OK
+</code>
+As we can see, we get the desired response from the webserver.
+The HTTP message body is "chunk"-encoded. I interpret this so, that each chunk is preceeded by the length of the chunk. The number is in bytes, and encoded as a hexadecimal number.
+A chunk is terminated with a <CR><LF>
+Lets decode the message above in details:
+  +IPD,170:
+this is sent from the WiFi module, and tells the terminal, that data from the open TCP connection is received. The data has 170 bytes.
+  HTTP/1.1 200 OK<CR><LF>
+bytes: This is the HTTP status line. For details click here: http://www.w3.org/Protocols/rfc2616/rfc2616-sec6.html
+ \\
+The line is terminated with <CR><LF>.
+  Date: Tue, 02 Dec 2014 13:46:03 GMT<CR><LF>
+bytes: From the server we get the current date and time
+  Server: Apache<CR><LF>
+bytes: The server tells us, that it is an Apache server.
+  Connection: close<CR><LF>
+bytes: The connection is closed by the server after the message is transmitted. This is because we did not tell the server to keep the connection alive (we could add **Connection: keep-alive** to the HTTP-GET message header).
+  Transfer-Encoding: chunked<CR><LF>
+bytes: the message body is transmitted in chunks.
+  Content-Type: text/html<CR><LF>
+  <CR><LF>
+bytes: end of http-message-header\\
+Body:
+<CR><LF>
+bytes: hexadecimal block length = 20 decimal
+  Hello World!<br><Space><LF>
+  <Space><LF>
+bytes message body.
+  <CR><LF>
+bytes empty line, which terminates the first chunk
+ <CR><LF>
+OK
++IPD,5:0
+OK
+</code>
+===== TCP Server Example =====
+**Attention:** the linebreaks are modified for better readability\\
+<code>
+AT+RST
+OK
+c_\0xc7\0xcfRS\0xfe\0xe2FjS\0xf6fJ[\0xfa\0xe2\0xea
+[Vendor:www.ai-thinker.com Version:0.9.2.4]
+ready
+AT+CWJAP="SSID","key"
+OK
+AT+CIPSTATUS
+STATUS:5
+OK
+AT+CIPMUX=1
+OK
+AT+CIPSTATUS
+STATUS:5
+OK
+AT+CIPSERVER=1,47000
+OK
+AT+CIPSTATUS
+STATUS:5
+OK
+Link
+AT+CIPSTATUS
+STATUS:3
++CIPSTATUS:0,"TCP","192.168.1.105",50583,1
+OK
++IPD,0,44:hello server, this is the client (lenovo)
+OK
+STATUS:3
++CIPSTATUS:0,"TCP","192.168.1.105",50583,1
+OK
+AT+CIPSEND=0,52
+> Hello Lenovo, thank you very much for your request
+SEND OK
++IPD,0,44:no problem, thank you for serving me. ciao
+OK
+Unlink
+AT+CIPSTATUS
+STATUS:4
+OK
+</code>
+A server is opened on a specific port. To this port there can be up to 5 connections in parallel, TCP and UDP mixed. When responding, we have to set the 'mux' ID, which can be from 0 to 4. Each new incomming connection (For simplicity I name also UDP packets a "connection" here), the ID will be increased, and we can see the active connections with CIPSTATUS.
+If we have multiple incomint TCP-connections from one client (multiple processes), we get multiple connections in the CIPSTATUS-list. Each with it's own reply port. \\
+But if we get multiple UDP connections from one client (also different client-processes), only the most recent one is stored in the CIPSTATUS-list, even though they have different reply ports.
+==== CIPSTATUS Example ====
+<code>
+AT+CIPSTATUS
+STATUS:3
++CIPSTATUS:0,"TCP","192.168.1.105",50618,1
++CIPSTATUS:1,"TCP","192.168.1.105",50626,1
++CIPSTATUS:2,"UDP","192.168.1.105",37690,1
+OK
+</code>
+Here I opened 4 instances of the application "SocketTest v 3.0.0" on my notebook, and opened 2 TCP connections, and sent 2 UDP packets (broadcasts). But we can only see 3 active connections here.
+===== Notes =====
+When we close the server with
+  AT+CIPSERVER=0
+, then the module has to be resetted!
+As far as I know, we cannot find out, on which port the server was opened.
+We can find the own IP address with
+  AT+CIFSR
+. Note, that there is no questionmark!
+{{tag>english software electronics wifi arduino product technical}}

Verschiedenste Artikel von Karl Zeilhofer

Benutzer-Werkzeuge

Webseiten-Werkzeuge

Unterschiede

Seiten-Werkzeuge