LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Using default signal names for dropdown boxes?

Newbie question: I'm starting to use LabVIEW with a 6025E DAQ. In VIs, I'd like the various input and output dropdown boxes to show the available pins of the 6025E. E.g. ACH8, DIO3, PB0, etc. I assume these names must exist as some sort of default config file or something that installed along with the 6025E, but I can't find it.

Example: Say I want to write to Port B, line 5. I copy the Write to Digital Line.vi into my main VI, and then create constants for the digital channel and line inputs. But when I go to put values into these constants, there is no guidance. Figuring out that line should be 5 is easy. But it takes a bit of trial and error to determine that Port B corresponds to channel 3. So it would be n
ice if the dropdown boxes could be limited to the hardware at hand, and the choices have logical names (i.e. Digital I/O, Port A, Port B, Port C, and PB0, PB1, PB2, etc.).

Now I realize that there is the whole Measurement & Automation Explorer route with creating DAQ Virtual Channels in the Data Neighborhood, but this doesn't seem to be quite the solution I'm after. First of all, I'd have to create a bunch of channels by hand: two for every I/O line (one for read, one for write), two for each port, etc. This seems a bit unnecessary since it's clear that MAX already has all of this info--I just want it to generate the virtual channels for me. Secondly, this doesn't address those channels which aren't in the I/O category (SCANCLK, EXTSTROBE, PFI0/TRIG1, etc). It seems that the main use of virtual channels is for analog signals that need scaling or if one wants to name their signals with specific titles (e.g. Vertical Door Actuator 1).

So is there another solution that I'm missi
ng here?
0 Kudos
Message 1 of 2
(2,638 Views)
Hello;

Unfortunately, those names are only used for identification of the connector pins and are not passed to MAX or even NI-DAQ. That is only a guidance for the users to identify which pin corresponds to which signal.

The way to go about what you want is to create virtual channels that would relate the channels to the pin numbers.

Regards
Filipe A.
Applications Engineer
National Instruments
0 Kudos
Message 2 of 2
(2,638 Views)