Getting started
Install Rignos for Windows
Rignos has two halves. The desktop app goes on the laptop that visits the truck;
the workspace is a website, so there is nothing to install for that.
Before you start
- Windows 10 or 11, 64-bit.
- An RP1210-compliant adapter with its vendor driver already installed — the
driver comes from the adapter maker (NEXIQ and friends), not from us.
- A Rignos account. If your shop just signed up, the owner’s email and password are
what the app asks for.
Install
- Download the installer from the download page and run it.
Windows may warn about an unrecognised publisher on a fresh release — choose
More info → Run anyway if the SHA-256 matches the one we publish.
- Launch Rignos. The first screen asks for your account.
- Enter the email and password of your Rignos account. If that account has
two-factor sign-in switched on, the app asks for the 6-digit code as well.
No code to copy. Older builds made you generate a 48-character
token on the website and carry it over. That is gone: signing in registers the laptop as a
machine and it collects its own token. The manual token field still exists for the case
where somebody sets a machine up remotely for a customer.
What activation actually does
Signing in creates a machine row in your workspace, named after the computer.
That machine holds the token the app uses from then on. You can see it, rename it, attach
the customer’s email and engine serial to it, or revoke it — all from
Machines & tokens in the workspace.
Your plan caps how many machines can be active at once. The cap is enforced at
activation, not just in the web form, so a shop cannot quietly go over it.
Reinstalling Windows
Sign in again with the same account on the same computer name and Rignos re-issues the
token into the existing machine row instead of creating a second one. The old token dies
at that moment. This matters: without it, every rebuild would burn one of your machine slots
until somebody noticed.