Hawkeye expert needed

The EKA code was turned off in the BCU with Hawkeye on my D2 a while ago with no problems, today I replaced the battery and when I went to open the door the alarm went off and the vehicle was immobilised. When this had happened to me in the past I was able to enter the EKA code and reset the immobiliser, now because the EKA code has been turned off I can't. It won't allow communications with Hawkeye now either.

wasnt the car unlocked when you replaced the battery?... anyway, as long as it's immobilised no tester will comunicate with the BCU... now EKA being disabled you have to disarm the alarm with the fob (unless it's set on "always disarm with key")... lock and unlock again with fob with the battery on

but as yo say you had to use EKA before i have the suspicion that it made some tricks before that and if you decided to disable the EKA instead of fixing the problem you might be in deep sh*t now... explain better what happened and exactly what you did maybe i can help

Thanks for your reply, I changed the battery (Main 12v in engine compartment) today and, when I went to restart the car the alarm went off and the engine immobilised. I found that I couldn't enter the EKA code which I was usually able to do whenever I had the battery disconnected for whatever reason, I mean I couldn't even get the horn to beep which as you know is the first step in entering the code.

I rang the guy that does any switching off of dash lights and resetting/reading fault codes for me and he told me that he had SWITCHED OFF THE EKA CODE with his Hawkeye the last time I had the car with him. The reason I have to use the EKA code is because I also need to have my key recoded, but I have just been locking the car with the key for the timebeing which has ok. I would say the problem lies with the EKA option being switched off in the BCU. The guy :fighting: has been round with his Hawkeye and can't connect, probably due to the car being immobilised.

I would think that the BCU needs to be returned to its proper setting of EKA enabled but as you already said the diagnostic equipment can't communicate when the alarm is in this state, therin is my problem.

turning off the EKA was really bad idea, it's a setting just for those who are turning off the immobiliser too for some reason... so it was to not fix things before that as the car is not suppose to immobilise if the battery is disconnected while it's unlocked..., also if the key looses syncronisation it means it's not the proper one or there's a problem with the BCU ...i suppose that there was a misslock issue before...anyway what's done is done so in this case if you can't remobilise the car somehow you'll need a replacement BCU and this one you can bin it as being locked it's useless

Yes I was thinking it was a bad idea to switch off the EKA, so what are the complications of fitting another BCU. Could a secondhand BCU be fitted, I see a guy selling them on ebay. He supplies them with chassis number and EKA code, what else has to be programmed into the unit to match it to the vehicle, or is it a new BCU from Land Rover??

Thanks again.

if it's in good working order the used BCU it's ok aswell, you have to synk' it with the engine ECU immobiliser code, sync the keys and do the desired settings for your needs(foglamps, electric seats, alarm disarm mode, sound, auto or manual, etc)...be aware that the BCU has the mileage stored in memory and if that's greater than the on in the instrument pack it will be assumed, always the greater mileage will be assumed.

OK thanks - you say sync it with the engine immobiliser code, where can I get this code and would hawkeye be sufficient to do all that is required.

you dont need the code ... in the engine EMS-programming section of Hawkeye there is a immobiliser menu and hwakeye will lead through it to "learn" the code...then the car must start ... the other settings are in BCU-programming section and hawkeye can do them all except the key programming as it needs the long barcode not the short code from inside the fob...though there is a solution for that too, attached, but i didnt try to be able to vouch if it works or not...for the beginning set the alarm in BCU to "always disarm with key" and disable the passive immobiliser untill you see if you can sync or not the keys...this way you'll be able to use the car and the alarm will be active with the main immobiliser but without passive immobiliser.

edit: i can't attach the file as it says it's invalid

EDIT2: here is the link https://docs.google.com/spreadsheet...QURxY3JLM1gzdTljN2JBaVNSanc&usp=sharing#gid=0

Thanks again, I have been in touch with Turner Diagnostics in Hemel Hempstead and have sent the BCU and both keys to them. They say they will be able to 'unlock' the BCU enable the EKA option that was disabled and recode both keys.

Thanks Sierrafery - I got the BCU back today and connected all up. Put on Hawkeye, went as you said to Engine EMS-Programming-Immobiliser menu, hawkeye detected a wrong engine code, after agreeing to that it started to learn the code and YES the engine started.

The only problem is that although both keys were reprogrammed none of them work, after speaking to the guy who reprogrammed the keys to the BCU he said that it can take up a week for them to be recognised. What is your opinion on this.

The only problem is that although both keys were reprogrammed none of them work, after speaking to the guy who reprogrammed the keys to the BCU he said that it can take up a week for them to be recognised.

Click to expand...

that's the greatest oddity i've ever heard, but i might be wrong though... the strange thing is that it lost the immobiliser code too... on a simple repair intervention the stored data in EEPROM must not suffer, and if they replaced the main chip everything is lost... are you sure it's the same BCU not other? ...anyway, as you have hawkeye set in BCU - Programming to "always disarm with key", check other settings to be OK, at the end of all when it asks if you want to reprogramm market settings(or something like that) prompt "yes" then you can lock/unlock with the key without getting immobilised... after that open one key, read the code from the circuit board, use that code generator link i gave you and try to programm your key with hawkeye(in transmitters menu)... i heard people who did it and others who couldnt, i didnt try myself as i have hawkeye too

if no joy with the key programming find somebody with nanocom to do it

in the BCU programming menu , when you have the desired option on the screen just go further to the next one with arrow cos with the yes/no buttons you swap the options.... you'll figure it out yourself

before that try to push consecutively 5 times the unlock on the fob, maybe you are lucky , but quite unlikely to work

isn't your odometer mileage reading flashing too?...cos if it is it means that all the memory was erased

BUT to have the benefit of a doubt... wait one week before you mix things up yourself as long as you can drive it and lock it, maybe i'm wrong

Its apparently my original BCU which had the chip changed, the odometer isn't flashing and has retained the original mileage. It is set to 'always disarm with key' but I'll do as you say and wait for a week and see if anything happens before I try what you say.

chainsaw said:

Thanks Sierrafery - I got the BCU back today and connected all up. Put on Hawkeye, went as you said to Engine EMS-Programming-Immobiliser menu, hawkeye detected a wrong engine code, after agreeing to that it started to learn the code and YES the engine started.

The only problem is that although both keys were reprogrammed none of them work, after speaking to the guy who reprogrammed the keys to the BCU "he said that it can take up a week for them to be recognised". What is your opinion on this.

Click to expand...

What a load of old baloney !!!

Does the little man inside the ECU get tired and go on his holidays?


Tossers eh? Don't you just love 'em !


Dave

Hey ferry my disco milage was flashing when I got it does this mean anything with regards to bcu?

Yes, you must go with hawkeye in BCU - programming and disable "odometer error warning" that's all

Howsit guys

I just love bringing old threads back from the dead! It seems my BCU has seen better days. My remote wont lock or unlock the car (I've put a fresh battery in to check and its still the same) and it wont turn the engine over if I try to start the car. Just flashing indicators. Also, I've put a hawkeye onto the car (is the port in the RH foot well the right one to use?) and it doesn't seem to be communicating with the BCU, it shows all the other settings and real time data no problem though.

Any idea please gents?

Hi. Probably it's immobilised cos you couldnt unlock with the fob and then the BCU doesnt comunicate with diagnostics. You have to remobilise it with EKA code then the BCU should comunicate and you can set the alarm to "not fitted" untill you replace the RF receiver which is the first suspect. If no joy with the EKA code simply replace the receiver to rule it out and if that was the problem it will be remobilised first time you can unlock with the fob

Thanks SF, I've tried doing the EKA code thing but to no avail. I'm pretty sure i got the sequence right too, I used the sequence that was quoted from the Rave manual. I used to use just the key to unlock and and the fob to lock it as the little micro switch was ruined by the Mrs finger nail but it would still unlock if i bridged the two contacts out on the fob. Can a BCU just fail? This is rather frustrating!

Yes the BCU can fail but if you can't unlock now which you could before the RF receiver is still suspect and if it's not working the BCU doesnt get the remobilisation coil's signal from the barrel and stays immobilised. What doesnt work with EKA? do you get the single bleep at the end like it's the wrong one?

Thanks SF once again for your reply. My car has never beeped even when the alarm went off so I suspect it was somehow disabled before I had bought the car so I'm not certain if I'm getting the beep at the end of the attempt to disable after trying to disable the immobiliser using the EKA code. So you're saying that the RF receiver will disable the immobiliser even when the key is used? If that's the case , ill have to get a replacement I think.