debug

The debug option displays diagnostic information that can help you solve a communications problem or analyze communications in certain situations.

The debug command needs two arguments:
 

debug setting true or false

These are the debug settings and the diagnostic information they display:

debug crt

Causes screen-formatting and cursor-positioning characters to be displayed in a printable form on your screen (and written to a get file if one is open). Cursor-positioning commands will appear in the format:
<row, col>
where row and col are numbers indicating the row and column to which the cursor is to be moved.
Screen-formatting commands will appear in the format:
<-num, num>
The first number is negative to distinguish screen-formatting commands from cursor-positioning commands. See Appendix B of the Autolog User's Guide for the meaning of the numeric screen-formatting codes.
debug input
Displays modem responses (such as OK or CONNECT) received by Autolog, which aren't normally displayed.
debug output
Displays modem commands that Autolog sends out to the modem that normally aren't displayed (such as the ATDT command to dial a phone number).
debug port
Note debug port works only on UNIX systems.
Displays diagnostic information about your communications port whenever you enter a command that affects the port (such as link, baud, or parity).
debug protocol
Displays diagnostic information about error-correcting file transfers.
debug script
Enables single-stepping through a script file.
debug uart
Note debug uart is not supported by UNIX systems. Use debug port instead under UNIX.

Displays UART errors (errors detected by your communications port hardware and software) and breaks received. These can indicate baud rate, flow control, noise, and other communications port problems. These are the types of errors or conditions that may be reported:

Framing error indicates that a received character had no stop bit, which may be a symptom of line noise or mismatched baud rates.
Overrun error indicates that incoming characters are being received faster than your computer can read them. Hardware flow control can help minimize this problem, or you may need to connect at a slower baud rate.
Parity error indicates that a character was received with the wrong parity, which may be a sign that you need to use the parity command to set parity appropriately or a symptom of a character damaged by line noise.
Break indicates that a break condition was received from the remote system.
Modem flow control changes indicate the number of times the hardware flow control signals to your modem changed. Many modem flow control changes indicate a slow or busy local computer or a noisy phone. If you are losing characters (or experiencing many file transfer retries) but no flow control changes are indicated, you may not have flow control turned on or it may not be supported by or configured correctly for your hardware.