UpdatesGPS trackersLoginFree trial

RACE RESULT

Apply predictive tracking with detections from Track Boxes (active and passive), decoders, and loop boxes.

All about live tracking in the RACE RESULT knowledge base:

Settings in RACE RESULT

Create your event with the required contests in your RACE RESULT account.

Synchronize participants with Racemap:

Tracking channel

Active transponders have to use the same tracking channel as TrackBoxes. Set up with management box, default configuration: channel 1 should be different from channel for timing.

Track Box settings - Forwarding

Set up your Track Boxes for live tracking to directly forward all the Track Pings to RACEMAP: Timing » Systems » Track Box Configuration Rules

Track Box configuration

  • Channel ID: using Track Boxes for live tracking requires a different channel than for timing system

  • Tracking Partner: Racemap

Loop box settings

Loop box detections are forwarded with the device ID of the connected decoder. That means, Racemap has no information, if the detection is received from loop box or decoder.

  • Repeat mode: Detections are forwarded directly and can be used for live visualization.

  • Store mode: Detections are forwarded with delay and can not be used for live visualization, but for the replay of the contest.

Loop box detections are forwarded through the exporters with the coordinates of the

  • decoder OR

  • specific timing point

    Use the automatic timing point assignment rules for these detections (based on loop ID and channel ID), if loop and channel ID have been manually defined in Main Window » Timing Points

Set coordinates for loop boxes, independent from location of connected decoder

Exporter to forward timing points

The exporter forwards reads that are addressed to timing points. Forwarding through exporters is the only way to consider decoders for predictive live tracking.

Settings in Timing » Exporter + Tracking to send data from systems different from Track Boxes - decoder, loop box, USB timing box. Select all timing points. Set tracking partner "Racemap", enter your RACE RESULT customer ID.

To start forwarding click green play button (Timing » Systems » Exporters + Tracking) and each reader forwards a box ping every 4 min. That way your systems are visualized in Racemap Map » Hardware and Detections.

Webinar about predictive tracking with data from RACE|RESULT, thanks Ugo Durand (https://timit.pro/)

Race simulation

Run a Race Simulation in RACE|RESULT, forward the reads from the simulation to your prediction in Racemap and keep dots moving in real-time.

Timestamps: Running a live visualization requires that the settings in RACE|RESULT fit the NOW time (event date, timezone, T0). Common mistake: running a simulation with the date of the upcoming event generates reads with a future timestamp that can not be processed in a live visualization.

set timing points with coordinates close the the shadowtrack of your visualization

Locations: The timing points in RACE|RESULT need to be configured with coordinates close to the shadowtrack of the Racemap event, as the prediction processes the location of the reads.

During the Race Simulation RACE|RESULT does not forward a specific readerID. That means Racemap receives reads from all simulated timing points with the same readerID, but with corresponding coordinates. In Racemap this scenario looks as if the RaceSim reader jumps along the shadowtrack.

Multiple timing points from Race Simulation are interetaed as one reader (RaceSim) jumping along the shadowtrack

If you repeatedly simulate a race in RACE|RESULT and combine it with predictive tracking in Racemap, the transponder codes may be "corrupted" with speed- and location data from previous predictions and unrealistically affect your ongoing Race Simu. You can prevent this issue by changing transponder codes for every Race Simu e.g. 1st Race Simu - 1 to 99, 2nd Race Simu - 100 to 199, and so on.

PreviousPredictive tracking with reads from race timingNextOther timing system

Last updated