with WØXI, LAW connected (via your request) to KC with WØXI-15. This is
automatic.
At this point, you could connect to another KA-Node, some other network node
using AX.25 as an uplink or downlink protocol, or to an end-user. Let’s assume
that you desire to connect to NØKN. So, just enter in response to the node “enter
command” above:
C NØKN STAY
and you’ll get the response:
###LINK MADE
+
We’ll explain the “STAY” later.
You are now connected to NØKN. If you have issued a connect command to a
KA-Node, and realize that you have made a mistake with the call, or for any
other reason wish to cancel the connection, you may do so by using the ABORT
command. In order for the abort to work, it MUST be the first word entered fol-
lowing the connect command and must be spelled out entirely. For instance if
you tell the KA-Node:
C KB5EEG
and then decide to abort the connect, your next entry must be:
ABORT
Any other entry will cancel any possible abort of the connection, and you must
wait for the KA-Node to retry out (e.g., because it will try to connect to
KB5EEG).
Now that you are connected to NØKN, you can carry on a normal packet QSO.
While everything appears “normal” and AX.25 compatible, acknowledgments to
your packets are generated by the KA-Node directly connected to you. Each link
in the chain/pathway takes care of its own errors. In other words, the link be
-
tween KC and LAW handles its own error checking. In this way, one weak link
will not cause end-to-end packets and acknowledgments to be repeated as they
would with digipeating. The result is substantial improvement in throughput for
connections using nodes.
KA-Node Packet Modes of Operation
KAM’98 v 8.3 203 User’s Guide
To Next Page
Loading...