Soooo... driving around tonight, and I get this red warning ! triangle on the dashboard, with a red temp indicator appearing intermittently 
Immediately pull over and shut down.
Oil temp which I've got displayed on the maxidot all the time, showed 105 degrees, which is perfectly normal.
Water temp showed 90 and has never deviated from that at all.
Waited a few minutes, opened bonnet, checked coolant level - was under the minimum mark, but when I opened the filler a fraction to let the pressure equalise, there was a suction of air and the level bubbled back up to between Min & Max, which it usually does.
Everything seemed normal, switched on again, no warning lights, no bad smells, no leaks, no obvious symptoms, so limped the car gently back home and immediately plugged in the OBD11 dongle (I didn't have it, or the android pad in the car at the time).
Scanned full system - 2 controllers/3 errors showed up as faults.
13 - the cruise control unit - and 17, the dashboard.
The dashboard one I knew about - it is the missing databus message or some such thing, which is the error message for the traffic sign recognition. As soon as I clear that, it immediately shows back up again in the OBD error log, but doesn't re-display on the dashboard/maxidot.
The controller 13 was the concerning one..... it indicated brake temp overheat, and the second fault was another databus message missing (foolishly, I didn't think to take a snapshot of the faults).
The MOST concerning thing was - they were both dated 10th December.
The day of the happy-laps at Willowbank!
I don't recall seeing any warnings on the dash as I was driving around the circuit, and I was eagle-eyed on the dash the whole time looking for exactly that - indications of something wrong with the car.
Since 10th Dec, I've been on holiday in Tasmania enjoying the cold.... and the car has been parked at the airport.
Now - 2 days after arriving back home, this warning decides to display on the dashboard.
So... I've cleared the faults, as they obviously relate to racing around the track like a lunatic.... BUT.... why did it take 3-4 days to actually display on my dash as an error/fault (leaving out the 7 days the car was switched off)?
And a secondary question - in the OBD11 app, it has a listing for "unlearning counter"...... some errors have 164, some have 160 or other similar numbers.
What are these counters? Is this how the dealer will know that someone has been checking/clearing fault codes?
Because I don't want to go clearing too many of these superfluous codes that have been caused by myself fiddling around activating little bits and pieces using VCDS/OBD long coding...... if the dealer is going to end up asking questions.....

Immediately pull over and shut down.
Oil temp which I've got displayed on the maxidot all the time, showed 105 degrees, which is perfectly normal.
Water temp showed 90 and has never deviated from that at all.
Waited a few minutes, opened bonnet, checked coolant level - was under the minimum mark, but when I opened the filler a fraction to let the pressure equalise, there was a suction of air and the level bubbled back up to between Min & Max, which it usually does.
Everything seemed normal, switched on again, no warning lights, no bad smells, no leaks, no obvious symptoms, so limped the car gently back home and immediately plugged in the OBD11 dongle (I didn't have it, or the android pad in the car at the time).
Scanned full system - 2 controllers/3 errors showed up as faults.
13 - the cruise control unit - and 17, the dashboard.
The dashboard one I knew about - it is the missing databus message or some such thing, which is the error message for the traffic sign recognition. As soon as I clear that, it immediately shows back up again in the OBD error log, but doesn't re-display on the dashboard/maxidot.
The controller 13 was the concerning one..... it indicated brake temp overheat, and the second fault was another databus message missing (foolishly, I didn't think to take a snapshot of the faults).
The MOST concerning thing was - they were both dated 10th December.
The day of the happy-laps at Willowbank!
I don't recall seeing any warnings on the dash as I was driving around the circuit, and I was eagle-eyed on the dash the whole time looking for exactly that - indications of something wrong with the car.
Since 10th Dec, I've been on holiday in Tasmania enjoying the cold.... and the car has been parked at the airport.
Now - 2 days after arriving back home, this warning decides to display on the dashboard.
So... I've cleared the faults, as they obviously relate to racing around the track like a lunatic.... BUT.... why did it take 3-4 days to actually display on my dash as an error/fault (leaving out the 7 days the car was switched off)?
And a secondary question - in the OBD11 app, it has a listing for "unlearning counter"...... some errors have 164, some have 160 or other similar numbers.
What are these counters? Is this how the dealer will know that someone has been checking/clearing fault codes?
Because I don't want to go clearing too many of these superfluous codes that have been caused by myself fiddling around activating little bits and pieces using VCDS/OBD long coding...... if the dealer is going to end up asking questions.....
Comment