Outlap Docs
Open Outlap

Integrations overview

What works with Outlap: track timing systems, drivers' data loggers, phones, and developer tools such as MCP, embeds and calendars.

Bring whatever timing you already have. Track systems feed an event’s live board while sessions run. Drivers’ loggers and phones fill in their own history, and the board too, when the organiser allows it.

Timing systems for organisers

SystemLiveFileHow
MyLaps Orbits✓✓Enable RMonitor output, run the bridge. Import results or passings CSV.
MyLaps Trackside / X2✓✓Enable the RMonitor / results relay, run the bridge. Import X2 CSV.
AxWare✓✓Enable Monitor output. Autocross runs, PAX and cone penalties supported.
Any RMonitor relay✓✓Point the bridge at the relay’s host and port.
Any results CSVn/a✓Columns are detected automatically; you confirm which driver is which.
Your own system✓✓Post laps or passings to the Live Timing API.

Live streams laps, running order and flags onto the board during a session. File imports a results export afterwards.

Telemetry for drivers

SourceHow it gets into Outlap
Racelogic VBOXImport the .vbo file.
AiM (Solo 2, MyChron, MXS…)Export CSV from Race Studio 3, then import.
RaceChronoExport CSV (v3), then import.
TrackAddictExport CSV data, then import.
Garmin CatalystExport GPX from Garmin Connect, then import.
RaceBoxPair over Bluetooth for 25 Hz GPS in the phone lap timer.
Your phoneThe phone lap timer uses its GPS.

Wherever a file has GPS, Outlap times the laps itself against the circuit’s start/finish line. Details for each logger are in Data loggers.

Platform integrations

esc
↑↓ to navigate ↵ to open esc to close