TCP socket unexpected closing when processing a large volume of CAN traffic
Posted: Thu Feb 01, 2024 11:38 am
Hi,
I'm facing a problem with my ESP32 project, which consists of multiple and non periodic TCP socket closings and they are unexpected. After many tests, I realized that these closings are caused by the large amount of CAN messages that the device is processing and sending.
For the TCP process the device is communicating with another one using Modbus TCP protocol, although the communication is successful , in the end the socket is closed and reopened.
Both functionalities are separated into multiple tasks, I tried to make sure that CAN tasks are being processed in Core 1 while TCP communication is being processed in Core 0. Furthermore, I have attempted to guarantee that the TCP priority is higher than the other one's.
I rather avoid these closings at all costs.
Thank you so much in advance.
I'm facing a problem with my ESP32 project, which consists of multiple and non periodic TCP socket closings and they are unexpected. After many tests, I realized that these closings are caused by the large amount of CAN messages that the device is processing and sending.
For the TCP process the device is communicating with another one using Modbus TCP protocol, although the communication is successful , in the end the socket is closed and reopened.
Both functionalities are separated into multiple tasks, I tried to make sure that CAN tasks are being processed in Core 1 while TCP communication is being processed in Core 0. Furthermore, I have attempted to guarantee that the TCP priority is higher than the other one's.
I rather avoid these closings at all costs.
Thank you so much in advance.