12-06-2019 08:03 AM
For some reason, when a vi is loaded, any daqmx input physical channel controls become invalid if the device is not present (i.e. not turned on). This doesn't happen for output channel controls. Is there some way to prevent this behaviour? On my front panel, I have an array of clusters that define a physical channel, a channel name and the input range (and potentially a few other items). The idea is to make it easier for the user to set up and define the inputs without having to use NI-MAX. Most of the time these don't change, so you would think one could preserve the input values with "make current values default". However, whenever the vi loads the array is disabled - presumably because the input physical channel is invalidated (? a control array of numbers won't become invalid when a vi is loaded). Turning the device back on does not enable things and the array has to be redefined every time the vi is loaded. Annoying. Is there a way to prevent this?
12-06-2019 09:33 AM
I suspect you can fix this if you:
- right-click on the physical channel GUI control
- select "I/O Name Filtering..."
- adjust your options as needed (pay particular attention to "Allow Undefined Names"
-Kevin P
12-06-2019 09:45 AM
Nice idea, but no banana. I didn't know about that option. As far as I can tell the input and output channel controls are identical under "I/O Name Filtering". The default case allows undefined names. I tried playing with it but couldn't find anything that stopped the unwanted behaviour
12-06-2019 03:03 PM
I'm not 100% certain I understand your problem/question. Here's what I do for a USB 6000-series Multifunction DAQ device:
Bob Schor