MaxxForce file identification online

How it works

Four steps, and you find out whether it can be done before you pay anything. What you get back is a ready-to-use .txt file.

How you pay

This tool costs 120 credits per file. Credits are prepaid and one credit is one US dollar — 120 credits is $120.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 the MaxxForce file identification works

Every workshop archive has them: files called full-off.bin, ecu-copy-2.bin, or a name that described what somebody did to it three edits ago. Opening one tells you nothing — 3 to 10 MB of binary with no heading. Flashing the wrong one into a truck is an expensive way to find out which it was.

The software number is in there. Navistar writes it into the calibration as plain text, eight characters, at a fixed place that depends on the ECU family. This tool finds it and reads it back to you. Because it reads what the ECU wrote, renaming the file changes nothing, and neither does editing it — a file that has been through a tuning session still identifies correctly.

Searching for eight-character text is not enough on its own, which is why a hex editor does not settle this. These files are full of strings shaped exactly like a software number: EDC17C04, EDC17CV42, MPC561, CANS0D00. Those are ECU type names, and they sit in hundreds of different files. The real software number sits in exactly one. That difference, measured across a corpus of 736 real files, is what separates them here — along with where in the file the string sits, whether it is padded into a field of its own, and whether it is written twice.

You also get what else the file will admit to. Siemens and Continental ECUs carry their platform code, so a file comes back marked NS0D00, NS1E00 or NS9800 — the same names your editing software uses for its projects. Bosch EDC17 files do not carry one, but they name their hardware and their build, which separates the release batches. Where the file is a read taken off a truck rather than a library calibration, the engine serial number is in it, and that is reported too. Where Navistar's own records pair that software with an aftertreatment calibration, you are told which one.

One thing is worth knowing before you buy: mileage, engine hours, fuel totals, fault codes and the VIN are not in the file at all. Those are live counters the ECU reports over J1939 or J1708 when a diagnostic tool asks. No tool can recover them from a read.

Questions