11-30-2005 06:58 PM
12-01-2005 05:14 PM
Hi John,
I don't think I'm totally understanding what's occurring when you lose the DataSocket connection. Could you please post the exact text of the error message you're receiving?
Thanks!
Megan B.
National Instruments.
12-14-2005 05:52 PM
Thanks for your response.
The problem is that when the datasocket connection is droped for some reasons at the client side and reconnect again, there're two datasocket connections turning up on the datasocket server and there is no data updated in this case. It seems the old datasocket connection hasn't been disconned on the datasocet server. I was told by NI that it will take 30S (using ethernet conneciton) for the datasocket server to kill the old connection. In this case I'm using a dialing-up modem for the communication. Could you help me to sort it out?
Kind regards
John
12-15-2005
01:54 PM
- last edited on
11-06-2025
01:39 PM
by
Content Cleaner
Hey John,
How is your VI setup? Maybe you could post it and we could take a look at it to make sure you are doing things correctly. I don't really understand what you are doing here. You are reading and writing from machine A? What is machine B doing? Do you just have two machines connected with a 56k dialup modem? Or are they connected via a network? Are you just sending the stuff out on A and receiving it on A? You can't close the writing datasocket from the reading datasocket program. You would have to be controlling that VI. You can just simply have the writing datasocket close the connection after a long delay or something.
Here is a great document that overviews datasockets: Integrating the Internet into Your Measurement System – DataSocket Technical Overview