P1610
LOCK MODESystem Description
IVIS (Infiniti Vehicle Immobilizer System - NATS) will immobilize the engine if someone tries to start it with- out the registered key of IVIS (NATS). Only IVIS (NATS) ignition keys with ID numbers that have been registered into the ECM and the IMMU allow the engine to run.
A malfunction that triggers this code may turn the security indicator ON to make the engine hard to start. If the security indicator illuminates with the ignition key ON or the engine running, it may indicate that there is an abnormality in the system. For this condition perform SELF DIAGNOSIS.
It is normal for the security indicator to blink when the ignition switch is in OFF or ACC.
IVIS (NATS) trouble diagnoses, system initialization and additional registration of other IVIS (NATS) ignition key IDs must be carried out using CONSULT-II hardware and CONSULT-II IVIS (NATS) software.
On Board Diagnostic Logic
When the starting operation is carried out five or more times consecutively under the following conditions, IVIS (NATS) will shift the mode to one which prevents the engine from being started.
- Unregistered ignition key is used
- IMMU or ECM malfunction
Possible Cause
- Use of unregistered ignition key
- Malfunctioning ignition key
- IMMU
- ECM
Diagnostic Repair Procedure
1. Perform SELF DIAGNOSIS results with CONSULT-II. Confirm LOCK MODE is displayed on CONSULT-II screen.
2. Escape from LOCK MODE: Perform steps a to e.
a. Turn ignition switch OFF.
b. Turn ignition switch ON with registered key. (Do not start engine.) Wait 5 seconds.
c. Return the key to OFF position.
d. Repeat steps 2 and 3.
e. Start engine. If engine start, system is escaped from LOCK MODE.
3. If engine cannot start in step 2, check IMMU installation.
4. Perform initialization with CONSULT-II and re-register all IVIS (NATS) ignition key IDs.
5. If initialization is not completed or fails, CONSULT-II displays INITIALIZATION FAIL: Perform steps a-b.
a. Check IVIS (NATS) ignition key ID chip:
Attempt to start the engine with any of the other registered IVIS (NATS) ignition keys. If the engine starts, replace non-functional key and perform initialization with CONSULT-II. Reregister all IVIS (NATS) ignition key IDs.
b. Check IMMU installation.
6. If IMMU installation is OK, IMMU is malfunctioning. Perform the following.
a. Replace IMMU.
b. Perform initialization.
Symptom Matrix Chart