KCS - How To Test Printer Command Code
KCS - How To Test Printer Command Code
How to test printer command code
Information
Article Number 000036883
Image Indicator
Question/Problem
How may I test printer code I've written or generated?
How may I manually send commands or print jobs to my printer?
Resolution
PREPARE THE PRINTER FOR TESTING
If testing a customwritten print job, make sure the testing printer is using the same firmware version as the
production printer. When testing a brandnew process, consider using the mostrecent firmware version which the
production printer can handle. the next step is to Factory Default the testing printer. This way, it printer will be as
close to 'Out of the Box' as possible. Third, select the correct Command Language. This may include IPL,
Fingerprint or ZSim. Finally, make any necessary changes to match the production setup: such as loading the
same type and size media.
There are two ways to send Command Code or Print Jobs to a Intermec printer. The first is using a TELNET or
Serial (COM) session and the second is using the Tools of the InterDriver 'Printer Properties' window. Each of
these methods will be covered, below.
SENDING COMMAND CODE TO THE PRINTER
Using a Terminal Program and a TELNET or Serial session...
For both TELNET and COM sessions, either 'puTTY' or 'HyperTerminal' will generally work. Click here to
download a .ZIP archive which contains both tools. Either tool may be used immediately after being extracted: no
install is necessary before use.
The process for using each tool is slightly different.
NOTE: While any terminal program may be used to send command code to the printer, Honeywell does not
provide direct support for terminal programs not running on Intermec or Honeywell devices.
Using 'HyperTerminal'
To Use 'HyperTerminal' to send the file(s)...
1. Start the HyperTerminal program and name the connection. HyperTerminal requires that each
connection be named, but won't actually let a user save this connection for later use in Win7 and
later, so the name choose doesn't matter.
2. After naming the connection, click on the 'OK' button
3. For Serial connections, on the next window, select to 'Connect using' "COM1" and then...
1. On the COM1 Properties window, match the HyperTerminal settings to the printer's
Serial Port settings
2. Click on the 'OK' button to connect
HyperTerminal will present an empty TELNET session window: not all commands will
result in a response, within this window, from the printer.
4. For network connections, on the next window, select to 'Connect using' "TCP/IP (Winsock)"
and then...
1. On the next window, select to 'Connect using' "TCP/IP (Winsock)"
2. Next, enter the printer's IP for the 'Host address' and the active network port probably
"9100" for the 'Port number'
3. Click on the 'OK' button to connect
HyperTerminal will present an empty TELNET session window: not all commands will
result in a response, within this window, from the printer.
5. Now that there is an open connection, a file may be sent: select "Transfer > Send Text file..."
6. If sending a file which doesn't have a ".TXT" extension, look in the lowerright corner of the
'Send Text File' window and click where the dropdown shows "Test file (*.TXT)" and select "All
files (*.*)" instead
7. Browse to the location of the file to be sent
8. Doubleclick on the desired file and it will be sent to the printer
9. Quit out of HyperTerminal, without saving the session
https://na7.salesforce.com/articles/HSM_Article/Howtotestprintercommandcode/p 1/5
9/14/2015 Knowledge Article
Using 'puTTY'
To Use 'puTTY' to send the file(s)...
1. Start the puTTY program
2. For Serial connections, on the PuTTY Configuration window, select 'Connection type' of
"Serial" and then...
1. In the left panel of the puTTY Configuration window, click on the 'Serial' Category:
clear at the bottom
2. Match the puTTY Serial Lines settings to the printer's Serial Port settings
3. In the left panel of the puTTY Configuration window, click on the 'Session' Category:
clear at the top
4. puTTY is able to save this session for later use. Enter a name just under "Saved
Sessions" and click on the 'Save' button
5. Click on the 'Open' button at the bottom of the window to start the session.
puTTY will present an empty TELNET session window: not all commands will result in
a response, within this window, from the printer.
3. For network connections, on the PuTTY Configuration window, select a 'Connection type' of
"Telnet" and then...
1. Enter the printer's IP for the 'Host Name (or IP address)' and the active network port
probably "9100" for the 'Port'
2. puTTY is able to save this session for later use. Enter a name just under "Saved
Sessions" and click on the 'Save' button
3. Click on the 'Open' button at the bottom of the window to start the session.
puTTY will present an empty TELNET session window: not all commands will result in
a response, within this window, from the printer.
4. Rightclick on the file to be sent and select to 'Open it With...' a basic text editor, such as
Notepad
5. In Notepad, select "Edit > Select All" and then "Edit > Copy"
6. Switch back to the puTTY window and rightclick inside it. This will Paste the code into the
TELNET session
7. Hit the [Enter] key once, if the printer doesn't start to print and also doesn't respond within the
TELNET session at all
8. Quit out of puTTY
puTTY can also send a full log of a TELNET or Serial session to the clipboard: so that it may be saved for
reference. To do this...
To Send the File Using the InterDriver 'Printer Properties' Tools...
1. Open either the 'Devices & Printers' (Windows 7 and later) or the 'Printers & Faxes' (Windows XP)
Control Panel
2. Rightclick on the printer and select Printer Properties. For Windows 7 and later, this should be fourth
from the top.
3. Select "Tools tab > Action > Sent File to Printer"
4. Browse to the location of the file to be sent
5. Doubleclick on the desired file and it will be sent to the printer.
The file should now be sent to the printer.
Product Category Printing
Add Applies to Must be in draft to edit Applies To
Edit Applies To Testing Printer Code: Best Practices
Applies To
Printer Command Languages (i.e. IPL, Fingerprint, Direct Protocol)
Related Links https://na7.salesforce.com/sfc/p/00000000SK3U/a/A00000000CB9/qA8OHo44jWzFGas9iJSVrHnm6K6JXAyAjX_kA4o8Nac
https://c.na7.content.force.com/servlet/rtaImage?
eid=ka0A0000000H1dq&feoid=00NA000000Aibqm&refid=0EMA00000004o2J
https://na7.salesforce.com/articles/HSM_Article/Howtotestprintercommandcode/p 2/5