PACCAR MX-13 file identification online
Reads the calibration, gearbox, rear axle ratio and power rating out of an unnamed PACCAR MX-13 file. Runs in your browser against our server — there is nothing to install and no licence to keep alive.
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 a ready-to-use .txt file.
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.
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 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 PACCAR MX-13 file identification works
MX-13 reads arrive named 128.bin, or read_PC4__1408P151I_1XK…bin, or with no extension at all. This opens one and tells you what it is: the calibration ID, the full software string, the PCI number that identifies the engine rating, the platform code, and the fourteen component part numbers the truck was built with.
It also reads the two things that decide whether a file belongs on the truck in front of you. The gearbox setting — manual, automated manual or fully automatic — and the rear axle ratio, straight out of the vehicle configuration record. Put the wrong pairing in and the shift strategy fights the driveline.
And it gives you the rating. The torque limit tables are read out in full, and power is worked out from them the ordinary way, torque times rpm over 5252. Taken at the rated point rather than the peak of the curve, that lands within about one percent of the published figure, so the tool names the closest factory rating alongside the calculated number. When nothing is within three percent, it says so — that file has been worked on.
Those torque tables are worth a second look on their own. A stock file has two of them and they differ. A file whose top table has been pulled down has two that match. You can see that here without needing the original to compare against.
The checksum is verified in passing, so the report also tells you whether the file is intact — useful on a file that has been through somebody else's editor.
One limit worth knowing before you buy. The earliest MX-13 reads, the EPA10 ones, store no text inside them at all: no calibration name, no software string, no PCI number. Those are refused at the quote step and charged nothing.
Questions
It is calculated, not looked up, and it lands within about one percent. We show you both: the number the tables give and the closest factory rating to it. There is no published PACCAR table mapping the PCI number to a rating that we have been able to obtain, so we would rather show our working than pretend to a precision we do not have.
It gives you two strong signals rather than a verdict. A power figure that matches no factory rating within three percent, and the top two torque tables reading the same when a stock file has them differing. Both are worth acting on; neither is proof on its own.
Yes. Reads taken off an MX-13 often have none. The check reads the contents, not the name, and it costs nothing.
Yes. There the calibration sits at its real flash address with everything before it erased, and the tool finds it rather than assuming a fixed position.
No. None of those are stored in the file — the ECU reports them live over J1939 while it is connected. What is in the file is the calibration and the vehicle configuration, and that is what you get.
No. The file is processed in memory and never written to disk. Nothing is stored, nothing is indexed, and the result 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 machine in the yard, or a computer that has never had manufacturer software on it. There is no licence, no dongle and nothing to keep alive.
| Price | 120 credits ($120.00) |
| You upload | .bin / .ori / .mod |
| You get back | .txt |
| Max size | 16 MB |
| Applies to | MX-13 EPA10 · MX-13 EPA13 · MX-13 EPA17 · Delphi · OLS810 |
- A ready-to-use .txt file, in seconds
- 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
| NavKal .zenc decrypt | 250 cr |
| NavKal .zenc rebuild | 250 cr |
| INSITE .eif opener | 120 cr |
| INSITE .eif rebuild | 120 cr |
| MaxxForce file identification | 120 cr |