Epson Multi-mode Data Controller MFJ-1278B - Manual (Page 300)

MFJ-1278B MULTI-MODE SYSTEM MESSAGES
Link Status Messages
These messages inform you of the status of AX.25 connections your MFJ-1278B may be
involved in. You can always interrogate the link status by giving the CONNECT command
without parameters. If you attempt a connection when your MFJ-1278B is not in the
disconnected state, the MFJ-1278B will display the link status but will take no other action.
The following messages appear in response to the CONNECT command.
Link state is: CONNECTED to call1 [VIA call2[,call3...,call9]]
This display shows the station your MFJ-1278B is connected to and the digipeater route if
any. The callsign sequence is the same sequence you would enter to initiate the connection.
Link state is: DISCONNECTED
No connection currently exists. You may issue the CONNECT command to initiate a
connection.
Link state is: CONNECT in progress
You have issued a connect request, but the acknowledgment from the other station has not
been received. If you issue a DISCONNE command, the connect process will be aborted.
Link state is: DISCONNECT in progress
You have issued a disconnect request, but the acknowledgment from the other station has not
been received. If you issue a second DISCONNE command, the MFJ-1278B will go
immediately to the disconnected state.
Link state is: FRMR in progress
The MFJ-1278B is connected but a protocol error has occurred. This should never happen
when two TAPR TNCs are connected. An improper implementation of the AX.25 protocol
could cause this state to be entered. The MFJ-1278B will attempt to re-synchronize frame
numbers with the TNC on the other end, although a disconnect may result. Connects are not
legal in this state, and a disconnect will start the disconnect process.
The MFJ-1278B will inform you whenever the link status changes. The link status may
change in response to a command you give the MFJ-1278B (CONNECT or DISCONNE), a
connect or disconnect request packet from another station, a disconnect due to the retry count
being exceeded, an automatic time-out disconnect (CHECK), or a protocol error.