In constructing the Test Harness, we define Signals with various properties. Manually making connections between systems is time consuming. Making connections automatically based on Signal Name can save a lot of time. The Signal properties (in MxVDev) and port properties (in MxTransIt) help make the connections in a consistent manner.
The properties include Signal Classification, Units, Initial Value, and for numeric signals: type (Continuous or Discrete), Min, and Max. These properties serve many purposes in the MxSuite Test Environment:
•When the MxV Input Reset System Signal is asserted, all stimulus signals are reset to their Initial Values.
•The Min and Max are used to set the default Y-axis (value) scale in TestCases.
•In TestCases, when the Min or Max is exceeded for a response signal, it causes a test failure. (This is optional, see Project Settings.)
•A run-time warning is generated the first time a transition on a port is outside the Min/Max range.
•Avoiding inconsistent connections, for example:
oA message port to an integer port
oAn integer port with max of 10 to a port with a min of 15)
oMismatched Units (a temperature in Fahrenheit connected to a temperature in Celsius)
These properties are stored in the Signal Dictionary. In MxTransIt, you can set the values manually using the Edit Port dialog. For some Transforms, you can also set these values in the Properties box. The data can also come from a Simulink model. If the values from the Simulink model do not match the values in the Signal Dictionary, a warning is generated. If you are using a VMC, the port properties come from the AppIF.c file.
Setting Signal Properties in MxVDev
Editing Port Properties in MxTransIt