Archived: TestStand ATML Toolkit 2010 Known Issues
Updated Mar 17, 2020
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.
This document contains the TestStand ATML Toolkit 2010 known issues
that were discovered before and since the release of
TestStand ATML Toolkit 2010. Not every issue known to NI will appear on this
list; it is intended to only show the severe and more common issues
that can be encountered.
Each Issue appears as a row in the table and
includes these 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.
Issue Title: in italics - it 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 might want more information on an issue. If you would like
more information on an issue feel free to contact NI (contact
information below) 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, please visit www.ni.com/kb/ and enter that KB
number in the search field to locate the specific document.
Reported Version - the earliest version of TestStand ATML Toolkit the
issue was reported in. If you discover the issue appears in an earlier
version of TestStand ATML Toolkit than is reported in this field, you can report that to NI (contact information below) to have the field updated.
Resolved Version - version the issue was resolved or was no
longer applicable. If an issue has not been resolved "N/A" will be
Date Added - the date the issue was added to the document
(not necessarily the reported date)
The Known Issues Document is divided into two separate tables appearing in two separate Developer Zone documents. The following document displays the issues by issue category.
Known Issues by Date
For those who wish to locate the newly reported issues, we have also published another version of the known issues table sorted only by date the issue was added to the document.
Feel free to contact NI regarding this document or issues in the document. If you are contacting NI in regards to a specific issue, be sure to reference the ID number given in the document to the NI representative. 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 consider contacting us if you find a workaround for an issue that is not listed in the document so that we can add the workaround to the document.
When you install the ATML Toolkit 2010 silently, the ATMLTDTranslator.dll fails to register
When you install the ATML Toolkit 2010 silently, the ATMLTDTranslator.dll file located in the <TestStand Public>\Components\Translators directory fails to register.
Workaround: When the silent installation completes, use the command prompt to the run regsvr32 command to manually register the ATMLTDTranslator.dll file.
The translator might hang if you use the TestStand API to programmatically open a TD file
The translator might hang when you use the Engine.GetSequenceFileEx() or ApplicationMgr.OpenSequenceFile() methods to open a TD file if the TestStand Sequence Editor loses focus but then regains focus during translation.
The translator might incorrectly create a backup code module when incrementally updating a LabVIEW code module for a TD file that contains an array element
If you configure the translator to create LabVIEW code modules, translate a TD file that contains an array <TestResult> element, and then perform an incremental update on the previously translated sequence file, the translator incorrectly creates a backup of any code modules that contain array parameters even though the TD file has not changed.
The translator removes local variables during an incremental update if you modify the actionID attribute of an <ActionReference> child element of a <TestGroup> element of the TestGroupParallel type
The TD file contains an <Action> element with an ID attribute value of "action1." and also contains an <ActionReference> child element of a <TestGroup> element of the TestGroupParallel type with an actionID attribute value of "action1." When you translate the TD file to a sequence file, change the value of the ID attribute of the <Action> element to "action2," change the value of the actionID attribute of the <ActionReference> element to "action2," and then perform an incremental update, the translator incorrectly removes the local variables the translator had previously created and assigned to parameters of the step created within the TestGroupParallel sequence.
Workaround: When you modify the value of the ID attribute of the <Action> element and the value of the actionID attribute of the <ActionReference> element, you must also modify the value of the name attribute of the <Action> and <ActionReference> elements. Alternatively, you can manually add the required local variables to the TestGroupParallel sequence.