01 · Before you start
Keep the timing network intact.
Stridelane fits into the timer’s working network. Do not change the timing computer’s IP or subnet, camera addresses, gateways, firewall protections, or any existing timing-device settings.
Create one new dedicated Stridelane Scoreboard output alongside every existing scoreboard object and device. Its blank destination uses local UDP broadcast on the current timing Ethernet.
What each cable does
| Connection | Purpose |
|---|---|
| Stridelane laptop → pacing box USB-C | Loads the selected pace, controls Stop, and reports controller state. |
| FinishLynx computer/network → pacing box Ethernet | Delivers the race clock over the existing timing Ethernet. |
| Pacing box → lights data connection | Carries light-data frames from the controller to the pacing lights. |
| Separate 48 V distribution → lights | Powers the pacing lights. It never connects to the pacing box terminals. |
The intended destination is 255.255.255.255:5000. It does not cross a router. If packets do not arrive, verify output delivery on the timing Ethernet; do not readdress the meet network.
02 · Connect Stridelane
Connect both control and clock paths.
- Power the lights and pacing box. Connect the pacing box’s USB-C data cable to the Stridelane laptop.
- Connect the pacing box Ethernet port to the timing computer or its timing-network switch.
- In Stridelane Control, open Settings → Pacing Box → Connect → Connect over USB. Confirm the intended box is connected.
- Open Racing → Control → FinishLynx, then expand FinishLynx setup.
- Confirm Ethernet link and UDP port 5000. The displayed controller address is diagnostic only; do not copy it into the timing computer’s network settings.
If the app reports Cable disconnected, reseat both Ethernet ends and check link lights and switch power first.
03 · Configure once
Add the Stridelane Scoreboard output.
Production live-clock script · UDP broadcast · Port 5000
- Copy Stridelane_Start.lss into the FinishLynx install/scripts folder. A common Windows installation uses
C:\Lynx. - Open Scoreboard → Options and add a new output. Leave all existing scoreboard objects untouched.
- Enter the exact settings below, save, and restart FinishLynx during setup before meet operations.
| Setting | Value |
|---|---|
| Name | Stridelane |
| Script | Stridelane_Start.lss |
| Port / connection | Network (UDP) |
| IP address / output destination | Leave blank for global UDP broadcast. The script default is 255.255.255.255. |
| Port | 5000 |
| Running Time | Normal |
| Results | Disabled |
It only tells this new output where to send its clock data. Leaving it blank selects broadcast; it does not change the timing computer, cameras, or other devices.
For the related timer settings, see FinishLynx’s official UDP broadcast instructions and Scoreboard configuration.
04 · Prepare the pace
The Ready event is the race that will run.
- In Settings → Track Setup → Edit, choose the actual course length and pace width before creating the race.
- Return to Racing → Control → FinishLynx.
- Add the event name, distance, target time, start mark, and any additional pace bands.
- Put the intended race first in the queue. Stridelane loads it automatically; there is no separate ARM button.
- Confirm the event and targets, then wait for Armed and waiting for start.
This production workflow follows Stridelane queue order. A stationary FinishLynx 0.0 does not start the lights. Confirm the Ready event before starting the race.
05 · Run the race
Start normally in FinishLynx.
- An advancing FinishLynx clock starts the prepared pace. Stridelane changes to Lights running and shows race elapsed time.
- Clock validation and remaining-program preparation use about a two-second lead. Playback joins the correct race position instead of starting late from zero.
- After normal completion, the next eligible queue pace loads automatically.
- Waiting for next race clock means the previous clock has already been used. Reset or arm the next FinishLynx race, then start it normally.
- If a race clock is already advancing before the pace is ready, Stridelane can join it after the pace arms and consecutive samples are stable. Confirm the event first.
06 · Stop and recover
Use Stridelane Stop to stop the lights.
| Action | Result |
|---|---|
| Stop | Stops the lights and records the race as stopped in History. The next race remains pending until Resume. |
| Disarm | Unloads an armed pace without starting it. Resume prepares it again. |
| Retry clock join | Retries joining the current advancing clock after the displayed problem is corrected. |
| Disable Scoreboard output | Stops clock messages only. The production script does not transmit a light STOP command. |
After a false start, Stop in Stridelane, reset or re-arm the FinishLynx event, select or rerun the intended pace, wait for armed status, and start again.
07 · Rehearse
Prove the whole sequence before competition.
- Create a scratch FinishLynx race and confirm Last signal received updates in Stridelane before arming lights.
- Prepare a pace using the actual course geometry and wait for Armed and waiting for start.
- Start from the timing system and observe physical movement, not only the app timer.
- Allow a normal finish, then verify the old race clock cannot start the next Ready pace.
- Repeat with an operator Stop and verify the lights are off and the controller returns idle.
Real FinishLynx broadcast reached the installed Stridelane app and produced observed movement on one powered 25-light string without changing Windows network settings. It did not qualify every fixed-address meet network, full-course installation, or millisecond physical timing.
08 · Troubleshooting
Check the two connections separately.
| What you see | What to do |
|---|---|
| Controller disconnected | Connect the correct pacing box in Settings. Saved queue state does not prove a live connection. |
| Ethernet disconnected | Reseat both ends and check link LEDs, switch power, and the timing computer’s wired adapter. |
| Ethernet address present, no fresh signal | Check the dedicated output, exact script, blank destination/broadcast, port 5000, Normal running time, and delivery on the timing Ethernet. |
| Armed at 0.0, no movement | Expected before a race. Start a new advancing FinishLynx clock. |
| Waiting for next race clock | Reset or re-arm the next FinishLynx event. The previous clock is deliberately blocked. |
| Controller, load, or ACK error | Stop, check light power/data, course geometry, and connected devices, then Resume. |
| Clock starts, app remains disconnected | USB/control and Ethernet/clock are separate. Restore the app’s pacing-box connection. |
Keep camera, adapter, gateway, and device addressing intact. If a dedicated local broadcast cannot reach the pacing box on the timing segment, contact Stridelane support for that installation.