Scribd Logo
Upload

Welcome to Scribd!

  • ISO 9141-3-1998.verification of The Communication Between Vehicle and OBD II Scan Tool PDF

    Uploaded by

    Parrex Parra
    249 views23 pages

    Original Title

    ISO 9141-3-1998.Verification of the communication between vehicle and OBD II scan tool.pdf

    Copyright

    © © All Rights Reserved

    Available Formats

    PDF or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Report this Document

    Copyright:

    © All Rights Reserved
    Download as PDF or read online from Scribd
    Flag for inappropriate content
    Download as pdf
    249 views23 pages

    ISO 9141-3-1998.verification of The Communication Between Vehicle and OBD II Scan Tool PDF

    Uploaded by

    Parrex Parra

    Copyright:

    © All Rights Reserved
    Download as PDF or read online from Scribd
    Flag for inappropriate content
    Download as pdf
    of 23
    iNTERNATIONAL Iso STANDARD 9141-3 First edition 1998-12-15 Road vehicles — Diagnostic systems — Part 3: Verification of the communication between vehicle and OBD II scan tool Véhicules routiers — Systémes de diagnostic — Partie 3: Vérification de la communication entre un véhicule et un outil d'analyse OBD I! Reference number (SO 9141-3:1998(E) ISO 9141-3:1998(&) Contents 1 Scope. 2 Normative references 3 Definitions and abbreviations .. 4 General 4,1 Test procedure overview. 4.1.4 Message structure test. 4.1.2 Initialization test. 4.1.3 Physical layer tes! 4.2 Test conditions 4.2.4 General test conditions. 4.2.2 Digital storage oscilloscope requirements. 4.2.3 Power supply requirement: 4.2.4 Network access device requirements.. 5 Message structure testernnnmnnn 5.1 Purpose. 5.2 Equipment... 5.3 Test Set-Up sien 5.4 Procedure 5.41-OBD Il scan tool. 5.4.2 Vehicle 6 Initialization test 6.1 Purpose. 6.2 Equipment 6.3 Test set-up © 150 1998 All sights reserved. Unless otherwise speciied, no part of this publication may be reproduced or uilized in any form or by any means, electronic ‘9r mecharical, including photocopying and eicroim, without permission in writing from the publisher. Intemational Organization for Standardization Case postale 66 « Ci#-1211 Geneve 20 « Switzerand Intemet iso@ico.ch Printed in Switzertand __ Annex E (informative) Bibliography ‘e1sO ISO 9141-3:1998(E) 6.4 Procedure. 6.4.1 OBD Il scan tool 6.4.2 Vehicle... 7 Physical layer test .. 7. Purpose .. 7.2 Equipment. 7.3 Procedure ww 7.3.1 OBD II sean tool 7.3.2 Vehicle . Annex A (normative) Test set-ups. Annex B (normative) Messages for use in verification test... Annex C (normative) Test parameter values. Annex D (normative) Network access device (NAD) — Minimum requirements, | | { ISO 9141-3:1998(E) ols Foreword 180 (the International Organization for Standardization) is a worldwide federation of national standards bodies (I¢ member bodies). The work of preparing Intemational Standards is normally carried out through ISO techni Committees. Each member body interested in a subject for which a technical committee has been established t the right to be represented on that committee. International organizations, governmental and non-governmental fiaison with ISO, also take part in the work. ISO collaborates closely with the International Electrotechn ‘Commission (IEC) on all matters of electrotechnical standardization. Dratt International Standards adopted by the technical committees are circulated to the member bodies for vot Publication as an International Standard requires approval by at least 75 % of the member bodies casting a vote. International Standard 1S09141-3 was prepared by Technical Committee ISO/TC 22, Road vehic Subcommittee SC 3, Electrical and electronic equipment. 1SO 9141 consists of the following parts, under the general tile Road vehicles — Diagnostic systems: — Part 2: CARB requirements for interchange of digital information — Part 3: Verification of the communication between vehicle and OBD Il scan too! NOTE — 1S0.141:1989, Road vehicles — Diagnostic systems — Requirements for interchange of digital informatior regarded as being part 1 of this International Standard. ‘Annexes A to D forrian integral part of this part of ISO 9141, Afinex E is for information only. INTERNATIONAL STANDARD ©1SO 180 9141-3:1998(E) ‘Road vehicles — Diagnostic systems — Part 3: Verification of the communication between vehicle and OBD II scan tool 1 Scope | | | This part of [SO 9141 establishes recommended test methods, test procedures and specific test parameters in | raario ety a vehicle or OBD I scan tool can communicate on a bus according to ISO 814-2, isnot applicable as atest fora single module or for any subpart of an ISO 9141-2 network. | “The test described is not provided to verily any tool or vehicle requirement not described in ISO 9141-2. In particular it does not check any requirement described in SAE J1962, SAE J1978, ISO 15031-6 or the expanded diagnostic protocol for scan tool The procedures and methods test a set of specific requirements applicable to all road vehicles and scan tools which make use of ISO 9141-2. 2 Normative references ‘The following standards contain provisions which, through reference in this text, constitute provisions of this part of 180.9141. At the time of publication, the editions indicated were valid. All standards are subject to revision, and parties to agreements based on this part of ISO 9141 are encouraged to investigate the possibilty of applying the most recent editions of the standards indicated below. Members of IEC and ISO maintain registers of currently valid International Standards. 180 9141:1989, Road vehicles — Diagnostic systems — Requirements for interchange of digital information. ISO 9141-2:1994, Road vehicles — Diagnostic systems — Part 2: CARB requirements for interchange of digital information, and its Amendment 1:1996. ISO 15031-5:—, Road vehicles — Emission-related diagnostics — Communication between vehicle and external equipment — Part 5: Emission-related ciagnostic services. SAE J1962:1995, Diagnostic Connector. SAE J1978:1994, OBD I! Scan Tool. 3 Definitions and abbreviations For the purposes of this part of ISO 9141, the definitions given in ISO 9141:1989 and the following abbreviations apply. DSO Digital storage oscilloscope 1) To be published. ALPE ED LED AL AARNE I Tat RL ND, f | else DUT Device under test NA Not applicable NAD Network access device PC Personal computer PID Parameter identifier PS Power supply 4 General 4.4 Test procedure overview Thee test procedures are identified to test ISO 9141-2 implementations. The following is a short synopsis of t! purpose of each of the tests. 4.1.1 Message structure test ‘The message structure test verifies that the DUT responds correctly to both correct and incorrect messagy generated by the NAD. This includes both the correct logical response and the correct response or reque message. 44.2 Ini jon test ‘The initialization test verifies that the DUT can complete the initialization sequence with correct timing and tha’ responds correctly to errors from the vehicle or the OBD II scan tool. 441.3 Physical layer test ‘The physical layer test verifies that the DUT shall receive and transmit data within physical parameter lirr specified in ISO 9141-2, 4.2 Test conditions 4.2.1 General test conditions ‘The maximum electrical vehicle load shall be as specified in ISO 9141:1989, ‘The tests shall be conducted when the DUT is stable within the operating range specified in ISO 9141-2:1994, € If a vehicle is being tested then it shall be stationary and with engine idling for the duration of the process unl: specified otherwise for an individual test. loscope requirements The DSO shall meet the following physical parameters: 20 pF maximum, 10 MQ minimum, 50 MHz minimum. 4.2.3 Power supply requirements ‘The PS shall be capable of supplying 5 A in a voltage renge between 0 V and 20 V. | ree $0 9141-3:7998(E .2.4 Network access device requirements The NAD shall be able to access and monitor the bus, display the initialization sequence and all messages. The IAD ig used to simulate the ISO 9141-2 behaviour of an OBD Il scan tool or a vehicle. For more information, refe jo annex D, fry roma be 10 wl ln po on sisig nd measur ing, ose an are Foie teis dosument accommocates the ronigeal NAD By adusin these lms according fo the tolerance of thy nD (NAO, see annex C), This adjustment necessary narrows the fange of acceptable DUT behaviour to preven la positive indication for a DUT that may fail in the field. ‘Conversely a good DUT may be rejected due to a large ANAD. For this reason it is recommended that a NAD i | elected which has the smallest ANAD. [5 Message structure test | | 5.1 Purpose ‘The message test verifies that the DUT transmits and interprets correctly messages whose structure and timing ar standardized in ISO 9141-2. Additionally, this test verifies that the DUT responds correctly to message structure © message timing errors. 5.2 Equipment — NAD, — Ps. 5.3 Test set-up — Connect the communication lines of the NAD to the DUT. figure At. |— If the DUT is an OBD Il scan tool, connect it as shown — Ifthe DUT is a vehicle, connect it as shown in figure A.2. — Set PS t0 13,5 V+05V. [5.4 Procedure [5.4.1 OBD II scan tool |e Message structure test | configure the NAD as a simulated vehicle with key bytes 08 08 and communication timing parameters P, = 10m P30 ms, Cause the sean tool 10 intialize the simulated vehicle, as described in ISO 9141-2:1994, clauses Ghd 7, Cause the OBD II scan tool to transmit a request message mode 1 PID 0 (request current powertrain date \Configure the NAD to respond withthe simulated vehicle response messages shown in table 1. Verity the OBC scan fool behaviour according to table 1 5.4.1.2 Message timing test Configure the NAD as a simulated vehicle with keybytes 08 08. Cause the scan tool to initialize the simulat vehicle, as in ISO 9141-2:1994, clauses 6 and 7. Cause the OBD II scan too! to transmit a request message mode PID 1 (request current powertrain data). Configure the NAD to respond with the simulated vehicle respon: message 48 6B D1 41 00 CB 4D 28 00 06 using the timing parameter values shown in table 2. Verify the OBC scan tool behaviour according to table 2. | 10 9141-3:1998(&) ° | | Table 1 — Message structure test for OBD II scan tool NAD r Reference Verification to wlated vehicle response message 1 (sien * se) ISO 9141-5 1994 Respond with correct message: Verity that the transmitted test message request on | Clauses + 48 6B D1 41 00 CB 4D 28.0006 (hex.) | the bus corresponds to the test message request | ang 12 as shown in annex B. Verify P, to be in range. Respond with incorrect checksum byte: | Verity that the OBDIl scan tool retransmits the| Subclaus 48 68 01 41 00.CB 40 28.0000 (hex.) _| original request message P, after the completion of| 13.2.1 Respond with incorrect tet header byte: |e last received byte (checksum byte). Verity Py to .| 49 6B D1 41 00. CB 4D 26 00 06 (hex), _|be in range between Pan) and Panes) — x %. Verity} that the OBD Il scan tool continues to retry for at Respond with incorrect length (to0 short): | east 1 min, 141 00 CB 4D 28 08 (hex. 48.680 Lis) NOTE—x% is not specified in ISOS141-2. It is| Subclav Respond with incorrect length (loo long): | recommended that x % is sot at least to 10% for this test.| 13.2.2 48 6B D1 41 00 CB 4D 28 00 0006 This is done io guarantee interoperability. (hex) Table 2 — Message timing test for OBD Il scan tool — NAD Verification Refer (simulated vehicle response message) tc Isos1 19% Respond with minimum P, period: Claus Py = Puen) id with maximum P, period: ; . A ANAD Verify that the OBD il scan tool received the response | Claus Pas Prax) message correctly, e.g. displays the message according | Respond with minimum P, period to ISO 18031-5 or displays the message at hex. level. [> Period: laus Pz = Protein) ANAD Respond with maximum P, perio cau Pa = Payminy + SNAD Respond with incorrect long P, period: | Verily that the OBD Il scan tool retransmits the original Py = Pony NAD request message P, after the completion of the last] Sube 1 tet received byte (checksum byte). Verify P, to be in range} 13 between Pygny ANd Pyne) 9%. Verify that the OBD II] 13.2 ‘scan tool continues to retry for atleast 1 min. 2 NOTE— x% Is not specified in ISO9141-2. It is Do not respond. recommended that x % is set atleast to 10 % for this test. This, is done to guarantee interoperability 5.4.2 Vehicle 5.4.2.1 Message structure test ‘Configure the NAD as a simulated OBD I! scan too! with communication timing parameters P, 60 ms, Pe Cause the simulated scan tool to initialize the vehicle, as described in ISO 9141-2:1994, clauses 6 and’7.” vehicle behaviour according to table 3 using the correct test message responses shown in annex B. Iso Table 3 — Message structure test for vehicle Iso 9141-3:1998(E NAD (simulated OBD II scan tool messages) Verification Reference to ISO 9141-2:1994 Transmit correct message: 68 6A Ft 01 00 C4 (hex.) Verify that vehicle responds with correct response message (see annex B). Verify that timings P, and P, are in range. Clauses 11 and 12 Transmit message with incorrect checksum byte: 68 6A F1 01 00 C5 (hex.) and 300 ms later with correct message Transmit message with incorrect length (too short): 68 6A Ft O1 C4 (hex.) and 300 ms later with correct message: 68 6A F1 01 00 C4 (hex.) Transmit message with incorrect length (too long): 68 6A F1 01 00 00 Ca (hex.) and 300 ms later with correct message: 68 6A F1 01 00 C4 (hex.) Verify that vehicle responds P, after the completion of the last byte of the correct, message. Subclause 13.2.1 Subclause 13.2.2 ‘Subclause 13.2.2 5.4.2.2 Message timing test Iso 9141: Table 4 — Message timing test for vehicle [Configure the NAD as a simulated OBD II scan tool. Cause the simulated scan tool to initialize the vehicle, as 1994, clauses 6 and 7. Cause the simulated OBD II scan tool to transmit a request messac 68 6A FI 01 00 C4 with the timing parameters given in table 4. Verily the vehicle behaviour according to table Using the correct test message responses shown in annex B. NAD (simulated BD Il scan tool messages) Verification Reference to ISO 9141-2:1994 ‘Transmit test message request with minimum Ps period: Ps = Pan ~ NAD. Transmit test message request with maximum P, period: P= Pagraxy + ANAD Transmit test message request with minimum Papetiod: Ps = Panny ~ NAD Verify that vehicle responds with correct, response message (see annex 8). Verify ‘that timing P, is in range. Transmit test message request with maximum P, period: Ps = Paynany + * % Clause 12 Clause 12 Clause 12 Clause 12 Transmit test message request with incorrect long P, period: P, = Pajaiay ~ ANAD and 800 ms later with correct P, period Verify that vehicle responds P, after the ‘completion of the last byte of the correct message. Subclause 13.2.3 Transmit test message request with incorrect] long Ps period: Py = Pao + % Vehicle shall not respond. Subclause 13.2.5, NOTE — 3 % is nol defined in ISO 9141-2. Itis recommended that x % shall not exceed 10 % for this test ISO 9141-3:1998() ols 6 Initialization test 6.1 Purpose ‘The initialization test verifies that the DUT handles correctly the initialization sequence and that it responds correc if errors occur in the sequence. 6.2 Equipment — NAD, — 2080. 6.3 Test set-up — Connect the communication ines of the NAD to the DUT. — Ifthe DUT is an OBD II scan tool, connect it as shown in figure A.1. — Ifthe DUT isa vehicle, connect it as shown in figure A.2. — Set PS1013,5V£0,5V. — Connect the DSO to K and L as shown in annex A. 6.4 Procedure 6.4.1 OBD Il scan tool ‘The NAD shall be set up to respond as shown in table 5. The OBD Il scan tool shall be set up as if just connecte the vehicle so as to cause itto start the initialization sequence, i.e. to send the address byte 33,.,. The parame to be measured are indicated in table 5. Note that the order of these tests is free but that the OBD I! scan tool have to be disconnected or reset following a successful initialization. eso ISO 9141-3:1998( ‘Table — Initialization timings and parameter settings NAD ven ertication | Referer (simulated vehicle behaviour) simulated vehicle response ree wy Syne Wy Kw Ws Kwe inv is0914 1 Addr 1998 08 Verity parameter ex cher. ex Wynn)” AAD Magny ~aNAD | PO ° Wena onan [OO"* | adarass, Bs, 8% Youn 55 98 VogrsayYnmy | Subctor hex hex 94 hex cchex| Many | S.tzclau 6.7an 08 Verity parameter Waggenn + NAD Weimar + SNAD | hex. | Wyjmany+ ANAD | 08Nex.| Wajney + ANAD |CChex.| KW2iv, Pa We (080 it scan tool) No action Wynn ~ BNAD ‘Stop transmission Stop transmission Verity that the * 8 (080 tt scan hex. ‘Stop transmission | ‘oeldossnot | sypctat revransmit the 131 ss 208 oa hex. actress bore 12x. | Wayen NAD | hex se n OMA | ex: ° ochex ime) Wing SNAD 8 18 | Warany~ ANAD hex hex. oshex. #00 hee. NOTE — The OBD I scan to! vetieation ofthe syns pattern i intentionally excluded from the lest 6.4.2 Vehit le — Configure the NAD to send the address 33;4, at BRyjaax) ON both the K- and Lline. — Capture the vehicle responses. Verify that there are three bytes. — Verify the time W, between the end of the address and the start of the first byte, the time W, between the and second bytes of the response and the time W, between the second and third bytes of the response. — Verify the values of the bytes are SYNC, KW1 and KW respectively. — Verify the values of the following parameters: Vgaay Vissi» Vinny Vimsey 8Te on the K-ling, BT, needs te within tolerance for each bit of the syne byte. — Set the NAD to allow 300 ms to elapse and then retransmit the address at BRygan, On both the K- and L-fines — Set the NAD to respond to the vehicle response by transmitting the inversion of the last value of the last byt the vehicle response Wana, after the end of the vehicle response. — Capture the vehicle responses. — Verity that the values of the bytes are SYNC, KW1, KW2. ISO 9141-3:1998(E) _— Verify the time W, between the end of the second NAD transmission and the subsequent vehicle response. Verify that the second vehicle response is a single byte. — Verity that the value is the inverted address. 7 Physical layer test 7A Purpose The physical layer test is to verity that the OBD I! scan tool or the vehicle reoeives and transmits at the phys layer parameters specified in ISO 9141-2. 7.2 Equipment — NAD, — 080, — Ps, — ampere meter. 7.3 Procedure 7.31 OBD I scan tool a) Resistance test Set up test equipment as indicated in figure 1. Verify the resistance to Vp of the K- and Liling, Rere by meast the voltage Von the DSO. Itis recommended that R, be 510.2. Verity Ru e1so ISO 9141-3:1998(E 2 i out i 16 : 7 i 050 8 ! CG fr De $ i ‘ : 6 : 8 : key 1. Connector according to SAE J1962 5 Signal GND 2 Unswitched va 6 Chassis GNO 3 Kline 7 Scan tool 4 Line 8 Repeat as Kane for Laine Figure 1 — Scan tool resistance test set-up b) Capacitance test Set up test equipment as indicated in figure 2. Verify the capacitance to signal GND of K-line, Cre. © pseasy Key 1 Connector accofding to SAE J1982. 2. Unswitched Vp 3 Kline 4 Signal generator 5 Signal GND 6 Chassis GND 7 Scan tool Figure 2 — Scan tool capacitance test set-up Verity that: T< Ryrenax * Cremsx: Js0 9141-3:1998(E) eIsc ¢) Voltage and rise time test Connect the equipment according to figure A.1. Configure the NAD to respond with the specific test response message given in table 8.1 with the settings given in the table 6. Cause the OBD I! scan tool to initialize the simulated vehicle, Force the OBD II scan tool to send mode 1 PID 0 (request current powertrain data) continuously Verify the values indicated by an "in the table are within the tolerances given in annex C and that the OBD Il sca: tool displays the correct response continually, throughout the test. Note that for each test the OBD II scan tool shall be reset and forced to reinitialize the NAD. Table 6 — Scan tool voltage and rise time test, settings NAD settings Scan tool measurements Test no fes| m |u| % Row Wu | The | The | BRre | Comms OK v BRosmay

    You might also like