Scan List Configuration Error When Reading Across Multiple Channels

Updated Sep 14, 2023

Reported In

Hardware

  • NI-9220

Driver

  • NI-DAQmx

Issue Details

  • I noticed that the NI 9220 will always return Error -200284: Some or all of the samples requested have not yet been acquired. or Error -209866 occurred at Property Node DAQmx Timing despite the computer, version of DAQmx driver, or configuration.
  • When reading multiple channels on my NI 9220 AI module, I receive Error -209866: The hardware cannot acquire data from the configured scan list.
  • When I try to read channels that are spread far apart, I receive an error. I am able to read other channels that are closer together.

Solution

NI discovered an issue where certain scan list configurations cause the module to hang due to the FPGA running onboard the device. Subsequent use of the module with the affected scan lists or after the scan list will return error -200284. If using DAQmx 18.1 or newer, error -209866 will be thrown. This issue only affects users employing the module with the DAQmx driver.

This error occurs specifically when there are 2 active channels, then a string of 11 inactive channels, followed by another active channel. The affected scan lists are as follows:
  • 2003->CH0, CH1, CH13
  • 4003->CH0, CH1, CH14
  • 4005->CH0, CH2, CH14
  • 4006->CH1, CH2, CH14
  • 4007->CH1, CH2, CH14
  • 6003->CH0, CH1, CH2, CH14
  • 8003->CH1, CH2, CH15
  • 8005->CH1, CH4, CH15
  • 8006->CH2, CH3, CH15
  • 8007->CH0, CH1, CH2, CH15
  • 8009->CH0, CH3, CH15
  • 800A->CH1, CH3, CH15
  • 800B->CH0, CH1, CH3, Ch15
  • 800C->CH2, CH3, CH15
  • 800D->CH0, CH2, CH3, CH15
  • 800E->CH1, CH2, CH3, CH15
  • 800F->CH0, CH1, CH2, CH3, CH15
  • A003->CH0, CH1, Ch13, CH15
  • C003->CH0, Ch1, CH14, CH15
  • C005->CH0, CH2, CH14, CH15
  • C006->CH1, CH2, CH14, CH15
  • C007->CH0, CH1, CH2, CH14, CH15
  • E003->CH0, CH1, Ch13, CH14, CH15
Please avoid using the affected scan lists. If the previously mentioned scan lists were used, you can perform the steps below to clear the error:
  • Reset the chassis.
  • Unplug and re-plug the module in the chassis.
  • Or power cycle the chassis in order to get the module back into a working state.