Japan’s proposal for EPPR-16-05 （OBD GTR_CLEPA comments on draft 2016-03-09.doc） 25/Apr/ 2016 JAPAN AUTOMOBILE STANDARDS INTERNATIONALIZATION CENTER http://www.jasic.org

Definition of three wheeler in Scope II.　 Text of the global technical regulation 　　　2. Scope and application P10 OBD Evap Scope and application Scope and application Two- and three-wheeled vehicles equipped with a propulsion unit in accordance with Table 1. Two- and three-wheeled vehicles of category 3 *1 equipped with a PI engine in accordance with Table 1: [Contracting Parties are requested to consider the details of this UN gtr while enacting national/regional regulations for OBD for other vehicles of category 3.] Footnote *1 ECE/TRANS/WP.29/1045, as amended by Amends. 1 and 2 Japan comment: Japan proposes to align the scope and application with the Evap GTR. Justification: It is more preferable to align the scope with the preceding new Evap GTR for L category.

General requirement(5.2.2.6) CLEPA 5.2.2.6. The OBD system shall record diagnostic trouble code(s) indicating the status of the control system. Separate status codes shall be used to identify correctly functioning control systems and those control systems which need further vehicle operation to be fully evaluated. If the MI is activated due to malfunction or permanent default modes of operation, a diagnostic trouble code shall be stored that identifies the type of malfunction. A diagnostic trouble code shall also be stored in the cases referred to in point 3.11. in Annex 1. CLEPA proposed to change the reference to 5.2.2.3 IMMA 5.2.2.6. The OBD system shall record diagnostic trouble code(s) indicating the status of the control system. Separate status codes shall be used to identify correctly functioning control systems and those control systems which need further vehicle operation to be fully evaluated. If the MI is activated due to malfunction or permanent default modes of operation, a diagnostic trouble code shall be stored that identifies the type of malfunction. A diagnostic trouble code shall also be stored in the cases referred to in point 5.2.2.3.3.   In EPPR-14-14, JPN proposed to change the reference to 3.11 of Annex 1, but the original reference to point 5.2.2.3.3. in EPPR-14-06 by IMMA was correct. Japan comment: Support the original proposal by IMMA Justification: See the next page

General requirement(5.2.2.6) Code shall also be stored in the cases referred to in point XX. →Situation for code storage should be described in point XX. Proposed by Referred point Summary of referred point Comment JAPAN EPPR-14-14 3.11 When a fault is registered, the manufacture shall identify the fault using an appropriate diagnostic trouble code consistent with those in section 6.3 of ISO 15031-6:2010 3.11 should describe situation for code storage. However, it describes method to identify trouble code. Proposal of JASIC seems inappropriate. IMMA EPPR-14-06 5.2.2.3.3 Electronic components shall be continuously monitored for any electric continuity failure, shorted circuits, stuck signal of control. No contradiction in expression is found. CLEPA orally proposed during the Telecon on 18 Apr 2016 5.2.2.3 In addition to IMMA proposal … Scope of monitoring and etc. are included. 5.2.2.3 should simply describe situation for code storage. However, it also mentions irrelevant issues such as scope of monitoring and etc. Proposal of CLEPA seems inappropriate.