How to programmatically set IO variable scaling?

[NI-hilator]

The scaling individual I/O channels on cRIO cards can be set at edit time through the shared variable properties dialog box.  Is it possible to access this programmatically at run time?  I have found the "Programmatic Module Configuration - Scan Mode" in the example finder.  

It shows simply connecting an IO reference to a property node, however the scaling is not one of the properties - only Range and Terminal Mode are available properties.  Also, the method shown does not seem very scalable.  I would like to be able to programmatically set scaling for all the analog channels on all my cRIO cards... 96 total. The use of a loop, shift registers and a compare seems a little less than elegant.  Could this be done with some sort of event?

Thanks in advance!

[[dk]]

You can use the SharedVariableIO property from the DSC module to programmatically configure the shared variable instance of the scan mode IO varibles:

https://www.ni.com/docs/en-US/bundle/labview-datalogging-and-supervisory-control-module/page/shared-...

I haven't messed with it too much, but you can try to use the generic variable properties to access them programmatically as well:

https://www.ni.com/docs/en-US/bundle/labview-api-ref/page/properties-and-methods/vi-server/variable-...

You would have to feed a reference from the specific project item to the variable property node to gain programmatic access. You can use this KB for a helpful as well.

I am playing around with a test project right now and if I get something going I will go ahead and post it.

[NI-hilator]

Thanks for the reply Daniel.  I have Labview Dev Suite but not the DSC module.  We are a small startup and don't see getting approval for DSC any time soon.  Any other approaches?

[NI-hilator]

Although I don't have the DSC Module, I do have the Runtime Module.  Should this give me access to the SharedVariableIO properties you suggested?

Thanks!

[[dk]]

SharedVariableIO properties are only available with the DSC module unfortunately.