SATO CL608e/CL612e manual IEEE1284 Parallel Interface

Section 8. Troubleshooting

The IEEE1284 Parallel Interface (Cont)

c.Verify the following:

•You have not typed a "0" (zero) for an "o" (letter) or vice-versa.

•You have not missed any <ESC> characters where they're needed.

•Make sure all printer command codes are capital letters.

•Your protocol codes are set for Standard or Non-Standard and data stream is consistent with these.

7.If you've checked all the above and the printer still isn't printing, you may want to try a Receive Buffer Hex Dump to determine what (if anything) the printer is receiving from your computer. See Hex Dump Mode in Section 8-10.

The Parallel port is now listening for incoming data. Send your print job. The printer will now print (only once) a Hexadecimal (Hex) Dump of everything it received from the host computer. Each 2-digit hexadecimal character represents a character the printer received. It may be tedious, but now you can analyze and troubleshoot the data stream.

WARNING: A small label may produce a large amount of data when printed in Hex Dump.

8.While checking the Hex Dump printout, look for 0DH 0AH (Carriage Return and Line Feed) characters throughout. The command string should be continuous. CR or LF characters are not allowed between the Start Command (<ESC>A) and the Stop Command (<ESC>Z). If you are using BASIC, it may be adding these characters automatically as the line wraps. Adding a "width" statement to your program can

help to suppress these extra 0DH 0AH characters by expanding the line length up to 255 characters.

If you're not programming in BASIC, check to see if you have an equivalent statement in the language you're using to suppress extra carriage returns and line feeds from your data being sent out to the printer. We want the data stream to be one complete line going to the printer.

PN 9001079	SATO CL608e/CL612e Service Manual	Page 8-3
Rev. B