Central American Enduros
Keeping Score 

(Free upgrades to licensed users)

The software also supports the type of racing sanctioned by the "ULM" - the Latin American equivalent to the American Motorcyclist Association (AMA).  I refer to this as the Central American Enduro Mode.

In this mode, we essentially have several stages which are known as "observations".  Inside of each of these stages there may be any number of "special tests".

These special tests are essentially of three types .... an "Extreme" test, a "Cross" test, or an "Enduro" test.

This could mean (for example) that an event might consist of the following checkpoints

        Start of stage 1
                Start of a Cross test
                Finish of the Cross test
                Start of an Extreme test
                Finish of the Extreme test
        Start of stage 2
                Start of an Enduro test
                Finish of the Enduro test
        Start of stage 3
                Start of a Cross test
                Finish of the Cross test
        Finish

Scoring ......

Riders are assessed point based on not only how they perform during the entire stage, but also how they perform in each of the stages.

As part of the course definition, the promoter assigns a "theoretical" time for each class inside of each stage. This is where the computer becomes mandatory since it becomes difficult to manually keep track of all of the theoretical times for each of the classes, in each of the stages.  Each rider is expected to complete each stage at exactly the time specified as the theoretical time for his class on that stage.  A rider is penalized 60 points for each full minute he is off - with points assigned if he arrives early, or if he arrives late.

A rider will always be penalized points for either arriving early or late - with one exception.  At the option of the promoter, the end of the last stage can be identified as a "Crazy Finish".  If the finish line is identified as a "Crazy Finish", there are no points assessed for finishing early - with points only assigned for finishing late.

For the special tests, the first step is to determine the fastest rider in each class for each special test, then each rider is penalized 1 point for each second he is slower than the fastest rider in his class in that particular special test.

• 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:

Identifying the classes

 

Rider Registration

Identifying the checkpoints
Note the option for the "crazy finish"

Additional information is needed when identifying an Observation (or stage). The screen below indicates a typical screen depicting a new stage. The user sets the theoretical time for each class for that stage, identifies whether or not gas is available, sets the length of the stage, and sets a name for the stage.

Once all of the checkpoints have been identified, the system gives you the ability to print the course instructions for the riders as shown below

There are three methods of data entry. Data can be imported from a barcode scanner for the selected checkpoint, or you have the option of either of the two screens below.

Manual data entry (option 1).

Note in the option above, that you first select the rider, then click on the specific observation. At that point you start typing in the time at the checkpoint.  The system will automatically advance to the next checkpoint as you enter data for each checkpoint. This method is perfectly suited for the case where a rider carries a scorecard with all of his times entered on the scorecard. In this case the rider brings the scorecard to the scoring team for easy data entry.

At other events the data may be collected at the checkpoint for each rider.  In that case you have the option of clicking the button to "manually enter each rider number" - which will provide you with the data entry screen shown below: This simplifies the data entry for all riders at a specific checkpoint.

Calculating the results

Note here that the "No DNF" option has been selected.  In thise case the system adds 3600 points to the rider for each checkpoint missed.
 

Viewing data on individual riders

Note in the display above, the system shows you the time at every checkpoint. It also shows you the theoretical time for the rider in two columns - one is the time he should have arrived at the checkpoint (in the case of a stage checkpoint, and the other is the reference time for the fastest rider in a stage

The system also automatically calls up the detailed report in an Excel format if desired - as shown below.  From here, it's easy to create any number of custom reports directly from Excel.:

The system provides an abbreviated report

Generating barcodes

Managing the Rider Database

Backing up the data

Back to the Race Timer home page