NI-HSDIO Known Issues

Overview

This document contains the NI-HSDIO known issues that were discovered before and since the latest release of NI-HSDIO. Not every issue known to NI appears on this list; it is intended to show the most severe and common issues that can be encountered.

Known Issues by Date

The following items are known issues in NI-HSDIO sorted by Date.

306802 Building NI-HSDIO-linked 64-bit user applications requires an additional linker library directory and dependency.
306803 When using a MXI connection, some NI PXI Express devices may not be recognized after a shutdown.
306807 Error -219001 may occur on NI PXIe-6544/6545/6547/6548 devices when scynchronizing acquisitions using NI-TClk.
306808 The NI PXIe-6544/6545/6547/6548 may not utilize the full bandwidth of the PCI Express bus.
306810 NI-HSDIO generates an error with an unknown status code when allocating streaming waveforms that are not 128-byte aligned.
306813 MAX might not display NI-HSDIO devices when deploying to a LabVIEW Real-Time target.
306816 Some Windows power management modes terminate in-progress NI-HSDIO operations.
306817 When installing NI-HSDIO in silent mode from the command line, your computer automatically trusts NI software
399545 Cannot perform self-calibration in MAX on NI 6555/6556.
307658 In NI 6555/6556 devices, if both acquisition and generation sessions are open when you conduct self-calibration in one session, the data from the other session is invalid.
183465 Using script triggers with Hardware Compare results in uncertain HW compare error locations.
346946 While using Scripts, reloading a different waveform with the same name as an existing waveform may generate an incorrect waveform.
393626 When using scripting on the NI PXIe-6548, if you nest a repeat forever loop immediately inside another loop, the device may throw a Device Data Underflow error.
407117 Multiple CVI examples will not compile on Windows XP because of file path length.
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 supported.
409366 C Examples that use NI-TClk fail in Visual Studio 2012 because they expect /SAFESEH to be enabled by default.
694038 PXIe-6548 Module May Not Be Recognized in NI-Max after Windows Restart.
676958 Hardware-Timed DIO Tasks Fail with the PXIe-653x Modules and a PXIe-8840 Dual-Core Controller with an RT OS.
738295 LabVIEW crashes during execution of 'niHSDIO Self Test.vi' with NI-HSDIO 19.0.
743720 NI-HSDIO cannot be installed on Japanese OS with NIPM 19.5.



ID Known Issue
306802

Return
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: 1.7    Resolved Version: N/A    Added: 07/01/2011
306803

Return
When using a MXI connection, some NI PXI Express devices may not be recognized after a shutdown.
When using a MXI connection, some NI PXI Express devices may not be recognized after a shutdown.

Workaround: When you turn off your computer, either restart or power cycle your chassis before powering up your computer again.

Reported Version: 1.7    Resolved Version: N/A    Added: 07/01/2011
306807

Return
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: 1.7    Resolved Version: N/A    Added: 07/01/2011
306808

Return
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: 1.7    Resolved Version: N/A    Added: 07/01/2011
306810

Return
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: 1.7    Resolved Version: N/A    Added: 07/01/2011
306813

Return
MAX might not display NI-HSDIO devices when deploying to a LabVIEW Real-Time target.
NI-HSDIO devices might not be visible in Measurement & Automation Explorer (MAX) when deploying to a LabVIEW Real-Time target.

Workaround: For more information, search ni.com/kb using the code 4RCAMBD4 or contact NI Technical Support at ni.com/support.

Reported Version: 1.6    Resolved Version: N/A    Added: 07/01/2011
306816

Return
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: 1.6    Resolved Version: N/A    Added: 07/01/2011
306817

Return
When installing NI-HSDIO in silent mode from the command line, your computer automatically trusts NI software
When you run setup.exe to install the software from the DVD, you are prompted to choose whether you want to always trust software from National Instruments. If you do not select this option, your installation may be interrupted by one or more Microsoft Windows security dialog boxes. However, if you run the installer in silent mode from the command line, you will not receive this prompt, and the installer will automatically install NI's Software Publisher Certificate to the your Windows Trusted Publisher Store.

Workaround: If you do not want to make this change to your Windows Trusted Publisher Store, do not choose this installation method. For more information, contact NI Technical Support at ni.com/support.

Reported Version: 1.6    Resolved Version: N/A    Added: 07/01/2011
399545

Return
Cannot perform self-calibration in MAX on NI 6555/6556.
If you try to self-calibrate an NI 6555/6556 device in MAX it returns error -200445. Self-calibration of NI 6555/6556 devices takes between 15 and 20 minutes, which is longer than the allotted time period for self-calibration in MAX.

Workaround: Self-calibrate your NI 6555/6556 device using the NI-HSDIO self-calibration VIs or functions instead.

Reported Version: 1.8    Resolved Version: N/A    Added: 07/01/2011
307658

Return
In NI 6555/6556 devices, if both acquisition and generation sessions are open when you conduct self-calibration in one session, the data from the other session is invalid.
Self-calibration of NI 6555/6556 devices uses both acquisition and generation sessions. Therefore, if you have both sessions open when you conduct self-calibration in one session, the data from the other session is invalid

Workaround: Workaround: Complete all measurements before or after self-calibrating your NI 6555/6556.

Reported Version: 1.8    Resolved Version: N/A    Added: 07/12/2011
183465

Return
Using script triggers with Hardware Compare results in uncertain HW compare error locations
Any 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: 1.5.4    Resolved Version: N/A    Added: 08/14/2012
346946

Return
While using Scripts, reloading a different waveform with the same name as an existing waveform may generate an incorrect waveform
To 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: 1.8.1    Resolved Version: N/A    Added: 08/14/2012
393626

Return
When using scripting on the PXIe-6548, if you nest a repeat forever loop immediately inside another loop, the device may throw a Device Data Underflow error.
For example, the following script will occasionally error: script script1 repeat until scripttrigger0 repeat forever generate wfm1 marker0(0) end repeat end repeat end script

Workaround: To work around this issue, program a waveform prior to the inner loop. If you insert "generate wfm1 marker0(0)" before "repeat forever", this will be functionally identical and will prevent the issue from occurring.

Reported Version: 1.9    Resolved Version: N/A    Added: 06/11/2013
407117

Return
Multiple CVI examples will not compile on Windows XP becuase of file path length
When using Windows XP, several NI-HSDIO CVI examples will fail to compile because the file path length is too long.

Workaround: There are several options you can take if you want to run any examples that exhibit this issue: - Manually copy the example folder to a shorter file path location. - Rename the folder to a shorter name.

Reported Version: 2.0    Resolved Version: N/A    Added: 06/11/2013
407892

Return
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 supported.
When 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: 1.9    Resolved Version: N/A    Added: 06/11/2013
409366

Return
C Examples that use NI-TClk fail in Visual Studio 2012 because they expect /SAFESEH to be enabled by default
When 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: 2.0    Resolved Version: N/A    Added: 06/11/2013
694038

Return
PXIe-6548 Module May Not Be Recognized in NI-Max after Windows Restart
After 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: 17.5    Resolved Version: N/A    Added: 03/5/2019
676958

Return
Hardware-Timed DIO Tasks Fail with the PXIe-653x Modules and a PXIe-8840 Dual-Core Controller with an RT OS
Both read and write hardware-timed DIO tasks will not work with the PXIe-653x modules if they are in a system where the controller is a dual-core PXIe-8840 with a real-time OS.

Workaround: Use a quad-core PXIe-8840 with a real-time OS. If you do not have a quad-core PXIe-8840 with a real-time OS, please contact your NI Sales representative and reference this known issue ID.

Reported Version: 17.5    Resolved Version: N/A    Added: 03/5/2019
738295

Return
LabVIEW crashes during execution of 'niHSDIO Self Test.vi' with NI-HSDIO 19.0.


Workaround: Run Self-Test through NI MAX

Reported Version: 19.0    Resolved Version: 19.5    Added: 11/5/2019
743720

Return
NI-HSDIO cannot be installed on Japanese OS with NIPM 19.5.
NI-HSDIO 19.0 fails to install via NI Package Manager 19.5 on a Japanese OS.

Workaround: Install NI-HSDIO 19.0 via NI Package Manager 19.0 or install NI-HSDIO 19.5.

Reported Version: 19.0    Resolved Version: 19.5    Added: 09/18/2019

 

Glossary of Terms

 

  • Bug ID - When an issue is reported to NI, you may be given this ID or find it on ni.com.  You may also find IDs posted by NI on the discussion forums or in KnowledgeBase articles.
  • Legacy ID – An older issue ID that refers to the same issue.  You may instead find this issue ID in older known issues documents.
  • Description - A few sentences which describe the problem. The brief description given does not necessarily describe the problem in full detail.
  • Workaround - Possible ways to work around the problem.
  • Reported Version - The earliest version in which the issue was reported.
  • Resolved Version - Version in which the issue was resolved or was no longer applicable. "N/A" indicates that the issue has not been resolved.
  • Date Added - The date the issue was added to the document (not the reported date).