Quick Data Send Commands

[Jan Kijonka]

Hi,

What are the best commands and optimized timmings for quick TCP data send ?

I use "AT+CIPSTART" and "AT+CIPSEND" commands in a loop. After the data are sent, the "SEND OK" and "CLOSED" messages are returned. The communication is closed automatically without "AT+CIPCLOSE" command call and regardless of <TCP keep alive> time settings.

How to stay connected to the server without sending the "AT+CIPSTART" command repetitivelly ?

I need to get faster. Now I can send only one data packet every 1 000 ms. When I'm trying to speed up to 500 ms, some data packet are sometimes ommited and some errors are returned.

Jan

[Her Mary]

Maybe you can have a try with the UART-Wifi passthrough mode.

[Jan Kijonka]

Hi,
I have tested some options. When I'm connected to an online server like "esp8266test1.000webhostapp.com", the packets are sent with more delay than when I'm connected to a local IP adress like "192.168.0.106". Moreover, with local IP the client is not automatically disconnected after one packet transmission.

Now I can send one 2048 Bytes packet every 500 ms:

Write: "AT+CIPSEND=2048\r\n>"
Read: "\r\nOK\r\n> " (wait for response max 4 ms)
Write: DATA
Read: "\r\nRecv 2048 bytes\r\n\r\nSEND OK\r\n>" (wait for response ~150 ms)

I use Baud Rate: 625000 Bd (a further increase of baud rate will not give a noticeable improvement).

Still not perfect (32 kbit/s). I have achieved almost 200 kbit/s with ZigBee CC2520 from TI (128 bytes packets transmitted in 6-8 ms intervals with every succesfully sent packet checksumed and confirmed by ACK from the receiver, TX 33.6 mA @ +5 dBm).

I have expected much faster WiFi communication than ZigBee:( I actually don't prefer continuous mode, because of loosing some control about missing packets and disabling the possibility of power saving modes.

Jan