You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When trying larger amounts of data through (+18kB/s) a socket (_espClient::SendTCP()), sending routine often times out waiting for ESP reply. This is caused by the unexpected reply from the ESP, or wrong logic in the processing function triggered by the ISR.
This bug limits the speed to 4-5kB/s instead.
Steps to reproduce:
Open a socket to TCP server (ESP8266::OpenTCPSock)
Periodically (200Hz) send small chunk of data (100B) using ESP8266::GetClientBySockID()->SendTCP()
Observe the amount of data received on the server side
Observe TX, Rx lines from the ESP with logic analyzer
Expected behavior:
Login analyzer:
Timing to send the data fits with the baud rate being used
Time between consecutive sends fits with the sending frequency
TCP server:
data arrives at a rate of 19.5kB/s +/-5%
Actual behavior:
Login analyzer:
Timing to send the data fits with the baud rate being used
Time between consecutive sends is the sending frequency, plus few milliseconds that it takes for watchdog to time out
TCP server:
data arrives at a rate of 4-5kB/s +/-5%
The text was updated successfully, but these errors were encountered:
When trying larger amounts of data through (+18kB/s) a socket (_espClient::SendTCP()), sending routine often times out waiting for ESP reply. This is caused by the unexpected reply from the ESP, or wrong logic in the processing function triggered by the ISR.
This bug limits the speed to 4-5kB/s instead.
Steps to reproduce:
Expected behavior:
Login analyzer:
TCP server:
Actual behavior:
Login analyzer:
TCP server:
The text was updated successfully, but these errors were encountered: