NI-Digital Pattern Driver 16.0 Known Issues

Overview

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

681944 Certain programming sequences can result in internal bus contention that, over time, could damage the instrument
673746 HRAM may return an incomplete set of failures if HRAM is configured to use pretrigger samples and capture failures only
649771 HRAM may trigger on the wrong vector
648748 Calling the select function on any channel right after initialize sets all channels to the input value of the select function
640885 Calling PPMU Source or Burst Pattern with a channel list could check the selected mode of the incorrect channel
577343 Loading large patterns in a 32-bit process runs out of memory
588214 No LED activity during firmware update
608891 After updating firmware, the completion indicator disappears
610028 niDigital Export Signal does not export the start trigger
610031 Exporting the sync pulse errors out
610148 The Requirements section does not list the PXIe-6570 for NI-Digital examples in the NI Example Finder
672536 NI Example Finder does not filter for PXIe-6570 hardware

 

ID Known Issue
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: 16.0    Resolved Version: 16.0.2/17.0.2/18.0    Added: 6/13/2018
673746

Return
HRAM may return an incomplete set of failures if HRAM is configured to use pretrigger samples and capture failures only
If the HRAM settings within the Digital Pattern Editor are configured to have the Cycles to Capture to Failures Only and the Pretrigger Cycles is greater than 0, the failures captured may be different than the requested failures. All returned failures are actual failures, but some of the failures that were requested may not be returned.

Workaround: Setting the Cycles to Capture to All will guarantee the correct samples are captured..

Reported Version: 16.0    Resolved Version: 17.1    Added: 6/4/2018
649771

Return
HRAM may trigger on the wrong vector
If you receive a digital scope error stating that niDigital_FetchHRAM failed to return data for requested cycle or that not enough cycle results exist in HRAM, HRAM might be triggering on the wrong vector.

Workaround: If you use a repeat opcode three vectors after a label, four vectors after a call opcode, or between 160 and 180 vectors after a label, move the opcode down at least one vector or remove it.

Reported Version: 16.0    Resolved Version: 17.0    Added: 6/14/2017
648748

Return
Calling the select function on any channel right after initialize sets all channels to the input value of the select function
This situation causes the software state to be out of sync with the hardware state, and the PPMU source or burst pattern functions do not automatically put the channels in the correct state.

Workaround: You must use the select function to manually select the state of each channel before using the PPMU source or burst pattern functions.

Reported Version: 16.0    Resolved Version: 17.0    Added: 6/14/2017
640885

Return
Calling PPMU Source or Burst Pattern with a channel list could check the selected mode of the incorrect channel
The PPMU Source or Burst Pattern functions may not select the correct mode for the specified channels when you call these functions with a channel list.

Workaround: You can explicitly set the mode of each channel before you call the PPMU Source or Burst Pattern functions by using the Select function.

Reported Version: 16.0    Resolved Version: 17.0    Added: 4/12/2017
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
588214

Return
No LED activity during firmware update
During a firmware update, there is no LED activity to indicate that there is an operation in progress.

Workaround: The indicator ribbon in Measurement & Automation Explorer displays during an ongoing firmware update. The upgrade might take several minutes to complete.

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

Return
After updating firmware, the completion indicator disappears
After you select another instrument in Measurement & Automation Explorer, the indicator ribbon that shows a successful firmware update disappears and the notification to power cycle the chassis is no longer present.

Workaround: Turn off the chassis after all firmware updates are complete to finalize the updates.

Reported Version: 16.0    Resolved Version: 17.0    Added: 10/20/2016
610028

Return
niDigital Export Signal does not export the start trigger
The niDigital Export Signal VI and NIDigital.ExportSignal method do not allow exporting the start trigger.

Workaround: Use the Start Trigger Output Terminal property to export the start trigger.

Reported Version: 16.0    Resolved Version: 17.0    Added: 10/20/2016
610031

Return
Exporting the sync pulse errors out
When attempting to synchronize multiple instruments, exporting the sync pulse returns an error that states the attribute is read only.

Workaround: Use the TClk synchronization VIs to configure synchronization for multiple instruments.

Reported Version: 16.0    Resolved Version: 17.0    Added: 10/20/2016
610148

Return
The Requirements section does not list the PXIe-6570 for NI-Digital examples in the NI Example Finder
The PXIe-6570 is required for every NI-Digital example in the NI Example Finder.

Workaround: N/A

Reported Version: 16.0    Resolved Version: 17.0    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).