ASAM XIL Port Configuration Tag Reference

Use specific XML elements and complex elements in the port configuration XML file to configure one or more VeriStand ASAM XIL testbench ports.

The following table displays the XML elements you can use in a VeriStand ASAM XIL port configuration XML file.

Tool Required? Element Type Min/Max Occurrences Description
<NIVSPortConfig> Yes Top-level 1/1 The type of configuration file.
<Version> Yes VersionType 1/1 The version of the port configuration file.
<Project> Yes NonEmptyStringType 1/1 The path to the VeriStand project you want to connect to through the ASAM XIL Interface.
<ShowWorkspace> No xs:boolean 0/1 Specifies whether to display the workspace when a project is deployed.
<ShowVeriStandScreen> No xs:boolean 0/1 Specifies whether to display the VeriStand screen when a project is deployed.
<UndeployVeriStandProjectOnDisconnect> No xs:boolean 0/1 Specifies whether to undeploy the running VeriStand project when the port is disconnected.
<EESPortConfig> No EESPortConfigType 0/1 A container for the EESPort configuration options.
<HWTriggerChannelList> No HWTriggerChannelListType 0/1 The list of channels you want to use to fire EESPort hardware triggers.
<HWTriggerChannel> No HWTriggerChannelType 0/unbounded The path to the channel you want use as a hardware trigger. You can only set one hardware trigger channel per target.
Note The hardware trigger only occurs if the channel value changes from 0 to any other value.
<SWTriggerChannelList> No SWTriggerChannelListType 0/1 A list of channels you want to use to fire EESPort software triggers.
<SWTriggerChannel> No SWTriggerChannelType 0/unbounded A path to the software channel you want to trigger. You can only set one software trigger channel per target.
Note The software trigger only occurs if the channel value changes from 0 to any other value. Set the AutoReset attribute of this element to true to automatically set the channel back to zero after the trigger fires. If AutoReset is set to false, you must manually set the channel value back to zero.
<MAPortConfig> No MAPortConfigType 0/1 The container for the MAPort configuration options.
<LogFilePath> No NonEmptyStringType 0/1 Specifies the path of the temporary TDMS log file that is created during capturing.
<TaskList> No TaskListType 0/1 A list of user-defined tasks.
<Task> No TaskType 0/unbounded Specifies the task name and frequency. Use the format <TaskN>, where N is the frequency of the task in Hz.
<LogPostProcessPeriodMS> No xs:int 0/1 The length, in milliseconds, of the post-processing period.
Note
  • If you call Fetch () before post-processing completes, Fetch ()returns an empty result.
  • If post-processing occurs periodically, a new TDMS file is created for each period, which adds overhead to the operation
<ChannelDataTypeOverrideList> No ChannelDataTypeOverrideListType 0/1 A list of channels that you want to override the default data type. In VeriStand, channels are double-precision, floating-point numerics by default.
<ChannelDataTypeOverride> No ChannelDataTypeOverrideType 0/unbounded A container for the channel name and data type. Channel names inside this container must be unique.
<ChannelName> Yes* NonEmptyStringType 0/1 The name of the channel for which you want to change the data type.
<DataType> Yes* DataTypeType 0/1 The data type you want the channel value to change to.
*Required child elements of optional parent elements are only required if you use the parent element.

Types

  • VersionType—Specifies version information.
    Attribute Required? Attribute Type
    Major Yes xs:unsignedInt
    Minor Yes xs:unsignedInt
    Fix Yes xs:unsignedInt
    Build Yes xs:unsignedInt
  • NonEmptyString—Restricts the element to allow only non-empty strings.
    Restrictions Minimum Length
    xs:string 1
  • DataTypeType—Restricts the element to only allow int, uint, bool and float data types. Only scalars, vectors, and matrices are allowed from the data types.