[aprssig] LINKn-N linear DIGI systems
bruninga at usna.edu
Thu Jul 29 09:20:17 CDT 2004
I have suggested some digipeater LINKn-N systems
in the mid Atlantic area along the coast and some
COASTn-N, 81LNKn-N, 85LNKn-N, 95LNKn-N
View the APRSdos screen capture of these digis with their
PHG circles overwhich I have drawn the suggeted LINKS:
Notice how the COASTn-N system will be relatively
immune to QRM because of its distance from BALTO
and DC areas and how the I-81 system would use
digis on the WEST side of the I-81 valley which also
do not hear into BALTO/DC/Richmond etc...
I-95 will also be a GREAT long distance LINKn-N
system because it carries a tremendous load of long
haul traffic along the east coast to Florida. And
advantageously, from Richmond to Florida it does
not go through ANY large cities or population densities.
Setting up these LINKn-N's is trivial since all the
digi's exist already. All the remote sysops need
to do is to change from:
To the new settings of:
Where of course "LINK" is given the proper name for
the link system involved.
Existing users of WIDEn-N will not be affected though
those that use LONG hops will have LONGER packets
and should be encouraged to cut back to the hop
length recommended in their area (no more than 3
in the metro areas)...
For more reading on this new n-N Paradigm, you can read:
ALSO, the screen capture above shows the now standard
PHG circles "for mobiles". So although some gaps may
appear along the links, these are only small gaps in
Mobile coverage, but they are not gaps in the LINK. This
is because PHG circles are now routinely drawn at HALF
their RF range to give a better user view of MOBILE
coverage. Whereas the DIGI's can all talk to each other
easily beyond that.
The above screen capture is only a recommendation.
Locals in the area who better know the coverage of
their digis should decide what is best. But please think
in terms of routing LINKn-N paths "around" population
densities and not THROUGH them.
de WB4APR, Bob
More information about the aprssig