02-07-2014 02:16 PM
One of my coworkers is running into an odd behavior that he feels has changed overnight.
When he creates a new vi in the project environment (it can be a brand new project/vi) and puts down a "DAQMx Physical Channel" control on the vi's front panel it doesn't show the actual channels on his development system (i.e a list of Dev2/ai0, Dev2/ai1,... on my machine).
Yet, if he creates a vi, with a project being opened (new project or existing) the control operates ok. It is driving him batty, he is one that gets very upset when LabVIEW behaves in a manner that isn't consistent, and has come to me. I, in turn, come to the power of crowd sourcing an answer!
LabVIEW 2012 sp1
As always, Thanks in advance.
02-10-2014 07:16 PM
Hi Putnam,
I get the expected behavior on my machine (drop down the DAQmx Physical Channel control from the palettes and see the available channels on my machine). If he right-clicks on the control and goes to "I/O Name Filtering..." and plays around there, does that fix the problem? At the least, he should have "External Channels" checked. I apologize if this seems over-simple, but it's worth a shot.
As he is able to do this in the block diagram using a VI, I am assuming that the device shows up in MAX and he can properly communicate with it when he runs the VI that allows him to select the desired terminals?