KA-NODE
27
The long (JHEARD L) version of this command will also show the destination field and digipeaters
used. This list would look like:
(KAM)
LAWKAN/H* >W0XI 01/09/88 08:25:15
VIA KSKU, TOP*, KSKU
N66046/V >BEACON 01/10/88 00:03:10
WK5M-3/H* >WD0EMR 01/10/88 00:03:19
VIA W0XI, TOP*
WD0EMR/V >KC 01/10/88 00:04:15
VIA KSTOP, KCMO
(KPC-4)
LAWKAN/1* >W0XI 01/09/88 08:25:15
VIA KSKU, TOP*, KSKU
N66046/2 >BEACON 01/10/88 00:03:10
WK5M-3/1* >WD0EMR 01/10/88 00:03:19
VIA W0XI, TOP*
WD0EMR/2 >KC 01/10/88 00:04:15
VIA KSTOP, KCMO
(KPC-1, 2 or 2400)
LAWKAN >W0XI 01/09/88 08:25:15
VIA KSKU, TOP*, KSKU
N66046 >BEACON 01/10/88 00:03:10
WK5M-3/ >WD0EMR 01/10/88 00:03:19
VIA W0XI, TOP*
WD0EMR >KC 01/10/88 00:04:15
VIA KSTOP, KCMO
Nodes [Short | Long]
This command will cause the node to return a list of KA-NODES it has heard, as well as NET/ROM
or TheNet nodes. The format of the list is similar to that of the JHEARD list above.
XConnect
callsign
(KAM and KPC-4 only)
This command will cause the node to issue a connect request to callsign in the usual AX.25 format
from the node but uses the other port of the KA-NODE. Cross-connecting enables you to gain ac-
cess via the node to another frequency.
To Next Page
Loading...
