Choose Settings on a device's card to open its settings. The fields shown depend
on the device type. Change what you need and choose Save Settings; the device picks up
its new settings the next time it asks for them. The Save button is highlighted while there are
unsaved changes, and closing the window with unsaved changes asks you first.
Settings are saved as a whole. Whatever is in the form when you save is what the
device gets, so check the whole form rather than just the field you changed.
Common to every device
| Setting | What it does |
|---|
| Event Name | The event's name, shown on the device's screen. |
Transponder kiosks
A self-service station where a participant scans their card or QR code, confirms their details, and is
assigned a transponder.
Appearance
| Setting | What it does |
|---|
| Event Logo URL | Web address of the logo shown on the kiosk screen. |
| Background Color | The screen's background colour. |
| Foreground Color | The colour of panels drawn over the background. |
| Text Color | The colour of ordinary text. |
| Button Color | The colour of buttons. |
| Button Text Color | The colour of the text on buttons. |
Timing software connection
| Setting | What it does |
|---|
| Timing Software | Which system holds the participants: Race Result or SportsPro. |
| List API (data/list) | The key the kiosk uses to read participants — a RaceResult Simple API key with list access. |
| Update API (part/savefields) | The key the kiosk uses to write the assignment back to the participant — a RaceResult Simple API key allowed to save fields. |
Participant fields
These name fields in the event. Each must exist in the event exactly as typed.
| Setting | What it does |
|---|
| UID Field | The field holding the ID printed on the participant's card or QR code. This is how the kiosk finds the participant when they scan. |
| Transponder Field | Where the assigned transponder's number is written. |
| Timestamp Field | Where the time of the assignment is written. |
| Kiosk ID Field | Where the ID of the kiosk that made the assignment is written. |
| Display Fields (comma separated) | The fields shown to the participant to confirm it is them, for example FirstName,LastName,Contest.Name. |
| Change Link Field | A field holding a link the participant can use to change their details. |
Reader
| Setting | What it does |
|---|
| Minimum Battery Voltage | A transponder reading below this voltage (2.0–4.0 V) is refused and logged as LOW_BATTERY. |
| Loop Channel | The channel (1–8) of the kiosk's reading loop. |
| Loop ID | The loop ID (1–8) of the kiosk's reading loop. |
| Enable S3 Logging | Also uploads the kiosk's logs to cloud storage. |
Check-in kiosks
| Setting | What it does |
|---|
| Style Profile | The screen's look: Hyrox, SoCal, TimingRobot or PainKllr. |
| Mode | What the kiosk does: CheckIn, Sponsor Kiosk, Presenter, Bulk CheckIn or Chip Check. |
| List API / Update API | The RaceResult keys for reading and writing participants, as for a transponder kiosk. |
| Screen 1 - URL | The page shown when the kiosk is in Presenter mode. |
| Transponder Assigned Field | The field that says whether the participant already has a transponder. |
| Transponder Field, Timestamp Field, UID Field, Kiosk ID Field | As for a transponder kiosk. |
| Sponsor | The sponsor shown in Sponsor Kiosk mode. |
| Comp Day Key | Identifies the competition day being checked in. |
| Transponder Qty | How many transponders each participant receives. |
| Signature | When ticked, the participant signs on screen as part of checking in. |
| Display Reset Interval | How long the screen waits before returning to the start. |
| Loop Channel, Loop ID, Enable S3 Logging | As for a transponder kiosk. |
Presenters
A presenter drives one or two screens, each showing a web page — a results or leaderboard page, for example.
| Setting | What it does |
|---|
| Screen Mode | Extend shows a different page on each screen; Duplicate shows Screen 1's page on both. |
| Screen 1 - URL | The page shown on the first screen. |
| Screen 1 - Resolution | The screen's resolution: 4K, HD (1920 × 1080), 1280 × 800, 1280 × 700 or 800 × 480. |
| Screen 1 - Rotation | Normal, Left, Right or Inverted, for a screen mounted on its side or upside down. |
| Screen 2 - URL / Resolution / Rotation | The same for the second screen. The URL is greyed out in Duplicate mode, since both screens show Screen 1's page. |
Relay devices
A relay device takes times from a connected timing device and sends them to RaceResult. See
Passing Files.
| Setting | What it does |
|---|
| Event ID | The RaceResult event the times are sent to. |
| Connected Device | What the relay is plugged into: HiLink or Timy3. |
| Protocol | The data format that device sends: Microgate or Alge. |
Dual slalom
Controls the start gates and readers for a two-course (red and blue) head-to-head race.
| Setting | What it does |
|---|
| Event ID | The RaceResult event the times are sent to. |
| RR Server IP | The address of the RaceResult server the controller talks to. |
| Red Timing Point | The timing point that red-course times are recorded against. |
| Blue Timing Point | The timing point that blue-course times are recorded against. |
| Gate Mode | The kind of start gate: Magnet - Manual Reset or Pneumatic - Double Acting. |
| Countdown Delay (s) | How long the countdown runs before the gates drop. |
| Countdown Interval (ms) | The time between countdown signals. |
| Impulse Interval (ms) | How long the gate-release signal is held. |
| Default Reader Power % | The readers' transmit power (5–100%). Lower it if the two courses' readers pick up each other's transponders. |