computer oddities
13
Jul
2008
Jul
2008
During T-bird, we ran our own Timewise 798A rally computer for the first time. We noticed a few oddities. #1. Fortunately I had written the factor down. So I reentered it. Fixed the distance. I started checking the factor regularly. Marinus is going to look at the wiring changes since the firewall hole fix to see if that contributed to the problem. Each time the wackiness seemed to happen right after the car’s engine was started.
February 16th, 2008 at 8:45 am
With regards to #2 I’ve noticed something similar when trying to load the Presets a second time. I don’t think that is what happened in your case (since you mentioned setting Calc Time). I’m a big fan of using Preset, using the following technique.
At the end of the section zero the Odo and switch to TRANSIT mode. As soon as the opportunity presents itself, set the Calc Time to the Car Zero Time for the next section. This gives the driver something to shoot for. But, be sure you tell the driver that’s Car Zero Time not your time (lest it cause a panic to get there on time). Go to Presets and load in the starting CAST and out time (for your car this time). Change the Next Speed to the second CAST of the TSD. When you pull up to the start of the TSD you have one keystroke to setup a) zero the Odo b) set the Calc Time and c) execute the first CAST. Plus the second CAST is ready to go.
So you (the reader) are now privy to sooper sekret TeamD rally knowledge!
Oh yes the point of this response. A couple times using Preset, I’ve had my mind go blank and hit it at the wrong point or for some reason thought something was wrong. Easy enough, just back up and load Presets again. That seems to put one or two extra seconds on the Calc Time. If you do have to do something like this, quickly change the CAST (in Presets), change it back, and load Presets again.