Volvo XC60 2017 DDM-PDM

[GameTheoryOptimal]

Hey guys!

I have a 2017 Volvo XC60 that I had to jump.
done the job with smok via OBD for dash and CEM synchro.
and done as per smok for the DDM and PDM.
I could read old km in both module via OBD with smok, but could not read eeprom and flash via OBD.
so open both module, read 70F3626 dataflash and flash, proceed to erase all memory and write only flash. left the eeprom filed with FF as per smok.

plug everything back, read value in DDM and PDM with smok again, see a weird number that look likes FF (1656656km let's say). drove the car for a few miles and checked again, now I read the same as dash.
problem is, both my front windows don't work properly (press up or down, it goes up/down a bit, then go back down/up, or just stop... typical like a module which need to initialize windows position) and rear windows and rear door lock don't work at all.

I plugged volvo VIDA online latest software, and even when I initialize windows, same result. battery reset, same result. even tried a software reload with VIDA in DDM, but same result. also... no DTC in any module!

I proceed to read again DDM and PDM, but the memory is exactly how I wrote it, not even one bytes different in dataflash (only FF) and in flash (even after a software reload with VIDA)
(so where smok read that mileage from???)

here are my original read from both module. (and the new read from DDM, but exactly the same as original)
do you guys think we can just edit the eeprom instead of erasing it all? maybe there lies my problem?

thanks for any help!

[Diagcar1]

Looks like the windows need calibration, no idea how it works for a Volvo.

[harius]

46487km in the original DDM and PDM dataflash...

[GameTheoryOptimal]

46487km original and now about 11030km.
but dataflash is still FF all around... how can it read 11030KM? doesn't make sense to me.

and can we modify original dataflash instead of just erasing whole memory?

regards

[Dr. Zoidberg]

doesn't make sense to me.

Harius knows very well what he does, if he tells you that there are 46487 km, it is because there are 46487 ...

[drpeter]

46487km original and now about 11030km.
but dataflash is still FF all around... how can it read 11030KM? doesn't make sense to me.

and can we modify original dataflash instead of just erasing whole memory?

regards

You should erase the D-flash and write the original P-flash back to the box, the ddm and pdm D-flash content will be taken over from the dash after a while (including the new km's!). About the windows problem i had the same with a S60 2012, i calibrated the windows by pressing some buttons, pull window button up and keep it a while up. then release and it will be calibrated if i am right (i tried this without a manual and it worked for me).

[GameTheoryOptimal]

Harius knows very well what he does, if he tells you that there are 46487 km, it is because there are 46487 ...

you misunderstood... i totally agree with him.
but...
if he can read 46487 in dataflash, how comes now I only have FF in my dump, but we now read new milleage via OBD with smok (in DDM and PDM).

I did drive the car for about 30-40km, data in DDM and PDM has update (was reading 46487km first, than 656656km or something, than after a few drive cycle, 11030km), but when I read back, eeprom still all FF and flash is exactly the same as it was. so it looks like DDM and PDM has update memory and took data from DIM (dash), but when I check memory, it doesn't add up.

so doesn't make sense to me.

I tried to do the relearn manually and with VIDA, many times and tried many battery reset, but always similar result.
I will try to spend more time on it tomorrow and keep you guys informed.

You should erase the D-flash and write the original P-flash back to the box, the ddm and pdm D-flash content will be taken over from the dash after a while (including the new km's!). About the windows problem i had the same with a S60 2012, i calibrated the windows by pressing some buttons, pull window button up and keep it a while up. then release and it will be calibrated if i am right (i tried this without a manual and it worked for me).

I'll try to find more info to see if there is not a procedure like that (about holding a button while I hold the windows up switch), but in VIDA service info, they said to only hold windows up and down switch for a few second (like on bmw).

Also guys, door lock doesn't work in the back.

thanks all for your time and help. always appreciated.

[harius]

You do not have to erase the dataflash, but you need to change the kilometers in it... Тhen you do not need to calibrate the windows...

[GameTheoryOptimal]

that is pretty much what I had in mind... if I didn't mess up something else somewhere, I should ''just'' write an edited file and it should be like it used to be. (if I didn't mess up CEM or something...)
if any kind soul in here is able to modify that dataflash so it has 11067km, I would really appreciate your help.

thanks guys!

[harius]

to modify that dataflash so it has 11067km, I would really appreciate your help.

thanks guys!

DDM and PDM 11067km...

[GameTheoryOptimal]

what a boss...
it worked like a charms.
wrote dump, had to initialize power windows and voila!
read the right km and everything is working properly.

thanks a lot for the help guys!

quick question... does anyone have done those CEM properly? (instead of blocking synchro)

[bugarcek]

Can someone tell me pinout for reading this module with vvdi prog

smpkl.jpg

attached smok prog prinout... I tried many variants with my vvdi and allways get bad frequency

[Arvix48]

Hi, need to change mileage in DDM and PDM 303810km to 203770km, thanks

[marina_rv]

NEC 70F3624 ???
read flash NEC.

[Arvix48]

NEC 70F3624 ???
read flash NEC.

there it is..