Setup Diagram for SAIC LIN Project

Setup Diagram for SAIC LIN Project

OEM Test: LIN Single wire

Specification: SMTC 3 800 003－2013

Transceiver: Configuration 4 LIN

Project: MxPLTSAICLIN.zip

hmtoggle_plus1Generate Test Cases for SAIC LIN Project

1.Open Mx‑VDev.

2.Select File-> Open->Project from the main menu.

3.Use the Open dialog to select one of the following project files:

•64 bit: C:\Program Files (x86)\MicroMax\ MxSuite 3.xx.xx.xxxxx \Samples\MxPLTSAIC_LIN\MxPLT Sample Project SAIC_LIN.mxp

•32 bit: C:\Program Files\MicroMax\MxSuite 3.xx.xx.xxxxx\Samples\MxPLTSAIC_LIN\MxPLT Sample Project SAIC_LIN.mxp

4.Click Open.

5.Click Edit Harness (3dots_button) to start Mx‑TransIt.

6.In Mx‑TransIt, click on the PLT Test Manager Transform to select it and display its Properties box.

7.Click the “Launch MxPLTConversionTool” Verb to open the tool.

8.Select the “TestCases Generation” tab to generate Scenarios and TestCases dynamically based on selected inputs.

PLT-SAIC-LIN-tct

9.Following are the inputs for the ‘TestCases Generation’ tab of the Mx‑PLT tool.

a.Select TestCase Definition File. Click the browse button (3dots_button) to select the file. Once the input test case definition file is selected, fields in the GUI (Vendor Spec, Bus Interface, Baud Rate, LIN Device Type, LIN Device Clock, LIN Slave Specific ID are automatically loaded.

b.Change the “Baud Rate” as per DUT type.

c.LIN Device Type. Select "Slave" or "Master" depending on the DUT type.

d.LIN Diagnostics. If the DUT supports the diagnostic messages, select “Supported”. If not, select "Not Supported".

e.Enter a valid LIN Slave Specific ID, which is the header received and ECU responds with Data bytes. Applicable for LIN Slave DUTs. This option is not mandatory for LIN Master DUTs.

f.Click the browse button (3dots_button) to select the Mx‑VDev project folder.

10.Click the Generate TestCases button to generate Scenarios and TestCases for a specific OEM.

Close the Test Conversion Tool, but leave MxVDev running.
hmtoggle_plus1Using the SAIC LIN Project

1.Open Mx‑VDev.

2.Select File-> Open->Project from the main menu.

3.Click Open.

4.The generated Scenarios and TestCases are displayed in the Project Explorer:

5.Select Tools->Regression Test->New.

6.Click the Add button in the Regression Command File dialog:

7.Enter User Details (Optional) in the Test Info panel. Click Next.

8.Click Next in Regression Output Wizard.

9.Click Next in Distribution List.

10. Click Next in Execution Options.

11. In the Scenario Query Builder, expand the tree for the Slave folder. Select a Scenario (for example: "4.1.1 Capacitance.mxs") and click Next.

12. Click Finish to open the Save Regression Script dialog:

13. Save the Regression Script File (.mxreg).

14. Click the "Close and Run" button in the Regression Command File dialog:

 

The Regression Test Progress window shows the progress and pass/fail information of the Regression Test for the selected Scenario.

 

After completion of the Regression test, the report is automatically displayed.
hmtoggle_plus1SAIC LIN Slave/Master Test Cases

Test Name

Test Description

Observation

4.1.1 Capacitance

To Verify if the node capacitance meets expected response of LIN 2.1.

198 pF≤C≤242 pF

4.1.2 LIN signal voltage level for recessive state

To verify LIN signal voltage level for recessive state

VBUSrec> 0.6*VSUP

4.1.3 LIN signal voltage level for dominant state

To verify LIN signal voltage level for dominant state

VBUSdom<0.4* VSUP

4.1.4 Bit time

Measure the time between two falling edges in the datafield when testing slave node

 

Measure the time between two falling edges in a synch field when testing master node

 

For Slave:51.04 μs≤tBit≤53.13 μs

 

 

 

For Master: 51.82 μs≤tBit≤52.34μs

4.1.5 Slew rate

Capture the LIN frame sent by the node with oscilloscope.

Select a rising edge slope (Dominant to Recessive) and falling edge slope (Recessive to Dominant)  of LIN signal voltage level.

Individually measure slew rate

1 V/μs< SL < 3 V/μs

 

4.1.6 Duty cycle

Capture the LIN frame sent by the node with oscilloscope.

Individually measure Duty Cycle (D1) and D2 and then Verify if the duty cycle (D1 and D2) meetsexpected response.

D1 > 0.396

D2 < 0.581

4.1.7 Tolerance of baud rate for slave nodes using synchronization

Verify if slave nodes that usesynchronizationthe tolerance of baud rate is within ±2% ofmaster .

Slave node baud rate is within19.2 kbit/s±2 %.

4.1.9.1 LIN wiring is interrupted

Interrupt LIN when the network is working.

 

Recover to communicating within300 ms after fault removal.

4.1.9.2 LIN shorted to the positive pole of the power supply

LIN is shorted to the positive pole of the power supply when network is working.

Recover to communicating within300 ms after fault removal.

4.1.9.3 LIN shorted to ground

LIN shorted to ground when the network is working

Recover to communicating within300 ms after fault removal.

4.1.10.1 Power of tested node is lost

Disconnect the power of the nodeWait for 120 sCheck if the tested node keep communication

The tested node communicates correctly

4.1.10.2 Ground of tested node is lost

Disconnect theground of the node

Wait for 120 sCheck if the tested node keep communication

The tested node communicates correctly

4.1.10.5 Inject frames with different baudrate

Verify if the nodes recovercommunicatingcorrectly afterstopping frames with different baudrate.

Inject frames with different baud rate at 9.6 kbit/sand 10.417 kbit/s separately to LIN network.

All nodes recover communicating correctly

4.2.1 Frame ID

Verify if LIN ID is according to designrequirement.

DUT transmit LIN frame ID meet therequirement of Network Config File

4.2.2 Frame DLC

Verify if LIN DLC is according to designrequirement

Frame DLC should meet the requirement ofNetwork Config File

4.2.3 Frame period

Verify if frame period is according to designrequirement.

Frame period should meet the requirement ofNetwork Config File

4.2.4 Header length

Verify if headerlength meets expected response.

1.771ms≤t≤2.480ms

4.2.5 Frame length

Verify if the frame length meetsexpectedresponse.

Refer to Table 24 of document SMTC 3 800 003

4.2.6 Communication error

Run tested-system about 24 h continuously

There should be no error.

4.3.1 Start-up condition

Verify if the starting condition of the node iscorrect

Acceptance Criteria:

Meet the requirements of theTable 27 of document SMTC 3 800 003

4.3.2 Start-up time

Verify if the start timing of the master node meets requirements

Acceptance Criteria:

80 ms ≤ △t ≤ 300 ms

4.3.3 Shut-down time

Verify if the timing of shut down meetsrequirements

The node should stop transmitting within 200 ms when the KL.15 is off,

4.3.4 Bus sleep

Verify if the node can enter sleep state

Acceptance Criteria:The node should go into sleep mode

4.3.5 Bus wake-up

Verify if the node is woken up correctly

The node should start communicating after receiving wake up.

4.3.6.1 Low power supply

Adjust the normal voltage of power supply with 0.2 V ata rate of 1 min per step down to stop communicating

The node should communicate correctlywhen the supply is above 8.5 V

4.3.6.2 High power supply

Adjust the normal voltage of power supply with 0.2 V at

a rate of 1 min per step up to 19.0 V

The node should communicate correctlywhen the power supply is under 17.5 V