Number P0513: Incorrect Immobilizer Key
The engine module receives a secret code from the immobiliser or body module (Chrysler SKIM/SKREEM/RF hub, Saab CIM); if it does not match the stored code, P0513 sets and starting is prevented – Saab cuts fuel and blocks the starter. The most common trigger is a replaced or reflashed engine module t
Can you drive with P0513?
Severity: Plan the repair. Generally yes for normal driving while you arrange the repair, unless symptoms say otherwise.
If you ignore it: Small faults in monitored systems tend to grow; the code will also block an emissions pass in most states.
This is the #109 most common code in our top-150 library, in the idle & throttle control family (Powertrain system). Severity is Number Nest's editorial triage — if the light is flashing or the car feels unsafe, stop driving it whatever any page says.
What P0513 means
The engine module receives a secret code from the immobiliser or body module (Chrysler SKIM/SKREEM/RF hub, Saab CIM); if it does not match the stored code, P0513 sets and starting is prevented – Saab cuts fuel and blocks the starter. The most common trigger is a replaced or reflashed engine module that was not taught to the immobiliser (FCA, Saab), less often handshake timing on FCA hybrids or a key not programmed. FCA lists it as invalid SKIM key. It is not emission-related; CARB does not require immobiliser monitoring, and no source documents a warning lamp.
Systems involved: immobilizer module, transponder key, engine control module (ECM/PCM).
Causes, ranked by likelihood
| # | Cause | Likelihood |
|---|---|---|
| 1 | Engine module replaced or reflashed and not taught to the immobiliser | most likely |
| 2 | Key or transponder not programmed or faulty | possible |
| 3 | Immobiliser, body or RF hub module replaced or faulty | possible |
| 4 | Software fault in the handshake | less common |
Check them in order — the list is ranked so the likely, cheaper causes come before the expensive part.
Symptoms you may notice
- Engine does not start or stops after 1–2 s
- Immobiliser or security lamp flashes
- Starter does not crank (Saab)
Misdiagnosis traps
- Replacing the part named by the code title without testing. The code reports a failed self-test; the cause list above is ranked so the likely, cheap causes are checked before the expensive part is condemned.
- Clearing the code and declaring victory when the light stays off for a day — the monitor that sets this code runs only under specific driving conditions.
(General diagnostic guidance for this code family — no code-specific trap is published for this code.)
How a good shop confirms it
- Confirm the code and record any companion codes — companions narrow the system fast.
- Inspect the affected components and their wiring/connectors for damage, corrosion and looseness.
- Test the top-ranked cause with live data or a multimeter before replacing anything.
(Standard diagnostic path for this family, labeled as general guidance.)
Repair options & costs
| Repair | Shop total (parts + labor) | DIY (parts only) | Difficulty |
|---|
No single repair is costed for this code — the fix follows the diagnosis. The Repair Cost Estimator prices 28 common repairs once you know which one this is.
OBDex repair data for this code rates the job difficulty hard with a typical labor time in the 0.5–2 hour range and DIY possible: see the guide above.
Frequently asked questions
How much does it cost to fix P0513?
There is no single fix — the code names a system, and the cost follows whichever cause on the ranked list proves out. The Repair Cost Estimator prices the common repairs in that system; diagnosis (often $100–$180, frequently credited) comes first.
Can I drive with P0513?
See the can-you-drive verdict above — it is based on the system involved and the cascading-damage risk, and it is our editorial triage, not a manufacturer instruction. If the light is flashing or the car feels unsafe, stop driving it regardless of any code.
Will P0513 clear itself?
If the fault was a one-off (a loose cap, a cold-start glitch), the light can go out after several clean trips and the code ages into history. A fault that is still present re-sets the code as soon as the car runs that self-test again — monitors run under specific conditions, which is why "it hasn't come back in two days" is not proof of a fix.
Will my car fail inspection with P0513?
In states with OBD-based emissions inspection, yes — an illuminated check-engine light or an incomplete readiness monitor fails the test regardless of what the tailpipe would show. C-codes (ABS) fall under safety inspection instead in states that have one.
What should I check first for P0513?
The first item on the ranked-causes list above — it is ranked likelihood-first for exactly this reason — plus the free checks: recent work in the area (connectors left loose are a classic), fluid levels, and the battery and grounds on electrical codes.
Where this data comes from
Code facts, causes and symptoms come from OBDex — an open dataset of independently authored descriptions of the standardized generic OBD-II codes (CC0 1.0, public domain; github.com/foerbsnavi/OBDex). The SAE J2012 document itself is copyrighted and is not reproduced here. Cost ranges are Number Nest's own US planning model: national parts and labor ranges cross-checked against the CarMD Vehicle Health Index 2026 published averages, with labor adjustable by the BLS OEWS May 2025 state wage index for auto technicians (occupation 49-3023) — a wage index, not a surveyed shop rate. Severity and can-you-drive notes are our editorial triage, not a manufacturer instruction.