Reading the report

Every block on a Rignos report comes from the session’s own numbers. Nothing on the page is an estimate, and nothing is a marketing claim.

Power and torque

The curve is computed from what the ECM published during the pull — engine speed, load and the reference torque the ECM itself declares. Points with too few samples are dropped rather than smoothed over, which is why a lazy pull produces a short curve instead of a pretty lie.

Fault codes

Active (DM1), stored (DM2) and permanent (DM28) codes are listed with SPN and FMI kept visible, decoded against the table of the module that raised them — Cummins, PACCAR P-codes, Detroit, Bendix blink codes, Meritor WABCO, Eaton. A code carries a source address, and an address other than the engine is not an engine fault; reading an ABS code through an engine table gives a confident wrong answer. Rignos keeps the source with the code, and where no maker table exists it prints SPN/FMI with the generic name rather than guessing. Details in Fault codes, freeze frames and clearing.

The truck timeline

One line per truck, every visit on it:

• Teal marks — a shop visit.
• Gold mark — the calibration’s shop mark changed on that date. Yours, or somebody else’s.
• Red dot — fault codes were present that visit.
• The line itself — measured power across visits.

Tune marks, and why the gold matters

Each session reads the shop mark stored in the calibration. When a truck you tuned comes back carrying a different mark, the timeline dates the change. That is the evidence for a warranty conversation, and no scan tool will give it to you.

Before / after

Two sessions side by side with a delta column: peak power, peak torque, codes. The arithmetic is visible so the customer can check it. If the two sessions were not recorded the same way, say so — the number is only as good as the pull.