LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

counter channel in daq assistant

I have a counter channel in DAQ Asstant. In previous vi's with analog inputs, I have had no problem propagating the channel name from the DAQ Asst. all the way through to the 'Write to Measurement.vi' where it appears as a column header for the data. In the case of this Counter Channel there are no attributes in the DDT wire. Is this normal for a counter input?
By the way, the channel is one of two counters available on a PCI-6143.
0 Kudos
Message 1 of 5
(4,105 Views)

Hi,

I do see the same behavior and will continue to investigate to see if this is a bug or expected behavior. In the meantime I believe I have found a work around for you the code is found below. I am adding the attribute to the data before it is sent to the measurement file. I hope this helps!!



Message Edited by jaced on 01-10-2008 03:29 PM
JaceD
Signal Sources Product Support Engineer
National Instruments
0 Kudos
Message 2 of 5
(4,079 Views)

Thanks Jace. I won't be able to get that code into the vi until late today or Monday, but I will let you know how it works.

Thanks again,

Dave

0 Kudos
Message 3 of 5
(4,063 Views)
Jace,
That example code did give me a good work around. Even though it does work I would still like to know if that is the expected behavior for the counter channel in that situation. It seems odd that it would differ from analog input channels in that respect.
I also have another application that utilizes counters and analog inputs that was developed using the DAQmx driver. It also lacked channel attributes and was therefore a problem in the data file (our data viewer requires channels be named in the header). It seems that when the channel is created using the polymorphic "Create Virtual Channel.vi" that channel attributes also do not appear in the data output from the "Read Channel.vi". I will try this method with that vi also.
Thanks much. Have a good weekend.
Dave
0 Kudos
Message 4 of 5
(4,052 Views)
Hi Dave,
 
This was reported to R&D (#4H9ENHQB) for further investigation. This is not expected behavior and will be invetegated for future releases. I hope this clears things up, Until this issue is resolved, the work around should suffice to accomplish your task. I hope this helps and have a great day!
JaceD
Signal Sources Product Support Engineer
National Instruments
0 Kudos
Message 5 of 5
(4,003 Views)