P3 (V40II, V40CC, S60II, V60, XC60, V70III, XC70III, S80)

Not always the IMMO code can be decoded in order to disable the ITP. On my 2013 V40 successfully cracked the PIN and making changes, but cant find the IMMO code, so I cant add keys or swap media for example.

@make-volvo what exact error codes are present in your car. Maybe your car was tuned/mapped by a former owner. This would trigger at least one of the following DTCs CEM-U030100, ECM-U032700, ECM-U032200

@radoslaw317
Happy to share what I learned over the last few months from mechanics and forums on the Volvo SRS.

Quite a few 2006-2011 S80, V70 and XCs use the same SRS module with part number 31264861.
A gentleman stated this particular module is not VIN-specific in one of the forums.
I believe this is correct as there is no VIN (in plain text) in my EEPROM dump. However, the module serial number and the TEMIC barcode code (only the first 10 characters) printed on the module label are present.
This leads me to believe that the replacement unit's serial no. and TEMIC barcode should be preserved during EEPROM cloning.

Regarding the microcontroller flash, inspection of the 256K flash dump (which contains the software program) reveals the presence of the module serial number, Hardware num, Diag. num, Software num. 1 and Software num. 6 reported by VDASH. However, Software num. 2 is not present in either the EEPROM or the flash.

Important: I learned in another forum that changing the flash content will cause the SRS module NOT to communicate with rest of the system and there are confirmed cases.

The 2012-2016 S80 uses an entirely different SRS module which is VIN specific. See this video for EEPROM editing details: https://www.youtube.com/watch?v=HhEAUVbzBIo
Someone successfully replaced the S60 SRS module, seatbelts and cleared all fault codes after a minor crash: https://www.youtube.com/watch?v=n_PM_DRKoQk

Regarding programmers for the microcontroller (part number 31264861,) I have seen Xprog being used. See one of the images in: https://diagmotors.ru/work-volvo-s80-31264861-srs-repair.php

Thank you for your offer to help. How can I contact you directly? I can do email and Whatsapp.

Many thanks!

Kabziński, nie Kaźbiński.
Pieniądze są zwracane na konto Vdash, aby mógł Pan ponownie spróbować wykonać procedurę po usunięciu przyczyny błędów (samo skasowanie DTC nie usuwa błędu).

What caind of battery support unit you use?. If you use bad battery charger you may dammage you battery or even worst baked your BCM.
Just check if the battery still holding power

To reset crash date in SRS you need first reset locked BCM, this can be done by using the OBD system to clear the stored crash date in BECM then run again SRS crash date reset using Vdash

Thank you very much, will do as you say.

Same as PBM (parking brake module)?

This is what I thought as well. Thank you for the confirmation! 🙂

OBDlink does not work. Regardless what you try. You need J2534 compatible hardware.

@joroartcorp VDASH program. It didn't have the error before

@Alexika there is no direct way to clone to a used CEM. Cloning requires a "virgin" (brand-new/unused), or a "virginized" CEM. Virginizing a used CEM requires special tools and knowledge.

@D5T5-zub I'm experiencing another problem since the update to firmware 0.95.59. My Sensus randomly fails to boot at the first attempt. When I turn on the ignition, I see the boot logo of the Sensus for a longer than usual time, followed by a reboot of the Sensus. This happens maybe 1 of 10 times I start the car and began shortly after the VDD was updated. No DTCs.