1、 M16 PHEV Project Data: Page1 Physical Layer Test Procedures for High Speed CAN V1.3 M16 PHEV Editor： Auditing： Authorize： Revision: 1.3 M16 PHEV Project Data: Page2 Document updates and issue history This document can be revised and appear in several versions. The document will be classified in ord
2、er to allow identification of updates and versions. Document status classification The document is assigned the status Outline, Draft or Issue. It will have the Outline status during the initial phase when parts of the document are not yet written. The Draft status is entered when a complete documen
3、t is ready, which can be submitted for reviews. The draft is not approved. The draft status can appear between issues, and will in that case indicated together with the new issue number E.g. Draft Issue 2.An Issue is established when the document is reviewed, corrected and approved. Version number a
4、nd history procedure Each issue is given a number and a date, and a history record shall be kept over all issues. Document in Outline and Draft status shall not have a history record. M16 PHEV Project Data: Page3 INDEX Document updates and issue history . 2 Document status classification . 2 Version
5、 number and history procedure . 2 1. Introduction 4 2. Document reference 4 3. Acronyms . 4 4. Modification history 4 4.1. Revisions Modified the Revision Number according to the numbering rule; Modified the power supply requirement in the 6th paragraph; Deleted the “software completeness percentage
6、” of ECU information in the 7th paragraph; Deleted the test report links; Modified the Terminal Resistances tolerance according to CAN Hardware Specification; Moved the test 15、 16、 17 into the 9th paragraph， and exchanged their sequence; Added VCANH+CANL test, referring to test3 for details; Modifi
7、ed the DtRt and RtDt time range of Testcase#4_2, referring to test4 for details; Added bit time test, referring to test17 for details. 5. Application range The tests described in this document can be carry out on any electronic control unit fitted with a CAN controller and are designed to test the h
8、igh speed network physics layer. M16 PHEV Project Data: Page6 6. Test Requipment Following instrumentation is necessary in order to perform all the test procedures included in this document: Power Supply +VBAT: Direct current power supply with voltage adjustable between 0 and 30V and enough power fo
9、r the current draw of the entire system under test. +VBAT = + 13.5 VDC when there is no otherwise specified. CAN network Analyzer (for example): CAN V2.0 B 2 High Speed channel ISO/DIS 11898 Baud rate up to 500 kbps Max bus load 100% Error frame detection capability Oscilloscope: 2 channels Input im
10、pedance: 1 M, 20pF Bandwidth: 60 MHz Sampling rate: from 5 S/s to 1 GS/s Accuracy DC: 3% Calibrated instrument Acquisition mode: continuous, continuous with persistency (envelope) CAN Scope: CAN Interface Trigger In/Out RS-232(PC Interface) 9-18V DC(Power Supply Interface) Fault Section:( Figure 1：
11、Fault Section) Special tool having manual or automatic switching capability. V1: DC adjustable generator used to generate ground shift. Voltage range: 5 VDC. Max. Current: 2 times nominal ECU Under Test current. (In APPENDIX A is suggested one of the many possible solutions in order to realize V1 ge
12、nerator). M16 PHEV Project Data: Page7 + V B A T+ V B A TS W 1 0+V1S W 1 112S W 6S W 312S W 812S W 5SW12S W 712S W 9S W 412F A U L T S E C T I O NFigure 1： Fault Section Load Sections:(Figure 2:Load Sections) Special tool having manual or automatic switching capability R3 and R4 resistors are used i
13、n order to simulate the resistance of the bus cable, assuming that: R3 = R4 = x L = 100exp-3 x 25 = 2.5 3 Where : = specific resistance per length unit = 100 m/mL = max length of the bus line = 25 m C2 and C3 capacitors are used in order to simulate capacitance of the bus cable, assuming that: C2 =
14、C3 = c x L = 150exp-12 x 25 = 3.75 nF 3.9 nF where: c = specific capacitance per length unit = 150pF/m L = max length of the bus line = 25 m R5 resistor and C4 capacitor are used to simulate the input impedance of the whole network, when maximum allowable number of nodes is implemented. R5 = Rdiff /
15、 (n-3) = 20,000 / (16-3) = 1,538 1.5 k where: Rdiff = minimum differential input resistance of a generic receiving node = 20 k (n-3) = max number of nodes, excluding 3 nodes already present in the test set. C4 = (n-3) x Cdiff = (16-3) x 10exp-12 = 130 pF 150 pF where: Cdiff = maximum differential in
16、put capacitance of a generic receiving node = 10 pF (n-3) = max number of nodes, excluding 3 nodes already present in the test set. M16 PHEV Project Data: Page8 Figure 2: Load Sections 7. ECU Information and State The description of the ECU Information: Electronic control unit type (e.g. engine cont
17、roller, body computer, etc.). Supplier name. Hardware version. Software version. Reference message map document. FIF used as a reference. The description of the ECU State: How significant the tested components are, depending on the hardware prototype level (A, B, C) . Note : The definition of the ha
18、rdware level : Prototype A ECU with components possibly not definitive and not manufactured on a production line. Prototype B ECU with definitive components and not manufactured on a production line. Prototype C ECU with definitive components and manufactured on a production line. The engineer who i
19、s running the tests should fill out these information in the test report. 8. Test layout R1 60 SW1 R2 60 SW2 C1 100nF R7 60 SW17 SW14 SW16 C3 3,9nF R5 1.5K R3 3 SW13 C2 3,9nF C5 100nF R6 60 C4 150pF SW15 R4 3 LOAD SECTION ECU SIDE LOAD SECTION ANALYZER SIDE M16 PHEV Project Data: Page9 Using the ins
20、trumentation described in the previous paragraph, is necessary to prepare a test layout as in the following schematics (Figure 3 Test layout). This layout will be common to the entire test procedures described in the following paragraphs. Figure 3 Test layout NOTE: Pay particular attention to correc
21、tly connect Ground References of CAN Analyzer. If the tool is supported by Laptop/PC, connect both Ground Reference of PC and Ground Reference of transceivers to GND via a wire of at least 1.0mm2 cross-sectional area. During the V1 regulation, dont care if error frames occur and wait some seconds fo
22、r allowing stable conditions. The Error Frames presence, after moving the switches of the fault section, must be analyzed only after the switch has firmly reached the new stable position (Normal Open or Normal Close). 9. Physical Layer test procedures Physical layer test procedures for High Speed CA
23、N interface are to be applied to all the Electronic Control Units equipped with such interface in order to verify that interface is compliant with specification 1 and 2. All the procedures described in the document take in consideration the single ECU, not the whole vehicle network. During the test,
24、 the ECU will be connected to instrumentation and proper circuits that will be able to simulate the rest of the network and that will be able to create repeatable fault conditions. 9.1. Test1: Terminal Resistance Purpose of test case#1_1 is to verify the terminal resistance value defined by chery. +
25、VBAT +VBAT SW16 R6 60 C5 100nF R7 60 SW17 R3 3 R4 3 SW14 SW13 SW10 OSCILLOSCOPE CH 1 CH 2 GND REF R5 1.5K SW15 R1 60 SW1 SW9 C4 150pF SW8 1 2 SW7 1 2 SW2 R2 60 CAN ANALYZER CAN1-H CAN1-L GND REF CAN2-H CAN2-L SW12 C1 100nF ECU UNDER TEST VBAT CAN-H CANL GND SW4 1 2 SW3 1 2 SW11 1 2 SW5 SW6 + V1 C3 3
26、,9nF C2 3,9nF FAULT SECTION LOAD SECTION ECU SIDE LOAD SECTION ANALYZER SIDE M16 PHEV Project Data: Page10 9.1.1 Test procedure TEST CASE#1_1 1. Disconnect the battery of the ECU UNDER TEST. 2. Connect a multimeter between CANH and CANL lines to measure the resistance, which is called RL. 3. the val
27、ue must meet :119.6 RL 122 (RL rating value is 120.8). 9.2. Test 2: C-CAN communication, normal operating mode Purpose of this test is to perform a verification of the ECU capability to exchange CAN frames on High Speed CAN bus under normal operating mode (no failures). Moreover, this test allows to
28、 verify that ECU UNDER TEST and test layout used also in the following more specific tests are correctly connected and all the setup is working. Two test cases are performed in order to take in consideration a simple network just loaded by ECU under test and 2 channel analyzer (Test Case # 2_1) and
29、a network with the maximum number of allowable ECUs, maximum cable length, plus 2 channel analyzer (Test Case # 2_2). These two conditions represent the two boundaries where the ECU under test could work, when inserted in different vehicle networks. 9.2.1 Test procedure TEST CASE # 2_1: 1. Set V1 ge
30、nerator: switched OFF. 2. Set switches accordingly to the following tables: SWITCH SW3 SW4 SW5 SW6 SW7 SW8 SW9 SW10 SW11 SW12 POSITION 1 1 CC CC 1 1 CC CC 1 OC SWITCH SW1 SW2 SW13 SW14 SW15 SW16 SW17 POSITION CC CC CC CC OC CC CC 3. If ECU UNDER TEST is provided with internal termination network, op
31、en switches SW1 and SW2. 4. Connect power supply +VBAT. 5. Using simulation capabilities of CAN Analyzer, establish a traffic on CAN network with a minimum bus load of 20%. Use two channels in order to simulate real conditions: more than one ECU active on the network. 6. Verify that frames periodica
32、lly issued by ECU UNDER TEST are present on CAN network. 7. Verify that no error frames conditions happen on CAN network in a period of 1 minute. 8. Verify that all the signals received from CAN Analyzer represent the ECU transmitted pattern correctly. 9. Stop measurement, disconnect power supply +V
33、BAT. TEST CASE # 2_2: 1. Set V1 generator: switched OFF. 2. Set switches accordingly to the following tables: SWITCH SW3 SW4 SW5 SW6 SW7 SW8 SW9 SW10 SW11 SW12 POSITION 1 1 CC CC 1 1 CC CC 1 OC M16 PHEV Project Data: Page11 SWITCH SW1 SW2 SW13 SW14 SW15 SW16 SW17 POSITION CC CC OC OC CC CC CC 3. If
34、ECU UNDER TEST is provided with internal termination network, open switches SW1 and SW2. 4. Connect power supply +VBAT. 5. Using simulation capabilities of CAN Analyzer, establish a traffic on CAN network with a minimum bus load of 20%. Use two channels in order to simulate real conditions: more tha
35、n one ECU active on the network. 6. Verify that frames periodically issued by ECU UNDER TEST are present on CAN network. 7. Verify that no error frames conditions happen on CAN network in a period of 1 minute. 8. Verify that all the signals received from CAN Analyzer represent the ECU transmitted pa
36、ttern correctly. 9. Stop measurement, disconnect power supply +VBAT. 9.3. Test 3: C-CAN output bus voltage levels, normal operating mode Purpose of this test is to verify that during normal operating mode, CANH and CANL lines voltage levels ， and differential bus voltage between CANH and CANL lines
37、， and the sum voltage levels of CANH and CANL， are compliant with specifications 1 and 2 , both during recessive and dominant conditions. Two test cases are performed in order to take in consideration a simple network just loaded by ECU under test and a 2 channels CAN analyzer (Test Case # 3_1) and
38、a network with maximum number of allowable ECUs, maximum cable length, plus a 2 channels CAN analyzer (Test Case # 3_2). These two conditions represent the two boundaries where the ECU under test could work, when inserted in different vehicle networks. 9.3.1 Test procedure TEST CASE # 3_1: 1. Set V1
39、 generator: switched OFF. 2. Set switches accordingly to the following tables: SWITCH SW3 SW4 SW5 SW6 SW7 SW8 SW9 SW10 SW11 SW12 POSITION 1 1 CC CC 1 1 CC CC 1 OC SWITCH SW1 SW2 SW13 SW14 SW15 SW16 SW17 POSITION CC CC CC CC OC CC CC 3. If ECU UNDER TEST is provided with internal termination network,
40、 open switches SW1 and SW2. 4. Connect power supply +VBAT. 5. Using analyzing capabilities of CAN Analyzer, establish a minimum traffic on CAN network, where just messages generated by ECU UNDER TEST are present. 6. Set the oscilloscope in order to visualize CANH 、 CANL and CANdiff、 CANH+CANL signal
41、s on the same screen with suitable precision； 7. Acquire signals for a time not less than two seconds, using “persistency” function. M16 PHEV Project Data: Page12 8. Verify that the envelopes of voltage levels of CANL 、 CANH、 CANdiff and CANH+CANL lines during dominant condition are always inside th
42、e grey boundaries indicated in the figure4、 figure6 and figure7. 9. Verify that the envelopes of voltage levels of CANL 、 CANH、 CANdiff and CANH+CANL lines during recessive condition are always inside the grey boundaries indicated in the figure5、 figure6 and figure7. 43210C A N - LC A N - HR E C E S
43、 S I V ED O M I N A N TR E C E S S I V E4 , 5 V5V0 , 5 Vt2 , 2 5 V2 , 7 5 VFigure4、 VCANH、 VCANL of dominant bit 43210C A N - LC A N - HD O M I N A N TR E C E S S I V E5V2 , 0 VD O M I N A N T3 , 0 VtFigure5、 VCANH、 VCANL of recessive bit 312VR E C E S S I V E D O M I N A N T-10R E C E S S I V E D O
44、 M I N A N T5 0 m V- 0 , 5 V+ 1 , 5 V+ 3 , 0 VtFigure6、 VCANdiffof dominant and recessive bit M16 PHEV Project Data: Page13 t0123564 . 2 V5 . 8 VVC A N H + C A N L4VFigure7、 VCANH+CANL of dominant and recessive bit 10. Stop measurement, disconnect power supply +VBAT. TEST CASE # 3_2: 1. Set V1 gener
45、ator: switched OFF. 2. Set switches accordingly to the following tables: SWITCH SW3 SW4 SW5 SW6 SW7 SW8 SW9 SW10 SW11 SW12 POSITION 1 1 CC CC 1 1 CC CC 1 OC SWITCH SW1 SW2 SW13 SW14 SW15 SW16 SW17 POSITION CC CC OC OC CC CC CC 3. If ECU UNDER TEST is provided with internal termination network, open
46、switches SW1 and SW2. 4. Connect power supply +VBAT. 5. Using analyzing capabilities of CAN Analyzer, establish a minimum traffic on CAN network, where just messages generated by ECU UNDER TEST are present. 6. Set the oscilloscope in order to visualize CANH 、 CANL and CAN-diff、 CANH+CANL signals on
47、the same screen with suitable precision. 7. Acquire signals for a time not less than two seconds, using “persistency” function. 8. Verify that the envelopes of voltage levels of CANL 、 CANH、 CANdiff and CANH+CANL lines during dominant condition are always inside the grey boundaries indicated in the figure4、 figure6 and figure7. 9. Verify that the envelopes of voltage levels of CANL 、 C
