2Timer
← Back to 2Timer

2Timer Help

Practical guides for humans, with structure that is easy for AI systems to parse.

FinishLynx for Track and Field

Using FinishLynx (track) and FieldLynx (field) with a track and field meet: setting up the shared folder, the files 2Timer writes for Lynx, the result files it reads back, and fixing results that are held for review. Event numbers must match between 2Timer and Lynx.

FlashTiming and Eagle Eye cameras use the same files and have their own entries in the timing list; see FlashTiming, Eagle Eye, and Other Lynx Timing Systems.

Set up FinishLynx with a new meet

  1. On the new-meet wizard’s Systems step (How will you time this meet?), choose FinishLynx.
  2. The first time, choose the shared folder: the folder FinishLynx and 2Timer can both reach, which holds a folder for each meet. 2Timer remembers it on this device.
  3. Under This meet’s folder, the step names the folder this meet’s files go in, such as LynxShare / spring_invitational: by default a folder named after the meet inside the shared folder, or whatever your last meets used.
  4. In FinishLynx, set both the input and output folders to that meet folder, not to the shared folder above it. Do the same in FieldLynx if you use it.

The connection is created with the meet, paused. Nothing is written to the folder until you start it on Connections. At that first start the browser asks to allow the folder again, and if Lynx files are already there, 2Timer asks whether to clear them, keep them, or stop.

Where this meet’s files are

The FinishLynx card on the meet’s Connections page shows This meet’s folder, starting from the shared folder’s name, and how to point FinishLynx at it. Until 2Timer first sends the meet’s files, the card says the folder is still empty. Your browser never tells 2Timer the full path on your computer, so the path starts at the shared folder you chose.

FinishLynx in Settings → Systems

The FinishLynx row in Settings → Systems is where you change the shared folder, see where each meet’s files go, or remove FinishLynx from your systems. You can add FinishLynx there and choose its folder before any meet exists, and make it track and field’s usual timing system.

On a meet’s FinishLynx connection, the folder is set by Shared folder and Meet subfolder, and This meet’s folder below them shows the result.

Files 2Timer writes for FinishLynx and FieldLynx

On the FinishLynx connection, under Push to this folder with Export files on, Files to generate chooses:

  • Athletes (PPL): lynx.ppl, the athlete list.
  • Teams (AFL): lynx.afl, the team list.
  • Schedule (SCH): lynx.sch for track events, and fldlynx.sch for field events.
  • Entries (EVT): lynx.evt, events with their heats, lanes, and athletes.

Export mode decides when they’re written: when the meet changes, on a timed check, or only when you press the card’s button.

Before the meet:

  1. Set up the FinishLynx connection and start it.
  2. Check that the files are in the folder.
  3. Load them into FinishLynx and FieldLynx.
  4. Check that event numbers and entries match.

Field events in FinishLynx files (FieldLynx)

Field events are written to fldlynx.sch, and can also appear in lynx.evt with Lynx field codes such as LJ1, HJ1, PV1, TJ1, SP1, DT1, JT1, and HT1. FinishLynx ignores those, and FieldLynx uses them to pick out the field events. FieldLynx sends results back as LFF files, with marks and each attempt’s wind.

Result files 2Timer reads back (LIF and LFF)

  • LIF files carry track results.
  • LFF files carry field results.

The connection’s Pull from this folder, with Import files on, reads both from the same folder. Watch for files chooses which: Track results (LIF) and Field results (LFF). Results that clearly belong to an entry are applied. Results that don’t are held for review instead of being guessed.

FieldLynx lists every athlete as DNS until the flight starts. While nobody in a field file has an attempt, 2Timer sets no statuses from it. Once anyone has an attempt, an athlete still listed DNS with no attempt is set to Did Not Start, and an athlete with no attempt and no status is left waiting to compete.

You can also load a result file by hand from the meet’s Import… page (Lynx results, at the Standard level). Its Review step shows which rows will be added, updated, left unchanged, removed, or held, before you press Import. If the meet changed meanwhile, nothing is written until you review again.

FieldLynx or FinishLynx results held as Identity Conflict

When a Lynx result can’t be matched safely, for example a long jump result naming an athlete whose bib belongs to someone else, it is held with a status such as Identity Conflict, No Match, Event Mismatch, or Import Needs Review, and nothing is applied. To clear it and accept the result:

  1. On Entries, select the event. The Import Review box says how many results are waiting. Press Open reads.
  2. Open the held result. Its Import Review section offers Apply to Entry for the matching entry, or Skip Result if the row shouldn’t be used.

All held Lynx results are also on the meet’s Data Issues page, under Lynx Results Needing Review, which also offers Apply Suggested Repairs and Repair Structure for event or heat problems. Loading the same file again doesn’t create duplicate issues.

A Lynx result with a bib no athlete has isn’t held: it is recorded on that bib and shows without a name until an athlete is given that bib.

How 2Timer matches Lynx results to entries

  • What 2Timer writes: PPL and EVT use the athlete’s bib as the Lynx ID when there is one; missing bibs don’t block the export. 2Timer also writes its own identity in Lynx’s User 3 field (2T.v1:).
  • What 2Timer reads: it checks that User 3 identity first. Without it, it uses the bib, then an exact name and team, then an exact name that only one athlete has, then lane or position in the heat. User 1 and User 2 are kept but never used to match.
  • Keep event numbers the same in 2Timer and Lynx, and event names matching where you can.

Hip numbers and the EVT lane field

FinishLynx’s EVT file has a lane field for each athlete. For track events, 2Timer writes either the lane or start position, or the athlete’s stored hip number, depending on the meet’s Hip numbers setting. With sequential hip numbers, what FinishLynx shows as a lane may be the athlete’s Hip #. See Hip Numbering.

Combined races (super-events) with FinishLynx

When FinishLynx times one physical race that covers several events, such as boys and girls running together:

  • Combined races are numbered from 10001. Use the super-event’s event number for the race Lynx times.
  • 2Timer sends each finisher’s result back to the event for their division.

For a combined field event, FieldLynx’s LFF file uses the super-event’s number too. 2Timer puts each athlete’s marks on their own event. An athlete in the file who isn’t entered is added to the one event for their gender. If 2Timer can’t tell which event that is (no gender is recorded, or two events take that gender), the row waits under Import Review and names the events. Enter the athlete in one of them, then link the row.

FinishLynx before race day: checklist

  • The connection’s folder is the one FinishLynx and FieldLynx use.
  • PPL, SCH, and EVT (and fldlynx.sch for field events) are in the folder.
  • FinishLynx shows the expected events.
  • Event numbers match exactly.
  • A test result file lands, and the expected event shows the result.
  • Held results show up under Import Review on Entries.

Metadata

  • Last Updated: 2026-10-20
  • Document Version: 0.5
  • Status: Active