Enduros - Keeping Score 

(Free upgrades to licensed users)

The intricacies of scoring Enduro events can result in riders having to stick around long after a race has been run - waiting for the final results to get posted - especially if there are a lot of riders. It can become a chore to keep track of rider numbers, starting times, which row a rider started from, along with the points awarded at each "standard" checkpoint, and those awarded at each "emergency" checkpoint. That task has been made a LOT easier with the advent of the Race Timer software. Here are some of the program's features.

• It's user friendly interface is simple and intuitive to use, requiring essentially no training. Contact the author if you'd like a sample set of data to run a practice race with.
• Class standings are a cinch to compute.
• You have the option of printing not only the class standings, but the Overall standings as well..
• The output is automatically shifted to a landscape mode - with the system able to print directly to a printer for up to 10 checkpoints. When there are more than 10 checkpoints in use, the system saves the data to disk, letting the promoter format the output via a standard word processor.  
• The program will display the individual checkpoint data for every rider. Double-clicking on any rider will provide every bit of detail held by the program for that individual - including name, class, starting row, the checkpoints completed, the time at each checkpoint, and the points (standard and emergency) awarded at each checkpoint.
• The program can be customized for any numbering sequence used by other promoters and does not require any specific rider numbering system be used. While it's traditional to have rider numbers equal to their starting position, that's not a requirement in this system.
• Mistakes in data entry are easy to correct.
• If you're using the barcode capability, and have scanners available at each checkpoint, the entire race can be scored electronically, with the different "raw data" files merged to form the master checkpoint database.
• The system can import data from a barcode scanner, without any special software from the barcode manufacturer. The system is intended to use the PDT3100 Series made by Symbol, but if you contact the author, the program can be modified to support other barcode scanners.
• The output is selectable - allowing you to include the riders class and the individual checkpoint times for each user..
• For those activities having access to a barcode scanner but who don't have a barcode printer, the system enables you to print your own barcodes via any word processor. It's much better if the barcodes are printed with a barcode printer (they're waterproof), but a laser printer and clear tape (to adhere the barcodes to a helmet) will work just fine.

You can continue to the registration page by clicking here or continue below for details of how the program is used to score Enduro events.

Program installation is very simple. Installation requires nothing more than to execute the setup program, then executing it from whatever directory you installed it into. When you no longer have a use for it, the program also comes with an uninstall program.

This program requires Windows 95, 98, or any of the latest variations of Windows NT or Windows ME. If you have any questions, send them to the author via email..

The following graphics show some of the screens used in the program. 

Informing Users of System Settings:

Opening Screen:

Identifying the classes

Rider Registration
(shown with a simulated rider database and simulated rider names)

Identifying the checkpoints
('emergency' checkpoints are marked with an asterisk)

A typical display screen prior to entering checkpoint data if a data file is already present. Note: the 'remote display' is not applicable to enduro events.

Manual data entry (i.e. at a centralized entry point).

Calculating the results

Viewing data on individual riders

(shown above is a totally fictitious rider. Normally you'd see times centered around their rider number - for example you'd expect to see times centered around 22 for rider number 22b )

Sample of the printed output

Downloading Data from a Barcode Scanner

Generating barcodes

Managing the Rider Database

Backing up the data

Back to the Race Timer home page