I presented my home brew at the December 2011 Club Meeting.  My home brew was a set of programs to help in the Buffalo Run. Some club members expressed interest in "testing" the program.  I have made the program available to download on my Sky Drive.  If you want to connect to my test server, connect to KD7HHW-4 on 145.070.  Let me know if you run into problems - This e-mail address is being protected from spambots. You need JavaScript enabled to view it .

Notes:  This program relies on AGWPE as the interface to the TNC/Radio.  AGWPE can be the TNC if you are using a soundcard interface.  AGWPE has two versions: a paid version and a free version.  I have written my program to work with the free version.  Two other programs to download are AGWTerminal and AGWMonitor.  Download these applications from SV2AGW.

In January, I will be going into more depth on the client and show the server as well.

Background

While working with the Buffalo Run, I saw a need to help get the runner data to Net Control in a better way.  We were using the mailbox on a KPC3+.  Most stations used a terminal program like Hyperterm to send the data.  I had found a program called OutpostPM that could perform the same function but with a mailbox format, like inbox, outbox, sent items.  For me, this allowed me to send the data easier and to see what I had sent. Net Control had to take the data from the KPC3+ mailbox and import the data into the database after manually formatting the data.  I wanted to find an easier way for both the sending station and Net Control.

My homebrew is the result of how I feel I could help automate both Net Control and the individual stations.  I created both a client and server.  Both programs were programmed using Lazarus, a Pascal based compiler.  I wanted to make my programs work with just about any TNC, including sound cards, so I decided to use AGWPE as an interface.  AGWPE allowed me to concentrate on how to handle the data rather than how to interface with a TNC.  There is another benefit with using AGWPE: the TNC can be used for more than just the race programs at the same time.

Server

The server allows stations to connect with my client program or a terminal program.  When using a terminal program, users can:

1. See the most heard stations
2. See all connected users
3. Insert information to a MySQL database (directly)
4. List the tables in the database (used to troubleshoot and future functions)
5. Show all stations a runner has passed through
6. List missing serial numbers for a station
7. Disconnect

This is similar to a mailbox.

End stations do not need to stay connected for the entire race; they can connect, send their data, and then disconnect. 

Client

The client tracks the runner number, day, time, status, and any notes.  It is setup in a spreadsheet form.  As station operators enter data, the client program checks for errors: runner numbers are truly numbers, days are numbers, times are numbers, status can be either C or D, if the status is D – notes are required.  The program also allows station operators to have the day and time entered based on the current system day and time.  The client program can be setup so that it sends the information either manually or after so many minuets have passed.  The client may be configured to connect directly to the server or through another packet node.  The client also saves the data entered so if the station’s computer looses power, they can recover quickly once power has been restored.  If updates are needed for any of the serial numbers, stations may make the changes and send just the entries that were changed.

Requirements

The minimum requirements for the client are:

1. Pentium 200MHz
2. Windows 2000/XP/Vista/7
3. 80MB RAM (RAM installed and not necessarily use this amount)
4. AGWPE

The minimum requirements for the server are:

1. Pentium/AMD 800MHz
2. Windows XP/Vista/7
3. 1GB RAM
4. AGWPE with at least 2 connections – loopback and a radio port
5. Connection to a MySQL 5 database – if on the same computer, the requirements will need to be greater