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 1.0 known issues
that were discovered before and since the release of
TestStand ATML Toolkit 1.0. 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 date.
Known Issues by Category
For those who wish to locate the newly reported issues, we have also published another version of the known issues table sorted by the category of the issue.
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. The ID number contains the current issue ID number as well as the legacy ID number (use the current ID number when contacting National Instruments). 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 ATML Toolkit 1.0 sorted by Date.
| ID | Known Issue | |||||
|---|---|---|---|---|---|---|
| 104809 Return | The ATML TD Translator does not process TestLimits elements of Test elements that describe a behavior of type TestGroupCall For TestLimits elements of Test elements that describe a behavior of type TestGroupCall, the translator will incorrectly create a LabVIEW Action step instead of a SequenceCall step. Workaround: N/A
| |||||
| 176403 Return | The ATML report generated for sequence files that contain arrays that begin with a non-zero index might not be consistent with the TestStand array type TestStand supports arrays that begin with any index value, but the ATML Test Results supports only zero-based indexing for arrays. If a sequence file contains arrays that begin with an index other than zero, the generated ATML report might not be consistent with the TestStand array type. Workaround: Do not use arrays beginning with a non-zero index in your sequence file when TestStand is configured to generate an ATML report.
| |||||
| 176403 Return | The ATML report generator does not generate a valid report if the sequence file uses negative array indexes TestStand supports negative array indexes, but the ATML Test Results schema does not. If a sequence file uses negative array indexes, the ATML report generator does not generate a valid report. Workaround: Do not use negative array indexes in a sequence file when you configure TestStand to generate an ATML report.
| |||||
| 183549 Return | The ATML Toolkit does not recognize the installation of LabVIEW 2009 (64-bit) Since ATML Toolkit is a 32 bit application, it is run as wow64 process in 64 bit platform. Due to this, the registry keys of the 64 bit applications(64 bit LabVIEW) are redirected when ATML Toolkit(32 bit app) tries to access the 64 bit registry. Workaround: N/A
| |||||
| 186913 Return | The ATML Test Description Translator Configuration dialog box takes longer to load when the computer is connected to a network but not connected to the internet The ATML Test Description Translator Configuration dialog box DLL contains a Microsoft Authenticode signature that causes the dialog box to take longer to load when your computer is connected to a network but not connected to the internet. Refer to the Microsoft KnowledgeBase article 936707, located at http://support.microsoft.com/kb/936707, for more information about Authenticode signatures affecting application load times. Workaround: Disconnect your computer from the network or connect to the internet to avoid the delay.
| |||||
| 188737 Return | The ATML Toolkit 1.0 uninstaller does not remove the ATMLTD_IEEE1641_Types.ini type file from the <TestStand Public>\Components\TypePalettes directory If you enable the Use IEEE 1641 Data Types in TestStand option on the General Settings tab of the ATML Test Description Translator Configuration dialog box, the ATMLTD_IEEE1641_Types.ini file is added to the <TestStand Public>\Components\TypePalettes directory. Uninstalling the ATML Toolkit does not remove the ATMLTD_IEEE1641_Types.ini type file from the <TestStand Public>\Components\TypePalettes directory. Workaround: Manually remove the ATMLTD_IEEE1641_Types.ini type file from the <TestStand Public>\Components\TypePalettes directory after you have uninstalled the toolkit.
| |||||
| 198055 Return | The ATML TD translator incremental update skips any TestGroup type of type TestGroupParallel The ATML TD translator incremental update does not update TestStand sequences associated with a TestGroup of type TestGroupParallel. Workaround: N/A
| |||||
| 215986 Return | Including the ATML Test Results Generator in a TestStand Deployment will install to both TestStand 4.1.1 and TestStand 4.2 directories If you install the ATML Test Results Generator component of TestStand ATML Toolkit 1.0 for both TestStand 4.1.1 and TestStand 4.2, and then build a deployment, in either TestStand 4.1.1 or TestStand 4.2, that includes the ATML Test Results Generator, running the deployment installer on a separate machine will install the ATML Test Results Generator component to both the TestStand 4.1.1 directory and the TestStand 4.2 directory, even if one of those versions of TestStand does not exist on the machine. Workaround: N/A
| |||||
| 245573 Return | Reinstalling the ATML Toolkit creates duplicate Configure ATML TD Translator items in the Tools menu If you repair the existing ATML Toolkit 1.0 installation or uninstall and then reinstall the toolkit, the TestStand Tools menu includes duplicate entries for the Configure ATML TD Translator menu item, depending on the number of times you repaired or installed the toolkit. Workaround: Select Tools»Customize to launch the Customize Tools Menu dialog box, in which you can manually remove the duplicate menu items by selecting the duplicate items and clicking Remove.
| |||||
| 255867 Return | The ATML Toolkit is not compatible with TestStand 2010 TestStand 2010 introduces a restriction that prevents the creation of a sub-property called Attributes when that property also contains Attributes. The TestStand ATML Toolkit 1.0 TD Translator is likely to run into this restriction and throw an error during translation. Workaround: N/A
| |||||
| 98211 Return | The ATML TD translator hangs if the LabWindows/CVI environment is closed during translation Closing the LabWindows/CVI environment while the ATML TD translator is generating LabWindows/CVI code modules causes the translator to hang. Workaround: N/A
|
Document last updated on 11/30/2010