Data Acquisition from NI PXIe-1062Q

Hello,

I'm using a machine with the Data Acquisition Toolbox and I'm trying to communicate with an NI PXIe-1062Q device. I am running Matlab Version R2012a 64 bit.I'm a able to communicate with my device but I am unable to run a Session in the foreground. To walk you through what I've done:

1) I can see the device is connected using daq.getDevices. This lists all my analog input and output subsystems, and my input and output counter subsystems. My device ID is 'ANADAQ1' and for whatever reason I see the instrument not as a NI PXIe-1062Q but rather as a NI PXIe-6358. I don't know what that's all about.

2) s = daq.createSession('ni') runs without a hitch.

3) s.addAnalogInputChannel('ANADAQ1','ai0','Voltage') also runs without a problem.

4) I can sample my analog input channel using s.inputSingleScan without any difficulty. I even read a proper voltage.

5) When I attempt to run the session using s.startForeground I get the following error:

NI Error -89136:

Specified route cannot be satisfied, because the hardware does not support it

Property: DAQmx_RefClk_Src

Request Value: /ANADAQ1/PXI_CLK10

Task Name: _unnamedTask<C4>

Status Code: -89136

Any ideas on what's going on?

Much appreciation

-David

Answer 1

[Manisha]

Hi David,

It seems that you are using the X- Series device NI PXIe-6358 on the NI PXIe-1062Q PXI chassis. The command daq.getDevices returns you the device and not the chassis and thus you see PXI 6358 and not PXIe1062Q.

R2012a added a new functionality to set your devices reference clock to the PXI chassis backpane 10 MHz clock PXI_CLK10, so that all the modules in your chassis will share the same clock. However, in you case it seems to error out at that point. X-Series boards do support reference clock synchronization, so I not sure about the exact reason you are seeing this. However, you can disable this functionality using these commands:

daq.reset
daq.HardwareInfo.getInstance('DisableReferenceClockSynchronization',true);

You will need to use the command after every daq.reset. I would also recommend that you contact technical support regarding this issue so that they can get to the root of this problem.

Hope this helps,

Manisha

[Peter Selivanov]

Thank you, Manisha. It does help a lot.

[Ran Sha]

Thank you Manisha ! I had the same problem, and this solved it ! Much appreciated.

-Ran