Title: AE4GX TANDY 102 Keyer/Logger

Author:

Sam Billingsley AE4GX
609 Old Ivy Rd
Atlanta, GA 30342
email: sbillingsley@usaninc.com

Purpose:

This program provides a message keyer and contest logging capabilities particular to the minimal needs of QRPers. The limitations for space, speed and display made the Tandy 102 environment a challenge but you can get basic functions form this OLD piece of gear. Like most of you I have had my Tandy 102 in the closet for many years and in the back of my mind thought it would make a good message morse code keyer. The logging was an after thought but why not. I was looking for something for backpacking (i.e. light, small, low power). The Tandy 102 fits the bill for me. It turned out that I initially developed this for the logging capability and the keyer was added as an extra. Strange world.

Size:

The BASIC program once loaded allows one to store about 300+ QSOs in RAM (I have the 24K unit so I have about 15k+ free space after the program is loaded.

Note on log004 release 7/18/98

The AE4GX Tandy102 Logger/Keyer program was released to the following qrp-l members as the result of any earlier thread where I was looking for a solution. The following were sent the log004 release on 7/18/98: Don Bullard/WA4IMI, Henry Freeenberg/N5HF, Jeff/WD4ET, Joe/KK5NA, Mark Kesner/KC4GIA and Niel Skousen/WA7SSA. Several references were brought up by the group members but none were a satisfactory solution to the logger problem. None addressed a combo logging/keyer solutions.

I used the logger portion of log004 in the ARS Bumblebee QRP contest in  July 1998. The logger worked as expected but I didn't have the keyer portion ready so didn't try to use it. If I had I would have seen some problems that were uncovered later. With the contest out of the way the unit was put back on the shelf.

Note on Update from log004 to log005.

Rick Sealey/W4SEA started up the thread again on Nov 6,1998 with a general question to the qrp-l about finding out who mentioned a logging program. I responded and as they say the rest is history. The response has been much more than expected. It seems that there are Tandy100/102's in closets and boxes all over the country. Well this should satisfy some pent up demand for use.

Between 11/6/98 and 11/16/98 there has been 23 qrp-l members added for a total of interested at a current total of 30 including myself. Calls include (my directory sort order - alpha by first name):

Anthony K9AM Mark
Barry WD4MSM Keating
Brian W5VBO Kassel
Bruce W6TOY Muscolino
Darrel WD6BOR  ??
Dave KD6KWM Willey
Dick AB0CD Schneider
Don WA4IML Bullard
Edwin AE4EC Lappi
Eric KC6SPN Shrader
Gary WD8KQY Nye
George W5YR Baker
Henry N5HF Freedenberg
James W0KSD Rybak
Jeff WD4ET ??
Jim KC1FB Francoeur
Jim VE2KN Lyons
Joe KK5NA  ??
Johnson KE0MC Lee
Mark KC4GIA Kesner
Mark WD0IQK/8 Gilger
Michael LK7IXI/7 Fletcher
Niel WA7SSA Skousen
Paul VE7CQK Erickson
R. YD3EBM Soetedjo
Sam AE4GX Billingsley
Steven KI0MZ Smith
Tom AD6N Upton

Many thanks to the group above particularly Mark KC4GIA, Don WA4IML, Jim VE2KN and Tom AD6N for their special effort and participation.
 

First of all, several of this group have actually tried to use it and give feedback. This has provided me with great information.

The most critical bug found was that the keying routine didn't actually control the internal relay as described. Several have offered fixes. PROBLEM solved.

Currently the keying solution uses the internal relay but several are looking at using the RS-232 port control leads for an electronic solution. There will be more to come on the electronic  solution.

There were several comments about the "not so smooth sounding" keying. I found a bug where I had left off the OFF time delay after DITs. Problem solved.

Call Sign DUP Checking has been included in this version log005. You can turn ON or OFF the DUP CHK capability. It is off on initialization. UP to 300 calls can be DUP Chked. I think you will run out of logging space before this is reached.

If the CAL,SPC,HRST,MRST are attempted to be changed after valid key in the old value will be cleared at the beginning of the new value being entered.
 

Since this is a  software and functionality oriented project it can be carried on as far you an individual wants it to in terms of enhancements. I will reach a point of minimal incremental return and FREEZE my solution. I'm sure that someone will want to tweak things further. It's a fun project and you would get soldering iron burns. :)
 
 

Note on Keying:

Since I used the SOUND BASIC command for WPM timing the relay seems be automatically keyed as a side affect. I plan to use this hard contact relay for my Transmitter keying. I haven't tried to tweak the WEIGHTing parameters (i.e. Dot/DASH time On/Off ratios, inter-word time, etc). I used the standard values I found in various Morse write-ups. You can easily change to suit yourself. I limited the Morse output set to A-Z, 0-9, "/" and "?". Additional characters and prosigns can be added. Notice my character table INDEX is artificial and doesn't have any algorithm to create it. With the MSG function "ay<return> (Sound/audio ON) you can hear the characters being outputted via the internal speaker.

Downloading to Tandy102:

I have been using WORDPAD(simple text file editor) or an old GWBASIC internal editor on my email PC to generate the logxxx.DO file. I then bring up the Tandy102  and use TELCOM DOWNLOAD capability to receive the xxx.DO file. I use PROcomm to SEND to file to the TANDY 102. I had to slow down the output from the PROcomm so I would not overrun the TANDY. I know I could have used XON/XOFF but I'm lazy. The only thing I noticed is that an extra hex"FF" character is in my file at the very end when it gets to the Tandy. I use the Tandy text editor to delete the "FF" character then use the "MERGE" capability of the BASIC package to convert the xxx.DO downloaded file into a run-able BASIC file in BASIC> You can then SAVE the "xxx" as a .BA file using standard BASIC calls.
 

All major functions are started by pressing a FUNCTION Key.

Function #8 MSG = Message system

 "CMD" wants you to enter one of the following:

 cX<return> where X is msg #  x in range 1 to 5
   msgs are up to 30 chars.

 pX<return> where X is msg # from 1 to 5 to be outputted

 sXX<return> where XX is WPM speed from 1 - 30

 aX<return> where x="y" means sound ON and x="n" means sound OFF

 
Function #7 COM = Common log stuff

 pXX<return> where XX is power in watts from 1 to 99

 bNN<return> where NN is BAND ID (80,40,20,15,10)

 mA<return> where A="c" for CW or A="s" for SSB

****NEW
      d<return> where DUP CHECK for is toggled ON or OFF
                If ON "*"appears next to left of CAL on Function line.
                If DUP off this position is <blank>  [ ON = *CAL     OFF =  CAL  ]
****NEW
      x<return> EXITS Logger program back to system prompt after closing files.

 
Function #6 MST = MyRST

 XYY<return> where X 1-5 and Y 1-9 (range chks done)

Function #5 HST = HisRst

 XYY<return> where X 1-5 and Y 1-9

Function # 4 SPC = State/Providence/Country

 AA<return> where AA is two char SPC code (no edits preformed)
 

Function # 3 CAL = Call of Station worked

 AAAAAA<return> where length A...A is 3 to 6 (no alpha chks done)

Function # 2 LOG = Write log info to file (system will force you to open file)

 Entries are as follows comma delimited:

 DATE$
 Time$
 Call
 SPC
 HisRST
 MyRST
 Band
 Mode
 Power

Function # 1 FILE = File actions

 If no file active the filename<return> (include .DO)

 The named file info is put on screen in upper right hand
 corner: name,date and time opened

 If file is already open
   do you want to close then Y otherwise N
 
 

**************** end of doc ****************************
log005.doc de AE4GX