Reyan

Hello Stéphane and Dave First thanks Dave for such a great work!! and extensive documentation! shared with the community. Stéphane, I was struggling with this issue for weeks... I didn't know what to do. I think it will be nice if we can expose the flush of TCP socket before any reading or error, but this solution is robust and guarantee the response match with request, which is better. It would be nice if the solution can be integrated into the Library as new version for next folks and future downloads....

Yes, I tried also, seems a just temporary delay in network. I am not sure what to do, I will add a delay time of few seconds, when an error happened, following by close/open, to see if that fix it. So it is only adding delay before close/open again. Thanks

Yes, the problem is that sometimes there is no apparent error, seems a just temporary delay in network, so it is hard to identify when to close/open connection again. I am not sure what to do. Thanks

Hello Dave Thank you so much for sharing nice work. We are using snap7 on C++ in Ubuntu 18. I am working on a system that sometimes experience an overload on the network and CPU, and when that happens we have seen old data in TCP socket, so the new reading is actually taken bytes previous read operation. Please is there a way to clear the TCP socket on Client before send a new read request to guarantee no residual is left from previous operation ? Thanks Reyan

Hello Dave Thank you so much for sharing nice work. We are using snap7 on C++ in Ubuntu 18. I am working on a system that sometimes experience an overload on the network and CPU, and when that happens we have seen old data in TCP socket, so the new reading is actually taken bytes previous read operation. Please is there a way to clear the TCP socket on Client before send a new read request to guarantee no residual is left for any reason ? Thanks Reyan

Hello Dave Thank you so much for sharing nice work. We are using snap7 on C++ in Ubuntu 18. I am working on a system that sometimes experience an overload on the network and CPU, and when that happens we have seen old data with new data mixing together, so the new reading is actually taken previous read operation. Please is there a way to clear the TCP socket on Client before send a new read request to guarantee no residual is left for any reason ? Thanks Reyan

Hello Dave Thank you so much for sharing nice work. We are using snap7 on C++ in Ubuntu 18. I am working on a system that sometimes experience an overload on the network and CPU, and when that happened we have seen old data with new data mixing together, so the new reading is actually taken previous read operation. Please is there a way to clear the TCP socket on Client before send a new read request to guarantee no residual is left for any reason ? Thanks Reyan

Hello Dave Thank you so much for sharing nice work. We are using snap7 on C++ in Ubuntu 18. I am working on a system that has sometimes experience an overload on the network and CPU, and when that happened we have seen old data with new data mixing together, so the new reading is actually taken previous read operation. Please is there a way to clear the TCP socket on Client before send a new read request to guarantee no residual is left for any reason ? Thanks Reyan