TodesBrote
7th April, 2025, 04:11 PM
Hello there.
ugh. I hate to ask, because i usually want to help other people first before stating my own questions but im at a bit of a roadblock information wise.
Maybe someone here, who is more knowledgable than me, has an Idea or knows something about this.
So, back in October of last Year, my GF bought a Volvo V60 D6. Quite the Unicorn but not known to be unreliable after the AC Compressor issue was sorted by Volvo. Was in absolute great condition and is supposed to have around 162000km by now.
Not everything went smoothly right away, but that was mostly due to a hole in the intercooler which she fixed pretty early on.
However, one thing still didnt work: the ACC (Adaptive Cruise Control). As the car just got a new windscreen the week before we thought it might have been that and booked an appointment with the same company to have them take a look at it. Turns out, they read the DTCs before replacing the windscreen and it was already an issue before they touched the car. So i finally dove a little deeper into the error messages. It became clear quite quickly that the ACC issue was related to them DIM DTC U300045 - Programm memory failure.
From what i gathered this usually happens when the mileage was manipulated and the synching between SRS, BCM, CEM, ECM, TCM etc. to DIM was blocked. VDASH report 0km for all other modules, whereas VIDA reports the correct mileage +-10km on other modules. So the mileage might be correct, but the synchin part still bugs me.
But, as it goes with buying a unicorn, it is pretty hard to actually find information and documentation on this stuff. I have created a EEPROM and Flash dump via P3tool. Its hard to find dumps from the same or almost the same Dash to compare. While i do know that the mileage is (not just) stored at 0x0D00, i havent been able to verify the part whee the Synching routine is stored and what it is supposed to look like.
Thats why im here. I just cant get hold of information that would let me be sure it was manipulated.
Would love to get some input on this, if someone has the expertise and is willing to take a look.
Thank you for your time.
Cheers and have a lovely day.
Edit: Sorry forgot to mention what Dash MCU is used:
MC9S12XHZ384VAG 1M80F
ugh. I hate to ask, because i usually want to help other people first before stating my own questions but im at a bit of a roadblock information wise.
Maybe someone here, who is more knowledgable than me, has an Idea or knows something about this.
So, back in October of last Year, my GF bought a Volvo V60 D6. Quite the Unicorn but not known to be unreliable after the AC Compressor issue was sorted by Volvo. Was in absolute great condition and is supposed to have around 162000km by now.
Not everything went smoothly right away, but that was mostly due to a hole in the intercooler which she fixed pretty early on.
However, one thing still didnt work: the ACC (Adaptive Cruise Control). As the car just got a new windscreen the week before we thought it might have been that and booked an appointment with the same company to have them take a look at it. Turns out, they read the DTCs before replacing the windscreen and it was already an issue before they touched the car. So i finally dove a little deeper into the error messages. It became clear quite quickly that the ACC issue was related to them DIM DTC U300045 - Programm memory failure.
From what i gathered this usually happens when the mileage was manipulated and the synching between SRS, BCM, CEM, ECM, TCM etc. to DIM was blocked. VDASH report 0km for all other modules, whereas VIDA reports the correct mileage +-10km on other modules. So the mileage might be correct, but the synchin part still bugs me.
But, as it goes with buying a unicorn, it is pretty hard to actually find information and documentation on this stuff. I have created a EEPROM and Flash dump via P3tool. Its hard to find dumps from the same or almost the same Dash to compare. While i do know that the mileage is (not just) stored at 0x0D00, i havent been able to verify the part whee the Synching routine is stored and what it is supposed to look like.
Thats why im here. I just cant get hold of information that would let me be sure it was manipulated.
Would love to get some input on this, if someone has the expertise and is willing to take a look.
Thank you for your time.
Cheers and have a lovely day.
Edit: Sorry forgot to mention what Dash MCU is used:
MC9S12XHZ384VAG 1M80F