Normally TestCase (.mxc) files are created and edited using MxVDev commands. This information is provided for editing the XML code in TestCase files manually.
ValPF
The <ValPF> tag in an XML TestCase file is for pass/fail settings in a DataBlock. It is defined as below in the schema:
<xs:element minOccurs="0" maxOccurs="1" name="ValPF">
<xs:complexType>
<xs:all>
<xs:element minOccurs="0" maxOccurs="1" name="Pos" type="xs:string" />
<xs:element minOccurs="0" maxOccurs="1" name="Neg" type="xs:string" />
<xs:element minOccurs="0" maxOccurs="1" name="InVal" type="xs:string" />
<xs:element minOccurs="0" maxOccurs="1" name="OutVal" type="xs:string" />
<xs:element minOccurs="0" maxOccurs="1" name="ToleranceGenerator" type="mxv:CSharp" />
</xs:all>
<xs:attribute name="Fmt" type="mxv:Format" />
<xs:attribute default="1" name="CheckInVal" type="xs:boolean" use="optional" />
</xs:complexType>
</xs:element>
A DataBlock may have 0 or 1 <ValPF> tags.
If the attribute “Fmt” is present, it indicates that the DataBlock overrides the value tolerance in the Signal Properties. When “Fmt” is specified, <Pos> is the upper value tolerance; <Neg> is the lower value tolerance. If "Fmt" is not present, the DataBlock uses its inherited value tolerance. See Tolerances.
The <InVal> is the Signal's value at the start of the DataBlock. <OutVal> is the value at the end of the DataBlock.
The attribute “CheckInVal” is the flag indicating if the Check InVal option is enabled (true) or disabled (false) for the DataBlock.
The <ToleranceGenerator> tag indicates that the DataBlock uses Custom value tolerances (defined by C# code).
VendStr
Effective with release 3.38.1.36642, the VendStr tag has been disabled. This information is now stored in the .mxo file.
The <VendInfo> tag in an XML TestCase file is for a Signal’s display settings. See Display Settings. It is defined as the below in the schema:
<xs:element minOccurs="0" maxOccurs="unbounded" name="VendInfo">
<xs:complexType mixed="true">
<xs:sequence />
<xs:attribute name="ToolName" type="xs:string" use="required" />
<xs:attribute name="VendStr" type="xs:string" use="optional" />
</xs:complexType>
</xs:element>
The attribute “ToolName” is hard coded as "MxVDev".
The attribute “VendStr” is a comma-delimited list of the Signal’s display properties:
VendStr=”{display_min, display_max}, graphEditHeight, IsDiscrete, ShowGrid, ShowToleranceBand, ShowText, DisplayFormat, Visible, DisplayFormatInSignalDictionary, IsWaypoint, TextEncoding, GraphMaximizedHeight)
1.{display_min, display_max}: The lower and upper values of the Y-Axis scale. When display_min=-1 and display_max=-1, the signal’s minimum and maximum in the Signal Dictionary are used.
2.graphEditHeight: The Signal's display height in the TestCase (Job) window. If -1, the default height is used.
3.IsDiscrete: Used for numeric Signals. If True, the discrete algorithm is used for pass/fail judgment. Otherwise, the continuous algorithm is used.
4.ShowGrid: If True, the grid labels are displayed on the right side of the TestCase. If False, they are hidden.
5.ShowToleranceBand: If True, Tolerance Bands are displayed.
6.ShowText: For message Signals, if True the data in the tool tips bubble is displayed as ASCII text. If False, the data is displayed in hex format.
7.DisplayFormat: Options are: ValueInEngUnits, ValueInCountsDecimal, ValueInCountsHex, Hex, ASCII, BlackAndWhiteImage, and ColorImage
8.Visible:If True, the Signal is displayed in the TestCase. If False, the Signal is hidden.
9.DisplayFormatInSignalDictionary: The Display Format saved in the Signal Dictionary. Options are: ValueInEngUnits, ValueInCountsDecimal, ValueInCountsHex, Hex, ASCII, BlackAndWhiteImage, and ColorImage
10.IsWayPoint: This property is not implemented.
11.TextEncoding: For message Signals, defines the text encoding. See Signal Properties.
12.GraphMaximizedHeight: The Signal's display height when the TestCase (Job) window is maximized. If -1, the default height is used.
The VendStr section was left as a CSV list instead of XML so that any other test tool vendor could use this field to store the display/presentation information that their test tool may capture and use.