09-09-2010 06:45 PM
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.
09-13-2010 03:55 PM
Do you get the same behavior without the subpanels? It will help troubleshoot this issue if we can just troubleshoot the datasocket part itself.
09-15-2010 05:58 PM
yes, i get the same behavior whether I load in a SubPanel or not
09-16-2010 06:26 PM
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?
09-17-2010 05:10 PM
Could you post a JING Video of this behavior?
09-21-2010 04:44 PM
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.
10-14-2010 11:17 AM
I've enclosed some VIs that if you run will illustrate my problem. testGen.vi should be run first.
10-15-2010 03:37 PM
You are missing several SubVIs needed to sun your code. Can you reproduce this issue using a simple one VI program?
10-18-2010 02:18 PM
is this what is missing? i thought it was part of LabVIEW 2010
10-18-2010 03:48 PM
maybe these libraries will help get to the VIs