
FIRMWARE VERSION HISTORY
ii TIMEWISE 798A
Modified the display of logged calculated time and clock data to always show “tenths of units”, regardless of the selected
time resolution mode for live or split data.
Increased the settable Alarm resolution to 0.01 mile. Previously, the resolution was 0.1 mile.
Added ability to continuously display an alarm “countdown distance” in the main AUXILIARY display without holding
down the SHIFT switch. Also added ability to display the countdown distance in the driver’s AUXILIARY display.
Changed the alarm To Go function to an alarm “warning” distance. The To Go distance can range from 0.00 to 9.99 miles.
Adjusting the To Go distance to a value other than 0.00 causes the beeper to sound at the selected distance prior to arriving
at the alarm mileage. Previously, the alarm beeper could only sound at the alarm mileage. (Also previously, the To Go
function simply served to temporarily display the alarm countdown distance in the AUXILIARY display.)
Altered the driver’s module LED display circuitry re-initialization procedure to also include a re-initialization of the main
LED display circuitry. The re-initialization procedure is now executed after a two-second Last Split activation rather than
simply a two second SHIFT switch activation.
Version 2.003 August 18, 2000
Eliminated illumination of the “thousandths of miles” digit of an Odo & Time adjustment amount (in the AUXILIARY
display) when thousandths of miles are not displayed in the main odometer. The log sequence number now counts to 255
before re-starting. Previously the sequence number counted to 250. You can now enter a Preset CAST with .01 mph
resolution if Option 6 is installed.
Version 2.004 August 21, 2000
Implemented a flashing ODOMETERdisplay when the Remote Park function is activated.
Version 2.005 September 7, 2000
Added an elective ERROR display offset of 0.45 second (or 0.45 hundredth). Some rallyists enable this offset to make it
easier to arrive at a checkpoint “within the count” intended by the rallymaster.
Version 3.000 October 29, 2000
Fixed a bug that prevented the factors associated with the inactive odometer input from being corrected during the
Compute Factor procedure if a sample factor was calculated first.
Added a visual warning that indicates when the odometer pulse rate is too fast (> 1000 pulses/second). Improved the Intelli-
Sense™ transducer failure detection system. Changed the AUXILIARY display system to allow showing “tenths of units”
when viewing a time parameter. Fixed an interrupt conflict introduced in version 2.002 that randomly produced a
speedometer miscalculation.
Version 3.001 December 29, 2000
Fixed a bug in version 3.000 that prevented electronic synchronization to Timewise multi-split chronometers.
Changed the odometer pulse interrupt routine to allow an increase in the permissible odometer pulse rate. Continuous
odometer pulse rates in excess of 5000 pulses/second are now tolerated, even without use of the 798A's built-in input signal
divider. The visual warning indicating an overly rapid odometer pulse rate now occurs at rates in excess of 5000
pulses/second. (Pulse rates up to 640,000 pulses/second are allowed when using the input signal divider.)
Also raised the speedometer timing routine to a higher interrupt priority. This guarantees the accuracy of the speedometer
calculation at extremely high speeds (>180 mph).
Version 3.002 January 3, 2001
Negative Odo & Time adjustment amounts (shown in the AUXILIARY display) are now displayed with a negative sign
preceding the value. Previously, a negative adjustment amount was shown as a number decreasing from 1000.000 (e.g.,
a – 0.100 mile adjustment was shown as “999.900”).
Version 3.003 February 22, 2001
Option 3 (Great Race testing) is now available.
Version 4.000 April 2, 2001
Fixed a bug that caused two problems with the use of the Last CAST odometer adjustment feature:
After exiting a transit zone (i.e., where the CAST had been 0.0 mph), any adjustment to the Last CAST odometer reading
resulted in an incorrectly displayed value of the “updated” last CAST calculated time reading. This was a display anomaly
only. The actual driving time error and the overall calculated time were not compromised.