This project is a comprehensive example of a SIL test environment for a body control module. It can be used to understand the basic features of the MxSuite.
There are two versions of the TurnDoor sample:
•TurnDoorSampleAutoTick - In the AutoTick project, the tick rate for the SUT is determined by an MxVSetTaskAutoTickPeriod function in the appif_register.h file. See: Port Registration.
•TurnDoorSample - In this project, the main entry point of TurnDoor is void AppTask_5ms(void). This is located in App.c. The Task_5ms Signal in the TestCase of the same name invokes (ticks) the App_Task_5ms function every 5ms of simulated time.
AutoTick is the preferred method.
Applies to: •MxSuite 3.40 or later Other Requirements: •A supported version of Visual Studio is required to compile or modify the SUT (MxVMC) code. You can run the test without Visual Studio. •The user should have an understanding of MxSuite Scenarios, TestCases, and Transforms. |
There are two versions of the TurnDoor sample. Use these links to download:
|
This sample includes examples of the following features: •All types of Signal classifications (discrete, continuous, message, image) •Signal patterns (specified, expected, and actual) •Scenarios •TestCases •CAN communication •Auto message transmission •Interactive Test Panels •Image signals •An MxVMC to simulate a simple body control module |
To run the open Scenario, click the run button ( You can experiment to see how the code behaves as follows: 1.Open the Scenario called InteractiveBackgroundScenario.mxs. 2.Open the Interactive Test Panel called InteractiveTest1. 3.On the toolbar set the Clock Source to RT Clock. The tortoise ( 4.Click the Run button, and experiment with the controls in the interactive test panel. |
There are four main features and four main functions: door_lamp_handling(); //This code provides the logic for changing the intensity of the Dome Lamp based on when the doors are opened.
turn_lamp_handling(); //This code flashes the indicators based on the position of the left and right turn switches.
Odo_Update(); //This code is responsible for incrementing the odometer (distance traveled) based on the speed of the vehicle.
LCD_Update(); //This code provides the logic for the scrolling marquee that displays 'MicroMax' in the driver information center. You may need to use the MSVS conversion wizard and convert the solution to run the sample. |
Getting Started with the Invert Sample (a simple VMC)
MxVMC - The Virtual MicroController