44LikesLapMonitor Lap Timer
05-11-2019 | 08:12 AM
#17
05-16-2019 | 08:15 PM
#22
Joined: Oct 2004
Posts: 3,360
From: Michigan
LapMonitor is successfully used in Turkey to time 1:8 nitro and brushless national championship and it is a very sunny country
Sun can slightly reduce the range (mainly if facing sun at sunset or sunrise) but it works well under sunny conditions
If you notice any miss lap, you can easily change LapMonitor location on the track to keep on getting good detection as LapMonitor has a long bluetooth range
Sun can slightly reduce the range (mainly if facing sun at sunset or sunrise) but it works well under sunny conditions
If you notice any miss lap, you can easily change LapMonitor location on the track to keep on getting good detection as LapMonitor has a long bluetooth range
05-16-2019 | 08:40 PM
#23
https://lapmonitor.com/store/en/12-lap-timer
05-16-2019 | 09:05 PM
#24
Joined: Oct 2004
Posts: 3,360
From: Michigan
looks like $135 with 1 transponder. Individual transponder are $35 each. I didn’t go to the full checkout procedure, but showed free shipping.
https://lapmonitor.com/store/en/12-lap-timer
05-16-2019 | 09:10 PM
#25
Thanks for the post. I have a nice backyard track and use a phone app that will record and broadcast via bluetooth one car at a time on track. My racing has improved dramatically since finding that app, to the point I also now keep excel spreadsheets to track my laps, fast laps, average laps, efficiency, and standard deviation of all my practice time. I've been looking for an affordable way to add competition (more cars) to the practices, and this looks like it may be it. I'll be checking this out for sure
05-31-2019 | 12:33 AM
#26
Tech Adept
Joined: Aug 2017
Posts: 117
Today there was a post on lapmonitor's facebook regarding differences of 1/100 sec which reminded me that when I tested it, for the local track, this effect was way bigger (tested by checking at the two extremes of the track's width when the car was detected).
Anyone knows if this is somehow handled by the software or hardware? I don't care, at all, it's a fantastic product, I'd just like to be able to now what is a significant difference and what is car placement between laps, and of course over multiple laps this will average out.
Anyone knows if this is somehow handled by the software or hardware? I don't care, at all, it's a fantastic product, I'd just like to be able to now what is a significant difference and what is car placement between laps, and of course over multiple laps this will average out.
05-31-2019 | 12:43 PM
#27
Tech Initiate
Joined: Aug 2016
Posts: 30
Hi, thanks for explaining this case, indeed when car path when passing the lap counter is very different between two passes (your drawing is showing the worst case) then accuracy is worse than few 1/100s .
But this is not the normal use case of racer who is battling for a 1/100s .The error in this case is dependent of the speed, the faster the car goes the better is the accuracy, for example a car at passing the lap counter at 40km/h and a lap with 2 passes separated by 2 meters you can get an expected error of 6/100s
Also this error is not cumulative and will be canceled at next lap when going back on the common car path of the driver.
We tested on a track and compared to video timestamp and error was few 1/100 secs differences (usually less than 2-3/100s) you can check it on some of our youtube video
This can be improved with software but not yet implemented in our software but as I wrote above the case you describe is not the normal use case when you're doing your best laps and as you wrote and expect the next lap this error is automatically corrected
But this is not the normal use case of racer who is battling for a 1/100s .The error in this case is dependent of the speed, the faster the car goes the better is the accuracy, for example a car at passing the lap counter at 40km/h and a lap with 2 passes separated by 2 meters you can get an expected error of 6/100s
Also this error is not cumulative and will be canceled at next lap when going back on the common car path of the driver.
We tested on a track and compared to video timestamp and error was few 1/100 secs differences (usually less than 2-3/100s) you can check it on some of our youtube video
This can be improved with software but not yet implemented in our software but as I wrote above the case you describe is not the normal use case when you're doing your best laps and as you wrote and expect the next lap this error is automatically corrected
Today there was a post on lapmonitor's facebook regarding differences of 1/100 sec which reminded me that when I tested it, for the local track, this effect was way bigger (tested by checking at the two extremes of the track's width when the car was detected).
Anyone knows if this is somehow handled by the software or hardware? I don't care, at all, it's a fantastic product, I'd just like to be able to now what is a significant difference and what is car placement between laps, and of course over multiple laps this will average out.
Anyone knows if this is somehow handled by the software or hardware? I don't care, at all, it's a fantastic product, I'd just like to be able to now what is a significant difference and what is car placement between laps, and of course over multiple laps this will average out.
Last edited by gfranck; 05-31-2019 at 01:40 PM.
05-31-2019 | 02:35 PM
#28
Tech Apprentice
iTrader: (2)
Joined: Oct 2012
Posts: 67
Hi, thanks for explaining this case, indeed when car path when passing the lap counter is very different between two passes (your drawing is showing the worst case) then accuracy is worse than few 1/100s .
But this is not the normal use case of racer who is battling for a 1/100s .The error in this case is dependent of the speed, the faster the car goes the better is the accuracy, for example a car at passing the lap counter at 40km/h and a lap with 2 passes separated by 2 meters you can get an expected error of 6/100s
Also this error is not cumulative and will be canceled at next lap when going back on the common car path of the driver.
We tested on a track and compared to video timestamp and error was few 1/100 secs differences (usually less than 2-3/100s) you can check it on some of our youtube video
This can be improved with software but not yet implemented in our software but as I wrote above the case you describe is not the normal use case when you're doing your best laps and as you wrote and expect the next lap this error is automatically corrected
But this is not the normal use case of racer who is battling for a 1/100s .The error in this case is dependent of the speed, the faster the car goes the better is the accuracy, for example a car at passing the lap counter at 40km/h and a lap with 2 passes separated by 2 meters you can get an expected error of 6/100s
Also this error is not cumulative and will be canceled at next lap when going back on the common car path of the driver.
We tested on a track and compared to video timestamp and error was few 1/100 secs differences (usually less than 2-3/100s) you can check it on some of our youtube video
This can be improved with software but not yet implemented in our software but as I wrote above the case you describe is not the normal use case when you're doing your best laps and as you wrote and expect the next lap this error is automatically corrected
