Saved Systems and New Meets

Choose how a new meet is timed and which registration, results, and scoreboard systems it uses on the new-meet wizard’s Systems step, finish connecting what a new meet chose, and keep your keys, sign-ins, and usual systems in Settings → Systems. For adding and running connections in a meet, see Systems and Connections.

The new-meet wizard’s Systems step: how will you time this meet?

2Timer remembers the systems you time, register, and publish with on this device. The new-meet wizard’s Systems step asks How will you time this meet? It lists your timing systems for that sport, then Hand timing, then Another timing system, which opens the rest of the list for the sport and this browser.

Your usual answer for that sport is chosen for you, including Hand timing when that is what you usually choose.
With no usual answer, nothing is chosen and Skip for now moves on. Nothing is remembered, and the meet’s dashboard asks how you will time it.
A timing system you choose is set up with the meet, paused, and marked Set up automatically.
FinishLynx shows its Shared Lynx folder (Choose a different folder). ONETIME shows its Device name, and ONETIME API key when none is saved.

The Systems step: registration, results, and scoreboard

Below the timing question, the Systems step shows Registration, Results, and Scoreboard. Each lists your systems of that kind that work with the sport, with their status, then None, then Another registration platform, Another results destination, or Another scoreboard. Your usual choice is already chosen, with where it came from (“You chose this in Fall Classic, 1 Oct.”). With nothing usual the line reads None. Results takes any number of destinations; None clears them. Under each line, one sentence says what the choice means for this meet.

At the Basic level a Registration, Results, or Scoreboard line appears only when you have a system of that kind for the sport.

The review step lists Timing, Registration, Results (one line per destination), and Scoreboard, each with Change on the Systems step.

What the next new meet remembers from the Systems step

Whatever you leave on the Systems step is what the next meet of that kind starts with, None included. Switch Registration to RunSignUp on a cross country meet, and the next cross country meet starts with RunSignUp; switch it to None there, and the meet after starts on None. A line that read None because nothing was usual, and that you left alone, remembers nothing. Road races and cross country meets are remembered separately. The step says so at the bottom: “Your next … starts with these choices. Change them any time in Settings → Systems.”

What 2Timer sets up with a new meet

What is chosen on the Systems step is set up with the meet, paused:

ONETIME: routes reads to every race’s finish.
A scoreboard such as DisplayWorks: with the receiver you used last.
Results destinations: publishing what they published last time, to the same kind of folder (a folder named after each meet, one fixed folder, or the top folder). Where the destination keeps your organization’s list of meets, each meet always gets its own folder.
RunSignUp: only when your account has exactly one race on the meet’s date and its events pair one to one with the meet’s races, by name or distance. The Registration line names the race and the pairs.
Time Machine: finds its USB adapter when you first start it, and asks only if it can’t tell which one.
Local Files: your browser asks to allow the folder again when you first start it in a meet.

Finish connecting a system the meet chose

A system you chose that 2Timer can’t set up with the meet is still the meet’s choice. The Systems step and the review say why (no race on the meet’s date, a key not saved on this device, no folder remembered for Local Files), and the meet shows Finish connecting and the system:

on the dashboard’s next step, and in its Connections column;
under the system’s heading on Connections.

MyLaps, IPICO, ChronoTrack, and the other file- and server-based timing systems are always finished from the meet, because their form asks for something only the meet can give. Any system is finished this way when it lacked something at creation, or when Set up my usual systems in new meets was off.

Press Finish connecting, and the system’s form opens with everything 2Timer remembers filled in. The line goes once the meet has that connection, or when you choose Not using MyLaps for this meet (with your system’s name). A timing system waiting to be finished doesn’t complete the dashboard’s Timing stage. The choice is kept with the meet, so it travels in a backup.

What new meets start with (Settings → Systems)

In Settings → Systems, the section What new meets start with (“Changes apply to new meets only”) holds your usual systems for each kind of meet.

The switch Set up my usual systems in new meets pauses all of it. While it’s off: “Paused. New meets start with nothing chosen.” The Systems step then chooses nothing and sets nothing up, but what you choose there is still remembered.
Each kind of meet (Track & field, Cross country, Running) is a card that says in one line what it starts with. Open it to change its Timing (Hand timing, one of your timing systems, or Not chosen yet so the first meet asks), Registration and Scoreboard (one of your systems or None), and Results (any of your results destinations).

To stop a system being added to every new meet, for example RunSignUp on every cross country meet, open that kind of meet’s card and set its line to None, or choose None on the next new meet’s Systems step. None of this changes a meet you already created, or removes a saved key.

Your systems in Settings → Systems

Your systems lists what you own or sign in to, under Timing, Registration, Results, and Scoreboard. Each row shows the system’s name, the kinds of meet it is usual for, and one status:

Ready;
Needs a key or Needs a sign-in;
Needs a device name (ONETIME);
Needs a shared folder (FinishLynx);
Needs a folder (Local Files): press Choose the folder in its row, pick the results folder for new meets, and allow access;
Needs plain FTP (see FTP);
Can’t run in this browser, naming what the browser lacks.

Open a row to see its key or sign-in, what 2Timer remembers for it (a device name, a folder, where results go) and where each came from, and when it was last used. A system that needs no key, such as FinishLynx, can be added and given its shared folder here before any meet exists, so the next track meet’s Systems step finds it Ready.

Each heading has its own add action, with the same list and descriptions as the meet’s Connections page. At the Basic level only Timing has an add action.

A system that needs a key or sign-in keeps it in its row in Settings → Systems:

ONETIME and Total Active Sports: Save key, Test key, Remove key.
RunSignUp: Sign in to RunSignUp, Test sign-in, Sign out.
RaceRoster: Save, Test sign-in, Remove saved details.
S3 / R2: Save, Test the bucket, Remove saved details.
FTP: Save, Test the server, Remove saved details.

Keys are saved on each device separately. Removing only the key keeps the system in the list with Needs a key, and nothing is set up with a new meet until a key is saved again. ONETIME’s row also holds Device name for new meets.

Remove a system from this device

Remove in a system’s row takes it out of your systems on this device completely: it is no longer usual for any kind of meet, its remembered values and history are forgotten, and its key or sign-in is removed. It says so before it acts. No meet changes: a meet already using the system keeps its connection.

Earlier versions of 2Timer kept one set of systems for every new meet. On the first open after the update, they were moved once into the systems above, usual for each kind of meet they work with.

Metadata

Last Updated: 2026-10-14
Document Version: 1.0
Status: Active