Bosch EDC17 / MED17 checksum fix online
Rebuilds the data-block and sub-range checksums of a Bosch EDC17 / MED17 4 MB read. Upload your file and it comes back ready to use, corrected automatically — the calibration content is never touched, only the integrity value.
Sending costs nothing. We confirm we have your file, run the job on our server and tell you whether we can do it. You decide about paying after that — and you get the same file with a correct checksum.
| Price | 100 credits ($100.00) |
| Accepted | .bin · .ori · .mod · .all |
| Max size | 16 MB |
| ECU families | EDC17C04 · TC1797 |
- The same file back with a correct checksum — content untouched
- A yes-or-no answer on your file before you pay anything
- Works from any machine, nothing to install or license
- Charged per file, only when it succeeds
- No copy of your file is kept, ever
| Cummins calibration | 100 cr |
| Calterm configuration | 100 cr |
| Detroit / Mercedes ACM & MCM | 100 cr |
| Siemens SID OLS280 | 100 cr |
How it works
Four steps, and you find out whether it can be done before you pay anything. What you get back is the same file with a correct checksum.
Upload it here. We confirm on screen that it arrived, with its name and size. This costs nothing.
We run the whole job on our server and answer one question: can we do this file, yes or no. If the answer is no you are told why, and nothing is charged — ever.
Only if the answer was yes. The price is shown before you decide, you tick to accept the payment terms, and the credits come off your balance.
Straight away, in the browser. Your file is processed in memory and never written to our disks.
How you pay
This tool costs 100 credits per file. Credits are prepaid and one credit is one US dollar — 100 credits is $100.00, with no subscription, no monthly fee and no minimum order.
You buy credits with a card or a PayPal account on the credits page, in packs — the larger packs carry a bonus, so a shop doing several files a week pays less per file. Credits do not expire and every movement, spent or returned, is listed in your account. Before any payment goes through — buying credits, or spending them here — you tick a box to accept the payment terms, and they are shown in full at that moment rather than hidden behind a link.
If a job fails after you have paid, the credits go back to your balance automatically and a refund line appears in your history. You are never charged for a file you did not receive.
How Bosch EDC17 / MED17 checksum correction works
This is the family WinOLS handles with the plug-in numbered OLS807 — the Bosch MED17 / EDC17 group on Infineon TriCore TC1797. On North American trucks it is the MaxxForce three- and four-plug ECUs, read out as a 4 MB dump.
The file is built from blocks. Each one opens with a header giving its start and end, and closes with a balance word followed by the marker DEADBEEF. A block is correct when its 32-bit words add up to one fixed constant, so the balance word is simply whatever makes the sum land on it. Smaller sub-ranges declared inside the file follow the same rule, and shadow copies of a block carry a plain byte sum instead.
Edit a map and one block's total drifts by exactly the amount you changed — which is why the ECU spots a hand edit immediately, and why the repair is exact rather than approximate.
The boot and code blocks at the bottom of the file use a different scheme that we have not solved, so this tool leaves them exactly as it found them. In practice that is what you want: tuning changes maps, never code, so those checksums were already correct and stay correct. If yours are broken by something else, this tool cannot repair them — we would rather say so than take your money.
Questions
No. Those use a scheme we have not solved and the tool leaves them untouched. Tuning does not modify code, so they stay valid on their own — this matters only if something else already corrupted them, and in that case this tool will not help.
Yes. Raw ECU reads often have no extension. Upload it anyway — the format check reads the contents, not the name, and it costs nothing.
A full 4 MB read. A partial read does not contain the block headers the checksums are described by, so it is refused before anything is charged.
No. Only the bytes that hold the checksum are rewritten. Every map, limiter and parameter is returned exactly as you sent it — the file comes back the same size, and if you send a file whose checksum is already correct you get back a file identical to the original, byte for byte.
No. The file is processed in memory and never written to disk. Nothing is stored, nothing is indexed, and the corrected file only exists in your browser once it comes back. Close the tab and it is gone.
The credits go back to your balance automatically and a refund line appears in your credit history. You are only ever charged for a file you actually received.
No. It runs on our server, so it works from a workshop laptop, a phone in the yard, or a machine that has never had tuning software on it. There is no licence, no dongle and nothing to keep alive.