youmitegetian

youmitegetian

Active Member
Hi all.

so it’s been a while since I sold my last Range Rover but I’m back with a D2 TD5 for green laning.

been ok for a little while but now I have an immobiliser issue, common fault I know, stupidly didn’t realise these had the EKA code but will get it tomorrow when the stealer is open.

My searching hasn’t found my exact fault.

car was fine but then not used for 2 weeks, go to use the car and fob not working but led lights up, used the key in lock and obviously set off the alarm, disconnected the battery to shut off the noise and then grill off to pull the plugs on the horns, connect battery back up and fob starts working.
Park up for couple of hours and fob not working again. Disconnect the battery for a while, come back to it and reconnect the battery, fob works again.
Have changed the RF receiver for a known good unit but makes no difference.

Any suggestions would be greatly appreciated.
 
I will get the alarm and immobiliser disabled once I can borrow a Nanocom or Hawkeye, not sure that will solve the issue but would be nice to find the actual cause so it doesn’t come back later,
Looking at that thread it will be work checking the bcu for signs of moisture. Will also check the fuses, you never know.
 
So no fuses blown, no sign of moisture inside (rare no sunroof model)
I guess I’ll have to wait until tomorrow and get the EKA code unless anyone knows a way to get it today?
 
Just a thought - but have you double pressed the fob? You know...the second press that takes the "girly" lock off and allows the other doors to open?
Had a strange experience with my own recently along those lines. I leave my D2 unlocked and usually with the key in the ignition (except during the Glasgow Fair :p) and it wouldn't start the other day. Finally did a double press and the bu66er leapt back to life. "Normal" service is now resumed. As I say...just a thought...
:)
 
When it happens again unlock/lock with the key WITHOUT OPENING the door then try the fob, the symptom is explained in the attached bulletin (neglect the 315Mhz/NAS thing cos the issue is the same).
 

Attachments

  • bcu_sleep-mode_troubleshooting_and_upgrade_8601nasf_2.pdf
    287.5 KB · Views: 274
Yeah tried the above, tried all sorts of stuff I’ve read to be fair, it’s probably the EKA but seems odd that it started after leaving it for a while, just seeing if it will do the same today, will leave it a couple of hours, fingers crossed as I have a mate lending me Hawkeye so might be able to turn off the alarm and immobiliser
 
You'll be able to communicate with hawkeye only if it's already remobilised with EKA or fob... do you have two fobs as to make sure it's not a fob misbehaviour cos the other things can be coincidental also if the RF receiver was not new it's not 100% ruled out, there are not many causes for such issue.
 

Attachments

  • remote_handset_function-alarm_module_troubleshooting_and_upgrade8610nasf.pdf
    286.9 KB · Views: 171
I’m hoping that by leaving it a while it will work like it did yesterday, that way Hawkeye should be able to connect to the bcu.
The receiver was new and used for a short time then lent to me so can’t see why it wouldn’t work as it came from a working vehicle, no symptoms different to my receiver.
Annoyingly and stupidly I only have one key, it’s on the to-do list but obviously should of been higher up the list.
 
Just realised my fob doesn’t have a transponder chip in it as well so I guess that’s probably been an issue before, have seen people tape them to the steering column before.
Wouldn’t explain why the fob had stopped working though.
 
youmitegetian said:
Just realised my fob doesn’t have a transponder chip in it as well so I guess that’s probably been an issue before, have seen people tape them to the steering column before.
Wouldn’t explain why the fob had stopped working though.
Click to expand...

Which chip are you on about?

Cheers
 
Ok so....... borrowed Hawkeye but when I returned to the car and connected the battery as before the fob didn’t work, car wouldn’t start. Plugged in Hawkeye and on the 3rd attempt it connected to the bcu, turned of alarm and immobiliser and the car now starts, checked fob to see if signal received and it wasn’t, tried the old receiver and still nothing so either both receivers are faulty or the wire from receiver to bcu is broken, can still lock and unlock with the key though and more importantly the car is now usable again.
 
Do you mean that the dash led reacts to the fob? if yes you have a problem with the central door locking not the fob or receiver
 
No was referring to the fob led. I’ve turned the dash led off now but don’t remember that reacting to the fob, it did react to the door lock though. I tested the receiver to see if it registered a signal from the fob and it didn’t but that could mean a wiring issue as much as a receiver issue from what I’ve read.
 
You must log in or register to reply here.

Similar threads

F
Disco 1 Immobiliser issues
Replies
11
Views
2K
discool
discool
D
Key fob
Replies
0
Views
491
DAVID HICKIE
D
moorsman61
Immobiliser problem
Replies
1
Views
575
discool
discool
G
Td5 central locking (another one)
Replies
3
Views
800
sierrafery
sierrafery
ian mitchell
Disco 3 (LR3) battery issue
Replies
11
Views
903
ian mitchell
ian mitchell