Timewave DSP-232, Operating Manual

Page: 237 / 271

Chapter 13 Troubleshooting
too many packets outstanding
You typed enough data to fill the outgoing buffer in either the
Converse or Transparent mode. You can’t re-enter Converse
or Transparent mode until some of the packets have been sent.
WARNING: Beacon too often
You’ve set the
BEACON
interval timer to less than
90
(15
minutes) which is too often for busy channels.
WARNING: CHeck/FRack too small
You’ve set the CHECK timer for too short a time relative to
the FRACK timer.
WARNING: RESptime/FRack too large You’ve set the
RESPTIME
timer for too long a time relative
to the
FRACK
timer.
WARNING: TXdelay too short
The
TXDELAY
timer has been set too short to send at least
one complete flag before the start of a packet.
WARNING: AUdelay > TXdelay
The AUDELAY timer has been set equal to or greater than the
TXDELAY
timer.
Packet Link Status Messages Link status messages show you the status of AX.25
connections in which your DSP is involved.
*** connect request:call1 [via call2[,call3...,call9]]
Your DSP has received, but not accepted, a connect request
from another station.
*** DISCONNECTED:
call
Your DSP has switched to the disconnected state. This
message may be preceded by a message explaining the reason
for the disconnect.
*** Retry count exceeded
Your DSP has been disconnected because of a retry
*** DISCONNECTED:
call
failure, rather than a disconnect request, from one of the
stations.
***
call
busy
Your connect request was rejected by a busy
*** DISCONNECTED:
call
signal from another station.
FRMR sent: xx xx xxor FRMR rcvd: xx xx xx
You’re connected but a protocol error has occurred. Your
DSP is trying to re-synchronize frame numbers with the
distant station’s packet system. The string
xx xx xx is
replaced with the hex codes for the three bytes sent in the
FRMR frame.
13-6 September, 05