meshO Manager

Appearance

Settings ​

Audience: Event organisers and operators configuring Manager's global defaults.

Reference for every setting on the Settings page, what it controls, and the trade-offs for changing it.

Status: Stub — not yet written. This page should list every visible setting; it will be kept in sync with the Settings UI.

What this page will cover ​

  • [ ] Where the Settings page is and how to open it
  • [ ] Each settings section (one subsection per section in the UI), in the order they appear:

    • [ ] Custom fields (Global registry group) — extra fields recorded against every competitor, beyond the built-in ones. Shared across all events, so the same set is there for every event you run.

      • Each field has a name of your choosing and holds either text or a number. The type decides how the value sorts in a column: a Number field sorts numerically, so 9 comes before 10 rather than after it. Values are always stored as text either way, and a value that can't be read as a number sorts last.
      • Use Move up / Move down to set the order fields appear in, everywhere they are shown.
      • Renaming a field keeps the values competitors already hold. Removing one hides it without deleting those values, so adding the field back under the same name brings them with it — under different wording it is a new, empty field.
      • Fields appear on the Custom fields tab of a competitor, on a Competitor registry entry, and as optional columns in the Competitors list and the Competitor registry table. In the Competitors list they are off by default (turn them on from the Columns menu); in the registry table they are shown by default.
      • Values recorded on a Competitor registry entry follow that person into every event they enter: they are copied onto the competitor when you import entries from Eventor or from an IOF XML entry list, and when you pick the person from the registry in the Edit Competitor dialog. A value already on the competitor always wins, so re-importing an entry list never overwrites a correction you made in the event — it only fills in fields that are still blank.
      • For an IOF XML file, the link relies on the file carrying the athlete's IOF ID. Entry lists exported by Eventor normally do; a file without it cannot be tied to a registry person, so those competitors arrive with the fields blank. Card number and name are deliberately not used for the match, because hire cards change hands.
      • Custom fields are not included in exports — not in IOF XML, results, or splits printouts. They are for your own records.
      • If you have enabled AI assistants (MCP), custom fields are among the competitor details an assistant can read. Bear that in mind for anything sensitive, such as a phone number.

    • [ ] Prime Connection — serial connection to the meshO Prime field unit (COM port, baud rate, retry intervals, "use Prime for radio punches" default)

    • [ ] Event Defaults — values applied when creating new events (start/finish/check unit codes, default event type, competition level, discipline, punching-start override default)

    • [ ] Replay Mode — replay speed for reviewing past events

    • [ ] Logging — log level (Verbose, Debug, Info, Warning, Error)

    • [ ] Eventor — Host Name, API Key, Organisation ID for the Eventor connection

    • [ ] Screen Defaults — defaults for new Leaderboard screens (club display, club icon, auto-scroll, max radios per class, time display options, single-line team members, max places per class)

    • [ ] Radio Punch Forwarding — TCP forwarding of radio punches to external systems (host, port, SIRAP or OE12 protocol, client name)

    • [ ] Radio Punch Listening — accept incoming SIRAP punches over TCP (listen port)

    • [ ] Splits printer — two separate things on one page. Printer connection is the printer — or printers — the server prints on: the Enable server splits printer switch, connection type, paper width, the list of named network printers, and a test print for each. Splits printer defaults is what a printout contains — auto-print on download, whether a mis-punch printout is held while you correct the class and for how long, logo, top 3 places, splits language, and the QR code (its own switch, plus the address, heading and caption) — for every event on the server, and each event can override most of them in Event details → Splits print. The defaults stay available with the connection switched off, because they are also what a download station's own printer prints from — auto-print on download included: it says whether a download prints without being asked, and both the server's printer and a station printing on its own obey it. There are two connection types, and the distinction matters on multi-computer setups:

      • Network printer (TCP) — the server opens a TCP connection to a host and port (default localhost:9100) and sends ESC/POS bytes. Use this for any printer reached over the network, including a printer physically attached to a different computer (e.g. a download station), provided that computer runs something that accepts raw TCP on the configured port and passes it to the printer. This is a list: add as many printers as you have, give each a name for where it stands (Left lane, Women's Elite, Public), and mark one as the Default. Each row has its own test button. The default is where a slip goes when nothing names a printer; each download station can name one instead, in Event details → Splits print.
      • Printer attached to this computer (Windows only) — drives a printer installed on the Windows machine running the server, via the print spooler/driver. "This computer" means the server computer, not the browser/download computer you may be reading these settings on. A USB printer plugged into a download station is not reachable this way — use the Network option for that. Choose the print language (Epson ESC/POS or the Windows driver) and select the printer from those installed on the server.

      The connection type is a single, server-wide setting: the server either prints over the network or on a printer attached to itself. Which network printer a slip comes out on is not — each download station picks from the named list in Event details → Splits print, and stations that pick nothing use the default.

      • Printing to a USB printer on a download station. If you want each download laptop to print to its own USB thermal printer — rather than to one of the server's network printers — use the per-station option instead: on that laptop, open the event's Event details → Splits print tab and turn on Print splits on this station, then pick the printer. This is a per-station setting saved on that computer (not part of the event), so it takes effect immediately and applies to every event you open there. It prints in the browser via WebUSB, so — like card download — it needs a secure connection on any computer other than the server (see HTTPS and certificates). The browser must be Chrome or Edge: WebUSB is a different API to the Web Serial one card download uses, and Firefox has Web Serial but not WebUSB. A station set up this way prints its own downloads locally and the server printer is skipped for them, so there's no double printing. Full guide: Printing splits

    • [ ] Access Protection — optional shared-PIN protection for manager screens

    • [ ] Auto Backup — enable (off unless you turn it on), the frequency in minutes (5, 10, 15, 30, 60), and how many backups to keep per event (1, 2, 5, 10, All — 5 to begin with) — defaults applied to new events; each event can override

    • [ ] Auto Update — automatically download and install new releases

    • [ ] AI assistants — lets an AI assistant read the live event over MCP, and optionally make changes. Off by default; both switches need a server restart. Full guide: AI assistants (MCP)

    • [ ] Video — what this server does with the pictures a camera sends it (cameras themselves are set up on the device holding them, at /info → Camera — see Info screens). Record cameras by default decides whether a camera records as well as showing a live picture, unless whoever sets it up turns that off for theirs; Keep recordings for (days) is how long one is held before Manager tidies it away, with 0 meaning until you delete it yourself; Minutes per recording file is how much each file covers; Picture quality (kbit/s) is what a camera is asked to encode at, with the resulting MB per hour shown beside it; Stop recording below (MB free) is the disk floor recording gives way at, so a full disk cannot take the event down with it; Ride out a dropped connection for (seconds) is how long a camera holds pictures it cannot send and how long its recording waits for it. The panel also shows what this event's video is costing, how much room is left, and where on disk it is — recordings are kept outside the event folder, so they are in no event backup and no cloud sync.

    • [ ] Server — this computer's name/LAN IP, the HTTP port the server listens on (default 5154), LAN access toggle, shareable access links, and optional HTTPS for download/backup stations on other computers (see HTTPS and certificates)

  • [ ] The settings.yaml file — where it is, what's safe to edit by hand, and what isn't
  • [ ] Restoring defaults
  • [ ] Migrating settings between machines
  • [ ] Application folders — where Manager stores events, downloads, backups, and logs on disk