SATO CW408, Руководство оператора, Страница: 90 / 120

Section 5: Troubleshooting
Page 5-10 CW408 Operator Manual
5.3 INTERFACE TROUBLESHOOTING
This section 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.
5.4 TEST PRINT TROUBLESHOOTING
This section provides instruction on special printing to identify and resolve specific print problems.
5.4.1 Hex Dump
Allows the operator to determine if there were problems in the downloading of data. The contents of the print
buffer can be examined using the Hex dump mode. In the left column, each line of data received is numbered.
The center column provides the data in hexadecimal format. And in the right column, the same data is
provided in the ASCll format. Refer to
Section 3.12 HEX Dump Mode for more details to perform this activity.
5.4.2 Test Print
Allows the operator to identify specific problems regarding mechanical performance and setup. The test print
is designed to assist in the identification of print problems. Refer to
Section 3.14 Test Print Mode for more
details to perform this activity.
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 TROUBLESHOOTING STEP
Click on Start, Settings, and then Control Panel.
Click on System within the new window.
Click on the Device Manager tab.
Make sure that the View Device By Type is checked.
Scroll to SATO-USB Device and make sure that errors do not exist. Reinstall as required.
Reboot the PC and the printer.
LAN ETHERNET INTERFACE
CHK TROUBLESHOOTING STEP
Make sure that the interface has been correctly configured. Wait two minutes and run self-test to verify. If a test
print does not print, there may be a hardware problem.
Make sure that the cable and its ports are not defective.
Make sure 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, make sure 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, make sure that the SQE is set to off. Also make sure that 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 possible, 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.
Preliminary