LEMON Manuals: Even more car manuals for everyone: 1960-2025
Home >> Honda >> 2011 >> Insight Base >> Repair and Diagnosis >> Body & Frame >> Door Locks >> Immobilizer System >> Status Log
April 5, 2026: LEMON Manuals is launched! Read the announcement.

Status Log

If you suspect there is a immobilizer system problem, check the status log in the HDS.

  1. Connect the HDS to the data link connector.
  2. Turn the ignition switch to ON (II).
  3. On the HDS screen, at MAIN MENU, enter IMMOBI, then select IMMOBILIZER SET-UP, select System Check, Number of Keys and Status Log, then select STATUS LOG.
  4. Check the Status Log count. Troubleshoot the status with the highest count first. If no counts are listed, the immobilizer system is OK. Continue with normal symptom troubleshooting.
    STATUS CHART

    Status Log No. Detected Item Probable Cause
    A-1 KEY CODE MISMATCH (Code format normal, but code data is mismatch)
    • The key was not registered
    • Interference from metal such as key chains
    • Low battery voltage
    A-2 KEY CODE MISMATCH (Code format failure)
    • Ignition switch was turned to ON (II) with another type of immobilizer key or aftermarket key
    • Interference from metal such as key chains
    • Low battery voltage
    A-3 KEY CODE MISMATCH (No key code or non-immobilizer key)
    • Ignition switch was turned to ON (II) with another type of immobilizer key or aftermarket key
    • Interference from metal such as key chains
    • Low battery voltage
    • Key failure
    • Immobilizer-keyless control unit failure
    B-1 PCM CODE MISMATCH (Code format normal, but code data is mismatch)
    • PCM was not registered correctly
    • Low battery voltage
    • Poor or loose terminal connections at the immobilizer-keyless control unit
    • Communication line electrical noise
    B-2 PCM MISMATCH (Code format failure)
    • PCM was not registered correctly
    • Low battery voltage
    • Poor or loose terminal connections at the immobilizer-keyless control unit
    • Communication line electrical noise
    C-1 IMOES UNIT MISMATCH (Code format normal, but data is mismatch)
    • Imoes unit was not registered
    • The communication was not good between imoes unit and immobilizer unit because of low battery voltage
    • The communication was not good between imoes unit and immobilizer unit because of electrical interference
    C-2 IMOES UNIT MISMATCH (Code format failure)
    • Imoes unit was not registered correctly
    • The communication was not good between imoes unit and immobilizer unit because of low battery voltage
    • The communication was not good between imoes unit and immobilizer unit because of electrical interference
    D-1 IMOCD (S-NET) LINE PROBLEM IMOCD (S-NET) (Short to ground)
    • Low battery voltage
    • Poor or loose terminal connections at the immobilizer-keyless control unit and the PCM
    • Communication line electrical noise
    D-2 IMOCD (S-NET) LINE PROBLEM (No communication)
    • Blown fuse
    • Harness open from imoes unit to immobilizer unit
    • The communication was not good between imoes unit and immobilizer unit because of low battery voltage
    • The communication was not good between imoes unit and immobilizer unit because of electrical interference
    • Imoes unit failure
    • Immobilizer unit failure
    D-3 IMOCD (S-NET) LINE PROBLEM IMOCD (S-NET) (Open line or PCM failure)
    • Open or short in the harness from the PCM to the immobilizer-keyless control unit
    • Low battery voltage
    • Poor or loose terminal connections at the immobilizer-keyless control unit and the PCM
    • Communication line electrical noise
scientia non olet · About LEMON Manuals