@nesaru always use a good charger when coding /programming a car. Even if changing CEM parameters don't take much time for programming, the voltage should always stay well above 12V while writing data. And keep in mind that most ecus in your car have only a limited amount of write cycles before the flash memory goes bad, so don't play around to much.

@gad300 type your VIN in the search field on the D5T5 homepage and see what options for engine optimization are available.

@Vauxi the VOE adapter is only compatible with cars that support DoIP (Diagnosis over Internet Protokol). That means SPA, SPA2, CMA plattform and maybe future generations. For the P1, P2, P3 plattform, you will need a DICE(clone), Super J2534, Mongoose Pro or whatever adapter, that supports the J2534-2 protocol. For the P80 plattform you would need an original DICE or a really good quality DICE-clone.

@wenger did you use new or rebuild / remanufactored injectors and the correct parts? Here https://d5t5.com/article/volvo_diesel_injectors you can find some info regarding injector coding.

@Dbend121 the fuel heater isn't designed to run for a longer period of time. If the heater runs continously, you will have a serious risk of fire under the bonet that could seriously harm or even kill you while you're sleeping. The battery would also be drained in no time. So, that's really no good idea. Get yourself a well isolated sleeping bag and leave a window or the sunroof slightly open for ventilation while you sleep, or get a car that is meant to use for sleeping inside, like a camper van or RCV.

Integration in Google Home, Alexa and so on would be great, but I don't think that such feature will be realized in the near future.

@randysw nope. In your case, a software reload with VIDA is needed. But i'm not sure, if this is possible with used modules.

@nesaru the ECM errors are not related to vdash. One of your configuration changes is not compatible with your car. No, Vdash has no checks for this, it's completely up to you, to find out what works and what not.
Revert to the factory configuration, try to delete the codes, and then start to change parameters only one at a time, and see what happens.
In your special case it's also possible that your CEM is dying. It's quite common on V40s.

@Yard007 wrong forum for such questions. Vdash isn't meant for this kind of modification.

@filviktor the PIN will be added to the vdash database, but you won't get to see it.
If your V40 is a P3, you will most likely need to change the IHU with a localized used one. https://svdns.info/2023/08/27/so-youve-bought-an-import-volvo/

@Puppi Wenn du LED's einbaust, hast du permanent diesen Fehlercode. Gibt aber keine Meldung im Kombiinstrument. Original sind Sofitten mit entsprechenden Gehäusen verbaut. Geht denn die Beleuchtung?

@Vulpes based on your description, I think you have a wrong MAF in your car, which would explain your problems.
Vacuum leaks lead to unmetered (not measured by the MAF) air and can cause all kinds of strange symptoms.

@Searchy the HCM for your replacements should have part number 31468411. The original UK ones should have 31395944. So that might be part of your problem. I'm not sure if a software reload is needed when using used parts.

@Vulpes did you do some live data readings while driving? If you see a constant barometric pressure of 1023 mbar regardless of the real outside pressure, you should check the wiring for brittle isolation and the connector of the MAF for corrosion and loose pins,and if they are ok, replace the MAF. You should also check for vacuum leaks, especially at the engine mounts.
Do you run the original air filter box, or some aftermarket cone filter crap?

Most probably incompatible/wrong HCM. What are the part numbers of original UK and the new headlights? And don't mention that you use orbit in the official vdash forum. That's a big red flag!

@spoonVolvo this adapter "should" work. At which exact point is vdash freezing? When you hit the diagnostic button or after you selected parameters? Vdash shows lots of parameters that aren't actually supported by the car it's connected to.
Did you create an exception for the (hidden) vdash directory (C:\Users{your user name}\AppData\Local\VDASH) in your antivirus? Some AV software like AVG, Avast, Norton heavily interfere with Vdash.

@Belos Did you receive a message/email that your pin code was successfully cracked and added to the vdash database?
You should always have a powerfull charger connected while you perform configuration changes. And after changing configurations, you should leave the car alone and locked for at least 15 minutes. What adapter do you use to connect your car and computer?

@spoonVolvo can't follow your link "This Item is not available in your region"
What name does Vdash show in the top right corner, when connected to the car?

@Vulpes have you "blanked" your EGR? And check/clean your MAP sensor. Do these errors appear with the original factory map?
D5T5 uses generic files from Obbe-Tuning. Custom tunes would require datalogging/dynoing.

@spoonVolvo what adapter do you use? DICE, Mongoose, Super J2534....?

@Viktor8989 programming keyless fobs needs the KVM pin which can't be cracked with vdash. Programming is only possible with an official VIDA subscription.