User manual

18
FILE COMMANDS
FILE ID COMMAND - <ID#>
See the downloading file supplement for further details
PERMANENT FILE COMMAND - <PF> [not available on 22/24/26]
See the downloading file supplement for further details
TEMPORARY FILE COMMAND - <TF>
See the downloading file supplement for further details
DELETE FILE COMMAND - <DF#>
See the downloading file supplement for further details
PRINT COMMANDS
PRINT / CUT TICKET - <p>
This is the normal print command. The printer will cut the ticket after printing if it has a cutter.
PRINT / NO CUT TICKET - <q>
This is the normal print/no cut command. The printer will not cut the ticket after printing even if it has a cutter.
PRINT TICKET AND EJECT - <z>
This command is to be used in place of a normal print command (<p> or FF) on "escrow" type printers. When
this command is used, the printer will activate the second stepper to eject the ticket after the ticket is cut.
Please note that the printer will not eject any tickets regardless of the <z> command in the middle of a run of
multiple tickets. (Multiple tickets are defined as any ticket printed without a break between tickets - including
tickets being printed via a repeat command.) Do not use this command unless you want the tickets to be
ejected (your printer must contain an eject stepper motor).
PRINT / CUT (HOLD TICKET IMAGE) - <h>
This command is also used in place of a normal print command (<p> or FF). The purpose of this command is to
allow the user to update a number of fields on the ticket without re-transmitting all of the data. This feature is
particularly useful when logos, graphics or large blocks of data are retained from ticket to ticket. While this
feature can greatly reduce the amount of data sent from the computer to the printer, it should be noted that
updating large blocks of data may result in an overall decrease in printer throughput.
In normal operation, the printer automatically clears its ticket image buffer after the ticket is printed. When this
command is used, the printer will hold the print image in memory. The image will remain intact until either a
ticket is printed with a normal print command (<p> or FF) or a clear buffer command, <CB>, is issued. This
command also places the printer in replace mode. This means that all text sent for succeeding tickets will
replace the text located at that same position on the original 'held' ticket. In this manner, you can send a main
ticket and then update only select fields on the following tickets. All the tickets must end with an <h> command
if you want to continue in this mode. The printer will cut the ticket after printing if it has a cutter. The last ticket
before a new main ticket is to be printed should end with a normal print command.
Please note that the "<h>" feature is intended to be used for the replacement of similar fields of data. The use
of the "<h>" command to overwrite a field of large characters with small characters will cause pieces of the
original data to remain on the ticket making the new field difficult to read. Similarly, changing the font size or
font type will also create undesirable results. Another factor to consider is that, although new data is placed on
the ticket on a bit by bit basis, "<h>" mode data is loaded on a byte by byte basis. This means that the data is
replaced in multiples of 8 bits. For example, a font6 character is 52 dots high but the actual amount of replaced
data will be 56 dots (next multiple of 8). Therefore, in this case, any characters located 4 or less dots below the
replaced field will be erased. To avoid erasing adjacent data accidentally, you should avoid printing any
characters within 8 dots below the field that is to be replaced. The exact number varies with font size, height
and width so trial and error is the best approach if you are losing parts of characters when printing in the replace
mode.
(NOTE: This command is not supported when using soft fonts, and is not applicable to Magi and Dual printers.)