LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

why does datasocket not connect

I programmatically assign datasocket URLs to multiple indicators in a VI that I load in a SubPanel control.  The first time I load the VI and assign URLs I have no problem.  The second time I load the VI only the first indicator successfully activates.  The second indicator remains in a connecting state.  Why?  I am repeating the identical process when I load the VI into the SubPanel control.  I've enclose a PPT showing the DataSocket Server diagnostics.

 

Offline means I have not started sending data to the URL.  Online means I'm already sending data to the URL.

 

The Probe values are from a property node for the indicator within a while loop.  The last probe is the iteration value of the loop.  When the code is 'Active' the loop is quit.

0 Kudos
Message 1 of 11
(4,177 Views)

Do you get the same behavior without the subpanels? It will help troubleshoot this issue if we can just troubleshoot the datasocket part itself.

0 Kudos
Message 2 of 11
(4,144 Views)

yes, i get the same behavior whether I load in a SubPanel or not

0 Kudos
Message 3 of 11
(4,123 Views)

more information ...

 

As the DkSktURLs are initially assigned to indicators, they appear in the DataSocket Server Diagnostics window.  They change between read and write mode, mostly in write mode.  When the VI is removed, all the DkSktURLs disappear except for the one 'caught' in write mode.  When the DkSktURLs are reassigned to indicators, the second DkSktURL and any assigned afterwards, never appear in the DataSocket Server Diagnostics window.  The DtSktStatus Code for these indicators is always Connecting; Parsing URL.  What is happening?

0 Kudos
Message 4 of 11
(4,104 Views)

Could you post a JING Video of this behavior?

0 Kudos
Message 5 of 11
(4,082 Views)

my compute that is running the VI cannot be connected to the internet.  so I can not install Jing.  I've enclosed a PowerPoint document that hopefully will help explain the situation.

0 Kudos
Message 6 of 11
(4,050 Views)

I've enclosed some VIs that if you run will illustrate my problem.  testGen.vi should be run first. 

0 Kudos
Message 7 of 11
(3,956 Views)

You are missing several SubVIs needed to sun your code. Can you reproduce this issue using a simple one VI program?

0 Kudos
Message 8 of 11
(3,937 Views)

is this what is missing?  i thought it was part of LabVIEW 2010

0 Kudos
Message 9 of 11
(3,912 Views)

maybe these libraries will help get to the VIs

Download All
0 Kudos
Message 10 of 11
(3,902 Views)