Key Code Lockout

[zzsteve]

Replaced the P38 (MY1995) battery after using it to jump start another vehicle and now have Key Code Lockout on message centre. Pressing key fob does nothing. Battery has good charge.
Fob sync with BECM has also failed as I can't re-sync using the key in door, unlock and lock procedure.
Probably related is that the Nanocom evo also now fails to communicate with ECU (BECM). Sounds bad, now that write it all down! I'll start by checking BECM fuses, but can't see how a simple battery in/out could cause such a catastrophe.
TIA
Steve

PS: Fob flashes with both buttons, batteries OK

[TheTree]

Hi Mate

Do you have your EKA code? That's probably what you need

Steve

[zzsteve]

Was led to believe that '95 didn't have an EKA code implemented.

[TheTree]

I think they all had EKA but some other stuff was added through the years

It might be worth trying one of the generic codes mentioned here

Security and Alarm System Operation & Diagnosis on Range Rover 4.0/4.6/P38A (http://www.rangerovers.net/repairdetails/becm/alarm.html)

Steve

[Rupert Prior]

the key code lockout is caused by the becm thinking the car is being stolen, too many attempts at the eka or the signals coming from another source (broken door lock, or out station etc).
it wants you to leave the ignition on (position2) until it clears, usually 20 to 30 mins (it will also need a power source as the battery will normally go too flat in that time)

[zzsteve]

Still no progress.
I'll summarise here for my benefit mainly, and hope the collective brains trust may be able to assist.
So, 'engine disabled, press remote' on msg centre when trying to start. Press remote - no change.
No CDL and attempts to re-sync fob all fail. Tried the 1515 generic (US) EKA and this prompts Key Code lockout. Key fob blinks and outputs pulses on 315 MHz.
Nanocom reads the three digit security code in EMS, but will not let me write it to BECM showing "Unable to start communications with ECU' error. Have put EMS into 'security learn' mode and cycled ignition with no joy.
It appears I need a BBS Sync-Mate to write some code back to the BECM so EMS can 'learn' it. How it communicates when Nanocom can't, I don't understand so I'm reluctant to dive into that straight away.
It seems the BECM has locked me out and there is no way to start the re-learning process of key fob codes and EMS-BECM code exchange.
TIA
Steve

So, question is: Will a Sync-Mate talk to a BECM which a Nanocom Evo can't communicate with?

[Eevo]

is this any help?

Range Rover Synchronisation Guide (http://www.reset.rover-tech.info/rangerover_keyfob.htm)

[mtb_gary]

Steve

In my owners handbook it specifically states that the EKA ois not for the Australian market. However, when i rang my local LR dealer they were able to provide me with the unique code for my car. That was around 5 years ago. I have since used the code on many occasions after parking near mobile phone towers.

[TheTree]

Hi

as far as I understand it;

"engine disabled, press remote' on msg centre when trying to start."

Every time I have this on my car I have to use the EKA code to get things going again.

"It appears I need a BBS Sync-Mate to write some code back to the BECM so EMS can 'learn' it."

I only needed to do this when I changed the ECM. I don't think this security code is related to the EKA and "engine disabled" stuff.

As Rupert has stated the "Key code lockout" is when too many attempts at the EKA have been made

So it looks as if you need to find out what your EKA is

Steve

[zzsteve]

Thanks to all.
Local LR says no EKA on their file for my 1995 MY. They say the next step is to ask UK LR, but they want photo ID, receipts etc...
Rupert is correct, key code lockout was from attempts using generic EKA 1515.
Looks like a Sync-Mate is in order.
Steve

[TheTree]

Mate

The only other option I know of is to contact Lee and lab electronics in Mittagong

Labtronx Home (http://www.labtronx.com.au/)

You would most likely have to send him the BECM and KeyFobs for him to do the job.

Steve

[Rupert Prior]

if you send me the bottom (security) board from the becm or whole becm I can unlock it and get it back to working normally.

[zzsteve]

Thanks Rupert.
However, is there are deeper problem lurking since I cannot 'start communication with ECU' (BECM) according to my Nanocom Evo? Is this due to it being 'locked'?
Similar Nanocom communication problem on my D2 was solved by unplugging SLABS ECU from the bus. Maybe this is a variant of the same problem.

TIA
Steve

[Rupert Prior]

the becm has always been easy to spike, but now they are old, just about any deviation from battery voltage can upset them.

[zzsteve]

All fixed now. Many thanks to Rupert for unlocking the logic board of BECM. Must look at a transient suppressor of some sort if this is a vulnerability of the BECM.
Steve