MESSAGES FROM THE TNC
62
Link state is:
This message is output in response to the CONNECT, DISCONNECT and RECONNECT com-
mands if the state of the link does not permit the requested action. It is prefaced by
Can't
CONNECT
or
Can't DISCONNECT
or
Can't RECONNECT
as appropriate and will be followed
by the current link state. A CONNECT command with no options will display the current link
state.
Current link states are:
Both devices busy
Both TNCs involved in the connection are unable to accept any more data.
CONNECTED to (callsign v path)
Your TNC is currently connected to the indicated station, using the path given.
CONNECT in progress
Your TNC is attempting to establish a connection.
Device busy
Your TNC is unable to accept any more data from the remote station at this time.
DISC in progress
Your TNC is attempting to disconnect from another station.
DISCONNECTED
No connection exists on the current stream.
FRMR in progress
Your TNC has detected an error in the protocol. This is normally caused by two TNCs using
the same callsign, resulting in both of them trying to respond to the same message.
REJ frame sent
Your TNC has rejected a packet sent by another TNC. This may be caused by a frame being
received twice, or by a frame being received out of sequence.
REJ sent and device busy
Your TNC has rejected a packet sent by another TNC and it is also unable to receive any
more data from the remote station at this time.
REJ sent and remote busy
Your TNC has rejected a packet sent by another station and the other station is unable to
accept any more data from you.
REJ sent and both devices busy
Your TNC has rejected a packet sent by another station and both, your TNC and the remote
stations TNC, are unable to accept any more data.
Remote device busy
The remote TNC is unable to receive any more data from the radio at this time.
Waiting ACK and device busy
Your TNC has sent a packet to another station and is waiting for the acknowledgment, but
your TNC is not able to accept any data from the radio at this time.