We correct the checksum, so the ECU accepts the file.
Edit a calibration and the numbers that guard it stop matching. Depending on the family the tool refuses the file, the write aborts part-way, or — worst of all — it goes in and the engine faults later. Correcting those numbers is its own job, and it is one we have done down to the algorithm for every family below.
Cummins
Both formats share one checksum scheme. A calibration edited without correcting it is rejected by INSITE before it ever reaches the engine.
Detroit Diesel
Two control units on one truck, each with its own map area. Correcting one and not the other is the usual reason a write looks fine and then faults.
PACCAR
The check lives in the last few bytes of the block — small enough to miss by eye, large enough to brick a flash.
Navistar / MaxxForce
The ServiceMaxx-facing format. We read the software identity out of the file itself, which also tells you what you are actually holding.
Caterpillar
S-record based. Both the record structure and the check have to survive the edit, not just the payload.
Bosch
The widest platform of the lot, and the one most often handed to us half-edited by somebody else's tool.
How it works
- Send the file. The edited one, and the original if you still have it. The original is not required, but it halves the guesswork.
- We identify the family and the map area. This is where most of the skill sits — two files with the same extension can belong to different platforms.
- You get it back valid, usually the same working day. Nothing else in the file is touched: what you edited stays exactly as you edited it.
Your family is not listed
Send it anyway. The list above is what we have solved and do routinely — it is not the limit of what we will look at, and we will tell you honestly if it is outside what we can do rather than take the job and stall.
Checksum work is part of every tuning job we do — you do not need to order it separately when VietDiesel is doing the calibration.