NATS (Nissan Anti-Theft System) / Gasoline engine — Trouble Diagnoses — Work Flow (Supplement-VII)
EL-7062flowchartNATS troubleshooting workflow. ALL KEYS required for initialization. Two distinct CONSULT-II program cards used: NATS-specific (AEN00A) for IMMU diagnostics, generic for engine ECM diagnostics. Loop-backs handle NG paths.
Trouble Diagnoses
WORK FLOW
NATS trouble diagnosis flow
1
CHECK IN
2
Listen to customer / request ALL KEYS
3
TROUBLE / KEY SERVICE REQUEST
KEY SERVICE REQUEST (initialization branch)
return to step 5
TROUBLE
4
Verify the security indicator
5
Use CONSULT-II program card for NATS — read SELF-DIAG RESULTS
6
NATS-only OR NATS+DON'T-ERASE-BEFORE-CHECKING-ENG-DIAG?
NATS+DON'T-ERASE
Check engine SELF-DIAG RESULTS via CONSULT-II generic program card
Check engine SELF-DIAG RESULTS via CONSULT-II generic program card
Repair engine control system (refer to EC section) for non-NATS DTCs
Engine starts properly?
NATS-only
7
Repair NATS (optionally C/U INITIALIZATION)
8
Erase NATS SELF-DIAG RESULTS via CONSULT-II 'ERASE'
9
Start the engine
10
Security indicator stays off?
NG (loop back)
return to step 5
OK
CHECK OUT
WARNING
Always collect ALL KEYS from owner before starting NATS diagnosis. Re-initialization wipes all registered IDs — without all the original keys, the customer leaves with an unstartable car. Note on 'CHAIN OF ECM-IMMU' false positive: this can be stored during a normal key-registration procedure even if nothing is broken; don't chase it as a fault if it appears immediately after a registration session.