Do you have any symptoms?

Do the codes have any dates or mileage (well, km) against them?

 

I think I would clear all the codes, drive the car around for a few days and then read the codes again.

A lot of them seem to be historic.

 

Although allegedlly you're not supposed too, that's exactly what I'd do 100%

It'd at least give you a much clearer indication of what's going on.

Take note of all the codes beforehand obviously

Jim

 

If you're not using SDD, and won't be daft enough to use franchised dealers, no harm in deleting all fault codes.

If you do use SDD or franchised dealers, might not be best idea, and you want to look at the dates/mileage of the codes to see if any are recent.

 

Seems its had a flat battery in the past - all historic codes seem to relate to that. Clear All of them and and rescan the whole car to see what comes back .................then post the results.

 

I can't really help with any of the codes but if you are anything like me you may wish you had never plug it in now

 

The codes come from my icarsoft v3.0 scan tool. The data which I posted earlier is all the scanner gives to me. I already did the obvious - I deleted all errors to see what comes back.
Symptoms:

• Recently a blackout of the instrument panel for roughly 2 seconds. It did come back to life without any intervention. For a short time (maybe a second or two) ALL error lamps were on too, but they cleared and the car did go on as if nothing happened at all. A very frightening event!
• TV and DAB+ never worked for me. The module seems shot. Fuse is OK.
• I recently replaced the passenger door lock. The errors relating to the door are probably from the time before, when the door lock was erratic.
• Sometimes when the car sat in the summer heat, the drivers side map lamp switches itself on and sometimes even refuses to go off.
• One of the front parking sensor intermittently goes crazy and beeps as if I touch something. Needs replacement I guess.

 

As a general rule the user interface is designed to let you know if anything important has happened, and then a code reader can be used to tell you why the light came on; chasing codes when nothing is broken is a fools errand.

This is one of those occasions where too much information is dangerous: error codes don't mean that action is necessary.

Our cars were - for good or ill - built primarily to meet the desires of automotive engineers, not electronics engineers. As a result the electronics have foibles. This means that sometimes things start up in the wrong order, or too slowly, or erratically. This results in an error as system 1 can't see system 2 etc., etc., etc. Next reboot (engine off, wait, engine on again) the problem will have likely gone away, as this time everything has been forewarned and therefore are paying attention when they start up. Or a different sequence may lead to slightly different (but equally uninformative) error codes.

What you need to do is only monitor codes that happen after you have set a baseline, and even then you can probably ignore most of them (particularly the "Lost communication with the digital audio control module B" type of thing, which in your list above is pretty much all of them)

 

This post is perfect timing for me. As a complete scan tool novice, I’ve just yesterday used an LR 3.0 on my 2013 XKR & scared myself silly at the amount of codes. I don’t have any standing warnings, but was searching for history of an intermittent pedestrian protection system fault. Many of the historic codes are similar to the OP’s, so I’ll sit back & chill.
Ta.

 

Surely the scanner reports date or mileage though. Given the car is designed for SDD diags, iCarsoft is a bit naff if they don't report that simple info!