<Datum> Element

TestStand ATML Toolkit 2017 Help

Edition Date: June 2018

Part Number: 374205B-01

»View Product Info
Download Help (Windows Only)

The <Datum> element is a child element of the <Parameter>/<Value> element when the <Value> element represents a single data value for the parent <Parameter> element.

The ATML TD translator uses the value of the xsi:type attribute of the <Datum> element to determine if the <Parameter> element maps to a simple data type or a strict data type.

If the <Parameter> element maps to a simple data type, the translator inserts the parameter value in the parameter settings of the step the translator creates for the parent <Action> element. If the <Parameter> element maps to a strict data type, the translator creates a local variable for the <Parameter> element.

Completing the Partial Test Program Completing the Partial Test Program  The translator translates the <Confidence>, <ErrorLimits>, <Range>, and <Resolution> child elements of the <Datum> element as TestStand PropertyObject attributes of the parameter the translator creates for the parent <Parameter> element. You must implement the logic the <Confidence>, <ErrorLimits>, <Range>, and <Resolution> elements describe. Refer to the post-translation recommended actions section of the log file for more information about the elements you must implement.

Simple Data Types

The value of the xsi:type attribute can be a simple data type that the TD schema files define and that corresponds to a data type TestStand natively supports, such as Boolean, number, and string types. The translator creates in TestStand a variable of the same type. The number value for the xsi:type attribute includes binary, hexadecimal, octal, unsigned, and signed numbers. The translator handles these types by changing the representation property on the number in TestStand.

Strict Data Types

The value of the xsi:type attribute can also be a strict data type that the TD schema files define but that does not correspond to any data type TestStand natively supports. The ATML Toolkit installs the ATMLTDTypes.ini TestStand type palette file that defines the strict TD schema types as supported data types in TestStand.

The translator determines if the ATMLTDTypes.ini type palette file contains an appropriate data type that corresponds to the data type value the xsi:type attribute of the <Datum> element specifies. If a corresponding data type exists, the translator creates an instance of the data type in TestStand for the <Parameter> element and appends an NI_ATML prefix to the data type name.

The translator supports the following strict data type values of the xsi:type attribute that do not correspond to a TestStand data type defined in the ATMLTDTypes.ini type palette file:

  • ValueFromTestGroupParameter—Indicates that the parameter value the <Datum> element indicates originates from a <TestGroup>/<ParameterDescription> element. The translator looks for the <ParameterDescription> element with an ID attribute value that matches the value of the testGroupParameterID attribute of the <Datum> element and creates a local variable with the same type. A step pre-expression assigns the value of the <TestGroup> parameter to this local variable.
    Incremental Update Incremental Update  If you modify a <Datum> element with an xsi:type attribute value of ValueFromTestGroupParameter such that the <Datum> element references a different <TestGroup> parameter, the translator updates the pre-expression that stores the parameter value.
  • ValueFromActionResults—Indicates that the parameter value the <Datum> element indicates originates from an <Action>/<TestResults>/<TestResult> element, from an <Action>/<SessionData>/<SessionDatum> element, or from multiple <TestResult> or <SessionDatum> child elements of different <Action> elements. The translator processes this similarly to how it translates other elements and types without strict type definitions and creates a container local variable.
    Completing the Partial Test Program Completing the Partial Test Program  At run time, you can update the value of the parameter the translator creates for a <Datum> element of the ValueFromActionResults type with the correct value. Refer to the post-translation recommended actions section of the log file for more information about the <Datum> element of the ValueFromActionResults you must implement.
Completing the Partial Test Program Completing the Partial Test Program  If the xsi:type attribute of a <Datum> element is IncrementedValue, ValueFromIterator, ValueFromOperationMeasurement, or ValueFromOperationMessageIn, the translator creates an unstructured container local variable in the translated sequence. At run time, you can update the value of this variable with the correct value. Refer to the post-translation recommended actions section of the log file for more information about the <Parameter> elements you must implement.
Note Note  If the value of the xsi:type attribute of the <Datum> element is ValueFromActionParameter, the translator returns an error. Use the ValueFromActionParameter value only for a child element of the <Action>/<Behavior> element.

For values of the xsi:type attribute other than the supported simple or strict types, the translator creates in TestStand a container local variable and translates the <Parameter> element as an element with no strict type definition. The translator passes the container local variable as an object reference to a LabVIEW code module or as a CAObjHandle to a LabWindows/CVI code module.. You can use the TestStand PropertyObject API to perform operations on the container local variable.


See Also

<Action> Element

ATML TD Schema File Data Types

<Behavior> Element

Creating LabVIEW Code Modules for <Behavior> Elements

Creating LabWindows/CVI Code Modules for <Behavior> Elements

Logging Translation Information

<Parameters> Element

PropertyObject

PropertyObject Attributes

<TestGroup> Element

Translating ATML Types and Elements with No Strict Type Definitions

WAS THIS ARTICLE HELPFUL?

Not Helpful