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
In tcp.c, line 35, setting TCP_NODELAY will make the TCP stack on the remote device (e.g. ESP8266) too busy with memory allocation and other things. I suggest to disable it and let TCP stack choose its own pace.
The text was updated successfully, but these errors were encountered:
It sounds quite reasonable. I used TCP_NODELAY flag merely for reducing latency, which I did a quick search on stackoverflow that said so. I have no idea of the side effect when interfacing low resource platform such as ESP8266 or other MCUs when TCP_NODELAY flag applied on PC side. You are welcome to modify the flag and create PR. By the way, this project is too old and I am not quite sure whether it still works in recent days.
Although a bit old, your DLL is now included in the official LCD smartie release and still works fine. Many thanks for your creation, which allows me to get rid of the serial cable.
I'm suffering with TCP_NODELAY when I create my own VFD display project and the ESP8266 frequently freezes and reboots due to WDT timeout. I suspect that TCP_NODELAY is messing up the TCP stack on the ESP8266.
By the way, I'm not using the native C++ SDK, but Micropython, whose slowness may be causing this problem. I'll switch to C++ and see if that fixes it.
In
tcp.c
, line 35, settingTCP_NODELAY
will make the TCP stack on the remote device (e.g. ESP8266) too busy with memory allocation and other things. I suggest to disable it and let TCP stack choose its own pace.The text was updated successfully, but these errors were encountered: