th 5v sr - programmers guide v19 p

7/31/2019 TH 5V SR - Programmers Guide v19 p

1/40

POSNET POLSKA S.A.ul. Municypalna, 3302-281 WARSZAWA\phone (+48 22) 868 68 88

fax (+48 22) 868 68 89www.posnet.com

FISCAL PRINTERPOSNET Thermal SR

PROGRAMMER'S MANUAL

Revision 1.19p

02.02.2005


2/40

FISCAL PRINTER POSNET Thermal SR PROGRAMMER'S MANUAL REV 1.19p

ContentsHISTORY OF CHANGES................................................................................................................................. 4INTRODUCTION.............................................................................................................................................. 5

CONTROL CODES........................................................................................................................................... 6BEL (07h) - sound signal........................................................................................................................ 6CAN (18h) - exit from the state of waiting for user reaction (command cancellation)..............................6ENQ (05h) - operation status query........................................................................................................ 6DLE (10h) - device status query.............................................................................................................. 6

COMMUNICATION........................................................................................................................................... 7COMMANDS SYNTAX..................................................................................................................................... 7

Algorithm of checksum calculation ......................................................................................................... 7Standard response.................................................................................................................................. 8Zero totalizers......................................................................................................................................... 8

DESCRIPTION OF SEQUENCES IN PRINTER THERMAL SR ...................................................................... 9BASIC SEQUENCES GROUP:.................................................................................................................... 9

[ OPNDRW ] Drawer opening................................................................................................................. 9[ LINEFEED ] Paper feed........................................................................................................................ 9

[ GETCLK ] Clock read........................................................................................................................... 9[ DSTSET ] Time change (winter/summer)........................................................................................... 10[ GETVAT ] VAT (tax) rates readout..................................................................................................... 10[ SETVAT ] VAT rates programming..................................................................................................... 10[ GETHDR ] Header readout................................................................................................................. 11[ SETHDR ] Header programming........................................................................................................ 11[ SETADV ] Advertising text programming............................................................................................ 12[ GETADV ] Advertising text readout..................................................................................................... 12[ DAYREP ] Daily report........................................................................................................................ 13[ PERREP ] Periodical report................................................................................................................ 13[ INTERSEC ] Status intersection (fiscal report).................................................................................... 13[ GETSTS ] Printer status..................................................................................................................... 14[ GETTOT ] Totalizers and counters readout........................................................................................ 14

[ BMPDATA ] Graphics programming................................................................................................... 15[ BMPDATAGET ] Graphics line readout.............................................................................................. 15[ BMPSET ] Sent graphics confirmation................................................................................................ 15[ BMPGET ] Graphics settings readout................................................................................................. 16[ ADV_BMP ] Advertising graphics and text test printout....................................................................... 16[ GETOPT ] Configuration options readout........................................................................................... 16[ SETOPT ] Configuration options programming................................................................................... 17[ DOCLINE ] Non-fiscal printout line...................................................................................................... 18[ DOCEND ] Non-fiscal printout ending................................................................................................. 19[ DSPOUT ] Display control................................................................................................................... 19[ FMINFO ] Fiscal memory information readout................................................................................... 20

PLU BASE MAINTENANCE SEQUENCES GROUP................................................................................. 21[ PLUADD ] Record adding to PLU base (items)................................................................................... 21[ PLUDEL ] Record deletion from PLU base (items)............................................................................. 22[ PLUDELALL ] Deletion of all records from PLU base (items)............................................................. 22[ PLUGET ] PLU base record information readout................................................................................ 22[ PLUFIND ] PLU base record search................................................................................................... 23[ PLUINFO ] PLU base information readout.......................................................................................... 23[ PLUREPORT ] PLU report.................................................................................................................. 24[ PLUREPLINE ] Selective PLU report line............................................................................................ 24[ DEFRAG] PLU base defragmentation................................................................................................ 24

SERVICE SEQUENCES GROUP.............................................................................................................. 26[ SETCLK ] Clock setting...................................................................................................................... 26[ SETFMID ] Fiscal module ID (IBFM) programming............................................................................. 26[ CRFSK ] Printer fiscalization............................................................................................................... 26

TRANSACTION SEQUENCES GROUP.................................................................................................... 28[ TRSHDR ] Transaction start............................................................................................................... 28

[ TRSLINE ] Transaction line................................................................................................................ 28[ TRSLINEVOID ] Transaction line storno............................................................................................. 30

page 2 of 40


3/40


[ TRSINFO ] Transaction information readout....................................................................................... 30[ TRSLINEGET ] Line readout from sales buffer................................................................................... 31[ TRSEXIT ] Transaction mode exit...................................................................................................... 31[ TRSSUB ] Transaction subtotal information readout.......................................................................... 31[ TRSEND ] Transaction closing........................................................................................................... 32

TECHNOLOGICAL SEQUENCES GROUP............................................................................................... 33[ SHORTSTS ] Device status (short)..................................................................................................... 33[ MEMSIZE ] Memory size readout....................................................................................................... 33[ READMEM ] Memory contents readout.............................................................................................. 33[ FMREAD] Technological area of fiscal memory readout..................................................................... 34[ FMWRITE] Technological area of fiscal memory write...................................................................... 34[ FMCHECK ] Fiscal memory test......................................................................................................... 34[ IDENTITY ] Device identification......................................................................................................... 35[ HWTEST ] Hardware tests................................................................................................................. 35[ HWINFO ] Hardware information readout........................................................................................... 37

ERROR MESSAGES LIST........................................................................................................................ 39

page 3 of 40


4/40


HISTORY OF CHANGESDate Revision Author Changes description

02.02.05 1.19p First published version

page 4 of 40


5/40


INTRODUCTION

This document describes communication interface of the Serbian version of the printer Thermal Usingdescribed below commands it is possible to make transaction (sales), program, read and delete PLU (items)

base records, print reports, set printer parameters, program graphics, control electronic circuitry, monitorprinter status, perform technological tests of the printer.Some commands execution requires fulfilment of certain conditions, e.g. it is necessary to perform dailyreport before using commands enabling PLU base or tax rates (if sales was done since last daily report wasperformed). Some commands are allowed in training mode only, others are functionally restricted dependingon the printer working mode (e.g. technological tests can be performed in training mode only).

page 5 of 40


6/40


CONTROL CODES

During command execution, the device does not analyse received commands. They are stored in the inputbuffer (until it is full) and executed after the previous command is finished. The device can only answer to

single byte status queries (ENQ,DLE). Status answer may be send with delay.

There are 4 control codes in the printer:

BEL (07h) -sound signal.

CAN (18h) - exit from the state of waiting for user reaction (command cancellation).

Action is always negative (i.e. does not confirm the operation) It also results in stopping long operation, exitfrom menu to on-line mode, exit from edition field, etc. Also stops analysing of control command.

ENQ (05h) - operation status query.

As the answer to the operation status query (ENQ), the printer sends one byte with the following format:

bit 7 6 5 4 3 2 1 0

meaning 1 1 USR BUSY CACHE FLASH NF_DOC TRANS

DLE (10h) - device status query.

Enables to read the device status e.g. paper end or erroneous situations.As the answer to the device status query (DLE), the printer sends one byte with the following format:

bit 7 6 5 4 3 2 1 0

meaning 1 0 FSK RD_ONLY FM_ERR BAT PRN ERR

Abbreviations meaning:

BAT operation from battery power supplyPRN lever up, printing mechanism error or paper endFM_ERR fiscal memory fatal errorFSK system status (the device in fiscal or non-fiscal mode)USR waiting for user reaction mode (service jumper short, confirmation, etc.). USR may be

resulted of waiting for operation confirmation using keyboard or waiting for reaction on error(printer error, fatal error, others).

TRANS transaction mode (transaction started)

BUSY device during time-consuming operation, e.g. during printingRD_ONLY read only modeCACHE Flash memory contents updating (Cache memory contents copying to Flash)ERR last command errorFLASH defragmentation of Flash memory in progressNF_DOC non-fiscal document open (selective PLU report, user defined text)

page 6 of 40


7/40


COMMUNICATION

RS-232Baud rate 2400, 4800, 9600 or 19200

Data bits 8Stop bits 1Parity none

Flow control by XON/XOFF

Communication should be synchronous, i.e. each command sent from PC is followed by printer response.The response may be one of the two types:

a) standard sequence containing the status of the operation execution: operation successful or error number

b) response specific to the command sent, containing specified parameters.

The parameters in sequences being sent can be:

- byte (^) - hex 1F- text (*) - hex 0A- numerical (@) - hex 09

COMMANDS SYNTAX

Commands syntax is as follows:First prefix is present (ESC P), then two bytes describing command identifier and command specificparameters. The parameters number is described below, in each command description. The parametersmust be separated by appropriate tags (see below) - one of: '*' or '^' or '@'. Sequences are completed withtwo hexadecimal characters containing checksum and ESC \ characters.

Example:

START COMMAND BODY CHECKSUM END

ESC P 2 bytes ASCII codes 2 bytes ESC \

$l 1111* BDh

1Bh, 50h 24h, 6Ch 31h, 31h, 31h, 31h, 0Ah 42h, 44h 1Bh, 5Ch

Algorithm of checksum calculation

The sequences sent are supplemented with two characters HEX digits (characters from the set: 0..9,A..F), which represent in hexadecimal notation the value of checksum byte calculated for the wholesequence in the following way:

- Initial value of checksum: := 255 (FFh);

- For each character following ESC P, checksum is calculated in the following way: := XOR XOR XOR ...;

until the last character in the sequence (except checksum characters and ESC \ 'end').

- This checksum is translated into two HEX digits in ASCII code and added to the sequence together withESC \ end.

Example of checksum calculation of#hPosnet* sequence calculation:

checksum=FFh XOR '#' XOR 'h' XOR 'P' XOR 'o' XOR 's' XOR 'n' XOR 'e' XOR 't' XOR LF

page 7 of 40


8/40


so, hexadecimally:

checksum=FFh XOR 23h XOR 68h XOR 50h XOR 6Fh XOR 73h XOR 6Eh XOR 65h XOR 74h XOR 0AhXORchecksum=8Dh

Standard response

Standard response after the sequence received is the following:

#Z* ^

where, is identifier of the sequence after which the standard response is sent. The identifier isalways twobyte, e.g. #z, #t, #x, *l etc.

describes error number; when the command is executed properly, its value is 0.

Error messages list is enclosed at the end of this manual.

Zero totalizers

Totalizers are equal to zero when receipts counter and turnover counters for each tax rate are equal to zero.

page 8 of 40


9/40


DESCRIPTION OF SEQUENCES IN PRINTER THERMAL SR

BASIC SEQUENCES GROUP:

All typical (basic) commands which can be called by user in fiscal and non-fiscal mode belong to this group.These sequences basically are used for the device configuration, header, advertising text and graphicsprogramming, tax rates change, display control, reports printing, the device identification and informationread from the printer. All sequences applied to fiscal memory write are connected with giving current date andtime or confirmation using keyboard is required.

[ OPNDRW ] Drawer openingSyntax:

*w

Response:Standard

Description:This command results with the drawer opening.The printer sends to the drawer electrical pulse of specified duration, which opens the drawer.

Remarks:Using [GETOPT] seguence enables user to set the pulse duration time

[ LINEFEED ] Paper feedSyntax:

#a^^

- number of lines for feed in original mechanism

- number of lines for feed in journal mechanism

Response:Standard

Description:This sequence enables paper feed from 1 to 8 lines. Parameters for Original and Journal are givenseparately.

Remarks:When value 0 is sent as a parameter - it does not result with paper feed.When value from range 9-255 sent as parameter - error 4 message is generated.

[ GETCLK ] Clock readSyntax:$c

Response:$C^^^^^

- current year - current month - current day - current hour - current minute

Description:This sequence results with current date read from the printer (in short format).

page 9 of 40


10/40


Year is given in short format, i.e. two last digits.

Remarks:For example the response: 10^11^24^12^50^ means 24 November 2010 year, time: 12:50

[ DSTSET ] Time change (winter/summer).Syntax:

#t^ - parameter describing time change direction

0 - means change by -1 hour1 - means change by +1 hour

Response:Standard

Description:This sequence changes time by +1 or -1 hour. Changes can be done interchangeably only.In case when +1 hour change was done, next use of this sequence can only change time by -1 hour. In casewhen -1 hour change was done, next use of this sequence can only change time by +1 hour.

Remarks:This operation is not allowed during transaction.Time change is possible only in the situation, when the last printout before this operation was daily report.Attempt of next time change results with message: 'date and time was already changed'.

[ GETVAT ] VAT (tax) rates readoutSyntax:

$v

Response:$V@@@@@ @@@

@

... - VAT rates values

Description:The sequence returns current value of all VAT rates.Decimal point is omitted. The two last digits of returned values represent fractional value of particular rates.10100 - represents inactive VAT rate.

Remarks:e.g. Returned value 1500 represents 15% VAT rate.

[ SETVAT ] VAT rates programmingSyntax:

#v^^^^^ @@@@@

@@@@

... - VAT rates values (0% - 99,99%). - current year - current month - current day - current hour - current minute

Response:Standard

Description:

page 10 of 40


11/40


The sequence programs VAT rates, then the progammed rates values are printed.Decimal point is omitted. The two last digits of returned values represent fractional value of particular rates.Sent 10100 value represents inactive VAT rate.Particular VAT rates are assigned do the digits: 0 ... 8.

Remarks:e.g. When value 2200 sent, 22% VAT rate is programmed.This operation is not allowed during transaction.VAT rates programming is possible only when totalizers are equal to zero.In non-fiscal mode programmed VAT rates are not written into fiscal memory.Maximum rates changes number in fiscal mode is equal to 30.Header programmed is a condition required for VAT rates programming/change.It is not necessary to confirm date using keyboard. Current date needs to be sent as a parameter.In the fiscal mode programmed VAT rates are written to fiscal memory (they are not removed when RAMclear occurs).

[ GETHDR ] Header readoutSyntax:

$h

Response:$H**** *

^^ ^^^

... Individual header lines (max.5)... Flags describing font size

0 - normal font size1 - double font size

Description:The sequence returns header lines programmed in the printer.

Only programmed lines are returned (together with assigned flags values).

Remarks:Empty lines at the beginning and at the end are omitted, and also starting and ending 'space' characters foreach line.

[ SETHDR ] Header programmingSyntax:

#h*****^^^^^

... Individual header lines... flags specifying font size for each header line


Response:Standard

Description:The sequence programs header lines in the printer memory.Empty lines at the beginning and at the end or containing space characters only are ignored. In particularlines, space characters at the beginning and at the end of line are removed.All the header lines are automatically centered.Header programming or change is possible only when totalizers are equal to zero.Maximum character number in each header line is equal to 40 (normal font size) or 20 (double font size).

page 11 of 40


12/40


Remarks:Font size flags statement is not necessary. If they are given, their number must be equal to the number ofheader lines being programmed.Default font is normal size font.When double font size chosen, remember about maximum character number (20) for this line.

Each header line font size is described by separate flag.This operation is not possible during transaction.

[ SETADV ] Advertising text programmingSyntax:

#i*******^^^^^^^ ^

... Individual lines of advertising text... flags specifying font size for each line


Response:Standard.

Description:The sequence programs advertising text lines to be printed on receipts.Empty lines at the beginning and at the end or containing space characters only are ignored. In particularlines, space characters at the beginning and at the end of line are removed.All the lines are automatically centered.Maximum character number in each header line is equal to 40 (normal font size) or 20 (double font size).No printout occurs after advertising text programming.

Remarks:

Font size flags statement is not necessary. If they are given, their number must be equal to the number oflines being programmed.Default font is normal size font.When double font size chosen, remember about maximum character number (20) for this line.Each header line font size is described by separate flag.Printing of programmed advertising text is possible using ADV_BMP command.

[ GETADV ] Advertising text readoutSyntax:

$i

Response:$I******

*^^^^^^^ ^

... Individual lines of advertising text... Flags describing font size in particular lines


Description:The sequence returns advertising text lines programmed in the printer.Only programmed lines are returned (together with assigned flags values).

Remarks:

Empty lines at the beginning and at the end are omitted, and also starting and ending 'space' characters foreach line.

page 12 of 40


13/40


[ DAYREP ] Daily reportSyntax:

#z^^^^^

^^^^^ - current date (year, month, day, hour, minute)or:

#z

Response:Standard

Description:The sequence performs and prints daily report and if the device is fiscalized, a record in fiscal memory iswritten. After printing of this report, statistics counters are cleared (totalizers become equal to zero).It is possible to give as parameter current date. It is also possible to send the command without parameters,in this case User must confirm date using keyboard. The difference between the time given and in the devicemust not be greater than +/- 1 minute.

Remarks:When the sequence is sent without date parameter, it is necessary to confirm the date using keyboard.It is necessary that header and VAT (tax) rates are programmed in the printer to perform this report (andprint).Maximum number, of available in the printer daily reports to perform, is 1801, however, daily report number 1is printed automatically during fiscalization. After 1801st daily report is performed, printer goes into READONLY STATE, and no further writing into fiscal memory is possible.This operation is not allowed during transaction.

[ PERREP ] Periodical reportSyntax:

#o^^^^^^^

flag specifying report type:0- fiscal1- non-fiscal

^^ starting date^^ ending date

Response:Standard

Description:The sequence performs and prints periodical report with the data taken from within the specified period. It isavailable in fiscal mode only. The periodical report contains records written in fiscal memory within specified

period (daily reports, RAM clears information, VAT rates programming/changes).

Remarks:It is necessary that header is programmed in the printer to perform this report (and print).Proper dates format is required (first starting date, then ending date).This operation is not allowed during transaction.If there are no records within specified period, an error message is reported.

[ INTERSEC ] Status intersection (fiscal report).Syntax:

#w

Response:

Standard

page 13 of 40


14/40


Description:The sequence performs and prints Status intersection report.The report prints daily totalizers, turnover for each of payment forms - the report does not clear totalizers orstatistics.

Remarks:This operation is not allowed during transaction.

[ GETSTS ] Printer statusSyntax:

$s

Response:$S^^^^^^

***

Device type: 0 - ECR; 1 - Bingo, 2 - Thermal Is the device fiscalized: 0 - NO, 1 - YES, Totalizers:

0 - not equal to zero,1 - equal to zero

, , Date of fiscalization PIB IBFM Firmware version

Description:The sequence returns the device information such as: device type, totalizers status, date of fiscalization, PIB,IBFM, firmware version.If IBFM is not set, '?' signs string is returned.If the device is in non-fiscal mode, PIB position returned is empty, date of fiscalization is not specified.

Remarks:The sequence is used for identifying of the device and its status readout.If the totalizers are not equal to zero, some operations cannot be executed (such as time change, PLU baserecord modification/deletion, header or VAT rates programming, fiscalization).Non-zero totalizers value means that there was sales (or receipt counter has increased) since the last dailyreport performed.

[ GETTOT ] Totalizers and counters readoutSyntax:

$t

Response:

$T@@@@@@@@@@ @@@

... current totalizers of particular VAT rates fiscal documents (fiscal receipts) counter since fiscalization fiscal documents (fiscal receipts) counter since last daily report non-fiscal documents counter since fiscalization (when printer is in

non-fiscal mode - since last RAM clear) non-fiscal documents counter since last daily report

Description:The sequence returns current totalizers and counters values.

page 14 of 40


15/40


Remarks:If fiscal documents counter (since last daily report) is not equal to zero, it is not possible to change PLU baserecords or change time.If fiscal documents counter (since last daily report) and current totalizers of particular VAT rates are not equalto zero, it is not possible to change VAT rates or header.

Remember that time can be changed once only between daily reports (and directly after daily report only).

[ BMPDATA ] Graphics programmingSyntax:

#n^*

line number (range 0-155) graphics in hexadecimal (ASCII) format

Response:Standard

Description:

The sequence transfers particular graphics lines contents from PC to the printer.Each graphics line size must be exactly 45 bytes. Each of 45 bytes is represented by 2-digit hexadecimalnumber (as two ASCII characters).After the needed number of graphics lines is sent, they must be confirmed using BMPSET command.

Remarks:None

[ BMPDATAGET ] Graphics line readoutSyntax:

$n^

line number (range 0-155)

Response:$N^*

graphics in hexadecimal (ASCII) format

Description:The sequence returns particular graphics line programmed in the printer.Each graphics line size must be exactly 45 bytes. Each of 45 bytes is represented by 2-digit hexadecimalnumber (as two ASCII characters).Particular graphics line contents can be changed using BMPDATA command.

Remarks:

None

[ BMPSET ] Sent graphics confirmationSyntax:

#g^^^ sent lines number (range 13 - 156) graphics line size (45 bytes) graphics identifier (0 - zero)

Response:Standard

page 15 of 40


16/40


Description:The sequence confirms graphics sent before from PC to the printer.The graphics is sent from PC to the printer using BMPDATA command (pay attention to the number of sentgraphics lines).The programmed graphics is present in the receipts under the header.

Graphics printing can be activated using SETOPT command.

Remarks:The programmed graphics can be checked using ADV_BMP command.Particular grapnics lines programmed in the printer can be read using BMPDATAGET command.

[ BMPGET ] Graphics settings readoutSyntax:

$g

Response:$G^^^

sent lines number (range 13 - 156)

graphics line size (45 bytes) graphics identifier (0 - zero)

Description:The sequence returns parameters of graphics programmed in the printer.Particular grapnics lines programmed in the printer can be read using BMPDATAGET command.

Remarks:If the graphics was not programmed using BMPSET command, returned parameter is 0.

[ ADV_BMP ] Advertising graphics and text test printoutSyntax:

#b

Response:Standard

Description:The sequence enables verification of advertising graphics and text sent before from PC to the printer.The graphics programmed (BMPSET) and advertising text programmed (SETADV) are printed.

Remarks:None

[ GETOPT ] Configuration options readoutSyntax:

$y^

0 - firmware version$y0^Response:$Y0^*

1 activation of graphics on receipts$y1^Response:$Y1^

0 graphics off

1 graphics on

page 16 of 40


17/40


2 activation of advertising text on receipts$y2^^

0 advertising text off1 advertising text on

Response:$Y2^


3 - paper sensitivity$y3^Response:$Y3^

- read paper sensitivity value set, values from range 0 - 3,where: 0 - type A, 1 - type B, 2 - type C, 3 - type D

4 display control

$y4^Response:$Y4^^^

value of display brightness (range 0 - 15) value of display contrast (range 0 - 31) backlight mode

0 - with backlight (only when external charger connected) - default value1 - with backlight (always)2 - without backlight

5 - drawer opening pulse length$y5^Response:

$Y5^ pulse duration multiplier (range 1-64)

6 reaction on errors$y6^Response:$Y6^

0 - PC (default value)1 - user

Description:The sequences return the values of the options contained in printer configuration registers.


[ SETOPT ] Configuration options programmingSyntax:

#y - setting default optionsor:

#y^

Response:Standard

page 17 of 40


18/40


1 activation of graphics on receipts#y1^^

0 graphics off1 graphics on

2 activation of advertising text on receipts#y2^^


Response:#Y2^


3 - paper sensitivity#y3^^

-paper sensitivity type, values from range 0 - 3,

where: 0 - type A, 1 - type B (default value), 2 - type C, 3 - type D

4 - display control#Y4^^^

value of display brightness (range 0 - 15), default value: 8 value of display contrast (range 0 - 31), default value: 13 backlight mode

0 - with backlight (only when external charger connected) - default value1 - with backlight (always)2 - without backlight

5 - drawer opening pulse length#y5^^

pulse duration multiplier (range 0-31)Default value is 2. 1 unit corresponds to the pulse duration 10ms (e.g. value 10 set meanspulse duration 100ms). User must set this value to obtain proper cash drawer openingeach time (ATTENTION: please note, that longer pulse set results with increased powerconsumption from internal battery).

6 reaction on errors#y6^^

0 - PC (default value)1 - user

Description:

The sequences set the values of the options in printer configuration registers.If #y command sent without parameters, default values are set.

Remarks:This operation is not allowed during transaction except commands: #y3, #y4, #y5.

[ DOCLINE ] Non-fiscal printout lineSyntax:

#l^*

flag describing the line position on the printout:0 - left side alignment (default)1 - text centered

2 - right side alignment4 - double font

page 18 of 40


19/40


string any text up to 36 characters or 18 (double font size)

Response:

Standard

Description:This sequence enables any text printout. parameter describes the way of the line printing. It ispossible to use sum of flags of the parameter .Each non-fiscal started document must be ended by DOCEND command.

Remarks:- e.g. #l6^Printout1* sequence results with printing of text 'Printout1' aligned to the right side with double fontcharacters (2+4).

[ DOCEND ] Non-fiscal printout endingSyntax:

#e

Response:

Standard

Description:The sequence ends non-fiscal printouts started with DOCLINE or PLUREPLINE commands. Appropriatefooter is added to the printout.

Remarks:None

[ DSPOUT ] Display control

Syntax: #q^* - display text line number

0 upper text line1 lower text line

- text sent to customer display (string max. 20 characters)

or:#q2^ - current date and time are sent to display

Response:

Standard

Description:The sequence sends string to given text line of the customer display. Maximum 20 characters can be sent.Because in serbian language some special (diacritical) characters occur, on the display (latin alphabet usedon the display) they are represented by two characters in latin alphabet. Hence the text sent may beshortened when these double characters occur (text will be limited to 20 characters).When #q2^ sequence is sent, date and time (with update) is displayed in the upper display text line.Date is displayed until the transaction is started.

Remarks:When sent parameter is empty, the display text line is cleared (blank).When text line is sent, and then date and time, on the display only date and time will be displayed. When dateand time is sent first, then a text line, the display is cleared, and then the text line is displayed.This operation is not allowed during transaction and when sequences DOCLINE and PLUREPLINE werestarted.

page 19 of 40


20/40


[ FMINFO ] Fiscal memory information readoutSyntax:

$j

Response:

$J @@@@@@

- Total number of allowed/available daily reports recordsin the printer - Number of daily reports already performed - Total number of allowed/available tax rates changes records in the printer - Number of tax rates changes already performed - Total number of allowed/available RAM clear records in the printer - Number of RAM clears that already occured

Description:The sequence returns information about fiscal memory contents: daily reports performed, tax rates changes,RAM clears.

Remarks:When the printer is in non-fiscal mode, parameters , and returned are equal to zero.

page 20 of 40


21/40


PLU BASE MAINTENANCE SEQUENCES GROUP

PLU base maintenance commands are used for programming or deletion of records in PLU base, search ofinformation contained in PLU base records, or printing of PLU reports (of reading and clearing type).Particular PLU record is uniquely identified by PLU (item) name.

PLU record contains the following information about the item:

- name - 36 bytes- tax rate - 1 byte- measurement unit - 1 byte- unit price - 4 bytes- quantity of items sold - 4 bytes- value of items sold - 4 bytes

[ PLUADD ] Record adding to PLU base (items)Syntax:

#r*@^^

PLU name (max. 36 characters) item (article) price (max. value 999999,99) 0...8 - VAT (tax) rate measurement unit

0 - none1 - g (gram)2 - kg (kilogram)3 - t (ton)4 - l (liter)5 - m (meter)6 - m2 (square meter)7 - m3 (cubic meter)

Response:Standard

Description:The sequence adds new item record to PLU base (in the printer memory).Decimal point is not used for non-integer values. The two last digits in the price value represent the decimalfractional part.Item name can be maximum 36 characters long, using Latin or Cyrillic alphabet. The name is not allowed tobe left empty or containing space characters only.In case when PLU base clear occurs, item named 'Artikal1' will be automatically programmed, with the firstactive tax rate (or 'A', if there is no active tax rates), with unit price 0,00 and with measurement unit 'none'.

Remarks:- The item name must be unique. During names comparison, all space characters are removed from thename, also starting and ending space characters.- When programming PLU base, information about it is not printed.- Particular VAT rates are assigned to the digits 0 ... 8.- Items programming can also be done during transaction.- During sales (using TRSLINE command) there is possibility of automatic item programming.- All programmed items information can be printed using PLUREPORT command.- Remember that PLU base must contain at least one record, hence the last record remaining in PLU basecannot be deleted.

Examples:#rlettuce*150@0^2^#rcarrot*9999@8^3^

page 21 of 40


22/40


[ PLUDEL ] Record deletion from PLU base (items)Syntax:

#d* PLU (item) name

Response:Standard

Description:The sequence deletes item record from PLU base (in the printer memory).

Remarks:- It is not allowed to delete PLU base records when totalizers and statistics are not equal to zero.- This operation is not allowed during transaction.- It is not allowed to delete the last existing record from PLU base. An error message occurs when trying todelete the last record existing in PLU base.

[ PLUDELALL ] Deletion of all records from PLU base (items)Syntax:

%acalled without parameters

Response:Standard

Description:The sequence deletes all items records from PLU base (in the printer memory), and then programs one itemwhich was the first one in the base (before deletion), its statistics are cleared.

Remarks:- It is not allowed to delete PLU base records when totalizers are not equal to zero (Daily Report must be

performed first).- This operation is not allowed during transaction.- This operation is not allowed when the printer is in 'Read Only' mode.

[ PLUGET ] PLU base record information readoutSyntax:

$r* PLU (item) name

Response:$R*@^^@@

PLU (item) name

price VAT rate measurement unit sold items quantity turnover (value of sold items: price * quantity)

Description:This sequence returns information about specified PLU record.Decimal point is not used for non-integer values. The two last digits in the price value and three last digit inthe quantity value represent the decimal fractional part.

Remarks:- PLU base information (e.g. base capacity, used records number) can be obtained using PLUINFO

sequence.- Particular VAT rates are assigned to the digits 0 ... 8.

page 22 of 40


23/40


[ PLUFIND ] PLU base record searchSyntax:

$o*^ PLU (item) name (can be initial part of the name) mode

1 equal2 - previous record than given4 - next record after given

Response:$o*@^^@@

PLU (item) name price VAT rate measurement unit sold items quantity

turnover (value of sold items: price * quantity)

Description:This sequence searches for and returns information about specified PLU record.The two last digits in the price value and three last digits in the quantity value represent the decimal fractionalpart.It is possible to use sum of flags of the parameter (except value 6 - previous and next together).

Remarks:- If parameter is equal to 3, the database record is found with the name given or previous one- Example of flags sum: $oJUICE*4^ returns information about the first item in data base with name startingJUICE.- It is possible to send the item name incomplete (beginning) with parameter equal to 2 or 4. In this

case, information about previous or next record in PLU base containing this beginning string will be returned.- If parameter is equal to 1, the database record is found with the name exactly given. If suchrecord does not exist, error message appears.- When is equal to 5, it means that searched is record equal or next according to the name given.- Sequence: $oJUICE*5^ returns information about the item with name JUICE (if exists) or (if exact namegiven does not exist) the next record in PLU database with the name starting with the string (e.g. JUICE1).- Empty name and mode 'next' entered result in finding the first record in PLU base.- Empty name and mode 'previous' entered result in finding the last record in PLU base.- If the name according to the and parameters given does not exist in the PLU base,appropriate error code is returned.

[ PLUINFO ] PLU base information readoutSyntax:

$d

Response:$D@@^

- PLU base capacity - programmed (used) PLU base records number - maximum length of PLU (item) name

Description:This sequence returns the following information about PLU base: base capacity, used records number,maximum PLU (item) name length (when programming).

Remarks:None

page 23 of 40


24/40


[ PLUREPORT ] PLU reportSyntax:

#p^^^^

1 - full

0 - short 1 - clearing0 - reading

1 - sold only0 - all

VAT rate according to which the report is performed (range 0..8)9 - for all rates

Response:Standard

Description:The sequence performs and prints PLU report. Full PLU report contains additional information about quantityand amount of sold items.After the clearing PLU report is performed, it is possible to delete PLU base records using PLUDELsequence.

Remarks:- Full clearing PLU report clears counters of all specified records.- It is not possible to perform short clearing PLU report.- This operation is not allowed during transaction.

[ PLUREPLINE ] Selective PLU report lineSyntax:

#p^^*1 - full

0 - short 1 - clearing0 - reading

PLU (item) name

Response:

Standard

Description:The sequence enables selection of records from PLU (items) base to be printed on PLU report.The first line, starting the PLU report, executes header printing.All following lines must have the same flags settings (flags and ).The report is finished by sending DOCEND command.After the clearing PLU report is performed, it is possible to delete PLU base records using PLUDELsequence.

Remarks:- It is not possible to perform short clearing PLU report.- This operation is not allowed during transaction.

[ DEFRAG] PLU base defragmentationSyntax:

#j^

0 - fast defragmentation (1 sector)1 - full defragmentation (all sectors)

page 24 of 40


25/40


Response:Standard.

Description:The sequence removes from FLASH memory deleted records space. It means that the space in sectors is

put in order, the sectors contain programmed records (without 'holes') and only the last sector is left withempty records.When large number of records is contained in PLU base, this operation may take several minutes.

Remarks:This operation is recommended in the systems, where often operations of records programming and deletionare performed in PLU base.This operation is not allowed during transaction.

page 25 of 40


26/40


SERVICE SEQUENCES GROUP

Service sequences are dedicated for use by servicemen. Fiscal module ID (IBFM) programming orfiscalization operations can be done once only. During clock setting or fiscalization, service jumper short mustbe executed.

[ SETCLK ] Clock settingSyntax:

#c^^^^^ - year (00-99) - month (1-12) - day (1-31) - hour (0-23) - minute (0-59)

Response:Standard

Description:The sequence changes current date and time settings.In fiscal mode, new entered time must not be earlier than the last writing to the fiscal memory time.After the sequence is sent, the device waits for the service jumper short.After the time setting is changed, appropriate printout is printed.

Remarks:- This operation is not allowed during transaction.- Allowed date range is from year 2000 to year 2099.- The parameter describing year is represented by the two last digits of the year, e.g.- The sequence #c10^11^24^12^50^ sets the time: 24 November 2010 year, 12:50 hour.

[ SETFMID ] Fiscal module ID (IBFM) programmingSyntax:

#u* fiscal module ID (IBFM) number in format: CCDDDDDD

C - letters (Cyrillic alphabet)D - digits

Response:Standard

Description:The sequence enables fiscal module ID (IBFM) number programming into fiscal memory. After the sequenceis sent, the transmitted number is printed (for verification). The number is written into the fiscal memory afterits confirmation using keyboard.

Remarks:- This operation is not allowed during transaction.- Until the fiscal module ID (IBFM) number is not programmed in the fiscal memory, the IBFM number area ofthe header is printed as '?' characters string on the printouts.

[ CRFSK ] Printer fiscalizationSyntax:

#k^^^^^*

date and time of fiscalization tax payer ID (PIB) number (string: 9-16 characters)

page 26 of 40


27/40


Response:Standard

Description:The sequence enables the printer fiscalization. After the sequence is sent, printer displays message, that

service jumper must be ON (shorted). After this is done, the data transmitted to the printer is printed (forverification). Date and time confirmation message is displayed.When date and time is not confirmed, printer exits fiscalization procedure.After date and time confirmation, printer goes into fiscal mode.During fiscalization necessary data is written into the fiscal memory (PIB number, tax rates, date and time offiscalization). Documents counters are cleared, tax rates report is printed, and 'zero' daily report is performed.

Remarks:- PIB number should contain 9-16 digits, however formatting of this number is not necessary. Only length ofthe number is verified by the printer.- All the sequence parameters described above are obligatory.

For fiscalization performing, the following conditions must be satisfied:

- printer is not fiscalized, with printer ID programmed- production tests performed (durability test and final production test)- totalizers equal to zero- header programmed- at least one tax rate programmed

page 27 of 40


28/40


TRANSACTION SEQUENCES GROUP

The sequences described in this group enable transaction (sales) realization in fiscal mode.The below sequences work also before printer fiscalization (in non-fiscaal mode), however in this case theprinter does not print any documents - operations are only visible on the display.

[ TRSHDR ] Transaction startSyntax:

*t**

printer number (up to 3 characters) - sales stand number - optional parameter cashier name (up to 16 characters, using Latin or Cyrillic alphabet) - optional

parameteror

*t

Response:

Standard

Description:The sequence starts transaction (sales) mode.Transaction can be ended using TRSEND command.After this command sent, it is possible to cancel started transaction using TRSEXIT command (on conditionthat TRSLINE command was not used after TRSHDR command).

Remarks:This operation is not allowed during already started transaction.Header, graphics, advertising text and printer data (cashier name and sales stand number) are printed afterthe first transaction line is received.After the first receipt line is printed, the transaction cannot be canceled. It can be finished using TRSENDcommand.

It is possible to use this command with two parameters or with no parameters.Parameters sent can be also empty (e.g. when it is not necessary to specify sales stand number).When the sequence without parameters is sent, or both parameters are empty, the line describing cashierand stand number is not printed on the receipt.If one of parameters sent is empty, only a part of line containing valid parameter is printed.

Example correct sequences:*t*t001*John Smith**t *Smith**t100* *

[ TRSLINE ] Transaction line

Syntax:

*l*@@

PLU (item) name quantity (the three last digits represent decimal fraction part) unit price (the two last digits represent decimal fraction part)

or

*l*@@^^

PLU (item) name (max. 36 characters) unit price

quantity (the three last digits represent decimal fraction part) 0...8 - VAT rate

page 28 of 40


29/40


measurement unit0 - none1 - g (gram)2 - kg (kilogram)3 - t (ton)

4 - l (liter)5 - m (meter)6 - m2 (square meter)7 - m3 (cubic meter)

Response:Standard

Description:The sequence specifies the item being sold. After the sequence is sent, sales line is printed on the receipt.Each use of this sequence results with printing the line containing sold item name, quantity, unit price, solditems value for this line (price * quantity) and item tax rate.When the sequence is sent with all the parameters including measurement unit and tax rate, the item isautomatically programmed into PLU base (if it does not exist) first, and then sales is performed.If the sequence contains existing PLU, but the parameters or are different than in the PLUbase - error message is returned.Also, when the sequence is sent without the parameters and , and the item does not existin the PLU base - error message is returned.If parameter sent is different than in the PLU base, the price in the PLU base is changed to thevalue sent.

Remarks:The parameters and can be sent with values equal to zero. In this case, price valueis taken from PLU base, and quantity is equal to 1.If the parameter value sent is equal to 1000 (i.e 1,000 piece), then information about itemquantity in the receipt line is not printed.Maximum transaction lines number on single receipt is equal to 500.

During transaction, current sales line value (together with sold item name) is displayed.

parameter format is: maximum 5 digits for integers (including three '0' digits representing zerovalue fractional part) or maximum 4 digits for numbers with fraction (including three digits representingdecimal fractional part). It means in practice that quantity range for integers is 1 ... 99, for fractional numbersrange is 0,001 ... 9,999.Example correct values sent:90000 - 90 pcs9999 - 9,999 pcs1 - 0,001 pcs

parameter format is maximum 6 digits (integer value) + 2 digits (decimal fraction).Example correct values sent:99999999 - 999 999,99 Dinars1 - 0,01 Dinars

Examples of correct sales lines sent:

*lgarlic*100@1000@ if item 'garlic' exists in PLU database, sold: garlic, 1 Dinar unit price, 1 piece*lcarrot*9000@2500@ if item 'carrot' exists in PLU database, sold: carrot, 90 Dinars unit price, 2,5 pcs (ormeasurement units in PLU base)*lbean*300@500@0^2^ programmed into PLU base and sold: bean, 3 Dinars unit price, 0,5kg (VAT rate A,measurement unit - kg). If item exists in PLU base with different VAT rate or measurement unit - errormessage is returned.*lbean*0@2000@ sold: bean, price taken from PLU base, 2 kg (2 pcs of measurement units in PLU base)*lbean*500@0@ sold: bean with new price 5 Dinars unit price, 1 kg (1 piece taken automatically, price inPLU base record changed into new value)

*llettuce*300@1000@0^0^ programmed into PLU base and sold: lettuce, 3 Dinars unit price, measurement

page 29 of 40


30/40


unit - none (VAT rate A)

When TRSLINE sequence is sent with the unit price different than programmed in PLU base, the item(s) aresold in this line with the new unit price, the price sent is programmed into PLU base record and it is validwhen next time the sequence is used.

[ TRSLINEVOID ] Transaction line stornoSyntax:

*s*@@

PLU (item) name quantity unit price

Response:Standard

Description:The sequence enables deletion (storno) specified transaction line from the receipt.

Remarks:It is allowed to delete (storno) integer quantities of items within the transaction line or the whole transactionline (even if the quantity of the line contains fractional quantity.In the parameter the three last digits represent decimal fraction part.In the parameter the two last digits represent decimal fraction part.

parameter format is: maximum 5 digits for integers (including three '0' digits representing zerovalue fractional part) or maximum 4 digits for numbers with fraction (including three digits representingdecimal fractional part). It means in practice that quantity range for integers is 1 ... 99, for fractional numbersrange is 0,001 ... 9,999. parameter format is maximum 6 digits (integer value) + 2 digits (decimal fraction).

Deletion (storno) of items in integer quantities result in:- deletion of the whole lines (sales records) from the transaction buffer (sold 2 pcs and storno 2 pcs),or,- in the sales record of transaction buffer the quantity sold is decreased (sold 5 pcs and storno 2 pcs),or,- in several sales records of transaction buffer the quantity sold is decreased (sold 2+1+1 pcs and storno 3pcs). In this case the three transaction lines for the same item are stored in the transaction bufferseparately. During deletion (storno) the three transaction lines are analysed, and removed completely insuccession as necessary, or the quantity sold is decreased.

Examples:sales: *lTomato*1@5055@

storno: *sTomato*1@5055@sales: *lcarrot*999@3@1^1^storno: *scarrot*999@2@1^1^

[ TRSINFO ] Transaction information readoutSyntax:

*i

Response:*I^@@^

1 - the device is in transaction mode0 - the device is out of transaction mode

transaction lines number (storno decreases the lines number respectively) subtotal value (current transaction value)

page 30 of 40


31/40


1 - receipt printing is started0 - receipt printing is not started

Description:The sequence returns current transaction information and the current printer state.

The values returned are in the format consistent to the respective numbers format in the TRSLINE command(decimal point is not present in the values returned).

Remarks:In the transaction buffer, information about particular transaction lines is stored. TRSLINE command addsnext sales record to the buffer. TRSLINEVOID sequence sent results in deletion of one or more salesrecords, or decreasing sold items number in one of sales records.

[ TRSLINEGET ] Line readout from sales bufferSyntax:

*g@

Response:

*G*@@@ - transaction line number in transaction buffer (according to sales and storno run) -name of particular transaction line sold item - price of the sold item - quantity of the sold item - value of the transaction line (price * quantity)

Description:The sequence returns transaction line record from the transaction buffer.Line numbers are from range 1 - 500.

Remarks:Only lines active in the transaction buffer are concerned (after line deletion - storno, the buffer contents are

updated). The number of transaction lines in the transaction buffer can be read using TRSINFO command.

[ TRSEXIT ] Transaction mode exitSyntax:

*x

Response:Standard

Description:This sequence can be used after transaction is started (using TRSLINE or TRSHDR command). It can beused only when there is no sales lines (no sales started) or the transaction subtotal is equal to zero (salesvalue equal to zero, e.g. after sold items deletion - storno). In this case the receipt will be closed with values

equal to zero.

Remarks:None

[ TRSSUB ] Transaction subtotal information readoutSyntax:

*u

Response:*U@

current transaction amount (subtotal)

Description:The sequence returns current transaction amount (subtotal) and the amount is displayed on the printer

page 31 of 40


32/40


display.The subtotal is in the format: maximum 6 digits (integer value) + 2 digits (decimal fraction).

Remarks:None.

[ TRSEND ] Transaction closingSyntax:

*e@@@

amount paid by cash amount paid by card amount paid by cheque

Response:Standard

Description:The sequence closes the transaction, prints the receipt and displays the total receipt amount and change on

the printer display.The amounts are in the format: maximum 6 digits (integer value) + 2 digits (decimal fraction).The transaction must be closed with total amount non-negative.

Remarks:If the amount is paid by card or cheque, the change is not given.It is possible to send the sequence without the parameters, then default payment form is cash. Additionallycorrect sequence formats are: command with one parameter (cash only) or with all parameters (cash, cardand cheque).In case when parameter is equal zero, possible ammount missing to close the transaction is addedand treated as cash payment.

Example sequence formats:

*e - payment done using cash only*e3000@ - payment done using cash only*e2000@500@500@ - payment done using all payment forms*e0@500@0@ - payment done using card only*e0@0@500@ - payment done using cheque only

The change is displayed on the printer display with '-' sign. If the change is equal to zero, just the total amountis displayed.

page 32 of 40


33/40


TECHNOLOGICAL SEQUENCES GROUPThe technological sequences are dedicated to test hardware and software work correctness. The sequencescan also be used for memory contents readout and diagnostics.

[ SHORTSTS ] Device status (short)Syntax:

$e

Response:$E*

- response status for ENQ (2 bytes) - response status for DLE (2 bytes)

Description:The sequence returns current statuses that are returned by and commands.

Remarks:

None

[ MEMSIZE ] Memory size readoutSyntax:

$q^

0 or 4 - program memory1 or 5 - protected memory2 or 6 - fiscal memory3 or 7 - application memory - always 0

Response:$Q^@*

memory size (bytes) ignored parameter (its value is undefined)

Description:The sequence returns the size of particular memory types in the printer.

Remarks:The application memory size returned is always 0.This operation is not allowed during transaction.

[ READMEM ] Memory contents readoutSyntax:

$q^^@

0 - program memory (hexadecimal)1 - protected memory (hexadecimal)2 - fiscal memory (hexadecimal)3 - application memory (hexadecimal)4 - program memory (binary)5 - protected memory (binary)6 - fiscal memory (binary)7 - application memory (binary)

bytes number to be read (1 - 255) reading logical address

page 33 of 40


34/40


Response:$Q^@*

returned contents (hex or bin).

Description:

The sequence returns the contents of particular memory space in the printer. The data format can behexadecimal or binary (chosen by sent parameter).


[ FMREAD] Technological area of fiscal memory readoutSyntax:

$f^^

always value 0 offset (0 - 31)

Response:$F^

read byte value

Description:The sequence returns the contents of the offset given.

Remarks:This operation is not allowed during transaction.The data can be written to fiscal memory area using FMWRITE sequence.

[ FMWRITE] Technological area of fiscal memory writeSyntax:

#f^^^

always value 0 offset (0 - 31) the value to be written (hexadecimal)

Response:Standard

Description:The sequence writes (programs) the value to the offset given.The fiscal memory is EPROM type, hence it is not possible to change bit value from 0 to 1 (value 0x00 cannotbe changed anymore).

Remarks:In the fiscal memory, separated area of 32 bytes is available for various purposes (e.g. it can be used fortechnological tests performed information storage).The data can be read from fiscal memory area using FMREAD sequence.

This operation is not allowed during transaction.

[ FMCHECK ] Fiscal memory testSyntax:

$m@@

test starting address (decimal)

test area length (decimal, from 1 to 32767)

page 34 of 40


35/40


Response:$M^

0 - all bytes in the area tested contain value 0xFF1 - the area tested contains at least one byte containing value different than 0xFF

Description:The sequence tests given area of fiscal memory. Information is returned whether the area is written or not.

Remarks:When the area tested contains bytes 0xFF only (parameter returned VAL=0) it means that the area is empty.This operation is not allowed during transaction.

[ IDENTITY ] Device identificationSyntax:

%s

Response:%S*

BADA for BINGO STD SRBADB for BINGO PLUS SRTADA for PERSONAL SRIADA for THERMAL SR

Description:The sequence returns a string containing the device type information.

Remarks:None

[ HWTEST ] Hardware tests

Syntax:#x1^ - durability test

Response:#Z#x0 - test OK#Z#x11 - test error

Description:The sequence starts durability test. When started for the first time, no additional conditions are required.When started next time(s), service jumper must be shorted.The duration og the full test is about 3.5 hour. When started next time(s), it is possible to set the testparameters such as: time of printout series, quantity of series, quantity of lines, voltage or pseudo-itemsselection for printing, lines delay.The sequence is used during production for defects testing.

This operation is not allowed when the printer is in fiscal mode.

Syntax:#x2^ - keyboard test

Response:#Z#x0 - test OK#Z#x(10 + key_number) - test error

Description:The sequence enables to check whether the printer keyboard works properly.After the command is sent to the printer, the keys 0-3 on the keyboard must be pressed in the appropriateorder (from the left to right side). Pressing YES key (the right side one) ends the test.Keys numbers: 0 - arrow 'down'

1 - arrow 'up'

page 35 of 40


36/40


2 - arrow 'left' (NO - red one)3 - arrow 'right' (YES - blue one)

Syntax:#x3^ - customer display test


Description:The sequence enables to check whether the characters are displayed properly on the printer display.After the command is sent to the printer, sequential characters AAA... ... ZZZ... are displayed on the display.It is necessary to check visually if all the display segments work properly. After the test, any key must bepressed to exit to tests menu.

Syntax:#x5^ - signalling LEDs test


Description:The sequence enables to check whether the signalling LEDs work properly.After the command is sent to the printer, signalling LEDs are turned on sequentially (except EXTERNALPOWER LED). It is necessary to check visually if all the LEDs work properly. After the test, YES key must bepressed.

Syntax:#x6^ - battery test


Description:The sequence enables to check the level of battery discharge.After the command is sent to the printer, user should sequentially connect and disconnect external charger.Information message is displayed on the display, depending whether the charger is connected or not. Alsobattery voltage is displayed (together with maximum and minimum allowed values). After the test, YES keymust be pressed.

Syntax:#x7^ - printing mechanisms sensors test


Description:The sequence enables to check whether the printing mechanisms sensors work properly.After the command is sent to the printer, it prints 'SERWIS' (Cyrillic) text continuously. User should simulatepaper end in the mechanisms and lever up. If the sensors work properly, appropriate messages appear onthe display depending on the particular sensor error. After erroneous situation is removed, printing continues.After the test, YES key must be pressed.

Syntax:#x8^ - printout quality test

page 36 of 40


37/40



Description:

After the command is sent to the printer, particular pattern is printed, based on which it is possible to assessquality of the mechanism printing.

Syntax:#x9^ - drawer test


Description:After the command is sent to the printer, message requesting drawer close is displayed, then confirmationwith YES key, then signal opening the drawer is generated by printer. It is necessary to confirm (with YES

key) when the drawer was open.Syntax:

#x14^ - durability test occurrence check

Response:#Z#x0 - durability test was performed#Z#x11 - durability test was not performed

Description:The command checks if durability test was performed.

Syntax:#x32^ - turning the printer off test


Description:After the command is sent, the printer turns off.

Syntax:#x71^* - RAM clear

ignored parameter

Response:

No response.

Description:This test checks if RAM clearing type 'C' can be done properly.After the sequence is sent, the device is restarted.


[ HWINFO ] Hardware information readoutSyntax:

$x33^ - device version

page 37 of 40


38/40


Response:$X33*

VER - device version

Syntax:

$x34^ - battery voltage readout

Response:$X34*

battery voltage in milivolts (hexadecimal number)

Syntax:$x35^ - bios status

Response:$X35*

-bios status (16-bit hexadecimal number)

Syntax: $x36^ - device type and language version readout

Response:$X36*

- 8-bit hexadecimal number describing device type - 8-bit hexadecimal number describing language version

Description:The sequence returns hardware information.


page 38 of 40


39/40


ERROR MESSAGES LIST

Code Description

1 operation not allowed in fiscal mode

2 checksum error

3 wrong parameters number

4 parameter(s) incorrect value

5 erroneous operation with RTC

6 erroneous operation with fiscal module

7 operation not allowed in non-fiscal mode

8 daily totalizers not equal to zero

9 the device is in read only mode (state)

10 cover open11 printing mechanism lever is up

12 paper end

13 mechanism error

14 mechanism error or Power Fail

15 weak battery

20 PLU item absence (attempt to, search or delete of non-existing item)

30 record statistics not equal to zero

31 attempt to delete the last item (record) in PLU base

32 wrong date, e.g. 31.II.33 date earlier than the last record in fiscal memory

34 printout was already performed after the report (during time change)

35 wrong time change direction ( +/-1 h ) e.g. second change to summer time

42 blockade after fiscal module error

53 PLU statistics overflow

54 incorrect PLU data (tax rate, measurement unit) - during transaction

55 cache space not sufficient enough

56 too many lines on receipt

57 transaction mode on58 transaction mode off

59 receipt closing error

60 amount range exceeded

61 amount too small

62 wrong quantity format

64 totalizers overflow

65 parameters error during storno

70 sales attempt in inactive tax rate

80 incorrect dates or numbers in report range

page 39 of 40


40/40


Code Description

84 no reports within dates range

85 no printer ID number

86 durability test not performed87 final production test not performed

92 date earlier than the last record in fiscal memory (during tax rates programming)

93 attempt to define identical tax rates

94 wrong tax rates (tax rates values programming)

95 tax rates changing limit exceeded

100 no header

101 programming error (empty or too long header)

102 daily report performing error

103 incorrect PIB length110 record adding to database error

112 incorrect item name

113 non-unique item name (programming)

114 incorrect price: zero or too high

115 incorrect measurement unit

116 wrong tax rate (during PLU base programming)

125 record adding to database error (FATAL)

130 wrong line width in bytes

131 incorrect graphics type (wrong parameter during graphics programming)132 incorrect graphics line number

133 wrong line number

134 wrong data length

135 wrong data outside 0-9,A-F

140 the same authorization code

141 wrong authorization code

142 no printer authorization

150 header damaged in RAM

151 configuration data damage152 databases damaged

156 wrong date or confirmation abandon (e.g. before daily report)

250 forbidden in demo mode

254 function forbidden

255 command unrecognized or temporarily unavailable