Document ID: chunk:federal_register_of_legislation:F2011C00805:reg:11:p16
Version: federal_register_of_legislation:F2011C00805
Segment Type: reg
Provision Reference: reg 11 (pt 16/45)
Character Range: 462442–465537

sequential driving cycles during which the monitoring system responsible for activating the MI ceases to detect the malfunction and if no other malfunction has been identified that would independently activate the MI.

    3.8.  Erasing a fault code

         3.8.1.  The OBD system may erase a fault code and the distance travelled and freeze-frame information if the same fault is not re-registered in at least 40 engine warm-up cycles.

         3.9. Bi-fuelled gas vehicles

         3.9.1. For bi-fuelled gas vehicles, the procedures:
           –      activation of malfunction indicator (MI) (see paragraph 3.5. of this Annex);
           –      fault code storage (see paragraph 3.6. of this Annex);
           –      extinguishing the MI (see paragraph 3.7. of this Annex);
           –      erasing a fault code (see paragraph 3.8. of this Annex),
 shall be executed independently of each other when the vehicle is operated on petrol or on gas.  When the vehicle is operated on petrol, the result of any of the procedures indicated above shall not be affected when the vehicle is operated on gas.  When the vehicle is operated on gas, the result of any of the procedures indicated above shall not be affected when the vehicle is operated on petrol.

           Notwithstanding this requirement, the status code (described in paragraph 3.6. of this Annex) shall indicate fully evaluated control systems for both fuel types (petrol and gas) when the control systems are fully evaluated for one of the fuel types.

         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 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