RangeRovers.net Forum banner

1 - 3 of 3 Posts

·
Registered
1995-2002 Range Rover P38A
Joined
·
9 Posts
Discussion Starter #1
Thank you to everyone beforehand, this forum and its user has provided a wealth of info...and saved me a bunch of money!

Anyways, i have a scan tool hooked up to my obd port to provide live info and recently received a "pending" p1667 code. This is the only pending code and there are no other fault codes. I've read multiple posts mostly relating to engine disabling and anti theft systems. A couple recent issues i've been having, which may or may not be related, is my key fob light is always on and the rear navigation system is always on. The key fob light will remain on as if its being pressed (solid no blinking), and pressing the lock/unlock would not do anything. I pulled and replaced the battery and everything seems to work fine now. When i got the p1667 code, i thought this might be related since the key activates the anti theft system. Also, my rear navigation unit will remain on when the car is off and few times it has drained my battery. I pulled its power to confirm, it was in fact the unit draining the battery and left it disconnected for the meantime. I've heard battery issues causing this fault and disabling the engine.

Question, what might be causing a "pending" 1667 code? For these types of issues wouldn't a hard code just register, not a pending? Perhaps something to do with fuses or relays? Am i wrong to think this is electrical related? I cleared the code, but it only came back the next day. All that being said, it runs great. But the truck is sensing something off and i'd like to get ahead of it before i'm stranded.

Any info is appreciated! Thanks

BTW 2002 Range Rover Westminster 4.6 w/200k miles
 

·
LEGACY VENDOR
1995-2002 Range Rover P38A
Joined
·
4,220 Posts
From memory P1667 is something to do with the immobiliser code from BECM to engine ECU.

If it's showing as 'pending', but the vehicle starts and runs, then I wouldn't worry about it. The Bosch ECU seems the list it as a 'fault' whenever it isn't receiving a valid immobiliser code from the BECM for any reason... If the passive immobiliser is still turned on, then the BECM automatically immobilises the vehicle after a period of inactivity (and the engine isn't already running!) - if you interrogate the engine ECU when it's not sending the code, then it will show up as a 'fauit'

Once the BECM mobilises again and sends the code, then it will go away. That might explain why it comes up as 'pending'
 

·
Registered
Joined
·
37 Posts
I had p1667 code since last few years. It was caused by nonoperational keyfob. It is like that because becm still waiting for fobcode - even if alarm is deactivated, EKA code deactivated and immobiliser is of (in becm options). In that condition you will be able to open car by blade and start it as well but system anyway will try to force key to sent code when iginition is on. If no code received then p1667 recorded.
In my case set of new fobcodes resolved that issue fully.
regards,
mariusz
 
1 - 3 of 3 Posts
Top