|Download Help (Windows Only)|
The following list describes the new features in the ATML Toolkit 2010 and other changes since the ATML Toolkit 1.0. This list only summarizes each new feature. Refer to the documentation listed for a particular feature for more information about that feature.
The ATML Test Description (TD) translator now supports translating limits associated with steps translated from <TestGroupCall> elements and localizing error and log messages.
In the case in which a TD instance document contains an <Action> element with a <Behavior> child element that contains a <TestGroupCall> child element, the translator in the ATML Toolkit 2010 uses the <TestLimits> element to determine the appropriate type of step to generate in the translated sequence file. Depending on the content of the <TestLimits> element, the translator generates a Pass/Fail Test, Numeric Limit Test, Multiple Numeric Limit Test, or String Value Test step. The translator in the ATML Toolkit 1.0 always generated a Pass/Fail Test step in this case.
Refer to the Determining Test Steps to Create for <Limit> Elements topic for more information about how the translator determines step types.
The ATML Toolkit 2010 adds support for localizing user interface strings. The following toolkit features contain strings you might want to localize:
The ATML Toolkit 2010 includes an ATMLTDString.ini string resource file, located in the <TestStand Public>\Components\Language\English directory. You can modify the strings in the resource file to modify the error or log messages. To support error and log messages for multiple languages, copy the resource file and place it in the required language directory in the <TestStand Public>\Components\Language directory.
The ATML Toolkit 2010 adds support for updating existing LabVIEW or LabWindows/CVI code modules the translator created for a previously translated sequence file.
The translator also updates block diagram labels or function comments that correspond to the <LocalSignal>, <TestLimit>, <Parameter>, <SessionDatum>, and <TestResult> child elements of the parent <Action> element.
In addition, the ATML Toolkit 2010 adds support for incrementally updating TestStand steps, attributes, and variables created from the child elements of a <TestGroup> element of the TestGroupParallel type.
The translator cannot translate all elements in a source TD instance document to TestStand constructs, such as steps, sequences, or code modules. The translator stores these elements in TestStand variables, attributes, or comments, but the generated sequence file does not use the variables, attributes, or comments.
The ATML Toolkit 2010 translation log file lists the elements the translator translated but cannot implement and describes how you must implement the required functionality to complete the test program. The log file uses subsections for the sequences and steps that contain the information you must implement. The translator generates the log file in the same directory that it generates the translated sequence file.
The General Settings tab of the ATML Test Description Translator Configuration dialog box now includes a Delete Previously Generated Sequence File and Code Module Constructs option, which is enabled by default.
When you enable this option, the translator deletes TestStand steps, sequences, and local variables and block diagram labels in LabVIEW code modules or function comments in LabWindows/CVI code modules created during the previous translation. The translator deletes these items when incrementally updating a sequence file if you have deleted the corresponding elements from the source TD instance document.
When you disable this option, the translator retains TestStand steps, sequences, and local variables and block diagram labels in LabVIEW code modules or function comments in LabWindows/CVI code modules when incrementally updating a sequence file, even if you have deleted the corresponding elements from the source TD instance document. The translator deletes in the retained TestStand constructs the attributes previously created for the attributes of translated elements in the source TD instance document. For comments in retained code modules, the translator deletes from the comments the <ATMLTranslatorComment> and </ATMLTranslatorComment> tags previously created for some elements in the source TD instance document.
The ATML Toolkit 2010 includes a new ATML Test Results report style sheet, TR_horizontal.xsl, located in the <TestStand>\Components\Models\TestStandModels\ATML\StyleSheets directory. The style sheet displays an ATML Test Results report in a concise tabular format with expand and collapse sections.
Select Configure»Report Options to launch the Report Options dialog box. Click the Contents tab, select ATML Report Document from the Report Format ring control, and select TR_horizontal.xsl from the Stylesheet ring control to select the new style sheet when you generate an ATML Test Results report.
The ATML Toolkit 2010 changes the prefixes of the types contained in the ATMLTDTypes.ini and ATMLTD_IEEE1641_Types.ini type palette files and also renames the Attributes subproperty of the types as ATMLAttributes. As a result of these naming changes, the ATML Toolkit 2010 does not correctly incrementally update sequence files you originally translated using the ATML Toolkit 1.0. Refer to ATML Toolkit 2010 Compatibility and Known Issues for more information about these naming changes.
You can use the Sequence File Updater application to convert sequence files you originally translated using the ATML Toolkit 1.0 to a sequence file you can use for an incremental update using the ATML Toolkit 2010. Complete the following steps to install and launch the Sequence File Updater application.