Use RSSI data to set a better time on early detected iTags
zingo opened this issue · comments
During 2:nd race test (v0.2) 2 persons that runned together got about 25s diff in time, I watch the unit one of the times when it happened and could see the "first" person was spotetd by the system really early, but the 2nd person was spoted where expected.
Invesigate:
- Look at diff for this 2 persons in all data from race 2
- Look at how RSSI values behave when approaching the unit.
Ideas
- After a detection, watch RSSI values for a short period (20-30s) and pick the time that coresponds to the owest RSSI value. Maybe use some ranges in the picking to remove fluctuating values on same distance.
Look at how RSSI values behave when approaching the unit.
A "live" plot/graph of the BT RSSI was added for the tags: b78a9e5
There are visable peeks when approaching the unit so this can defently be used to "save" a better lap time, e.g. make early detections be moved if there is a stronger signal a short while after first spot as the participand get closer to the unit. Some smothing might be needed to remove "jitter" if participand stand still near the "goal"
Fixed with 92e13ab
Grace period is set to 30s after first tag detection, during this time if RSSI get "stronger" the lap time is updated.