-
Notifications
You must be signed in to change notification settings - Fork 70
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Heat Results occasionally do not populate with FastTrack timer without Laser Reset #317
Comments
Sorry about this -- -no-gate-watcher doesn't behave quite as I'd remembered it. This is specific to a FastTrack timer that doesn't support the LR ("laser reset") command. Stuart from MicroWizard tells me that most timers sold in the last few years have this feature on by default, so this should be applicable to a relatively small population. Setting -fasttrack_automatic_gate_release will fix this for sure, but it will present a "start" button on the race dashboard even though you don't actually have an automatic gate release. I'm working on a more substantial fix for next season. |
The fasttrack-automatic-gate-release option works! Thanks! |
This particular timer also doesn't support the "RG" command used to interrogate the gate state. -no-gate-watcher turns off the RG commands, but the LR's (also not supported on this timer) would continue. Most FastTrack timers do support both these commands, and don't require special flags being set. As I mentioned, I'm working on a more robust fix that will detect the unsupported commands and stop issuing them on its own. |
I'm having an issue with occasional heats not displaying results. I tried the -no-gate-watcher flag on the timer jar application per Jeff's suggestion, but I still seem to have the issue. I've attached logs where the last heat did not register in derbynet.
timer-20240209-1131.log
timer-20240209-1127.log
timer-20240209-1129.log
The text was updated successfully, but these errors were encountered: