To enable the harness to use LIN Diagnostics:
1.Choose one of the following to open the LIN Bus Configuration form:
•Click in the LIN Database field in the properties of the LIN Transmit Driver Transform:
•Click in the LIN Database field in the Network Configuration form:
2.Select a diagnostic request and a diagnostic response schedule table.
4.If your bus was defined in Network Configuration (MxVDev), skip the remaining steps:
a.The LIN Transmit Driver has a property under the Diagnostic header named Response Web. Select the Response Web from the drop-down list.
LIN Transmit Driver Properties
b.On the LIN Receive Driver, select the Stimulus Web.
c.Add an MxV LIN Diagnostic Request Router Transform to the harness.
d.Connect its outport to the MxV Lin Diagnostic Request port on the LIN Transmit Driver, and export its inport.
e.Save the harness, and close MxTransIt.
LIN Diagnostics use two System Signals: MxV Lin Diagnostic Request and MxV Lin Diagnostic Response. Both have their own transition editors, which are used to create messages. In a TestCase, double-click on the Signal's plot line to create a transition (message).
Transition Editor Form
Bus: Use the Bus drop-down list to specify which bus to send the message to. The text in parenthesis indicates where the network is defined. This field is used by the MxV LIN Diagnostic Request Router.
NAD: Node Address for Diagnostics (The address of the node to which the message will be sent).
SID: Service Identifier (On the diagnostic response form, this is RSID or Response SID which is SID + 0x40, or 0x7F if it is a negative response.)
Length: This is how many bytes to send. The maximum is 4095.
Data: The bytes to send.
If the message to send is over 5 bytes, MxVDev uses a transport protocol to transfer the message. Likewise, the transport protocol is used to receive a response that is over 5 bytes.