ATML Toolkit 2010 Bug Fixes

TestStand ATML Toolkit 2017 Help

Edition Date: June 2018

Part Number: 374205B-01

»View Product Info
Download Help (Windows Only)

The following items are changes from the ATML Toolkit 1.0 to the ATML Toolkit 2010, unless otherwise specified.

Toggle Expansion Use this Toggle Expansion button to expand or collapse the following sections. You must enable the Allow Blocked Content option in Microsoft Internet Explorer to collapse each section. You must expand each section you want to print or search.

 General

ID Fixed Issue Issue Details
215986 Including the ATML Test Results report generator in a TestStand deployment installs the report generator to both TestStand 4.1.1 and TestStand 4.2 directories If you install the ATML Test Results report generator component of the TestStand ATML Toolkit 1.0 for both TestStand 4.1.1 and TestStand 4.2, build a deployment, and run the deployment installer on a different computer, the installer installs the ATML Test Results report generator component in both the TestStand 4.1.1 and TestStand 4.2 directories, even if one of those versions of TestStand does not exist on the computer.
255867 The ATML Toolkit is not compatible with TestStand 2010 TestStand 2010 introduces a restriction that prevents the translator from creating a subproperty named Attributes when the property also contains attributes. If the translator in the ATML Toolkit 1.0 encounters this restriction, the translator returns an error during translation.

 Installation

ID Fixed Issue Issue Details
188737 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 translator adds the ATMLTD_IEEE1641_Types.ini file 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.
201735 The toolkit installs the NI TestStand ATML Toolkit Help in the default <TestStand>\Doc\Help directory when TestStand is not installed in the default installation directory The toolkit installs the NI TestStand ATML Toolkit Help in the default <TestStand>\Doc\Help directory when TestStand is not installed in the default installation directory.
218266 The ATML Toolkit autorun.exe dialog box does not display correctly The ATML Toolkit autorun.exe dialog box might not display correctly if you make a different window active after you launch the autorun.exe but before the autorun.exe dialog box displays.
245573 Reinstalling the ATML Toolkit creates duplicate Configure ATML TD Translator menu items in the Tools menu If you repair the existing ATML Toolkit installation or uninstall and then reinstall the toolkit, the TestStand Tools menu includes a duplicate entry for the Configure ATML TD Translator menu item for each time you repaired or installed the toolkit.

 Test Description Translator

ID Fixed Issue Issue Details
183549 The translator does not recognize the installation of LabVIEW 2009 (64-bit) The translator runs as a Windows 32-bit On Windows 64-bit (WoW64) process on 64-bit operating systems, which causes registry queries from the translator to be redirected to the Wow6432Node registry node and prevents the translator from recognizing the installation of 64-bit versions of LabVIEW in the 64-bit registry.
186711 Limit values for a custom step type that is similar to Numeric Limit Test, Multiple Numeric Limit Test, or String Value Test step types do not update during an incremental update If the translator uses the customType attribute of an <Action> element to specify a custom step type and the custom step type definition is similar to the definition of the Numeric Limit Test, Multiple Numeric Limit Test, or String Value Test step types, the translator does not update the limit values of the step during an incremental update.
186913 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 the computer is connected to a network but not connected to the Internet. Refer to the Microsoft KnowledgeBase article 936707, located at support.microsoft.com/kb/936707, for more information about how Authenticode signatures affect application load times.
198055 Incremental update skips any <TestGroup> element of the TestGroupParallel type The translator does not incrementally update a TestStand sequence the translator previously created for a <TestGroup> element of the TestGroupParallel type.
201786 The translator does not enable additional results for parameters of Sequence Call steps the translator creates for <Action> elements The translator does not enable additional results for parameters of Sequence Call steps the translator creates for <Action> elements.
208443 The translator does not properly incrementally update <TestGroup> elements If you remove a <TestGroup> element from a previously translated TD instance document, the translator does not properly remove the sequence the translator previously created for the <TestGroup> element during an incremental update. If you change the name of a <TestGroup> element in a previously translated TD instance document, translator does not properly update the name of the sequence the translator previously created for the <TestGroup> element during an incremental update. If two Sequence Call steps call into the same sequence, and during an incremental update the translator changes one of the Sequence Call steps to no longer call into the sequence, the translator incorrectly deletes the sequence from the sequence file even though a Sequence Call step that calls into the sequence still exists.
209833 The translator does not use the <NominalValue> child elements of <TestResult> elements to specify the default values for VI indicators If an <Action> element contains <TestResult> elements, the translator uses the <TestResult> elements to store the output parameters of the <Action> element. If the LabVIEW code module the translator creates for such an <Action> element does not actually wire data to one of these output parameters, the indicator should default to the value that the <NominalValue> child element of the respective <TestResult> element specifies. When generating LabVIEW VIs, the translator does not specify the default values of indicators to match the values that the <NominalValue> elements of the respective <TestResult> elements specify.
219534 The translator does not properly recognize year-based versions of LabVIEW and LabWindows/CVI The translator incorrectly evaluates year-based versions of LabVIEW and LabWindows/CVI as versions earlier than LabVIEW 8.2.1 and LabWindows/CVI 8.1.1.
234677 The translator incorrectly populates parameter values for a Sequence Call step that calls a sequence created for a <Step> element that exists under a <TestGroup> element of the TestGroupParallel type The translator incorrectly populates parameter values for a Sequence Call step that calls a sequence created for a <Step> element that exists under a <TestGroup> element of the TestGroupParallel type and references an <Action> element that contains a <Behavior>/<TestGroupCall> child element.
234678 The translator hangs when you execute it in a LabVIEW-built user interface The translator hangs when you execute it in a TestStand User Interface built with LabVIEW.
243363 The translator does not update the data source for Multiple Numeric Limit Test steps when the number of parameters exceeds the number of limits The translator does not update the data source for Multiple Numeric Limit Test steps when the number of parameters exceeds the number of limits.
286139 The translator incorrectly skips some custom code generator callbacks during an incremental update When performing an incremental update, the translator skips the TranslateTestGroup custom code generator callback for <TestGroup> elements and the PreTranslateStep and PostTranslateStep custom code generator callbacks for <Step> and <ActionReference> elements.
289410 The translator incorrectly specifies the Load Option and Step Failure Causes Sequence Failure run options for a step translated from an <ActionReference> element The translator incorrectly specifies the Load Option and Step Failure Causes Sequence Failure run options for a step the translator creates for an <ActionReference> child element of a <TestGroup> element of the TestGroupParallel, TestGroupDiagnosticModel, TestGroupSerial, or TestGroupUnspecifiedOrder type. The translator incorrectly specifies Load dynamically for the Load Option run option and True for the Step Failure Causes Sequence Failure run option when the translator should specify Preload when execution begins and False, respectively.
294302 The translator returns the error 'Item is locked, protected, or in use and cannot be deleted.' when you use the example custom code generator VIs The translator returns the error 'Item is locked, protected, or in use and cannot be deleted.' when you configure the translator to use the LabVIEW custom code generator VIs, located in the <TestStand Public>\Components\Translators\ATMLTDTranslator\Examples\Code Generator\LabVIEW directory.
297288 The translator does not properly call the LabVIEWParameter.UpdateClusterMapping method for container parameters of LabVIEW steps created for <ActionReference> child elements of <TestGroup> elements of the TestGroupParallel type The translator does not properly call the LabVIEWParameter.UpdateClusterMapping method for container parameters of LabVIEW steps created for <ActionReference> child elements of <TestGroup> elements of the TestGroupParallel type.
98211 The translator hangs if you close the LabWindows/CVI environment during translation Closing the LabWindows/CVI environment while the translator is generating LabWindows/CVI code modules causes the translator to hang.

 Test Results Generator

ID Fixed Issue Issue Details
165526 The ATML Test Results report generator does not correctly process the Default Numeric Format setting The ATML Test Results report generator does not correctly process the setting you specify in the Default Numeric Format control on the Contents tab of the Report Options dialog box. When you select ATML Report Document from the Report Format ring control on the Contents tab of the Report Options dialog box, the Default Numeric Format control and Edit Format button are disabled.
209830 The ATML Test Results report generator does not process and include descriptions for Sequence Call steps in the ATML report The ATML Test Results report generator does not process and include descriptions for Sequence Call steps in the ATML report.
220888 The ATML Test Results report generator does not process and include the results of step post actions in the ATML report The ATML Test Results report generator does not process and include the results of step post actions in the ATML report.
221937 The ATML Test Results report generator omits Sequence Call step names from the ATML report The ATML Test Results report generator omits Sequence Call step names from the ATML report and instead uses the generic name TestGroup to record Sequence Call steps.
228564 The ATML Test Results report generator does not include <Event>, <Data>, or <Description> elements under <TestGroup> elements in the ATML report The ATML Test Results report generator does not include <Event>, <Data>, or <Description> elements under <TestGroup> elements in the ATML report.
231930 The ATML Test Results report generator does not include additional results when you enable the Is Limit option but do not enable the Is Measurement option If you configure an additional result for a step and enable the Include in Report option, the generated ATML Test Results report displays the additional result. However, if you also enable the Is Limit option but do not enable the Is Measurement option, the report does not display the additional result. The report does correctly display the additional result if you enable the Include in Report and Is Measurement options but you do not enable the Is Limit option.

WAS THIS ARTICLE HELPFUL?

Not Helpful