From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
NI-DAQmx 9.3 contains bug fixes for the following issues present on X Series devices (NI USB-63xx) when used with earlier versions of the driver. If you believe any of these issues have the possibility of affecting your application, NI recommends that you upgrade to NI-DAQmx 9.3.
Digital I/O Glitches on Computer Restart
In NI-DAQmx 9.2.3 and earlier, if a USB X Series device remains powered during a computer restart, the digital lines will glitch high for approximately 1-2 seconds before loading programmable power-up states. This behavior only occurs on lines that were previously being driven low at the time of the the computer restart. If a line was being driven high or configured as an input (i.e. tri-state) at the time of the restart, then the glitch would not occur.
Starting with NI-DAQmx 9.3, the digital lines retain their original value until the programmable power-up states are loaded.
Digital I/O Returns/Generates 0 in Some Cases:
In DAQmx 9.2.3 and earlier, USB X Series devices with 32 digital I/O lines on port 0 (NI USB-6343, NI USB-6353, and NI USB-6363) may return or generate 0 lines if either of the following cases are met:
The behavior may be worked around by including the lines mentioned above, but has been corrected for in NI-DAQmx 9.3.
Analog Input Channels Swap in Some Cases (Multiplexed Boards Only)
In DAQmx 9.2.3 and earlier, multiplexed USB X Series devices may return data from the incorrect channels if the following events occur sequentially:
If the device is in the middle of converting samples when it is stopped (step 3 above), then upon restart DAQmx will return data from the incorrect channels.
Encountering this issue should be very rare given that there are not any obvious use-cases for performing the above steps as described. The behavior is corrected in NI-DAQmx 9.3.