Interface Troubleshooting - SATO CG2 Series Operator's Manual

Section 4: Troubleshooting

4.3 INTERFACE TROUBLESHOOTING

This chapter provides a checklist for the various interface types. Locate the checklist relative to the interface
used and perform each of the troubleshooting tasks until the problem has been isolated.
UNIVERSAL SERIAL BUS (USB) INTERFACE
If nothing prints during a test print, verify the device drivers have been successively installed by performing the following:
CHK
Click on Start, Settings, and then Control Panel.
Click on System within the new window.
Click on the Device Manager tab.
Ensure that the View Device By Type is checked.
Scroll to SATO-USB Device and ensure that errors do not exist. Reinstall as required.
Reboot the PC and the printer.
RS232 SERIAL INTERFACE
CHK
Ensure the correct interface module is correctly installed. Run self-test to verify.
Ensure the serial cable (Null Modem) meets specifications and is correctly connected at each end.
Ensure the serial cable is not defective.
Ensure the communication parameters for the baud rate, parity, data bits and stop bits are consistent with those
being sent from the host computer.
Ensure the printer is receiving information from the computer using the Receive Buffer Hex Dump mode. Refer to
that procedure within this manual for instructions. The command stream should be continuous and possess
0Dhex and/or 0Ahex (carriage return and line feed) characters throughout. However, there should not be either
located between the start (<ESC>A) and the stop (<ESC>Z) commands.
Try another port to isolate the problem.
Replace the main circuit board if determined to be the problem.
LAN ETHERNET INTERFACE
CHK
Ensure the interface has been correctly configured. Wait two minutes and run self-test to verify. If a test label
does not print, there may be a hardware problem.
Ensure the cable and its ports are not defective.
Ensure that a faulty print server or other protocol related scenarios are not creating a queue setup issue.
Systematically perform checks and tests to isolate the cause.
If using TCP/IP, ensure that a valid IP address is specified and that all parameters are correct (subnet mask,
gateway, etc.). Attempt to PING the IP address assigned to the network interface.
If using a repeater or hub, ensure the SQE is turned off. Also ensure the repeater port is not defective by trying
the print server on another port.
Install the IPX/SPX protocol on a workstation to determine if the network device can be discovered via the MAC
address. If able, configure the appropriate protocols and retest connectivity.
Use a crossover cable to isolate the printer from the network by connecting from the interface and workstation.
Verify that the parameters match on each. Test connectivity.
Page 4-6
TROUBLESHOOTING STEP
TROUBLESHOOTING STEP
TROUBLESHOOTING STEP
CG2 Series Operator Manual