cable for TdC8000 to PC

This is a chronic problem, and there are several posts about it in this topic and others. We found the line was clean if the computer was not connected. Connecting the computer to the clock while the clock is connected to the hill wiring causes big noise on the hill circuit. This causes false starts, or no starts. We had this problem. We just stopped using the data import function.
Grounding/shielding did not improve anything.

Cranmore had this problem. They bought an opti-data. You will have to contact them for more information about this; my information is hearsay. But note, if you use the TdC 8000 mode, which sends start/finish time of day times to the computer, you will sometimes have the computer calculate a different run time (by 0.01) than the clock computes. This produces run times on the clock tapes which are different from the computer generated run time. I don't think this is a good thing. Try the TdC 4000 mode, which sends just the run time to the computer, but uses a different cable. Let people know how you make out.... PLEASE!
I have had too many back to back to back races to experiment any more with this. Now I have a 3 week break. Maybe I can find out some more.
Jim Green
Wildcat Ski Club

In regard to the difference in times when you are sending start and finish time of days from the TDC8000 to Split second Software, and the times that Split Second Calculates, this is not a problem at all. The TDC8000 always calculates it times based on the 10th of a second 1/10000, and then, if set appropriately, truncates to the 1/100 of a second. Split Second, Truncates the 1/10000 of a second, calculates times of the 1/1000 of a second, and truncates to the 1/100 of a second. The reason you have an occasion difference at the 1/100 of a second for a net time is due to the rounding that is done during math. Either method is fine as long as you are consistent.
Jordan

Yes, I know. What I don't like is having the tape and computer show a different run time. Someone not as knowledgeable as you might think there was a problem.
I think the answer it to put the program into the 4000 mode and send just the bib number and run time from clock to computer.
I will try that shortly, and see how that works. I think an isolator will still be needed.
Input from anyone else who has experience with this (the overall issue of directly importing times from clock to computer, and/or line noise) and knows additional things would be highly appreciated.

Jim Green
Wildcat Ski Club

The ALGE OPTODATA is now in stock. This little box is powered by the Timer and will eliminate the noise on the headsets. It is placed between the RS232 output on the timer and the PC. The cost is $340.00 The OPTODATA is also perfect for removing noise from the Timer if a display board is plugged in. Just place the OPTODATA between the Timer and the display. The OPTODATA for use with the display is $325.00

Jim,
The issue with using your TDC8000 in the 4000 mode is that the competitors will not be shown on course...the are shown in the start, and as the finish. This just makes it much harder for the announcer to keep track.
Jordan

Thanks.
But, the way I thought it worked was you told the software in the computer that you were using a 4000, and just changed the RS-232 output parameters in the 8000 to match the 4000 output. Does this create a change in how the 8000 displays, on its own displays, results?
Obviously, I have not tested this yet. I spent yesterday at Pats Peak and today at Attitash. Will probably spend next Sat at Sunapee and Sun at Skiway. Maybe I won't really get to do any more testing this season. In the meantime, I will just continue with the tried and true manual run time input method.
Thanks for your support.
Jim Green

Most of the following is reduntant and has been well documented elsewhere. Just follow along as a refresher or skip to the bottom.

The selection of TDC 4000 in the SST software only allows the software to capture the "net" finish time from either the 4000 or the 8000. You are then obligated to handle all of the timing tasks on the timer. The software just sits there. The green leg of the cable is connected to the display out on the timer. The blue leg is free.

Selecting TDc 8000 plus in the software allows you to run the 8000 and the software simultaneously. The 8000 must have the RS-232 baud rate set at 9600. The 8000 is set on program "split". Sync the timer and make sure that start time print has been selected in the menu and that timing precision is 100's.

At this point you can operate either the software or the timer for "live" timing. The timer will output the channel id and tod time regardless of whether you are controlling it or not. The tape will show bib numbers for the starts if you left it incrementing up or ??? if you left it blank. Likewise the finish will either show bib numbers or ???. The channel id will appear regardless therefore satisfying the FIS rule. How you run the system depends on the number of people you have at your disposal. Most clients run the 8000 on auto pilot and control the race on the SST PC. They only go over and time live on the 8000 if there is a PC or software problem. Clients with plenty of staff let one person run the 8000 and the other run the software in tandem. That is the prefered way as there is always a check on each time. Both the 8000 and the SST software are using the same tod impulses and calculating the times.

As it has been mentioned, there is a possibility that the times will be off by 100th every once and awhile due to the method that the time was calculated. If you set set up the SST as the primary system for displaying net times than so be it. The consistent application of the calculation is whats important.

We will be at Mt. Cranmore for the Hannes Schneider race on March 8. Anyone wishing to spend time with us and go over these issues or headset noise issues is welcome to come. We will arrive Thursday night. Setup and consulting on Saturday. We have to leave Sunday by noon.

[This message was edited by FKP on February 24, 2003 at 09:00 AM.]