This error code means you have either a cracked/damaged DPF, or a defective particle sensor.
The readiness codes should be green after you drive the car for a while.

@Mange37 UPDATE: this function could also be in the DIM, but i couldn't find such function in VIDA, so it's most probably something else that gives you a warning message.

@Mange37 How about simply trying. Diagnostics and service functions just require a free account and don't cost anything. Connect your car, click on the ECM and see what functions are available.

@TomR what kind of adapter did you use to connect vdash. There are some really bad clones out there, that are known to create problems just by connecting them to the OBD-port.

@Kierzek vdash doesn't support your car.

@Brannon 5 cylinder petrol engines don't need injector coding.

@Bowtiekilla Try to read the car with VIDA. It's working with newer P3 models with a little knowhow.

https://svdns.info/2022/01/15/using-vida-2014d-with-an-unsupported-vin/

https://svdns.info/2021/09/06/vida-2014d-p3-support-up-to-2018-how-to-update-vida-yourself/

If your car is connected to vdash and all modules are showing, you have to click on CEM or BMS. There should be something like reset Battery timer. But if your car is already an ICUP(Android Automotive) one. You need VGM pin for that.

@Miki89 D5T5 doesn't let you see the pin. It is stored in the vdash database so you can use vdash. If you want to see the pin, you would need to decode your car with another another tool like p3tool, or you need to find someone who is able to retrieve the pin via the VIDA/Wireshark-method. But this will cost you money.

@gintasd This basicly means the car is not ready for an emission test. DPF and cat to cold, EGR closed. Nothing to worry about. If you drive for 20-30 minutes and than connect vdash, everything should be green.

@D5T5-zub YV1FZ40LCJ2053368
Dongle 1x333

VIDA now also has troubles communicating with the door modules, so maybe its time to inspect the wiring for me. But there are no DTCs for communication problems nor are there any problems with locks, windows etc...
As said earlier, everything started when firmware 95.00 was installed on my dongle.

@danielraistrick Then everything works as intended. ITP (Infotainment theft protection) detects a module that doesn't belong to your VIN and shuts down the whole Infotainment.
You need to decode the CEM pin, IMMO pin and Security pin with vdash, and than you can disable ITP.
Or you visit a Volvo dealer and ask for the installation of software with the partnumber 31268617, which also disables ITP. But allot of dealers refuse to do this. Atleast here in germany.

@danielraistrick Did you disable ITP-security in the CEM and IHU?

i have excatly the same problem since my dongle was updated to firmware version 95.00, all window commands don't work, before that update everything worked as intended. Vdash also doesn't recognise my door modules since several month while Vida 2014D is communicating normally with them on excactly the same hardware. Third party hardware like two different LAUNCH devices, as well as several android apps through an OBD-Dongle have no problems with adressing the PDM/DDM. It's only Vdash/VDD which doesn't work as intended.