LabVIEW Idea Exchange

cancel
Showing results for 
Search instead for 
Did you mean: 
viScience

Full Support of Network Shared Variables

Give LabVIEW full parity with the CVI 'Network Variables' API.

CVI has many useful API functions such as adding a NSV to a existing deployed process

or registering for SV change events that are impossible in LabVIEW.

5 Comments
David_L
Active Participant

I'm not very familiar with CVI or Network Variables, but there is a lot more Shared Variable functionality build into the LabVIEW DSC module.  Have you looked at this?  Is there anything missing from the Shared Variable functions in DSC that you'd like to see?


To specifically address the two examples in your post, you can definitely add a new SV to an existing process with DSC and you can register shared variable events in the LabVIEW event structure.

AristosQueue (NI)
NI Employee (retired)
viScience
Active Participant

I guess my point is that native functionality of the SVE, which is exposed in the CVI Network Variables API, comes with the standard CVI development system.

The same should be the case with LabVIEW.  Extensions to the SVE to support such things as IO servers, alarms, citadel logging etc. could be considered to be the added value of the DSC.  Historically, LabVIEW seems to only grudgingly been given access to the SV API, IMHO this is one of the reasons why there has been so much discontent with the adoption of the technology. 

viScience
Active Participant

The original idea exchange post (shared variables are deliberately crippled) was not so much of a suggestion as it was a discussion on the topic of "enhanced" global variables and 'stative' objects.

My suggestion is very specific - give the native LabVIEW SV API parity with CVI.

 

Laura F.
Active Participant