This document contains the NI-HSDIO known issues that were discovered before and since the release of NI-HSDIO 2025 Q3. Known issues are performance issues or technical bugs that NI has acknowledged exist within this version of the product.
Not every issue known to NI appears on this list; it is intended to show the most severe and common issues that you may encounter and provide workarounds when possible. Other technical issues that you may encounter could occur through normal product use or system compatibility issues. You may find more information on these issues in NI’s Product Documentation, Knowledgebase, or Community; see Additional Resources.
|
Bug Number |
Legacy ID |
Description |
Details |
|---|---|---|---|
| 382895 | 183465 |
Using script triggers with Hardware Compare results in uncertain HW compare error locationsAny script statement that relied on external events will add an unknown delay to the locations of all the HW compare error samples decteted. Examples of such statements are: WAIT UNTIL ScriptTriggerN REPEAT UNTIL ScriptTriggerN Because the HW compare engine is running while the script operation waits, it is impossible to HW compare errors to digital pattern locations.
Workaround: If possible, do not rely on external triggers when the HW Compare engine is active. |
Reported Version: NI-HSDIO: 1.5.4 Resolved Version: N/A Added: Aug 14, 2012 |
| 259697 | 346946 |
While using Scripts, reloading a different waveform with the same name as an existing waveform may generate an incorrect waveformTo optimize performance and reduce memory usage, use scripting. If the waveforms are known before the script is written to memory, the behavior is as advertised. However, if a script is loaded, and then a waveform is modified (overwritten, deleted and then loaded with same name), the HSDIO card may or may not generate the correct waveform and never throws an error. Workaround: After changing the waveform, reload the script. |
Reported Version: NI-HSDIO: 1.8.1 Resolved Version: N/A Added: Aug 14, 2012 |
| 259896 | 306808 |
The NI PXIe-6544/6545/6547/6548 may not utilize the full bandwidth of the PCI Express bus.In rare cases, the NI PXIe-6544/6545/6547/6548 may not utilize the full bandwidth of the PXI Express bus. These modules are x4 PXI Express devices, which are capable of using up to four 2.5 Gbps bus data lanes. Start-time negotiation between the PXI Express controller and the device may result in the device using only one or two data lanes. The result is reduced performance when reading or writing large amounts of waveform data. Workaround: This situation is normally corrected the next time you restart your system. For more information, contact NI Technical Support at ni.com/support. |
Reported Version: NI-HSDIO: 1.7 Resolved Version: N/A Added: Jul 1, 2011 |
| 259646 | 306810 |
NI-HSDIO generates an error with an unknown status code when allocating streaming waveforms that are not 128-byte aligned.NI-HSDIO generates an error with an unknown status code when allocating streaming waveforms that are not 128-byte aligned. Workaround: When allocating streaming waveforms, ensure that they are 128-byte aligned. |
Reported Version: NI-HSDIO: 1.7 Resolved Version: N/A Added: Jul 1, 2011 |
| 259662 | 306816 |
Some Windows power management modes terminate in-progress NI-HSDIO operations.NI recommends that you disable Windows power management modes, such as sleep, standby, and hibernate when using this product. These modes terminate any NI-HSDIO operation in progress. Notice that in Windows 7/Vista or on a laptop computer, the default power management settings are likely to enable sleep mode. Workaround: Disable Windows power management modes. For more information, contact NI Technical Support at ni.com/support. |
Reported Version: NI-HSDIO: 1.6 Resolved Version: N/A Added: Jul 1, 2011 |
| 259886 | 306802 |
Building NI-HSDIO-linked 64-bit user applications requires an additional linker library directory and dependency.For building NI-HSDIO examples in 64-bit user mode applications that link to NI-HSDIO, you must add $(NIIVIPATH32)\Lib_x64 as an additional linker library directory and add niHSDIO.lib as an additional linker dependency. Workaround: Add $(NIIVIPATH32)\Lib_x64 as an additional linker library directory and add niHSDIO.lib as an additional linker dependency. |
Reported Version: NI-HSDIO: 1.7 Resolved Version: N/A Added: Jul 1, 2011 |
| 259669 | 407892 |
Passing an invalid value for Number of Records to niHSDIO_ReadMultiRecord and niHSDIO_FetchMultiRecord entry points produces an error message that says to use -1, which is not supportedWhen you use an invalid value for the Number of Records parameter when calling any of the niHSDIO_ReadMultiRecord or niHSDIO_FetchMultiRecord functions, the error message suggests that -1 (negative 1) can be used to obtain all available records. Workaround: Passing -1 to these functions is only supported when using LabVIEW, because the LabVIEW entry points automatically allocate memory for the arrays, whereas the array must be allocated outside of the function when using other programming languages.. |
Reported Version: NI-HSDIO: 1.9 Resolved Version: N/A Added: Jun 11, 2013 |
| 260199 | 409366 |
C Examples that use NI-TClk fail in Visual Studio 2012 because they expect /SAFESEH to be enabled by defaultWhen attempting to compile an NI-HSDIO C example that uses NI-TClk using Visual Studio 2012, you may receive an error similar to the following: "niTClk.lib(niTClk.dll) : error LNK2026: module unsafe for SAFESEH image." This error is cause by Visual Studio 2012 having /SAFESEH (Safe Exception Handling) enabled by default, which niTClk.dll is not compiled with. For more information, consult the Microsoft documentation here: http://msdn.microsoft.com/en-us/library/9a89h429.aspx
Workaround: To work around this issue, follow the steps described below. 1. Right-click on the Project and select Properties 2. Expand Configuration Properties -> Linker -> Advanced 3. Change "Image Has Safe Exception Handlers" to "No (/SAFESEH:NO)" 4. Click OK. - Try compiling again
|
Reported Version: NI-HSDIO: 2.0 Resolved Version: N/A Added: Jun 11, 2013 |
| 260309 | 694038 |
PXIe-6548 Module May Not Be Recognized in NI-Max after Windows RestartAfter performing a Windows restart on a system with a PXIe-6548, the module may no longer be recognized in NI-MAX. This will cause the module to error on device initialize for any test programs that use this module. Workaround: A complete Windows shutdown will always guarantee that the PXIe-6548 module will be properly recognized in NI-MAX. |
Reported Version: NI-HSDIO: 17.5 Resolved Version: N/A Added: Mar 6, 2019 |
| 259894 | 306807 |
Error -219001 may occur on NI PXIe-6544/6545/6547/6548 devices when scynchronizing acquisitions using NI-TClk.For the NI PXIe-6544/6545/6547/6548, internal error -219001 may occur intermittently when synchronizing multiple acquisitions using NI-TClk at rates below 5 MHz. Workaround: If this error occurs, consider oversampling by configuring your acquisition with a higher sample rate. For more information, contact NI Technical Support at ni.com/support. |
Reported Version: NI-HSDIO: 1.7 Resolved Version: N/A Added: Jul 1, 2011 |
Issues found in this section will not be listed in future known issues documents for this product.
There are currently no issues to list.
Explore Support Content and Product Documentation
Ask the NI Community
Request Support from an Engineer
A valid service agreement may be required, and support options vary by country