@ZaanTerror fixing the IE mode problem might be hard to impossible. But still good luck with trying it.

You should also clean the list of VINs in the vehicle profile tab. To do this you have to create 2 text files.
The first one needs the following 3 lines:

pause
osql -S (local)\VIDA -U sa -P GunnarS3g3 -i clearVINS.sql
pause

and has to be saved as .bat file. For example clearVINs.bat

The second file has these 3 lines:

GO
delete from recentVINs
GO

And needs to be saved as clearVINS.sql

Executing the bat file cleans the list of VINs without breaking anything.

@skuzeri the VDD servers suffer from heavy Ddos attacs from time to time. It seems like this is actually happening again. I have the same problem.

After checking the install instructions in VIDA, I think the software is needed for the AEM and has nothing to do with "call start" shown in the CSC tab. You might want to create a support ticket and ask if vdash is able to help you.

@Jannek I checked the manual for your modelyear. Your car doesn't support remote start. So it's correct that vdash doesn't show this option.

I created a VMware VM with WIN11 25H2 to test this. Installation worked perfect, but i noticed 2 problems.
VIDAMonitor errors out at system boot with an error "Can't connect to database". Switching the start type of the SQL service from "Automatic (delayed start)" to "Automatic" solved this.
The desktop link to start Edge in IE Mode doesn't work. Had to manually enable IE Mode and add localhost/vida. Additionally i used this https://github.com/LesFerch/IEModeExpiryFix to make this permanent instead of just 30 days.

Look under Clima and Heating.,There are the options for remote preconditioning or remote fuel heater start. But I'm not sure if this is available/working for P1s.

The combination of all 3 codes indicate a problem with the map sensor.

Check your swirl flaps and clean the map sensor located at the intercooler.

Get a DICE-clone/Mongoose JLR pro/Super J2534 adapter, a Laptop with Windows 10/11 and internet access, a charger that is able to maintain a constant load of 8 Ampere. Connect everything to your car, switch the ignition to pos. II (ignition on, engine not running) , start vdash, log in, click the connect button in the top left corner, click the decode CEM button, click the green button somewhere on the left. Wait for up to 24 hours until the PIN is decoded. The car goes into programming mode while the decode is running and can't be locked or used in any way. You can pause/restart the decoding at any point, the progress is stored on the vdash servers.

@Kapa what are the first 2 digits of your dongle serial number? 1x, 2x or 3x? The serial is shown in the VDD app under the settings tab.

@joroartcorp remappings/tunes for the ECM/TCM and changes in the CEM configuration are two completely different pairs of shoes when it comes to software updates with an official VIDA.
Mappings/tunes are only overwritten/deleted when a reload/update for the ECM/TCM is installed.
Changes in the CEM configuration get overwritten with the original configuration known to the volvo servers with every software update/reload that is performed with VIDA for any ecu in the car.
Normal diagnostics or activating service functions does nothing/keeps everything as is.
Additionally most tunes/remaps create a permanent checksum error, which tells the guys working with VIDA that the ECM/TCM was modified, so they won't perform updates/reloads without consent of the owners.
All the above is only valid for P1, P2, P3 cars. On SPA and newer any configuration change/tune is detected whenever VIDA gets connected and can lead to a blacklisting for software and OTA updates until the original software is present in the car.

@Oleksandr1540 DIM-U300045 is the result of milage manipulation. Vdash should provide a software reload to fix this. Just connect your car to vdash and click on the DIM. There should be an option to perform a software update/reload. Use a Mongoose JLR or Super J2534 adapter for this. Don't do this if your adapter is a Vxdiag/Vxnano, or you will brick your car.

@ALEX-ch do you have a "sponsored" or "small home" account? If you have a sponsored account, you have only limited access and need to contact the support to enable the options you want to purchase. Or buy a config subscription for your car, if you want to change more than one thing.

The CCM was replaced with a used part that isn't configured like the original part (one of the 3 buttons in the middle of the lower row of the CCM doesn't match your CEM configuration) and also didn't perform LIN discovery. So the damper module DMM doesn't work/communicate with the CCM.

@Steve2 did you buy the correct key with the correct frequency for your car? And does your car have keyless entry or not? Did you decode all necessary pins?

When exactly did those errors occur? The massive amount of communication errors looks like a voltage problem. Or did you try to perform a configuration change while the engine was running?

@T5-T6-Schnappi did you clone the software of the old module to the new one before running the SRS reconfiguration? This is mandatory for the process to be successful. Read here https://d5t5.com/article/srs-config

@jv vdash isn't 100% bullet proof. It's possible that the reconfiguration messed something up. Your codes basically mean that the software configuration isn't compatible with the hardware of your car.
This can be caused by a wrong CEM configuration or wrong software in a module. I don't know what the vdash SRS wizard actually does and if it tampers parameters in the CEM or SRS, but it's possible that it didn't work as intended. It's also possible that your car hasn't been at the dealer for a longer time and lacks some software updates, while the donor module had newer software that is incompatible with the rest of your car. You might need to visit a dealer, or someone with an official VIDA subscription, who can look up the fault codes and fault trace to possibly solve your problem if the vdash support doesn't come up with a solution.

@jv did you compare the software numbers of the old and new module? Same hardware doesn't mean same software.
Did you do any configuration changes besides SRS reconfiguration?
Did you have a powerfull enough charger attached to the car while running vdash?
Did the donor car have exactly the same safety features than your car? U230055/U230056= wrong configuration / missing hardware or sensors.

@nesaru that's really strange. Did you try to disconnected the battery for at least 1 hour? The code means no communication between SRS and CEM, or incorrect CEM configuration. Maybe your seatbelt reminder config is incompatible with your car. Vdash has no compatibility checks for this, so you could have applied a wrong/incompatible config.
The S40 is really sensitive to undervoltage, so your errors were most probably phantom errors due to low voltage.