LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Labview Datasocket momentarily locks up

Labview Datasocket Ver 4.1(36) for LV 7 momentarily freezes when another socket connects. Simple example publish a dynamic tag to DS Server then subscribe to that tag from another network PC. I've tried this on multiple machines and the results are similar. The DS Server packets stop incrementing and the Server/Diagnostic window becomes unresponsive for 5-10 seconds.

Any help would be appreciated..
0 Kudos
Message 1 of 5
(3,350 Views)
I just tried this and I don't see the same behavior. I am running on XP with LabVIEW 7.0. I ran the server and the diagnostic, and then I ran the DS Writer example. On another computer I then ran the DS reader example. There was no pause in the packets and the diagnostic tool updated and worked fine without becoming unresponsive.
0 Kudos
Message 2 of 5
(3,350 Views)
So far I've tried serving from 3 different machines 1 of them has just been reformatted. I verified what I saw yesterday using the DS Reader/Writer examples and found the same thing. I setup the DS Server on machine 1 along with the writer and everything works good. But as soon as I launch the Reader the server hangs and the Reader times out, to get around this I set the reader to never time out and after 8-15 sec the server continues and the the reader can see the data. I wanted to rule out the network so I connected 2 PC's with a crossover cable assigning them 10.1.1.1 and 10.1.1.2 and saw the same reaction.

Both PC's are logged in as the same user.
0 Kudos
Message 3 of 5
(3,350 Views)
I observed the same behaviour of the DSS 4.0 (36) first PC with WXP, second PC with W2K. Furthermore, in the Windows Task Manager, DSS appeared with "no response". After 5-10 seconds it appeared again with ok-status.
I used the DSS on both machines : same behaviour.
0 Kudos
Message 4 of 5
(3,350 Views)
I am experiencing the same type of problem. I have one computer as datasocket server, one as writer, one (or more) as reader, and it takes up to 20 seconds for the connection to be made, all the while both writer and reader(s) appear "frozen" or update very, very slowly. However, once the connection is made, the data moves quickly. If this is not "normal" behavior then I really want to know what I am doing wrong!
0 Kudos
Message 5 of 5
(3,350 Views)