System Signals control and monitor the operation of MxVDev and the Test Harness. System Signals are predefined and always available. You can add these Signals to your tests just as you would add other Signals. The Signals are inputs to (or outputs from) Transforms of MxVDev and the Virtual Wiring Harness.

The Signals are:

Signal Name

Classification

Signal Purpose

MxV Input Reset

Event

When a transition is executed on this signal, all Stimulus Signals from MxVDev to the Harness (that may have been changed as a Scenario runs) are reset to their Initial Value as defined in the Signal Dictionary. This is equivalent to resetting all the switches for input signals to their nominal position on a HIL tester.

For more details, see System Reset.

MxVMC - MxVDev sets all input signals to their initial value as defined in the Signal Dictionary or in the AppIF.c file.

MxV Module Reset

Event

MxV Module Reset is used to re-initialize the Test Harness. This is equivalent to cycling the power. See System Reset for more details. For an example using this signal, see Getting Started with MxTransIt.

MxVMC -  When a transition is executed on this signal, the SUT is unloaded and loaded. This means that all global and static variables in the code reset back to their initial values as defined in the code (all RAM is reset to zero, then variables explicitly initialized in the SUT C source code are set to those values). After loading the SUT, MxVDev sets all input signals to their last value. The value of all input signals remains the same after a MxV Module Reset, but the value of all output signals could change.

MxV RegressionInfo

Message

This System Signal is a fixed-length message signal of 1024 bytes. It enables you to capture data from the Test Harness that is subsequently used in building the Regression Report. It has the following characteristics:

Data received on this port is added to the Mxrlg file in an XML block called <RegressionInfo>. Each transition received is stored as a new record.

The captured information is presented in the Run Time Information section of the Regression Report. Each transition record is a new line in the report.

Only printable ASCII characters (including tabs and spaces) are displayed in the report. Characters after the first non-printable character are discarded. You can therefore use null (0) to terminate a string.

By default, MxVDev adds Regression Start and Regression End times to the <RegressionInfo> block.

To deliver information to the Run Time Information section of the Regression Report:

1.Create a custom Transform that has a fixed-length message output port called MxV RegressionInfo.

2.Export the port.

3.Send printable ASCII transitions to the port.

For a typical use case, see Regression Report.

MxV RunTime Event

Message

Certain events can occur during execution of a Scenario that cause the Scenario to not complete successfully.  For example:

A Transform in the Harness fails to find a referenced file or generates an overflow

The MxVMC encounters a memory access violation

These are classified as Run-Time Events. When such an event occurs, the MxV RunTime Event signal is automatically added to the running test case(s). This System Signal captures information about when the event occurred and what happened. This causes the Scenario to fail and enables you to see a message indicating what happened. Transitions on the MxV RunTime Event signal contain information about the Run-Time Event.

Typically you do not add this signal to a TestCase manually. If it exists in a test, then an unusual event must have occurred. Once the issue is diagnosed and resolved, the MxV RunTime Event signal should be removed.

MxV Shell Command

Message

This System Signal enables you to submit an executable (script, program, or batch file) to Windows for execution while a test runs.  Anything that can be run from the windows command line can be run from here.  Double-click on the plot line to place a transition on this Signal at the point that you want the executable to run.  A dialog box is presented enabling you to provide the following:

MxV-Shell-Command

Executable File - This is the name of the executable to be run.  You can, for example, enter notepad.exe to launch the Windows Notepad Editor as a test executes.

Command Line Parameters - A string of parameters passed to the executable as part of the command line.  The %% delimited strings are used to pass different parameters in the command line based on the current execution context of MxVDev.  For example, providing %ScenarioName% in the parameters field results in the command line parameter being set to the name of the Scenario that is running.

Other options:

Pause Simulation until execution is completed - Setting this flag stops the MxVDev simulation clock until the executable is completed.  This option is not recommended for real-time systems. If you do not check this box, then be sure to leave enough time in the test for the executable to run before you continue with other dependent actions.  It is usually desirable to keep this box unchecked, since otherwise recorded times after the transition cannot be related to those before the transition.

Executable Path Save Options - There are three options for saving the path that is entered.  This becomes important to consider when an MxSuite project is copied from one location in the file system to another. Note that if no path is provided (that is, only the executable name is entered) then no path will be saved.  In this way, the Windows search path is used to locate the executable to be run.

oAbsolute - Save the path starting with the drive letter of where the executable is stored.

oRelative - Save the path relative to the MxVDev project folder.

oAuto - If the executable is in or below the project folder the path is saved as relative, otherwise it is saved as absolute.

Comments - Comments are used to document the test cases.  If a comment is added, then the transition is marked with a yellow dot, and the comment is displayed when the mouse passes over the dot.

MxV Tick Duration

Continuous Float

This System Signal is useful for diagnosing execution performance problems. It measures in milliseconds the time spent ticking the test harness. The "Capture Performance Statistics" option on the Project Settings Execution tab must be enabled for this Signal to measure its data.

MxV Tick Latency

Continuous Float

This System Signal is useful for diagnosing execution performance problems. It measures in milliseconds the time difference between the expected tick time and the actual tick of the test harness. The "Capture Performance Statistics" option on the Project Settings Execution tab must be enabled for this Signal to measure its data.

This signal only has valid values when the Simulation Clock Time Source is set to RT Clock (Real-time).

Bus Control System Signals

Signal Name

Classification

Signal Purpose

MxV Auto Msg Tx

Discrete

This signal enables you to start and stop the automatic transmission of CAN message Signals as configured in the DBC file.

When set to True, automatic transmission of messages for all buses and all nodes is switched on.

Transmission occurs as defined in the DBC files, unless explicitly switched off by one of the System Signals below.

Default value is True.

See Automatic Message Transmission.

MxV Auto Bus Tx

Message

This Signal controls the automatic transmission of periodic messages on a specified CAN or LIN Bus.

NO automatically generated messages are transmitted on the specified Bus when this Signal is set to False.

Default value is True.

When you add a transition to this Signal in a TestCase, the following form is displayed:

MxVAutoBusTx-TE

If you are using the CAN Transmit Driver, see MxV Auto Bus Tx Router.

MxV Auto Node Tx

Message

This Signal controls the auto transmission of periodic messages from a particular Node on a Bus.

NO automatically generated messages are transmitted for the specified Node when this signal is set to False.

Default value is True.

When you add a transition to this Signal in a TestCase, the following form is displayed:

MxVAutoNodeTx-TE

MxV Auto Msg Cfg

Message

This Signal is used to modify the automatic transmission of messages.

You can modify whether auto-transmission is on or off, and for periodic messages you can modify the transmission rate.

You can also easily revert back to the standard transmission pattern defined in the DBC/LDF file.

This cannot be added to an Interactive Panel at present.

If a LIN Signal is not explicitly contained in the Normal schedule table, it is not affected by the MxV Auto Msg Cfg setting. For example, MasterReq cannot be disabled unless a LIN Diagnostic signal is part of the Normal schedule table.

When you add a transition to this Signal in a TestCase, the following form is displayed:

MxV-AutoMsgCfg

See Automatic Message Transmission.

MxV Bus Enable

Message

This Signal enables or disables a Bus. Buses are enabled by default.

The signal is a 17-byte message.

The first 16 bytes contain the GUID of the bus.

If the last byte is zero (False), the bus is disabled and NO messages are transmitted on the bus, even if they are explicitly specified in a TestCase.

If the last byte is nonzero (True), the bus is enabled.

When you add a transition to this Signal in a TestCase, the following form is displayed:

MxV_BusEnable

To import data for this Signal, see Importing Test Data.

If you are using the CAN Transmit Driver or LIN Transmit Driver, see MxV Bus Enable Router.

MxV Node Enable

Message

This Signal enables or disables a Node on a Bus. Nodes are enabled by default.

The signal is a 57-byte message.

The first 16 bytes contain the GUID of the bus.

The next 40 bytes contain the node name.

If the last byte is zero (False), the node is disabled. If it is nonzero (True), the node is enabled.

When the node is disabled , NO messages are transmitted from the Node, even if they are explicitly specified in a TestCase.

When you add a transition to this Signal in a TestCase, the following form is displayed:

MxVNodeEnable

To import data for this Signal, see Importing Test Data.

MxV LIN Go to Sleep

Message

This Signal transmits a LIN-Go-To-Sleep frame (Id=0x3C, data=0x00FFFFFFFF) on the specified bus. When a LIN Go-To-Sleep is issued, the bus remains sleeping even if the Scenario is closed. It does not wake up until a Wakeup is issued or the project restarted.

When you add a transition to this Signal in a TestCase, the following form is displayed:

MxVLIN_sleep

The text in parenthesis indicates where the network is defined.

To connect this Signal to a port, see MxV LIN Go To Sleep Router.

MxV LIN Wakeup

Message

This Signal transmits a LIN Wakeup request (forcing the bus to be dominant for 250 µs to 5 ms) on the specified bus.

When you add a transition to this Signal in a TestCase, the following form is displayed:

MxVLIN_wakeup

The text in parenthesis indicates where the network is defined.

To connect this Signal to a port, see MxV LIN Wakeup Router.

MxV LIN Switch Schedule Table

Message

This Signal enables you to change the LIN Signal Table used by the LIN Transmit Driver Transform it is connected to. Use this Signal to change the Schedule Table during a test. If you are using more than one LIN Transmit Driver, route this Signal through a Pass-Through Transform.

When you add a transition to this Signal in a TestCase, the following form is displayed:

MxVLIN-SwitchScheduleTable

The text in parenthesis indicates where the network is defined.

MxV Lin Diagnostic Request

Message

This Signal transmits Diagnostic Request messages onto the specified LIN bus. See LIN Diagnostics.

MxV Lin Diagnostic Response

Message

This Signal receives Diagnostic Response messages from the specified LIN bus. See LIN Diagnostics.

Related Topics:

Signal Classification

Signal Dictionary

Automatic Message Transmission

Creating a Trigger on System Signals