Unterschiede

Hier werden die Unterschiede zwischen zwei Versionen angezeigt.

--- esp8266_wifi_modules [2014/12/02 17:30] – [Testing it as a TCP client] karl
+++ esp8266_wifi_modules [2017/04/04 06:42] (aktuell) – [Notes] karl
@@ 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 102: / Zeile 103: @@
 ready
-AT+CWJAP="MKZ","BE662F3BC9"
+AT+CWJAP="ssid","key"
@@ Zeile 173: / Zeile 174: @@
 <CR><LF>
 bytes: hexadecimal block length = 20 decimal
-  Hello World!<br> <CR><LF>
+  Hello World!<br><Space><LF>
- bytes body
+  <Space><LF>
+ bytes message body.
+  <CR><LF>
+bytes empty line, which terminates the first chunk
  <CR><LF>
@@ Zeile 186: / Zeile 190: @@
 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}}