LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

TCP/IP

Hi,

Whenever I run the Data Server and Data Client examples Labview on the server
machine completely "locks up". Windows reports "not responding" and the Labview
task has to be ended. I have setup the TCP/IP preferences and am using the
known IP address of the server machine. I am using port 65535, but it has
failed this way on many different port numbers. This has also occurred on
many different machines. Does anyone have a suggestion? I must be doing something
basically wrong. By the way it does work OK if all run on the local host
machine (ie. a single machine).
Cheers,
Nick...
0 Kudos
Message 1 of 3
(2,753 Views)
In article <384b57a5@newsgroups.ni.com>,
"Nick Cole" wrote:
>
> Hi,
>
> Whenever I run the Data Server and Data Client examples Labview on the
server
> machine completely "locks up". Windows reports "not responding" and
the Labview
> task has to be ended. I have setup the TCP/IP preferences and am using
the
> known IP address of the server machine. I am using port 65535, but it
has
> failed this way on many different port numbers. This has also occurred
on
> many different machines. Does anyone have a suggestion? I must be
doing something
> basically wrong. By the way it does work OK if all run on the local
host
> machine (ie. a single machine).
> Cheers,
> Nick...
>
I happened to online collect my instrument data by labview with TCP/I
P.
It works very well. I even can show the signals nicely by running the
TCP/IP client in my home (dial up network) while running TCP/IP server
binding to the instrument in my Lab.

Look, you have to make sure several things are correct:
1. your network is working--computers are "networkly" connected
properly and not too slow.. 6000ms for a round trip (RTT)?

2. the port number is fine.(not same as the other, fg. 3444, 8888...)
Note that the port numbers in the server and client are IDENTICAL.

3. Running the server b4 you run the client.(you did, I think, b/c you
run it well in localhost.)

4. Why not use the numerical IP address instead of host name? I use host
name like abc.deja.com... works well

Still not working?

luck,
--
G. Chen
Ph.D. Candidate
Ohio Univeristy, Athens, OH
Nothing can dim the light which shines from within.


Sent via Deja.com http://www.deja.com/
Before you buy.
0 Kudos
Message 2 of 3
(2,753 Views)
Nick

You must disable DNS and RAS dialup connection in order to work smoothly
with
TCP/IP communication in LabVIEW.
At least that's if you don't want to transmit data over a Modem-line 🙂

The problem is that every time you make a connection, windows tries every
way to connect to that client. Even with a modem you have not dialed in
with. So windows will wait until it timed out.

Hope this helps

Happy wirings

Tom Limerkens
tom . limerkens @ imce . cit.be





Nick Cole wrote in message <384b57a5@newsgroups.ni.com>...
>
>Hi,
>
>Whenever I run the Data Server and Data Client examples Labview on the
server
>machine completely "locks up". Windows reports "not responding" and the
Labview
>task has to be ended. I have setup the TCP/IP preferences and am using the
>known
IP address of the server machine. I am using port 65535, but it has
>failed this way on many different port numbers. This has also occurred on
>many different machines. Does anyone have a suggestion? I must be doing
something
>basically wrong. By the way it does work OK if all run on the local host
>machine (ie. a single machine).
>Cheers,
>Nick...
0 Kudos
Message 3 of 3
(2,753 Views)