L

DAD/DRIVER

SOFTWARE INTEGRATION GUIDE

Fieldbus Master

Fieldbus Slave
Node #2
Fieldbus Slave
Node #3

Fieldbus Slave
Node #1

Fieldbus Communication
Datalogic S.r.l.
Via S. Vitalino, 13
40012 Calderara di Reno (BO)
Italy
Tel. +39 051 3147011
Fax +39 051 3147205

© 2023 Datalogic S.p.A. and /or its affiliates

All rights reserved. Without limiting the rights under copyright, no part of this documentation may be
reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means, or
for any purpose, without the express written permission of Datalogic S.p.A. and/or its affiliates.
Owners of Datalogic products are hereby granted a non-exclusive, revocable license to reproduce and
transmit this documentation for the purchaser's own internal business purposes. Purchaser shall not
remove or alter any proprietary notices, including copyright notices, contained in this documentation and
shall ensure that all notices appear on any reproductions of the documentation.
Electronic versions of this document may be downloaded from the Datalogic website ([Link]-
[Link]). If you visit our website and would like to make comments or suggestions about this or other
Datalogic publications, please let us know via the "Contact" page.

Disclaimer
Datalogic has taken reasonable measures to provide information in this manual that is complete and accu-
rate, however, Datalogic shall not be liable for technical or editorial errors or omissions contained herein,
nor for incidental or consequential damages resulting from the use of this material. Datalogic reserves the
right to change any specification at any time without prior notice.

Trademarks
Datalogic and the Datalogic logo are registered trademarks of Datalogic S.p.A. in many countries, including
the U.S.A. and the E.U.
All other trademarks and brands are property their respective owners.

Patents
See [Link] for patent list.
TABLE OF CONTENTS

CHAPTER 1. INTRODUCTION..................................................................................... 1
About this Manual ............................................................................................................ 1
Manual Conventions ............................................................................................................................1
Technical Support ............................................................................................................ 1
Support Through the Website .............................................................................................................1
Reseller Technical Support .................................................................................................................1

CHAPTER 2. FIELDBUS COMMUNICATION ................................................................. 2

Data Exchange ................................................................................................................. 2
Datalogic Flow Control Mode (FCM) .................................................................................. 3
Flow Control Drivers ........................................................................................................ 3

CHAPTER 3. FCM WITH DAD DRIVER......................................................................... 5

Control Field .................................................................................................................... 6
SAP Field ........................................................................................................................ 7
Length Field .................................................................................................................... 8
Data Transmission from the device to PLC ........................................................................ 8
Data Transmission from PLC to the device ...................................................................... 10
Resynchronization .......................................................................................................... 12
Fragmentation and Reassembling ................................................................................... 13
SAP Services ................................................................................................................. 16
DAD Internal Queues ...................................................................................................... 16

CHAPTER 4. DATA CONSISTENCY ........................................................................... 18

Data Consistency with DAD Driver .................................................................................. 18

CHAPTER 5. NETWORK CONFIGURATION ................................................................ 21

Configuration Files for Fieldbus ...................................................................................... 21

INTEGRATION GUIDE iii

iv FIELDBUS DAD DRIVER
CHAPTER 1
INTRODUCTION

ABOUT THIS MANUAL

To increase communication reliability or to manage large labels, Datalogic Flow Control
Mode can be selected on the Fieldbus device. In this case, the corresponding driver
must be implemented on the Fieldbus Master (PLC) side.
This document is intended to provide all the necessary information to implement Flow
Control on PLC side.

Manual Conventions
The following conventions are used in this document:
The symbols listed below are used in this manual to notify the device of key issues or
procedures that must be observed when using the device:

NOTE: Notes contains information necessary for properly diagnosing,

repairing and operating the device.

TECHNICAL SUPPORT

Support Through the Website

Datalogic provides several services as well as technical support through its website. Log
on to ([Link]).
For quick access, from the home page click on the search icon , and type in the name of
the product you’re looking for. This allows you access to download Data Sheets, Manu-
als, Software & Utilities, and Drawings.
Hover over the Support & Service menu for access to Services and Technical Support.

Reseller Technical Support

An excellent source for technical assistance and information is an authorized Datalogic
reseller. A reseller is acquainted with specific types of businesses, application software,
and computer systems and can provide individualized assistance.

INTEGRATION GUIDE 1
CHAPTER 2
FIELDBUS COMMUNICATION

DATA EXCHANGE
The Fieldbus Master is usually a PLC. Sometimes it could be a PC-based device as well.
The Datalogic device is always a Slave in the Fieldbus network.

Fieldbus Master

Fieldbus Slave
Node #2
Fieldbus Slave
Node #3

Fieldbus Slave
Node #1

Basically, two shared memory areas (Exchange Areas) exist between SLAVE and MASTER
so both devices provide information to each other. Exchange areas are physically placed
in the Fieldbus device inside the SLAVE.

2 FIELDBUS DAD DRIVER

 DATALOGIC FLOW CONTROL MODE (FCM)

Input and output areas always refer to the Master: this means that the slave writes to
the Input buffer and the PLC writes to the Output buffer.
Dimensions of exchange areas can be set to different values by the PLC through the spe-
cific Fieldbus Configuration file (i.e. GSD file for Profibus) or by the slave's configuration
program.

DATALOGIC FLOW CONTROL MODE (FCM)

The Datalogic Flow Control Mode is a powerful way to manage and optimize the com-
munication with the Fieldbus Master. By enabling the FCM, a few bytes of the exchange
areas are reserved for driver operations and the rest are used by the application layer.

The reserved bytes are used to implement many different features, such as:
• Flow-control and corresponding buffering in both directions
• Fragmentation and reassembling of data longer than the exchange area sizes
• Synchronization of flow control numbers
• Service Access Point oriented communication
• Length information

NOTE: If the Datalogic Flow Control is disabled, all the bytes of the
exchange areas are used by the application layer. The input area is updated
whenever a new reading event has to be transferred to the Master station.

• In this situation, the Master must read the input area before it changes due to a
new message, typically new barcode occurrence.
• Moreover, two occurrences of the same barcode cannot be understood, since the
input area does not change.
• In addition, if application data is longer than input area sizes, data is automatically
truncated.
FCM can be selected by means of the Data Flow Control parameter.

FLOW CONTROL DRIVERS

The Flow Control driver is a layer that is built upon the intrinsic data exchange mecha-
nism. Such a layer is required because the intrinsic data exchange mechanism is not
message oriented.
In the following figure the complete Stack is represented:

INTEGRATION GUIDE 3
FIELDBUS COMMUNICATION

As described previously, it can be selected separately on the device by means of the

device configuration tool. Obviously, the corresponding driver must be implemented on
the Fieldbus Master (PLC) side.

4 FIELDBUS DAD DRIVER

CHAPTER 3
FCM WITH DAD DRIVER

From now the Input Area will be referred to as a buffer made up of InputAreaSize bytes:
IN[0] IN[1] IN[2] ... IN[InputAreaSize - 1]

and the Output Area as a buffer made up of OutputAreaSize bytes:

OUT[0] OUT[1] OUT[2] ... OUT[OutputAreaSize - 1]

Only the first three bytes are used by the DAD Driver layer in both buffers:

Control Field Used to issue and control the driver primitives such as flow-
(byte 0) control, fragmentation and resynchronization.
Used to distinguish among different services and to provide
Service Access Point Field future expandability. (Since this SAP definition is introduced
(byte 1) by the DAD Driver, it must not be confused with the SAP that
is defined by the international standard).
Contains the number of bytes used by the application layer:
Length Field (see also note below)
(byte 2) Length Field ≤ (InputAreaSize - 3) for the Input Area
Length Field ≤ (OutputAreaSize - 3) for the Output Area.

INTEGRATION GUIDE 5
FCM WITH DAD DRIVER

NOTE: If Data Consistency is enabled, then the last byte is used for packet
integrity and therefore the bytes available to the application are reduced by
1. See Chapter 4, Data Consistency for details.

The Application Data buffer holds useful information, typically the barcode messages,
processed by the application program. IN[3] contains the first significant byte of the
Application Data buffer (the same first byte you would see if the device transmitted the
barcode buffer onto a serial port instead of the Fieldbus interface).
The structure of the application buffer and its length strictly depend on the selected
data format on the device. Barcode messages longer than (InputAreaSize - 3) will be
split in pieces through an automatic fragmentation process (see "Fragmentation and
Reassembling" on page 13).

CONTROL FIELD
This is the core of the flow-controlled communication.
The Input Area structure reserves bit 0 and bit 1 of IN[0] for handshake purposes while
the Output Area structure, which is symmetrical, reserves bit 0 and 1 of OUT[0].
At any time, the Master station can make a resynchronization request by means of bit 2
of the Output Area. This process, which resets the synchronization numbers (bit 0 and
bit 1 of both Input and Output areas), has to be acknowledged by the Slave on bit 2 of
the Input Area.
Bit 3 is used to control a fragmentation sequence in both directions.
Bit 7 is always set to 1.

6 FIELDBUS DAD DRIVER

 SAP FIELD

TxBufferFull toggles when Slave has made available new

IN[0].bit0
Input Area data
RxBufferEmpty toggles when Output Area data has been
IN[0].bit1
read by Slave
Resync Acknowledge set to 1 as an acknowledge to a
IN[0].bit2 resync request. With this bit, the master can detect a slave is
on line.
More Bit is 1 when this is not the last piece of a fragmenta-
IN[0].bit3
tion sequence while it is 0 when this is the last piece
IN[0].bit4,5,6,7 Set to 0, 0, 0, 1 when DAD messaging protocol is used

TxBufferEmpty must toggle when Input Area data has been

OUT[0].bit0
read by Master
RxBufferFull must toggle when Master makes available
OUT[0].bit1
new Output Area data
Resync Request set to 1 for one second to resynchronize
OUT[0].bit2 the slave. After resynchronization, all 4 handshake bits are
set to 0.
More Bit must be 1 when this is not the last piece of a frag-
OUT[0].bit3
mentation sequence and it must be 0 when this is the last
OUT[0].bit4,5,6,7 Set to 0, 0, 0, 1 when DAD messaging protocol is used

SAP FIELD
SAP (Service Access Point) is an identifier that is used to implement multiple services
sharing the same communication channel between two remote stations.
The following values have been defined:
SAP = 0 Used to transfer information messages between the device and the PLC
SAP = 255 Reserved for driver services (see details in paragraph 2.8)
All other SAP values are free, and they could be used by dedicated application programs
after agreement between the application programs themselves.

INTEGRATION GUIDE 7
FCM WITH DAD DRIVER

LENGTH FIELD
The Application layer uses all or a part of the remaining bytes of the Exchange Area buf-
fers that are not used by the DAD Driver. The Length Field is introduced to keep the
information of how many bytes are really used by the Application Layer.
A fragment that is not the last one of a fragmentation sequence must fill this field with
[InputAreaSize - 3] (or [OutputAreaSize - 3]), depending on whether it is an Input or an
Output fragment. Otherwise this field gets a value that is less than or equal to [InputAr-
eaSize - 3].

DATA TRANSMISSION FROM THE DEVICE TO PLC

This paragraph describes how it is possible to exchange messages with flow control. The
communication mechanism is simple:

• IN[0].bit0 [ A ] is used by the device to notify that “Slave has written a new data so
Master can read it”
• OUT[0].bit0 [ B ] must be used by PLC to notify that “Master has read last data so
Slave can send next message”
This happens each time bit A (or B) changes its state (toggles). Bit level doesn't matter,
only the transition has to be considered.

The following state machine shows data transmission from Slave to Master. Please note
that each cycle transfers two data messages.

8 FIELDBUS DAD DRIVER

 DATA TRANSMISSION FROM THE DEVICE TO PLC

Let's analyze a typical data exchange based on the following settings:

• Flow Control = DAD Driver
• Input Area Size = 16
• Output Area Size = 8

1. After power-on, Input and Output areas are generally filled by zero. According to
DAD driver implementation, Input area has Control Field = 80Hex and SAP = 00Hex.

Input 80He 00He

00Hex 00Hex 00Hex 00Hex 00Hex 00Hex 00Hex 00Hex 00Hex 00Hex 00Hex 00Hex 00Hex 00Hex
Area x x

Output 00Hex 00Hex 00Hex 00Hex 00Hex 00Hex 00Hex 00Hex

Area

2. PLC must also set the Control Field of Output area properly, as long as DAD mes-
saging protocol is used.

Input 80Hex 00Hex 00Hex 00Hex 00Hex 00Hex 00Hex 00Hex 00Hex 00Hex 00Hex 00Hex 00Hex 00Hex 00Hex 00Hex
Area

Output 80He 00He

00Hex 00Hex 00Hex 00Hex 00Hex 00Hex
Area x x

3. The device reads a barcode "01234567". Let's assume standard data formatting
with <CR> as terminator. The device toggles bit A.

Input 81He
00Hex
09He 30He 31He 32He 33He 34He 35He 36He 37He 0DHe
00Hex 00Hex 00Hex 00Hex
Area x x x x x x x x x x x

Output 80Hex 00Hex 00Hex 00Hex 00Hex 00Hex 00Hex 00Hex

Area

INTEGRATION GUIDE 9
FCM WITH DAD DRIVER

4. PLC detects transition of bit A so now it can read incoming data (it copies 9 bytes
in its memory from IN[3] on) then toggles bit B as acknowledge.

NOTE: Before the acknowledge, all further barcodes read by the device are
buffered.

Input 81Hex 00Hex 09Hex 30Hex 31Hex 32Hex 33Hex 34Hex 35Hex 36Hex 37Hex
0DHe
00Hex 00Hex 00Hex 00Hex
Area x

Output 81He
00Hex 00Hex 00Hex 00Hex 00Hex 00Hex 00Hex
Area x

5. The device reads a barcode "10DL" and toggles bit A.

Input 80He
00Hex 5Hex 31Hex 30Hex 44Hex
4CHe 0DHe
00Hex 00Hex 00Hex 00Hex 00Hex 00Hex
Area x x x

Output 81Hex 00Hex 00Hex 00Hex 00Hex 00Hex 00Hex 00Hex

Area

6. PLC reads new data message (it copies 7 bytes in its memory from IN[3] on) then
toggles bit B as acknowledge.

Input 80Hex 00Hex 5Hex 31Hex 30Hex 44Hex

4CHe 0DHe
00Hex 00Hex 00Hex 00Hex 00Hex 00Hex
Area x x

Output 80He
00Hex 00Hex 00Hex 00Hex 00Hex 00Hex 00Hex
Area x

7. The device reads ABC and toggles bit A.

Input 81He
00Hex 04Hex 41Hex 42Hex 43Hex
0DHe
00Hex 00Hex 00Hex 00Hex 00Hex 00Hex 00Hex 00Hex 00Hex
Area x x

Output 80Hex 00Hex 00Hex 00Hex 00Hex 00Hex 00Hex 00Hex

Area

8. PLC reads new data message (it copies 4 bytes in its memory from IN[3] on) then
toggles bit B as acknowledge.

Input 81Hex 00Hex 04Hex 41Hex 42Hex 43Hex

0DHe
00Hex 00Hex 00Hex 00Hex 00Hex 00Hex 00Hex 00Hex 00Hex
Area x

Output 81He
00Hex 00Hex 00Hex 00Hex 00Hex 00Hex 00Hex
Area x

9. Data exchange continues...

DATA TRANSMISSION FROM PLC TO THE DEVICE

Analogous to the previous paragraph, flow control works even when data are coming
from the Master towards the Slave. The communication mechanism is based on the
same concepts:

10 FIELDBUS DAD DRIVER

 DATA TRANSMISSION FROM PLC TO THE DEVICE

• OUT[0].bit1 [ C ] must be used by PLC to notify that "Master has written new data
so Slave can read it"
• IN[0].bit1 [ D ] is used by the device to notify that "Slave has read data so Master
can send next message"
This happens each time bit C (or D) changes its state (toggles). Bit level doesn't matter,
only the transition has to be considered.

The following state machine shows data transmission from Master to Slave. Please note
that each cycle transfers two data messages.

INTEGRATION GUIDE 11
FCM WITH DAD DRIVER

RESYNCHRONIZATION
The resynchronization process restarts the messaging protocol from a predefined state.
It may be used either at the Master startup to detect if the Slave is on line or during nor-
mal operations in case of errors requiring a protocol reset procedure.
The process is based on bit two:

• OUT[0].bit2 [ E ] must be used by PLC to request the Resynchronization

• IN[0].bit2 [ F ] is used by the device to acknowledge the request

The following state machine shows the resynchronization cycle, requested by the PLC
and performed together with the device:

12 FIELDBUS DAD DRIVER

 FRAGMENTATION AND REASSEMBLING

Let's analyze the resynchronization process, starting from the previous data exchange
discussed in "Data Transmission from the device to PLC"…

Input 81Hex 00Hex 04Hex 41Hex 42Hex 43Hex

0DHe
00Hex 00Hex 00Hex 00Hex 00Hex 00Hex 00Hex 00Hex 00Hex
Area x

Output 81Hex 00Hex 00Hex 00Hex 00Hex 00Hex 00Hex 00Hex

Area

1. PLC requests resynchronization by setting bit E = 1.

Input 81Hex 00Hex 04Hex 41Hex 42Hex 43Hex

0DHe
00Hex 00Hex 00Hex 00Hex 00Hex 00Hex 00Hex 00Hex 00Hex
Area x

Output 85He
00Hex 00Hex 00Hex 00Hex 00Hex 00Hex 00Hex
Area x

2. The device detects the request and so it resets IN[0].bit0 and IN[0].bit1. Then it
gives an acknowledge back to the PLC by means of bit F.

Input 84He
00Hex 04Hex 41Hex 42Hex 43Hex
0DHe
00Hex 00Hex 00Hex 00Hex 00Hex 00Hex 00Hex 00Hex 00Hex
Area x x

Output 85Hex 00Hex 00Hex 00Hex 00Hex 00Hex 00Hex 00Hex

Area

3. PLC has to reset OUT[0].bit0 and OUT[0].bit1 before completing its request with
bit E = 0.

Input 84Hex 00Hex 04Hex 41Hex 42Hex 43Hex

0DHe
00Hex 00Hex 00Hex 00Hex 00Hex 00Hex 00Hex 00Hex 00Hex
Area x

Output 80He
00Hex 00Hex 00Hex 00Hex 00Hex 00Hex 00Hex
Area x

4. The device completes the acknowledge process by setting bit F = 0.

Input 80He
00Hex 04Hex 41Hex 42Hex 43Hex
0DHe
00Hex 00Hex 00Hex 00Hex 00Hex 00Hex 00Hex 00Hex 00Hex
Area x x

Output 80Hex 00Hex 00Hex 00Hex 00Hex 00Hex 00Hex 00Hex

Area

5. Now Flow Control has been returned to a predefined state. All data exchange bits
in the Control Field are surely zero and data transmission can proceed safely.

FRAGMENTATION AND REASSEMBLING

The fragmentation process is activated whenever Application Data cannot be contained
in the related exchange area. Basically, long messages are split into pieces which are
transmitted separately. Reassembling allows the reconstruction of the whole messages.
The device already implements these functions in the DAD layer, while the PLC needs a
congruent management.
The fragmentation is based on the More Bit (bit 3) in the Control Field byte.

INTEGRATION GUIDE 13
FCM WITH DAD DRIVER

More Bit = 0 indicates that all the information is included within the current message.
When Application Data is longer than (exchange area size - 3), the first partial message
is transmitted having More Bit = 1. Following fragments keep More Bit = 1 and only the
last piece will have More Bit = 0 again. Thanks to this mechanism, the receiver station
may detect the last piece and so reassemble the entire information.
Some notes:
• Intermediate fragments have Length Field = (exchange area size - 3)
• Last fragment has Length Field ≤ (exchange area size - 3)
• Bit0 and Bit1 of both Input and Output areas are independently managed for any
fragment
The following figures show how the Control Byte changes according to the fragmenta-
tion process. Both data flow directions are considered.

Let's analyze a fragmented data exchange based on the following settings:

• Flow Control = DAD Driver
• Input Area Size = 16
• Output Area Size = 8

1. After power-on, Input and Output areas are generally filled by zero. According to
DAD driver implementation, Input area has Control Field = 80Hex and SAP = 00Hex.

Input 80He 00He

00Hex 00Hex 00Hex 00Hex 00Hex 00Hex 00Hex 00Hex 00Hex 00Hex 00Hex 00Hex 00Hex 00Hex
Area x x

Output 00Hex 00Hex 00Hex 00Hex 00Hex 00Hex 00Hex 00Hex

Area

2. PLC must also set the Control Field of Output area properly, as long as DAD mes-
saging protocol is used.

Input 80Hex 00Hex 00Hex 00Hex 00Hex 00Hex 00Hex 00Hex 00Hex 00Hex 00Hex 00Hex 00Hex 00Hex 00Hex 00Hex
Area

14 FIELDBUS DAD DRIVER

 FRAGMENTATION AND REASSEMBLING

Output 80He 00He

00Hex 00Hex 00Hex 00Hex 00Hex 00Hex
Area x x

3. The device reads a barcode with content "01234567890abcde1234567890abcde".

Let's assume standard data <CR> as terminator. In this condition since the whole
message cannot be included in Input Area, the device transmits first fragment
01234567890ab" only (setting More Bit = 1) then it toggles bit A.

Input 89He
00Hex
0DHe 30He 31He 32He 33He 34He 35He 36He 37He 38He 39He 30He 61He 62He
Area x x x x x x x x x x x x x x x

Output 80Hex 00Hex 00Hex 00Hex 00Hex 00Hex 00Hex 00Hex

Area

4. PLC detects transition of bit A so now it can read first incoming fragment (it copies
13 bytes in its memory from IN[3] on) then toggles bit B as acknowledge.

Input 89Hex 00Hex

0DHe
30Hex 31Hex 32Hex 33Hex 34Hex 35Hex 36Hex 37Hex 38Hex 39Hex 60Hex 61Hex 62Hex
Area x

Output 81He
00Hex 00Hex 00Hex 00Hex 00Hex 00Hex 00Hex
Area x

5. The device detects transition of bit B so it sends second fragment

"cde1234567890" (still More Bit = 1) and toggles bit A.

Input 88He
00Hex
0DHe 63He 64He 65He 31He 32He 33He 34He 35He 36He 37He 38He 39He 30He
Area x x x x x x x x x x x x x x x

Output 81Hex 00Hex 00Hex 00Hex 00Hex 00Hex 00Hex 00Hex

Area

6. PLC reads second fragment (it copies 13 bytes in its memory from IN[3] on) then
toggles bit B as acknowledge.

Input 88Hex 00Hex

0DHe
63Hex 64Hex 65Hex 31Hex 32Hex 33Hex 34Hex 35Hex 36Hex 37Hex 38Hex 39Hex 30Hex
Area x

Output 80He
00Hex 00Hex 00Hex 00Hex 00Hex 00Hex 00Hex
Area x

7. The device sends third (last) fragment "abcde<CR><LF>" (finally More Bit = 0) and
toggles bit A.

Input 81He
00Hex
06He 61He 62He 63He 64He 65He 0DHe 00He
00Hex 00Hex 00Hex 00Hex 00Hex 00Hex
Area x x x x x x x x x

Output 80Hex 00Hex 00Hex 00Hex 00Hex 00Hex 00Hex 00Hex

Area

INTEGRATION GUIDE 15
FCM WITH DAD DRIVER

8. PLC reads last fragment (it copies 7 bytes in its memory from IN[3] on) and now
the reassembling can be completed. Then it toggles bit B as acknowledge.

Input 81Hex 00Hex 06Hex 61Hex 62Hex 63Hex 64Hex 65Hex

0DHe
00Hex 00Hex 00Hex 00Hex 00Hex 00Hex 00Hex
Area x

Output 81He
00Hex 00Hex 00Hex 00Hex 00Hex 00Hex 00Hex
Area x

9. Whole message has been completely transmitted.

SAP SERVICES
When SAP = 255, the FLUSH QUEUE is the unique driver service currently available. It
performs flushing of the internal queues and may be issued at any time.
FLUSH QUEUE SERVICE
Request Flush data buffers (issued by the Master station to the device)
Action Flush all information from previous decoding phases
Command accepted/rejected (generated by the device toward the
Response
Master).
Application data areas must be formatted as follows:

REQUEST COMMAND BYTE 3 BYTE 4

Flush data buffer ' [ ' (5B Hex) ' F ' (46 Hex)

RESPONSE COMMAND BYTE 3 BYTE 4

Command accepted ' A ' (41 Hex) ' ' (20 Hex)
Command rejected ' C ' (43 Hex) ' ' (20 Hex)

DAD INTERNAL QUEUES

The Fieldbus device has two internal queues (one for each direction) to keep the appli-
cation events: input queue and output queue.
The input queue is used when a new message (generally a barcode) has to be transmit-
ted by the Fieldbus device before the Master station has generated all the acknowledge
handshakes for each previous transmission.
The output queue is rarely used at the moment.

The queues are sized in the following way:

• 10 elements for the input queue (number of messages buffered from Slave to
Master)
• elements for the output queue (number of messages buffered from Master to
Slave)
The queues may be flushed by the Master station through the SAP=255 primitive. This is
generally done at the Master startup if the Master station wants to cancel all the previ-
ous buffers that were generated before its startup. However, the Master station is free
to decide not to cancel them.

16 FIELDBUS DAD DRIVER

CHAPTER 4
DATA CONSISTENCY
When Flow Control is used, the Data Consistency option is available.
If enabled, the driver implements a specific mechanism to guarantee consistency of
both transmitted and received data over the entire size of the exchange area.

DATA CONSISTENCY WITH DAD DRIVER

As shown in the following figure, the application layer copies the Control Field byte in
the last position of the exchange area. In this way, as the Control Field changes from
message to message, the whole message is consistent as long as the first and last bytes
are matching.

From the practical point of view, a complete message in the Input area could be consid-
ered consistent as soon as the PLC verifies that IN[0] is equal to IN[InputAreaSize - 1].
The PLC should take care to double OUT[0] in OUT[OutputAreaSize - 1] to let the driver
check the consistency.
Due to the new byte used by the DAD driver, barcode messages longer than (InputArea-
Size - 4) will be split into pieces through an automatic fragmentation process.

Let's analyze a fragmented and consistent data exchange based on:

• Flow Control = DAD Driver
• Data Consistency = Enable
• Input Area Size = 16
• Output Area Size = 8

INTEGRATION GUIDE 18
DATA CONSISTENCY

1. After power-on, Input and Output areas are generally filled by zero. According to
DAD driver implementation, Input area has Control Field = IN[0] = IN[15] = 80Hex
and SAP = 00Hex.

Input 80Hex 00Hex

00He 00He 00He 00He 00He 00He 00He 00He 00He 00He 00He 00He 00He
80Hex
Area x x x x x x x x x x x x x

Output 00He 00He 00He 00He 00He 00He 00He

Area x x x x x x x

2. PLC must set Control Field = OUT[0] = OUT[7] = 80Hex according to DAD messag-
ing protocol with Data Consistency.

Input 80He 00He 00He 00He 00He 00He 00He 00He 00He 00He 00He 00He 00He 00He 00He 80He
Area x x x x x x x x x x x x x x x x

Output 80Hex 00Hex

00He 00He 00He 00He 00He
80Hex
Area x x x x x

3. Slave reads a barcode with content "1234567890abcde1234567890abcde". Let's

assume standard data formatting <CR> as terminator. Slave transmits first frag-
ment "01234567890a" only (setting More Bit = 1) then it toggles bit A.

Input 89Hex
00He 0CHe
30Hex 31Hex 32Hex 33Hex 34Hex 35Hex 36Hex 37Hex 38Hex 39Hex 30Hex 61Hex 89Hex
Area x x

Output 80He 00He 00He 00He 00He 00He 00He 80He

Area x x x x x x x x

4. PLC detects transition of bit A so now it can read first incoming fragment (it copies
12 bytes in its memory from IN[3] on) then toggles bit B as acknowledge.

Input 89He 00He 0CHe 30He 31He 32He 33He 34He 35He 36He 37He 38He 39He 30He 61He 89He
Area x x x x x x x x x x x x x x x x

Output 81Hex
00He 00He 00He 00He 00He 00He
81Hex
Area x x x x x x

5. Slave detects transition of bit B so it sends second fragment "bcde12345678" (still

More Bit = 1) and toggles bit A.

Input 88Hex
00He 0CHe
62Hex 63Hex 64Hex 65Hex 31Hex 32Hex 33Hex 34Hex 35Hex 36Hex 37Hex 38Hex 88Hex
Area x x

Output 81He 00He 00He 00He 00He 00He 00He 81He

Area x x x x x x x x

19 FIELDBUS DAD DRIVER

 DATA CONSISTENCY WITH DAD DRIVER

6. PLC reads second fragment (it copies 12 bytes in its memory from IN[3] on) then
toggles bit B as acknowledge.

Input 88He 00He 0CHe 62He 63He 64He 65He 31He 32He 33He 34He 35He 36He 37He 38He 88He
Area x x x x x x x x x x x x x x x x

Output 80Hex
00He 00He 00He 00He 00He 00He
80Hex
Area x x x x x x

7. Slave sends last fragment "90abcde<CR><LF>" (finally More Bit = 0) and toggles bit
A.

Input 81Hex
00He
08Hex 39Hex 30Hex 61Hex 62Hex 63Hex 64Hex 65Hex
0DHe
00Hex
00He 00He 00He
81Hex
Area x x x x x

Output 80He 00He 00He 00He 00He 00He 00He 80He

Area x x x x x x x x

8. PLC reads last fragment (it copies 9 bytes in its memory from IN[3] on) and now
the reassembling can be completed. Then it toggles bit B as acknowledge.

Input 81He 00He 08He 39He 30He 61He 62He 63He 64He 65He 0DHe 00He 00He 00He 00He 81He
Area x x x x x x x x x x x x x x x x

Output 81Hex
00He 00He 00He 00He 00He 00He
81Hex
Area x x x x x x

9. Whole message has been completely transmitted.

INTEGRATION GUIDE 20
CHAPTER 5
NETWORK CONFIGURATION

CONFIGURATION FILES FOR FIELDBUS

A Fieldbus configuration file is a readable ASCII text file that contains a complete
description of the specific device. It basically includes both general information (e.g.
vendor and device name, hw/sw releases) and device specific information (Input and
Output area size).
Powerful configuration tools can be used to setup a Fieldbus network (e.g. Siemens
SIMATIC Manager for Profibus). Based on the configuration files, these allow easy con-
figuration of Fieldbus networks with devices from different manufacturers.

NOTE: A configuration file must first be installed into the PLC environment
in order for a new device to be identified and to work on the Fieldbus net-
work.

The Fieldbus configuration files (EDS and GSDML) are found on the specific product
page under "Downloads>Software & Utilities". See [Link].

The Fieldbus configuration file is a certified part of the device and must not be changed
manually. This file is also not changed by the configuration tool.

21 FIELDBUS DAD DRIVER

 CONFIGURATION FILES FOR FIELDBUS

NOTES

INTEGRATION GUIDE 22
© 2023 Datalogic S.p.A. and /or its affiliates • All rights reserved • Without limiting
the rights under copyright, no part of this documentation may be reproduced,
stored in or introduced into a retrieval system, or transmitted in any form or by any
means, or for any purpose, without the express written permission of Datalogic
S.p.A. and/or its affiliates • Datalogic and the Datalogic logo are registered trade-
marks of Datalogic S.p.A. in many countries, including the U.S. and the E.U.

[Link]

Datalogic S.r.l.
Via S. Vitalino, 13 | 40012 Calderara di Reno | Bologna - Italy
Tel. +39 051 3147011 | Fax +39 051 3147205

June 2023