Boldly Go Collection/version40.iso/TS/05B/TOR109.ZIP/DOCS

Text File | 1992-01-14 | 23.3 KB | 612 lines

PCTOR V1.09

(TORBIOS V1.07)

PCTOR, TORBIOS (c) Johan Forrer KC7WW 1991,1992


Author: Johan B. Forrer KC7WW
26553 Priceview Drive
Monroe, OR 97456
United States of America


CIS id: 70730,3472


Shareware notice



These programs are distributed as Shareware products. You may
freely copy and share the programs with your friends, associates
and other radio amateurs. PCTOR or TORBIOS may not be sold or
distributed with another product without the express written
permission of the author. The author, Johan Forrer, KC7WW will
only support unmodified copies of this software.

If you decide to use any of these products, you should become a
registered user by sending $20.00 or equivalent in foreign
currency together with the completed registration form to the
author. All transactions must be drawn on US banks. Upon receipt
of your registration, you will receive one free update disk
containing the latest release of the software . You will also be
notified of future developments. Improvements are continually
being made and exciting additions are under way or in the process
of being implemented such as a DSP software modem front end for
i486 compatible machines.

If you are not satisfied with the program after registering it,
you have 30 days from your registration date to return it for a
full refund of your money, no questions asked.

Commercial Users please contact Johan Forrer directly for
modifications and/or details of Site licensing.

The helpful suggestions of Frank Gorichar, W7JUF, who beta tested
early versions of this software is greatly appreciated. Helpful
suggestions by Vic Poor, W5SMM was invaluable especially on
compatibility with MBBIOS and PAMS. Thanks to Frank Wyatt, N6FW
for forwarding technical documentation to me.


     Please support the efforts of shareware developers.
Table of contents



1.0  PCTOR and TORBIOS what does it do ?

     1.1  Minimum requirements to run PCTOR and TORBIOS

     1.2  CAUTION

     1.3  Planned enhancements

2.0  Introduction

3.0  Hardware Interface

4.0  Installation

     4.1  Software

     4.2  Customizing the configuration file

5.0  Operating PCTOR

     5.1 Function keys

     5.2 Command menu

6.0  Principle of operation

7.0  Disclaimer



1.0 PCTOR and TORBIOS what does it do ?


PCTOR and TORBIOS makes it possible to run AMTOR without the
investment of a hardware TNC. TORBIOS is the low-level
interface/emulator and PCTOR is a user-interface.

There are two versions of the BIOS available. Distributed with
this software is generic low-level emulation software that uses
only PC hardware. For applications that include multitasking or
working with Microsoft Windows, further requirements must be met.
These are provided in a special version of the BIOS. Contact the
author about these requirements.



This main features of PCTOR, the user interface are:



1  - Split screen operation: Data received through the AMTOR
     translator is displayed on the upper window. The operator's
     keyboard entry is displayed on the lower window. A status
     window shows real-time operational status of the digital
     translator. This includes, timing, path propagation delay,
     processor idle time, link status, selcals, and more.

2 -  All AMTOR modes are supported: ARQ, FEQ, and "Listen".

3 -  The user may define several text buffers, i.e. brag tape,
     CQ messages, etc. that may be loaded for transmission with
     with one key stroke.

4 -  Text files my be transmitted. Typically the user will
     prepare these off-line.

5 -  Unshift-on-space (UOS) option.

6 -  "PLX"-method for upper/lower case.

7 -  A "high" reliability option based on bit averaging.

8 -  Receive data can be optionally be captured in a file.
     Automatic time stamps, as well as user-initiated time stamps
     may be entered into this capture file. The capture file can
     be read using an ordinary text editor.

9 -  PCTOR can open a Dos shell (viable only for 386/486)
     with TORBIOS, the low level AMTOR decoder running. The low
     level decoder has buffered I/O queues to accept traffic even
     when PCTOR has opened a DOS shell.

10 - The user can customize the working environment through use
     of a configuration file that is read when PCTOR starts up.The main features of TORBIOS are:



1  -  A collection of routines performing low-level time-
      critical translation of modem signals to ascii.

2  -  A subset of INT14 calls are supported. These calls is a
      minimum requirement to be able to run APLINK/PAMS with
      this software AMTOR emulation.  A superset of function
      calls are available that makes full use of the capabilities
      of the software emulation.

3  -  TORBIOS is written in Assembler.1.1 Minimum requirements to run PCTOR and TORBIOS


PCTOR and TORBIOS will run on an IBM PC or close compatible
computer. DOS 3.1 or higher is required. A monochrome or EGA/VGA
display adaptor will work. Although the software will run on a
floppy-based system, a hard disk is recommended.

On the radio side, an HF modem, i.e. ST-6 or equivalent is
required to decode received audio to +/- 12V RS232 logic signals.
For transmission of AMTOR over the air, the user also has to
provide a PTT interface and either AFSK or FSK. These interfaces
are often included in an HF modem. If the software is used for
monitoring only, only the HF modem is required. The HF modem is
required to convert audio tones to RS232 compatible digital
levels required by TORBIOS.

TORBIOS uses some of the signal lines of the standard COM1 or
COM2 serial ports as a digital interface (the user specifies
which COM port - see "Installation - software").  1.2 Caution



This software may not be suitable for all working environments.
The user should therefore proceed with the usual caution and make
sure critical software is backed up.

The author has done extensive tests on a very modest PC-
compatible system running an 8 Mhz V20 processor and 20 MB hard
disk. No other potentially competing resident software was used.
The author has recently upgraded to a 486 clone and 80 MB hard
drive and DOS 5.0 software. There was some incompatibilities,
however these have since been corrected.

Every effort has been made to ensure that the software is "well
behaved", however, the user is reminded that this software relies
on critical timing. It "tricks" the system by speeding the system
timer up to run at an one millisecond interrupt rate and installs
itself in the timer interrupt chain. Normal system timer
functionality is retained, i.e. time-of-day and floppy disk
timeout activities. The user must thus be careful not to run
other software that relies on similar "tricks" as the
consequences is indeterminable.

Normal program usage and program termination will undo the
actions of TORBIOS and restore normal system operation. Should a
program failure occur, the only way to restore normal system
operation is to reboot DOS.

1.3 Planned enhancements


Several enhancements are planned for release in the near future.
As a registered user you will be notified of these when it
becomes available. These include:

* SAA/CUA standard interface.
* Operation under windows as an option.
* DSP modem and tuning indicator (for 386/486 machines).2.0 Introduction



TORBIOS is an implementation of CCIR specification 476-2 on an
IBM personal computer or compatible computer. As such, it
replaces the need for dedicated TNC hardware and is an attractive
alternative for the casual user evaluating a new operating mode,
as well as the serious developer that needs to embed low level
I/O functionality into a system.

PCTOR is a user interface program that works in conjunction with
TORBIOS that enables a user to operate and monitor TOR traffic
with a minimum of fuss. It has a multiple-window user interface.
The keyboard function keys are used to control operations. Split
screen displays shows the progression of the dialogue and the
real-time status of low-level internal functions.

PCTOR was developed using the sophistication of C++ with calls to
TORBIOS, a resident driver that was written in assembly language.
3.0 Hardware interface



TORBIOS interfaces through signals of the COM1 or COM2 RS232
port. The following allocation of RS232 signals have been made:
Other signal pins may be connected, however will play no part in
the operation of PCTOR.


             For a 25-pin connector:
pin 20  (DTR) - output data bits (mark -12V, space +12V)
pin 4   (RTS) - PTT              (off  -12V, on    +12V)
pin 8   (DCD) - input data bits  (mark +12V, space -12V)


If your RTTY modem and interface requires different logic levels,
these may be configured using either the on-line command menu in
PCTOR, or included in a configuration file "TOR.CNF". An example
has been included. (See below for more details in "customizing
the setup file).4.0 Installation


4.1 Software


It is assumed that a hard disk is available, though the program
can be run off a floppy disk as well. In fact it is suggested
that you first run off a floppy disk to see if this software is
compatible with other software that you may have on your system.

1. Create a new subdirectory and change directory to it, i.e.

   mkdir tor
   cd tor

2. Copy the contents of the floppy to the new subdirectory.

   copy a:*.*

   The following files will be copied:

   tor.exe    -- The split screen AMTOR program.
   tor.cnf    -- Setup file to custom configure your program.
   tor.doc    -- This documentation.
   TORBIOS.COM  -- COM1 TSR driver.
   TORBIOS2.COM -- COM2 TSR driver.
   brag.tor   -- An example test file to load.
   cq.tor     -- Another example file to load.
   AMTOR.BAT  -- A batch file to run TOR with a parameter. Check
                 to see which communications port COM 1 or 2 you
                 desire.

3. Customize tor.cnf  (see 4.2 Customizing the configuration)

4. Run the batch file AMTOR, i.e. type AMTOR <enter>, or
   alternatively run it directly from the command line:

   type TORBIOS <enter>  ...... if you are using COM1
          or
        TORBIOS2 <enter> ...... if you are using COM2

(If you use DOS 5.0, TORBIOS may be loaded "high" using the
loadhigh TORBIOS command.)

   then type TOR <enter>  .....  to run the program.

   Note that there is an optional parameter on the "TOR"
   command line. This parameter allows the setting of the size of
   the screens on the split-screen display, i.e.

   TOR 13   .... will run TOR and divide the split-screen display
                 into approximately 12 lines each.
4.2 Customizing the configuration



To enable a user to streamline the setup of the program to his
requirements, a configuration file, "tor.cnf" is read during
startup. Read and edit the contents of the provided file
"tor.cnf" to suit your own preferences. This file is optional,
but when not found, the system will use defaults.



The following entries may be customized:

id:KCWW/KC7WW             ----- set your identity selcal/callsign
selcal:WDRZ/WA8DRZ/6      ----- set the  startup selcal/callsign.
wru:QRA KC7WW KCWW        ----- your WRU text.
txdelay:30                ----- delay after PTT on till data out
outmask:0                 ----- normal/inverted output data logic
inmask:0                  ----- normal/inverted input  data logic
timing:25                 ----- system clock timing adjustment
uos:0                     ----- unshift-on-space off
case:0                    ----- upper/lower case off
log:1                     ----- receive data capture (logging)
logfile:tor.log           ----- data capture filename
rel:0                     ----- reliability off (bit averaging)

Note that the syntax isn't tested very rigorously. Please check
your input carefully against the supplied example.

Since TORBIOS is supposed to work with any modem, the logic of
the input/output interface needs to be configurable. This is done
by setting up input and output "masks". There are two bits on the
output mask that need to be set (DTR - used for sending data
bits, and CTS - used for PTT control). On input there is only one
bit level that needs to be set (DCD - used for input data). The
meaning of these masks are as follows:


outmask:0    - normal RTS  normal DTR
        1    - normal RTS  invert DTR
        2    - invert RTS  normal DTR
        3    - invert RTS  invert DTR

inmask:0     - normal DCD
       1     - invert DCD

As a suggestion, leave the settings as outmask:0 and inmask:0

Until you have sorted out the required logic interfacing logic,
prepare your transceiver for low power output into a dummy load
(you may find your PTT unexpectedly comes on upon executing the
program).

Now run TOR. If your PTT comes on right away, the sense of RTS
must be inverted before further testing can be done (Try
outmask:2). Normally, TOR should put you in standby mode.

Next, on-the air tests will be necessary. Try to decode some FEC.
FEC will be decoded while in standby mode. To make sure that you
are in standby mode, hit F10. Tune in on an FEC transmission and
wait for it to sync. If it fails to decode anything, first try
changing the other sideband setting of your transceiver (if you
normally use LSB, try using USB). This will show whether it's the
interface logic or whether there is some other problem. If TOR
receives FEC in the other sideband setting, the sense of DCD
needs to be changed (Try inmask:1) and revert to your preferred
sideband setting (or RTTY setting if your transceiver has one).

The final test is to determine the logic level required for the
transmitted data. Try an ARQ call. If it fails, you need to
invert the sense of DTR (this will be either outmask:1 or
outmask:3 depending on the outcome of the RTS/PTT test above).

There is an additional timing-related entry, "timing:" that need
to be set up. This parameter allows external adjustment of the
system clock pulses to cater for systems with inaccurate clocks.
Very few PC's have accurate clocks and although the default value
(25) will work reasonable well in most cases, adjustment of this
parameter is very desirable. For determining the value of this
timing parameter, see  5.2 - Command menu: usage of the 'T'
option.
5.0 Operating PCTOR



Upon startup, the shareware banner will be displayed. Press any
key to proceed to the TOR screen.

TOR displays three windows: the status window, the received
traffic window, and the keyboard display.

CAUTION: PCTOR extends the function of the system timer. If TOR
is terminated abnormally, the system clock may not be working
correctly. TOR may be exited normally by hitting ESC once and
then selecting the "Q" option in the command menu.


The smallest window. at the top of the screen, is the status
window. It is updated in real time and some machines may show
some flickering. This is normal.

Link status information is displayed on the left hand side of the
status line.

Adjacent to the link status is the selcal/callsign of the remote
station. This data is used in establishing the link and also for
printing out identification data (see usage of the "Ins" key).

Next, the transmit data delay is shown. You may change this
parameter using the command menu.

Once some traffic start flowing, the block receive time will be
displayed. This is an internal timing parameter that cannot be
changed.

If the unshift-on-space (UOS) feature has been selected, this
will be displayed as a µ symbol.

If the user has selected the receive screen capture
(autologging), the a ¢ symbol will be displayed.

When the reliability option is selected a √ symbol will be
displayed.

If the user selected upper/lower case operation, there will be
two arrows, the first one is associated with the case of the
receive text, while the second one is associated with the
transmit case. An "up" arrow means upper case, while a "down"
arrow indicates lower case.

A 24 hour-format clock is also shown on the display. This clock
will be used for logging and time stamps. Note that this clock
displays local time as defined by DOS. UTC is used to enter time
in the outgoing data (see "Function keys").

An eleven bit analog indicator on the right hand side shows how
bit phasing is progressing. During FEQ or ARQ, the indicator
shows how much your clock and the other station's are differing
relative to each other.5.1 Function keys



The function keys have the following functions:

F1  - Initiate an ARQ call.
F2  - Initiate an FEC call.
F3  - Force a change-over (works only in ARQ).
F4  - Initiate QRT sequence (ends ARQ and FEC transmissions).
F5  - If receive text capture is enabled, will insert a timestamp
      into the log file.
F6  - Initiate ARQ listen mode.
F7  - Clear keyboard type ahead and special buffers (used for
      WRU), clears keyboard display.
SHFT F7 - Clears receive display.
F8  - Open a DOS shell (use with care - 386/486 machines).
F9  - Not used.
F10 - Abort any operation and revert to standby mode.

End - Enter the +? sequence into the keyboard buffer.
Ins - Enter an identification string into the keyboard buffer.
Del - Force LTR case during receive (FEC or ARQ).
Ctrl-Home - toggles "raw" data mode. For experimenters only -
      displays untranslated ITA2 (Baudot) code in Hex. This data
      is also written to the log for later analysis.

ESC - Calls up the command menu when in user mode. When in
      the Command menu, quits the program.

ALT-B - Enter the buffers menu. This allows a data buffer to be
      loaded into the keyboard buffer. The user prepares these
      buffers ahead of time using a text editor. These files have
      a "TOR" extension and will be loaded when TOR is
      initialized. Also note the usage of the ALT-1 through ALT-9
      keys as speedup keys to load any of these buffers with one
      keystroke.
ALT-C - Prompt user to enter the selcal/callsign of the remote
      station AND initiate an ARQ call immediately.
ALT-F - File transmission menu. Allows the transmission of text
      files while in FEC or ARQ. The transmitted text will be
      displayed as it is transmitted. There will be no echo to
      the receive window.
ALT-R - Prompt user for the selcal/callsign of the remote station
      WITHOUT initiating an ARQ call.
ALT-T - Enter UTC time into the keyboard buffer for transmission
      in FEC or ARQ.

5.2 Command Menu



The command menu (called up when the ESC key is pressed when in
the main display) has the following one letter commands:



C - Enable or disable upper/lower case operation.
D - Set the tx-delay. This sets the time delay after the PTT is
    activated to when data is sent. On slower switching equipment
    set it longer. Fast switching equipment set it short.
    Acceptable values range in 1 millisecond increments from 1 -
    50 ms. Default is 30 ms. This parameter may be adjusted to
    compensate for working local or DX distances, however, this
    practice is not normally required.

H - Help with the function keys.
I - Set your own ARQ identity.
L - Enable or disable receive capture (logging).
M - Modify the interface logic masks - see section 4.2.

T - Set clock timing. This parameter allows fine adjustments of
    the master clock. See Appendix A for more details.

U - Sets UOS (unshift on space) on or off.
W - Set up your WRU text.
Y - Sends out 500 HZ pulse train from pin 20 for diagnostic
    purposes.
X - Exit the command menu to main display.
Q - terminate PCTOR.



6.0 Principle of Operation



TORBIOS is a TSR software library that is installed as part of
DOS. The calling program usually installs it if it isn't there
already, also prevents it from being re-installed if it has been
loaded before. Two special versions of TORBIOS can be installed:
TORBIOS will interface with COM1 and TORBIOS2 will interface with
COM2. These programs is mutually exclusive as they both use the
same software entry point. The TSR must be installed before
running the TOR program. It need to be installed only once. After
installation the TOR program can be entered and exited as often
as you like without reloading TORBIOS.
APPENDIX A.


Experiencing problems setting your master clock timing ?


The most common feedback from users appears to be setting up
PCTOR's master clock timing. Once this is done, the user enters
the "magic" number into the configuration file that is used
automatically each time the program is started. Only when
installing the program on another computer will it be necessary
to reset this timing parameter.

Please note that this parameter has noting to do with the speed
of your computer, or whether you use an 8088 or 486. Its about
how to program a certain chip (8253/4) on the PC's motherboard.

Typical symptoms will be that either nothing happens when trying
to decode a FEC signal, or, the FEC sync is obtained, some text
is printed, however, synch is lost and only a few words of garble
is printed before it starts re-sync.

If you have a scope, or frequency counter available, try the
following (its not serious if you do not have access to test
equipment - you will just have to be a little patient and do some
common-sense trial and error. It will take a little longer, but
you will obtain the same end-result. Skip the next paragraph if
you do not have access to test equipment).

Enter the command menu (Hit ESC) and select the "Y" option. This
command will send a signal out of the COM port pin 20 (for 25 pin
RS-232). This signal should be set to as close to as you can to
500 Hz. Use the "+" and "-" keys to toggle the speed up or down.
When you have completed the test, return to the main display.

Tune in FEC mode to a strong FEC broadcast station, i.e. (KMI or
WOO on 8.087 Mhz, 8.534MHz). Observe the timing indicator on the
right hand corner of the status line. Notice that it may slide
slowly. The objective is to have it as stationary or indecisive
as possible. However, do not be concerned if you cannot get a
perfect steady display, that is quite normal.

Vary the timing value, one step at a time using the "+" or "-"
keys. After changing the clock setting, the previous value as
well as the new value will be displayed. You MUST then exit the
command menu for the new settings to become effective. Once back
to the main display, select STANDBY (F10) and wait for sync to be
detected. Notice that when you return from the command menu to
the main menu, you may see some received text being written to
the receive display. This is text that have been accumulated by
the low-level decoder and was stored in a system buffer while you
were using the command menu. This text should be ignored as the
changed clock setting was not yet in effect.

Once the optimal setting has been found, modify the configuration
file TOR.CNF to include the parameter for your system. Values
ranging from 0 to 36 is valid. This procedure set the system
clock close to the +/-50ppm requirement for AMTOR.7.0 Disclaimer


The author, Johan Forrer KC7WW is not responsible for any damage,
injury, loss of profit or gain associated with the use,
installation, or application of this software.



 January 1992
J.B.Forrer KC7WW
26553 Priceview Drive
Monroe, OR 97456
United States of America