NI-Digital Pattern Editor 17.1 Known Issues

Overview

This document contains the NI-Digital Pattern Editor 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

611267 Digital Pattern Editor might crash when opening a project immediately after closing it
611269 Digital Pattern Editor might crash when closing a project immediately after opening it
611275 Launching the Digital Pattern Editor from the TestStand Semiconductor Module does not always bring the existing editor to the front
611808 Errors occur when using NI-Digital with the TestStand Semiconductor Module if the TestStand Semiconductor Module 2016 f1 Patch has not been installed
651023 Running the digital scope in demo mode without the pattern open in the Digital Pattern Editor returns an incorrect error
608222 Changing the active pin map file of a project while executing can lead to unexpected behavior
605969 Launching Digital Pattern Editor from a network drive crashes on startup or gives unexpected errors when evaluating formulas
651018 Editing a pin state immediately after inserting a new pin item sometimes edits the wrong cell
644093 Digital Pattern Editor sometimes does not preserve window layout

 

 

ID Known Issue
611267

Return
Digital Pattern Editor might crash when opening a project immediately after closing it
The Digital Pattern Editor might crash when you open a project immediately after you close it on slower computers or on virtual machines.

Workaround: Avoid using the Digital Pattern Editor on slower computers or on virtual machines.

Reported Version: 16.0    Resolved Version: N/A    Added: 10/24/2016
611269

Return
Digital Pattern Editor might crash when closing a project immediately after opening it
The Digital Pattern Editor might crash when you close a project immediately after you open it and before the project has finished opening.

Workaround: When you open large projects, wait for the project to finish loading before you close the project. Avoid rapidly opening and closing multiple projects.

Reported Version: 16.0    Resolved Version: 18.0    Added: 10/24/2016
611275

Return
Launching the Digital Pattern Editor from the TestStand Semiconductor Module does not always bring the existing editor to the front
When an instance of the Digital Pattern Editor is running, attempting to launch the Digital Pattern Editor from the TestStand Semiconductor Module does not always bring the existing editor to the front. If the Digital Pattern Editor was originally launched from the Start menu, the TestStand Semiconductor Module instead launches a new instance of the Digital Pattern Editor.

Workaround: Manually navigate to an existing instance of the Digital Pattern Editor instead of using the TestStand Semiconductor Module shortcut to bring the existing instance of the editor to the front.

Reported Version: 16.0    Resolved Version: N/A    Added: 10/24/2016
611808

Return
Errors occur when using NI-Digital with the TestStand Semiconductor Module if the TestStand Semiconductor Module 2016 f1 Patch has not been installed
If you use NI-Digital 16.0 with the TestStand Semiconductor Module, you must install the TestStand Semiconductor Module 2016 f1 patch to resolve multiple compatibility issues. Failing to install the f1 patch for the TestStand Semiconductor Module prevents you from using the NI-Digital .NET API and causes examples to not function properly.

Workaround: You can download the TestStand Semiconductor Module 2016 f1 patch from the following location:


TestStand Semiconductor Module 2016 f1 (32-bit)


TestStand Semiconductor Module 2016 f1 (64-bit)

Reported Version: 16.0    Resolved Version: N/A    Added: 10/24/2016
651023

Return
Running the digital scope in demo mode without the pattern open in the Digital Pattern Editor returns an incorrect error
When you run the digital scope in demo mode and the pattern is not open in the editor, the editor returns the error: "Could not find pattern file path in list of loaded patterns". The pattern must be open in a document in the editor before you can execute digital scope in demo mode.

Workaround: Open the pattern in the editor before running digital scope on it.

Reported Version: 16.0    Resolved Version: N/A    Added: 6/9/2017
608222

Return
Changing the active pin map file of a project while executing can lead to unexpected behavior
Changing, deleting, excluding, or making the current active pin map file inactive while the Digital Pattern Editor is executing can lead to unexpected behavior.

Workaround: Wait until the execution finishes or abort the current execution before changing, deleting, excluding, or making the current active pin map file inactive.

Reported Version: 16.0    Resolved Version: N/A    Added: 6/9/2017
605969

Return
Launching Digital Pattern Editor from a network drive crashes on startup or gives unexpected errors when evaluating formulas
The Digital Pattern Editor currently does not support being installed on or being run from a network drive.

Workaround: Install the Digital Pattern Editor to a local location and run the editor from that location.

Reported Version: 16.0    Resolved Version: N/A    Added: 6/9/2017
651018

Return
Editing a pin state immediately after inserting a new pin item sometimes edits the wrong cell
When you edit a pattern in the Digital Pattern Editor, editing the already selected pin state cell after inserting a new pin item column can sometimes cause the cell in the original column at that location to be edited instead of the cell in the current column.

Workaround: Change the selection at least once after inserting a new pin item column in the pattern.

Reported Version: 17.0    Resolved Version: N/A    Added: 6/15/2017
644093

Return
Digital Pattern Editor sometimes does not preserve window layout
The Digital Pattern Editor might not preserve the window layout when you close and reopen the application.

Workaround: Close the application, delete the .digiprojcache file associated with the project, reopen the project, reset the window layout, and save the project.

Reported Version: 17.0    Resolved Version: 18.0    Added: 6/15/2017

 

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