Clock Resetting

[manca]

Hello All

Can anyone tell me why my clock keeps resetting itself. It must be 80% of the time. It only happens when I get in the car. It mainly goes to 0:00 but just for the hell of it will sometimes pick something completely random. Date is often wrong as well, and usually sticks at the last date I used the car. Time will go wrong without affecting the date but date never goes wrong on its own. I can't set it to Radio or whatever the setting is, it just goes to 0:00 when I do that. Running latest firmware, but don't have any of these cable things to check anything with.

Thank you (and Happy New Year).

Adam

[snapdragon]

Mine does it if I leave the sidelights on such as when parking somewhere dark and get out the car and lock it. There was a radio software fix for this, but it didn'tw ork for me and I have the latest SW.

[manca]

I don't appear to have any rhyme or reason to explain mine. Lights on or off, wipers in auto or off. Open door using fob or handle (and any handle). Use the key or the start button. Daylight night time... lights programmed to say on or go off.... I doubt I've tried every variation but all the same.
I've run the gambit of ritual dances, talking to it in German. I've tried sacrificing chickens and goats (I'm still on the lookout for a virgin.... )
All seems a bit ridiculous really .
Definitely wasn't as bad when I first got it. If no-one can point to a likely cause I'll have to run it into a stealers

[limoncello]

only tsb i can see for clock being wrong like this is as snap says ussually due to sidelights being on when key taken out.

you could try the fix its quite simple but doesnt always work, its a quick bit of coding with vcds

however there is a proviso that on MY2006 cars produced from 12/05 and with the software data version 0400 or 0410 where the fix is to Update to software version 0420 (or higher) via the software version management (SVM) ie only done at the dealers

details of tsb are roughly here http://www.audi-resource.com/faq/con...is-wrong.html?

[manca]

Thanks very much limoncello

Mine is a facelift 2005 car registered in May. I guess produced before 12/05. I'll need to look up how to check my software version. I remember reading sometime ago that the lights could cause problems. I went through a period of ensuring they were off before switching the car off but it didn't cure anything. I'd also swear the clock doesn't wait 1.5 hours to reset itself but I might be wrong so will check.

[Adrian E]

I'm fairly local to you and have the latest update discs if you want to run them through the car - also have an old copy of VCDS and a clone cable which worked fine on Audifin's D3 4.2d the other day

[manca]

Hello Adrian That's a very generous offer thank you .

I haven't had a chance to look anything up yet. I'm assuming the software version limoncello has advised about is different to my having upgraded the MMI. Assuming I can find out somehow without the need for additional cables, I can check over the weekend what version I have .

[Adrian E]

Sounds like yours is the earlier type so the VCDS coding change and then a software update should resolve. I've done some coding on the instrument cluster on my D2 for the radio clock module so the actual coding change should be extremely simple.

[limoncello]

with the earlier model car the fix is supposed to be the coding change only. not the software update, but its worth looking to see what version f/w is being used in the module. as the tsb car "years" doesnt take into condifderation that the module may have been replaced. so possibly might benefit from the software upgrade

[snapdragon]

Thanks limoncello, that's the TSB I knew I had seen but couldn't remember.
Looking at my coding and the TSB link you supplied, maybe I will try putting the 8 on the end instead of 3

Address 17: Instruments Labels: 4E0-910-xxx-17.lbl
Part No SW: 4E0 910 950 P HW: 4E0 920 950 P
Component: KOMBIINSTR. VDO H71 0400
Revision: D02 Serial number: AUDID3ED000392
Coding: 0032413
Shop #: WSC 00097 210 17577
VCID: 31629C61A8327B1