Error -200284 When Performing Strain Calibration on NI-DAQmx Tasks With CJC Built-In Thermocouple Modules

Updated Mar 15, 2024

Reported In

Hardware

  • CompactRIO Controller
  • cDAQ-9189
  • cDAQ-9185
  • NI-9211
  • NI-9212
  • NI-9213

Driver

  • NI-DAQmx

Issue Details

I have a CompactRIO (cRIO) controller daisy chained with CompactDAQ chassis (cDAQ). I have a NI-DAQmx task that contains a thermocouple module inside the cRIO and a strain module inside the cDAQ-chassis, so this is a multi-device task. When running the NI-DAQmx code (developed in LabVIEW) shown in the VI below, error -200284 shows up just after the DAQmx Perform Bridge Offset Nulling Calibration.vi (this one was used in the example) or  DAQmx Perform Shunt Calibration Ex Strain.vi. The issue is only present when the CJC Source input of the DAQmx Create Channel (AI-Temperature-Thermocouple).vi is configured as Built-In.
VI.png
Error -200284 occurred at DAQmx Perform Bridge Offset Nulling Calibration.vi:1900001
Possible reason(s):
Measurements: Some or all of the samples requested have not yet been acquired. To wait for the samples to become available use a longer read timeout or read later in your program. To make the samples available sooner, increase the sample rate. If your task uses a start trigger,  make sure that your start trigger is configured correctly. It is also possible that you configured the task for external timing, and no clock was supplied. If this is the case, supply an external clock.
error.png
I am using a cRIO-9047+NI-9213 and cDAQ-9189+NI-9236. Both the cRIO and the cDAQ are TSN-enabled. How can I fix this issue?
 

Solution

This is a known issue and R&D is aware of it. There are no plans to fix this issue in the short term, however, the following workarounds can be considered.
  • Use separate tasks for the Strain and Thermocouple modules.
Separate Tasks.png
  • Configure the calibration first (only with the strain module) and then configure both modules together.
Workaround2.png
 

Additional Information

This issue should be only present when configuring NI-DAQmx multidevice tasks. If the Strain/Thermocouple modules are both in the same cRIO controller or cDAQ chassis the code should run with no issues.