Packet Operator Reference Card for RACEDATA

(Translation of PACKET.HLP)

1. TNC Settings for remote packet stations. These are quite important for efficient operation of a master/slave network like RACEDATA. Not all of these commands will be found on your TNC. Different manufacturers use slightly modified command sets. Use those that apply to your equipment.

   TAPR, AEA, etc.

   DWAIT	73	(730 ms) (few modern TNCs have this command)
   MAXFRAME	1
   FRACK	10	(10 sec)
   RETRY	10
   AX25L2V2	ON
   RESPTIME	10	(1.0 sec)
   TXDELAY	40	(400 ms)
   PACLEN	234
   PERSIST	63
   PPERSIST	ON
   SLOTTIME	30
   ACKPRIOR	ON
   DEADTIME	30	(MFJ & TAPR only)
   SLOTS	4	(MFJ only)
   BEACON	0

2. Summary of database operations:

   1. Before data entry will be accepted from a connected packet station, the station must log in with with the checkpoint indentification letter assigned. This letter is then used for all data coming from the logged in callsign. This eliminates the need for a station to include the checkpoint letter in each data record sent. To receive a list of checkpoint letters, enter the command chkpt <cr> and the the system will respond with a list of checkpoint names and letters.

      Login example: chkpt=x<cr>

      Current information input: (commas are REQUIRED separators, and <CR> means carriage return)

      runnernumber,in-time,out-time,comment<CR>

      where

      1. Runnernumber is three digits and a required entry.
      2. In-time and out-time are four digits. One may be omitted.
      3. Comment is limited to 20 characters and should be used only when necessary.

      For example: 100,0900,0910

      Multiple entries can be made on one tranmission by separating the entries with a dash.

      For example: 101,0900,-102,0900,0910,-103,0912,0915,-104,0915,

      Maximum characters for one multiple entry transmission is 255.

      YOU MUST WAIT FOR A SYSTEM ACKNOWLEDGMENT RESPONSE BEFORE SENDING ANOTHER RECORD (or Multiple entry) OR DATA WILL BE CORRUPTED.

   2. Correcting information entered in error: An erroneous entry can be deleted by the station logged in at the checkpoint. The command to delete an entry is: DELETE ###, where ### is the runner number.

   3. Searches available: Runner position, DNF list, Checkpoint Runner lists.

      /R# gives last reported position of runner number #.
      /DR gives current DNF list sorted by runner number.
      /DT gives DNF list sorted by increasing time of DNF.
      /C,%,#### gives list of runners into ckpt % after time ####.
      /P,% gives list of runners still inbound to checkpoint %.
      /L###% gives record of runner ### at checkpoint %.
      LEADS gives a summary of the four leading runners.
      TEMP gives a listing of reported checkpoint air temperatures.
      TEMP=xx allows entry of the air temperature at your checkpoint.
      

3. CONFERENCE BRIDGE: users and tell commands:

   users<CR> u<CR>	requests list of calls connected to RACEDATA and checkpoints on line
   tell callsign message<CR>   t callsign message<CR>	sends message to callsign (Partial calls, such as suffix, work.)
   tell % message<CR> t % message<CR>	sends message to checkpoint % (% is checkpoint letter designator)
   tell * message<CR> tell all message<CR>	sends QST message to all connected stations including sysop
   tell sysop message<CR>	sends message to sysop

4. OTHER COMMANDS:

   help<CR> h<CR> ?<CR>	requests a brief syntax reminder from system
   get filename	requests download of "filename", which may be any file in the public subdirectory.
   For example,    get info	requests download of a file named "info", which gives more information on the program
   dir	requests directory of the public subdirectory
   status	current RACEDATA system status
   <CR>	tests to see if RACEDATA is running - response is a line feed plus the ">" prompt.
   b<CR> bye<CR>	requests logoff from RACEDATA

5. IN CASE OF INADVERTENT DISCONNECT

   If your packet station becomes disconnected for any reason and you wish to reconnect, first reconnect to the node (CLAY or MURD) then send a <cr> and wait for a response. If the command prompt (>) is returned, you remain connected to the database program. If not, reconnect to RACE.