Error -50103 retrieving device temperature

[xl600]

Why is it that I cannot retrieve a PXI-6281 device temperature (From the Calibration Info property node) while an analog input task is running?  It seems a no-brainer to want to read the temperature while operating for long periods (To detect if there's been a drift in the self calibration).

Give it a try:

Start a continuous analog input task in Max on an analog card

Run this:

And you should get this:

"Error -50103 occurred at Property Node DAQmx Calibration Info (arg 3) in Cal_Info_Test.vi
Possible reason(s):
The specified resource is reserved. The operation could not be completed as specified."

Is the 6281 using an analog input task to read the sensor?

Thanks,

XL600

[JustNI]

Hi XL600,

If you try doing this entirely in LabVIEW, do you get the same error? For example, opening up the "Voltage - Continuous Input" shipping example, and adding the "Calibration Info" property node to the Acquire stage while loop is a quick way to test this.

Additionally, please ensure that you have no MAX Test Panels or other tasks running when you try this.

Justin

Applications Engineer 

National Instruments 

[Mcdan · Accepted solution]

xl600,

Yes, this device uses analog input to read the temperature sensor.  As such, you will be unable to read this while running an analog input task.

Hope that helps,
Dan

[xl600]

That's what I suspected.  This seems like an odd limitation in the design (And very obscurely documented, if at all).  Can't run more than one Ain task and it gets used up just to read the on-board PCB sensor.  Are all NI analog cards like this?

[Mcdan]

 I don't have much experience outside of multi-function DAQ devices (and some other DAQmx supported devices), so this answer only applies to them. Most of these devices (E Series, M Series, and X Series) use an analog sensor which requires an analog channel to read. There are some (maybe all) simultaneously sampling devices which do not have this limitation. For these devices, the best method I can think of to check would be to look at what internal channels this device supports. If you drop a DAQmx physical channel control, and configure 'I/O Name Filtering' to show internal channels, devices which list the channel "DevX/_boardTempSensor_vs_aignd are the ones with this restriction.

Note: For simultaneous sampling devices, you should be able to get this same information by creating a task, setting the DAQmx Channel->General Properties->Input Configuration->AI.InputSrc to something invalid, and examining the valid sources listed in the error.

This can be done using simulated devices if you're curious about any DAQmx supported devices that you don't have.  In lieu of finding this in documentation, which I could not, I think this would be your best method for determining this.

Hope that helps,

Dan

[xl600]

Thanks again for the tips!  Those internal names really do shine a light on what's going on inside the cards.