Multifunction DAQ

cancel
Showing results for 
Search instead for 
Did you mean: 

Are there size limits in DAQmxGetDevDOLines

Hi all,

 

I'm using the text based DAQmx interface (Version 9.1.0) and try to find the names of all digital output terminals with the following code snippet:

 

 char data[1024];

DAQmxGetDevDOLines("Dev1", data, 1024);

 

and get always an incomplete string cutted at position 430 like this:

"Dev1/port0/line0, Dev1/port0/line1, Dev1/port0/line2, Dev1/port0/line3, Dev1/port0/line4, Dev1/port0/line5, Dev1/port0/line6, Dev1/port0/line7, Dev1/port1/line0, Dev1/port1/line1, Dev1/port1/line2, Dev1/port1/line3, Dev1/port1/line4, Dev1/port1/line5, Dev1/port1/line6, Dev1/port1/line7, Dev1/port2/line0, Dev1/port2/line1, Dev1/port2/line2, Dev1/port2/line3, Dev1/port2/line4, Dev1/port"

 

Are there any size limitations? Work arounds?

 

Thanks

 

0 Kudos
Message 1 of 3
(3,220 Views)
Hello,

unfortunately I’m not able to reproduce the problem you’re describing.
I tested the “DAQmxGetDevDOLines" function with a NI PCI 6289 board and get the following result:

6289/port0/line0, 6289/port0/line1, 6289/port0/line2, 6289/port0/line3, 6289/port0/line4, 6289/port0/line5, 6289/port0/line6, 6289/port0/line7, 6289/port0/line8, 6289/port0/line9, 6289/port0/line10, 6289/port0/line11, 6289/port0/line12, 6289/port0/line13, 6289/port0/line14, 6289/port0/line15, 6289/port0/line16, 6289/port0/line17, 6289/port0/line18, 6289/port0/line19, 6289/port0/line20, 6289/port0/line21, 6289/port0/line22, 6289/port0/line23, 6289/port0/line24, 6289/port0/line25, 6289/port0/line26, 6289/port0/line27, 6289/port0/line28, 6289/port0/line29, 6289/port0/line30, 6289/port0/line31, 6289/port1/line0, 6289/port1/line1, 6289/port1/line2, 6289/port1/line3, 6289/port1/line4, 6289/port1/line5, 6289/port1/line6, 6289/port1/line7, 6289/port2/line0, 6289/port2/line1, 6289/port2/line2, 6289/port2/line3, 6289/port2/line4, 6289/port2/line5, 6289/port2/line6, 6289/port2/line7

These are 883 characters.

Which board are you using?
Have you tried it with another board?
Have you tried it with a simulated board?

Regards
Ulrich
AE NI-CER

Message 2 of 3
(3,195 Views)

Hi Ulrich,

 

today I tried to reproduce my problem. But it works perfectly. It could be a problem with my debugger string display because the 430 seems to be correct for the string length. (USB-6251 simulated board)

 

Thanks

 

0 Kudos
Message 3 of 3
(3,187 Views)