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:
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.
The following items are known issues in the TestStand ATML Toolkit 2010 sorted by Category.
| ID | Known Issue | |||||
|---|---|---|---|---|---|---|
| Installation | ||||||
| 305527 Return | 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.
| |||||
| Test Description Translator | ||||||
| 277922 Return | 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. Workaround: N/A
| |||||
| 303276 Return | 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. Workaround: N/A
| |||||
| 304392 Return | 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.
| |||||
Document last updated on 7/13/2011