NI-Digital Pattern Driver 17.1 Known Issues

Aperçu

This document contains the NI-Digital Pattern Driver known issues that were discovered before and since the release of NI-Digital Pattern Driver and Digital Pattern Editor 17.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 in 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-Digital Pattern Driver and Digital Pattern Editor in which the issue was reported. If you discover the issue appears in an earlier version of NI-Digital Pattern Driver and Digital Pattern Editor 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

 
899451 NI-Digital does not validate Bit Order for Capture Engine reconfiguration
715045 Frequency measurements are returned in ascending order of channels regardless of the channel list or pin list parameter
716093 Capture memory streaming may return incorrect samples when fetching more than a million samples per pattern burst
681944 Certain programming sequences can result in internal bus contention that, over time, could damage the instrument.
696854 There is an intermittent 10 ns delay seen between synchronized digital pattern instruments when using NI-TClk.
577343 Loading large patterns in a 32-bit process runs out of memory
672536 NI Example Finder does not filter for PXIe-6570 hardware

 

ID Known Issue
899451

Return
NI-Digital does not validate Bit Order for Capture Engine reconfiguration
If multiple capture waveforms are used within a single session, the NI-Digital driver should validate Sample Width, Pins, Waveform Type (Serial/Parallel), and Bit Order (MSB/LSB) to determine if the Capture Engine must be reconfigured. The Bit Order setting is not being validated. This means that if the two capture waveform configurations differ in Bit Order and the other 3 settings are consistent, then no reconfiguration will take place and the data for one of the waveforms will be returned with incorrect bit order..

Workaround: Configure all waveforms to be a consistent Bit Order and reorder in software as necessary. Alternatively, close and create a new NI-Digital session between waveforms with settings that differ only in Bit Order.

Reported Version: 17.0    Resolved Version: N/A    Added: 11/25/2019
715045

Return
Frequency measurements are returned in ascending order of channels regardless of the channel list or pin list parameter.
Frequency counter measurements will incorrectly return data in ascending channel order regardless of the channel list or the pin list. If the provided channel list or pin list input to the frequency measure function is not in ascending channel order, then the application will get incorrect results.

Workaround: Install NI-Digital Pattern Driver and Digital Pattern Editor patch 17.0.4, 17.1.2, or 18.0.1.

Reported Version: 17.0    Resolved Version: 17.0.4/17.1.2/18.0.1    Added: 10/24/2018
716093

Return
Capture memory streaming may return incorrect samples when fetching more than a million samples per pattern burst.
If less than one million capture samples are fetched in a single pattern burst, then the application is unaffected. Otherwise, incorrect samples may be returned.

Workaround: Install NI-Digital Pattern Driver and Digital Pattern Editor patch 17.0.4, 17.1.2, or 18.0.1.

Reported Version: 17.0    Resolved Version: 17.0.4/17.1.2/18.0.1    Added: 10/24/2018
681944

Return
Certain programming sequences can result in internal bus contention that, over time, could damage the instrument.
Contention can occur after using source memory on the PXIe-6570 internal bus. Over time this can cause damage to the instrument.

Workaround: Install NI-Digital Patch 16.0.2 or 17.0.2 to resolve this issue. Additionally, any future version of NI-Digital post NI-Digital 17.5 will resolve this issue.

Reported Version: 17.1    Resolved Version: 16.0.2/17.0.2/18.0    Added: 6/13/2018
696854

Return
There is an intermittent 10 ns delay seen between synchronized digital pattern instruments when using NI-TClk.
When using NI-TClk with the Timing Absolute Delay Enabled property set to FALSE, there is an intermittent 10 ns delay seen between synchronized digital pattern instruments. The Timing Absolute Delay Enabled property is set to FALSE by default.

Workaround: If the digital pattern instruments are not being used within an STS, then the Timing Absolute Delay Enabled property can be set to TRUE in order to resolve the issue. If the digital pattern instruments are being used within an STS, then the Timing Absolute Delay Enabled property should be left as FALSE because timing absolute delay conflicts with the adjustment performed during STS timing calibration. To resolve this issue for digital pattern instruments being used inside an STS, the version of NI-Digital must either be downgraded to NI-Digital 17.0.2 or upgraded to NI-Digital 18.0 or later.

Reported Version: 17.1    Resolved Version: 18.0    Added: 6/13/2018
577343

Return
Loading large patterns in a 32-bit process runs out of memory
As a result of limited system memory in a 32-bit process, loading a large pattern in a 32-bit process might fail.

Workaround: Split large patterns loaded in a 32-bit process into patterns that are small enough to fit into the available system memory.

Reported Version: 16.0    Resolved Version: N/A    Added: 10/20/2016
672536

Return
NI Example Finder does not filter for PXIe-6570 hardware
Using hardware filtering in the NI Example Finder does not return any examples that support the PXIe-6570.

Workaround: To find PXIe-6570 examples, use the NI Example Finder search feature with "6570" as the keyword or browse the task structure under Hardware Input and Output»Modular Instruments»NI-Digital Pattern Driver.

Reported Version: 16.0    Resolved Version: N/A    Added: 10/20/2016

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