Professional Documents
Culture Documents
Manual Protocoale - PRELIMINARY
Manual Protocoale - PRELIMINARY
COMMAND MANUAL
COMMUNICATION
PROTOCOLS
© 2018 All rights reserved. Total or partial repro- GENERAL SAFETY INFORMATION THE CE MARK AFFIXED TO THE
duction of this manual in whatever form, whether Your attention is drawn to the following actions PRODUCT CERTIFY THAT THE
by printed or electronic means, is forbidden. While PRODUCT SATISFIES THE BA-
that could compromise the characteristics of the
guaranteeing that the information contained in it SIC SAFETY REQUIREMENTS.
product:
has been carefully checked, the manufacturer
and other entities utilized in the realization of • Read and retain the instructions which follow. The device is in conformity with the essential
this manual bear no responsibility for how the • Follow all indications and instructions given Electromagnetic Compatibility and Electric Safety
manual is used. on the device. requirements laid down in Directives 2014/30/EU
Information regarding any errors found in it or • Make sure that the surface on which the device and 2014/35/EU inasmuch as it was designed in
suggestions on how it could be improved are ap- rests is stable. If it is not, the device could fall, conformity with the provisions laid down in the
preciated. Since products are subject to continu- following Standards:
seriously damaging it.
ous check and improvement, the manufacturer • EN 55032 (Limits and methods of measure-
• Make sure that the device rests on a hard (non-
reserves the right to make changes in information ments of radio disturbance characteristics of
contained in this manual without prior notification. padded) surface and that there is sufficient
Information Technology Equipment)
ventilation.
• EN 55024 (Information Technology Equip-
• Do not fix indissolubly the device or its accesso-
ment – Immunity characteristics – Limits and
ries such as power supplies unless specifically
The pre-installed multimedia contents are pro- methods of measurement)
provided in this manual.
tected from Copyright of manufacturer. Other • EN 60950-1 (Safety of information equipment
• When positioning the device, make sure cables
company and product names mentioned herein including electrical business equipment)
may be trademarks of their respective companies. do not get damaged.
Mention of third-party products is for informational • [Only OEM equipment] The equipment must The device is in conformity with the essential
purposes only and constitutes neither an endorse- be installed in a kiosk or system that provides requirements laid down in Directives 2014/53/EU
ment nor a recommendation. The manufacturer mechanical, electrical and fire protection. about devices equipped with intentional radiators
assumes no responsibility with regard to the • The mains power supply must comply with the The Declaration of Conformity and other available
performance or use of these products.
rules in force in the Country where you intend certifications can be request to by the manufac-
to install the equipment. turer please providing the correct part number
• Make sure that there is an easily-accessible shown on product label or in the invoice.
outlet with a capacity of no less than 10A closely
THE IMAGES USED IN THIS MAN- to where the device is to be installed.
UAL ARE USED AS AN ILLUSTRA- • Make sure the power cable provided with the
TIVE EXAMPLES. THEY COULDN’T appliance, or that you intend to use is suitable
with the wall socket available in the system.
REPRODUCE THE DESCRIBED
• Make sure the electrical system that supplies
MODEL FAITHFULLY. power to the device is equipped with a ground
wire and is protected by a differential switch.
UNLESS OTHERWISE SPECIFIED, • Before any type of work is done on the machine,
disconnect the power supply. GUIDELINES FOR
THE INFORMATION GIVEN IN THIS THE DISPOSAL OF
• Use the type of electrical power supply indi-
MANUAL THE PRODUCT
cated on the device label.
ARE REFERRED TO ALL MODELS • These devices are intended to be powered
IN PRODUCTION AT THE ISSUE by a separately certified power module hav-
The crossed-out rubbish bin logo means that
DATE OF THIS DOCUMENT. ing an SELV, non-energy hazardous output.
used electrical and electronic products shall NOT
(IEC60950-1 second edition). be mixed with unsorted municipal waste. For
• [Only POS equipment] The energy to the more detailed information about recycling of this
equipment must be provided by power supply product, refer to the instructions of your country
approved by the manufacturer. for the disposal of these products.
GENERAL INSTRUCTIONS • Take care the operating temperature range of • Do not dispose of this equipment as miscel-
The manufacturer declines all responsibility for equipment and its ancillary components. laneous solid municipal waste, but arrange to
accidents or damage to persons or property • Do not block the ventilation openings. have it collected separately.
occurring as a result of tampering, structural or
• Do not insert objects inside the device as this • The re-use or correct recycling of the electronic
functional modifications, unsuitable or incorrect
could cause short-circuiting or damage compo- and electrical equipment (EEE) is important
installations, environments not in keeping with
the equipment’s protection degree or with the nents that could jeopardize printer functioning. in order to protect the environment and the
required temperature and humidity conditions, • Do not carry out repairs on the device yourself, wellbeing of humans.
failure to carry out maintenance and periodical except for the normal maintenance operations • In accordance with European Directive WEEE
inspections and poor repair work. given in the user manual. 2002/96/EC, special collection points are
available to which to deliver waste electrical
• The equipment must be accessible on these
and electronic equipment and the equipment
components only to trained, authorized per-
can also be handed over to a distributor at the
sonnel.
moment of purchasing a new equivalent type.
• Periodically perform scheduled maintenance on
• The public administration and producers of
the device to avoid dirt build-up that could com-
electrical and electronic equipment are involved
promise the correct, safe operation of the unit. in facilitating the processes of the re-use and
• Do not touch the head heating line with bare recovery of waste electrical and electronic
hands or metal objects. Do not perform any equipment through the organisation of col-
operation inside the printer immediately after lection activities and the use of appropriate
printing because the head and motor tend to planning arrangements.
become very hot. • Unauthorised disposal of waste electrical and
• Use consumables approved by the manufac- electronic equipment is punishable by law with
turer.. the appropriate penalties.
The format used for this manual improves use of natural resources reducing the quantity of necessary paper to print this copy.
CUSTOM PROTOCOL
XON/XOFF PROTOCOL
CUSTOM PROTOCOL
CUSTOM Protocol │ 5
TABLE OF CONTENTS
INTRODUCTION
Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
6 │ CUSTOM Protocol
1020 Detection of the device type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
2005 Fiscalization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
CUSTOM Protocol │ 7
2201 Counter of class 2 increasing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
8 │ CUSTOM Protocol
3111 Closing fiscal document. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
6801 Read number of rows set to be printed for business name . . . . . . . . . . . . . . . . . . . . . . 106
CUSTOM Protocol │ 9
MISCELLANEOUS COMMANDS
7001 Paper feed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
8002 Electronic journal print out by date and receipt number . . . . . . . . . . . . . . . . . . . . . . . . 120
8003 Electronic journal print out by closing number to closing number . . . . . . . . . . . . . . . . . 121
BITMAP MANAGEMENT
9100 Start transmission BMP image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
10 │ CUSTOM Protocol
INTRODUCTION
Functionality
Communications between PC and the printer are performed via RS232, USB or ETHERNET channel.
NOTE:
The RTS signal must be high.
With the new generation products the baud rate is up to 57600 bps.
<STX><CNT><IDENT><COMMANDS><CKS><EXT>
where:
STX Frame beginning 1 byte 0x02
If the syntax is complete and not corrupted, the answer is: <ACK>
After receiving the answer, the printer start the command processing.
If the command processing is correct, the answer is: <COMMAND ECHO><COMMAND DATA>
If the execution of the command goes wrong (e.g. paper end, cover open ...), the printer transmits:
<COMMAND ECHO>ERRxx
where xx represent a number from 0 to 99 that assign a status.
CUSTOM Protocol │ 11
NOTES:
ACK acknowledge 1 byte 0x06
NACK not acknowledge 1 byte 0x15
Frame counter increases for every sent string (even if the previous has not gone well); at the contrary it doesn’t increase
if the same string is resent (retry).
The answer ACK (acknowledge) for each frame is done only if the reception is correct.
The parameter CKS (checksum) is the module 100 addition of the parameters: CNT+IDENT+MESSAGE.
The parameter IDENT is fix to “0” (ASCII character).
NOTE: If the fiscal product shouldn’t support a command described in this manual, please verify the firmware version
installed on the fiscal product.
12 │ CUSTOM Protocol
DATA REQUEST COMMANDS
1001 Date/time
Sent command:
CONTENT LENGTH NOTES
1 1 byte HEADER1: indicates the commands group
001 3 bytes HEADER2: indicates the function
Response:
CONTENT LENGTH NOTES
1 1 byte
The four bytes at the beginning indicate the command sent.
001 3 bytes
GG 2 bytes DD = Day [from 01 to 31]
MM 2 bytes MM = Month [from 01 to 12]
AA 2 bytes YY = Year [from 00 to 99]
HH 2 bytes HH = Hour [from 00 to 24]
Mm 2 bytes mm = Minutes [from 00 to 59]
CUSTOM Protocol │ 13
1002 Heading lines
Sent command:
CONTENT LENGTH NOTES
1 1 byte HEADER1: indicates the commands group
002 3 bytes HEADER2: indicates the function
N.LINE 1 byte N.LINE: heading line number [from 1 to 6]
Response:
CONTENT LENGTH NOTES
1 1 byte
The four bytes at the beginning indicate the command sent.
002 3 bytes
N.LINE 1 byte N. LINE = heading line number [from 1 to 6]
PITCH [from 1 to 6] =
1 (normal)
2 (bold)
PITCH 1 byte 3 (42 character)
4 (double height)
5 (double width)
6 (italic)
LEN 2 bytes Line length [from 00 to 32]
LINE 0-32 bytes Text in the line [alphanumeric]
14 │ CUSTOM Protocol
1003 Receipt totals
Sent command:
CONTENT LENGTH NOTES
1 1 byte HEADER1: indicates the commands group
003 3 bytes HEADER2: indicates the function
Response:
CONTENT LENGTH NOTES
1 1 byte
The four bytes at the beginning indicate the command sent.
003 3 bytes
TPMA 9 bytes TPMA = partial extra charge total [from 0 to 999999999]
TPS 9 bytes TPS = partial discount total [from 0 to 999999999]
TPRET 9 bytes TPRET = partial rectification total
TPRE 9 bytes TPRE = partial returns total [from 0 to 999999999]
SEGNOS 1 byte SEGNOS = subtotal mark [+,-]
SUBT 9 bytes SUBT = subtotal [from 0 to 999999999]
SEGNOR 1 byte SEGNOR = remainder mark (if “-” is Change) [+,-]
RIM 9 bytes RIM = remainder to pay or change [from 0 to 999999999]
N° FRAMES 4 bytes N°FRAMES = n° frames sent fiscal receipt [from 0 to 9999]
SCONTR 1 byte SCONTR = fiscal receipt in progress [from 0/1]
CUSTOM Protocol │ 15
1004 Daily total
Sent command:
CONTENT LENGTH NOTES
1 1 byte HEADER1: indicates the commands group
004 3 bytes HEADER2: indicates the function
Response:
CONTENT LENGTH NOTES
1 1 byte
The four bytes at the beginning indicate the command sent.
004 3 bytes
NSF 4 bytes NSF = n° fiscal receipts [from 0 to 9999]
TSF 9 bytes TSF = fiscal receipts total [from 0 to 999999999]
NFA 4 bytes NFA = N/A [from 0 to 9999]
TFA 9 bytes TFA = N/A [from 0 to 999999999]
NRIC 4 bytes NRIC = N/A [from 0 to 9999]
TRIC 9 bytes TRIC = N/A [from 0 to 999999999]
NSLM 4 bytes NSLM = fiscal memory reader receipts n° [from 0 to 9999]
TMA 9 bytes TMA = extra charge total [from 0 to 999999999]
TSC 9 bytes TSC = discount total [from 0 to 999999999]
TRET 9 bytes TRET = rectification total [from 0 to 999999999]
TRE 9 bytes TRE = returns total [from 0 to 999999999]
TCNP 9 bytes TCNP = corresponding not paid total [from 0 to 999999999]
16 │ CUSTOM Protocol
1005 Daily closing data by order number
Sent command:
CONTENT LENGTH NOTES
1 1 byte HEADER1: indicates the commands group
005 3 bytes HEADER2: indicates the function
N° ORD 4 bytes Number of fiscal closing
Response:
CONTENT LENGTH NOTES
1 1 byte
The four bytes at the beginning indicate the command sent.
005 3 bytes
N° ORD = n° of fiscal closing [from 1 to 9999]
N° ORD 4 bytes
If the requested n° of fiscal closing is not valid, the device answers with error.
T.GIO 9 bytes T.GIO = Daily total [from 0 to 999999999]
N. TE 4 bytes N. TE = N/A [from 0 to 9999]
T.E. 9 bytes T.E. = N/A [from 0 to 999999999]
DD 2 bytes DD = Day [from 01 to 31]
MM 2 bytes MM = Month [from 01 to 12]
YY 2 bytes YY = Year [from 00 to 99]
CUSTOM Protocol │ 17
1006 Daily closing data by date
Sent command:
CONTENT LENGTH NOTES
1 1 byte HEADER1: indicates the commands group
006 3 bytes HEADER2: indicates the function
DD 2 bytes DD = Day [from 01 to 31]
MM 2 bytes MM = Month [from 01 to 12]
YY 2 bytes YY = Year [from 00 to 99]
Response:
CONTENT LENGTH NOTES
1 1 byte
The four bytes at the beginning indicate the command sent.
006 3 bytes
N° ORD = n° order [from 1 to 9999]
N° ORD 4 bytes
If the requested order is not valid, the device answers with error.
T.GIO 9 bytes T.GIO = Daily total [from 0 to 999999999]
N. TE 4 bytes N. TE = N/A [from 0 to 9999]
T.E. 9 bytes T.E. = N/A [from 0 to 999999999]
DD 2 bytes DD = Day [from 01 to 31]
MM 2 bytes MM = Month [from 01 to 12]
YY 2 bytes YY = Year [from 00 to 99]
NOTE:
If the requested data is not valid, the device answers with error.
18 │ CUSTOM Protocol
1007 Fiscal reset data
Sent command:
CONTENT LENGTH NOTES
1 1 byte HEADER1: indicates the commands group
007 3 bytes HEADER2: indicates the function
N° ORD 4 bytes Number of HW/INIT
Response:
CONTENT LENGTH NOTES
1 1 byte
The four bytes at the beginning indicate the command sent.
007 3 bytes
DD 2 bytes DD = Day [from 01 to 31]
MM 2 bytes MM = Month [from 01 to 12]
YY 2 bytes YY = Year [from 00 to 99]
HH 2 bytes HH = hour [from 00 to 24]
mm 2 bytes mm = Minutes [from 00 to 59]
N. RIP 4 bytes N. RIP = n° of HW/INIT [from 0 to 9999]
CUSTOM Protocol │ 19
1008 Fiscal register number
Sent command:
CONTENT LENGTH NOTES
1 1 byte HEADER1: indicates the commands group
008 3 bytes HEADER2: indicates the function
Response:
CONTENT LENGTH NOTES
1 1 byte
The four bytes at the beginning indicate the command sent.
008 3 bytes
ID 2 bytes ID = constructor’s approval and code number [alphanumeric]
N. MATR = Number of register [from 00000000 to 99999999]
N. MATR. 8 bytes
If the register is not registered, the device answers with error.
20 │ CUSTOM Protocol
1009 Printer status
Sent command:
CONTENT LENGTH NOTES
1 1 byte HEADER1: indicates the commands group
009 3 bytes HEADER2: indicates the function
Response:
CONTENT LENGTH NOTES
1 1 byte
The four bytes at the beginning indicate the command sent.
009 3 bytes
COD_ERRSTAM = error code
00 = Cover closed - Paper present
COD_
2 bytes 10 = Cover open - Paper present
ERRSTAM
01 = Cover closed - Paper not present
11 = Cover open - Paper not present
CUSTOM Protocol │ 21
1010 Printer status
Sent command:
CONTENT LENGTH NOTES
1 1 byte HEADER1: indicates the commands group
010 3 bytes HEADER2: indicates the function
Response:
CONTENT LENGTH NOTES
1 1 byte
The four bytes at the beginning indicate the command sent.
010 3 bytes
S1 1 byte S1 = no_mf [0/1]
S2 1 byte S2 = err_prog_mf [0/1]
S3 1 byte S3 = date_to_set [0/1]
S4 1 byte S4 = mf_ko [0/1]
S5 1 byte S5 = HW/INIT (1: HW/INIT to do) [0/1]
S6 1 byte S6 = HW/INIT jumper (1: HW/INIT jumper inserted) [0/1]
S7 1 byte S7 = register (1: programmed register) [0/1]
S8 1 byte S8 = fiscal closing (1 closing executed) [0/1]
S9 1 byte S9 = print in progress [0/1]
S10 1 byte S10 = printer error [0/1]
S11 1 byte S11 = learn in progress [0/1]
NOTE:
If the flag “S3” is 1 has been executed a HW/INIT. Should be necessary set the date.
22 │ CUSTOM Protocol
1011 Receipts status
Sent command:
CONTENT LENGTH NOTES
1 1 byte HEADER1: indicates the commands group
011 3 bytes HEADER2: indicates the function
Response:
CONTENT LENGTH NOTES
1 1 byte
The four bytes at the beginning indicate the command sent.
011 3 bytes
S1 1 byte Fiscal receipt in progress [0/1]
S2 1 byte Non fiscal receipt in progress [0/1]
CUSTOM Protocol │ 23
1012 Fiscal receipt step
Sent command:
CONTENT LENGTH NOTES
1 1 byte HEADER1: indicates the commands group
012 3 bytes HEADER2: indicates the function
Response:
CONTENT LENGTH NOTES
1 1 byte
The four bytes at the beginning indicate the command sent.
012 3 bytes
STEP = fiscal receipt step [from 0 to 8] where:
0 Receipt off
1 Receipt body (transaction)
2 Payments in progress
3 Change print
STEP 1 byte
4 Fixed lines print (optional)
5 Closing executed
6 Courtesy messages print (optional)
7 Ejection executed
8 Non fiscal receipt open
24 │ CUSTOM Protocol
1013 Printer model and release
Sent command:
CONTENT LENGTH NOTES
1 1 byte HEADER1: indicates the commands group
013 3 bytes HEADER2: indicates the function
Response:
CONTENT LENGTH NOTES
1 1 byte
The four bytes at the beginning indicate the command sent.
013 3 bytes
Rel.Stamp.= printer model and release (Description line that is same obtained using
Rel.Stamp. 32 byte
the command 2004 with the keyboard).
CUSTOM Protocol │ 25
1015 Error code
Sent command:
CONTENT LENGTH NOTES
1 1 byte HEADER1: indicates the commands group
015 3 bytes HEADER2: indicates the function
Response:
CONTENT LENGTH NOTES
1 1 byte
The four bytes at the beginning indicate the command sent.
015 3 bytes
ERR 3 bytes ERR = word ‘ERR’
nnn 3 bytes nnn = Last generated code over 99
DES Up to 10 bytes DES = description of the last generated code over 99
26 │ CUSTOM Protocol
1016 Receipts and invoice status
Sent command:
CONTENT LENGTH NOTES
1 1 byte HEADER1: indicates the commands group
016 3 bytes HEADER2: indicates the function
Response:
CONTENT LENGTH NOTES
1 1 byte
The four bytes at the beginning indicate the command sent.
016 3 bytes
S1 1 byte S1 = fiscal receipt in progress [0/1]
S2 1 byte S2 = non fiscal receipt in progress [0/1]
S3 1 byte S3 = invoice in progress [0/1]
CUSTOM Protocol │ 27
1017 Request for the last receipt
Sent command:
CONTENT LENGTH NOTES
1 1 byte HEADER1: indicates the commands group
017 3 bytes HEADER2: indicates the function
Response:
CONTENT LENGTH NOTES
1 1 byte
The four bytes at the beginning indicate the command sent.
018 3 bytes
GG 2 bytes GG = day (01 - 31)
MM 2 bytes MM = mounth (00 - 12)
AA 2 bytes AA = year (00 - 99)
HH 2 bytes HH = hour (00-24)
mm 2 bytes mm = minutes (00 - 59 )
NSCO 4 bytes NSCO = number of receipt
TOTSCO 9 bytes TOTSCO = total of the receipt
TIPO = 0 non fiscal receipt
TIPO = 1 fiscal receipt
TIPO 1 byte
TIPO = 2 invoice
TIPO = 3 credit note
STATUS = 0 receipt closed correctly
STATUS 1 byte
STATUS = 1 receipt cancelled
28 │ CUSTOM Protocol
1018 Daily total for credit notes
Sent command:
CONTENT LENGTH NOTES
1 1 byte HEADER1: indicates the commands group
018 3 bytes HEADER2: indicates the function
Response:
CONTENT LENGTH NOTES
1 1 byte
The four bytes at the beginning indicate the command sent.
018 3 bytes
NNC 4 bytes NSF = number of credit note [from 0 to 9999]
TNC 9 bytes TSF = total credit notes [from 0 to 999999999]
CUSTOM Protocol │ 29
1019 Total record in FM for specified file
Sent command:
CONTENT LENGTH NOTES
1 1 byte HEADER1: indicates the commands group
019 3 bytes HEADER2: indicates the function
NUMFILE 3 bytes NUMFILE: number of file to read (see TABLE FOR FILE CODES)
Response:
CONTENT LENGTH NOTES
1 1 byte
The four bytes at the beginning indicate the command sent.
019 3 bytes
NUMFILE 3 bytes NUMFILE: number of file to read
REC.CURR 4 bytes REC.CURR: current record number in FM
REC.MAX 4 bytes REC.MAX: max. possible records for the specified file (if required by fiscal law)
30 │ CUSTOM Protocol
1020 Detection of the device type
Sent command:
CONTENT LENGTH NOTES
1 1 byte HEADER1: indicates the commands group
020 3 bytes HEADER2: indicates the function
Response:
CONTENT LENGTH NOTES
1 1 byte
The four bytes at the beginning indicate the command sent.
020 3 bytes
TYPE:
NNC 4 bytes 01 = fiscal
10 = non fiscal
CUSTOM Protocol │ 31
1030 State service of sending documents to the Server
Sent command:
CONTENT LENGTH NOTES
1 1 byte HEADER1: indicates the commands group
030 3 bytes HEADER2: indicates the function
Response:
CONTENT LENGTH NOTES
1 1 byte
he four bytes at the beginning indicate the command sent.
030 3 bytes
FMON_STS = File Monitor Status
32 │ CUSTOM Protocol
1104 Last fiscal closing data and number of EJ
Sent command:
CONTENT LENGTH NOTES
1 1 byte HEADER1: indicates the commands group
104 3 bytes HEADER2: indicates the function
Response:
CONTENT LENGTH NOTES
1 1 byte
The four bytes at the beginning indicate the command sent.
104 3 bytes
N. CHIUS. 4 byte N. CHIUS. = Number of current fiscal closing
N. EJ 4 byte N. EJ = Number of current EJ
CUSTOM Protocol │ 33
1105 Grand total
Sent command:
CONTENT LENGTH NOTES
1 1 byte HEADER1: indicates the commands group
105 3 bytes HEADER2: indicates the function
Response:
CONTENT LENGTH NOTES
1 1 byte
The four bytes at the beginning indicate the command sent.
105 3 bytes
GRAN T. 10 bytes GRAN T. = Grand Total [from 0 to 9999999999]
34 │ CUSTOM Protocol
1106 Date and time of the last Z-report
Sent command:
CONTENT LENGTH NOTES
1 1 byte HEADER1: indicates the commands group
106 3 bytes HEADER2: indicates the function
Response:
CONTENT LENGTH NOTES
1 1 byte
The four bytes at the beginning indicate the command sent.
106 3 bytes
GG 2 bytes DD = Day [from 01 to 31]
MM 2 bytes MM = Month [from 01 to 12]
AA 2 bytes YY = Year [from 00 to 99]
HH 2 bytes HH = Hour [from 00 to 24]
mm 2 bytes mm = Minutes [from 00 to 59]
ss 2 bytes ss = Seconds [from 00 to 59]
CUSTOM Protocol │ 35
1107 Read last ticket date and time
Sent command:
CONTENT LENGTH NOTES
1 1 byte HEADER1: indicates the commands group
107 3 bytes HEADER2: indicates the function
Response:
CONTENT LENGTH NOTES
1 1 byte
The four bytes at the beginning indicate the command sent.
107 3 bytes
DATETIME 12 bytes DATETIME: last ticket date and time (DDMMYYHHMMSS)
36 │ CUSTOM Protocol
1109 Printer status
Sent command:
CONTENT LENGTH NOTES
1 1 byte HEADER1: indicates the commands group
109 3 bytes HEADER2: indicates the function
Response:
CONTENT LENGTH NOTES
1 1 byte
The four bytes at the beginning indicate the command sent.
109 3 bytes
S1 1 byte S1 = Cover open [0/1]
S2 1 byte S2 = Paper end [0/1]
S3 1 byte S3 = Near paper end [0/1]
S4 1 byte S4 = EJ full [0/1]
S5 = EJ nearly full [0/1]
S5 1 byte
(10 closing are still possible)
CUSTOM Protocol │ 37
1111 Receipt status
Sent command:
CONTENT LENGTH NOTES
1 1 byte HEADER1: indicates the commands group
111 3 bytes HEADER2: indicates the function
Response:
CONTENT LENGTH NOTES
1 1 byte
The four bytes at the beginning indicate the command sent.
111 3 bytes
S1 1 byte S1 = fiscal receipt in progress [0/1]
S2 1 byte S2 = non fiscal receipt in progress [0/1]
N.RECEIPT 4 bytes Fiscal/non fiscal receipt number (0 if no receipt in progress)
38 │ CUSTOM Protocol
1112 Fiscal receipt step
Sent command:
CONTENT LENGTH NOTES
1 1 byte HEADER1: indicates the commands group
112 3 bytes HEADER2: indicates the function
Response:
CONTENT LENGTH NOTES
1 1 byte
The four bytes at the beginning indicate the command sent
112 3 bytes
Fiscal receipt step
STEP 0: receipt off
STEP 1: receipt body (transaction)
STEP 2: payment in progress
STEP 3: change print
STEP 1 byte
STEP 4: printing of fixed line (optional)
STEP 5: closure executed
STEP 6: printing of courtesy message (optional)
STEP 7: ejection executed
STEP 8: non fiscal receipt open
N.RECEIPT 4 bytes Fiscal/non fiscal receipt number (0 if in receipt off)
CUSTOM Protocol │ 39
1113 Total counters
Sent command:
CONTENT LENGTH NOTES
1 1 byte HEADER1: indicates the commands group
113 3 bytes HEADER2: indicates the function
ITEM: Requested counter
ITEM 01: Number of fiscal receipt
ITEM 02: Total of fiscal receipt
ITEM 03: Net of VAT 1
ITEM 04: Tax of VAT 1
ITEM 05: Net of VAT 2
ITEM 06: Tax of VAT 2
ITEM 07: Net of VAT 3
ITEM 08: Tax of VAT 3
ITEM 09: Net of VAT 4
ITEM 10: Tax of VAT 4
ITEM 11: Net of VAT 5
ITEM 12: Tax of VAT 5
ITEM 13: Net of VAT 6
ITEM 14: Tax of VAT 6
ITEM 15: Total of cash in drawer
ITEM 2 bytes ITEM 16: Total of not payed
ITEM 17: Number of paid out
ITEM 18: Total of paid out
ITEM 19: Number of received in account
ITEM 20: Total of received in account
ITEM 21: Number of cancelled documents
ITEM 22: Total of cancelled documents
ITEM 23: Number of corrections
ITEM 24: Total of corrections
ITEM 25: Number of discounts
ITEM 26: Total of discounts
ITEM 27: Number of surcharges
ITEM 28: Total of surcharges
ITEM 29: Number of negative
ITEM 30: Total of negative
ITEM 31: Number of given back
ITEM 32: Total of given back
40 │ CUSTOM Protocol
Response:
CONTENT LENGTH NOTES
1 1 byte
The four bytes at the beginning indicate the command sent
113 3 bytes
COUNTER 9 bytes Requested counter value
CUSTOM Protocol │ 41
1115 Meter reading daily extended
Sent command:
CONTENT LENGTH NOTES
1 1 byte HEADER1: indicates the commands group
115 3 bytes HEADER2: indicates the function
Response:
CONTENT LENGTH NOTES
1 1 byte
The four bytes at the beginning indicate the command sent
115 3 bytes
NSCO 4 bytes NSCO = number receipt
TOTSCO 9 bytes TOTSCO = Total receipt
NNOTECR 4 bytes NNOTECR = Number of credit note
TOTNOTECR 9 bytes TOTNOTECR =Total of credit note
NALLV 4 bytes NALLV = Number annulled receipt
TOTALLV 9 bytes TOTALLV = Total annulled receipt
NFOND 4 bytes NFOND = Number Discount “Foundation“ (only for customized models)
TOTFOND 9 bytes TOTFOND = Total Discount “Foundation“ (only for customized models)
42 │ CUSTOM Protocol
1209 Printer status
Sent command:
CONTENT LENGTH NOTES
1 1 byte HEADER1: indicates the commands group
209 3 bytes HEADER2: indicates the function
Response:
CONTENT LENGTH NOTES
1 1 byte
The four bytes at the beginning indicate the command sent
209 3 bytes
S1 1 byte S1 = Cover open [0/1]
S2 1 byte S2 = Paper end [0/1]
S3 1 byte S3 = Near Paper end [0/1]
S4 1 byte S4 = EJ Full [0/1]
S5 = EJ nearly full [0/1]
S5 1 byte
(10 closing are still possible)
S6 = Cutter condition [0/1]
S6 1 byte
(1= error)
CUSTOM Protocol │ 43
1210 Printer status + virtual paper end
Sent command:
CONTENT LENGTH NOTES
1 1 byte HEADER1: indicates the commands group
210 3 bytes HEADER2: indicates the function
Response:
CONTENT LENGTH NOTES
1 1 byte
The four bytes at the beginning indicate the command sent.
210 3 bytes
S1 1 byte S1 = Cover open [0/1]
S2 1 byte S2 = Paper end [0/1]
S3 1 byte S3 = Near Paper end [0/1]
S4 1 byte S4 = EJ full [0/1]
S5 1 byte S5 = EJ nearly full [0/1]
S6 1 byte S6 = Cutter error [0/1]
S7 1 byte S7 = Near virtual paper end [0/1]
44 │ CUSTOM Protocol
1211 Fiscal memory status
Sent command:
CONTENT LENGTH NOTES
1 1 byte HEADER1: indicates the commands group
211 3 bytes HEADER2: indicates the function
Response:
CONTENT LENGTH NOTES
1 1 byte
The four bytes at the beginning indicate the command sent
211 3 bytes
S1 1 byte S1 = Fiscal Memory absent [0/1] (no_mf)
S2 1 byte S2 = Fiscal Memory damaged [0/1] (mf_ko)
S3 1 byte S3 = Fiscal Memory “inizialized” [0/1]
S4 1 byte S4 = Fiscal Memory nearly full [0/1]
S5 1 byte S5 = Fiscal Memory full [0/1]
CUSTOM Protocol │ 45
1270 Enable / disable autocutter
Sent command:
CONTENT LENGTH NOTES
1 1 byte HEADER1: indicates the commands group
270 3 bytes HEADER2: indicates the function
X = 1 Autocutter enabled
S1 1 byte
X = 0 Autocutter disabled
Response:
CONTENT LENGTH NOTES
1 1 byte
The four bytes at the beginning indicate the command sent.
270 3 bytes
46 │ CUSTOM Protocol
1271 Enable/disable keyboard and keys panel
Sent command:
CONTENT LENGTH NOTES
1 1 byte HEADER1: indicates the commands group
271 3 bytes HEADER2: indicates the function
TI = TYPE
0 = KEYB: OK, FEED: OK, COVER: OK
1 = KEYB: KO, FEED: OK, COVER: OK
TI 1 byte
2 = KEYB: KO, FEED: KO, COVER: OK
3 = KEYB: KO, FEED: OK, COVER: KO
4 = KEYB: KO, FEED: KO, COVER: KO
Response:
CONTENT LENGTH NOTES
1 1 byte
The four bytes at the beginning indicate the command sent
271 3 bytes
CUSTOM Protocol │ 47
1309 Paper status
Sent command:
CONTENT LENGTH NOTES
1 1 byte HEADER1: indicates the commands group
309 3 bytes HEADER2: indicates the function
Response:
CONTENT LENGTH NOTES
1 1 byte
The four bytes at the beginning indicate the command sent.
309 3 bytes
COD_ERRCARTA = error code
SCOD_ERR- 000 = No error
2 bytes
CARTA 100 = Paper end
010 = Near paper end
48 │ CUSTOM Protocol
1513 Wait end of security operation
Sent command:
CONTENT LENGTH NOTES
1 1 byte HEADER1: indicates the commands group
513 3 bytes HEADER2: indicates the function
Response:
CONTENT LENGTH NOTES
1 1 byte HEADER1: indicates the commands group
513 3 bytes HEADER2: indicates the function
CUSTOM Protocol │ 49
50 │ CUSTOM Protocol
FISCAL OPERATIONS COMMANDS
Response:
CONTENT LENGTH NOTES
2 1 byte
The four bytes at the beginning indicate the command sent.
001 3 bytes
STEP [0,1,2] where:
0 If date is programmed
STEP 1 byte
1 Message received, waiting for confirmation (re-send the same command)
2 Message received, waiting the second confirmation
NOTE:
When it is required to the device to program date/time, the device waits a confirmation (double if the new date exceeds
of 2 days or more the latest daily closing date) before making the clock programming. If the sequence above is not
respected, the device doesn’t accept the new date and it maintains the previous one.
CUSTOM Protocol │ 51
2002 Fiscal Z-report
Sent command:
CONTENT LENGTH NOTES
2 1 byte HEADER1: indicates the commands group
002 3 bytes HEADER2: indicates the function
PITCH (optional):
PITCH 1 byte 1 = Enables the use of bytes 5-6, 7-28
2 = Enable Retract
LEN 2 bytes LEN = length (num. bytes) of the next parameter (optional)
DES = Additional description printed at the end of the closing [alphanumeric]
DES 0-max. bytes (*)
(optional), the number of remaining EJ lines is shown below
Response:
CONTENT LENGTH NOTES
2 1 byte
The four bytes at the beginning indicate the command sent.
002 3 bytes
NOTES:
If the daily receipt closing print is not executed correctly, an error message will be sent; after this the master may ask
the status to know the error (or the errors) happened.
(*): max. value can be 22 bytes (normal font) or 56 bytes (compressed font).
52 │ CUSTOM Protocol
2003 Fiscal X-report
Sent command:
CONTENT LENGTH NOTES
2 1 byte HEADER1: indicates the commands group
003 3 bytes HEADER2: indicates the function
Response:
CONTENT LENGTH NOTES
2 1 byte
The four bytes at the beginning indicate the command sent.
003 3 bytes
CUSTOM Protocol │ 53
2005 Fiscalization
Sent command:
CONTENT LENGTH NOTES
2 1 byte HEADER1: indicates the commands group
005 3 bytes HEADER2: indicates the function
Response:
CONTENT LENGTH NOTES
2 1 byte
The four bytes at the beginning indicate the command sent.
005 3 bytes
54 │ CUSTOM Protocol
2006 Periodical report
Sent command:
CONTENT LENGTH NOTES
2 1 byte HEADER1: indicates the commands group
006 3 bytes HEADER2: indicates the function
MM 2 bytes MM = Month [from 01 to 12] of the next periodical report
YY 2 bytes YY = Year [from 00 to 99] of the next periodical report
Response:
CONTENT LENGTH NOTES
2 1 byte
The four bytes at the beginning indicate the command sent.
006 3 bytes
NOTE:
The sequence performs and prints periodical report checking the operative functionality for fiscal memory and memory
card (electronic journal).
CUSTOM Protocol │ 55
2008 Programming/reading production string
Option 1 - Programming parameters
Sent command:
CONTENT LENGTH NOTES
2 1 byte HEADER1: indicates the commands group
008 3 bytes HEADER2: indicates the function
PRODNUM 16 bytes PRODNUM: production string (alphanumeric)
Response:
CONTENT LENGTH NOTES
2 1 byte
The four bytes at the beginning indicate the command sent.
008 3 bytes
Sent command:
CONTENT LENGTH NOTES
2 1 byte HEADER1: indicates the commands group
008 3 bytes HEADER2: indicates the function
Response:
CONTENT LENGTH NOTES
2 1 byte
The four bytes at the beginning indicate the command sent.
008 3 bytes
PRODNUM 16 bytes PRODNUM: production string (alphanumeric)
56 │ CUSTOM Protocol
2102 Departments zero setting
Sent command:
CONTENT LENGTH NOTES
2 1 byte HEADER1: indicates the commands group
102 3 bytes HEADER2: indicates the function
Response:
CONTENT LENGTH NOTES
2 1 byte
The four bytes at the beginning indicate the command sent.
102 3 bytes
CUSTOM Protocol │ 57
2103 Departments read out
Sent command:
CONTENT LENGTH NOTES
2 1 byte HEADER1: indicates the commands group
103 9 bytes HEADER2: indicates the function
Response:
CONTENT LENGTH NOTES
2 1 byte
The four bytes at the beginning indicate the command sent.
103 93 bytes
58 │ CUSTOM Protocol
2201 Counter of class 2 increasing
Sent command:
CONTENT LENGTH NOTES
2 1 byte HEADER1: indicates the commands group
201 3 bytes HEADER2: indicates the function
VAL.DOC2 9 bytes VAL.DOC2 = value with implicit decimal for invoice printed with non fiscal receipt.
Response:
CONTENT LENGTH NOTES
2 1 byte
The four bytes at the beginning indicate the command sent.
201 3 bytes
CUSTOM Protocol │ 59
2202 Report execution with zero setting
Sent command:
CONTENT LENGTH NOTES
2 1 byte HEADER1: indicates the commands group
202 3 bytes HEADER2: indicates the function
00 = Information device report
01 = Z-Report
02 = Financial report
03 = Historical financial report
04 = Time band report
05 = Historical time band report
06 = Departments report
TYPE 2 bytes 07 = Historica IVA Report
08 = Historical departments report
09 = PLU report
10 = Historical tender report
11 = Historical PLU report
12 = User report
13 = Historical user report
14 = Customer report
Response:
CONTENT LENGTH NOTES
2 1 byte
The four bytes at the beginning indicate the command sent.
202 3 bytes
60 │ CUSTOM Protocol
2203 Report execution
Sent command:
CONTENT LENGTH NOTES
2 1 byte HEADER1: indicates the commands group
203 3 bytes HEADER2: indicates the function
00 = Information device report
01 = X-Report
02 = Financial report
03 = Historical financial report
04 = Time band report
05 = Historical time band report
06 = Departments report
TYPE 2 bytes 07 = Historica IVA Report
08 = Historical departments report
09 = PLU report
10 = Historical tender report
11 = Historical PLU report
12 = User report
13 = Historical user report
14 = Customer report
Response:
CONTENT LENGTH NOTES
2 1 byte
The four bytes at the beginning indicate the command sent.
203 3 bytes
CUSTOM Protocol │ 61
62 │ CUSTOM Protocol
C O M M A N D S O F C R E AT I O N O F F I S C A L
DOCUMENT
ATTENTION:
This command execute a generic sale not related to department / VAT rate. See command 3101 for sale related to
department / VAT rate.
For “description” parameter use characters up to 0x7D of ASCII standard set.
NOTES:
The description can’t, in any case, occupy the same columns of the 5 figures less important of the amount, otherwise
it will be cut off; moreover description and amount (or symbols that precede it) must be divided by at least a space,
otherwise the amount (with symbols) will be printed on a second line.
In case = 4 (void) , IMP field must be equal to the amount to reverse. Besides, after “all void” (type = 8), send the ap-
propriate commands the eject the receipt (3011 and 3013).
(*): max. value can be 22 bytes (normal font) or 56 bytes (compressed font).
Response:
CONTENT LENGTH NOTES
3 1 byte
The four bytes at the beginning indicate the command sent.
001 3 bytes
NOTES:
To the string reception, before executing the print are checked the following conditions:
• In the description there isn’t the inscription “TOTAL”;
• There are any other operation or fiscal receipt in progress;
• The amount doesn’t overflow or underflow the receipt totals, the daily totals and the progressive fiscal total.
If all these are verified, the operation will be printed, at the contrary the error will be signalled.
CUSTOM Protocol │ 63
3002 Additional line (additional operator description)
Sent command:
CONTENT LENGTH NOTES
3 1 byte HEADER1: indicates the commands group
002 3 bytes HEADER2: indicates the function
PITCH [from 1 to 9] =
1 (normal)
2 (bold)
3 (42 characters)
4 (double height)
PITCH 1 byte
5 (double width)
6 (italic)
7 (normal/double height/42 characters)
8 (bold/42 characters)
9 (bold/double height/42 characters)
LEN 2 bytes LEN = length (num. bytes) of the next parameter
ROW 0-max. bytes (*) ROW = Operator description [alphanumeric]
Response:
CONTENT LENGTH NOTES
3 1 byte
The four bytes at the beginning indicate the command sent.
002 3 bytes
NOTES:
It’s possible to use the command when a fiscal operation is allowed (not calculable function or following operation
description).
If ROW contains special symbol/characters the description is managed as simple text.
(*): max. value can be 42 bytes (normal font) or 56 bytes (compressed font).
64 │ CUSTOM Protocol
3003 Subtotal print out
Sent command:
CONTENT LENGTH NOTES
3 1 byte HEADER1: indicates the commands group
003 3 bytes HEADER2: indicates the function
Response:
CONTENT LENGTH NOTES
3 1 byte
The four bytes at the beginning indicate the command sent.
003 3 bytes
NOTE:
If the subtotal is negative, it’s printed the value preceded by “-” sign.
CUSTOM Protocol │ 65
3004 Payment with corresponding paid
Sent command:
CONTENT LENGTH NOTES
3 1 byte HEADER1: indicates the commands group
004 3 bytes HEADER2: indicates the function
LEN 2 bytes LEN = length (num. bytes) of the next parameter
DES 0-22 bytes DES = Description of the operation [alphanumeric]
IMP 9 bytes IMP = Amount [numeric]
Response:
CONTENT LENGTH NOTES
3 1 byte
The four bytes at the beginning indicate the command sent.
004 3 bytes
SIGN 1 byte SIGN = sign for remnant [+/-] where sign “–“ indicate the change
REM = remnant to pay (or change) [from 0 to 999999999]
REM 9 bytes
(if remnant = 0 the sign is “-“).
66 │ CUSTOM Protocol
3005 Payment with corresponding not paid
Sent command:
CONTENT LENGTH NOTES
3 1 byte HEADER1: indicates the commands group
005 3 bytes HEADER2: indicates the function
LEN 2 bytes LEN = length (num. bytes) of the next parameter
DES 0-22 bytes DES = Description of the operation [alphanumeric]
IMP 9 bytes IMP = Amount [numeric]
Response:
CONTENT LENGTH NOTES
3 1 byte
The four bytes at the beginning indicate the command sent
005 3 bytes
SIGN 1 byte SIGN = sign for remnant [+/-] where sign “–“ indicate the change
REM = remnant to pay (or change) [from 0 to 999999999]
REM 9 bytes
(if remnant = 0 the sign is “-“).
CUSTOM Protocol │ 67
3006 Payment with EFT POS
Sent command:
CONTENT LENGTH NOTES
3 1 byte HEADER1: indicates the commands group
006 3 bytes HEADER2: indicates the function
LEN 2 bytes LEN = length (num. bytes) of the next parameter
DES 0-22 bytes DES = Description of the operation [alphanumeric]
IMP 9 bytes IMP = Amount [numeric]
Response:
CONTENT LENGTH NOTES
3 1 byte
The four bytes at the beginning indicate the command sent
006 3 bytes
SIGN 1 byte SIGN = sign for remnant [+/-] where sign “–“ indicate the change
REM = remnant to pay (or change) [from 0 to 999999999]
REM 9 bytes
(if remnant = 0 the sign is “-“).
68 │ CUSTOM Protocol
3007 Prefixed payment
Sent command:
CONTENT LENGTH NOTES
3 1 byte HEADER1: indicates the commands group
007 3 bytes HEADER2: indicates the function
PAYM 2 bytes PAYM= indicates the fixed payment code in cash (default [from 1 to 0])
AGREE 2 bytes AGREE = indicates the payment convention code [from 1 to 99]
LEN = length (num. bytes) of the description characters of PAYM parameter (if LEN =
LEN 2 bytes
0 the description is not sent)
DES 0-22 bytes DES = Description of the payment related to the PAYM field [alphanumeric]
AM = Payment amount [from 0 to 999999999]
AM 9 bytes
(if AM = 0 the price is not sent and the the payment is closed directly).
Response:
CONTENT LENGTH NOTES
3 1 byte
The four bytes at the beginning indicate the command sent
007 3 bytes
SIGN 1 byte SIGN = sign for remnant [+/-] where sign “–“ indicate the change
REM = remnant to pay (or change) [from 0 to 999999999]
REM 9 bytes
(if remnant = 0 the sign is “-“).
CUSTOM Protocol │ 69
3008 Additional line for payments
Sent command:
CONTENT LENGTH NOTES
3 1 byte HEADER1: indicates the commands group
008 3 bytes HEADER2: indicates the function
PITCH [from 1 to 9] =
1 (normal)
2 (bold)
3 (42 characters)
4 (double height)
PITCH 1 byte
5 (double width)
6 (italic)
7 (normal/double height/42 characters)
8 (bold/42 characters)
9 (bold/double height/42 characters)
LEN 2 bytes LEN = length (num. bytes) of the next parameter
ROW 0-max. bytes (*) ROW = additional description text for payment [alphanumeric]
Response:
CONTENT LENGTH NOTES
3 1 byte
The four bytes at the beginning indicate the command sent.
008 3 bytes
NOTE:
(*): max. value can be 42 bytes (normal font) or 56 bytes (compressed font).
70 │ CUSTOM Protocol
3009 Remnant print out
Sent command:
CONTENT LENGTH NOTES
3 1 byte HEADER1: indicates the commands group
009 3 bytes HEADER2: indicates the function
Response:
CONTENT LENGTH NOTES
3 1 byte
The four bytes at the beginning indicate the command sent.
009 3 bytes
CUSTOM Protocol │ 71
3010 Fixed rows
Sent command:
CONTENT LENGTH NOTES
3 1 byte HEADER1: indicates the commands group
010 3 bytes HEADER2: indicates the function
PITCH = 1 (normal)
PITCH = 2 (bold)
PITCH = 3 (42 chrs)
PITCH = 4 (double height)
PITCH = 5 (double width)
PITCH 1 byte PITCH = 6 (italic)
PITCH = 7 (normal/double height/42 chrs)
PITCH = 8 (bold/42 chr)
PITCH = 9 (bold/double height/42 chrs)
PITCH = B (customer CF/PIVA)
PITCH = C (customer description, used only if PITCH B is present as well)
LEN 2 bytes LEN = row length
ROW 0-max. bytes (*) ROW = description
Response:
CONTENT LENGTH NOTES
3 1 byte
The four bytes at the beginning indicate the command sent
010 3 bytes
NOTES:
It’s possible to use the command when a receipt closing is allowed. It come useful to print as number of package,
number/name of operator, etc. It can occupy the complete paper width.
With the PITCH value = C the customer description lines are defined as invoice consignee, that are positioned in the
printing layout in the Consignee data. This customer insertion is defined straightaway because the data are not added
into customer machine archive; they are not restrictions of the lines number to send with this command.
(*): max. value can be 42 bytes (normal font) or 56 bytes (compressed font).
72 │ CUSTOM Protocol
3011 Closing fiscal document
Sent command:
CONTENT LENGTH NOTES
3 1 byte HEADER1: indicates the commands group
011 3 bytes HEADER2: indicates the function
Response:
CONTENT LENGTH NOTES
3 1 byte
The four bytes at the beginning indicate the command sent
011 3 bytes
NUMDOC 4 bytes NUMDOC: document number
NOTES:
If you don’t use partial payments, with closing command is printed the TOTAL and the same closing.
If you send another payment after covering the amount, you receive an error message.
Before the closing or the first fixed line, if you effect some payment, CHANGE is automatically printed.
CUSTOM Protocol │ 73
3012 Courtesy lines
Sent command:
CONTENT LENGTH NOTES
3 1 byte HEADER1: indicates the commands group
012 3 bytes HEADER2: indicates the function
PITCH [from 1 to E] =
1 (normal)
2 (bold)
3 (42 characters)
4 (double height)
PITCH 1 byte 5 (double width)
6 (italic)
7 (normal/double height/42 characters)
8 (bold/42 characters)
9 (bold/double height/42 characters)
E (print Courtesy lines of the till)
LEN 2 bytes LEN = length (num. bytes) of the next parameter
ROW 0-max. bytes (*) ROW = additional description text for payment [alphanumeric]
Response:
CONTENT LENGTH NOTES
3 1 byte
The four bytes at the beginning indicate the command sent.
012 3 bytes
NOTE:
This command can be used only before the receipt ejection command.
(*): max. value can be 42 bytes (normal font) or 56 bytes (compressed font).
74 │ CUSTOM Protocol
3013 Receipt ejection with partial cut
Sent command:
CONTENT LENGTH NOTES
3 1 byte HEADER1: indicates the commands group
013 3 bytes HEADER2: indicates the function
Response:
CONTENT LENGTH NOTES
3 1 byte
The four bytes at the beginning indicate the command sent
013 3 bytes
CUSTOM Protocol │ 75
3014 Receipt ejection with partial cut and feed
Sent command:
CONTENT LENGTH NOTES
3 1 byte HEADER1: indicates the commands group
014 3 bytes HEADER2: indicates the function
Feed 1 bytes Number of paper feeds after the cut [from 0 to 9]
Response:
CONTENT LENGTH NOTES
3 1 byte
The four bytes at the beginning indicate the command sent
014 3 bytes
76 │ CUSTOM Protocol
3015 Receipt ejection with total cut
Sent command:
CONTENT LENGTH NOTES
3 1 byte HEADER1: indicates the commands group
015 3 bytes HEADER2: indicates the function
Response:
CONTENT LENGTH NOTES
3 1 byte
The four bytes at the beginning indicate the command sent
015 3 bytes
CUSTOM Protocol │ 77
3016 Buffered print out
Sent command:
CONTENT LENGTH NOTES
3 1 byte HEADER1: indicates the commands group
016 3 bytes HEADER2: indicates the function
SET =
SET 1 bytes 0 Disable buffered printing
1 Enable buffered printing
NOTE:
When the buffered printing is enabled an acoustic signal is emitted. When the buffered printing is disabled a double
acoustic signal is emitted.
Response:
CONTENT LENGTH NOTES
3 1 byte
The four bytes at the beginning indicate the command sent.
016 3 bytes
78 │ CUSTOM Protocol
3017 Graphic image print out
Sent command:
CONTENT LENGTH NOTES
3 1 byte HEADER1: indicates the commands group
017 3 bytes HEADER2: indicates the function
X 1 bytes X = starting of graphic image [from 0 to 3]
Y 1 bytes Y = number of graphic image [from 0 to 3]
Z 1 bytes Z = number of logo [from 1 to 2]
NOTE:
Command 3017 must be sent after command 3011.
Response:
CONTENT LENGTH NOTES
3 1 byte
The four bytes at the beginning indicate the command sent.
017 3 bytes
CUSTOM Protocol │ 79
3020 Force buffered print out
Sent command:
CONTENT LENGTH NOTES
3 1 byte HEADER1: indicates the commands group
020 3 bytes HEADER2: indicates the function
Response:
CONTENT LENGTH NOTES
3 1 byte
The four bytes at the beginning indicate the command sent
020 3 bytes
NOTE:
This command automatically clean the buffer before its use to optimise the emission of very long documents.
80 │ CUSTOM Protocol
3021 Receipt internal barcode print out
Sent command:
CONTENT LENGTH NOTES
3 1 byte HEADER1: indicates the commands group
023 3 bytes HEADER2: indicates the function
TYPE = barcode type [from 1 to 9] where:
1 (EAN13)
2 (EAN8)
3 (CODE39)
4 (EAN128)
TYPE 1 byte
5 (ITF, I2/5)
6 (QRCode)
7 (G1DATABAR)
8 (PDF417)
9 (UPC)
HRI = Human Readable Interpretation (Numeric code barcode)
HRI 1 byte 0 Numeric code barcode not printed
2 Numeric code barcode printed below
N/A 1 byte ALT = barcode height from 1 to 9 (customized)
N/A 1 byte Reserved
LEN 2 bytes LEN = Barcode length
CODE 0-40 bytes CODE = Numeric code of barcode
Response:
CONTENT LENGTH NOTES
3 1 byte
The four bytes at the beginning indicate the command sent
021 3 bytes
NOTE:
The ability to print barcodes depends on the features of the device.
CUSTOM Protocol │ 81
3022 Buffered print length definition
Sent command:
CONTENT LENGTH NOTES
3 1 byte HEADER1: indicates the commands group
022 3 bytes HEADER2: indicates the function
ROW 3 bytes ROW = n° lines in the buffer [from 0 to 255]
Response:
CONTENT LENGTH NOTES
3 1 byte
The four bytes at the beginning indicate the command sent.
022 3 bytes
82 │ CUSTOM Protocol
3023 Barcode print out
Sent command:
CONTENT LENGTH NOTES
3 1 byte HEADER1: indicates the commands group
023 3 bytes HEADER2: indicates the function
TYPE = barcode type [from 1 to 9] where:
1 (EAN13)
2 (EAN8)
3 (CODE39)
4 (EAN128)
TYPE 1 byte
5 (ITF, I2/5)
6 (QRCode)
7 (G1DATABAR)
8 (PDF417)
9 (UPC)
HRI = Human Readable Interpretation (Numeric code barcode)
HRI 1 byte 0 Numeric code barcode not printed
2 Numeric code barcode printed below
N/A 1 byte ALT = barcode height from 1 to 9 (customized)
LEN 3 bytes LEN = Barcode length
CODE 0-248 bytes Numeric code of barcode
Response:
CONTENT LENGTH NOTES
3 1 byte
The four bytes at the beginning indicate the command sent
021 3 bytes
NOTE:
The ability to print barcodes depends on the features of the device.
CUSTOM Protocol │ 83
3024 Trailer rows
Sent command:
CONTENT LENGTH NOTES
3 1 byte HEADER1: indicates the commands group
024 3 bytes HEADER2: indicates the function
PITCH = 1 (normal)
PITCH = 2 (bold)
PITCH = 3 (42 characters)
PITCH = 4 (double height)
TYPE 1 byte PITCH = 5 (double width)
PITCH = 6 (italic)
PITCH = 7 (normal/double height/42 characters)
PITCH = 8 (bold/42 characters)
PITCH = 9 (bold/double height/42 characters)
LEN 2 bytes LEN = (up to 56 characters)
ROW 0-max. bytes (*) Row to be printed as trailer
Response:
CONTENT LENGTH NOTES
3 1 byte
The four bytes at the beginning indicate the command sent
024 3 bytes
NOTE:
The ability to print barcodes depends on the features of the device.
(*): max. value can be 42 bytes (normal font) or 56 bytes (compressed font).
84 │ CUSTOM Protocol
3101 Fiscal operation with selected department
Sent command:
CONTENT LENGTH NOTES
3 1 byte HEADER1: indicates the commands group
101 3 bytes HEADER2: indicates the function
TYPE = type [from 1 to C] where:
1 = Sale on specific department
2 = Extra charge on specific department
3 = Discount on specific department
TYPE 1 byte 4 = Void
5 = Void of the last fiscal operation
8 = All void
B = Percentage Add-on
C = Percentage Discount
DEP. MERC 2 bytes REP. MERC = Department referred to Type 4 [from 1 to 20]
LEN.DES = Length for the description of department
LEN.DES 2 bytes
[alphanumeric]
DES max. bytes (*) DES = Description from the operator [alphanumeric]
IMP 9 bytes IMP = operation amount [numeric]
ATTENTION:
For “description” parameter use characters up to 125h of ASCII standard set.
NOTES:
TYPE 5: the DEP. MERC., the LEN.DES and the IMP may have value zero.
The description can’t, in any case, occupy the same columns of the 5 figures less important of the amount, otherwise
it will be cut off; moreover description and amount (or symbols that precede it) must be divided by at least a space,
otherwise the amount (with symbols) will be printed on a second line.
In the case of TYPE 4 (Reverse) the “amount” (IMP) field must be equal to or less than the amount to reverse. If greater,
the document can not be closed, as the total of the transaction will be result negative.
(*): max. value can be 22 bytes (normal font) or 56 bytes (compressed font).
Response:
CONTENT LENGTH NOTES
3 1 byte
The four bytes at the beginning indicate the command sent
101 3 bytes
CUSTOM Protocol │ 85
3111 Closing fiscal document
Sent command:
CONTENT LENGTH NOTES
3 1 byte HEADER1: indicates the commands group
116 3 bytes HEADER2: indicates the function
Response:
CONTENT LENGTH NOTES
3 1 byte
The four bytes at the beginning indicate the command sent
116 3 bytes
NUMDOC 4 bytes NUMDOC: document number
86 │ CUSTOM Protocol
3116 Buzzer activation
Sent command:
CONTENT LENGTH NOTES
3 1 byte HEADER1: indicates the commands group
116 3 bytes HEADER2: indicates the function
N. Beep 1 byte N.Beep = n° of beep emitted [from 0 to 9]
TONE = Musical tone [from 0 to 6] where:
0 C
1 D
2 E
TONE 1 byte
3 F
4 G
5 A
6 B
NOTE:
This command allows to emit an acoustic signal to draw the attention of the user, depending on the operative necessity.
Response:
CONTENT LENGTH NOTES
3 1 byte
The four bytes at the beginning indicate the command sent
116 3 bytes
CUSTOM Protocol │ 87
3203 Fiscal operation on selected PLU
Sent command:
CONTENT LENGTH NOTES
3 1 byte HEADER1: indicates the commands group
203 3 bytes HEADER2: indicates the function
TYPE = type where:
1 Sale
TYPE 1 byte
4 Void
9 Refund
LEN 2 bytes LEN = PLU code lenght
PLUCODE 1-13 bytes PLUCODE = Selected PLU code
LEN 2 bytes LEN = PLU code lenght
DES 0-max. bytes (*) DES = operation description
AMOUNT 9 bytes AMOUNT = amount
QTY 9 bytes QTY = item quantity (4 integer and 5 decimal)
Response:
CONTENT LENGTH NOTES
3 1 byte
The four bytes at the beginning indicate the command sent
203 3 bytes
NOTE:
(*): max. value can be 22 bytes (normal font) or 56 bytes (compressed font).
88 │ CUSTOM Protocol
3301 Fiscal operation with selected department and VAT
Sent command:
CONTENT LENGTH NOTES
3 1 byte HEADER1: indicates the commands group
301 3 bytes HEADER2: indicates the function
TYPE = type [from 1 to C] where:
1 = Sale on specific department
2 = Value extra charge on specific department
3 = Value discount on specific department
TYPE 1 byte 4 = Void (during the register items)
5 = Void of the last fiscal operation
8 = All void
B = Percentage Add-on
C = Percentage Discount
QTY 9 bytes QTY = item quantity (4 integer and 5 decimal)
NUM 3 bytes NUM = [numeric] department
LEN 2 bytes LEN = Length for the description of department [alphanumeric]
DES 0-max. bytes (*) DES = Description of department [alphanumeric]
IMP 9 bytes IMP = operation amount [numeric]
IDVAT 2 bytes IDVAT = ID VAT rate
Response:
CONTENT LENGTH NOTES
3 1 byte
The four bytes at the beginning indicate the command sent
301 3 bytes
NOTE:
(*): max. value can be 22 bytes (normal font) or 56 bytes (compressed font).
CUSTOM Protocol │ 89
3302 Fiscal operation with splitting up of price
Sent command:
CONTENT LENGTH NOTES
3 1 byte HEADER1: indicates the commands group
302 3 bytes HEADER2: indicates the function
TYPE = 1 Sale
TYPE = 2 Add-on
TYPE = 3 Discount
TYPE = 4 Void
TYPE 1 byte TYPE = 5 Void last fiscal operation
TYPE = 8 Receipt cancellation
TYPE = B Percentage Add-on
TYPE = C Percentage Discount
TYPE = D Payment cancellation
DEP 3 bytes DEP = number of selected department
PRICE 9 bytes PRICE = amount
IDVAT 2 bytes IDVAT = vat index
LEND 2 bytes LEND = department description lenght
DESC 0-max. bytes (*) DESC = Description of department [alphanumeric]
LENM 2 bytes LENM = measure description length
MEAS 0-5 bytes MEAS = measure description
QTY 9 bytes QTY = fraction numerator (4 integer and 5 decimal)
NOTES:
Operation TYPE 8 and TYPE 5 don’t need other filelds.
Operation TYPE D doesn’t need fileds DEP, IDVAT, LENM, MEAS, NUMER, DENOM.
(*): max. value can be 22 bytes (normal font) or 56 bytes (compressed font).
Response:
CONTENT LENGTH NOTES
3 1 byte
The four bytes at the beginning indicate the command sent
302 3 bytes
90 │ CUSTOM Protocol
COMMANDS OF DOCUMENTS CREATION
Response:
CONTENT LENGTH NOTES
4 1 byte
The four bytes at the beginning indicate the command sent
001 3 bytes
CUSTOM Protocol │ 91
4002 Heading print out
Sent command:
CONTENT LENGTH NOTES
4 1 byte HEADER1: indicates the commands group
002 3 bytes HEADER2: indicates the function
Response:
CONTENT LENGTH NOTES
4 1 byte
The four bytes at the beginning indicate the command sent
002 3 bytes
92 │ CUSTOM Protocol
4003 Print out description line
Sent command:
CONTENT LENGTH NOTES
4 1 byte HEADER1: indicates the commands group
003 3 bytes HEADER2: indicates the function
PITCH [from 1 to D] =
1 (normal)
2 (bold)
3 (42 characters)
4 (double height)
PITCH 1 byte 5 (double width)
6 (italic)
A (Reverse)(customized)
B (66 characters)
C (66 characters and reverse)
D (60 characters)
LEN 2 bytes LEN = length (num. bytes) of the following parameter
DES 0-80 bytes DES = Description of the line [alphanumeric]
NOTE:
(See command 4001).
The PITCH B, C, and D are valid only on devices that support 80 mm paper.
Response:
CONTENT LENGTH NOTES
4 1 byte
The four bytes at the beginning indicate the command sent
003 3 bytes
CUSTOM Protocol │ 93
4004 Non fiscal document closure
Sent command:
CONTENT LENGTH NOTES
4 1 byte HEADER1: indicates the commands group
004 3 bytes HEADER2: indicates the function
Response:
CONTENT LENGTH NOTES
4 1 byte
The four bytes at the beginning indicate the command sent
004 3 bytes
94 │ CUSTOM Protocol
4005 Business name print out
Sent command:
CONTENT LENGTH NOTES
4 1 byte HEADER1: indicates the commands group
005 3 bytes HEADER2: indicates the function
Response:
CONTENT LENGTH NOTES
4 1 byte
The four bytes at the beginning indicate the command sent
005 3 bytes
NOTE:
Prints a non fiscal receipt with the programmed heading lines.
CUSTOM Protocol │ 95
4007 Print receipt copy
Sent command:
CONTENT LENGTH NOTES
Response:
CONTENT LENGTH NOTES
4 1 byte
The four bytes at the beginning indicate the command sent
007 3 bytes
96 │ CUSTOM Protocol
COMMANDS OF FISCAL MEMORY CONTENT
PRINT OUT
Response:
CONTENT LENGTH NOTES
5 1 byte
The four bytes at the beginning indicate the command sent
001 3 bytes
CUSTOM Protocol │ 97
5002 Daily closing print out by date
Sent command:
CONTENT LENGTH NOTES
5 1 byte HEADER1: indicates the commands group
002 3 bytes HEADER2: indicates the function
DDi 2 bytes
MMi 2 bytes XXi = starting day, month, year
YYi 2 bytes
DDf 2 bytes
MMf 2 bytes XXf = final day, month, year
YYf 2 bytes
Response:
CONTENT LENGTH NOTES
5 1 byte
The four bytes at the beginning indicate the command sent
002 3 bytes
98 │ CUSTOM Protocol
5003 Daily closing addition print out by date
Sent command:
CONTENT LENGTH NOTES
5 1 byte HEADER1: indicates the commands group
003 3 bytes HEADER2: indicates the function
DDi 2 bytes
MMi 2 bytes XXi = starting day, month, year
YYi 2 bytes
DDf 2 bytes
MMf 2 bytes XXf = final day, month, year
YYf 2 bytes
Response:
CONTENT LENGTH NOTES
5 1 byte
The four bytes at the beginning indicate the command sent
003 3 bytes
CUSTOM Protocol │ 99
5004 Complete fiscal memory content print out
Sent command:
CONTENT LENGTH NOTES
5 1 byte HEADER1: indicates the commands group
004 3 bytes HEADER2: indicates the function
Response:
CONTENT LENGTH NOTES
5 1 byte
The four bytes at the beginning indicate the command sent
004 3 bytes
Response:
CONTENT LENGTH NOTES
5 1 byte
The four bytes at the beginning indicate the command sent
005 3 bytes
NOTE:
When device receives this command, it stops the receipt printing, closing the receipt.
Response:
CONTENT LENGTH NOTES
5 1 byte
The four bytes at the beginning indicate the command sent
006 3 bytes
Response:
CONTENT LENGTH NOTES
6 1 byte
The four bytes at the beginning indicate the command sent
301 3 bytes
Response:
CONTENT LENGTH NOTES
6 1 byte
The four bytes at the beginning indicate the command sent
302 3 bytes
Response:
CONTENT LENGTH NOTES
6 1 byte
The four bytes at the beginning indicate the command sent
303 3 bytes
REC.CURR 4 bytes REC.CURR: current record number in FM
REC.MAX 4 bytes REC.MAX: max. possible records for the specified file (if required by fiscal law)
Response:
CONTENT LENGTH NOTES
6 1 byte
The four bytes at the beginning indicate the command sent
801 3 bytes
N.ROW 1 byte N.ROW = Number of rows
NOTE:
To set the number of lines to print, use the command 6301.
Response:
CONTENT LENGTH NOTES
7 1 byte
The four bytes at the beginning indicate the command sent
001 3 bytes
Response:
CONTENT LENGTH NOTES
7 1 byte
The four bytes at the beginning indicate the command sent
005 3 bytes
NOTE:
Before you send the 7005 command, you must send the “Z-report” command (2002).
Response:
CONTENT LENGTH NOTES
7 1 byte
The four bytes at the beginning indicate the command sent
006 3 bytes
NOTE:
Before you send the 7006 command, you must send the “Z-report” command (2002).
Sent command:
CONTENT LENGTH NOTES
7 1 byte HEADER1: indicates the commands group
007 3 bytes HEADER2: indicates the function
N.LINE 40 bytes N.LINE = lines to display [alphanumeric]
Response:
CONTENT LENGTH NOTES
7 1 byte
The four bytes at the beginning indicate the command sent
007 3 bytes
Sent command:
CONTENT LENGTH NOTES
7 1 byte HEADER1: indicates the commands group
007 3 bytes HEADER2: indicates the function
Response:
CONTENT LENGTH NOTES
7 1 byte
The four bytes at the beginning indicate the command sent
007 3 bytes
Response:
CONTENT LENGTH NOTES
7 1 byte
The four bytes at the beginning indicate the command sent
008 3 bytes
DES: Alphanumeric description for department respecting the length LEN. Vice-
DES 0-16 bytes
versa the response is ERR03
IMP: Configured price for the department con implicit decimal (Example: 00010
IMP 5 bytes
= 10 cents)
IVA 2 bytes IVA: VAT rate for the department
Response:
CONTENT LENGTH NOTES
7 1 byte
The four bytes at the beginning indicate the command sent
009 3 bytes
Response:
CONTENT LENGTH NOTES
7 1 byte
The four bytes at the beginning indicate the command sent
010 3 bytes
NOTE:
This command can be used to program the scroll message on the customer display.
Response:
CONTENT LENGTH NOTES
7 1 byte
The four bytes at the beginning indicate the command sent
011 3 bytes
Response: If OP = “R”
CONTENT LENGTH NOTES
7 1 byte
The four bytes at the beginning indicate the command sent
106 3 bytes
SEGNOD 1 byte SEGNOD = sign of the cashdrawer content [+,-]
DRAWER 9 bytes DRAWER = cashdrawer content
Response:
CONTENT LENGTH NOTES
7 1 byte
The four bytes at the beginning indicate the command sent
107 3 bytes
Response:
CONTENT LENGTH NOTES
7 1 byte
The four bytes at the beginning indicate the command sent
108 3 bytes
S= 0 Drawer closed
S 1 byte
S= 1 Drawer open
Response:
CONTENT LENGTH NOTES
8 1 byte
The four bytes at the beginning indicate the command sent
001 3 bytes
Response:
CONTENT LENGTH NOTES
8 1 byte
The four bytes at the beginning indicate the command sent
002 3 bytes
Response:
CONTENT LENGTH NOTES
8 1 byte
The four bytes at the beginning indicate the command sent
003 3 bytes
Response:
CONTENT LENGTH NOTES
8 1 byte
The four bytes at the beginning indicate the command sent
004 3 bytes
ROW 64 bytes ROW = text in the line [alphanumeric]
NOTE:
Command 8004 should be used after command 8006.
Response:
CONTENT LENGTH NOTES
8 1 byte
The four bytes at the beginning indicate the command sent
005 3 bytes
Response:
CONTENT LENGTH NOTES
8 1 byte
The four bytes at the beginning indicate the command sent
006 3 bytes
REC INI = n° of starting line EJ
REC INI 9 bytes
[from 1 to 999999999]
REC.FIN = n° of final line EJ + 1
REC.FIN 9 bytes
[from 1 to 999999999]
REC.CUR = n° of the next line used in EJ
REC.CUR 9 bytes
[from 1 to 999999999]
REC.TOT = n° of total lines available in EJ
REC.TOT 9 bytes
[from 1 to 999999999]
Response:
CONTENT LENGTH NOTES
8 1 byte
The four bytes at the beginning indicate the command sent
007 3 bytes
Response:
CONTENT LENGTH NOTES
8 1 byte
The four bytes at the beginning indicate the command sent
008 3 bytes
PERC 5 bytes PERC = percentage of employment
Response:
CONTENT LENGTH NOTES
9 1 byte
The four bytes at the beginning indicate the command sent
100 3 bytes
NOTES:
The printer supports only monochrome bitmaps.
If the device detects a .bmp format not supported, the file is simply ignored and not loaded.
The new logo will actually be used by the machine only after making a Z-report.
In any case, you can check if the logo has been successfully loaded, checking for example, that the file header.bmp,
present at the path: FLASH DRIVE / Pict / Logos, is the one just sent.
Response:
CONTENT LENGTH NOTES
9 1 byte
The four bytes at the beginning indicate the command sent
101 3 bytes
SIZE 6 bytes Current size of the bmp file stored on printer.
NOTE:
This command should be sent several times until completion the entire image.
Response:
CONTENT LENGTH NOTES
9 1 byte
The four bytes at the beginning indicate the command sent
102 3 bytes
NOTE:
If no error occurs after this command, the device have successfully consolidate the logo just received.
INTRODUCTION
Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
COMMAND SEPARATOR
* Quality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
“ “ Wording . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
COMMAND TERMINATOR
= Subtotal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
1f X-Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
1F Z-Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
K Clear . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
21T Payment with luncheon voucher + change calculation (only FP models) . . . . . . . . . . . . .176
22T Payment with luncheon voucher + change calculation (only ECR models) . . . . . . . . . . .176
The aim of this document is to illustrate the specifications about communication protocol called “XON/XOFF” between fiscal
printers and generic host. All information defined in this document apply to all Custom fiscal devices (where applicable).
This protocol allow to create in advance all the data about sales transaction with a HOST and to transfer them to the fiscal
device for the real fiscal receipt (with all fiscal and managerial updating).
This “XON/XOFF” protocol is more adapt for generic HOST or enslaves terminal, governed by operating systems where
usually data transfer by serial line mechanisms are not accessible easily, neither to programmers neither to users.
Functionality
The XON/XOFF protocol is a software protocol used to control the data transferring between a transmitting devices (HOST)
and a receiving device (DEVICE).
According to the protocol, the HOST device transfers sequences of congruent data as described in this manual both to
syntactic and semantic level.
During the commands execution, because it is an unidirectional communication, the fiscal printer can’t reporting to the
HOST device possible error status generated from commands or sequence of command wrong. In this case the status
signalling will be displayed on customer display. For more information about the status signalling see the user manual.
The connection functionality with XON/XOFF protocol has to be programmed on the fiscal printer because it represents an
additional formality in comparison with the standard CUSTOM connection formality.
In the following scheme is synthetically described the rules of conduct for the fiscal printer which is regulated by means
of a flag or traffic lights. In normal condition the traffic lights is green (XON). When the printer receive the data to process
from the HOST, each data sent from the keyboard cannot be processed and vice versa. When the fiscal printer is newly
ready to receive new data send to the HOST device the green light (XON) and wait to receive data from the keyboard or
the HOST device.
1 2 3
BUFFER
BUFFER
DEVICE DEVICE DEVICE
During the communication between HOST device and fiscal printer, could occur a “buffer-overflow”. This condition happen
when the buffer of the fiscal printer is full and the data sent are irrecoverable loss.
To avoid this condition it is used a SECURITY LEVEL. When the data sent exceed the SECURITY LEVEL the fiscal printer
send the red light at the HOST device. The HOST device complete the transmission of the data package in progress and
then stops. When the data level in the buffer reach an appropriate level the transmission from the HOST device begin again.
MAX.
512 byte
512 byte
SECURITY LEVEL
Red light (XOFF) to the HOST
BUFFER
BUFFER
ATTENTION:
On the Fiscal printer has been set a communication time-out (4 seconds). If a command sent from the HOST device
is incomplete at the time-out expiring this command is deleted and the printer turn back to waiting status (for example
is possible send commands from the keyboard).
Fiscal printer can perform only the commands related with the expected functionality that are listed in the user manual or
in the add-on that come with the new FW version. Following are listed all the command for the the available functionality.
The logical connection protocol provides a “light” coding for data and/or commands received. Doesn’t use data to check
the package validity.
The structure for the command is composed of a sequence of DATA FIELDS attended by a TERMINATOR FIELD to indicate
the univocal end of the command:
C O M M A N D
TERMINATOR FIELD
DATA FIELD (optional) DATA FIELD (optional) DATA FIELD (optional)
(obligatory)
Where:
ATTENTION:
All the characters in the DATA FIELDS are valid if included in ASCI standard set (range 20H-7FH).
NOTE:
In the following pages data will be written down between ‘[‘ ‘]’; these types are not included in the data. Different input
sequences of the same type will be separated by ‘/’.
• Open a file with an example of input sequences (for example TEST.txt”), through a normal text editor.
• Execute the order from MS-DOS prompt: MODE COM1: 9600,N,8,1,R
• Execute: TYPE TEST.TXT > COM1
To make the first connection test between PC and fiscal printer, where PC is equipped with WINDOWS operating system,
after having set the fiscal printer, proceed as follows:
• Open a file with an example of input sequences as in previous chapters (for example TEST.txt”), through a normal
text editor.
• Execute:
- WINDOWS 9X-2K. XP the program Hyperterminal “Hypertrm.exe”
• At “SETTINGS”:
- select the port,
- transmission speed (baud rate = 9600),
- stop bit number (1),
- the parity (no parity),
- the flow control (Xon/Xoff).
• At “TRANSFERS”, execute SEND TEXT FILE and select the file “TEST.txt”.
Connection parameters
The connection parameters for the 1st generation of fiscal products are the following:
The connection parameters for the 2nd generation of fiscal products are the same of 1st MODE (see previous table). Only
the BAUD RATE can be set with 1200, 2400, 4800, 9600, 19200, 38400 or 57600.
NOTE:
To modify the parameters see the user manual of the fiscal printer.
100 *
100.25 *
1000 H
100000 H
“ ART.N.1 “
“ ~TOT.~ “
NOTE:
The maximum length for the description is 22 characters;
description can contains ALPHANUMERICAL characters.
Print a line with the total of sales till then without closing Print a line with a number attended by character [ # ] without
the receipt. consider the number a sale.
Example of command:
1000 #
Example of command:
“ 123456 “ @
“ TEST “ 1%
Example of command with descriptive line inside the ticket
body
NOTE:
The maximum length of the description is 20 digits per line.
1000 H 1 R “ PANE “ @ 1 T
Example of command:
“ TEST “ 2%
NOTE:
The maximum length of the description is 20 digits per line
1f 2f
3f 4f
Example of command:
6f
7f
Example of command:
8f
j “ 123456 “ @ J
k
1w
NOTE:
When the fiscal printer is using the Buffered mode and
the “Print fiscal receipt void” is enabled, the terminator [
k ] doesn’t print the receipt.
Example of print from 01/01/2015 to 01/02/2015: Example of print from receipt number 0001 to 0002:
“ 010115020108 “ 2w “ 00010002 “ 3w
4w
“ 0101150201115 “ 5w
“ 01011500010002 “ 6w
Example of command: Fiscal memory dump (totals) between two dates. The se-
quence is: starting date and final date in DDMMYY format
(between inverted comas) attended by the terminator.
8w
Example of print from 1 January 2015 to 2 January 2015:
“ 010115020115 “ 9w
Example of command: 1F
“ 0101151200 “ D
3F
2F
4F 5F
6F 7F
Example of command:
• Alphanumeric code [ @ ]
Example of command:
“ 012345678901 “ @ 41F
0M 3 R
0M 200 H 3 R
0M 2 * 3 R
3 R 25 * 1M = 25 * 2M
3 R 500 H 3M = 500 H 4M
Example of 25% extra charge on DEPARTMENT3: Example of 25% extra charge on SUBTOTAL:
3 R 25 * 5M = 25 * 6M
3 R 500 H 7M = 500 H 8M
10M 3 R
10M 200 H 3 P
10M 2 * 3 R
14M
13M
Note:
Example of closing with 2 € credit and cash for the remain- The closure is allowed only by payment in cash.
ing:
200 H 13M 1T
15M
ATTENTION:
If the cash drawer contains an amount less than the levy
imposed, the display shows the message “NOT ENOUGH
CASH”.
NOTE:
The closure is allowed only by payment in cash.
5 * 1 R
5 . 25 * 1 R
1000 H 1 R
1025 H 1 R
“ BREAD “ 5 * 1000 H 1 R
STX n ETX 1T
Example of payment with cheque without change calcula- Example of payment with electronic card without change
tion: calculation:
2T 3T
Example of payment with cheque with change calculation: Example of payment with electronic card with change cal-
culation:
2000 H 2T
2000 H 3T
Closing of fiscal receipt with a generic payment using one Closing of fiscal receipt with a payment with luncheon
the following mode: voucher using one the following mode.
If the value of the transaction is less than the luncheon
Example of generic payment without change calculation. voucher is printed a SUNDRIES line indicating the difference
to reach the luncheon voucher value.
7T
200 H 4T 1T
Example of payment with luncheon voucher without change Example of payment with luncheon voucher without change
calculation: calculation:
21T 22T
Example of payment with 20 € luncheon voucher with Example of payment with 20 € luncheon voucher with
change calculation: change calculation:
ATTENTION:
The command is allowed from HOST to keyboard and “ 123456789012 “ 1Z
not vice versa.
“ 1234567890123 “ 1Z
Print a EAN8 type BARCODE at the end of the receipt. The Print a CODE39 type BARCODE at the end of the receipt.
string to convert must be in numeric format of 7 or 8 digits. The string to convert must be in alphanumeric format (all
in CAPITAL).
Example of string with 7 digits + calculated CHECKDIGIT:
Example of command:
“ 1234567 “ 2Z
“ ABCDEFGHILMNOP “ 3Z
Example of command:
Examples of commands:
“ {A12345678901234 “ 4Z
“ {B123456789AaBbCc “ 4Z
“ {C1200000003456789012345678901 “ 4Z
Example of command:
“ ABCDEFGHILMNOP “ 6Z