Archived: NI-HSDIO 1.8.1 Known Issues

NI does not actively maintain this document.

This content provides support for older products and technology, so you may notice outdated links or obsolete information about operating systems or other relevant products.

Aperçu



This document contains the NI-HSDIO known issues that were discovered before the release of NI-HSDIO 1.8.1. 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.

Each issue appears as a row in the table and includes the following fields:

  • Issue ID - The number at the top of each of the cells in the first column. When you report an issue to NI, you may be given this ID. You can also find IDs posted by NI on the discussion forums or in Knowledge Base articles.  "N/A" indicates that there is no ID assigned to the issue.
  • Issue Title (in italics) - Describes the issue in one sentence or less.
  • Problem Description - A few sentences which describe the problem in further detail. The brief description given does not necessarily describe the problem in full detail, and it is expected that you may want more information on an issue. If you would like more information on an issue, contact NI and reference the ID number given in the document.
  • Workaround - Possible ways to work around the problem. The workarounds that appear in the document are not always tested by NI and are not guaranteed to resolve the issue. If a workaround refers you to the NI KnowledgeBase, visit www.ni.com/kb/ and enter the KnowledgeBase number in the search field to locate the specific document.
  • Reported Version - The earliest version of NI-RFSG in which the issue was reported. If you discover the issue appears in an earlier version of NI-RFSG than is reported in this field, report the discrepancy to NI to have the field updated.
  • 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).

Known Issues by Severity

 

ID Known Issue
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.
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: Complete all measurements before or after self-calibrating your NI 6555/6556.

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

Cannot perform self-calibration in MAX on the NI 6555/6556 devices.
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
306810

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

When using 64-bit user mode, NI-HSDIO does not support NI-HWS.

Workaround: Contact NI Technical Support at ni.com/support.

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

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

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

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

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

Contacting NI

Contact NI regarding this document or issues in the document. If you contact NI in regards to a specific issue, reference the ID number given in the document. The ID number contains the current issue ID number as well as the legacy ID number (use the current ID number when contacting NI). You can contact us through any of the normal support channels including phone, email, or the discussion forums. Visit the NI Website to contact us. Also contact us if you find a workaround for an issue that is not listed in the document.

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).