To work with an MxVMC, the version of the MxSuite you are using must be set as the current version. If you are not sure, use one of the procedures in Set Current Version.
1.Create a new project in MxVDev. Follow the wizard until you see this form:
2.Select Custom SUT and MxClock. For information on clocks, see Real Time/Accelerated Time.
3.Check Start MxTransIt on Finish.
4.Click the Finish button. MxTransIt opens.
Note: If your project contains more than one VMC, create a subfolder for each VMC.
a.Use Windows Explorer to navigate to your Project folder and click the new folder button ().
b.Create a new folder for each VMC to be created. In this example, we use folders One and Two.
c.After you've created the folders, return to MxTransIt.
1.Type VMC in the Filter box at the top of the Toolbox on the left of the screen to find the Virtual Microcontroller Transform. Double-click to put it into the Harness window.
2.Click the Create VMC Visual Studio Solution verb at the bottom of the Properties box.
3.Navigate to the folder you created. In this example, One.
4.Click the Select button to launch Visual Studio.
If Visual Studio does not open, see Visual Studio and MxVDev.
6.Select Build->Rebuild Solution from the Visual Studio main menu.
7.When the build has completed successfully, exit Visual Studio.
8.Use the Name field in the Properties box to choose an appropriate name for the new transform. In this example we used VMC One.
9.In the Properties Box, set the Signal Dictionary File Path. Navigate to your Single Dictionary file in the Project folder--not in the subfolder you created for the VMC. The file name ends in .mxd.
10.Click the Connect/Reconnect verb at the bottom of the Properties box to display the predefined ports.
11.Repeat this procedure for each VMC to be used in your project. In this example, we create two VMCs, named VMC One and VMC Two.
To avoid confusion, you may want to rename some of the ports in the C source code so that the signal names are unique.
There are 3 ways to add ports to a VMC:
•Guided Harnessing - Use the Guided Harnessing tool to select the Signals to use for testing the SWC.
•Manually - The AppIF.c is a C code file and can be written or revised by a programmer. This may be the best way when working with an existing project or a non-standard interface. For details, see Manual Harnessing.
For more detail on harnessing, see Linking your code with the MxVMC.
There are two ways to export ports from an MxVMC:
Use the procedure in Connecting Signals to connect the ports to MxVDev.
Use the Properties box to set properties which control the behavior of the MxVMC:
By default, IsSut = True and the MxVMC is a Connector Transform. All Connector Transforms in the Test Harness logically execute in parallel. Interconnections between Connector Transforms require a Delay Transform.
Set IsSut to False to treat the MxVMC as a Signal Processing Transform. SP Transforms are ticked sequentially. Inport values are read and outport values are transmitted in a single tick.
Auto Export Signals
Use this property to choose the method of exporting ports: manual or automatic. False (manual) is the default.