RS 232 TROUBLESHOOTING CHECKLIST

• HECC 80/1

• HECC 80/3**

• GN6 & 0P

TROUBLESHOOTING CHECKLIST - HECC 80/1

CANNOT RECEIVE DATA AT CONTROL

• Cable wired correctly?
• Baud rates match?
• CPU jumpered for RS 232?
• Remote device sends 10 null characters (Control-@) at end of program, or program ends with M02 or M30 command?
• PROM correct revision level?
• Configuration diagnostic shows tape punch interface option?
• Remote device is configured not to expect handshaking, and for 7 data bits, even parity, and 1 stop bit?
• Data being received at pin 3 of cable plug at control end?
• Cable OK between RS 232 socket and CPU board?
• CPU board bad? DS1489N receiving data?

CANNOT RECEIVE DATA AT REMOTE

• Cable wired correctly?
• Baud rates match?
• CPU jumpered for RS 232?
• Remote device is configured not to expect handshaking, and for 7 data bits, even parity, and 1 stop bit?
• Configuration diagnostic shows tape punch interface option?
• Data being received at pin 3 of cable plug at remote end?
• Connected to correct port at remote end?
• Cable OK between RS 232 socket and CPU board?
• CPU board bad?

TROUBLESHOOTING CHECKLIST HECC 80/3xx

CANNOT RECEIVE DATA AT CONTROL

• Cable wired correctly?
• Baud rates match?
• Remote device sends 10 null characters (Control-@) at end of program, or program ends with M02 or M30 command?
• Remote device is configured not to expect handshaking, and for 7 data bits, even parity, and 1 stop bit?
• Data being received at pin 3 of cable plug at control end?
• Cable plugged into proper port at remote device?
• Cable OK between RS 232 socket and CPU board?
• Swap L2 and L10 boards in control.
• CPU board bad? DS1489N receiving data?

CANNOT RECEIVE DATA AT REMOTE

• Cable wired correctly?
• Baud rates match?
• Remote device is configured not to expect handshaking, and for 7 data bits, even parity, and 1 stop bit?
• Data being received at pin 3 of cable plug at remote end?
• Cable plugged into proper port at remote device?
• Cable OK between RS 232 socket and CPU board?
• Swap L2 and L10 boards in control.
• Repair RS 232 port at remote.

TROUBLESHOOTING CHECKLIST GN6 & OP

CANNOT RECEIVE DATA AT CONTROL

• Cable wired correctly?
• Baud rates match?
• Parameters 340 and 341, and SET page parameters set correctly?
• Remote device sent % to indicate end of program?
• Remote device is configured for 7 data bits, even parity, and 1 stop bit, and not to expect handshaking?
• Data being received at pin 3 of cable plug at control end?
• Cable plugged into proper port at remote device?
• Replace CRTC/PUNCHER board in control (Master PCB in OP control)

CANNOT RECEIVE DATA AT REMOTE

• Cable wired correctly?
• Baud rates match?
• Parameters 340 and 341, and SET page parameters set correctly?
• Remote device is configured for 7 data bits, even parity, and 1 stop bit, and not to expect handshaking?
• Data being received at pin 3 of cable plug at remote end?
• Cable plugged into proper port at remote device?
• Replace CRTC/PUNCHER board in control. (Master PCB in OP control)
• Repair RS 232 port at remote.

If data signal is present on pin 13 but not on pin 11 then the DS1489N is defective or the signal is not strong enough.