The algorithm for predictive tracking considers the timestamp when a read is recorded respectively generated. The timestamp when Racemap receives the detection is not used for the prediction.
Possible reasons for a significant difference between the recorded timestamp and the received timestamp of the same read:
There is a delay in forwarding the reads from the timing system to Racemap. Minimize the delay to improve the quality of the prediction.
Settings that impact the timestamps such as date, start time, and time offsets of your event in the timing system do not fit the NOW time.
Predictive tracking with any timing system
The set-up guide checks your settings for predictive tracking. For RACE|RESULT timekeeping system Racemap additionally checks the forwarding of detections with emulated track pings. If the forwarding is configured in RACE|RESULT then the emulated pings are sent back to Racemap.
Intuitive setup guides to correct settings for predictive live tracking
We recommend testing to gain experience with the prediction. We support your test events.
Strategically place hardware along the race course.
1st & 2nd read approx 0.5 & 1 km behind the start.
Place readers along the race course to detect each transponder every 20 min.