Jeff Piazza

I don't think the logs actually got attached, for whatever reason. If you don't mind, could you email them to me (jeff at jeffpiazza.org). Thanks!

Any logs you can share? Timer logs especially, but server logs may be helpful, too. What’s your set-up look like? Are you using the timer jar or the in-browser timer...

Thanks for these logs! In at least some instances (e.g., at +14:37:38 in the -1436 log), this looks to be a Champ-specific bug that was recently fixed in b0919cb49fa74a39921c0b537bee19f8f0735445. Briefly,...

I'm not sure what you're asking. The "faulty switch" theory was positing a slight mis-positioning of the physical switch on the track start gate (the travel on the switch is...

Andy, thanks for the feedback, and continued patience. Timer logs and apache logs if you can? You're still using derby-timer.jar, right?

So far I've been unable to reproduce in my experiments with a borrowed Champ timer. If you have a repro case, it'd certainly help. Second best would be the timer...

@DionMSmith14, the logs you posted are from a FastTrack K2 timer, and probably one that doesn't support the RG (read gate state) command. Try turning on the flag for fasttrack-automatic-gate-release....

I've opened #270 for the FastTrack-without-RG issue.

I borrowed a Champ timer from a local pack, but wasn't able to reproduce this. The proximate cause is that the Champ timer won't send captured results unless it receives...

I still haven't been able to reproduce this. (And the neighboring pack is going to want their timer back soon.) https://derbynet.org/download/v9pre/derby-timer.jar incorporates some code changes intended to address this issue....