Re: TCP error 66

2004-02-19 Thread Ben
It seems you do not want to suspect the other node! I will monitor this Q to see if others post. Please keep us updated on what you find. Trying to help, Ben

Re: TCP error 66

2004-02-19 Thread kmoorthy76107
Hi, Thanks for your prompt response. The other node is also a PC (that acts as a data collection unit)which is connected to a bunch of sensors. The sensors feed in data to the other node (PC) and I am collecting the data, analyzing it and finally displaying it with alarm conditions. The other nod

Re: TCP error 66

2004-02-18 Thread Ben
Error = 66 is LabVIEW: The network connection was closed by the peer. This indicates the peer (i.e. the other node) closed the conncetion. This leads me to believe the the "issue" is not on your XP machine, but the other node. I have seen this error when doing TCP/IP based interactions with a

TCP error 66

2004-02-17 Thread kmoorthy76107
Hi I use LV 7, version 7.0 on a Windows XP machine. I am using TCP/IP vi's to read data over the LAN. I am able to receive the data over the LAN, but I keep getting error 66 in the TCP Read.vi My VI stops after running for 8-9 hours. HOw can I avoid that error 66? Also, I am not saving any of the