Gasboy CFN Series Diagnostic Manual - Manual (Page 103)

Site Controller II
2210 3-39
Terminal communications are down. The system is working.
Possible Cause Checks Corrective Action
Terminal turned off. Check terminal power
indicator Turn on, if off
Terminal offline. Check ON LINE indicator Put online if offline.
Cable disconnected. Check connections. Re-connect cable if not
connected or loose.
Incorrect terminal set-up. Check the terminal set-up
parameters. If a CRT, the
terminal should be set for
VT52 emulation, 8 data bits,
no parity, 1 stop bit. The
baud rate should match the
site controller's baud rate.
For Link terminal, follow
instructions in Start-Up
Manual. Configure the proper set-up
parameters according to the
terminal manufacturer's
instructions
Defective power supply. Measure the voltages
between the black (DC
ground) and red (+12VDC),
and black and white (-12VDC)
wires at connector P8 on the
site controller CPU board. Replace the power supply if
the proper voltages are not
measured at P9.
Incorrect baud rate switch
settings on the site controller
CPU board. Check that the baud rate
settings on DSW2 are correct If baud rate switches are
wrong, correct the settings
and press reset switch SW1
Short haul modem off, offline,
disconnected, or bad Check both modems at site
and terminal. If off, turn on; if offline, put
online; if disconnected,
reconnect; if bad, replace
Defective terminal. Try using a different site
controller communications
port. This requires changing
the communications cable.
Use a C04549 cable if the
terminal is in Port 0. Use a
C05039 cable if the terminal
is in Port 2. Make sure the
terminal's baud rate matches
the baud rate of the new
communications port. The
cable for Port 1 and 3 will
depend on the K1 and K2
jumper settings. If the terminal doesn't work in
either port, replace the
terminal. Site may not be
configured for terminal
communications at all ports.
(Continued)