Hi,

My car was working great till yesterday morning. I went out to drive it and at first it wouldn't unlock. It did eventually then wouldn't lock or unlock again. I tried both my keys and the same problem. At this point I tried to start it and it worked fine!

I dug out my trusty Hawkeye and plugged it in and went to the security menu. There were no new errors but I ran the Synchronise ECU function hoping it miigt help (Hawkeye user guide is useless) and it did not fix it. However now when I try to start the car it just cranks and cranks without starting and when I check ofr engine faults I see the immobiliser throwing an error 39 - EWS Tampering Protection.

I reseated the BCU connections under the rear seat and the rear rf sensor connections and resynced the keys and they now work again. However I'm now left with the engine error and the car not able to start! I can't help think the Hawkeye function for syncronise ECU caused this but I'm not sure. I see the EWS (Immobiliser) and the DME talk to each other with rolling codes that are burnt in to them so I'm guessing this 'Synchronise ECU' was to set them back in sync? I've contacted Hawkeye and they are offering to update the firmware to v7 and I notice from the the documentation that this function for Sync ECU is no longer there.

I'd appreciate any help here! Are there any members in the Glasgow area that have better diagnostic computers that may be able to help fix this? I'm in Bridge Of Weir. I hear the All Comms might be able to do it?

Thanks for any help James

Don't know if it applies to FFRR but on the D2 with similar symptoms I have seen it being necessary to go into the Engine ECU (using Nanocom and I presume Hawkeye will do the same) and learn the engine security code.

1. Engine
2. Check Security Status
3. ECU Immobiliser
4. Security Code -
5. Alarm Security Code Learn

This has arisen after a replacement BCU ( you have been into the BCU so may be giving the same result) but requires going into the Engine ECU.

Don't know if that is of assistance but you can look to see.. John
2008 Stornoway Grey 3.6 Tdv8 Vogue - SOLD
2005 TD6 Java Black Vogue - Written off!!
GAP iiD BT-Sold

Thanks John,

The HawkEye I have had the security / Syncronise ECU option but that may have been what caused the issue in the first place as I ran it then discovered the car wouldn't start.

Car was flat bedded in to the main dealer yesterday so I'm awaiting any news from them. Fingers crossed its just a diag and ECU resync.

James

James
Would be interested in the result.

The reason I quoted the above was because, as I mentioned, with the Disco 2 when you sync the BCU you also have to go into the engine ECU to learn the security code. Just thought it might be the same for the FFRR.

I've got Nanocom for the D2 so not too familiar with Hawkeye.

Hope it turns out to be straightforward. John
2008 Stornoway Grey 3.6 Tdv8 Vogue - SOLD
2005 TD6 Java Black Vogue - Written off!!
GAP iiD BT-Sold

Hi,

Just to report, the main dealer diagnosed my car and performed a resync of the rolling codes from the EWS to the engines PCM computer and it started and has been fine since. I'm still not sure what caused this problem but its worked for nearly a week now.

I do not believe anyone except the main dealer can perform this resync on the L322.

Total cost was £114 which included a good hoover and wash which my car needed anyhow!

Interesting now when I program my time and date in the car, it already knew it was 2014...I wonder if they updated other things at the same time?

James

Not too bad then, now stop playing with it and drive it.....  Pete
__________________________________________________
2014 L405 Autobiography SDV8 4.4 Loire Blue Ebony interior
2012 L322 Autobiography 5.0 Supercharged Ipanema Sand Sold
2011 L322 Vogue SE 4.4 TDV8 Baltic Blue. Sold
2002 L322 Vogue 4.4 V8 Epson Green (Fatty Offroader) Sold
-Click for Project Fatty off roader-

Ha Ha well said Pete
Glad all is ok the dealer probably updated all software releases from day 1 mine does when the car is serviced