Document ID: chunk:federal_register_of_legislation:F2012C00283:reg:7:p15
Version: federal_register_of_legislation:F2012C00283
Segment Type: reg
Provision Reference: reg 7 (pt 15/51)
Character Range: 545757–548951

diagnostic scan tool, the diagnostic signals shall be transmitted on one or more source addresses. The use of source addresses is described in ISO DIS 15031-5 "Road vehicles - communication between vehicles and external test equipment for emissions-related diagnostics – Part 5: Emissions-related diagnostic services", dated 1 November 2001.
              3.9.3.2. Identification of fuel specific information can be realized:
               (a) By use of source addresses; and/or
               (b) By use of a fuel select switch; and/or
               (c) By use of fuel specific fault codes.
              3.9.4. Regarding the status code (as described in paragraph 3.6. of this annex), one of the following two options has to be used, if one or more of the diagnostics reporting readiness is fuel type specific:
               (a) The status code is fuel specific, i.e. use of two status codes, one for  each fuel type;
               (b) The status code shall indicate fully evaluated control systems for both  fuel types (petrol and (NG/biomethane)/LPG)) when the control               systems are fully evaluated for one of the fuel types.
               If none of the diagnostics reporting readiness is fuel type specific, then only one status code has to be supported.
              4. Requirements relating to the type-approval of on-board diagnostic systems
              4.1. A manufacturer may request to the authority that an OBD system be accepted for type-approval even though the system contains one or more deficiencies such that the specific requirements of this annex are not fully met.
              4.2. In considering the request, the authority shall determine whether compliance with the requirements of this annex is infeasible or unreasonable.
               The Approval Authority shall take into consideration data from the manufacturer that details such factors as, but not limited to, technical feasibility, lead time and production cycles including phase-in or phase-out of engines or vehicle designs and programmed upgrades of computers, the extent to which the resultant OBD system will be effective in complying with the requirements of this Regulation and that the manufacturer has demonstrated an acceptable level of effort towards compliance with the requirements of this Regulation.
              4.2.1. The authority will not accept any deficiency request that includes the complete lack of a required diagnostic monitor.
              4.2.2. The authority will not accept any deficiency request that does not respect the OBD threshold limits in paragraph 3.3.2.
              4.3. In determining the identified order of deficiencies, deficiencies relating to paragraphs 3.3.3.1., 3.3.3.2. and 3.3.3.3. of this annex for positive-ignition engines and paragraphs 3.3.4.1., 3.3.4.2. and 3.3.4.3. of this annex for compression-ignition engines shall be identified first.
              4.4. Prior to or at the time of type-approval, no deficiency shall be granted in respect of the requirements of paragraph 6.5., except paragraph 6.5.3.4. of Appendix 1 to this annex.
              4.5. Deficiency period
              4.5.1. A deficiency may be carried-over