Freelander 1 Code P1672 alarm/immobliser signal error

2001 Freelander 1 v6.

Reprogrammed another fob today and they all work. However, the keys still lock/unlock/alarm ma hippo but they won't start the engine. Keys show up as being "used" in ma hawkeye so they're connected/installed still. With ma hippo locked, turning each key in the ignition will turn the ignition on and unlock all the doors. Engine turns over and me hawkeye tells me error code p1672 is now present and comes back after clearing it, when trying to restart the engine again. Immobilised count counts up each time in ma hawkeye. Battery is charged. Loads of fool and the pump works. Ma hippo worked until today.

Been looking around the interweb and it seems the security code between the engine ecu (ems2000) and immobiliser (ews3d) needs to be re-synchronised.

Any ideas?

have you tired just doing it again and coding your old 1 fob only

matt1295 said:

have you tired just doing it again and coding your old 1 fob only

Click to expand...

Yes. I'm happy it's not the fob's at fault.

i dont really know what went wrong then mine worked a treat

you got the right one didnt you transmitters and not programming

sorry to ask silly questions but worth a check

Hi, yes transmitters. This problem seems to be popular on range rovers too (not when adding transmitters) but I don't know how to do it other than use a computer diagnostic to re-sync. It looks like black box solutions may have a device which will re-sync the ecu's.

I'v an idea why your car won't start. You programmed the remote fob to open the doors. I think there are two different fobs. The earlier version has the immobiliser chip in the fob. Are you are using the correct fob for the Freelander with the chip in the key? Having a chip in the key and another in fob will cause problems.

Nodge68 said:

I'v an idea why your car won't start. You programmed the remote fob to open the doors. I think there are two different fobs. The earlier version has the immobiliser chip in the fob. Are you are using the correct fob for the Freelander with the chip in the key? Having a chip in the key and another in fob will cause problems.

Click to expand...

I'll nip out and re-program the original 2 fobs only, and report back.

I thought 1 of me fobs weren't working so got a replacement. Then found the 1 that weren't working was ok. All 3 work ok, but will try anything. I think the new one was 17tn.

Had another go and set only the 2 original fobs set up only and the 3rd stopped working as eggspected. Tried all sorts again like disconnecting the battery. Still won't start. P1672 returns when trying to start it. Also retuned after reconnecting the battery I think - been a long day. Also found some codes in the abs mk20. 5E14 can interface DME timeout and 5E15 can interface egs timeout. But this may just be some codes that popped up long ago and they didn't come back. The hakweye has a synchronise option so I tried it. Didn't do anything or confirm anything from what I saw. Strange. the black box manual tells you the synchronisation process is more involved. One ecu listens while the other generates codes, then the first is switched of.

It appears that you have altered the code the alarm sends to the engine ecu or altered the code the ecu is expecting. I didn't think the code was synchronized, more they just has to match.

Nothing to do with fobs, there is a transponder in each key. Just handles the immobiliser, not the alarm or locks. If you try to use a strange key it locks the immobiliser.

I will try to find the info. but if you can I.D. the original key/s try just turning the ignition on then off without starting

Also, as Nodge said there is the possibility of another transponder in an old fob, make sure you use a key on its own

Thanks all.
Will try the on/off but I think I will have done this during playing about with the ignition/door lock with the key.

I found someone on lro who had the same problem with the same error code P1672. They took it to the main dealer for a very quick program and problem solved. I get the word "mismatch" on the hawkeye under the immobilisation thing in the security section which links up to the text in rave which says:

"The immobilisation ECU receives information from related systems on the vehicle and passes a coded signal to the ECM to allow starting if all starting parameters have been met. The information is decoded by the ECM which will allow the engine run if the information is correct. The information is on a rolling code system and both the ECU and the ECM will require synchronisation if either component is renewed...

...The ECM and the EWS-3D immobilisation ECU will however need have their rolling code synchronised using TestBook."

and black box solutions gives the process to re-sync the code over ere at the bottom:

https://www.blackbox-solutions.com/shop/help/SM044.html

After finding the error code and eggsausting all options I thought I'd try the hawkeye re-sync option as I have nothing to lose. It just jumps back to the menu, but I have no idea if anything has happened or not so a warning to all not to even try this option. From reading the black box stuff it seems the engine and immobiliser ecu need instructions in a sequence, which I guess the hawkeye can't do, to re-sync the 2 units to allow starting. There's some sort of code between them which needs synchronised. Black box lists the options of

Currently the engine will turn over but not start
Fobs will lock/unlock/alarm it
Keys work in the door to lock/unlock/alarm/disarm
With doors locked and alarm on, insert the key and turn it in the the ignition and the doors unlock
hawkeye can detect the presence of the key in the ignition, confirm vehicle immobilised when normally it would say something different, confirm when key is inserted in ignition without turning, and no other codes popping up other than P1672.

I can't find it currently but black box lists the options of mobilisted, immobilised, mismatch etc as error codes. Mismatch is what I have. This fault only popped up after trying to connect a new transponder which is the same as the others I have. Fault code P1672 which relates to the coding of ecm2000 engine and ews-3d immobiliser computers. I'm not sure if something wrong with the programming. It's too much of a coincedence it happening at the same time. Could be something not related but a blip in the process/system caused it to happen. The ignition seems happy to recognise the key and the hawkeye confirmed the keys were ok afterwards. The hawkeye is what is and I don't eggspect it to be T4, but a manual or simple list of what it does or what the options are and if they work would be nice. Original keys/fobs connected only to it now and it hasn't solved the problem. I'm certain the new remote was the same as I checked the part numbers.

FreeTaz said:

Also, as Nodge said there is the possibility of another transponder in an old fob, make sure you use a key on its own

Click to expand...

I tried that. Key only to unlock and try to start with fobs well away from the door lock/ignition. Thanks.

I wasn't aware that the ecu and immobiliser use a rolling coded sequence, that's pretty advanced stuff. I'm sure that Mems doesn't do that. So your only option is to take it to the stealer and get them to re synchronize the ecu and immobiliser

Nodge68 said:

I wasn't aware that the ecu and immobiliser use a rolling coded sequence, that's pretty advanced stuff. I'm sure that Mems doesn't do that. So your only option is to take it to the stealer and get them to re synchronize the ecu and immobiliser

Click to expand...

The Freelander is so advanced it was well ahead of it's time. Yep thats the way I understand it from what I see online at bbs and in rave. I remember the rolling codes from the 90's. It was the big thing for car security so peeps couldn't scan the remote from a distance, and use the code to make their own fob etc. Our v6's run siemens engine management system ems2000 computer. The immobiliser is a ews-3d or ews3d. I assume the eka code won't do anything. I don't know it anyway.

I spoke to someone who previously did mobile diag with T4 but he doesn't move out of the workshop anymore. So the other option is to ask the AA for help but I don't think their kit will sort this problem. I phoned the main dealer and they have a slot available on Thursday. They agreed to take it in if I could get it there "...as close to the door as possible". I guess they don't have suitable tow vehicles. They may be able to fit it in sooner if I get it up there but won't confirm. I appreciate they want a full work load to keep the workshop busy. I'm tempted to ask them to change the coolant for me while it's there. Never did get round to it and if mine dun't want to bleed propper then I could kill it.

im sure an option on my hawkeye shows if i was immobilised or not maybe worth checking other menus as i cnt think off top my head

matt1295 said:

im sure an option on my hawkeye shows if i was immobilised or not maybe worth checking other menus as i cnt think off top my head

Click to expand...

Can't remember which option it is now, but when you first look at the status it reads "mismatch" for the immobiliser. I've looked all round for other stuff and compared it and it's not happy. Even when trying to re-sync using hawkeye it doesn't provide another menu option anywhere. So I don't know if the re-sync is doing anything, or failing. Best option is for peeps never to try it. I did as after it feked up there was nothing to lose.

such a shame we have being talking about fobs for so long and i got the confirmation from Bearmach in a email and i had no problems what so ever which is why you tired it

matt1295 said:

such a shame we have being talking about fobs for so long and i got the confirmation from Bearmach in a email and i had no problems what so ever which is why you tired it

Click to expand...

I guess it's one of those things that can happen. If it's talking with the immobiliser ecu to program the fobs then it could easily fek up if things don't go as planned. I can confirm if you don't apply an existing fob again when adding others, it stops working.

Just out of interest have you tried to re sync the remotes like when you change the batteries in them?
Oh there is no eka for the transponder key Freelander.