Click here to submit a question for possible inclusion in our roster of FAQ's.
The Character Generator V2.01 (p/n A15-90035) adds the Euro Symbol to both the ETX and LTx series printers.
All ITX printers have the Euro symbol.
The Euro Symbol is implemented in 12 of the 13 printer fonts (not in font 12).
It is located at character position 128(DEC), 80(HEX).
This Character Generator requires that the ETX/LTx printers have the latest firmware:
Practical Automation RMA Procedures
Click here to fill in an on-line form or email or fax the following information:
We will contact you with an RMA number.
Non-warranty repairs are subject to a $50 estimate charge, which is deducted from the cost of repair
If you have questions, call Practical Automation (203) 882-5640, Ext 127
Email: rma@practicalautomation.com
Fax: 203-882-5648
Margins at the top, bottom, and sides edges, of a printed ticket, where printing too close to these edges is ineffective the effective printable area is reduced by this amount.
A 2" x 5.5" Ticket printable area of approximately: 9.5 Sq-Inch.
A 3.25" x 4" Ticket printable area of approximately: 11.6 Sq-Inch
One printable dot requires one bit of data.
There are eight bits to a data byte.
At 203.2 DPI One Sq-Inch print area contains (203.2 x 203.2) = 41,290 Dots
At 300 DPI One Sq-Inch print area contains (300 x 300) = 90,000 Dots
At 203 DPI the 41,290 Printable Dots / 8 Bits per Data Byte = 5,161 Bytes per Sq-In of printable data.
At 300 DPI the 90,000 Printable Dots / 8 Bits per Data Byte = 11,250 Bytes per Sq-In of printable data.
The above can be used to estimate the size of data storage by taking the Sq-Inches of the printable images, to be stored, with the number of data bytes/square-inch. This assumes that the image data is saved "one to one' without compression.
When the data image is stored in PCX file the data is compressed. It is not directly predictable as to the amount of compression that will occur for a given image, however, the range of 2 to 5 is typical. An image requiring 50,000 bytes at "one to one" may only require 10,000 to 25,000 bytes if compressed.
The procedure for loading the Printer Driver, on Win 2K or Win XP, for a USB interface printer, is defined by the document: “USB Interface Driver Loading & Troubleshooting Guide V1.02” (ANUSB002-x.ZIP, where “x” = blank or 1-9 to distinguish multiple copies of the same file). This document is available, on the WEB, in printer’s Technical Notes section.
This document describes the direct plug-in USB Interface Module for the ITK38, ITK23/24 and ITX2000/3000 printers.
It is important to note that the older printers support USB with an add-on IEEE1284 Parallel to USB adapter cable (ATX38, GTX2000, GTX3004A) by converting the Printer’s Parallel Interface to USB. This is also detailed in this document.
All USB printers require a V2.xx Printer Driver.
It is not recommended to cut on the perforation.
The cutter needs to apply a shearing force to the paper as it cuts. If the blades cut directly on the perforation the perforation can cause the paper to fold and defeat the shearing action. This can lead to incomplete cuts and paper jams
The cut position must be adjusted to be just behind ~ 1/16" (~1.6 mm) the perforation.
When the document/ticket emerges from the printer, if it has been cut behind the perforation, the perforation will be seen on the trailing edge of the document with a very small paper segment attached by the perforation.
If the leading edge of the document emerges with a small paper segment and then perforation it means that cutting is being done before the perforation. Adjustment should be made to correct this to cut behind.
Refer to the printer's User Manual for instructions for adjusting the cut position sensor to insure cutting is behind the perforation.
Although some customers have experienced relatively good success when cutting directly on the perforation it is a practice that is not recommended for reliable long term operation.
REGISTRATION MARK LOCATION: ETX 2000, GTX 2000, ITX 2000, ITX 3000 PRINTERS
NOTE: The registration mark sensors on the ETX2000, GTX2000 and ITX2000/3000 ticket printers are located below and to the left side of the ticket when looking at the printer. The distance from the cut line to the cut position sensor is factory set to 6.7".
The following formula must be used to determine the location of the registration mark relative to the leading edge of the ticket. Refer to the drawing below for dimensions.
DCRM = 6.7" - (TL x m)
where:
DCRM = the distance from the cut line to the leading edge of the registration mark
TL = the ticket length in inches
6.7" = the physical distance from the cut line to the cut position sensor on the printer
m = 6.7" / TL (multiple of tickets within 6.7"; integer value)
Examples:
TL = 2.0"
m = 6.7" / 2.0 = 3
DCRM = 6.7" - (2.0" x 3) = 0.7"
TL = 5.5"
m = 6.7" / 5.5 = 1
DCRM = 6.7" - (5.5" x 1) = 1.2"
Common ticket lengths with resulting DCRM's
| 2.0" | 0.7" |
| 2.5" | 1.7" |
| 3.0" | 0.7" |
| 3.5" | 3.2" |
| 4.0" | 2.7" |
| 4.5" | 2.2" |
| 5.0" | 1.7" |
| 5.5" | 1.2" |
| 6.0" | 0.7" |
| 6.5" | 0.2" |
| 7.0" | 6.7" |
Note: For all tickets 6.7" and longer the DCRM is 6.7".

Note:
Note: This method is common to all Practical Automation Printers. (There are, however, a few differences, noted below).
on ETX Model Printers: The EEPROM function must be enabled. This requires DIP switch SW2 #8 to be set to the 1 / OFF position.
on LTx Model Printers: This printer does not have a beeper. The flash of the ATTN/ERROR LED will replace the beep.
REGISTRATION MARK LOCATION GTX3004A, ITX2003A & ITX3003A PRINTERS
NOTE: The registration mark sensors on the GTX3004A, ITX2003A and ITX3003A ticket printers are located below and to the right side of the ticket when looking at the printer. The distance from the cut line to the cut position sensor is factory set to 6.7".
The following formula must be used to determine the location of the registration mark relative to the leading edge of the ticket. Refer to the drawing below for dimensions.
DCRM = 6.7" - (TL x m)
where:
DCRM = the distance from the cut line to the leading edge of the registration mark
TL = the ticket length in inches
6.7" = the physical distance from the cut line to the cut position sensor on the printer
m = 6.7" / TL (multiple of tickets within 6.7"; integer value)
Examples:
TL = 2.0"
m = 6.7" / 2.0 = 3
DCRM = 6.7" - (2.0" x 3) = 0.7"
TL = 5.5"
m = 6.7" / 5.5 = 1
DCRM = 6.7" - (5.5" x 1) = 1.2"
Common ticket lengths with resulting DCRM's
| TL | DCRM |
| 2.0" | 0.7" |
| 2.5" | 1.7" |
| 3.0" | 0.7" |
| 3.5" | 3.2" |
| 4.0" | 2.7" |
| 4.5" | 2.2" |
| 5.0" | 1.7" |
| 5.5" | 1.2" |
| 6.0" | 0.7" |
| 6.5" | 0.2" |
| 7.0" | 6.7 |
Note: For all tickets 6.7" and longer the DCRM is 6.7".

Note:
REGISTRATION MARK LOCATION: ITL and LTx series TICKET PRINTERS
The registration mark sensor on the ITL and LTx series ticket printers is located below and to the right side of the ticket when looking at the printer. The printer uses the trailing edge of the registration mark to locate the ticket at the tear/cut line. It also uses the leading edge of the mark for fast printing, without cutting, sequences of tickets. The distance from the tear/cut line to the sensor is factory set to 2.20". Due to proximity of the sensor to the tear/cut line, all sizes of tickets must be printed with the trailing edge of the registration mark located 2.20" behind the leading edge of the ticket. Refer to the drawing below for dimensions.
Note:
Instructions for changing the Serial Data Selections (DIP-Switches)


Dip Switch Position:
0 = Closed / On
1 = Open / Off
Baud Rate Selections
(Switches: 1,2,3):
9600: 0,0,0
4800: 1,0,0
19.2K: 0,1,0
57.6K: 1,1,0
1200: 0,0,1
Future Use: 0,1,1; 1,0,1; 1,1,1
| Dip Sw. # | Switch Description |
| 1 | Baud |
| 2 | Baud |
| 3 | Baud |
| 4 | Data Length 0 = 8 Bits; 1 = 7 Bits |
| 5 | Parity Check 0 = Disabled; 1 = Enabled |
| 6 | Parity Type 0 = Even; 1 = Odd |
| 7 | Flow Control 0 = Busy; 1 = Xon/Xoff |
| 8 | (Future Use) 0 |
DIP Switch Factory Default Setting:
All switches are closed (0) for 9600 Baud, 8 Data Bits, No Parity, Busy Flow Control
For the ATX 23/24/38, ITK 23/24, ITX 2000/3000, GTX 2000/3004A Printers
For the ETX 2000, LTx2000, cLTx200 Printers
The above procedure cleans the printhead. To clean the drive roller:
Allow the printhead and roller to dry for several minutes before inserting tickets.
Find your printer series and order cleaning cards using the Practical Automation part number, shown below. Each cleaning card is packaged in a sealed package.
ITX 2002, ITX 3002, GTX 2002, ETX 2002, cLTx 2002, LTx 2002 (All Models)
One 2 inch (50.8 mm) wide card cleaning card.
Part Number: A15-70051-1
ITX 2003, ITX 3003, ITX 2003A, GTX 2003, ETX 2003, cLTx 2003, LTx 2003 (All Models)
One 3.25 inch (82.6 mm) wide cleaning card.
Part Number:A15-70051-2
ITX 2004A ITX 2004AS, ITX 3004A, ITX 3004AS, GTX 3004A
One 4 inch (101.6 mm) wide cleaning card.
Part Number:A15-70051-3
ITK38 and ATX 38 (All Models)
A package of ten 8 inch (203.2 mm) wide cleaning cards.
Part Number:A15-70071
ITK 23 and ATX 23 (All Models)
One 3.34 inch (84.8 mm) wide cleaning card.
Part Number:B15-70120-1
ITK 24 and ATX 24 (All Models)
One 4.48 inch (113.8 mm) wide cleaning card.
Part Number:B15-70120-2
Most RS232 Serial Interface problems are due to having the printer's serial setting selected incorrectly to that of the computer's or due to using the incorrect serial cable.
First, insure the printer's serial setting are matched to the computer's.
Next, purchase the cables suggested in the User's Manual for the printer.
In the Technical Notes area, for the printer, you will find an application note: ANIMGT00.ZIP
This contains two documents PDF documents to assist with the troubleshooting process of the serial interface. Download this application information and use it to resolve your serial interface problem.
FGL Firmware:
If the application software is using the FGL image generation resources of the ITX Printer by sending FGL commands directly to the ITX 2000/3000 Printer to accomplish its ticket printing task, then the printer should be loaded with the FGL firmware. If you have been using ETX or Boca FGL printers, you should use the FGL firmware.
G Firmware:
If the application software will be using the image generation resources, of the Windows Operating System environment to generate the image for the ticket and using our Windows Printer Driver to render this image and send its data to the ITX 2000/3000 Printer to accomplish its ticket-printing task, then the printer should be loaded with the G firmware.
If you have been using GTX printers, or another printer using a Windows Printer Driver, you should use the G firmware. Remember to install the latest Windows Printer Driver.
Can I change from one to the other?
Yes our WEB site has the latest G and FGL firmware. This can be downloaded and then uploaded into the printer to change between firmware types. This permits convenient use of the same printer for the two different operating modes.
General:
All Practical Automation printers, that use Registration Mark (Black Mark) paper/ticket stock can have a Registration error occur. The specific error code (beeps, flashes, status data, etc.) may vary for each printer model. The printer's User's Manual should be consulted.
A Registration Error indicates that the printer was unable to find or freely move the Registration Mark on the paper/ticket stock over the detection sensor while driving the paper advance motor.
What can cause a Registration Error to occur?
A fine white line(s) that runs in the direction of paper movement through the printer is usually caused by a dot failure of the printhead.
If a printhead dot fails to transfer its thermal energy to the paper a white line will appear where its printed dots were to have been located.
A printhead dot can fail for several reasons:
Dot cycle and Abrasive wear: (1; 2) are normal wear factors for any printhead. As the dots cycle on and off, to print the image, and as paper is forced under pressure to travel under the printhead’s active dot image line, over time, these factors will cause the loss of dot(s). The printheads are, however, very durable and this typically will not occur for many hundreds of thousands of printed documents.
Abrasive damage (3) can occur if the environment is unclean and dirt particles are picked up by the paper media and transferred under the printhead or if the thermal media has abrasive characteristics. Direct thermal printing puts the media in direct contact with the paper and it must be under force to maintain this intimate contact. If debris gets trapped on the paper’s surfaces and carried under the printhead it can scar the print surface and cause damage. Insuring that the paper input supply to the printer does not pick up dirt and debris will prevent this damage Thermal media must have a high quality, smooth finish. Media that has abrasive thermal side press printed inks, or other damaging abrasive characteristics must be avoided to insure long printhead life.
Impact damage (4) can occur if the printhead’s image line (glass surface) comes into contact with a sharp object. When removing the printhead care must be taken to insure that this image surface is not damaged.
Foreign Deposits (5) can be transferred to the surface of the printhead. As these deposits build they block the thermal energy from transferring to the media and printing. This build up also has a secondary damage influence factor. As the thermal energy is blocked from flowing between the printhead’s thermal resistors (dots) to the media thermal overstress will occur which will cause these dots to prematurely fail. Under normal thermal printing circumstances (plain white thermal media) the build up of deposits, due to the print process, will occur at a very slow rate requiring the printhead’s surface to be cleaned only after many thousands of printed documents. If, however, the media used has inks that are not thermally stable and they bleed off and bond to the printhead, this can cause damage to the printhead. Very frequent cleaning may be required, however, if this occurs, it is a red flag indicator that the media is the problem and it must be corrected! There is a small possibility that the print energy setting is set too high, for the media being imaged, however, this is somewhat rare. Frequent buildup of deposits should not occur under normal printing conditions. This condition must be prevented to achieve long printhead life.
ESD damage (6) can cause printhead dots to fail or in more severe cases cause the entire printhead to fail. When handling the printhead for cleaning or jam removal anti-static measures must be used to prevent this damage.
Only dot cycle and abrasive wear are covered under the printer's warranty.
The Practical Automation FGL Emulation ticket printers (ITX2000/3000) have built in commands with internal barcode encoding support, which forms barcodes from commands sent to these printers. The barcodes can be made in any size and rotation. It should be noted that barcodes may not be readable when constructed with a minimum feature size that is too small. Most barcode specifications require a minimum of 0.0075" for the minimum feature size (the smallest line or space element). For a 203 DPI printer this requires a minimum of two dots and for a 300 DPI printer a minimum of three dots.
The Practical Automation raster paper printers (ATX23/24/38 ; ITK23/24/38) and raster ticket printers (ITX2000G/ITX300G) can also print barcodes, however, the barcode's information must be created, in the Windows GDI (Graphics Data Interface), and then passed through the Windows printer driver, to the printer, for that barcode to be printed as graphical information. The encoding of the barcode is done by an application program (interfacing with the Windows GDI). There are many programs on the market that will do this function quite well. It should, however, must be noted that there are subtle challenges that must be understood that can cause the printed barcode to be inaccurately formed. For example, many Windows barcode programs use True Type font elements to create the space and bar pattern elements of the barcodes. With this mechanism characters are translated (in this case, barcode character elements) from the graphical resolution of the Windows GDI (Pixels per Inch) to the printer's resolution (Dots per Inch) using True Type font character mathematical techniques. This process works exceedingly well for smoothly formed printable characters but has been found to have limitations when creating some barcode elements. It works well in most cases, however, when the target barcode size, that will be printed on the printer, starts to approach the minimum element size for the barcode, mathematical round off errors can cause barcode inaccuracies when forming the line and space patterns. This can usually be corrected by making the printed barcode larger, as the round off errors will no longer matter, or, if the barcode program can use bit mapped fonts, instead of True Type fonts, so that the target barcode elements can be mapped "one-to-one" to the printer's graphical resolution, then this mathematical round off error problem will not exist.
Can barcodes be printed on Practical Automation FGL Emulation or Raster printers? YES!
For the FGL printers the minimum feature size must be considered when establishing the minimum size for the barcode.
For the raster printers, where the barcodes approach the minimum feature size of the barcode, the application engineer must be aware of an additional error source that can come from round off errors related to barcode generation program.
The RL (Reverse Landscape) printer drivers, for the ITX 2000/3000 printers, permit the Landscape orientation of the driver's output to match that of the older drivers used with the ETX and LTx printers (the XTX printer drivers). This RL Landscape is opposite the normal Windows convention for this orientation. When using an ITX printer to replace a GTX printer using, or using an ITX printer, in a new application, the non-RL suffix printer driver is the correct choice.
The PDF document (ITX 2000G_3000G RL Printer Driver Application Note.pdf) is supplied with the "RL" printer driver. Please refer to this PDF document as it provides a graphical portrayal of this concept.
It should also be noted that the Portrait mode orientation, which is characterized by the top edge of the printed document emerging first in the print direction, does not change for the "RL". The "RL" and the non-RL drivers have the same portrait mode orientation. If the programmer needed to rotate the portrait mode he would need to use the Windows APIs to rotate his printed image.
Two of the most common errors when trying to print a PCX file using the FGL command set are:
The FGL command string, to print a PCX file, contains four basic parts:
If a PCX file contained 1000 bytes, and it were to be printed at Row 100 and Column 100, its pcx command string would be:
<RC100,100><pcx><G1000>...
where: ... is the PCX file’s content (its data), not its file name. Also, note that the byte count of 1000 needs to be the exact length of the PCX’s file size. The Windows Explorer only provides a rounded off file size. Looking at the file size using Properties or at the Command prompt may be required to insure that the correct file size is used.
Introduction:
The setting of paper size can be confusing. There are two related printer paper settings that give rise to the confusion. The following definitions will aid in understanding.
Definitions:
Paper Size - Specifies that paper size selected. The size selected will be used by an application when printing. The printer Device Context, created by an application for printing, will reflect the paper size selected.
Form To Tray Assignment: Some printers have paper trays that contain different sizes of paper. Matching a form to a source ensures that documents always print on the correct paper size when the form is selected from within a program. Practical Automation printers do not support this feature. Altering the Form To Tray assignment value will not have any effect on printing. As stated above, the printer Device Context, created by an application for printing, will reflect the paper size selected, NOT the Form To Tray assignment.
Paper size setting procedure:
Method for Setting Paper Size, Practical Automation Printers
Click OK and then APPLY to complete the process.
The Incorrect path of Properties and Device Settings WILL NOT set the paper size. Notice the labels Form To Tray Assignment and Not Used: . As noted above, this selection is used to select available paper trays, but does not apply to Practical Automation printers.
Also, some Practical Automation Printer Drivers may display "Default" instead of "Not Used".
5 Beeps
L-S-S-S-S = 1 = MPU/System Error
S-L-S-S-S = 2 = RAM Fault Error
L-L-S-S-S = 3 = EEPROM Checksum Error
S-S-L-S-S = 4 = FLASH Memory Error
L-S-L-S-S = 5 = Character Generator Memory Error
S-L-L-S-S = 6 = IMAGE Memory Error
L-L-L-S-S = 7 = Analog to Digital Converter Error
S-S-S-L-S = 8 = FPGA/ASIC Error
L-S-S-L-S = 9 = Voltage Error
S-L-S-L-S = 10 = Printhead Thermistor Error
L-L-S-L-S = 11 = Printhead Print Resistor Error
S-S-L-L-S = 12 = Printhead Data Error
L-S-L-L-S = 13 = Cutter Initialization Error
S-L-L-L-S = 14 = Configuration Strap Error
L-L-L-L-S = 15 = Miscellaneous Error
4 Beeps
L-S-S-S = 1 = Paper Path Jam / Error
S-L-S-S = 2 = Cutter Operational Error
L-L-S-S = 3 = Transport Presenter Error
S-S-L-S = 4 = Paper Output Error
L-S-L-S = 5 = Registration Mark Detection Error
S-L-L-S = 6 = Printhead Pressure Release Lever Error
L-L-L-S = 7 = Out of Paper Error
S-S-S-L = 8 = Interface Data Error
3 Blinks (no beeps)
L-S-S = 1 = Ticket Not Taken Condition
S-L-S = 2 = Ticket Not Presented
L-L-S = 3 = Printhead Too Hot/Cold
S-S-L = 4 = Power Supply Wait
L-S-L = 5 = Data Communication Warning