06-24-2003 07:24 AM
06-24-2003 09:35 AM
04-27-2011 08:28 AM
I am expiriencing the same issue. I am only using a TCP read in one VI and a write in the other VI. The read VI got that error. The program will run if I erase the errors and I am then able to send data between the two VIs.
Thanks
04-27-2011 08:33 AM
Look at the second possible explanation for your error: The network connection was refused by the server. That seems much more likely. Some of the error codes are "reused" from other programs or the OSes and as a result the same code is used for two different kinds of errors. Since you have a network and not a serial port, the second one applies.
So, look for a network issue.
Lynn
04-29-2011 05:06 PM
Lynn,
Good point. Unfortunately that still didn't work.
Even if I run the labview data client examples for TCP I get the same error.
I tried disabling my firewall. At this point I am very confused. I am sure that I am doing something wrong as this should be easy... What else should I check?
Thanks for the help!
04-29-2011 05:12 PM
In the example you posted you're trying to make a connection, but the listener (your other VI) isn't running. You need to run the VI that has the listener first. Otherwise, the connection will fail. The examples that ship with LabVIEW (Simple Data Client and Simple Data Server) provide explicit instructions on which to run first.
06-10-2014 12:20 AM
hi
Even i am facing the same problem. i can run the server and client vi in same pc, without giving ip address in client. But its not working if I use two PC's. Itis giving the above error as u all r getting. May i please know what might be the reason.
Thank u in advance.
10-10-2015 05:52 AM
10-10-2015 05:34 PM
What's a "TPC/IP to Serial" converter? That's like saying I have an "Unleaded gas to fuel line" converter.
11-12-2015 03:50 PM
TCP buffer size can be restricted by OS or hardware. OS may be unnecessarily limiting the buffer size. Both the sender and receiver need to be set appropriately. Windows 7 has a fixed default TCP receive buffer of 64 kb, scaling up to 16 MB through "autotuning". You might find details you need here: http://www.onlamp.com/pub/a/onlamp/2005/11/17/tcp_tuning.html