MxSuite MOST Transforms provide a testing environment to test and simulate Fblocks. These transforms interact with real modules using MOST FBlock messages or simulate the FBlock functionality. There are three transforms required for MOST protocol: the MOST VNode transform, the MOST Receive Driver, and the MOST Transmit Driver.

The MOST VNode Transform is meant for complete simulation. It acts as a simulator for single or multiple Fblocks.

The MOST Receive Driver is meant for monitoring MOST Bus and MOST Spy Bus. The MOST Receive Driver monitors the total bus activity and can monitor communication between two different modules. It can also analyze the messages with expected results. The Receive driver also get the notification and status messages from the corresponding FBlock.  

The MOST Transmit Driver acts as a transmitter to the MOST bus. It can transmit messages to any module according to its connection. It can be connected to both the MOST Bus or to an FBlock, according to port property selection.

The MOST Master Transform controls all the MOST Transforms available with the MxSuite (MOST Transmit Driver, MOST Receive Driver, and MOST VNode Transform).

 

MOST001

Advantages of MOST Transforms

It’s a more generic approach of simulating a particular test environment for Fblocks.

You can simulate a single or multiple FBlock for simulation by loading a single or multiple K2l generated DLLs.

You can use multiple TestCases with different conditions for an FBlock.

Making TestCases is easy, you just have to export ports, edit the Signal pattern to set the value, and you are ready to simulate.

Handling stream signals is easier with a simple and effective transition editor user interface.

Once testing is complete, MxVDev generates an HTML report, which contains all the details of the test and a description of pass/fail results.

K2L Automotive Test System with the MxSuite

The K2L Automotive Test System (ATS) is a set of .NET libraries and programs that communicate with MOST devices through the MOCCA compact hardware interface. The effort of writing device and system test applications is reduced by using ATS, because they can use the integrated development environment Microsoft Visual Studio in conjunction with the power of the standard .NET languages C# and Visual Basic. Furthermore, the usage of generated catalogs (binary files created by the MAG) allows access to the complete and structured object model representing, for example, the methods, properties, and events of a specific MOST interface.

Architecture

A typical ATS system with MxSuite configuration looks like the figure shown below.

MOST002

The example above includes two executables: the K2L viewer and the MxVDev application, which is executing all three MOST Transforms. These programs are linked to the MOCCA compact hardware using the ATS software components. The MOCCA compact device is a member of the underlying MOST ring, which contains one or more "Devices Under Test." The Network Master is necessary just for completeness.

All executables are connected to a common service called the ATS service. The ATS service runs in the background. It manages all MOST message traffic in the PC and the messages between the MOCCA hardware and the executables running on the PC. This ATS service also acts like a virtual MOST bus in the PC.

All executables which communicate with the ATS service are embedded with the ATS framework, which is the library containing all methods and protocols defined by K2L for MOST protocol communication with ATS. The executables/processes communicate with the ATS service with an inter-process communication (IPC) mechanism.

In MxVDev, all three MOST Transforms are running. Each Transform acts as a separate module in the executable embedded with the ATS framework. When the MOST VNode Transform is connected, the MOCCA hardware is disconnected, as with VNode Transform the Fblocks are simulated as virtual ECU and its parameter values can be controlled with a C# snippet, SIL, or a Simulink model. When the Transmit driver is connected to the ATS service, it creates shadow(s) of the FBlock(s) as specified by the user during the port generation for the Transform. While sending any Tx signal, the Transform sends it to the ATS service. If MOCCA hardware is connected, it will update the shadow in the ATS service and the Receive driver Transform will detect it, if present.

In the absence of real hardware, the MOST VNode Transform can be used to simulate any FBlock and its behavior. The VNode Transform simulates the Fblocks as specified by the user during its port generation. In that case, the Tx messages sent by Transmit driver are received by the VNode Transform from the ATS service. The parameters are updated respectively with SIL or Simulink, and then it updates the shadows in the ATS service. Then, the Receive Transform receives the updated message as a simulated FBlock, in the same way it receives from the MOCCA hardware.

Related Topics:

MOST VNode Transform

MOST Transmit Driver

MOST Receive Driver

MOST Master Transform

MOST Stream Parser

MOST TestCase Generator

Demonstration Projects

MOST Virtual Bus Monitor and Filter

MOST Connector (deprecated)