RIGNOS
RIGNOS DiagAvailable now
Heavy-duty diagnostics for tune shops

Diagnostic reports under your shop’s name.

RIGNOS Diag reads the whole truck at the bay — every module, every code — builds the report in the cloud, and hands your customer a portal branded as your shop. Your name on every page — ours on none of them.

See pricing
New shop accounts are opening soon. Already a customer? Sign in.
How it works

From the bay to your customer’s inbox in three steps.

One desktop app at the truck, one web workspace for the shop, one portal for the fleet owner.

1

Plug in

The Rignos app reads every module on the bus over the RP1210 adapter you already own (NEXIQ tested) — 90+ live parameters, active, stored and permanent faults in the maker’s own codes, freeze frames, a full dyno pull. Works offline in the bay.

2

Upload

The recording lands in your workspace and the report builds itself: summary sheet, before/after tune, engine-brake curve, DPF & regen history.

3

Hand it over

Your customer signs in on your domain, sees only their trucks, and reads a report with your logo at the top. Rignos never appears.

What you get

Built for shops that tune, not just diagnose.

The gold mark on the timeline is a tune. Yours — or, when somebody flashes over your work, theirs. Either way, it’s on record.

White-label everything

Your domain, your logo, your shop name — on the portal, the reports and the emails. Even the login page carries your brand, not ours.

Tune-mark tracking

Every visit, Rignos reads the calibration’s shop mark. If another shop flashes over your work, the truck’s timeline shows the day it happened — JPRO and INSITE can’t tell you that.

Before / after tune

Two sessions side by side: horsepower, torque, codes. The delta column is arithmetic your customer can verify, not a sales pitch.

Expert session reports

Plain-English findings drafted from the session’s own numbers. Nothing reaches the customer until the shop approves it — you review, you sign.

Techs & machines

Per-tech accounts with four permission levels. Machine tokens you can revoke from the office the moment a laptop walks away.

Customer portal

Each fleet owner signs in and sees exactly their trucks — nothing else. Reports stay online; no more PDFs lost in email threads.

Peterbilt 579 — Hargrove Trucking1XP5DB9X7MD456821
Shop visit Tune installed Fault code read Measured power
The app, expanded

It now reads the whole truck, not just the engine.

Every controller that talks on the bus shows up — engine, aftertreatment, transmission, ABS, body and cab — with faults in the maker’s own words, freeze frames, permanent codes, and a dashboard tab the driver would recognise.

Dashboard tab

The truck’s own warning lamps in a strip — check engine, stop, ABS, DPF, DEF, park brake and more — tach and speed dials, boost, coolant, oil, fuel and DEF levels. Lamps have three states, not two: on, off, and this truck does not broadcast it, drawn dashed instead of a false “off”.

Every module on the bus

Engine, aftertreatment, transmission, ABS, body and cab controllers, each named from its own Component ID, each with a card that shows only what that module broadcasts. Reads CAN channels 1 to 3 on multi-channel adapters — on PACCAR trucks from 2016 the transmission, ABS and cab controller sit on channel 3, where a single-channel read never sees them.

Faults in the maker’s own words

Each code is decoded against the table of the module that raised it: Cummins, PACCAR P-codes, Detroit, Bendix blink codes, Meritor WABCO, Eaton — 20,000+ definitions across those six makers, with 10,000+ generic SPN names as the fallback for every other module. Active (DM1), stored (DM2), permanent (DM28), and the freeze frame (DM4) behind each stored code. See the full list →

Clearing codes, with proof

One button sends DM11 and DM3 to each module by address, engine off and key on. The verdict comes from the module’s ACK and a re-read of stored codes 3 and 8 seconds later — “sent” is not “cleared”. Permanent codes are shown for what they are: untouched by DM11 and DM3, and needing the maker’s own tool or the ECM’s own drive cycles.

Guided test scripts

A step-by-step script at the truck: warm-up, settled idle, load pull, road steps if the shop wants them, and a final engine-off code clear. Each step’s result is written into the session, so the report can say which steps were reached and which were not.

Event log per session

Codes appearing and clearing, lamps changing, regens starting, derate and engine-protection flags, engine start and stop — each with a timestamp and the module it came from. Regen and derate questions get answered from the log, not by scrolling raw frames.

One code to activate. Paste a service code from your workspace into the app — no email, no password on the laptop. Codes expire after 15 days by default and can be revoked from the office; a Windows reinstall re-uses the same machine slot. How activation works →
What’s in the box

Three pieces. One subscription.

Nothing else to buy — except the RP1210 adapter you already own.

Rignos for Windows

The app that sits on the laptop at the truck. Reads every module over J1939 — 90+ live parameters, faults in the maker’s own codes, freeze frames, a dashboard tab with the truck’s own lamps — records a full session and writes the report right there. No internet needed in the bay.

Windows 10 / 11 · RP1210 adapter

Shop workspace

The web side your techs live in: every truck, every visit, every session side by side. Tech accounts, machine tokens, customer records, an audit log of who did what.

Any browser · nothing to install

Customer portal

Your fleet owners sign in and see exactly their own trucks — reports, history, measured power. On Pro and up it runs on your domain with your logo, so it reads as your shop’s software.

Included on every plan
Where Rignos fits

It doesn’t replace your scan tool. It replaces the paperwork.

Keep JPRO or INSITE for deep diagnostics and flashing. Rignos is the layer on top: the record, the report and the customer’s copy.

 Dealer scan toolsRignos
Live data & fault codes Yes — deepest coverageYes — 90+ parameters, every module on J1939
Writes to the ECM Yes (INSITE)No — read-only by design
Report under your shop’s brand ×Tool vendor’s name ✓Your logo, your domain
Truck history across visits ×Per session ✓One timeline, every visit
Tells you somebody re-flashed your tune ×No ✓Tune-mark on the timeline
Portal for the fleet owner ×No ✓Their trucks only

Full comparison

Pricing

Priced per machine, like the tools you already pay for.

Billed yearly. Your customer data is yours — visible to your shop only.

Standard

$590 / year
  • 2 machines in the field
  • 1 tech account
  • 1 RIGNOS Link connection at a time
  • Unlimited trucks & reports
  • Customer portal
  • White-label branding
  • Expert session reports
Sign in
Most shops

Pro

$1,190 / year
  • 5 machines in the field
  • 3 tech accounts
  • 2 RIGNOS Link connections at a time
  • Unlimited trucks & reports
  • Customer portal
  • White-label — your domain & brand
  • Expert session reports
Sign in

Priority

$2,390 / year
  • 15 machines in the field
  • 10 tech accounts
  • 4 RIGNOS Link connections at a time
  • Unlimited trucks & reports
  • Customer portal
  • White-label — your domain & brand
  • Expert session reports
  • Priority support — we answer you first
Sign in
RIGNOS Link is included in every plan to reach trucks outside your bay — Standard 1 · Pro 2 · Priority 4 links at a time, 1 during the trial.
About Link ›
Questions shops ask

Straight answers.

Which trucks and adapters?

Any J1939 heavy-duty truck, over an RP1210-compliant adapter — the same one you use for JPRO or INSITE. NEXIQ USB-Link is what we test on. Maker code tables today: Cummins, PACCAR, Detroit, Bendix, Meritor WABCO and Eaton; Allison and Navistar codes show SPN/FMI with the generic name until their tables land.

Does RIGNOS Diag write to the ECM?

No. RIGNOS Diag is read-only by design — the one exception is clearing stored fault codes (DM11 and DM3), only when you press the button, engine off — and the app tells you whether each module actually cleared them. Reading and writing calibrations is a job for RIGNOS Flash.

Does the trial include white-label?

No. White-label is the thing our subscribers pay for, so trials show the Rignos name. Everything else on Pro is open during the trial.

What if I downgrade?

Machines already activated keep working — we never kill a laptop that’s in the field mid-job. You just can’t add machines past the new limit.

Whose data is it?

Yours. Your customers, your trucks, your history — visible to your shop only, never shared between shops.

How do I pay?

Yearly, by PayPal invoice. Ask for an upgrade inside your workspace and the invoice comes to your email — no card details ever go through Rignos. Questions first? Write to rignos@vietdiesel.com.

Longer answers live in the documentation — install, adapter setup, your first recording, and what each number on the report means.

Your data

Your customer list is not our asset.

Walled off per shop

Every query in Rignos is scoped to one shop. No screen, no export and no search crosses from your workspace into another’s.

Read-only at the truck

Rignos listens on J1939 and never writes calibration. The one write it can do is clearing stored fault codes — and only when a tech presses the button.

Two-factor & audit log

Turn on 2FA per account. Machine tokens are revocable from the office. Who created, changed or deleted what is written down.

How Rignos handles your data →

Put your name on the next report.

New shop accounts are opening soon.

Sign in
Talk to us