Speed In Motion PRO
Platform owner login
Forgot the password? A reset code goes to the recovery address β nowhere else.
Platform owner login
Forgot the password? A reset code goes to the recovery address β nowhere else.
Five wrong passwords in a row. To open it again you need the unlock code, which is written on the server itself β so somebody guessing from the internet cannot get past this.
On the Synology: File Station β simp β simp-unlock-code.txt. It is in the server's log too.
You have been given access to the Speed In Motion central.
At least 12 characters.
Choose the password for your mailbox.
At least 12 characters. Nobody else ever sees it β not even us.
This is the first time this licence server has run. Pick the password you will use from now on β nobody else has one.
It is printed in the server's log. On the Synology: Package Center β
Speed In Motion PRO Licence Server β Log. It is also in setup-code.txt
next to the database.
The only place the module is activated and membership is decided. Every NUC learns its group at its next daily check-in β the centres type nothing. The main centre hosts the group website and runs the group's events.
Pick dist/simp-<version>.tar.gz (built on request, never automatically).
It uploads to this server and is served to the NUCs from here; the checksum is computed during upload.
A fresh publish reaches NOBODY yet β pick the chosen centres below, or release it to everyone.
Big upload keeps breaking off in the relay? Put the file in the simp/releases folder with
File Station instead β it appears here with a Publish button; no .sha256 file needed, the server
computes it from the file itself.
Where NUCs fetch the bundle β the bulk port. Check-ins ride QuickConnect, but a release is too big for the relay, so update offers carry this address. On the centre LAN the local one above is right; give it a public address once the bulk port is forwarded for remote centres.
The port is the one bulk forward on the router β release downloads out, backups in, nothing else rides it, and LAN centres need no forward at all. Saving moves the listener immediately (update the router forward to match). Each centre's copies show under its licence β Manage; a centre online without a fresh backup raises an alert.
Faults the centres reported themselves. Each row is one fault, however many times and in however many centres it happened β a rig switched off or a customer closing the game are not faults and never appear here.
The diagnosis key moved to the Settings tab (owner spec 2026-08-29).
Answers come from the same key as the nightly diagnosis and are grounded in the desk above and the release notes each bundle carries. It reads evidence, never source code.
What centres asked for β support and feature requests, with their screenshots. Book a timeslot, connect at that time from the session below, then mark it resolved.
Open a session on a centre and its NUC dials in within about a minute β the centre does nothing. You get its own admin and command pages, and its screen, in your browser. One session at a time.
Every night running on this server β its centre, its ports, its slots, the server template and the settings it chose. Access is granted per centre (Licences β race nights on our server).
What centres have set to run here, from their own events β soonest first. A night that is cancelled, or moved to a rented server, disappears at that centre's next check-in.
The page that sells the software. Built and changed here with the same kind of builder the centres use β sections, pictures, texts per language β and published as finished pages. No part of the centre software is on it: the site is plain pages and pictures, so there is nothing on it anybody could copy and run.
Every form sent on the website is kept here on the central the moment it arrives β mailed or not. Each one says whether its mail went out; one that did not (mail not set up, or the mail server refused) can be sent again. A demo request becomes a demo login in one click β on the Demo tab, with the name and e-mail already filled in.
Where each form's messages go β several addresses separated by commas; empty = the site's e-mail address below. They are sent through Settings β Email (SMTP), and every message is also listed on the left.
The same settings your centres have in Admin β Website β Search & tracking. Paste an ID or the whole snippet a service gives you β the ID is read out of it. A tracker loads only after a visitor says yes in the cookie banner, which appears by itself as soon as one is filled in. Saved here, live after Publish now.
Each login is its own demo centre with its own data. Everybody who signs in with the same login sees the same screen β and so do you, with Watch & help, without signing in: your clicks land on their screen.
This is exactly what they see. Click and type here as if you sat next to them β they see your orange pointer move and every click land. Nothing you do here signs them out.
Nobody yet.
Everybody who may sign in to this central. Each tab of the top menu is off, view (can look, cannot change anything) or change. A tab that is off does not appear in their menu at all, and the server refuses what it would have shown. The owner account always has everything and cannot be removed.
Tap a level to change it β off β view β change. It counts from their next click; a user who is signed in is not thrown out, the tab simply disappears for them. Settings β change lets somebody see the keys and mail settings β Users & rights itself stays with the owner.
Start from the same rights as somebody else Β· view everything Β· or set them per tab:
The whole central on your phone. It opens this central and nothing else, over an encrypted connection the app checks itself β it accepts only the certificate authority this central uses β and you sign in every time you open it. Who may use it at all is the Phone app switch per user under Users & rights β the owner always may.
Used by the nightly fault diagnosis on the Faults tab. Write-only: once saved, only its last characters ever show again.
Checked with Anthropic before it is stored, so a typo cannot sit there looking fine.
Delivered to every NUC at its check-in and obeyed by the assistant on top of its built-in instructions. The centres never see or edit this. Each NUC's own key is set per licence, on the Licences tab.
Every mail this central sends goes through this one account: security notices and password-reset codes, alerts, the website's form messages and their automatic answers, demo logins and user invitations. Nothing sends until a host is filled in.
Where a password reset code goes. One address on purpose β this one is not a list.
Several addresses are fine, separated by commas. Empty means it falls back to the recovery address, so nothing is ever sent nowhere.
Anything critical still goes straight out β a digest is for the rest, so the inbox stays worth opening.