Freelander 2 2007

Completely out of the blue, car has been working fine for ages.

Monday morning:
Started about 4 times and the engine stopped withing a few seconds showing "engine system fault" on the dash. Started on the next attempt, reversed it and parked so I could get my wifes car to use if necessary, car seemed ok so I drove it, all fine. Drove to work and no issues

Rest of the week car drove absolutely fine

Friday:
Car started fine, drove about 1/2 mile, engine system fault showed on dash, car was driving, drove real slow home.
Connected obd device, too many codes, so erased them so I had a clean sheet to start. Started car, all fine, no sign of the error

Saturday:
Started car, all fine, no sign of the error

Sunday:
Started car, engine cut out and engine system fault on dash. Read the codes :


1. P0380-00 Permanent Glow plug/heater circuit ‘A’
2. U0100-87 Intermittent Lost communication with engine control module/powertrain control module ‘A’
3. U0415-94 Intermittent Invaid data received from ABS control module
4. U3000-87 Historic Control module
5. B1D85-23 Permanent Headphone panel 2
6. B1B42-01 Permanent Front left inner sensor
7. B1A14-96 Historic Restraints control module warning lamp circuit
8. U0208-08 Intermittent Lost communication with the seat control module ‘A’

Anyone have any ideas where to start checking.

Check the battery as FL2 are very sensitive to low voltage. 94 Disco 300 TDI Gone
96 Defender 300 TDI Gone...Should have kept it.
2003 Freelander ES TD4 Gone
2002 Defender TD5 Gone
2005 Freelander HSE TD4 Gone
2015 Freelander 2 Metropolis Keeping for now!

As the FL2 control modules depend upon one and other for signals, it can be confusing.

Try grouping your error codes in time sequence, and you may be able to spot what kicks off the rest. FL2 XS SD4 Auto 2010 2012-2017 (21k - 91k miles) (MY2011)
FL2 Metropolis SD4 Auto 2014 2017- (16k - 79k+ miles) (MY2015)
Metro in its 11th Year of (Extended) LR Warranty / Full LR Service History
(Expensive, but Trouble/Worry free - hopefully?)

Will do ta

I'll have to suss the obd unit to see if it records date/time, the error codes don't have any timing on the display its an autel ds708 pro - on loan from mate

Wasn't able to get dates/times against the codes.

Car has been working most of the time now, drives fine, generally fault only appears when starting. Couple of times the fault triggered but it started on 3rd attempt. Friday, 8 goes before it started. Drove a short distance, then the error flashed on screen but the car kept driving for about 10 metres then the error went off, and was fine after that.

Added the secondary earth lead today between battery and starter.

Cleared all the errors, started and it failed twice.

Only 2 error codes this time.

O0380-00 glow plug /heater circuit A
P0606-00 control module processor.

What I did find strange, while I had the OBDII connected, the ignition on, engine not started ... the error message came up on the dash twice. hopefully that might steer some opinions on fault.

Just checked the battery voltage using a multimeter 12.3V,

OK, I've had an auto spark look at the car, he has checked all the wiring and only thing he found was that the ecu had corrosion on the bottom edge.

Popped the ecu back into the car, drove back to my house, it started first press, left it 30 mins, started 1st press again and idled for about 10 mins, I switched it off.

tried next day, 1st press start, short journey, couple of starts, all seemed fine.

Next day, engine system fault.

diagnosis says:

Stored Fault Codes: U0100-00-permanent lost communication with control module/powertrain control module 'A'
U0208-08-Intermittent. Lost conmmunication with the seat control module 'A'
B1D17-87-Intermittent Battery backed sounder
U0100-87-permanent lost communication with control module/powertrain control module 'A'


Based on these codes, suspecting the ECU, via chat I confirmed the company could test, sent it away, ended up being returned FOC they were unable to test and confirm faulty.

sooooo, now where do I go, I don';t want to turn this 2007 car into a piggy bank with no bottom, but I love it, it has served me pretty well, a workhorse with no limits, and I can walk in and out of it when my back is bad ... constructive advice welcomed

In your previous post you said checked battery voltage at 12.3v, that really is too low & most of those fault codes are ones that can show up with a failing battery.

Out of interest, how old is the battery & what sort of voltage are you getting with the engine running? (Now Sold). 2008 Freelander 2 (Nazca Sand) SE TD4 Auto. Statutory write off & on WOVR for hail damage but still road legal.
171037Km as of 09/05/22
Superchips Bluefin Flash
Nanocom Evo II (also sold)

The original battery was about 3 years old, I was getting readings around 12.3 - 12.5 if I remember correctly.

I had a new unused battery that had been sitting in it's packaging for a couple of years, used a repair and charge cycle to refresh it and used it in the car, still the same issue.

I think you're right, to rule this out i'll just buy a new battery and try it.

I had a similar problem with my 2007 freelander. Found the problem to be a plug loose under the carpet on the paassenger side of the car. There is a bank of 3 plugs on the floor just in front of the front door. If you pull back the carpet you will see them. When a passenger enters the car he/she puts their foot on the carpet which pulls against the plugs. Mine just fell out when I moved the carpet. Two tie wraps later the problems solved. Worth a look.

I have a new battery arriving later today, so i'll put the ECU back in and give it a try.

I'll also be checking the plugs under the carpet - thanks georgetina

This fault is intermittent - a real PIA to resolve

The extracts from the from the Repair Manual shown below seem to indicate that you have a loose connection on the CAN cct.
georgetina has a good idea, try looking around for something loose or damaged, and as the drivers seat is amongst the errors, start by looking around there at the wiring etc.

------
Driver Seat movement from switch-pack occurs in inch mode. When any seat axis movement is requested from the seat switch pack the requested seat axis immediately moves a short distance then stops. This behaviour occurs for ALL seat axis movement (slide, height or squab) when requested

DSM is disconnected from the MS CAN bus

Check for Instrument Cluster DTC U020808 Lost Communication with Driver Seat Module. If this DTC is present then check the Driver Seat Module CAN bus connections


-----
U0100-00Lost communication with ECM "A"

CAN circuit: open circuit CAN circuit: short circuit to each other CAN circuit: short circuit to power CAN control module failure

Carry out a complete vehicle read for DTCs indicating a CAN or module fault. Rectify as necessary. Refer to the warranty policy and procedures manual if a module is suspect.
----- FL2 XS SD4 Auto 2010 2012-2017 (21k - 91k miles) (MY2011)
FL2 Metropolis SD4 Auto 2014 2017- (16k - 79k+ miles) (MY2015)
Metro in its 11th Year of (Extended) LR Warranty / Full LR Service History
(Expensive, but Trouble/Worry free - hopefully?)

Great info IanMetro - thank you, i'll add that to tomorrow checks

Here's where i'm at, rain has delayed play.

New battery arrived late yesterday, popped it on to a charge just to make sure all ok.
Refit ecu back into the car
Connect the new battery
lock/unlock the car
press start
engine system fault - did not start
reset the clock in the car
start car again - success
Currently idling to see if it fails, which it would have done before, but generally within 5 minute of starting

Going to check connections in passenger and driver area while it's idling .....

after it had been idling for about 10 minutes, opened passenger door to start removing trim to lift carpet, engine stopped straight away, engine system fault. Conicidence !!! tried to start again, wouldn't start same fault. getting a coffee then going to move carpet see whats uhnderneath .... could georgetina be on the money ?

Removed the door sill trims so I can lift carpet to get a look at the wiring loom, nothing evident yet, going to check the junctions that are under the white plastic cover on the left side of the passenger footwell.

I tried to start the engine again, came up with HDC fault, system unavailable this time .... didn't start

Checked the 3 connectors behind the white panel, nothing obvious unfortunately, general visual check of local wiring - nothing.

key in, no clutch pedal, press start
system check in progress
4 bleeps
terrain response system faulty
HDC fault system not available
bonnet open (yes it is)
engine system fault
special programs off
HDC fault system not available
switch off

Last edited by Blitzer on 28th Jun 2020 2:59 pm. Edited 3 times in total

It looks like you start by finding Connector C33N on the Medium Speed CAN. I can't spot anything in common with the other modules, but it may be an earthing problem, as this can cause havoc with Signalling Systems.

I will look later when I have time.
(Edit) Electronic Ground is via Earthing Point G3D135-1 Black/Grey
Earthing Points Diagram is on this thread

https://www.freel2.com/forum/topic32832.html

(Edit) - Power Ground is via Earthing Point G3D133-1
Memory Control Wiring and Earthing are below

https://www.freel2.com/gallery/albums/user...20Diag.pdf
https://www.freel2.com/gallery/albums/user...Wiring.pdf


MS CAN Wiring Cct

https://www.freel2.com/gallery/albums/user...Wiring.pdf FL2 XS SD4 Auto 2010 2012-2017 (21k - 91k miles) (MY2011)
FL2 Metropolis SD4 Auto 2014 2017- (16k - 79k+ miles) (MY2015)
Metro in its 11th Year of (Extended) LR Warranty / Full LR Service History
(Expensive, but Trouble/Worry free - hopefully?)

Last edited by IanMetro on 28th Jun 2020 7:01 pm. Edited 3 times in total