“Practice makes Perfect”

We encourage all to take advantage of the time prior to the run to hone your skills, and advise us of any issues or suggestions to make the system better.
Several nodes are set up in the Salt Lake Valley so that the hardware and software for the race can be evaluated, and so that you can practice using the system. These node stations connect to the database via a uhf link with the system in a test configuration.  If a node is not on the air, fear not.  Try another node and get ready.

CLAY               144.910 MHz    Clayton Peak node at temporary location in the Salt Lake Valley
CLAY               145.530 MHz    Clayton Peak node at temporary location in the Salt Lake Valley
MDELL             144.970 MHz    Mountain Dell
ISLAND            144.930 MHz    Antelope Island
PEAK               145.050 MHz    Ensign Peak  [This node has a integral deviation meter]
To avoid confusion in the node system and the operators, the practice database name is “W100”. The database for the actual event is “RACE”. To use the practice system, connect through a node to “W100”. On the Wasatch 100 weekend, connect through a node to “RACE”.

Using any terminal program (ARESPACK, Procomm, TeraTerm, Hyperterminal, etc.), and get to the TNC command prompt. Entering the commands in italics as shown, you should receive the responses from the system as shown in normal text.


The system is configured so that when you connect to W100 you go directly to the database. The W100 system is accessible from any of the nodes.
To check your transmitter’s deviation, connect to PEAK on 145.05, then enter “MH”. Your transmitter deviation will be listed. Approximately 4.0 kHz  is optimal for packet service. Deviation is normally adjusted on the TNC with an internal potentiometer. 

cmd:c peak 
cmd:*** CONNECTED to PEAK 
c w100 
PEAK:KD0J-11} Connected to W100:KD0J-7
Connected to Wasatch 100 Database Ver 2008
Sysop Status Messages
This is a test version of the RACE program for pre race practice.

For a description of changes to the program: CHANGES
Before entering data, you must input your Checkpoint ID Letter
Example: CHKPT=% where % is your Checkpoint ID Letter
To get a list of Checkpoint Letter designators:  CHKPT
Syntax for input: Runner#,in time,outtime
Example: 102,0100,0105,  Separator is comma, one time field required
Multiple records may be entered by separating them with a dash (-)
Example: 103,0100,0110,-104,0115,0120-105,0125
Trailing comma on record is optional
You must wait for system response before sending more data.
Search request: ### or # is Runner Number, % is checkpoint letter
T is local time in four digits, D is duration in hours
[] indicates optional entry.
Runner: /R# (Multiple request /R#-#-#, numbers separated by dash)
All reported times for one runner: /R#A
Checkpoint List: /C[O],%,T,[D]   Current DNF List: /D or /DT
List of Runners Still Out: /P[,%]   Single Record: /L###%
Runner number from last name: /N,name or /N,partial*
Next ten runners inbound to checkpoint: /I[,%]
Checkpoint Audit for missing d PEAK               145.050 MHz    Ensign Peak  [This node has a integral deviation meter]ata: /A[,%]
Runners in but not out: /H[,%]
Listing of Leading Runners: LEADS
Enter Temperature at Ckpt: TEMP=xx, Read Temps: TEMP
Delete record : DELETE ###
System Status:  STATUS
List of Runners: NUMBERLIST   Current Stations: U or USERS
Send Message: T or TELL CALLSIGN|*|SYSOP|% [message]   Logoff: B or BYE


After you are connected to the system, you may remain connected as long as you like. Twenty stations can be simultaneously connected, so you are not keeping others from using it by staying connected for long periods of time. Please try all of the commands and inputs.  There is a portion of the database from the previous year race loaded in the system so that you may make inquiries and requests. Please take the time to practice data entry.

As we move radios from the valley, to the mountain sites just before the race, the practice setup in the valley will be taken down.