FinishLynx for Track and Field

Purpose

Explain the shared Lynx workflow in 2Timer, including LIF and LFF imports plus the outbound files used by FinishLynx and FieldLynx.

Prerequisites

FinishLynx connector configured.
T&F meet events created in 2Timer.
Event numbers aligned between 2Timer and FinishLynx.

Standard File Exchange

For T&F meets, the usual pre-meet exchange is:

PPL for athlete / participant list
SCH for track schedule
fldlynx.sch for field schedule
EVT for event definitions and entries

Before the meet starts:

configure the FinishLynx connector
export the needed exchange files
load them into FinishLynx
confirm event numbers and identities match

Result Imports

During or after competition:

LIF files carry track-result data
LFF files carry field-result data

2Timer reads both file types from the same Lynx exchange folder and applies results back to the matching entries.

Matching Requirements

The most important rule is consistency:

event numbers in 2Timer must match FinishLynx
bib numbers must match the athlete or entry records

When those identifiers drift, results will not link correctly.

Super-Events and FinishLynx

If FinishLynx is timing one combined physical race for multiple sub-events:

export using the super-event event number when that is the race Lynx is timing
let 2Timer route the results back to the appropriate sub-events when supported

Field events can still be exported in lynx.evt, but they should carry Lynx field designators such as LJ1, HJ1, PV1, TJ1, SP1, DT1, JT1, and HT1 so FinishLynx ignores them and FieldLynx can isolate them.

Before Race Day

Verify:

connector path is correct
PPL, SCH, and EVT exported successfully
FinishLynx loaded the expected event list
event numbers match exactly
a test file import lands on the expected event

2Timer Help