split second issues

Hello---

No, never heard of this one---what do you mean "thrown"?
You mean the time just drops out, then defaults back to dns? Never that one, lots of other problems, but I think you must be doing something to get this problem---is the time still on the timing log?
Do you hit false start by mistake?
Send me your XML file to look at
chase@alpinetrainingcenter.com

The competitor crosses the finish line, run time appears, I announce it, and at the end of the race, the competitor is mysteriously showing DNS instead of his run time. I am positive I haven't hit a "wrong" key. This happened several times last year, and a couple times already this year. I've tried to reach Geoff Elder, but can't seem to get an answer. Next time it occurs, I'll look in the timing log.

Kathy, I had this same thing happen for the first time this weekend at the J-3 finals. It was the announcers kid that wasn't listed on the 2nd run start list so we caught it right away. In the competitor list he showed as a DNS. But clicking on the TOD edit tab I found that he indeed had both start and finish TOD's and an elapsed time. The only thing wrong was that the little button at the bottom was checked next to DNS, rather than TIME. I checked the TIME box and the problem was fixed. I double checked all the first run DNS's and found another one with the same problem. No idea what happened.

The only weird thing that happened during the run were a few false starts. I caught them with the false start button and there were no problems. I noticed on another topic that you said you still get a few false starts every now and then also. I switched to a different start pair for the 2nd run and didn't have a problem the rest of the weekend.

Could there be a connection between false starts and kids getting thrown in the DNS list? Any one have any ideas?

Send me your XML files, can't tell without them

chase@alpinetrainingcenter.com

Hi Dirk, no I don't think the false start issues are related. I think the software has a bug in it somewhere. Our false starts are wiring related, probably too much resistance.

One thing I am going to pay attention to next time the splitsecond program DNS's a racer who actually finished - I am wondering if it is happening during when the snow seed racers are running. If we select snow seed, and then don't run them, it seems to affect the program. One time I had three racers on course, in the snow seed bib numbers, and suddenly all bib #'s on course flickered and changed to different racers. Needless to say, I jumped off the chair - it really got my attention! When this happened, it also changed a competitor who had just finished to a DNS. So, I'll keep an eye out, and let you know.

Are your false starts just on the primary, or on the backup at the same time? Are you using a speech headset on the primary line so you can hear if it is noisy? High line resistance, with an 8000, will give you no starts rather than false starts. Noise on the line will give you false starts. Is there an isolator from the 8000 to the PC? Read some of the recent posts about line noise induced by connecting the 8000 to the PC with the RS-232 port. Some users just switched their speech communications to another line so they did not hear it. This did nothing to clean up their primary start line.
Jim Green