MESSAGES FROM THE TNC
59
Messages From the TNC
*** (callsign) busy
*** DISCONNECTED
The Packet station you were attempting to connect to (callsign) is unable to accept connects.
Already connected on stream
You are attempting to connect to someone you are already connected to on another stream.
The STATUS command will show you who you are connected to and on what stream.
CALIBRATE MODE: PRESS R, T, OR X
This message appears on your screen when you enter the Calibrate Mode and prompts you to
press
R
for receive,
T
for transmit and
X
for exit back to Command Mode.
cmd:
This is the Command Mode's prompt for input. Any characters entered after the TNC prints
cmd:
will be used as command input and not packet data.
Can't CONNECT
Already connected on stream x
You cannot CONNECT to the same station on two different streams. Use the STATUS command
to see who is connected.
Can't DISCONNECT
You are not connected on this stream, so therefore cannot disconnect. This message will be fol-
lowed by the stream and a
Link state is:
message, described under "Link state is:" later
in this section.
Can't RECONNECT
Already connected on stream x
The station you are trying to RECONNECT is on a different stream. Use the STATUS command
to see who is connected.
*** connect request
A remote Packet station has attempted to connect to you, but there is not a valid stream avail-
able for the connection to be entered on. The remote station will be sent a busy message,
<DM> packet. See the USERS and MAXUSERS command for setting more streams and allow-
ing more connects at one time if desired. Also be sure CONOK is ON.
*** CONNECTED TO CALL1 [VIA call2 ... call9]
A Packet connection has taken place. This can happen by you issuing a connect request or a
connect request coming from a remote station. CALL will be the callsign entered in the remote
stations MYCALL and if a path was used it will be shown.
Device busy
The TNC is not able to accept further data packets from the radio for the time being. An RNR
(Receiver Not Ready) has been sent.
*** DISCONNECTED
The packet connection no longer exists.
DISCONNECT in progress
A disconnect packet has already been issued. Connects are not valid in this state, and a second
DISCONNECT command will cause a "retry count exceeded" condition.