What Rignos reads, clears and writes today — and how far each one has actually been taken. We mark what has run on a real truck separately from what has only run on the bench, because the difference is the whole point.
These modules have their own code table built into the app, so a code comes back as the maker words it — not just a number. Figures are how many definitions each table holds.
| Module | Definitions | Source |
|---|---|---|
| Cummins | 12,987 | Calterm |
| PACCAR | 5,636 | Davie, P-code |
| Detroit Diesel | 1,511 | DDEC, description |
| Bendix ABS | 281 | blink, SD-13-4869/4983 |
| Bendix FLR-21 radar | 219 | SD-61-4963 |
| Bendix FLC-20 camera | 114 | SD-64-20124 |
| Meritor WABCO | 151 | blink, MM-0112 |
| Eaton | 52 | FC, TRTS0940 |
| Total | 20,951 | plus 10,365 standard SPN names |
These still read and still clear — you get SPN and FMI with the standard SAE name, just not the maker’s own wording: Allison · International / Navistar · Freightliner · PACCAR CECU · Eaton VORAD · Volvo / Mack.
Real sessions on real trucks, not a compatibility guess from the J1939 standard. Rignos talks J1939, J1708 / J1587, ISO15765, UDS over NEXIQ USB-Link 1 · 2 · 3 (RP1210).
Your truck is almost certainly J1939 and will record even if its engine is not on this list — the list is what we have proven, not a limit. Tell us what you run and we will say plainly what to expect.
Flash reads, writes and verifies an ECM calibration over RP1210, and can bring an ECM back when a write stops halfway. RIGNOS Flash is still in development; this is where it has actually got to.
| Maker | Module | How far | What we have |
|---|---|---|---|
| PACCAR | MX-13 (PC22_1201R08) | Proven on a real truck | Kenworth, write completed 16 Sep 2026 |
| Detroit | ACM GHG17 | Proven on a real truck | 3 trucks written, MCM still powered, 0 foreign frames |
| International | MaxxForce DT (S4I6) | Proven on a real truck | 24 Sep 2026, NEXIQ USB-Link 2 — 0 retries, 0 timeouts, 0 NACKs |
| PACCAR | MT Legacy | Proven on a real truck | real session on PC22_1201R08, reported complete — but the image was not read back |
| International | MaxxForce EDC17 | Bench-tested only | — |
| PACCAR | remaining branches (PRO Standard/151I, PRO 161/161J, 181) | In the catalogue, not yet proven | — |
| Detroit | MCM (EPA7 · EPA10 · GHG14 · GHG17) | In the catalogue, not yet proven | — |
| Detroit | ACM EPA7 · EPA10 · GHG14 | In the catalogue, not yet proven | — |
| International | MaxxForce EDC7 · EIM7 · S3V8 · S4I6Special · S8V8 · NECM2 · IDM2 | In the catalogue, not yet proven | — |
| PACCAR · Detroit · International | ECM stuck in ROM boot | Proven on a real truck | recovery tested on a truck for all three makers (16 Sep 2026) |
Straight answer, because the difference matters when you are planning a job: a read-and-backup path exists for PACCAR and passes our tests, but it has not been verified against a real ECM yet. There is no read or backup path for Detroit or International / MaxxForce — those are write and recover only. We would rather you heard that here than at the truck.