NI-Digital Pattern Editor 17.1 Bug Fixes


The following items are the IDs and titles of a subset of issues fixed in the NI-Digital Pattern Editor 17.1. If you have a CAR ID, you can search this list to validate that the issue has been fixed.

1. Bug Fixes

The following items are Bug Fixes in NI-Digital Pattern Editor 17.1.

ID Legacy ID Fixed Issue Issue Details
Capturing a waveform with zero samples or an incomplete sample causes the Digital Pattern Editor to hang When a waveform captures zero samples (no capture opcode executes between capture_start and capture_stop opcodes) or a serial waveform captures an incomplete sample in which the number of bits captured does not make up a whole sample (the sample width is greater than the number of bits captured), the Digital Pattern Editor hangs when you burst the pattern.
Settings in the Instrument Settings pane have no effect if you are using a newly created project When you create a new project, the Digital Pattern Editor might get into a state in which changing settings in the Instrument Settings pane does not take effect. This issue persists until you close and reopen the project or restart the Digital Pattern Editor. This is not an issue with the project files themselves. It is an issue caused by the creation of a new project.
Using the Delete key in Time Set Name fields crashes the Digital Pattern Editor Clearing the Time Set Name fields by using the Delete key causes the editor to crash.
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.

Glossary of Terms


  • Bug ID - When an issue is reported to NI, you may be given this ID or find it on  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).