Document ID: chunk:federal_register_of_legislation:F2024L00446:reg:13:p9
Version: federal_register_of_legislation:F2024L00446
Segment Type: reg
Provision Reference: reg 13 (pt 9/23)
Character Range: 1967446–1970609

paragraph 6.5.3.2.(a) of Appendix 1 to this annex.

              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.

              3.10. Additional provisions for vehicles employing engine shut - off strategies.

              3.10.1. Driving cycle

              3.10.1.1. Autonomous engine restarts commanded by the engine control system following an engine stall may be considered a new driving cycle or a continuation of the existing driving cycle.

              4. Requirements relating to the type approval of on-board diagnostic systems

              4.1. A manufacturer may request to the Type Approval 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. The Type Approval Authority may approve up to two separate components or systems with one or more deficiencies.

               When a manufacturer adopts specific conditions for misfire defined in paragraph 3.3.3.2.1. of this annex, these conditions shall not be considered as a deficiency.

              4.2. In considering the request, the Type Approval Authority shall determine whether compliance with the requirements of this annex is infeasible or unreasonable.

               The Type 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 Type Approval Authority shall not accept any deficiency request that includes the complete lack of a required diagnostic monitor or the lack of mandated recording and reporting of data related to a monitor.

              4.2.2. For Level 1A

              The Type Approval Authority will not accept any deficiency request that does not respect the OBD thresholds set out in paragraph 6.8.2. of this Regulation.

              For Level