Task channel order bug in MAX?

[cpede]

Using MAX version 4.2.1.3001 on Windows Vista x64.

Please look at the 3 channels defined in the Task.

I have specified different ranges for each, but the ranges are applied to the wrong channels?

Am I doing something wrong?

-cpede

[Tom_W_[DE]]

Hi cpede-

Which DAQ device are you using?  What ranges have you specified for the other channels?  What are the characteristics of the signals you have applied to the three channels in the task (amplitude of the sine wave, etc).

[cpede]

I'm using simulated devices, so it can be easily reproduced.

I added a CompactDAQ frame, and added two NI 9215 USB devices to the two first slots. Like this:

NI cDAQ-9172: "cDAQ1"
     1: NI 9215 (BNC): "cDAQ1Mod1"
     2: NI 9215 (BNC): "cDAQ1Mod2"
     3: Empty
     :

Then I added a NI-DAQmx Task with the following 3 channels:

Voltage_0     0     cDAQ1Mod2/ai3     NI 9215 (BNC)     Range: 6-10V
Voltage_1     1     cDAQ1Mod2/ai2     NI 9215 (BNC)     Range: 0-10V
Voltage_2     2     cDAQ1Mod1/ai3     NI 9215 (BNC)     Range: -10-10V

The signals are the standard signals generated for the simulated devices.

-cpede

[Tom_W_[DE]]

Hi cpede-

Thanks for the detailed information on how to reproduce the issue.  I was able to reproduce this with simulated hardware, but the good news is that I was unable to reproduce with physical (i.e. "real") hardware.  So, once you begin testing with physical hardware this phenomenon will not be present.  The behavior is indeed incorrect for the simulated case, so I am recording CAR #4HKGOJFB for further investigation by DAQ software R&D.

Thanks again-