Kantronics KPC–3 Plus User Manual page 106

Hide thumbs Also See for KPC–3 Plus:
Table of Contents

Advertisement

To use the KA-Node as a means of connecting to some other node or end-user, you
must first connect to the KA-Node. At the cmd: prompt on your TNC, issue a connect
request to the callsign of the KA-Node, let's say it's been named LAW. When you make
connection you will see the following messages on your display:
*** CONNECTED TO LAW
### CONNECTED TO WILD NODE LAW (NØGRG) CHANNEL A
ENTER COMMAND B,C,J,N,X, or Help ?
The *** CONNECTED message is sent by your local TNC to your terminal, and the ###
CONNECTED TO NODE message comes from the distant KA-Node. NØGRG is the
MYCALL of the station containing the KA-Node in this example, WILD indicates that he
is running a ―wildcard‖ node, and CHANNEL A indicates that you have connected to its
channel A. If A is in use, you may obtain channel B. The channels, or circuits, are
assigned by the KA-Node as needed.
After connecting to the KA-Node, you are in CONVERS mode at your own station, 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 response 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:
106

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents