Connect and set up the QR reader
Let a simulator read your customers' QR codes, over a COM port or in keyboard emulation, and check that the reader responds.
The QR reader is what opens the simulator to the player: it reads the ticket, IGNITION has it checked by NEXUS, and the simulator unlocks. IGNITION recognizes most USB readers on its own; usually you only need to plug it in and do a test scan.
The two ways a reader talks
A QR reader transmits what it reads in one of two ways:
- Keyboard emulation (HID): it "types" the code like a keyboard. This is the factory setting of most USB readers.
- COM port: it sends the code over a serial port, a virtual one for a USB reader.
By default, IGNITION listens to both at the same time: you do not need to know how your reader is set up. The same code received through both channels is only counted once.
Check the reader
Plug the reader into the simulator.
On the unlocked simulator, tap the ⚙ button at the top left. If a PIN code protects the settings, enter it. Open the System tab, QR CODE block.
Check that Enable the QR code reader is ticked and that Reader input channel is set to Automatic — COM port and keyboard emulation.
Click Detect the scanner by scanning a QR code, then scan any QR code within 20 seconds: the one in the reader's manual will do.
Click Save.
photos/en/borne/parametres-code-qrIGNITION System tab, QR CODE block, after a successful detection in keyboard emulationResult
IGNITION shows "Reader detected in keyboard emulation (HID)." or "Scanner detected on COM3." (the port varies). Once the simulator is back on its screensaver, scan a valid ticket: it must unlock.
Good to know
- The reader is ignored during the race: nothing it reads is taken into account while Assetto Corsa is running or the results are displayed. A code scanned by mistake in the middle of a game has no effect.
- Re-scanning a ticket on its own simulator locks it, and a new scan unlocks it, without deducting anything from the credit.
- The same code is only read once within 1.5 seconds: a reader that "stutters" does not create two sessions.
- A reader in keyboard emulation cannot report that it is unplugged: only a detection confirms it. A reader on a COM port, on the other hand, reports its failure to NEXUS.
- The advanced settings (baud rate, parity, keystroke delays) are in Advanced settings. They are a last resort only; detection is enough in most cases.
Without a reader
If you untick Enable the QR code reader, no QR code is read any more, including command QR codes. The simulator is then opened from NEXUS (Simulators) or in free access, and each session lasts the Default session duration set in NEXUS.
Troubleshooting
During detection
| Message | Cause | Solution |
|---|---|---|
| "No reader transmitted, neither on a COM port nor on the keyboard." | The reader did not transmit anything. | Check the cable and that the reader beeps on each scan, then run the detection again. |
| "Scanner found on …, but the baud rate does not match." | The reader goes through a serial adapter at a different baud rate. | Enter the baud rate given in the reader's manual in Advanced settings › Baud rate. |
| "No COM port is available on this machine, and nothing was typed on the keyboard." | Reader missing, or port held by another program. | Plug in the reader, or close the program holding the port. |
At the simulator
| Message | Cause | Solution |
|---|---|---|
| "Internet connection lost — try again in a moment." | The simulator can no longer reach NEXUS. | Check the center's connection. |
| "This simulator is already in use with another ticket." | Another player is using the simulator. | Wait for the end of their session, or re-scan their ticket to free it. |
| Nothing happens on scan | Reader unplugged, or input mode too restrictive. | Run the detection again from System › QR CODE. |
Rejections related to the ticket itself (expired, used up, wrong simulator type…) are explained in Understand a QR code rejection at the simulator.