MOST Connector

The MOST Connector Transform uses K2L ATS version 1.07.14 by default. If a different version is installed on your system, the following dialog box is displayed:

Select the version installed on your system. See Compatibility.

Note: MxTransIt must be running in Administrator mode. If it is not, close it, right-click on MxTransIt in the Windows Start menu, and select Run as administrator.

Use this procedure to configure the MOST Connector Transform:

1.In the MOST Transform's Select K2L Generated dll File property, click on the browse button () to display the Generate FBlock form.

2.Click the Add button to open the file open dialog.

3.In the file open dialog, browse to the location where K2L MAG generated .dll files (such as AudioDiskPlayer.dll) are stored.

4.Select a K2L MAG generated .dll file (such as AudioDiskPlayer.dll). Click on the Open button to add the selected DLL file to the Selected Dll Path list box in the Generate FBlock form.

Note: Multiple DLL files can be added. DLL files can be removed using the Remove button.

5.Click the Refresh button to list all available FBlock names (along with their associated fields).

6.Choose the appropriate check boxes. You can select one, both, or neither:

•Select the Use Simulated Fblocks check box if you want to send data to the corresponding simulated FBlock connected to the K2L ATS.

•Select Use MOCCA Compact Hardware.

7.Select one or more Fblocks from the Receive From column to simulate a Shadow object (for example, AudioDiskPlayer FBlock).

Note: At least one FBlock in the from Receive From column should be selected.

8.Select one or more Fblocks from the Simulate and Transmit for column to create a simulated FBlock object. Then click the OK button.

All Inports and Outports for the selected Fblocks are automatically generated on the Most Connector Transform.

Notes:

•Standard Inports and Outports are generated for the Fblocks selected in the Receive From column. For example:

oAmplifier.Dspmode.dspmode_i as inport

oAmplifier.Dspmode.dspmode_o as outport

oIts corresponding Get: Get_ Amplifier.Dspmode

•Simulated Inports are generated for status and Get of Fblocks selected in the Simulate and Transmit for column. For example:

oGet port name: Si_Get_ Amplifier.Dspmode

oStatus port name: Si.Amplifier.Dspmode

•Inports that can be used to change the device ID of selected Fblocks in the Simulate and Transmit for column are created. You can specify the specific device ID for which you want to transmit status message.

•Message type signals are created for every function of Fblocks selected in the Receive From or Simulate and Transmit for columns to send MOST messages completely configured by the user. For example:

oIMsg_ Amplifier_Dspmode as inport

oOMsg_Amplifier_Dspmode as outport

1.Configure the Transform by selecting the required Fblocks To Simulate and To Test.

2.To use the Message type signals to configure MOST messages, export ports prefixed with IMsg and OMsg.

3.In MxVDev, create a TestCase and use the Pick Signals dialog to select Signals prefixed with IMsg and OMsg.

4.Save the TestCase. It should look something like this:

5.To create a transition on a Signal, double-click in the plot area of the Signal or right-click and select Insert Transition.

Time: The time of the transition (the time the message Signal is transmitted).

Comment: Optional comment about the transition.

DeviceId: By default, the DeviceId of the message Signal is 01023 for broadcasting (Unblocking). You can change the DeviceId to a value from 0 to 65535.

FblockName.Function: This field is read only. It shows FBlockName and Function Name.

InstId: By default, the Instance ID for the FBlock is 0. The valid range is 0 to 255.

OpTypes: The OpTypes field is a combo box that is automatically populated according to the available optypes of the specified function of the FBlock. OpType generation also depends on whether the FBlock is a shadow or simulated FBlock or both in the Generate FBlock options.

After selecting OpType from OpTypes field, all the parameters and parameter types present in the selected OpType are populated in ParameterName field and Type field. Enter the data for value field.

6.You can also edit or insert raw data bytes in Message Raw Data tab.

7.After clicking OK, if all the data bytes are valid, the system generates the message buffer.

8.To run your TestCase, add it to a Scenario. If necessary, you can create a new Scenario.

9.Click the Run button to execute the Scenario.

Note: You can use other Signals, together with the IMsg or OMsg Signals, in the same test case.

For Simulated Input

1.Follow steps 1 through 7 above.

2.Select signals preceded  by “Si.” to set the corresponding status parameters of a specific function of a specific FBlock. Add the required signals to the TestCase as described above.

3.Add deviceid Signal of the corresponding FBlock for which status is to be sent. Set the required device ID in decimal value.

4.Add Get Signals preceded by “Si” to call the corresponding Status of a specific function of a specific FBlock. Make the Get Signal high to get the status.

MOST Message Input

1.Follow steps 1 through 7 above.

2.Select signals preceded by “IMsg” or “OMsg”.

3.To insert a transition to specific signal, double-click on the Signal plot line or right-click and select Insert Transition.

4.Enter the data in various fields:

Time: The time at which the message is to be transmitted.

Comment:  Comment on the transition.

DstID (Hex): By default the DstID (Destination ID) of the message Signal is 03FF (for broadcasting (Unblocking)). This field only allows hex values. You can change the value of the DstID within the range 0 to FFFF.

FblockName.Function: This field is read only.

InstID: By default the instance ID for the FBlock is 0. You can change the InstId within the range 0 to 255.

OpTypes: The Optypes field is a combo box will be automatically populated according to the available optypes of the specified function of the FBlock. Optype generation also depends on whether the FBlock is selected as a shadow or simulated FBlock or both in the Generate FBlock options.

After selecting an Optype, all the parameters and parameter types present in the selected Optype are populated in the ParameterName and Type fields respectively. Enter the data for Value field. For numeric values, enter in decimal or enter a Hex format number preceded by 0x. For example: 0x03FF.

You can also edit or insert Raw data bytes using the Message Raw Data tab. (See format below.)

Format of Message Raw Data

0th & 1st  byte is for DstID (Destination ID) in Hex Format.

2nd byte is for FBlockId in Hex format.

3rd  byte is for InstID (instance ID) in Hex format.

4th and 5th byte is for Fktid. (in Hex Format).

6th byte is for Optype, User have to give the Hex value of required Optype.(e.g Set =00,Get=01, Status=0C).

From 7th byte onwards all are for Payload. (in Hex Format)

Use these instructions to create a demo program that issues some simple MOST commands and will familiarize you with setting up the transform and messages.

Prerequisites

Procedure

In MxVDev:

1.Open MxVDev and create a new project:

a.Locate the project in a new folder or an existing folder.

b.For SUT Type, select Custom.

c.Select the RTClock.

d.Click Finish.

2.To make the project portable, copy the MOST FBlock dll file (GIS-361_FCv245_MAGv234_27Nov12.dll) into the new project’s folder (the same place that the MxV.mxp file is located).

In MxTransIt:

1.Add the MOST Transform block from the Toolbox.

2.Click on the MOST Transform to select it.

3.In the Transform's Properties box, under MOST Configuration, click at the end of the Select K2l Generated dll Files property.

4.In the Generate FBlock dialog box, add the FBlock DLL file (GIS-361_FCv245_MAGv234_27Nov12.dll).

5.Click Refresh – it takes a few seconds

6.For this example, select:

•Use MOCCA Compact HW

•Use Simulated Fblocks

7.In the Receive From column select:

•ClusterHMI

8.In the Simulate and Transmit for column select:

•NetworkMaster

•AVManager

9.Select the MOST transform block and Export the following ports:

•IMsg_AVManager_BaseChannelStatus

•IMsg_NetworkMaster_Configuration

•OMsg_ClusterHMI_FBlockInfo

10.Click Save ().

In MxVDev:

1.Click OK on the two Connections screens that appear to import the three exported signals.

2.Create a new Scenario.

3.Create a new TestCase. Add the three exported signals to the TestCase.

4.Add the TestCase to the Scenario.

5.In the TestCase, right-click on the IMsg_NetworkMaster_Configuration message plot line around the 1s mark.  Select Insert Transition.

6.Configure the transition as shown below.

7.Right click on the IMsg_AVManager_BaseChannelStatus message signal line in the test case around the 2s mark.  Select Insert Transition.

8.Configure the transition as shown below:

9.Click Save All () then run the Scenario.  The TestCase sends a Network Master configuration followed by an AVManager message to select XM radio.