esp8266_wifi_modules
Unterschiede
Hier werden die Unterschiede zwischen zwei Versionen angezeigt.
| Beide Seiten der vorigen RevisionVorhergehende ÜberarbeitungNächste Überarbeitung | Vorhergehende Überarbeitung | ||
| esp8266_wifi_modules [2014/12/18 23:31] – karl | esp8266_wifi_modules [2017/04/04 06:42] (aktuell) – [Notes] karl | ||
|---|---|---|---|
| Zeile 103: | Zeile 103: | ||
| ready | ready | ||
| - | AT+CWJAP=" | + | AT+CWJAP=" |
| Zeile 191: | Zeile 191: | ||
| </ | </ | ||
| - | ==== TCP Server Example ==== | + | ===== TCP Server Example ===== |
| + | **Attention: | ||
| < | < | ||
| AT+RST | AT+RST | ||
| - | |||
| - | |||
| OK | OK | ||
| c_\0xc7\0xcfRS\0xfe\0xe2FjS\0xf6fJ[\0xfa\0xe2\0xea | c_\0xc7\0xcfRS\0xfe\0xe2FjS\0xf6fJ[\0xfa\0xe2\0xea | ||
| [Vendor: | [Vendor: | ||
| - | |||
| ready | ready | ||
| - | AT+CWJAP=" | ||
| + | AT+CWJAP=" | ||
| + | OK | ||
| + | AT+CIPSTATUS | ||
| + | STATUS:5 | ||
| OK | OK | ||
| + | |||
| AT+CIPMUX=1 | AT+CIPMUX=1 | ||
| + | OK | ||
| + | AT+CIPSTATUS | ||
| + | STATUS:5 | ||
| OK | OK | ||
| + | |||
| AT+CIPSERVER=1, | AT+CIPSERVER=1, | ||
| + | OK | ||
| + | AT+CIPSTATUS | ||
| + | STATUS:5 | ||
| OK | OK | ||
| + | |||
| Link | Link | ||
| + | |||
| + | AT+CIPSTATUS | ||
| + | STATUS:3 | ||
| + | +CIPSTATUS: | ||
| + | OK | ||
| +IPD, | +IPD, | ||
| OK | OK | ||
| - | AT+CIPSEND=0, | ||
| - | > Hello Lenovo, thank you very much for your request | + | STATUS:3 |
| + | +CIPSTATUS: | ||
| + | OK | ||
| + | AT+CIPSEND=0, | ||
| + | > Hello Lenovo, thank you very much for your request | ||
| SEND OK | SEND OK | ||
| +IPD, | +IPD, | ||
| - | |||
| OK | OK | ||
| + | |||
| Unlink | Unlink | ||
| + | |||
| + | AT+CIPSTATUS | ||
| + | STATUS:4 | ||
| + | OK | ||
| </ | </ | ||
| + | |||
| + | 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 ' | ||
| + | |||
| + | 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), | ||
| + | |||
| + | ==== CIPSTATUS Example ==== | ||
| + | < | ||
| + | AT+CIPSTATUS | ||
| + | STATUS:3 | ||
| + | +CIPSTATUS: | ||
| + | +CIPSTATUS: | ||
| + | +CIPSTATUS: | ||
| + | OK | ||
| + | </ | ||
| + | |||
| + | Here I opened 4 instances of the application " | ||
| + | |||
| + | ===== 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> | ||
| + | |||
esp8266_wifi_modules.1418941867.txt.gz · Zuletzt geändert: von karl
