This isn't a dumb question. It's just irrelevant.

What is your source for this info?

​​​​​​​

 

UPDATE: after reading through other comments (thanks), I cleared the P1668 code. After driving it around - starting & restarting a few times - the error has not rendered again (yet). It may have been a fluke or mis-keying of the Nanocom on my when trying to program FOBs. Anyway, I hope this is helpful to other members.

 

I don't think it's irrelevant. It's detective work. The forum member here unlocks the car with the key but has a working fob. I'm wondering why someone would do that. It might bring new information to light that is otherwise not out there and help us solve the problem. For example "I cut the roof off my Disco, dropped in an L494 SC V8 and made it into 6x6 pickup truck, and relocated the 315mhz receiver to the drivers footwell but I don't see why that would have an affect on this issue." Not suggesting that's what is going on here but many # of times other seemingly unrelated modifications turn out to be the problem.

The Nanocom users manuals. https://www.nanocom-diagnostics.com. I own a Nanocom, and they have PDF's explaining the different ECU functions. This text is found under D2 BCU.

 

I do get the ocassional P1668 error code. It seems to be related to this issue that I am facing, i.e., need to replace my driver side door actuator motor:
https://landroverforums.com/forum/di...not-up-104766/

I was able to clear the code with my Nanocom each time the code appears to get my engine started.

I am waitin for the weather to clear to replace my actuator motor. Hopefully, this ocassional P1668 isse will also disappear.

 

What other symptoms are leading you to replace the actuator?

 

As a courtesy to the OP, I do not want to hijack his/her OP's thread here

This is my thread on probably reason for replacing the actuator:

https://landroverforums.com/forum/di...not-up-104766/

 

I am the OP. 🙂 But okay.

 

Problem solved, and it appears it was self-inflicted.

I noted above that we used a Nanocom a while back to set up a second keyless entry fob, and played around with some other settings.

One of the other settings we changed was to enable EKA (emergency key access). Last night I used the Hawkeye to disable EKA and the problem was resolved. I can now use the physical key to lock and unlock the truck and disable immobilization when unlocking with the key, regardless of whether the truck was locked using the key in the lock or using the plip.

Big shout out and thanks to keninnc for figuring this out. He had the same situation with his '04 DII and put two and two together.

It seemed weird at first, and it is still a little counterintuitive, but I guess if the key will disable the alarm and immobilization system on its own, there is no need for EKA. And conversely, EKA is needed only if you want the truck to remain immobilized when unlocking the truck with the key in the lock.

I have not found this information in any of the literature, either the RAVE Workshop Manual or in the Valeo BCU documentation that is available from the nanocom-diagnostics website.

Perhaps the moral of the story is "no good deed goes unpunished." The "good deed" of enabling EKA brings with it the loss of ability to unlock and start the truck with a plain key.