[F32_PiccoloPiccolo]

Try to make control plan in ista on this mistake and see what ista will say

good idea but I will have to wait summer or simply the good weather (those speeds now impossible where I am) before I can get this error code in ISTA+. I had to delete it as I needed to take care to dealer for Service...... Safe is safe.
Nonetheless I did not think DSC could be a factor here and I will also complain with the tuning company for simply having it raised but not removed all together. I guess this is the "quicker and easier" way to do it for them. But I am definitely not happy about it.

[mrproper]

Seems like your tuner did increase KLVMAXO, and changed value of CWDVMX & CWVMAXCOD, but forgot to increase VMAXOVC

[F32_PiccoloPiccolo]

Very interesting the details you provide. Thanks to your suggestion, by googling I also just found that if the coded VMAX-Wert < VMAXOVC, then the content of key value VMAXOVC will be written to vmax_eep.
The question now arises for me whether in order to finish the "V-MAX job" properly....., the DME must be physically removed or whether the tuner can simply do this via software.

[pdc]

Hi

As far as i know the tuner normaly do not use esys with coding to change vmax speed,they instead read ecu map with Ktag or similar tool and change the value of vmax directly on map adress from 275 to 300 or 350 even 400 km/h,but when the speed is greater than 275 triggers the error speed to high.
So the tuner can only avoid that if we erase that specific DTC from DSC ecu map which is not easy for the normal tuner...

[mrproper]

There is no need to remove ecu and do a Bootjob... All Fxx ecus are doable by OBD since years, u just need to know how -
If Im not mistaking some comercial tool developers have released OBD protocol for Fxx a few days ago.