RP1210 adapter setup

Rignos talks to the truck through the same RP1210 adapter your other software uses. It does not ship a driver of its own and does not replace one.

Install the vendor driver first

Install the adapter maker’s software (for a NEXIQ USB-Link, the NEXIQ device drivers) and confirm the adapter works in their tool before you bring Rignos into it. If the vendor tool cannot see the adapter, nothing above it will either.

Choose the adapter in Rignos

1. Open Rignos and go to the connection screen.
2. The list shows every RP1210 vendor registered on that laptop. Pick yours.
3. Pick the J1939 link at the standard speed (250k unless your truck is one of the 500k applications).
4. Connect. The status line should start moving within a second or two.

Rignos remembers the choice per laptop, so this is a one-time step unless you swap adapters.

The address Rignos claims on the bus

Rignos claims source address 0xFA first, and falls back to F9, FD, FC or FB if that one is taken. F9 and FA are the off-board diagnostic tool slots in J1939 — some ECMs only answer requests from those two — and FA is chosen so JPRO or INSITE on 0xF9 can run alongside. You can leave them installed on the same laptop.

On a multi-channel adapter (USB-Link 3) Rignos also opens CAN channels 2 and 3 and claims an address on each. On PACCAR trucks from 2016 the transmission, ABS and cab controller sit on channel 3; a single-channel read sees the engine only. Nothing to configure — switch it off with kenh_phu=0 in the app’s config file if an adapter misbehaves.

If the bus stays silent

• Key on. Plenty of ECMs say nothing with the key off.
• Check the 9-pin cable is fully seated — the usual culprit, by a wide margin.
• Close the other diagnostic software. Some tools hold the adapter open exclusively.
• Try the vendor’s own tool again to prove the adapter, then come back.

More failure modes in Troubleshooting.