
TWCW README

DESCRIPTION:
   This version has been compiled with the static libraries.  So, there
   is nothing to compile, and no libraries or development packages needed.
   See INSTALLATION below for instructions.

   This program sends Morse code and is implemented with a Motif interface.
   It was written using openMotif.  Earlier versions used lessTif.

   There is a helpfile in the twcwDir sub-directory.  This file can be viewed
   with the "more" command, or from the Help button while twcw is running.

   Code is sent by typing the text into a window, or you can select a file,
   and the contents of the file will be sent.  As the text is read from the
   file, twcw looks for any words that start with an "*", for example *RST
   or *Name.  If one is found, a dialog box is displayed and you can enter
   the text you want to send.  

   The transmitter is keyed by switching the serial port's Request To Send
   (RTS) line.  A line in the resource file, Twcw, allows you to specify
   which serial port you want to use,  A cheap and simple circuit is used
   to interface the PC with the rig.  The interface circuit fits inside the
   serial port's RS232 connector and does not require a power supply.  A 
   sidetone can be produced via the computer's speaker.


INSTALLATION:

   The following steps create a directory to hold your log, edit the
   resource file (Twpsk), compile twlog, copy the executable and resource
   files to their install locations.

1)  As your normal user, run the make command to install twcwDir in
    your home directory -

       make

2)  Then, as root, run the command -

       make install

3)  Edit the resource file, Twlog

    The "make install" copied Twlog to:   /usr/X11R6/lib/X11/app-defaults
    That file has some generic settings.  You will want to change some of
    them.  You could, as root, edit the copy made by the "make install".

    Or, to make it easier to edit, you can copy Twcw to one of the locations
    below.  Resource files in these locations will override the settings
    in the generic file.

         append it to the .Xdefaults file in your home directory

    or   copy it to your home directory

    or   I have a directory (app-defaults) in my home directory and copy
         all resource files there.  Then, in my start up script say:

         XAPPLRESDIR=$HOME/app-defaults
         export XAPPLRESDIR


   You may also, as root, do a "make remove" to delete the installed files.

TESTING:

   If all went well, you should be able to run the program now.  cd to your
   home directory and run twcw. It will fork sendCW as a child process.

   If you see the main window, push the Help button on the menu bar and read
   the fine manual.


CALIBRATION:

   By now, you should have things working pretty good, but the cw speed may
   need to be calibrated.  Start twcw and look at the messages printed.  If
   you see a line like this:

      Using gettimeofday for the timebase.

   then you do not need to calibrate the timing.  The program does it for
   you.  It may take a few seconds to do this whenever you change speeds.
   The cursor will be a clock while it is calibrating.

   If the message at start up was:

      Using RDTSC for the timebase.

   Great! Your CPU has a RDTSC instruction.  This method will change speeds
   without a delay.  Under the menubar's File button is a PARIS button.
   This file has the word PARIS repeated 20 times.  At 20 wpm, it should
   take exactly 60 seconds to send.  I put an E at the end to make it
   easier to time.  So,


   1. Set the WPM to 20 wpm.  Turn XMIT off and SIDETONE on.
   
   2. Click on File in the menubar and then PARIS in the drop down menu.
      This will load the file into the text widget.
   
   3. Click Xmit and time how long it takes to send the PARIS file.  It
      should take exactly 60 seconds. If not, do this calculation -

      60/time * cpuSpeed

      where
         time = the time in seconds it took to send the file
         cpuSpeed = the current value of twcw.cpuSpeed in Twcw

   4. Edit the Twcw you copied and change the value of cpuSpeed to the
      result of your calculation.

   5. Exit and restart twcw and test it again.  You can repeat this
      as needed, always using the current value of cpuSpeed, but I've
      never had to do it more than once or twice.


INTERFACE:

     WARNING:  THIS INTERFACE CAN DAMAGE YOUR EQUIPMENT.  I AM NOT
               RESPONSIBLE FOR ANY DAMAGE TO ANY OF YOUR EQUIPMENT.

   So, use xv or xpaint to view the file interface.gif.  This is the
   interface I use.  The chip is a opto-coupler, a transistor with a
   photo-sensitive base, and a led to drive the base.   Since there is no 
   electrical connection between the rig and the serial port, it provides 
   good isolation between the rig and the computer.  It is capable of
   switching up to 70 volts, so check the voltage across your key contacts.

   I mounted the chip socket on a PC board about 1 inch square   Make sure 
   you have the most positive key voltage connected to the Key Hi (pin 5) 
   and the most negative voltage to Key Lo (pin 4).
   
   The only other component needed is a resistor.  I used a decade box to 
   find the maximum resistor value that would provide enough drive to key 
   the rig.  For me, it was a 1K ohm resistor.  You may need something 
   different, so start with a high resistance and work down until it starts
   to key.

   Once it is working, it is easy to put the whole circuit inside the cover
   of the RS232 connector.  This makes for a very neat set up, just a cable
   with an RS232 connector on one end and a phone jack on the other.  I
   also hooked in a straight key by connecting it across the connections on
   the phone jack.


FINAL:

   A thank you goes to Vibroplex.  They allowed me to use a gif file
   from there Web page for the program's icon.  You can visit Vibroplex 
   at www.vibroplex.com and say Hi to Mitch, W4OA. 
   
   To date, I have used twcw for over 100 QSOs, and it has been very solid.
   One of the best QSOs was when I got a compliment on my fist by someone 
   who didn't know I was using a computer.

   If you are still having problems, send me all the info on the error to
   the e-mail address below and I'll be glad to help.

   If everything is OK, then still, send me e-mail.  I'd like to hear what
   you think.  Are there any additional menu function, features needed,
   bugs, typos, general comments, just to say Hi!  Whatever. 


PLS SEND COMMENTS TO:       wa0eir@comcast.net

73,  
Ted - WA0EIR

