06-25-2019 11:52 AM
Ive got the Network Variable working simple enough.
I have a DAQ VI that will record data and such and Id like to peak in from another VI on another system to work with the DAQ data.
Works no problem.
However, I often run multiple instances of the DAQ VI recording different tasks from different devices etc.
From the client side its easy enough to include a selection tool to specify which shared variable to look at.
From the server side is where Ive hit a snag.
If I have an executable publish at runtime and as far as the project goes, Ive only created one shared variable.. I was hoping somehow the SVC will detect an redundant instance of the server VI and automatically publish "sharedvariable2".
But in my test case with multiple instances of the same server VI running, they simply write over one another to the same "sharedvariable1", which I thought would more likely be the case.
So from the client side you can still only select the same variable to monitor, whos value is being written to by several instances of the same server VI.
Perhaps I can look at the instructions for programmatically publishing the shared variable as suggested for labview version prior to 2009, but I was wondering if perhaps there was any insight on the matter here.
Thanks
06-27-2019 02:44 PM
Fullauto2009,
Where are the instances of the server VI running? And are they saved as the same name? I've had issues in the past of multiple instances being saved as the same name doing the same behavior as you are seeing. All I had to do was save them as different names and it worked fine after that.
Garrett