The DUT XML configuration file (.dut) defines the characteristics and signals associated with a DUT. A DUT XML configuration file can be created and edited within TestStand by navigating to Tools»Edit DUT XML. Use the DUT XML editor to customize the configuration by defining how this test should appear in the Web UI. For example, you can customize the display name that shows in the Web UI Test Definition selector menu, or the description that shows in the info tip in the Web UI; you can declare a connector with its endpoints and measurement types; and you can declare the communication channels with their measurement types that need to be mapped to test endpoints in the Web UI and/or that you need to logged to a file.

DUT XML File Tag Reference

  • <DutModel> —Top-level tag for .dut files.
    Table 9. <DutModel> Attributes
    Attribute NameData TypeRequired?Accepted and Default ValuesDescription
    NamestringYesUnique name of the DUT package. Once defined, this name should never be changed. If DisplayName is not defined, this name is shown in the Model drop-down listbox in the DUT Model section of the BTS Web UI Test Plan Editor.
    DisplayNamestringNoDisplay name for the DUT model. This name is shown in the Model drop-down listbox in the DUT Model section of the BTS Web UI Test Plan Editor.
    DescriptionstringYesHigh-level description of the DUT described in the DUT package. Once a DUT is added to a test plan, this description is shown as an info tip in the DUT Model section of the Test Plan Editor in the BTS Web UI when the corresponding test is selected in the Model drop-down listbox.
    BarCodeScanner.PluginstringNoComponent name of a DUT plugin that allows DUT serial numbers to be read using a barcode scanner. If included, appears to the right of the Serial Number control in the DUT Model section of the BTS Web UI Test Plan execution page.
    DutDebugging.PluginstringNoComponent name of a DUT plugin that allows live confirmation of a DUT connection to the BTS. If included, appears to the right of the Serial Number control in the DUT Model section of the BTS Web UI Test Plan Editor.
    DutHelper.PluginstringNoComponent name of a DUT plugin that gives specific instructions to an operator on how to connect and set up a DUT. These instructions can take the form of text or an image. If included, appears to the right of the Serial Number control in the DUT Model section of the BTS Web UI Test Plan Editor.
    SystemLink. ConfigurationPathstringNoName and location of a SystemLink configuration file. The file defines a select set of port endpoints to publish as SystemLink tags. The file path should be relative to the .dut file.
    IsDeprecatedbooleanNoFalseIndicates if the DUT package name should be included in the DUT selector menu when creating a new Test Plan.
  • <MeasurementEndpoints> —Tag that contains a list of all <MeasurementEndpoint> elements in a .dut file.
  • <MeasurementEndpoint> —Tag that contains a DUT measurement monitored in a test. DUT measurement endpoints serve as an alias for a connected channel path to a DUT measurement. Contains a Measurement Attribute element, which contains information on the signal's properties. Measurement Attribute elements are described in Measurement Attribute XML Conventions.
    Table 10. <MeasurementEndpoint> Attributes
    Attribute NameData TypeRequired?Accepted and Default ValuesDescription
    NamestringYesName of the DUT measurement. This name appears in one of the drop-down listboxes in the Endpoint list in the Endpoint Mappings section of the BTS Web UI Test Plan Editor.
    ChannelPathstringNoPath of the port-related channel, such as a VCOM custom device channel. For VCOM custom device channels, the path is relative to the VCOM custom device.
  • <DutConnectors> —Tag that contains a list of all <DutConnector> elements in a .dut file.
  • <DutConnector> —Tag that contains the signal mapping information for a .dut file and a .connectorinterface file.
    Table 11. <DutConnector> Attributes
    Attribute NameData TypeRequired?Accepted and Default ValuesDescription
    NamestringYesName of the DutConnector tag.
    ConnectorInterfacestringYesName of the connector package the <DutConnector> tag maps measurements to.
  • <SignalMapping> —Tag that maps a described signal in a .connectorinterface file to a measurement endpoint from a DUT. Contained within a <DutConnector> tag.
    Table 12. <SignalMapping> Attributes
    Attribute NameData TypeRequired?Accepted and Default ValuesDescription
    ConnectorSignalstringYesName of the connector package signal that a DUT measurement is being mapped to.
    MeasurementEndpointstringYesName of the DUT measurement being mapped.
  • <Ports> —Tag that contains a list of all <Port> elements in a .dut file.
  • <Port> —Tag that describes an industrial communication port used to monitor a measurement endpoint.
    Table 22. <Port> Attributes
    Attribute NameData TypeRequired?Accepted and Default ValuesDescription
    NamestringYesName of the port.
    PortNumberunsigned intYesNumber of the port.
    TypeenumYes
    • CAN
    • LIN
    Type of industrial communication protocol used on the port.
  • <Endpoint> —Tag that defines a measurement endpoint monitored on an industrial communication port. Contained within a <Port> tag.
    Table 14. <Endpoint> Attributes
    Attribute NameData TypeRequired?Accepted and Default ValuesDescription
    NamestringYesName of the measurement endpoint.
  • Sample .dut File

    The following example illustrates a sample structure for a .dut XML file.

    <?xml version="1.0" encoding="utf-8" ?>
    <DutModel Name ="6251.12" Description="Generic Battery" 
     SystemLink.ConfigurationPath = 
     "SystemLinkConfiguration.xml">
        <MeasurementEndpoints>
            <MeasurementEndpoint Name="Cell Voltage">
                <VoltageInputAttributes Unit="Voltage" 
    		MinValue = "0" MaxValue = "5" 
    		InputConfiguration="Differential"/>
            </MeasurementEndpoint>
            <MeasurementEndpoint Name="Cell Temperature">
                <TemperatureInputAttributes Unit="Celsius"
    		MinValue="0" MaxValue = "80"/>
            </MeasurementEndpoint>
    	 <MeasurementEndpoint Name="BMS Bat Pack Voltage"  
    	  ChannelPath="HS1_Rx/VICM/MSG_2005/HVBI_BatPackPrcdVltg">
                <VoltageInputAttributes Unit="Voltage" 
    		MinValue="0" MaxValue="450" />
            </MeasurementEndpoint>
            <MeasurementEndpoint Name="BMS Bat Pack Current" 
    		ChannelPath="HS1_Rx/VICM/MSG_2005/
    		HiVltgBatPrcdCurr">
                <CurrentInputAttributes Unit="Amperage" 
    	      MinValue="0" MaxValue="1000" />
            </MeasurementEndpoint>
        </MeasurementEndpoints>
        <DutConnectors>
            <DutConnector ConnectorInterface="ConnectorA" >
                <SignalMapping ConnectorSignal="VC"
    		MeasurementEndpoint="Cell Voltage" />
                <SignalMapping ConnectorSignal="TC" 
                 MeasurementEndpoint="Cell Temperature" />
            </DutConnector>
        </DutConnectors>
        <Ports>
            <Port Name="CAN_1" PortNumber="1" Type="CAN">
               <Endpoint Name="Battery Pack Voltage" />
               <Endpoint Name="Battery Pack Current" />
            </Port>
        </Ports>
    </DutModel>