The issue stems from the fact that CVN numbers weren’t checked during previous TÜV inspections. This practice only became standard after the diesel scandal. Logically, if the original CVN is read and then reprogrammed correctly, this error shouldn’t occur. The CVN would match the CALID, assuming Audi hasn’t introduced any issues with their updates. I’ve encountered similar cases where a car supposedly had the latest Audi software and matching CVN, but the TÜV insisted a newer update existed, flagging an error.
In my situation, I’m unsure of the tuner’s exact process, but the TÜV device clearly indicated a CALID match with a mismatched CVN. The question remains: how does the tuner determine the correct CVN? The one they programmed was evidently incorrect.
The initial TÜV feedback simply suggested I had an outdated software version and advised contacting Audi. There was no mention of software specifics. Only after the tuner’s alleged CVN correction did the TÜV inspector indicate potential issues arising from improper software modification, hinting at a suspected optimization.
This problem should be solvable. Many cars with tuning pass TÜV inspection without issue. The fault likely lies with my tuner’s approach. The challenge is ensuring the correct CVN is identified and programmed to align with the CALID and satisfy the TÜV requirements.
