Kantronics KPC-9612 Plus, Руководство пользователя

Страница: 197 / 348

After connecting to the KA-Node, you are in CONVERS mode at your own sta-
tion, and the KA-Node is waiting for a command. You issue a command to the
node by STAYING IN CONVERS MODE.
Note: The KA-Node will interpret the data you send as its commands.
At this point, let’s assume that you wish to know what other KA-Nodes are
nearby. You would issue the NODES command by typing N, or NODES, in re-
sponse to the KA-Node “enter command” prompt. You will receive a list of
KA-Nodes which have recently been heard. For example, let’s suppose that KC
was heard by LAW. Your list received from the Nodes command would be:
KC (NØAPJ-2) 12/23/87 02:38:45
ENTER COMMAND B,C,J,N,X, or Help ?
KC denotes the KA-Node callsign (MYNODE), the MYCALL of the KA-Node
station is in parentheses, followed by date and time heard. If LAW had heard
nothing, it would respond with:
NO KNOWN NODES
You may, instead, wish to know what other stations the KA-Node has heard
lately. This would be accomplished by sending a J for the JHEARD command.
The node will respond by listing its own MHEARD log. The list will contain end
user and node callsigns and is the same type of list you get by using your own
MHEARD command at the cmd: prompt.
At this point, let’s suppose that you would like to connect to the node called KC
through your current connection with LAW. Just issue a connect request to KC as
follows in response to the “enter command” from LAW:
CONNECT KC
The response will be:
###LINK MADE
###CONNECTED TO NODE KC (NØAPJ-2) CHANNEL A
ENTER COMMAND B,C,J,N,X, or Help ?
At this point you are “patched” through the KA-Node LAW to the node KC.
When LAW issued the connect request to KC it used your own call but sub-
tracted a count of one from your SSID. For example, if you connected to LAW
KA-Node Modes of Operation
KPC-9612 Plus v 8.2 181 User’s Guide