Setup Diagram for Fiat LSFT Project
OEM Test: FIAT Dual Wire Low Speed Fault Tolerant CAN
Specification: 7-Z0140
Transceiver: Configuration 2 DWCAN FT
Project: MxPLTFiatLSFT.zip
1.Open Mx‑VDev. 2.Select File-> Open->Project from the main menu. 3.Use the Open dialog to select the project file: MxPLT Sample Project FiatLSFT.mxp 4.Click Open. 5.Click Edit Harness ( 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. 9.Following are the inputs for the ‘TestCases Generation’ tab of the Mx‑PLT tool. a.Select TestCase Definition File. Click the browse button ( b.Change the Baud Rate as per DUT type. c.Crank Communication. If the DUT supports communication during cranking, select “Supported”. Otherwise select the “Not Supported” option. d.Select Ignition Type: •Select “Input High” if DUT wakes-up with 12V – 14V on ignition line. •Select “Input Low” if DUT wakes-up with 0V on ignition line. •Select “None” if DUT wakes-up with Vbatt itself. e.Enter a valid CAN Rx Id, which is received from ECU. This Rx ID is used to trigger and display the waveform. f.Click the browse button ( 10.Click the Generate TestCases button to generate Scenarios and TestCases for a specific OEM. 11.Select the Message Configuration tab. 12.Configured default messages are displayed and you can edit the messages as applicable based on the ECU under test. This message used to wake-up the DUT and to continue the ECU communication (BCM message). Note: Default configured messages need to be deleted if the ECU wakes up with Vbatt or Ignition line. 13.Click the Save Configuration button, and observe the “XML file successfully generated” message. Note: The CAN Configuration file path is the same as the MxV Project folder path selected in the “TestCase Generation” tab. 14.Close the Test Conversion Tool, but leave MxVDev running.
|
1.Open Mx‑VDev. 2.Select File-> Open->Project from the main menu. 3.Use the Open dialog to select the project file: MxPLT Sample Project FIAT.mxp 4.Click Open. 5.The generated Scenarios and TestCases are displayed in the Project Explorer: 6.Select Tools->Regression Test->New. 7.Click the Add button in the Regression Command File dialog: 8.Enter User Details (Optional) in the Test Info panel. Click Next. 9.Click Next in Regression Output Wizard. 10. Click Next in Distribution List. 11. Click Next in Execution Options. 12. In Scenario Query Builder, expand the Tree for the FIAT folder. Select a Scenario (for example: "7.2.2 Dominant signal Voltage levels.mxs") and click Next. 13. Click Finish to open the Save Regression Script dialog: 14. Save the Regression Script File (.mxreg). 15. 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. |
Test Name |
Test Description |
Observation |
---|---|---|
7.1.1 Extended format message compatibility |
To establish communication on the CAN bus then use the test instrument to transmit a single extended format 8 data byte message (29 bit ID). |
Check that the DUT returns an acknowledgment in the message (ACK slot =dominant) and cannot send error messages. |
7.2.1 Recessive signal voltage levels |
To measure the CAN bus signal recessive state signal voltage levels and check that the level meet the specifications. |
Observe the scope data should be in the below ranges. 1. VCAN_H < 0.3V 2. VCAN_L > 4.45V 3. -5.25 < Voutput_diff < -4.15V |
7.2.2 Dominant signal voltage levels |
To measure the CAN bus signal dominant state signal voltage levels and check that the level meet the specifications. |
Observe the scope data should be in the below ranges. 1. VCAN_H > 3.35V 2. VCAN_L < 1.4V 3. 1.95 < Voutput_diff < 5.25V |
7.4 Minimum and maximum power level for communication via bus |
To measure the minimum and maximum power voltage threshold for correct bus communication. |
The DUT must be able to transmit and receive messages in a power range equal to: 6V < Vsupply < 18V The DUT must resume communication on the bus when the power returns to ≥ 6.5 V. When the power returns to ≥ 6.5 V, the DUT must resume operation by Tinit |
7.5 Engine cranking power voltage curve |
To test whether the startup procedure is run correctly during voltage drops |
For devices which must be able to communicate during cranking: 1.After eliminating the interference and when power returns to ≥ 6.5V, the DUT must resume operation by TINIT ms. 2.After eliminating the interference and when power returns to ≥ 9V, the DUT must resume operation by TINIT ms. |
7.6 Bit rising edge and falling edge times |
To check whether the bit rising/falling edge times comply with Std. 07324 [HWCAN] considering the recessive-to-dominant transition. |
The measured time must be in the specified limit: 0.25 μs < Trise < 4.5 μs 0.25 μs < Tfall < 4.5 μs |
7.7 Signal features |
To check symmetry of both CAN bus signals in different physical load conditions. |
1. No asymmetric behavior or oscillations must occur 2. During the first half of the bit time, the bus output level must be comprised in the range from 81% to 150% of the DC value at the end of the bit. 3. During the second half of the bit time, the bus output level must be comprised in the range from 95% to 105% of the DC value at the end of the bit. 4. No asymmetric behavior or oscillations must occur 5. During the first half of the bit time, the bus output level must be comprised in the range from 81% to 150% of the DC value at the end of the bit. 6. During the second half of the bit time, the bus output level must be comprised in the range from 95% to 105% of the DC value at the end of the bit. |
7.8 Bit time precision during message transmission |
To measure the bit time precision during DUT message transmission on CAN bus. Note: The configured message should have maximum DLC and also fixed data bytes value as per specification. |
The maximum allowed oscillator deviation is 0.4%. |
7.9.1 Ground potential deviation immunity test - No anomalies |
To determine ground potential deviation immunity |
|
7.9.1 Positive Ground Offset |
Expose DUT to ground offset levels up to 4.5V |
The DUT must be running (the device must be capable of transmitting and receiving data) during the applied ground offset of 1.5V. The DUT is able to communicate via the bus without errors to Vgndoffset. |
7.9.1 Negative Ground Offset |
Expose DUT to ground offset levels up to -4.5V |
The DUT must be running (the device must be capable of transmitting and receiving data) during the applied ground offset of 1.5V. The DUT is able to communicated via the bus without errors to Vgndoffset. |
7.9.2 Ground potential deviation immunity test - Anomalies |
To determine ground potential deviation immunity. |
|
7.9.2 Pos Ofst CAN_L Open |
To determine ground potential when CAN_L is open (Pos Ofst) |
Observe the DUT at Vbat=13.5V. Expose DUT to ground offset levels up to 4.5V. |
7.9.2 Neg Ofst CAN_L Open |
To determine ground potential when CAN_L is open (Neg Ofst) |
Observe the DUT at Vbat=13.5V. Expose DUT to ground offset levels up to -4.5V. |
7.9.2 Pos Ofst CAN_H Open |
To determine ground potential when CAN_H is open (Pos Ofst) |
Observe the DUT at Vbat=13.5V. Expose DUT to ground offset levels up to 4.5V. |
7.9.2 Neg Ofst CAN_H Open |
To determine ground potential when CAN_H is open (Neg Ofst) |
Observe the DUT at Vbat=13.5V. Expose DUT to ground offset levels up to -4.5V. |
7.9.2 Pos Ofst CAN_L Short to Batt |
To determine ground potential when CAN_L is Short to Batt (Pos Ofst) |
Observe the DUT at Vbat=13.5V. Expose DUT to ground offset levels up to 4.5V. |
7.9.2 Neg Ofst CAN_L Short to Batt |
To determine ground potential when CAN_L is Short to Batt (Neg Ofst) |
Observe the DUT at Vbat=13.5V. Expose DUT to ground offset levels up to -4.5V. |
7.9.2 Pos Ofst CAN_H Short to Batt |
To determine ground potential when CAN_H is Short to Batt (Pos Ofst) |
Observe the DUT at Vbat=13.5V. Expose DUT to ground offset levels up to 4.5V. |
7.9.2 Neg Ofst CAN_H Short to Batt |
To determine ground potential when CAN_H is Short to Batt (Neg Ofst) |
Observe the DUT at Vbat=13.5V. Expose DUT to ground offset levels up to -4.5V. |
7.9.2 Pos Ofst CAN_L Short to Gnd |
To determine ground potential when CAN_L is Short to Gnd (Pos Ofst) |
Observe the DUT at Vbat=13.5V. Expose DUT to ground offset levels up to 4.5V. |
7.9.2 Neg Ofst CAN_L Short to Gnd |
To determine ground potential when CAN_L is Short to Gnd (Neg Ofst) |
Observe the DUT at Vbat=13.5V. Expose DUT to ground offset levels up to -4.5V. |
7.9.2 Pos Ofst CAN_H Short to Gnd |
To determine ground potential when CAN_H is Short to Gnd (Pos Ofst) |
Observe the DUT at Vbat=13.5V. Expose DUT to ground offset levels up to 4.5V. |
7.9.2 Neg Ofst CAN_H Short to Gnd |
To determine ground potential when CAN_H is Short to Gnd (Neg Ofst) |
Observe the DUT at Vbat=13.5V. Expose DUT to ground offset levels up to -4.5V. |
7.9.2 Pos Ofst CAN wires shorted |
To determine ground potential when CAN_H & L is Shorted (Pos Ofst) |
Observe the DUT at Vbat=13.5V. Expose DUT to ground offset levels up to 4.5V. |
7.9.2 Neg Ofst CAN wires shorted |
To determine ground potential when CAN_H & L is Shorted (Neg Ofst) |
Observe the DUT at Vbat=13.5V. Expose DUT to ground offset levels up to -4.5V. |
7.10.1 Short-circuit test |
To determine the robustness of the node short-circuited to battery and ground. |
|
7.10.1 CAN_L Short to +27V |
To determine the robustness of the node short-circuited to battery for CAN-L to +27V |
To check that the DUT does not cause communication interference and must not be damaged during the test. |
7.10.1 CAN_H Short to +27V |
To determine the robustness of the node short-circuited to battery for CAN-H to +27V |
To check that the DUT does not cause communication interference and must not be damaged during the test. |
7.10.1 CAN_L Short to 0V |
To determine the robustness of the node short-circuited to battery for CAN-L to 0V |
To check that the DUT does not cause communication interference and must not be damaged during the test. |
7.10.1 CAN_H Short to 0V |
To determine the robustness of the node short-circuited to battery for CAN-H to 0V |
To check that the DUT does not cause communication interference and must not be damaged during the test. |
7.10.1 CAN_L Short to -27V |
To determine the robustness of the node short-circuited to battery for CAN-L to -27V |
To check that the DUT does not cause communication interference and must not be damaged during the test. |
7.10.1 CAN_H Short to -27V |
To determine the robustness of the node short-circuited to battery for CAN-H to -27V |
To check that the DUT does not cause communication interference and must not be damaged during the test. |
7.10.2 CAN wires short-circuit test |
To determine failure tolerance in event of short-circuit between CAN wires. |
Observe the short-circuit between CAN wires for approximately 1 min. Check that the DUT maintains the communication up. |
7.10.3 Open circuit test |
To determine failure tolerance in the event of a CAN wire open circuit. |
|
7.10.3 Open ckt test CAN_L Open |
To determine failure tolerance in the event of a CAN-L wire open circuit. |
Observe the CAN L wire and leave it disconnected for 1 min and reconnected the CAN L wire. Observe the CAN H wire and leave it disconnected for 1 min. Check that the DUT maintains the communication up. |
7.10.3 Open ckt test CAN_H Open |
To determine failure tolerance in the event of a CAN-H wire open circuit. |
Observe the CAN L wire and leave it disconnected for 1 min and reconnected the CAN L wire. Observe the CAN H wire and leave it disconnected for 1 min. Check that the DUT maintains the communication up. |