Saving the Original CVN (Calibration Verification Number) in MDG1 ECU
The CVN (Calibration Verification Number) saving function for the MDG1 ECU family is designed to preserve the checksum of the firmware when modifying engine calibrations.
This is especially important for vehicles under warranty — during diagnostic checks, the dealer compares the actual CVN read from the ECU with the CVN stored in the manufacturer’s database.
If the CVNs don’t match, the dealer may deny warranty service due to detected interference in the engine control system.
With this feature, you can safely edit firmware without changing the original CVN.
To operate the module, you need a USB protection key ChipTuningPro. To activate the module, please attach a request file.
How to Fix the Checksum
To fix the checksum (CVN):
- Open the required firmware file without changing any calibrations.
- From the “Commands” menu, select “Fix Checksum (CVN)”.
- In the pop-up window, check the “Fix” box and click “OK”.
After this, you can edit the firmware — its CVN will remain unchanged, ensuring your car passes warranty checks at authorized dealers.
Important Notes Before Purchase
- This function may not work with all MDG1 firmware versions. Please confirm compatibility with technical support before purchasing.
- Only the original CVN from the source firmware is saved. Do not use modified files without the CVN saving mode — such firmware will have an invalid CVN and fail dealer verification.
- If the checksum in the open firmware is missing or incorrect, CVN fixing will not be possible.
An activated module or license cannot be returned.
If you have entered the wrong key or device number, the return is not valid. It is not possible to modify the license for another device.
After status update to "Waiting for activation", the data has already been sent to the developer for activation. The order cannot be canceled or corrected starting from this status update.
Pay attention to all information specified in the description of modules and scripts taken from the manufacturer. We are not responsible if the information is not correct or there are some differences from the reality. In the disputed situation, it is necessary to look for a solution to the issue to the manufacturer.
Our store is not responsible for the functionality of the software module. We cannot guarantee the declared functions since we are not the developer.