DIBALCOM

V – 10.00

49-MDIBALCOMEN01
Manual
Table of Content
1. PROGRAM DESCRIPTION ..................................................................................................... 2

2. DATA FILE MANAGEMENT.................................................................................................... 5

2.1. CONTROL FILE (DIBCTRL.TXT) .............................................................................................. 5
2.2. INPUT FILE (TX.TXT)............................................................................................................... 8
2.3. OUTPUT FILE (RX.TXT)........................................................................................................... 8
2.4. COMMAND FILE (CTRL.TXT) ................................................................................................... 8
3. SALES EXPORTATION......................................................................................................... 10
3.1. DIBAL FORMAT (RX.TXT)...................................................................................................... 10
3.2. ALL THE SALES TO A FILE ....................................................................................................... 10
3.3. EXPORTATION OF EACH SALE TO A FILE................................................................................... 11
4. ADSL COMMUNICATIONS ................................................................................................... 14

5. MESSAGE TRANSLATION FROM “A” TO “L” ................................................................... 15

5.1. CONFIGURE THE DIBALCOM IN ORDER TO TRANSLATE THE MESSAGES ...................................... 15
5.2. IMPLEMENTED MESSAGES IN THE DIBALCOM ........................................................................... 15
5.3. FUNCTIONING ........................................................................................................................ 16
6. MESSAGE TRANSLATION FROM “A” TO “K”................................................................... 17
6.1. CONFIGURE THE DIBALCOM IN ORDER TO TRANSLATE THE MESSAGES ...................................... 17
6.2. IMPLEMENTED MESSAGES IN THE DIBALCOM ........................................................................... 17
6.3. FUNCTIONING ........................................................................................................................ 17
7. L SERIES INTEGRATION STEP BY STEP .......................................................................... 18
7.1. DOWNLOAD SALES ................................................................................................................ 18
7.2. INITIALIZATION ....................................................................................................................... 20
7.3. START OF DAY ....................................................................................................................... 22
7.4. END OF DAY .......................................................................................................................... 23
8. K SERIES INTEGRATION STEP BY STEP .......................................................................... 25
8.1. DOWNLOAD SALES ................................................................................................................ 25
8.2. INITIALIZATION ....................................................................................................................... 26
8.3. START OF DAY ....................................................................................................................... 28
8.4. END OF DAY .......................................................................................................................... 30
9. LP/LS INTEGRATION STEP BY STEP................................................................................. 31
9.1. DOWNLOAD SALES ................................................................................................................ 31
9.2. INITIALIZATION ....................................................................................................................... 32
9.3. START OF DAY ...................................................................................................................... 34
9.4. END OF DAY .......................................................................................................................... 35
10. A SERIES’ SCALES COMMUNICATION EXAMPLES......................................................... 36
10.1. END OF DAY WITH DELETION AND START OF DAY.................................................................. 36
10.2. END OF DAY WITHOUT DELETION, SALES DELETION AND START OF DAY ................................ 39
10.3. INITIALIZATION ................................................................................................................... 42
11. L SERIES’ SCALES COMMUNICATION EXAMPLES ......................................................... 44
11.1. END OF DAY WITH DELETION AND START OF DAY.................................................................. 44
11.2. END OF DAY WITHOUT DELETION, SALES DELETION AND START OF DAY ................................ 47
11.3. INITIALIZATION ................................................................................................................... 50

49-MDIBALCOMEN01 1
 Dibalcom
1. PROGRAM DESCRIPTION
This program allows establishing communication with DIBAL scales and other weighing and
labelling equipment, hereinafter called "scales". It was developed specifically to work under
Windows 95, 98, NT, 2000 and XP.

In the program’s main screen, you can select the following parameters:
• Name of the data file to be transmitted (TX.TXT by default).
• Name of the file where the messages received from the scales are stored (RX.TXT by
default).
• Addresses of the scales with which you wish to communicate (00 by default).
• Type of communication (Ethernet, TCP or UDP and RS-232)

Only for RS-232:

• Communication speed (9600 by default).
• Only for RS-232: Communications port (COM1 by default).
• Only for RS-232: Number of bits of the communication (7 by default).
• Parity (Even by default).

2
Manual

The program allows communication with a maximum of 16 scales per port in the case of
communication via RS-232 and 50 scales via Ethernet. With communication through RS-232, if you
select only one communications port, the scales’ addresses will be between 00 and 30, whereas if
communications use 2 ports, they will between 00 and 62.

The format of the files can be chosen in the Configuration-File Format menu. By default, it is
DIBAL’s.
To enter in the Configuration Menu, select in Main Menu File--Edit Communication.
Then the option Configuration is enabled in the Main Menu

49-MDIBALCOMEN01 3
 Dibalcom
In Configuration – General Configuration menu you decide if a code needs to be entered to modify
parameters, stop communication and/or quit the program. When the program is installed a code is
not used by default. Where a code is requested to quit the program, the said code is only
requested when you attempt to quit the application by pressing the END button. If you attempt to
terminate the execution of the program by means other than those of Dibalcom, the code is not
requested.
The default value of this code will be null (press <enter>). Go to Configuration – Change code menu
to change the value of this code.

It is also possible to change the language of the Interface. To do it select menu Language, and
choose Spanish or English.

All the program’s parameters can be selected from the control file "Dibctrl.txt", which can be
modified by the user availing of the text editor.
In addition, commands can be sent to the program by means of a command file (CTRL.TXT by
default).
Once the program has started executing, it maintains communication with the scales, even when
there is a change in tasks.

4
Manual
2. DATA FILE MANAGEMENT
2.1. Control file (DIBCTRL.TXT)
It allows you to select most of the program’s control parameters. Its name is fixed "DIBCTRL.TXT"
and it must be in the same directory as the “DibalCom.Exe” program.
If the first character is “*”, it means that the whole line is a comment and it will not be taken into
account. If the line starts with "-", it shows that is a command line.
The list of commands is:

To set the type of communication,

1. –m 1 Type of communication
0: RS-232
1: TCP
2: UDP

To serial communication
2. . –p COM1 Communications port: COM1 / COM2 / COM3 / COM4.

3. . –v 9600 Communication speed: 9600 / 4800 / 2400 / 1200 / 600 / 300.

4. –b 7 Number of bits per character: 7 / 8.

5. –e 0 Parity
0, Even
1, Odd
2, None
3, Flag
4, Space
6. –T 02,50 Polling timeout and message timeout (in ms*100). By default the polling timeout is 2
and the message timeout is 50

To TCP and UDP communication,

7. –d DD#XXX.XXX.XXX.XXX:PPPP Master slave’s address. A line is added for each scale
which we want to communicate with

DD: Address (even) of each scale to be communicated with

(Between 00 y 98)
XXX.XXX.XXX.XXX Scale’s Ethernet address
PPPP: Transmission port for ADSL

8. –F XXX.XXX.XXX.XXX PC’s IP address. It is used when the computer has multiple network
cards, to identify where we want to communicate

9. –j Pescucha, Penvio Communication ports through TCP

Pescucha: Port by which the DibalCOM listens via TCP. 3001 by default
Penvio: Port by which DibalCOM sends the information through TCP. 3000
by default.

49-MDIBALCOMEN01 5
 Dibalcom
10. –k Pescucha, Penvio Communication ports through UDP
Pescucha: Port by which DibalCOM receives through UDP. 25500 by default.
Penvio: Port by which DibalCOM sends information through UDP. 4660 by
default.

11. –E 1 Configuration of ping to determine if the scale is present or not. By default this
parameter is set to 1. This parameter must be disabled in case of ADSL
communications. In the case of not having opened that port on the router the Ping
service would not release and the program would be caught.
0: Disable
1: Enable

12. –s 0 Enable DoPing.exe pin’s program that determines if the scales are constantly
discharged with the-d parameter are present or not.
0: Disable
1: Enable

Other parameters:
13. –a 0 Automatic start-up of the program:
0 = No
1 = Yes

14. –A 0 Start-up the Dibalcom that appears in the task’s bar minimised.
0: Normal start.
1: Minimised start.

15. –I 0 Language:
0 = Spanish
1 = English

16. –t tx.txt Name of the file to transmit. tx.txt by default

17. –r rx.txt Name of the reception file. rx.txt by default

18. –c ctrl.txt File name or command control. ctrl.txt by default

19. –P ***** Password CODED (DO NOT CHANGE ITS VALUE HERE: USE DIBALCOM)

20. –w 0 How to use the password:

0:– No password
1:– On changing parameters
2:– On changing parameters and on terminating
3:– On terminating.

21. –f 0 Sales exportation format to a file.

0: No exportation
1: File format by scale and day
Output file. “BLONDDM.TOT”
2: Dibal format (RXGlobal.txt)
Output file. ”RXGlobal.txt”

6
Manual
22. – x X 0: Dibal format file disabled (RX.txt is not generated)
1: Dibal format file enabled (RX.txt is generated) (By default)

-x -f Output file Description

0 0 X Not allowed –x is forced to 1
“BL0NDDddm.TOT” / The sales records 25,78 and LA export to sales files “BL0DDddm.TOT” and other
0 1
BL0DDM.TOT records go to the output file “BL0DDM.TOT” whose name is fixed.
In RXGlobal.txt all the records are written and in the selected –r all except the
0 2 RXGlobal.txt
mentioned sales.
1 0 Selected in -r All the records are written in the selected –r
1 1 Selected in -r Same as above, but also sales are exported to the sales files
All the records are written in RXGlobal.txt but also in the selected –r
1 2 RXGlobal.txt Todos los registros son escritos tanto en el RXGlobal.txt como en el seleccionado
en -r

23. C 0 Sales exportation format to several files, one file for each sale.
0: Exportation disabled.
1: Exportation “Format 2.1” Output files. “2NNNNGGEEEEEC.txt”
2: Exportation “Format 2.2” Output files. “2NNNNGGEEEEECDD.txt”
3: Exportation “Format 2.3” Output files. “2DDNNNNNNEEEEEEEEEC.txt”

24. –i path InfoService Path (only valid for communication with InfoService)

25. –L 1 Save Communication Logs

0: Logs are not saved
N: They are saved, in “N” the number of days is indicated
26. –S value Shop Communicating (Information supplied by the RMS)

27. –Q dir1, dir2, ... , dirn Indicates which scales are from the L series and which are the
ones we want that the Dibalcom translate the message from A to
L..

28. –K dir1, dir2, ... , dirn Indicates which scales are from the K series and which are the
ones we want that the Dibalcom translate the message from A to K
(The messages translate are only from 22 to X1).

29. –U value Users’ possible values are the following:

1 or unialco: Unialco
2 or china: China
30. –H value Indicates scale’s which we are going to communicate with.
The possible values are as follows:
0: Any model except 500 series
1: 500 Series
31. –B DataBase:User: Password Reserved for Pascal’s driver.

32. –N CompanyID:ShopID Reserved for PCscale’s driver.

33. –D DecimalsNumberAmount: DecimalsNumberWeight Reserved for PCscale’s driver.

34. –Z XXX Reserved for PCscale’s driver. Process delay Timer Tx, Rx.

35. –M X Reserved for PCscale’s driver. Day’s movement.

49-MDIBALCOMEN01 7
 Dibalcom
2.2. Input file (TX.TXT)
This file contains the messages that are to be sent to the scales. Each line must be a message
written following a given structure. The first two characters of the line are the scale’s address. With
RS-232 communication, if these characters are “AA” or “aa”, this message will be sent to all the
selected scales. If they are “ZZ” or “zz”, the program terminates its execution. When the message
has been sent correctly, it is marked with a “*” in the third position.
Example: 002250A0000101LETTUCE 000250000000000000000
It sends scale 00 register 22 with item 00001, PLU 01, the name lettuce and price 25.

Once all messages have been sent, the date and time of the file is checked, as is its size. If any of
these characteristics have changed, open the file and seek the next message to be sent.
This program opens the input file, reads the message to be sent and closes it, to allow other
applications to add more messages. These applications must take into account the fact that when,
on trying to open the file, an error message may appear as you are accessing the DibalCom
program. If this occurs, re-try opening. If an application is going to write in this file, it must be
opened for the addition, and remain open as short a time as possible.

2.3. Output file (RX.TXT)

This file contains the messages received from the scales. Whenever a message is received from
any of the scales, the output file is opened for adding, the message with the address of the scale
sending it is entered and the file is closed. Any other application can access this file, checking its
size and opening it in read mode if there is any variation.

2.4. Command file (CTRL.TXT)

This file contains the commands which allow communication to be carried out. The DibalCom
program reads the communication steps to be taken from this file. Whenever a line is read, the file
is erased. For every command you wish to send to the DibalCom program a file has to be created,
written and closed.

To carry out local communication the following commands are written:

R (Restart) It closes communication. It prompts the DibalCom program to
read configuration file "DIBCTRL.TXT" to take control parameters and it
reopens communication. It initialises reader pointers of the TX file at the
start
S (Start) It starts polling the scales’ addresses.
Messages are sent and received.
S (Stop) It terminates polling.
To carry out communication via modem the following commands are written in the same order:
R (Restart) It closes communication. It prompts the DibalCom program to
read the configuration file "DIBCTRL.TXT" to take control parameters and
reopens communication.
MON Indicates MODEM communication.
s (Start) It starts polling the scales’ addresses.
S (Stop) It terminates polling.
A (ActDTR) It enables the modem’s DTR signal (data terminal).

8
Manual
Depending on the modem’s type of dialling, one or other of these two commands is written:

TATDTxxxxxxx The call is made to the remote MODEM number xxxxxxx. Tone
dialling.
TATDPxxxxxxx The call is made to the remote MODEM number xxxxxxx. Pulse
dialling.
s (Start) It starts polling the scales’ addresses.
S (Stop) It terminates polling.

To terminate communication via modem:

S (Stop) It terminates polling.
B (Break) It enables the Break signal.
I (Inactive) It disables the modem’s DTR signal (data terminal ready).
T+++ Modem in command mode.
TATHO It hangs up the telephone.
MOFF Disabled the communication flag MODEM

Other options:
C It closes communication.
X (Restart but without sin cutting off communication) It prompts the DibalCom
program to read configuration file “DIBCTRL.TXT” to take control parameters.
G Close the Dibalcom

49-MDIBALCOMEN01 9
 Dibalcom

3. SALES EXPORTATION
There are 2 types of sales exportation:
Export to a single file: In this functionality, there are two types of format. The format File per Scale
and Day that generates many files as scales we have, and in each of these files introduces the
sales of the day. The next day the file’s name is different. The other format, Dibal Format, is actually
a copy of RX.txt but it will not be deleted by the RMS.
Export of each sale to a file: It generates a file for each scale’s sale. This way of working is
designed for removing the sales when are processed by the server, otherwise it can lead to trouble
for having files on different days with the same name.

3.1. DIBAL Format (RX.txt)

This format is enabled by default. All the records received from the connected scales will be saved
in this file, which is created in the directory where the application resides.
You can enable or disable either in the graphic interface by the check called Dibal Format (RX.txt),
which is in general configuration menu and export sales, or by placing the parameter – x to 0 if you
want to disable or – x to 1 if you want to enable.

3.2. All the sales to a file

Format 1.1
– f1
File per Scale and Day:
This export sales are made to the messages 25,LA and 78 of the scales series such as: A, M,
Supreme, L and K.
The export is called Infoservice. It can be activated through the graphic interface, selecting in the
screen the General Configuration and in the Sales Exportation menu, the "File Per Scale and Day"
option (It is necessary to have activated the check of "All the sales to a file") or placing the
parameter – f to 1 in the dibctrl.txt file.
This export is generating a file for each scale with the different receipts lines that are made
The name of the file is BL0DDddm.TOT
BL0: Fix
DD: The master scale’s Address divided between 2 (1 digit)
dd: It is the sale’s day (2 digits)
m: It is the month sales 0…9, A, B y C where 0: January ,…9: September, A:
October, B: November and C: December (1 digit)
.TOT: It is the file’s extension.

Therefore, we can have stored in files the receipts of a year. The following year, the files’ names
star to repeat.

10
Manual
The information in the sales line appears formatted in the file in the following way:

Field Length

Scales Address 2

Receipt Number 5

Receipt Line Number 3

Item Code 6

Quantity or Sale Weight (The first digit indicates the sale sign, 6
0:positive, – :negative)

Amount sold receipt line 9

Vendor. You take the last two digits of the vendor’s code 2

Date in format yyyymmdd (year, month, day) 8

Time in format hhmm (hours, minutes) 4

Client code. Only for the scale that has implemented that is the L, 5
the rest set to cero.

Format 1.2
– f 2

Dibal Format (RXGlobal.txt):

Selecting this option generates a file called RXGlobal.txt, which is written the same as in the RX.txt
but with the exception that it is not deleted by the RMS.
The file stored in the path indicated is in the menu. If null, it would be stored in the directory where
the application is.
To select this option you can do through the graphic interface, selecting in the General
Configuration screen and the sales exportation menu, the option “Dibal Format File” Required have
enable the check of “All the sales to a file” or placing the parameter – f to 2 in the dibctrl.txt file.

3.3. Exportation of each sale to a file

This exportation sales for the format 2.1 and 2.2 is made for the messages LA and LY (78 and 7C
from Dibalcom 8-01H). For the 2.3 format is made for the LE message generated by the LP/LS to
each label.
Through the graphic interface, we select in the sales exportation the Receipt Exportation (File Per
Format 2 Sale) or put the parameter – C to 1, 2 or 3 in the dibctrl.txt file.
This exportation consists on the creation of a file for each sale made with the receipt lines.
Format 2.1
– C 1
If we select this option, the file name is 2NNNNGGEEEEEC.txt,
2: Fix
NNNN: It is the scale receipt number (4 digits)
GG: It is the scale group (2 digits)

49-MDIBALCOMEN01 11
 Dibalcom
EEEEE: It is the total sale amount (5 digits)
C: It is the checksum (1 digit)
.txt: It is the file extension

Format 2.2
– C 2

If we select this option the file includes the master address, the files name is
2NNNNGGEEEEECDD.txt,
2: Fix
NNNN: It is the scale receipt name (4 digits)
GG: It is the scales group (2 digits)
EEEEE: It is the sales total amount (5 digits)
C: It is the checksum (1 digit)
DD: Scale Address (2 digits)
.txt: It is the files extension

In both cases the sales line information appears formatted in the file in the following way:

Field Length

Item Code 5

Quantity or weight sold (The first digit indicates the sign of the sale, 6
0 positive, - negative.

Estimated price of the ticket line 5

Amount sold in the ticket line (The first digit indicates the sign of 6
sale, 0 positive, - negative.

Format Date ddmmyy 6

Format Hour hhmm 4

Vendor 5

Group 2

Ticket Number 4

Format 2.3
– C 3
If we select this option, the file name is: 2DDNNNNNNEEEEEEEEEC.txt,

2: Fix
DD: Scales Address (2 digits)
NNNNNN: It is the scale receipt number (6 digits)
EEEEEEEEE: It is the sales total amount (9 digits)
C: It is the checksum (1 digit)
.txt: It is the files extension

12
Manual
In this case the information of each label appears in the file with the following format:

Field Length

Ticket Number 6

Item Code 6

Weight 6

Sign (0 positive, 1 negative) 1

Price 7

Amount 9

Order 6

Client 5

Lot 24

Tare 6

Animal 3

Format Data ddmmyy 6

Format Hour hhmm 4

NOTE: Only to register LE

49-MDIBALCOMEN01 13
 Dibalcom

4. ADSL COMMUNICATIONS
It has been implemented the possibility of communication with the scales connected by ADSL by
means of DIBALCOM.

Due to the characteristics of the ADSL connections, from the PC all the scales will have the same
IP address (Public IP address of the router where the scales are installed) so for having a complete
identification of the scales in this case, every scale will have its own IP address and a different
communications port.

From version 126 of DIBALCOM it is possible, when it is created a communication with a scale, to
program its IP address and the transmission port through which the PC will communicate with the
scale.

The port for data reception is programmed in the Main Configuration

If the information is entered in the file dibctrl.txt, it must be added a line showing the master
address, the IP address and the port. Example:
-d 00#10.1.2.207:3000

If the communication is ADSL, the parameter -E must be set to 0 in the file dibctrl.txt. With this
parameter to 0 the functioning is the following:
- There is not make ping to the scales
- Increase of the Timeouts in ADSL communications.

This parameter can be set up in the RMS WHEN the connection with the shop is set up.

14
Manual

5. MESSAGE TRANSLATION FROM “A” TO “L”

In order to the Dibal clients that have integrated the scale of the A series with its management
system can integrate L series scales without making any changes into your program. It has been
implemented in the Dibalcom the translation functionality of the A series to the L Series when it is
configured to do so.

5.1. Configure the Dibalcom in order to translate the messages

In order to the Dibalcom execute the translation of the messages from the A series to the L series, it
must include a line in the dibctrl.txt file that is in the following way:
-Q 02, 04
With this line we are indicating that it has to translate the messages from the A to the L to the scales
with the 02 and 04 addresses.

5.2. Implemented messages in the Dibalcom

The Dibalcom translates the messages to send from A series to the L series according to:
SEND TO A SCALE
DESCRIPTION
A SERIES L SERIES
21 Z0 Configuration, Start of day
22 L2, L3 Mto Items (basic)
X1 L2, L3 Mto Items (complete)
X2 L4 Item texts
33 L4 Item texts
28 L7 Receipt Texts (headers and footers). The first 8
28 lines.
Label Texts. From the 9 line to the 15
46 46 Label Format (It is set to the maximum)
47 L6 Label Dimensions Format
4Q L6 Label Dimensions Format
KB (vendors X5 Vendor registering Keyboard simulation
registering)
KB (end of day KB (no retransformed) Keyboard simulation without erasing end of day
without erasing)
KB (end of day KB (no retransformed) Keyboard simulation with erasing end of day
with erasing)
KB (Initialization) KB (no retransformed) Initialization keyboard simulation
KB (grand total KB (no retransformed) Keyboard simulation of the grand total group list
group)
KE (vendors X5 + KB Vendor registering Keyboard simulation
registration)
KE (Label KB Keyboard simulation of the label global format
formats) change
KE (grand total KB Keyboard simulation of the grand total group list
group)
31 “” Vendors registering answer

49-MDIBALCOMEN01 15
 Dibalcom
The remaining keyboard simulations is filtered to “” in order to avoid problems.

- The Dibalcom will translate the received messages of the L series to the A series receipts
according to the following table:

RECEIVED FROM SCALE

DESCRIPTION
L SERIES A SERIES

LA 25 Receipt sales
2M 2J Receipt sales per section

F6 36 Accumulated sales per item

F9 29 Total accumulated sales

5.3. Functioning
Every time we start the communication with the Dibalcom either through the graphic interface or
through commands in the file ctrl.txt the Dibalcom performs the processing of the transmission file
and transforms the scales’ records set in the dibctrl.txt (Option – Q).
To carry out the registers transformation from A to L when we work with a file ctrl.txt we must write
the following commands sequence.

We stop, command: S + CRLF

Restart pointers, command: R + CRLF

We start communication, command: s + CRLF

To process each command we generate a ctrl.txt file with its order and we wait until the file
disappears.

On the other hand, every time a sale is done in a scale, if it is configured to transform the records, it
will be done online.

16
Manual

6. MESSAGE TRANSLATION FROM “A” TO “K”

In order to the Dibal clients that have integrated the scale of the A series with its management
system can integrate K series scales without making any changes into your program. It has been
implemented in the Dibalcom the translation functionality of the A series to the K series when it is
configured to do so.

6.1. Configure the Dibalcom in order to translate the messages

In order to the Dibalcom execute the translation of the messages from the A series to the K series, it
must include a line in the dibctrl.txt file that is in the following way:
-K 02, 04
With this line we are indicating that it has to translate the messages from the A to the K to the
scales with the 02 and 04 addresses.

6.2. Implemented messages in the Dibalcom

The messages that have been translated in the Dibalcom are the following ones:

Items Data, it is turned from the record 22 to X1.

6.3. Functioning
Every time we start the communication with the Dibalcom either through the graphic interface or
through commands in the file ctrl.txt, the Dibalcom performs the file transmission process and
transforms the scales’ records set in the dibctrl.txt (Option – K).
To carry out the registers transformation from A to K when we work with a file ctrl.txt we must write
the following commands sequence.

We stop, command: S + CRLF

Restart pointers, command: R + CRLF

We start communication, command: S + CRLF

To process each command we generate a ctrl.txt file with its order and we wait until the file
disappears.

It is possible to have in the same shop L series and K series scales and generate for all of them the
record 22 of items. Configure correctly the parameter – Q and –K.

49-MDIBALCOMEN01 17
 Dibalcom

7. L SERIES INTEGRATION STEP BY STEP

7.1. Download Sales
1) Configure the file “dibctrl.txt” with the appropriate parameters for the communication. In
this file the master addresses, IP, path files ports are defined (See point 2.1 Configuration
File).

2) Start the Dibalcom

3) Delete the file “Tx.txt”.

4) Start the communication with the scale. For that purpose:

Send Process

5) Save the file “Tx.txt”.

6) As a general rule, every time you want to send the content of the file “Tx.txt”, the process
is divided into three steps:
6.1) Create the file “ctrl.txt” and write ‘S’, indicating Stop, save. The Dibalcom will
remove once the instruction is collected.
6.2) Create a new file “ctrl.txt” and write ‘R’, indicating Restart, save. The Dibalcom will
remove once the instruction is collected.
6.3) Create a new file “ctrl.txt” and write ‘S’, indicating Start, save. The Dibalcom will
remove once the instruction is collected.

7) When the Dibalcom reads ‘S’ loads the structures with the configuration that reads from
the file “dibctrl.txt”. Then the Dibalcom starts reading the “Tx.txt” file and look at the
master address of the record send, it checks that it is for a defined scale and sends

End Send Process

8) Once the communication is establish, the scale will start downloading the sales to the
“Rx.txt” file.

9) If you spend more than 5 seconds without receiving sale we must send the record P0
asking to the scale if you have more sales.

10) The scale only accepts the records in which the group matches with its group number, so
the first thing to do is send the records that configured the scale and defined this group
number. These are Z0 and ZA.

11) To ask to the scale if you have something to send we use the record P0 with the following
format:

Ex.: To a scale with the master address 04 and group 00: 04P000ASK000000000001

12) We will use this communication to send Z0, ZA and P0. For this matter, open the “Tx.txt”
and write the records Z0, ZA and P0 and repeat the Send Process.

18
Manual
13) Once sent, poll the content of the “Rx.txt” until receive the P0 answer record.
Approximately the answer lasts about 3 seconds.

13.1) If the received record P0 is 04P000RES0000NO000001, the bytes 12 and 13

(always start counting from the registry key, in other words from P0) indicate with
the characters NO that the scale has nothing pending to send.

13.2) If the received record P0 is 04P000RES0000SI000001, the bytes 12 y 13 indicate

with the characters SI that the scale has sales to download. If so it will start
downloading all the sales automatically.

To see whether it is completed it will wait a 5 seconds since the last sale received. After
this time, it is written another P0 record in the following line of the “Tx.txt”.

Ex: 04P000ASK000000000002
th
NOTE 1: In the 14 position of the record P0 we have 6 bytes which defined the
message number. This code ensures that the answer corresponds to the question,
when the scale answers with a P0 always puts the same number you received in the
P0 question.

NOTE 2: If the Dibalcom is polling whenever you add lines at the end of the file, the
Dibalcom detects them and sends them.

14) When the answer of P0 is NO, the scale will no longer have to download sales so that we
can run to the following action (initialization, start of day, end of day…)

The scale can be configured to send to the Dibalcom some or other records depending on the
needs we have. By default the L series download the sales through the LA record (See the
record description in Dibal’s record data base, Communication Registers.mdb).

49-MDIBALCOMEN01 19
 Dibalcom

7.2. Initialization
1) To do an initialization the first thing is download from the scale all the sales it could have
stored. To that end, it will need to execute all the steps of the previous point “Download
Sales”.

2) Once received the record P0 saying that there are no more sales we create a “ctrl.txt” file
and write ‘S’, indicating Stop, save.

3) Create again the “ctrl.txt” file and write ‘R’, indicating Restart, save.

4) Delete the file “Tx.txt”.

5) Open the file “Tx.txt” and write the configuration records Z0 and ZA followed by the
record KB which is in charge of doing the initialization. The KB record for an initialization
will always have the same form varying only the master address and group, if necessary.

The initialization record KB for the master 04 and group 00.

04KB00116337373737373737373761

The Dibalcom will be in charge of completing the record with zeros until 130.

Send process

6) Save the Tx.txt file.

7) As a general rule, every time you want to send the content of the file “Tx.txt”, the process
is divided into three steps:
7.1) Create the file “ctrl.txt” and write ‘S’, indicating Stop, save. The Dibalcom will
remove once the instruction is collected.
7.2) Create a new file “ctrl.txt” and write ‘R’, indicating Restart, save. The Dibalcom will
remove once the instruction is collected.
7.3) Create a new file “ctrl.txt” and write ‘S’, indicating Start, save. The Dibalcom will
remove once the instruction is collected.

8) When the Dibalcom reads ‘S’ loads the structures with the configuration that reads from
the file “dibctrl.txt”. Then the Dibalcom starts reading the “Tx.txt” file and look at the
master address of the record send, it checks that it is for a defined scale and sends.

9) The Dibalcom will indicate in the “Tx.txt” file in the record’s corresponding line with an
rd
asterisk (*) in the 3 line position.

End Send Process

10) When the 3 records (Z0, ZA and KB) have been sent, we keep polling from time to time
the “Rx.txt” file until receive the record 30.
For example: 0430L870ESP VC32D

The scale approximately takes 15 seconds in initialize and send the record 30.

11) Once received this record with the key 30 will indicate that the scale has finished its
initialization and it is ready to receive the record we send.

20
Manual
12) The first thing will be to send again the configuration records Z0 and ZA to configure
correctly the scale as it has been deleted. And then, all the records with the data we want
to load (PLU’s, vendors…) For that open the file “Tx.txt” (from programming open with
“Append”) and write in the following line to KB the records Z0, ZA, L2, L3…

13) Save the “Tx.txt” file.

NOTE: If the Dibalcom is polling whenever you add lines at the end of the file and saves
the file “Tx.txt”, the Dibalcom detects them and sends them.

14) We must check that all the line has been sent. To this end, we read the file “Tx.txt” and
we check that all the lines have an asterisk (*) in the position 3.

15) If any line has not been sent by any reason, we repeat the procedure from the step 6.

49-MDIBALCOMEN01 21
 Dibalcom

7.3. Start of day

1) To do a start of day the first thing to do is download all the scale’s sales that could be
stored. You will have to execute all the steps in the previous point.

2) Once we receive the record P0 telling us that there is no more sales, create a file “ctrl.txt”
and write ‘S’, indicating Stop, save.

3) Create again the file “ctrl.txt” and write ‘R’, indicating Restart, save.

4) Delete the file “Tx.txt”.

5) Open the file “Tx.txt” and write all the records that we want to send preceded by the
master address which we want to communicate with.

NOTE: If we have several scales, to optimize the data sending process to them, you have
to write the records ordering them by the master address, that is, firstly, those who have
the same master, then all of the following one.

Send Process

6) Save the file “Tx.txt”.

7) As a general rule, every time you want to send the content of a file “Tx.txt”, the process is
divided into three steps:
7.1) Create the file “ctrl.txt” and write ‘S’, indicating Stop, save. The Dibalcom will
remove once the instruction is collected.
7.2) Create a new file “ctrl.txt” and write ‘R’, indicating Restart, save. The Dibalcom will
remove once the instruction is collected.
7.3) Create a new file “ctrl.txt” and write ‘S’, indicating Start, save. The Dibalcom will
remove once the instruction is collected.

8) When the Dibalcom reads ‘S’ loads the structures with the configuration that reads from
the file “dibctrl.txt”. Then the Dibalcom starts reading the “Tx.txt” file and look at the
master address of the record send, it checks that it is for a defined scale and sends.

9) The Dibalcom will indicate in the “Tx.txt” file in the record’s corresponding line with an
rd
asterisk (*) in the 3 line position.

End Send Process

10) We must check that all the line has been sent. To this end, we read the file “Tx.txt” and
we check that all the lines have an asterisk (*) in the position 3.

11) If any line has not been sent by any reason, we repeat the procedure from the step 6.

22
Manual

7.4. End of day

1) To do an end of day the first thing to do is download all the scale’s sales that could be
stored. You will have to execute all the steps in the previous point Download Sales.

2) Once we receive the record P0 telling us that there is no sales, we create a file “ctrl.txt”
and write ‘S’, indicate Stop, save. The Dibalcom will remove once the instruction is
collected.

3) Create again the file “ctrl.txt” and write ‘R’, indicating Restart, save. The Dibalcom will
remove once the instruction is collected.

4) Delete the file “Tx.txt”.

5) Open the file “Tx.txt” and write the start of day records Z0, ZA, P0, KB for the Grand Total
Group list and end of day KB.

- The start of day record P0 for a master 04 and group 00 is:

04P000INI2000

- The record KB for the listing of the Grand Total Group is:
04KB 0006644921595961

- The record KB of the end of day is:

04KB 0006630101010161

The Dibalcom will complete with zeros the records until 130.

Send Process
6) Save the file “Tx.txt”.

7) As a general rule, every time you want to send the content of a file “Tx.txt”, the process is
divided into three steps:
7.1) Create the file “ctrl.txt” and write ‘S’, indicating Stop, save. The Dibalcom will
remove once the instruction is collected.
7.2) Create a new file “ctrl.txt” and write ‘R’, indicating Restart, save. The Dibalcom will
remove once the instruction is collected.
7.3) Create a new file “ctrl.txt” and write ‘S’, indicating Start, save. The Dibalcom will
remove once the instruction is collected.

8) When the Dibalcom reads ‘S’ loads the structures with the configuration that reads from
the file “dibctrl.txt”. Then the Dibalcom starts reading the “Tx.txt” file and look at the
master address of the record send, it checks that it is for a defined scale and sends.

9) The Dibalcom will indicate in the “Tx.txt” file in the record’s corresponding line with an
rd
asterisk (*) in the 3 line position.

End Send Process

10) When you receive the KB of scale’s end of day, all the accumulated are download to
the “Rx.txt” file. We must keep polling every certain time the “Rx.txt” file until receive the
F9 record.

49-MDIBALCOMEN01 23
 Dibalcom
The F9 record is the Total Accumulated Sales. The receiving time will vary depending on
the accumulated sales.

11) Once received the F9, in order to delete the scale’s accumulated, we have to send the
P0 record indicating that the End of Day is over, the scale waits for a minute the
reception of the end of P0, if in this time the scale does not receive it, the sales will not
be deleted and it is necessary to repeat the process. When the scale receive this
record, it will delete all the stored accumulated.

To send the record P0 of End of day, open the “Tx.txt” file (from programming open with
“Append”) and write in the following line to KB the records Z0, ZA, and End of day of P0.

- The record P0 has to have the following form:

04P000FIN2000

The Dibalcom will be in charge of completing the record with zeros until 130.

12) Save the file “Tx.txt”.

NOTE: When we save the file “Tx.txt”, if the Dibalcom is communicating, the lines that are
added at the end of the “Tx.txt” file will be sent automatically.

13) If there is any line that is not sent, we repeat the process starting from the point 6.

24
Manual

8. K SERIES INTEGRATION STEP BY STEP

8.1. Download Sales
1) The first thing to do is to configure the communication type that we are going to establish
with the scale. To do this, follow the scale’s K series manual instructions.

2) In the file “dibctrl.txt” will have to modify certain parameters depending on the
communication type that we will use. See section 2.1 Configuration.

3) Start the Dibalcom.

4) Delete the “Tx.txt” file.

5) Configure the scales’ parameter:

Once programmed the Dibalcom and the scale K for the chosen communication, send the
configuration in order to establish the machine operation mode.
To do this, write the “Tx.txt” file the record “21 Start of day” that is defined in the record
database “Communication Registers.mdb”. In this database all the records supported
by the k series scales are defined. That is where we find the record that we are interested
in based on the data we want to send.
In this example for a master 00, the 2 in red indicates that the scale will send the receipt
to the PC every time that is generated.
00210009082809240000002000000000000000000000000000000000000000000000000
0000000000

Send process
6) Save the file "Tx.txt”.

7) As a general rule, every time you want to send the content of the file “Tx.txt”, the process
is divided into three steps:
7.1) Create the file “ctrl.txt” and write ‘S’, indicating Stop, save. The Dibalcom will
remove once the instruction is collected.
7.2) Create a new file “ctrl.txt” and write ‘R’, indicating Restart, save. The Dibalcom will
remove once the instruction is collected.
7.3) Create a new file “ctrl.txt” and write ‘S’, indicating Start, save. The Dibalcom will
remove once the instruction is collected.

8) When the Dibalcom reads ‘S’ loads the structures with the configuration that reads from
the file “dibctrl.txt”. Then the Dibalcom starts reading the “Tx.txt” file and look at the
master address of the record send, it checks that it is for a defined scale and sends.
9) The Dibalcom will indicate in the “Tx.txt” file in the record’s corresponding line with an
rd
asterisk (*) in the 3 line position.
End Send Process
10) If we configure the scale to send the sales to the PC, all you have to do is communicate
with it so every time you print a receipt, it will send a record 78 with the data sales.

49-MDIBALCOMEN01 25
 Dibalcom

8.2. Initialization
1) To do an initialization the first thing is to download from the scale all the sales it could
have stored. To that end, it will need to execute all the steps of the previous point
“Download Sales”.

2) Once received all the sales, we create a “ctrl.txt” file and write ‘S’, indicating Stop. Save.

3) Create again the “ctrl.txt” file and write ‘R’, indicating Restart, save.

4) Delete the file “Tx.txt”.

5) Open the file “Tx.txt” and write the configuration record 21 followed by the record KB
which is in charge of doing the initialization. This KB record for K series initialization will
always have the same form only varying the master address and group, if necessary.
Configuration record
00210009082809240000002000000000000000000000000000000000000000000000000
0000000000
KB initialization record for the master 00 and group 00.
00KB00115660605642431427252727
The Dibalcom will in charge of completing the record with zeros until 130.

Send Process
6) Save the ”Tx.txt”.

7) As a general rule, every time you want to send the content of the file “Tx.txt”, the process
is divided into three steps:
7.1) Create the file “ctrl.txt” and write ‘S’, indicating Stop, save. The Dibalcom will
remove once the instruction is collected.
7.2) Create a new file “ctrl.txt” and write ‘R’, indicating Restart, save. The Dibalcom will
remove once the instruction is collected.
7.3) Create a new file “ctrl.txt” and write ‘S’, indicating Start, save. The Dibalcom will
remove once the instruction is collected.

8) When the Dibalcom reads ‘S’ loads the structures with the configuration that reads from
the file “dibctrl.txt”. Then the Dibalcom starts reading the “Tx.txt” file and look at the
master address of the record send, it checks that it is for a defined scale and sends.

9) The Dibalcom will indicate in the “Tx.txt” file in the record’s corresponding line with an
rd
asterisk (*) in the 3 line position.

End Send Process

10) When the 2 records (21 and KB) have been sent, we keep polling from time to time the
“Rx.txt” file until receive the record 30.
0030VERSION V A.05000000000000000000000000000000000000000000000000000

11) Once received this record with the key 30 will indicate that the scale has finished its
initialization and it is ready to receive the record we send.

26
Manual
12) The first thing will be to send again the configuration record 21 to configure correctly the
scale as it has been deleted. And then, the rest of records (PLU’s, vendors…).
For that, open the file “Tx.txt” (from programming open with “Append”) and write in the
following line to KB the records 21, X1, X2…

13) Save the file “Tx.txt”.

NOTE: If the Dibalcom is polling whenever you add lines at the end of the file and saves
the file “Tx.txt”, the Dibalcom detects them and sends them.

14) We must check that all the line has been sent. To this end, we read the file “Tx.txt” and
we check that all the lines have an asterisk (*) in the position 3.

15) If any line has not been sent by any reason, we repeat the procedure from the step 6.

49-MDIBALCOMEN01 27
 Dibalcom

8.3. Start of day

1) To do a start of day the first thing is download from the scale all the sales it could have
stored. To that end, it will need to execute all the steps of the previous point “Download
Sales”.

2) Once received all the sales, we create a “ctrl.txt” file and write ‘S’, indicating Stop. Save.

3) Create again the “ctrl.txt” file and write ‘R’, indicating Restart, save.

4) Delete the file “Tx.txt”.

5) Open the file “Tx.txt” and write all the records we want to send preceded by the master
address we want to communicate with.

Examples of the K series records:

5.1) Configuration:

002100090828092400000020000000000000000000000000000000000000000000
000000000000000

5.2) Vendors registering:

In this example we are registering the vendor 1 and 2 through the KB and 31
records.
00KB00205660605657121457404509575757574260605660000000000000000000
0000000000000000000000000000000000000000000000000000000000000000
00310000001Vendor 1
000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000
00KB00205660605657121457404524575757574360605660000000000000000000
0000000000000000000000000000000000000000000000000000000000000000
00310000002Vendor 2
000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000
The characters in red represent a key of the scale and its relation with the vendor’s
number is the following:
42
Vendor 1; 43
Vendor 2; 44
Vendor 3;
27
Vendor 4; 28
Vendor 5;

5.3) Items registration.

00X100M000001001Item 1
000123000000000000000000000000000000000000000000010000000000000000

5.4) Item’s text.

To register the item’s text we send the X2 record.
00X2000000011 T e x t o 1 d e a r t 1 0000012 T e x t o 2 d e a r
t 1 00000000000000

28
Manual
NOTE: If we have several scales, to optimize the data sending process to them,
you have to write the records ordering them by the master address, that is, firstly,
those that have the same master, then all of the following one.

Send Process

6) Save the file ”Tx.txt”.

7) As a general rule, every time you want to send the content of the file “Tx.txt”, the process
is divided into three steps:
7.1) Create the file “ctrl.txt” and write ‘S’, indicating Stop, save. The Dibalcom will
remove once the instruction is collected.
7.2) Create a new file “ctrl.txt” and write ‘R’, indicating Restart, save. The Dibalcom will
remove once the instruction is collected.
7.3) Create a new file “ctrl.txt” and write ‘S’, indicating Start, save. The Dibalcom will
remove once the instruction is collected.

8) When the Dibalcom reads ‘S’ loads the structures with the configuration that reads from
the file “dibctrl.txt”. Then the Dibalcom starts reading the “Tx.txt” file and look at the
master address of the record send, it checks that it is for a defined scale and sends.

9) The Dibalcom will indicate in the “Tx.txt” file in the record’s corresponding line with an
asterisk (*) in the 3rd line position.

End Send Process

10) We must check that all the line has been sent. To this end, we read the file “Tx.txt” and
we check that all the lines have an asterisk (*) in the position 3.

11) If any line has not been sent by any reason, we repeat the procedure from the step 6.

49-MDIBALCOMEN01 29
 Dibalcom

8.4. End of day

1) To do an end of day the first thing is to download from the scale all the sales it could have
stored. To that end, it will need to execute all the steps of the previous point “Download
Sales”.
2) Once received all the sales, we create a “ctrl.txt” file and write ‘S’, indicating Stop. Save.
The Dibalcom will remove once the instruction is collected.
3) Create a new file “ctrl.txt” and write ‘R’, indicating Restart, save. The Dibalcom will
remove once the instruction is collected.
4) Delete the file “Tx.txt”.
5) Open the file “Tx.txt” and write the configuration record 21 followed by the record KB
which is in charge of doing the end of day. This KB record for K series initialization will
always have the same form only varying the master address and group, if necessary.
Configuration record:
00210009082809240000002000000000000000000000000000000000000000000000000
0000000000
KB record for the master00 and the group 00 that shows the “Grand Total Group” list.
00KB001056606056424314274460
KB record for master 00 and group 00 that generate the download of the “end of day”.
00KB001356606056424314272543435660
The Dibalcom will be in charge of completing the record with zeros until 130.

NOTA: The end of day will remove the vendors and will reset the scale’s accumulated. To
work in the next start of day we have to register the vendors.

Send Process
6) Save the file ”Tx.txt”.
7) As a general rule, every time you want to send the content of the file “Tx.txt”, the process
is divided into three steps:
7.1) Create the file “ctrl.txt” and write ‘S’, indicating Stop, save. The Dibalcom will
remove once the instruction is collected.
7.2) Create a new file “ctrl.txt” and write ‘R’, indicating Restart, save. The Dibalcom will
remove once the instruction is collected.
7.3) Create a new file “ctrl.txt” and write ‘S’, indicating Start, save. The Dibalcom will
remove once the instruction is collected.

8) When the Dibalcom reads ‘S’ loads the structures with the configuration that reads from
the file “dibctrl.txt”. Then the Dibalcom starts reading the “Tx.txt” file and look at the
master address of the record send, it checks that it is for a defined scale and sends.
9) The Dibalcom will indicate in the “Tx.txt” file in the record’s corresponding line with an
rd
asterisk (*) in the 3 line position.
End Send Process
10) From time to time we poll the file “Rx.txt” until receive the record 29.
NOTE: The record 29 is Total Accumulated sales. The receiving time will vary depending
on the accumulated sales.
11) Once received the record 29 we concluded the process end of day.

30
Manual
9. LP/LS INTEGRATION STEP BY STEP
9.1. Download Sales
1) Configure the file “dibctrl.txt” with the with the appropriate parameters for the
communication. In this file the master addresses, IP, path files ports are defined (See
point 2.1 Configuration File).

For example, if we want to communicate with the labeller by Ethernet with the following
values:
IP:192.168.1.12
Master address: 04
TX Port: 3001
RX Port: 3000
You have to edit the file “dibctrl.txt” with the following values:
- d 04#10.1.8.41:3000
- j 3001,3000

2) Save the file “dibctrl.txt”

3) Start the Dibalcom.

4) Delete the “Tx.txt”.

5) Save the file ”Tx.txt”.

6) Create the file “ctrl.txt” and write ‘S’, indicating Stop, save. The Dibalcom will remove
once the instruction is collected.

7) Create a new file “ctrl.txt” and write ‘R’, indicating Restart, save. The Dibalcom will
remove once the instruction is collected.

8) Create a new file “ctrl.txt” and write ‘S’, indicating Start, save. The Dibalcom will remove
once the instruction is collected.

9) When the Dibalcom reads ‘S’ loads the structures with the configuration that reads from
the file “dibctrl.txt”. Then the Dibalcom starts reading the “Tx.txt” file and look at the
master address of the record send, it checks that it is for a defined scale and sends.

10) When communicating with the LP/LS, is automatically release all the sales that we have
accumulated.

11) Once received the first sale, if the scale spends 8 seconds without receiving we finalize
the sales download .

12) By default the LP/LS download the sales through the record 53, 2P, LE, LY, MH, MK, MS
(See Dibal’s database record description, Communication Registers.mdb). The record
we want to download the sales from the menu.

49-MDIBALCOMEN01 31
 Dibalcom
9.2. Initialization
1) To do an initialization the first thing is download from the scale all the sales it could have
stored. To that end, it will need to execute all the steps of the previous point “Download
Sales”.

2) Once received the record P0 saying that there are no more sales we create a “ctrl.txt” file
and write ‘S’, indicating Stop, save.

3) Create again the “ctrl.txt” file and write ‘R’, indicating Restart, save.

4) Delete the file “Tx.txt”.

5) Open the file “Tx.txt” and write the specific KB which is in charge of doing the
initialization. This record for an initialization will always have the same form only varying
the master address, depending on the scale we want to communicate with.
The initialization KB record for the master 04.
04KB00116337373737373737373761
The Dibalcom will in charge of completing the record with zeros until 130.
NOTE: The LP/LS ignores the group that is defined in each record. It accepts all the
records it receives.

Send Process
6) Save the file “Tx.txt”.

7) As a general rule, every time you want to send the content of the file “Tx.txt”, the process
is divided into three steps:
7.1) Create the file “ctrl.txt” and write ‘S’, indicating Stop, save. The Dibalcom will
remove once the instruction is collected.
7.2) Create a new file “ctrl.txt” and write ‘R’, indicating Restart, save. The Dibalcom will
remove once the instruction is collected.
7.3) Create a new file “ctrl.txt” and write ‘S’, indicating Start, save. The Dibalcom will
remove once the instruction is collected.

8) When The Dibalcom reads ‘S’ loads the structures with the configuration that reads from
the file “dibctrl.txt”. Then the Dibalcom starts reading the “Tx.txt” file and look at the
master address of the record send, it checks that it is for a defined scale and sends.

9) The Dibalcom will indicate in the “Tx.txt” file in the record’s corresponding line with an
rd
asterisk (*) in the 3 line position.

End Send Process

10) Alter receiving KB, the labeller will delete all its data and it will send us a record with key
30 when it is finished. Therefore, we will poll from time to time the file “Rx.txt” until receive
the record 30.
For example: 0430LP3400 V-1.09
The scale spends approximately between 2’20’’ and 3’ initializing and sending the record
30.

32
Manual
11) Once this record with the key 30 is received, it will indicate that the scale has finished its
initialization and it is ready to receive the records that we send to it.

12) Now, we will send the records 2L, 2J and 2N. Then, all the record with the data we want
to load (PLU’s, vendors…)
For this, open the file “Tx.txt” (from programming open with “Append”) and write in the
following line in the KB record 2L,2J,2N,L2, L3...

13) Save the file “Tx.txt”.

NOTE: When the Dibalcom is polling whenever you add lines at the end of the file and
saves the file “Tx.txt”, the Dibalcom detects them and sends them.

14) We must check that all the line has been sent. To this end, we read the file “Tx.txt” and
we check that all the lines have an asterisk (*) in the position 3.

15) If there is any reason why any line is not sent, we repeat the Send Process.

49-MDIBALCOMEN01 33
 Dibalcom

9.3. Start of Day

1) To do a start of day the first thing is download from the scale all the sales it could have
stored. To that end, it will need to execute all the steps of the previous point “Download
Sales”.

2) Once received the record P0 saying that there are no more sales we create a “ctrl.txt” file
and write ‘S’, indicating Stop, save.

3) Create again the “ctrl.txt” file and write ‘R’, indicating Restart, save.

4) Delete the file “Tx.txt”.

5) Open the file “Tx.txt” and write all the records that we want to send preceded by the
master address that we want to communicate with. See the description in Dibal’s record’s
database “Communication Registers.mdb”.
NOTE: If we have several scales, to optimize the data sending process to them, you have
to write the records ordering them by the master address, that is, firstly, those that have
the same master, then all of the following one…

Send Process
6) Save the file “Tx.txt”.

7) As a general rule, every time you want to send the content of the file “Tx.txt”, the process
is divided into three steps:
7.1) Create the file “ctrl.txt” and write ‘S’, indicating Stop, save. The Dibalcom will
remove once the instruction is collected.
7.2) Create a new file “ctrl.txt” and write ‘R’, indicating Restart, save. The Dibalcom will
remove once the instruction is collected.
7.3) Create a new file “ctrl.txt” and write ‘S’, indicating Start, save. The Dibalcom will
remove once the instruction is collected.

8) When the Dibalcom reads ‘S’ loads the structures with the configuration that reads from
the file “dibctrl.txt”. Then the Dibalcom starts reading the “Tx.txt” file and look at the
master address of the record send, it checks that it is for a defined scale and sends.

9) The Dibalcom will indicate in the “Tx.txt” file in the record’s corresponding line with an
rd
asterisk (*) in the 3 line position.

End Send Process

10) We must check that all the line has been sent. To this end, we read the file “Tx.txt” and
we check that all the lines have an asterisk (*) in the position 3.

11) If any line has not been sent by any reason, we repeat the procedure from the step 6.

34
Manual

9.4. End of day

1) To do an end of day the first thing is to download from the scale all the sales it could have
stored. To that end, it will need to execute all the steps of the previous point “Download
Sales”.
2) Once received all the sales, we create a “ctrl.txt” file and write ‘S’, indicating Stop. Save.
The Dibalcom will remove once the instruction is collected.

3) Create again the “ctrl.txt” file and write ‘R’, indicating Restart, save. The Dibalcom will
remove once the instruction is collected.

4) Delete the file “Tx.txt”.

5) Open the file “Tx.txt” the end of day KB record and the KB in charge of deleting the
accumulated.
- The end of day KB record is:
04KB0006631313131361
- The KB record for deleting the accumulated is:
04KB001064491212121212121261
The Dibalcom will in charge of completing the record with zeros until 130.

Send Process
6) Save the file “Tx.txt”.

7) As a general rule, every time you want to send the content of the file “Tx.txt”, the process
is divided into three steps:
7.1) Create the file “ctrl.txt” and write ‘S’, indicating Stop, save. The Dibalcom will
remove once the instruction is collected.
7.2) Create a new file “ctrl.txt” and write ‘R’, indicating Restart, save. The Dibalcom will
remove once the instruction is collected.
7.3) Create a new file “ctrl.txt” and write ‘S’, indicating Start, save. The Dibalcom will
remove once the instruction is collected.

8) When the Dibalcom reads ‘S’ loads the structures with the configuration that reads from
the file “dibctrl.txt”. Then the Dibalcom starts reading the “Tx.txt” file and look at the
master address of the record send, it checks that it is for a defined scale and sends.

9) The Dibalcom will indicate in the “Tx.txt” file in the record’s corresponding line with an
rd
asterisk (*) in the 3 line position.
End Send Process
10) When the record KB have been sent, we keep polling from time to time the “Rx.txt” file
until receive the record F9, which is the last record that the scale sends.
The record F9 is the Total Accumulated Sales. The receiving time will vary depending on
the accumulated sales.

11) If any line has not been sent by any reason, we repeat the procedure from the step 6.

49-MDIBALCOMEN01 35
 Dibalcom
10. A SERIES’ SCALES COMMUNICATION EXAMPLES
Some examples are shown below where you can display the different records that must be sent to
an A series’ scale with address 02 to perform different operations.
The records for the End of Day with deletion, Without deletion, Sales Deletion and Initialization
(Keyboard Simulations, KB) are the same for all Dibal scales, what changes is the rest of the
records that are documented in ComunicationRegister.mdb document and is recommended to
determine the structure of the records that are handled in communications.
The information contained in the records of the following examples are that in situations of Polling
and Selecting explained above appears as Data.

10.1. End of day with deletion and Start of day

When we connect to the scale, the first thing is to give us the sales it has in the communications
buffer.
Sales’ Records (Scales
PC)
02F500A000010001683200001000127001150000914300012900110000076890000000000000000
000000000000000000000000000000000000000001106190402
02F500A000020000914300002000127001150000914300000000000000000000000000000000000
000000000000000000000000000000000000000001106190402

In this case we receive the sales number one and two.

After a series of polls (fifty exactly) in which they do not reach more sales we send the keyboard
simulation to the scale in order to do the End of day with Sales deletion. First of all, we send the
record Z0 in order to make the scales’ group and the records we send to the scales the same.

Configuration Record (PC
Scale)

02Z0000204191235000000110000000000000000000000000000000000000000000000000000000
000000

Keyboard Simulation Record for the End of day with deletion (PC
Scale)
02KB0006630101010161

The scale will send the accumulated items, vendors and the total group, before deleting these
accumulated.
Removing Employees Records (Scale
PC)
0224000000100890000300000364780000300000364780000000000000000000300000338820000
400000025960000000000000000089000100000001235190402

Accumulated Employee Record (Scale
PC)

0227000000100012700000091430001290000007689000618000001705000000000000
025960000000000000000000000000000000000000000000000000000000

Items Accumulated Records (Scale
PC)

0236000000700000000000004000000259600004000127000002300000018286000020001290000
011000000076890000100054500000001000006450000001000
0236000000700061700000110000001705000001000618000001100000017050000010000000000
000000000000000000000000000000000000000000000000000

36
Manual
Total Records for payment mode (Scale
PC)
02Y500?100127171?200000000?300000000?400000000?50000000000000000000000000000000
000000000000000000000000000000000000000000000000000

Total Group’s Records (Scale
PC)

0229001000700006000012717100006000012717100000000000000000005000006007500005000
006709600000000000000000000000000000000001235190402

Once received the Record 29, we know that the scale have just delete all the accumulated and it is
ready to begin with the Start of day.

Start of day Record (PC
Scale)

02KB0006630101010161

Receipts’ Headers and Footers Records (PC
Scale)

022800104 204 304 404
022800504 604 704 804

Records with the sections’ names (PC
Scale)

02Z10000 01 02 03 04
02Z10005 06 07 08 09
02Z10010 11 12 13 14
02Z10015 16 17 18 19

Records with the departments’ names (PC
Scale)

02Z2000 1 2 3 4 5 6

Records with the EANs formats (PC
Scale)

02Z30001 02 03 04 05 06 07 08
02Z30009 10

Records with the Currencies (PC
Scale)

02Z400000000000000000000000000000000000000000000000000000000000000

Records with the Tare keys (PC
Scale)

02Z500100000200000300000400000500000

Records with the VAT types (PC
Scale)

02Z600100000200000300000400000500000

Keyboard Simulation to Register the employees (PC
Scale)

02KB001062010757575757455961
02KB001062011957575757465961
02KB001062013157575757475961

49-MDIBALCOMEN01 37
 Dibalcom
Registering employees Records (Scale
PC)
0223000000100000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000001236190402
0223000000200000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000001236190402
0223000000300000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000001236190402

Vendors’ Description Records (PC
Scale)

02310000001Vendor 1
02310000002Vendor 2
02310000003Vendor 3

38
Manual

10.2. End of day without deletion, Sales deletion and Start of

day
When we connect to the scale, the first thing is to give us the sales it has in the communications
buffer.

Sales’ Records (Scales
PC)

02F500A000010001683200001000127001150000914300012900110000076890000000000000000
000000000000000000000000000000000000000001106190402
02F500A000020000914300002000127001150000914300000000000000000000000000000000000
000000000000000000000000000000000000000001106190402

In this case we receive the sales number one and two.

After a series of polls (fifty exactly) in which they do not reach more sales we send the keyboard
simulation to the scale in order to do the End of day without Sales deletion. First of all, we send the
record Z0 in order to make the scales’ group and the records we send to the scales the same.

Configuration Record (PC
Scale)

02Z0000204191235000000110000000000000000000000000000000000000000000000000000000
000000

Keyboard Simulation Record for the End of day without deletion (PC
Scale)
02KB0006631313131361

The scale will send the accumulated items, vendors and the total group, before deleting these
accumulated.

Removing Employees Records (Scale
PC)

0224000000100890000300000364780000300000364780000000000000000000300000338820000
400000025960000000000000000089000100000001235190402

Accumulated Employee Record (Scale
PC)

0227000000100012700000091430001290000007689000618000001705000000000000
025960000000000000000000000000000000000000000000000000000000

Items Accumulated Records (Scale
PC)

0236000000700000000000004000000259600004000127000002300000018286000020001290000
011000000076890000100054500000001000006450000001000
0236000000700061700000110000001705000001000618000001100000017050000010000000000
000000000000000000000000000000000000000000000000000

Total Records for payment mode (Scale
PC)

02Y500?100127171?200000000?300000000?400000000?50000000000000000000000000000000
000000000000000000000000000000000000000000000000000

Total Group’s Records (Scale
PC)

0229001000700006000012717100006000012717100000000000000000005000006007500005000
006709600000000000000000000000000000000001235190402

49-MDIBALCOMEN01 39
 Dibalcom
Once received the Record 29, we know that the scale does not send more accumulated information
and we delete the sales.
02KB0006631313131361
02KB001064491212121212121261

Having received the information, the scale deletes all the accumulated and it is ready to begin with
the Start of day.

Start of day Record (PC
Scale)

02KB0006630101010161

Receipts’ Headers and Footers Records (PC
Scale)

022800104 204 304 404
022800504 604 704 804

Records with the sections’ names (PC
Scale)

02Z10000 01 02 03 04
02Z10005 06 07 08 09
02Z10010 11 12 13 14
02Z10015 16 17 18 19

Records with the departments’ names (PC
Scale)

02Z2000 1 2 3 4 5 6

Records with the EANs formats (PC
Scale)

02Z30001 02 03 04 05 06 07 08
02Z30009 10

Records with the Currencies (PC
Scale)

02Z400000000000000000000000000000000000000000000000000000000000000

Records with the Tare keys (PC
Scale)

02Z500100000200000300000400000500000

Records with the VAT types (PC
Scale)

02Z600100000200000300000400000500000

Keyboard Simulation to Register the employees (PC
Scale)

02KB001062010757575757455961
02KB001062011957575757465961
02KB001062013157575757475961

40
Manual
Registering employees Records (Scale
PC)
0223000000100000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000001236190402
0223000000200000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000001236190402
0223000000300000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000001236190402

Vendors’ Description Records (PC
Scale)

02310000001Vendor 1
02310000002Vendor 2
02310000003Vendor 3

49-MDIBALCOMEN01 41
 Dibalcom

10.3. Initialization
When we connect to the scale, the first thing is to give us the sales it has in the communications
buffer.
Sales’ Records (Scales
PC)
02F500A000010001683200001000127001150000914300012900110000076890000000000000000
000000000000000000000000000000000000000001106190402
02F500A000020000914300002000127001150000914300000000000000000000000000000000000
000000000000000000000000000000000000000001106190402

In this case we receive the sales number one and two.

After a series of polls (fifty exactly) in which they do not reach more sales we send the keyboard
simulation to the scale in order to do an Initialization. First of all, we send the record Z0 in order to
make the scales’ group and the records we send to the scales the same.

Group’s Configuration Record (PC
Scale)

02Z0000204191235000000110000000000000000000000000000000000000000000000000000000
000000

Keyboard Simulation Record for the Initialization (PC
Scale)

02KB00116337373737373737373761

Items Data Records (PC
Scale)

02X100M000129SALCHICHA PICANTE 069900000000000000000000
4000000000050100000000000000000
02X100M000545TXANGURRO 06450000000000000010000
0000000000050100000000000000000
02X100M000617FILETE BRAZUELO 155000000000000000000000
4000000000052000000000000000000

Item’s ingredients Records (PC
Scale)

02X2000001291 S A L C H I C H A P I C A N T E 0005451 T X A N G U R R O A L H O R N O
02X2000006171 T E R N E R A N A T U R A L 0006181 T E R N E R A N A T U R A L
02X2000006191 T E R N E R A N A T U R A L 0006201 T E R N E R A N A T U R A L
02X2000006211 T E R N E R A N A T U R A L 0006221 T E R N E R A N A T U R A L
02X2000006241 T E R N E R A N A T U R A L 0007261 T E R N E R A G A L L E G A

Receipts’ Headers and Footers Records (PC
Scale)

022800104 204 304 404
022800504 604 704 804

Records with the sections’ names (PC
Scale)

02Z10000 01 02 03 04
02Z10005 06 07 08 09

42
Manual
02Z10010 11 12 13 14
02Z10015 16 17 18 19

Records with the departments’ names (PC
Scale)

02Z2000 1 2 3 4 5 6

Records with the EANs formats (PC
Scale)

02Z30001 02 03 04 05 06 07 08
02Z30009 10

Records with the Currencies (PC
Scale)

02Z400000000000000000000000000000000000000000000000000000000000000

Records with the Tare keys (PC
Scale)

02Z500100000200000300000400000500000

Records with the VAT types (PC
Scale)

02Z600100000200000300000400000500000

Keyboard Simulation to Register the employees (PC
Scale)

02KB001062010757575757455961
02KB001062011957575757465961
02KB001062013157575757475961

Registering employees Records (Scale
PC)

0223000000100000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000001236190402
0223000000200000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000001236190402
0223000000300000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000001236190402

Vendors’ Description Records (PC
Scale)

02310000001Vendedor 1
02310000002Vendedor 2
02310000003Vendedor 3

49-MDIBALCOMEN01 43
 Dibalcom

11. L SERIES’ SCALES COMMUNICATION EXAMPLES

Some examples are shown below where you can display the different records that must be sent to
an L series’ scale with address 16 to perform different operations.

The records for the End of Day with deletion, Without deletion, Sales Deletion and Initialization
(Keyboard Simulations, KB) are the same for all Dibal scales, what changes is the rest of the
records that are documented in ComunicationRegister.mdb document and is recommended to
determine the structure of the records that are handled in communications.

11.1. End of day with deletion and Start of day

When we connect to the scale, the first thing is to give us the sales it has in the communications
buffer.
Sales’ Records (Scales
PC)
16LA09E000090000000000000000069000012862410000100000000690000000000000000000000
000000000000000000000000000000000000000001218060409
16LA09E000200000000000000000017000012863740016500000000170000000000000000000000
000000000000000000000000000000000000000001218060409

In this case we receive two sales.

After a series of polls (fifty exactly) in which they do not reach more sales we send the keyboard
simulation to the scale in order to do the End of day with Sales deletion. First of all, we send the
record Z0 in order to make the scales’ group and the records we send to the scales the same.

Configuration Record (PC
Scale)

16Z009090406113200000011000001120000000000300210002000010025ANNNNEEEEE2CCCC
CCEEEEE0000000000000000000000000000

Keyboard Simulation Record for the End of day with deletion (PC
Scale)
16KB0906630101010161

The scale will send the accumulated items, vendors and the total group, before deleting these
accumulated.
Removing Employees Records (Scale
PC)
16F4090000102340000300000002760000300000002760000000000000000000000000000000000
000000000000000000000000000235000000000001536060409

Accumulated Employee Record (Scale
PC)

16F7090000109999900000002760000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000

Items Accumulated Records (Scale
PC)

16F6090000128624100000001000000006900001286374000001650000000017000012865340000
000100000001900000100000000000000000000000000000000

Total Records for payment mode (Scale
PC)

44
Manual
16Y509?100000276?200000000?300000000?400000000?50000000002370000000000000000000
000000000000000000000000000000000000000000000000000

Total VAT Records (Scale
PC)

1639090000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000

Total Group’s Records (Scale
PC)

16F9091000100003000000027600003000000027600000000000000000001000000001700002000
000025900000000000000000000000000000000001536060409

Once received the Record F9, we know that the scale have just delete all the accumulated and it is
ready to begin with the Start of day.

Start of day Record (PC
Scale)

16KB0906630101010161

EANs’ Items Records (PC
Scale)

16AS092341232CCCCCCEEEEEQ2348612CCCCCCEEEEEQ2862412CCCCCCEEEEEQ286374
2CCCCCCEEEEEQ2865342CCCCCCEEEEEQ3061062CCCCCCEEEEEQ0000000000

Records with the departments’ names (PC
Scale)

16Z2090 1 2 3 4 5 6
00000000000000000000000000000000000000000000000

Records with the EANs formats (PC
Scale)

16Z30901 02 03 04 05 06 07 08
000000000000
16Z30909 10 000000000000

Records with the Currencies (PC
Scale)

16LP09A000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000FFFF0
16LP09A1
0000000000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000

Records with the Tare keys (PC
Scale)

16Z5091000002000003000004000005000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000

IVA’s Type Records (PC
Scale)

16Z6091000002000003000004000005000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000

Header’s Font Record (PC
Scale)

16LF090100162823000000000000121C27374453637384919DADB9000000000000000000000000
0000000000000000000000000000000000000000000000000000

49-MDIBALCOMEN01 45
 Dibalcom
Receipts’ Headers and Footers Records (PC
Scale)
16L709A02020100050001SUPERMERCADO
16L709A02030100000001SECCION PANADERIA
16L709A02040100000000
16L709A02050101000051GRACIAS POR SU COMPRA

Registering employees Records (Scale
PC)

16X50900001vendor1 0100002vendor2 0200003vendor3
030000000000000000000000000
16X50900004vendor4 0400005vendor5 0500006vendor6
060000000000000000000000000
16X50900007vendor7 0700008vendor8 0800009vendor9
090000000000000000000000000
16X50900010vendor10 1000011vendor11 1100012vendor12
120000000000000000000000000
16X50900013vendor13 1300014vendor14 1400015vendor15
150000000000000000000000000
16X50900016vendor16 1600017vendor17 1700018vendor18
180000000000000000000000000
16X50900019vendor19 1900020vendor20
200000000000000000000000000000000000000000000000000000000000

46
Manual

11.2. End of day without deletion, Sales deletion and Start of

day
When we connect to the scale, the first thing is to give us the sales it has in the communications
buffer.
Sales’ Records (Scales
PC)
16LA09E000090000000000000000069000012862410000100000000690000000000000000000000
000000000000000000000000000000000000000001218060409
16LA09E000200000000000000000017000012863740016500000000170000000000000000000000
000000000000000000000000000000000000000001218060409

In this case we receive two sales.

After a series of polls (fifty exactly) in which they do not reach more sales we send the keyboard
simulation to the scale in order to do the End of day without Sales deletion. First of all, we send the
record Z0 in order to make the scales’ group and the records we send to the scales the same.

Configuration Record (PC
Scale)

16Z009090406113200000011000001120000000000300210002000010025ANNNNEEEEE2CCCC
CCEEEEE0000000000000000000000000000

Keyboard Simulation Record for the End of day without deletion (PC
Scale)
16KB0906631313131361

The scale will send the accumulated items, vendors and the total group, before deleting these
accumulated.
Removing Employees Records (Scale
PC)
16F4090000102340000300000002760000300000002760000000000000000000000000000000000
000000000000000000000000000235000000000001536060409

Accumulated Employee Record (Scale
PC)

16F7090000109999900000002760000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000

Items Accumulated Records (Scale
PC)

16F6090000128624100000001000000006900001286374000001650000000017000012865340000
000100000001900000100000000000000000000000000000000

Total Records for payment mode (Scale
PC)

16Y509?100000276?200000000?300000000?400000000?50000000002370000000000000000000
000000000000000000000000000000000000000000000000000

Total VAT Records (Scale
PC)

1639090000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000

Total Group’s Records (Scale
PC)

16F9091000100003000000027600003000000027600000000000000000001000000001700002000
000025900000000000000000000000000000000001536060409

49-MDIBALCOMEN01 47
 Dibalcom
Once received the Record F9, we know that the scale have just delete all the accumulated and it is
ready to begin with the Sales deletion.
16KB091064491212121212121261

Received this information the scale deletes the accumulated and we can begin with the Start of day.

Start of day Record (PC
Scale)

16KB0906630101010161

EANs Items Records (PC
Scale)

16AS092341232CCCCCCEEEEEQ2348612CCCCCCEEEEEQ2862412CCCCCCEEEEEQ286374
2CCCCCCEEEEEQ2865342CCCCCCEEEEEQ3061062CCCCCCEEEEEQ0000000000

Records with the departments’ names (PC
Scale)

16Z2090 1 2 3 4 5 6
00000000000000000000000000000000000000000000000

Records with the EANs formats (PC
Scale)

16Z30901 02 03 04 05 06 07 08
000000000000
16Z30909 10 000000000000

Records with the Currencies (PC
Scale)

16LP09A000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000FFFF0
16LP09A100000000000000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000

Records with the Tare keys (PC
Scale)

16Z5091000002000003000004000005000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000

Records with the VAT types (PC
Scale)

16Z6091000002000003000004000005000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000

Headers Font Record (PC
Scale)

16LF090100162823000000000000121C27374453637384919DADB9000000000000000000000000
0000000000000000000000000000000000000000000000000000

Receipts’ Headers and Footers Records (PC
Scale)

16L709A02020100050001SUPERMERCADO DIBAL
16L709A02030100000001SECCION PANADERIA
16L709A02040100000000
16L709A02050101000051GRACIAS POR SU COMPRA

48
Manual
Registering employees Records (PC
Scale)
16X50900001vendor1 0100002vendor2 0200003vendor3
030000000000000000000000000
16X50900004vendor4 0400005vendor5 0500006vendor6
060000000000000000000000000
16X50900007vendor7 0700008vendor8 0800009vendor9
090000000000000000000000000
16X50900010vendor10 1000011vendor11 1100012vendor12
120000000000000000000000000
16X50900013vendor13 1300014vendor14 1400015vendor15
150000000000000000000000000
16X50900016vendor16 1600017vendor17 1700018vendor18
180000000000000000000000000
16X50900019vendor19 1900020vendor20
200000000000000000000000000000000000000000000000000000000000

49-MDIBALCOMEN01 49
 Dibalcom

11.3. Initialization
When we connect to the scale, the first thing is to give us the sales it has in the communications
buffer.

Sales’ Records (Scales
PC)

16LA09E000090000000000000000069000012862410000100000000690000000000000000000000
000000000000000000000000000000000000000001218060409
16LA09E000200000000000000000017000012863740016500000000170000000000000000000000
000000000000000000000000000000000000000001218060409

In this case we receive the two sales.

After a series of polls (fifty exactly) in which they do not reach more sales we send the keyboard
simulation to the scale in order to do the Initialization. First of all, we send the record Z0 in order to
make the scales’ group and the records we send to the scales the same.

Group Configuration Record (PC
Scale)

16Z009090406113200000011000001120000000000300210002000010025ANNNNEEEEE2CCCC
CCEEEEE0000000000000000000000000000

Keyboard Simulation Record for the Initialization (PC
Scale)

16KB09116337373737373737373761

Item data Records (PC
Scale)

16L209M286241 PAN SERRANO 000000690000000000000000
16L3092862411000002000000000000000000000000000090000000000000000000000000000000
000000000000000000000000001000000000000000000000000
16L209M286374 BANDEJA DE COCOS 000001000000000000000000
16L3092863740000000000000000000000000000000000090000000000000000000000000000000
000000000000000000000000001000000000000000000000000
16L209M286534 TARTALETA FRESA X 2 000001900000000000000000
16L3092865341000003000000000000000000000000000090000000000000000000000000000000
000000000000000000000000001000000000000000000000000

Items ingredients Records (PC
Scale)

16L409234861B 286241B 00000000000000
16X40928624101INGREDIENTES:HARINA DE TRIGO AGUA SALLEVADURA Y
MEJORANTESPANARIOS AUTORIZADOS CONSERVAR EN LUGARFRESCO Y SECO
16L409286374B 286534B 00000000000000
16X40928637401
16L409286374B 286534B 00000000000000
16X40928653401ING:TARTALETA AZUCAR BRILLONATA FRESAS

EANs’ items Records (PC
Scale)

16AS092341232CCCCCCEEEEEQ2348612CCCCCCEEEEEQ2862412CCCCCCEEEEEQ286374
2CCCCCCEEEEEQ2865342CCCCCCEEEEEQ3061062CCCCCCEEEEEQ0000000000

50
Manual
Records with the departments’ names (PC
Scale)
16Z2090 1 2 3 4 5 6
00000000000000000000000000000000000000000000000

Records with the EANs formats (PC
Scale)

16Z30901 02 03 04 05 06 07 08 000000000000
16Z30909 10 000000000000

Records with the Currencies (PC
Scale)

16LP09A000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000FFFF0
16LP09A100000000000000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000

Records with the Tare keys (PC
Scale)

16Z5091000002000003000004000005000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000

Records with the VAT types (PC
Scale)

16Z6091000002000003000004000005000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000

Header Font Record (PC
Scale)

16LF090100162823000000000000121C27374453637384919DADB9000000000000000000000000
0000000000000000000000000000000000000000000000000000

Receipts’ Headers and Footers Records (PC
Scale)

16L709A02020100050001SUPERMERCADO DIBAL
16L709A02030100000001SECCION PANADERIA
16L709A02040100000000
16L709A02050101000051GRACIAS POR SU COMPRA

Registering employees Records (Scale
PC)

16X50900001vendor1 0100002vendor2 0200003vendor3
030000000000000000000000000
16X50900004vendor4 0400005vendor5 0500006vendor6
060000000000000000000000000
16X50900007vendor7 0700008vendor8 0800009vendor9
090000000000000000000000000
16X50900010vendor10 1000011vendor11 1100012vendor12
120000000000000000000000000
16X50900013vendor13 1300014vendor14 1400015vendor15
150000000000000000000000000
16X50900016vendor16 1600017vendor17 1700018vendor18
180000000000000000000000000
16X50900019vendor19 1900020vendor20
200000000000000000000000000000000000000000000000000000000000

49-MDIBALCOMEN01 51
The information content in this manual can be modified without previous notification.
Ref.: 49-MDIBALCOMES01 13/01/2011
Version: 10.00