joe84
Member Since: 19 Feb 2020
Location: Yorkshire
Posts: 2
 
|
| 2003 Defender Td5 Hard Top - Immobiliser Problem? | |
Afternoon All,
I hope you're all well.
I'm new to the forum and I'm in a bit of a pickle with my 2003 Defender 110 Td5 Hard Top so I'm praying that I can find someone who has a solution! I know others have had similar issues but seemingly nothing identical, but apologies if I'm covering old ground with this thread.
For context this car is a basic 135k mile 2003 110 Td5 Hard Top with no key fobs, no alarm and supposedly no enabled immobiliser. The car had been starting and running without issue for the three years I've owned it. The battery's died on a number of occasions as it intermittently spends time sitting around, but has always then been fully charged and normal service has resumed.
However, a couple of weeks ago the battery died again and the following sequence of events occurred:
1. The battery went flat
- We then fully charged the battery, but;
- The car would turn over but not fire.
2. Fault traced to oil having worked its way up the ECU/injector loom as is the Td5's way, apparently. So;
- The ECU/injector loom was replaced with a new, genuine part from Land Rover;
- The ECU socket and pins were checked but were found to be free of oil and the internals appear to be clean and in working order;
- Again, the car would just turn over but not fire up.
3. We then traced the cause of the car not firing up as being due to poor fuel pressure. The car's covered a good number of miles we thought, so the fuel pump's probably pretty knackered, hence the no starting. So;
- We changed the fuel pump for a new, genuine part from Land Rover;
- The car turned over without issue, fired up immediately but would then cut out after two seconds.
4. Having checked forums, the web and consulted a few ECU specialists, we bought a Nanocom system. We then;
- Connected the Nanocom to the ECU and the Nanocom identified that the 10AS module had decoupled itself from the ECU;
- Recoded the 10AS module to the ECU;
- Found that the same problem persists whereby the engine fires up only to cut out two seconds later;
- The Nanocom readout states that the ECU's immobilised and the red immobiliser indicator LED on the dash is illuminated. The system is otherwise performing as it should, according to the Nano's readout.
The immobiliser has never been enabled on the car due to it not being a County nor an XS. It’s always started without issue but this problem’s reared its head and we’re at a bit of a loss as to where to go from here as (we think) we've tried pretty much every solution. We’ve even tried another Td5 ECU and 10AS module, coded together using the Nanocom, but the car still fires up only to cut out seconds later, with the Nanocom displaying that that ECU is also immobilised. The Nanocom further states that all systems are working as they should, but that the ECU's immobilised. Could the new ECU/injector loom installation have caused problems with the ECU/s leading it to immobilise the ECU? Or could the flat battery have scrambled something? Or have we inadvertently coded something into the ECUs that's immobilised them?
We’ve tried inputting the EKA code, disconnecting and reconnecting the battery, have checked the fuses, the ECU earth and seemingly everything in between, everything and anything that we’ve found in forums, online and the from the direction of a few specialists but all seems in order aside from the fact the ECU's in an immobilised state. Paul from Technozen has been incredibly helpful but couldn't diagnose what the problem could be given we've tried many known solutions but with no success. We’ve sent one of the ECU/10AS pairings down to Technozen to fit his Immobiliser Code Emulator in the hope that we just need to bypass the 10AS module and then she'll fire up. If that doesn't work then we're really stumped.
Has anyone experienced this sequence of events before and if so, how did you overcome it, assuming you did?
Any help, tips and/or direction would be greatly appreciated.
Cheers,
Joe
|
12th Feb 2021 1:57am
