Making sense of fault codes?

So this Fl2 went into reduced power (limp) mode on the 16th of this month (and came back after a reboot).
Ive just purchased Gap IID to read the codes, but not seen anything that makes sense.

This is a copy and paste. The only one with the date of the 16th by it is odometer tampering... Which certainly wasn't deliberate so what else is going on?


Thank you. Fault list below -

VIN SALFA27C07H004895
Model L359 - Freelander 2 / LR2 2007
Vehicle scanned on 23 Jul 2020 7:54:50 pm
IIDControl 2.9.9.7 Build 71 Android - IIDTool BT V4.0 B2691

AAM-Audio Amplifier

B1D84-23 (69) Headphone panel 1 - General signal failure - signal stays low

B1D85-23 (69) Headphone panel 2 - General signal failure - signal stays low

U3000-87 (28) Control module - Bus signal/message failure - missing a message

BCM-Body Control

B112C-87 (6C) Interior motion sensor - Bus signal/message failure - missing a message
( on 09-07-2020 15:41:32 at 210157 km )

DABM-Digital Audio

U3003-62 (28) Battery voltage - Algorithm based failure - signal compare failure

U3000-04 (2F) Control module - General failure information - system internal failure

DDM-Driver Door

B109C-15 (6C) Front courtesy lamps - General electrical failure - circuit short to battery or open
( on 09-07-2020 14:43:06 at 210157 km )

ICM-Infotainment

U3003-62 (28) Battery voltage - Algorithm based failure - signal compare failure

U3000-04 (2F) Control module - General failure information - system internal failure
( on 23-07-2020 19:53:55 at 210719 km )

IPC-Instrument Pack

C2002-62 (28) Odometer tampered - Algorithm based failure - signal compare failure
( on 16-07-2020 11:47:18 at 210711 km )

U0208-08 (2C) Lost communication with the seat control module A - General failure information - bus signal/message failure
( on 09-07-2020 15:40:02 at 210157 km )

NCM-Navigation

U2005-31 (28) Vehicle speed - Frequency modulation/pulse width modulation failure - no signal

PDM-Passenger Door

B110B-11 (6C) Rear door passenger side central locking motor - General electrical failure - circuit short to ground
( on 10-07-2020 11:53:22 at 210188 km )

How old is the battery?

Most erroneous fault codes are generated at startup, when the low battery voltage can cause failure or corruption of CAN data.

I witnessed this myself on Sunday, when the battery went flat on cranking, and the word CRASH flashed on the LCD, the locks popped and the hazards came on.

I suspect that if I had an IID BT, then I'd have a similar string of erroneous codes.

I'm not sure, but....

The times when the vehical has gone into limp have always been hours into a long drive on a roads or motorways. It has never failed 5 mins into the trip.

So, what I'm thinking is that, crusing at speed, after hours of driving is when the voltage levels are going to be most stable. Or at least a load more stable than 5 mins after starting on a cold day driving down slow country roads.

I've read elsewhere about the battery issues. I just can't get it to make logical sense in my head that that is the issue.


I cleared the codes last night. The only one that came back on tickover was a steering position sensor. I think I'll need to do some driving and watch what's going on.

Thank you.

Different modules will detect low power at different times, and switch oft, causing loss of comms to that module. Different modules will flag up error messages which may still be current, or occasional problems. Like the seat waning. Over time you will get a number of warnings like this where a fault was detected but its only an occasional blip.

Read the codes and take note of them. Then clear them and read them again. Some codes will be historical and clear. Others will be current and stay present.

Yer iidbt should be able to provide mileage and dates for when the code was first raised. If its an old problem that's still a problem it will come back now, with the old date against it.

Low volts when starting is due to the battery being low, and the volts dropping as the engine cranks. Yer normally get reduced traction or special programs type warnings that mean features like terrain response int working. This can be resolved and proven to be caused by low volts during starting by leaving the engine to idle for 30 seconds then stop and restart the engine. The dash error message will not appear and moving to grass gravel snow will now work. Tick over time will have given the battery the boost it needed.

It wont be a general problem with battery volts unless you have charging problems. It will be start time faults.

Fault codes can be generated at any time. When it goes into limp mode its because it detected a fault at that particular time, which requires system protection. Hence limp mode which restricts max speed and power.

This guy explains a lot about how to make sense of fualt codes:
https://www.youtube.com/channel/UCR73yN7vT7-P541g2qlfRrg
He combines the fault codes and shows you how to get a diagnosis when there are several.