Well - there is no firewall between the UDS-10 and the server. I will try to get you the netstat output by tomorrow, because it takes a while before it stops logging. Thanks in advance for all your help - I almost re-wrote the code in C++ to see if I had more luck. Here is the netstat output when it's working:
tcp 0 0 localhost:36903 uds-10#1:10001 ESTABLISHED
tcp 0 0 localhost:36939 uds-10#2:10001 ESTABLISHED
If you want to see more detailed netstat info in my next post, let me know. | [reply]
[d/l] |
In the meantime - what do you think the state would be after the process stops working, and how would you resolve the problem, given the netstat data? | [reply] |
I don't know that I am expecting anything from netstat -- If the output has something other than ESTABLISHED than that may point to other problems, Can you check the config on the Serial->Net plug and tell me what you have set for: Inactivity Timeout: and Inactivity Timer: under the Additl settings? Default is enabled This can cause the plug to drop connections after a timeout period -- and if it does not handle this properly can leave the port on the logging server side in one of the WAIT states that can make the port apear to be used but really is just partally connected.
-Waswas
| [reply] |
Good thinking:
Inactivity Timeout = Enabled
Inactivity Timer = 0:0
I also noticed something called "Packing Algorithm" that might be helpful. If I could get my UDS to send out a unique charachter every so often, that should also keep my connection alive.
| [reply] |