Chorus32-ESP32LapTimer icon indicating copy to clipboard operation
Chorus32-ESP32LapTimer copied to clipboard

Published 20 hours ago • verified publisher icon AlessandroAU

[Feature request] Better lap detection

Open Smeat opened this issue 4 years ago • 1 comments

We are currently only using a threshold based approach, where we trigger a new lap as soon as the threshold is reached. I think I don't have to explain, why this isn't ideal. I did some test with a simple max based approach, which showed a significant difference in time (about 50ms): https://github.com/Smeat/Chorus32-ESP32LapTimer/wiki/Data

The original project also has another trigger mode which might be worth a look

Smeat avatar Apr 14 '20 21:04 Smeat

I've had this idea but haven't tried it yet:

  1. Use slightly lower threshold to get a small window of peak data, this would be a window of data where we know a lap is about to happen.

  2. Take the time derivative to get the rate of change of RSSI and use the maximum of that to determine when the lap happened.

AlessandroAU avatar Apr 14 '20 22:04 AlessandroAU