03-03-2023 05:24 AM
Hi all...
Attaching the code snippet...
- The Device is a Ethernet data logger
- Was working fine for a few years
- It failed and was sent to Service
- After that I can only ping the device successfully
- But the LV app throws a "Error 66" in the TCP read Function
Not sure if the Port 502 was changed when servicing ( we are waiting for response the vendor on this ) ... is there any way to find out on which port it will communicate ? Or what else can go wrong ?
Hope someone can help !
Thanks.
03-03-2023 04:53 PM
All you can do for the port entry to some 3rd party service is know what it is. But you're connecting just fine.
Error 66 means the remote side of the connection disconnected you. The write succeeds but you get the error once you try to read data back. My guess is it didn't like the data you sent it and so it just closes the connection. You'll want to look up the current documentation and see if anything changed about handshakes, packet formatting, etc.