What happened to your Discovery 2 today?

Unsure, ECU change was some years back. No problems with Security System/Immobiliser/Locked In/Locked Out/Starting etc until Tuesday of this week.
Still no go, EKA not being accepted. Very frustrating. Now Nanocom sync between ECU/BCU or reverse not working.

Quote:

---

Originally Posted by Collins

Unsure, ECU change was some years back. No problems with Security System/Immobiliser/Locked In/Locked Out/Starting etc until Tuesday of this week.
Still no go, EKA not being accepted. Very frustrating. Now Nanocom sync between ECU/BCU or reverse not working.

---

I had an issue recently where the Nanocom wouldn't talk to anything. Check the fuse box in the engine bay, last fuse on right as you look from RH side (15A I think). I found this blown and when changed everything was talking again. Won't hurt to check.

Quote:

---

Originally Posted by ChookD2

I had an issue recently where the Nanocom wouldn't talk to anything. Check the fuse box in the engine bay, last fuse on right as you look from RH side (15A I think). I found this blown and when changed everything was talking again. Won't hurt to check.

---

Thanks for the suggestion. Unfortunately I had already checked ALL fuses - All OK
Very frustrating, particularly as now Nano Evo not able to communicate with ECU/BCU
Anyone know of a competent auto elec familiar with Discovery2 in the Sunbury area?

Also check the fuse in the cabin that sits by itself at the top left, no 36? I think.

My Nanocom would not connect with teh bCU without the fuse in.

Regards PhilipA

Hi Collins,

I think I'm out of my depth here!
In the Hexadecimal number system, "F" = 15 and "10" = 16 (second number in each example is a simple, everyday counting or decimal number).
So what did you interpret "F-1" as being?
How many key-turns would you have tried for each instance of "F-1" when trying to enter the EKA via the driver's door lock?

I am afraid that it seems likely to me that, if the ECU has been changed without the necessary steps to amend the EKA at that time, then "all bets are off".

I'm not sure that this is correct, but I expect that it would be necessary for you to achieve a successful entry and acceptance of the previous EKA before changing it via Nanocom (or any other means) would work.

Good luck, and I would be interested to hear how you eventually solve this one.

Regards,
Andrew

Quote:

---

Originally Posted by Collins

Andrew, thanks for your comments.
Yes, do have 2 wireless functions - Internal/External thermometer & Door Bell. Same units were installed at previous residence & were never a problem. Doorbell not stuck & continuously chiming, however have now disabled both.
New battery in remote, although initial battery OK - 3.16V. No activity when either button depressed. Nanocom is reading remote RF signal. Still unable to start vehicle & not accepting EKA.

EKA Code was definitely 3 digits (identical), Hexadecimal(F-1) in each of the four fields. The ECU fitted currently is not the original & code is possibly a corruption from when it was removed/reinstalled. It has been installed for 3+ years now. Replaced original to attempt to alleviate fluctuating idle RPM. It was suggested that the original ECU may have been damaged by a previously installed LPG fueling system, which had been removed prior to my purchase of the vehicle. EKA Code now changed as mentioned.

Further query. What does the Immobilisation Code apply too?

---

Nope. Just log in. Change EKA to your chosen code.
Save changes to ECU.

Mine became 1111 [emoji41]

I put the car on ramps to get easier access.
Attachment 157114 The black mat came with the rear steel bar.

Attachment 157115 The access, the access!

Attachment 157116

Quote:

---

Originally Posted by AndrewMilne

Hi Collins,

I think I'm out of my depth here!
In the Hexadecimal number system, "F" = 15 and "10" = 16 (second number in each example is a simple, everyday counting or decimal number).
So what did you interpret "F-1" as being?
How many key-turns would you have tried for each instance of "F-1" when trying to enter the EKA via the driver's door lock?

I am afraid that it seems likely to me that, if the ECU has been changed without the necessary steps to amend the EKA at that time, then "all bets are off".

I'm not sure that this is correct, but I expect that it would be necessary for you to achieve a successful entry and acceptance of the previous EKA before changing it via Nanocom (or any other means) would work.

Good luck, and I would be interested to hear how you eventually solve this one.

Andrew

---

It would be tedious attempting to enter the previous code, "255" in each of the 4 fields. Seems improbable I know, when the number according to RAVE is a number between 1 & 16.
Checking via Nanocom indicates that the new Code has been accepted.
May reinstall previous ECU, however still have to be able to have the ECU/BCU sync, which is not happening at present. Also had fault, when data was being displayed P1668, which would not clear. ie Press Clear, receive Clear Message Screen, but same fault message reappears. Message said the fault was persistent Ha!
Have checked every fuse in both Engine bay & in Cabin, all OK. Plan to disconnect battery & physically disconnect & remove ECU & BCU, then reinstall & HOPE that something changes for the better

Regards,
Charles

Quote from a UK forum

ust FYI for anyone who may run into this problem. (Please excuse my ignorance of all things mechanical as well as I write this post).

My husband was stuck on the side of a mountain last night in his 04 LR Discovery II. Wouldn't start initially. Showing code P1668. He climbed the mountain a bit to get reception and called me to look it up from home. Showing alarm system. I looked through what I could find and saw lots of info about the BCU possibly being bad - not good when you're stuck where fed ex can't reach you. Ran through reset procedure with position II on the ignition and unlocking with the key fob and still nothing. Did see a post about checking the intertia switch 10A fuse in the engine compartment fuse box. Replaced it with a 15 and they were good to go for a short time until it blew again. Went through several fuses repeating this process until they had to abandon her at 11:00pm and hike down the mountain about 7 miles. Went back this morning and discovered a frayed wire. It looks like when the previous owner installed the after market stereo they moved part of the wiring harness and over time it became frayed.

Regards PhilipA

Quote:

---

Originally Posted by PhilipA

Quote from a UK forum

ust FYI for anyone who may run into this problem. (Please excuse my ignorance of all things mechanical as well as I write this post).

My husband was stuck on the side of a mountain last night in his 04 LR Discovery II. Wouldn't start initially. Showing code P1668. He climbed the mountain a bit to get reception and called me to look it up from home. Showing alarm system. I looked through what I could find and saw lots of info about the BCU possibly being bad - not good when you're stuck where fed ex can't reach you. Ran through reset procedure with position II on the ignition and unlocking with the key fob and still nothing. Did see a post about checking the intertia switch 10A fuse in the engine compartment fuse box. Replaced it with a 15 and they were good to go for a short time until it blew again. Went through several fuses repeating this process until they had to abandon her at 11:00pm and hike down the mountain about 7 miles. Went back this morning and discovered a frayed wire. It looks like when the previous owner installed the after market stereo they moved part of the wiring harness and over time it became frayed.

Regards PhilipA

---

Thank's for your input, all suggestions appreciated, even the humurous ones. Unfortunately though, operating the Door Bell did not reset security or start the engine.

The P1668 Error Message ' Anti theft circuit Signal High (Serial link Open Circuit - RAVE) will not clear.
Until I reconnect, battery, ECU & BCU and attempt to interrogate via Nanocom I will not know whether I have cleared the problem. Hopefully [bigsmile]Nanocom Evo will be able to communicate with both again.

Any suggestions/advice will be welcomed. Need vehicle operational ASAP. Medical Appointments, Life in general. Public Transport is not a real option, particularly when you have a seriously damaged leg.