HAM Radio 3/hamradioversion3.0examsandprograms1992.iso/packet/thenet08/readme.1st

Text File | 1991-11-08 | 4KB | 70 lines

Perhaps not clearly stated in the docs is the fact that there are TWO
rom images provided.  One is 2.08 which features just the aliases in the
node routes list.  2.08B features both the alias and the callsign.  Your
option as to which format you prefer.  Some NodeOps like the standard
2.08 and others like the 2.08B.   Other than that, the images are identical.

Also, with this version you will find the SYSOP settable parameters have
been shortened AND placed in a different order.  To familiarize yourself
with these changes, suggest you print out the parameter menu.  Feedback
from some users indicate they didn't pay attention to the parameter changes
and ended up by setting their node parameters incorrectly.  Typically they
had their node(s) not recognizing broadcasts from other nodes.

Before making any parameter changes, suggest you review the parameter
explanations in the TN206.DOC file and match em up with the new order
in this version.

This code version works quite well and all reports of problems from the
users thusfar have turned out to be incorrectly set parameters (the
recommended defaults work great for "standard" applications) or due to
external RF or power glitches scrambling the TNC memory (or users not
pulling the TNC battery jumper for 1 minute before inserting the new
"Plus" chip).

One late reported bug (9-20-91) has been uncovered.   It concerns the audio
frequency of the "KEY SPACE" command.  Appears it really does not yield
the space tone frequency, rather a combination of mark and space.  This then
affects the frequency of the "KEY DIDDLE" command which then gives a
"diddle" of the mark, plus or minus the space diddle.  There is ZERO effect
on node operation and is only mentioned for those who might attempt to use
the "K S" space alignment tone to set up a frequency on a HF radio.  The
"KEY MARK" alignment tone is correct and should be used for this rather
infrequent application.  The "KEY DIDDLE" command still is useful in checking
deviation on FM, or on setting mic gain on HF SSB radios.

Also on this disk, I have added a "MISC" subdirectory.  The files here
include the TNC DCD mods for both VHF and HF.  These mods are for the
TNC-2 style of units which include the XR modem chips.  Tiny-2s take a
more complicated mod.  The mod info in the files work the same as the
mod kits provided by TAPR, except in this case they are less expensive.

The R95 utility is one that converts binary into a format that is accepted
by the packet BBS system.  Files can be ZIPPed to compress their size,
then R95ed for packet transmission.  The nice feature of R95 is that it
has the capability to chop a large file into say, 2K segments for BBS
handling, then reassembled on the distant end.

The latest TNC-2 TAPR firmware release is 1.1.7 and the notes describing
the new features and commands are contained in a series of files that
can be placed in your local BBS directory, if you wish.

I am also adding the PATHCALC program.  This is a very useful tool for
evaluating the radio parameters between two sites.  As we move to higher
data speeds, it will be more necessary than ever to provide "solid" RF paths.
Part of the reason for this is that the effects of multi-path will have more
detrimental affects on 9600 baud data, then say 1200.  Unless the radios
used at higher data rates have IF filters specifically designed for a flat
phase delay across the 0 - 7 KHz audio range, higher radio path SNR's will
be required to compensate.  PATHCALC allows you to do desktop evaluations of
various equipment/frequency configurations of your present site, or possible
candidate sites.  PATHCALC is menu driven but does require you to have a
detailed map showing latitude/longitude and ground elevation data between the
two sites.  Detailed maps may be available from FAA Flight Service Stations or
local stationary and bookstores.

An additional benefit of 2.08/2.08B is the elimination of "impossible" route
entries from the display response when doing the "N node call/alias" command.

Good luck, -=73=- de Jack, [e-mail]