Hi,
TCP/IP communication errors most often are caused by timeout conditions in either the LabVIEW TCP/IP VIs or at the operating system level. If you are sure that the network cable is properly connected to the slave device, a timeout condition of some type is likely the cause of the errors. The particular error code and symptoms associated with the error depend on whether a LabVIEW operation timed-out first or if an error is generated first by the operating system.
There are two typical error codes in cases where TCP/IP communication fails as a result of a timeout condition:
-Error 56 is generated when an operation exceeds the user-specified time limit. This error is caused by the LabVIEW code not receiving a network response in the defined time limit.
-Error 66 occurs if the TCP/IP connection is closed by the peer. In this case, Windows notices that no data is returned within a reasonable time, and it closes the TCP/IP connection. When LabVIEW attempts to communicate after Windows closes the connection, error 66 is the result.
Try to increase the length of the timeout value wired to the timeout terminal of the event structure in the Ethernet Master VI. Also, make sure your command that you are trying to write is formatted according to the manual for the slave device you have. Sometimes if the data is formatted wrong the slave cannot recognize it.
Regards,
Message Edited by Ryan_F on 10-23-2009 11:00 AM
National Instruments
Applications Engineer