electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead

Protocol manual

Profibus

applicom® 3.8

a product of Woodhead Software & Electronics

profibus.doc 06/05/2004

Copyright © 2004 Woodhead Software & Electronics. All rights reserved.

http://www.applicom-int.com
 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead

profibus.doc 06/05/2004
® TM TM TM
Copyright © 2004 Woodhead Software & Electronics. All rights reserved. applicom , Direct-Link , RJ-Lnxx , SST are registered
trademarks of Woodhead Software & Electronics. Other product names are trademarks of their respective owners.

http://www.applicom-int.com
 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead

Table of contents

1. - Generalities ..................................................................................1
- General presentation.............................................................................................1
- Network management principle ............................................................................2

2. - Functionality ................................................................................4
- S5 messaging .......................................................................................................4
- DP messaging.......................................................................................................9
- MPI interface (Multi-Point-Interface).................................................................18
- Simatic® S7 protocol...........................................................................................18
- PROFIBUS FDL protocol ....................................................................................23

3. - Configuration .............................................................................25
- Channel configuration .........................................................................................25
- Configuring the local DP slave............................................................................28
- Equipment configuration .....................................................................................29

4. - SIEMENS equipment configuration..........................................45

- PROFIBUS PLC (SINEC® L2), S5 messaging...................................................45
- Siemens SIMATIC S7 equipments configuration with S7 protocol.....................53

5. - applicom® functions usable on the master channel ..............56

- Wait mode ...........................................................................................................56
- Deferred mode ....................................................................................................57
- Cyclic mode.........................................................................................................58

6. - Item of image variables .............................................................59

- Presentation ........................................................................................................59
- Standard descriptor.............................................................................................60
- DP descriptor ......................................................................................................65
- Siemens PLC descriptor - German (D) and French syntax ................................69
- Siemens S5 PLC descriptor - English syntax .....................................................79
- Siemens series 7 PLCs descriptor for MPI and S7.............................................89

7. - Appendices ................................................................................95
- List of extra files for this protocol ........................................................................95
- Evolution / compatibility.......................................................................................95
- List of the applicom® materials supporting the PROFIBUS protocol .................96
Access to the Profibus DP services ......................................................................97

8. - Return status of applicom® functions................................... 101

- Introduction .......................................................................................................101
- applicom® general statuses..............................................................................101
- Statuses according to the protocol....................................................................103

9. - Glossary of terms .................................................................... 107

Profibus •i• Table of contents

 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead
10. - Index ......................................................................................... 110

Profibus • ii • Table of contents

 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead

1. - Generalities

- General presentation
PROFIBUS is a heterogeneous local network which is located both at the cell supervisor level (level
3) and at the field network level (levels 0 and 1).
PROFIBUS (PROcess FIeld BUS) is the European standard related to field process buses. It is
defined in the PROFIBUS standard (EN 50170) which specifies the functional, electrical and mechanical
characteristics for a serial transmission field bus. The purpose of this standard is to network PLCs and
field devices from different manufacturers, without the need for time-consuming and complex adaptation
work.

CLIENT
APPLICATION

applicom®
S5
Siemens France
PLC messaging

Layer 7
Application FMS MPI S7 DP

Layer 6
Presentation

Layer 5
Session

Layer 4
Transport

Layer 3
Network

Layer 2 FDL_IDENT ..... SDA SDN SRD CSRD

Link FMA FDL

Layer 1 RS485
32 Stations/segment (max 127 stations)
Physical 9,6 to 1500 Kbps

applicom® PROFIBUS functionality faced with the OSI model

Layer 2 (Layer 2 = L2) can be accessed in different ways.

• DP MPI / S7
Standardized PROFIBUS messaging.
• S5
Messaging developed by Siemens France. This access is materialized by a program portion
supplied with applicom®, to be installed in the PLCs (details of this messaging are given at
the end of the chapter).

Profibus •1• - Generalities

 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead
Layer 2 addressees are divided into 2 families (FDL and FMA) :

Layer 2 services FDL Services = Fieldbus Data Link:

• SDA (Send Data with Acknowledgment)

This service allows a local station to send user data to a remote station.
• SDN (Send Data with No acknowledgment)
This service allows user data to be sent to one of the remote stations, a group of them, or all
of them.
• SRD (Send and Request Data with reply)
This service allows a local station to send data and at the same time ask to receive data from
this station.
• CSRD (Cyclic Send and Request Data)
This service allows a local station to send data cyclically to a remote station.

Diagnostic layer 2 FMA Services = Fieldbus MAnagement:

Service allowing the bus and station diagnostic.
Example:
FDL_IDENT Bus station identification

- Network management principle

There are 2 types of station, with different access rights
• Active stations:
Can initiate exchanges.
• Passive stations:
Can only exchange data after having been prompted to do so by an active station.

Whether a station is active or passive depends on the device considered. Generally, simple field
devices, such as motor controls, are passive whereas "intelligent" devices such as PLCs are active. Many
devices can be parametered quite indifferently as either active or passive.
The applicom® interface is currently an active station.

In order to avoid all active stations accessing the bus simultaneously, a station wanting to transmit
must wait until it has received authorization to access the bus. It receives this authorization as a special
telegram called the "token".

• The token passes automatically from one active station to the next active station (in increasing
order of station address).

• The token is transmitted according to a logic ring, i.e. that the station with the highest address
sends the token back to the station with the lowest address. Rule valid for every station:
between token transmission and reception, there is a token rotation cycle.

• Each active station "knows" the addresses of the other active stations. An active station checks
cyclically the address range between itself and the next active station. This address range is
called the "GAP". During this check, it detects any:
- Addition of an active or passive station.
- Deletion of a passive station.

The GAP updating factor indicates the periodicity during which active station checks the GAP
between itself and the next station.

Profibus •2• - Generalities

 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead
If the check reveals that a new active station has been added, the new station immediately receives
the token.

Two special cases result from this operating mode :

• If there is only one active station and all the others are passive, the network operates according
to the master-slave principle.

• If all stations are active, the network operates purely as a token ring..

The figure below shows a PROFIBUS network including 3 active stations and 3 passive stations.

1 2 3

4 5 6

Stations 1, 2, and 3 are active. The token will be transmitted as follows:

1 => 2 => 3 => 1 => 2 ...

The token rotation cycle lasts a certain amount of time. The maximum token cycle time must be set
using the applicom® configurator as Target-Rotation-Time .
The value set for the Target-Rotation-Time (TTR) must be respected even when there is a large
volume of data to be transmitted. To respect this time, PROFIBUS uses the following principle:

Each active station measures the time during which it did not have the token. This time then
represents the effective token rotation time.
It compares this measured time to the parametered TTR. The way the telegrams are processed
depends on the result of this comparison and on the link priority:
• Measured token rotation time < TTR:
All the existing transmission and reception contracts are executed until the TTR is reached or
until all waiting contracts are executed: first the contracts on the high priority links, then the
contracts on the low priority links.
• Measured token rotation time >= TTR:
A single high priority contract will be executed. Low priority contracts will only be executed
during the next token cycles when the measured token rotation time is again shorter than the
TTR (Target Rotation Time).

Communication between devices takes place through logic channels defined during configuration.
For each communication connection, the following data is called:

• Destination station address on the bus

• Local and remote service access point
The transmitting and destination point between 2 bus stations are "Service Access Points:
SAP". An SAP is an additional address criterion, given as well as the station address on the
bus.

Profibus •3• - Generalities

 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead

2. - Functionality

- S5 messaging
Functions managed by choosing a PROFIBUS Master channel allow access to variables defined in
the table below.
The address of the variable accessed must be calculated in some cases by referring to the "
applicom® addressing" column in the following table.

Siemens applicom® Exchange type Corresponding applicom®

PLC addressing (cyclic mode) function
Variable (addr) (library/DLL access)
M v.w v*8+w Read bits READPACKBIT, READDIFBIT
S v.w idem+2097152 Write bits WRITEPACKBIT, WRITEDIFPACKBIT
DB x D y.z x*4096+y*16+z
DX x D y.z idem +1048576
MB v v Read bytes READBYTE
SY v v + 131072 Write bytes WRITEBYTE
MB v v Read packed bytes READPACKBYTE, READDIFBYTE
SY v v + 131072 Write packed bytes WRITEPACKBYTE, WRITEDIFPACKBYTE
MW v v Read words READWORD, READDIFWORD
SW v v + 131072 Write words WRITEWORD, WRITEDIFWORD
DB x DW y x*256+y
DX x DW y idem + 65536
MD v v Read double words READDWORD, READDIFDWORD
SD v v + 131072 Write double words WRITEDWORD, WRITEDIFDWORD
DB x DD y x*256+y
DX x DD y idem + 65536
MD v KG v Read floating words READFWORD, READDIFFWORD
SDvKG v + 131072 Write floating words WRITEFWORD, WRITEDIFFWORD
DBxDDyKG x*256+y
DXxDDyKG idem + 65536
E v,w v*8+w Read input bits READPACKIBIT, READDIFIBIT
EB v v Read input bytes READIBYTE
EB v v Read packed input bytes READPACKIBYTE, READDIFIBYTE
EW v v Read input words READIWORD, READDIFIWORD
A v.w v*8+w Read output bits READPACKQBIT, READDIFQBIT
Write output bits WRITEPACKQBIT, WRITEDIFPACKQBIT
AB v v Read output bytes READQBYTE, READDIFQBYTE
Write output bytes WRITEQBYTE
AB v v Read packed output bytes READPACKQBYTE, READDIFQBYTE
Write packed output bytes WRITEPACKQBYTE,
WRITEDIFPACKQBYTE
AW v v Read output words READQWORD, READDIFQWORD
Write output words WRITEQWORD, WRITEDIFQWORD
TB n n Read timers READTIMER
Write timers WRITETIMER
ZB n n Read counters READCOUNTER
Write counters WRITECOUNTER

Profibus •4• - Functionality

 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead
v : Byte N°
w : N° of bit in byte (0 to 7)
x : DB N° (1 to 255)
y : N° of word in DB (0 to 255)
z : N° of bit in word (0 to 15)
n : Timer or counter N° (0 to 255)

Profibus •5• - Functionality

 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead
- Maximum number of variables per frame with the library

Object Max. quantity in read Max. quantity in write

Bit 1600 8 or 16 *
Byte 200 200
Word 100 100
Double word, floating word 50 50
Timer/counter 100 100

*: A write bit request is limited to a maximum of:

- 8 bits for a memo or a Smerker with modulo 8 start address
- 8 bits for outputs with modulo 8 start address
- 16 bits for a DB or a DX with modulo 16 start address
Example:
You can force on the output card:
8 bits from address 0
7 bits from address 1
etc..

- Maximum number of variables per frame with PCDDE

Object Max. Quantity in read Max. Quantity in write

Bit 1600 1
Byte 200 1
Word 100 1
Double word, floating word 50 1
Timer/counter 100 1

The number given for read frames corresponds to the maximum number of points (as imposed by
the server and/or the protocol) which can be grouped together during dynamic optimization of the frames
carried out by the server. However, this number can be reduced to suit a specific item of equipment by
configuring the length of frames in the topic (see chapter "Implementation/Topics configuration/Advanced
options").
Where write operations are concerned, a variable automatically entails the formation of a frame.

Profibus •6• - Functionality

 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead
- Maximum number of variables per frame with OPC server

Object Max. Quantity in read Max. Quantity in write

Bit 1600 8 or 16 *
Byte 200 200
Word 100 100
Double word, floating word 50 50
Timer/counter 100 100

*: A write bit request is limited to a maximum of:

- 8 bits for a memo or a Smerker with modulo 8 start address
- 8 bits for outputs with modulo 8 start address
- 16 bits for a DB or a DX with modulo 16 start address

The number given for read frames corresponds to the maximum number of points (as imposed by
the server and/or the protocol) which can be grouped together during dynamic optimization of the frames
carried out by the server. However, this number can be reduced to suit a specific item of equipment by
configuring the length of frames in the topic (see chapter "Implementation/Topics configuration/Advanced
options").
For the write frames, see chapter "OPC Server/Optimization of synchronous and asynchronous
requests".

Profibus •7• - Functionality

 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead
- Reminder on S5 messaging.

S5 messaging, developed by Siemens France, uses the SDA services. This access is materialized
by a program portion supplied by applicom® to be installed in Siemens PLCs. This program comes under
the form of a FB( FB100 ). It has been validated on the CPU 928, 928B, 942, 943, 943B, 944, 944B, 945,
946, 947, 948, 948B and on the 95U.
S5 messaging is conveyed in the "Data" part of a PROFIBUS telegram. The protocol management
is fully transparent for applicom® product users.

For information, the protocol description is given below.

S 5 Byte 0 & 1
00: Read Object DB N° Byte 2 & 3
01: Write type
(2 bits) (6 bits) (If type 01 otherwise 0)
First object address Byte 4 & 5
Number of objects Message counter Byte 6 & 7

Object type:

Type Object Step5 Description

01 DB Data block
02 M Internal variable (memo)
03 E Input
04 A Output
08 SY Internal variable (SMerker)
10 DX Expanded data block

Profibus •8• - Functionality

 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead
- DP messaging
The PROFIBUS DP field bus is based on the European standard EN 50170. PROFIBUS DP
telegrams can be used to transfer up to 244 bytes of data per telegram and connect to devices of address
from 0 to 126. All data exchanges use the SAPs (Service Access Point). PROFIBUS DP uses SAPs from
54 to 62.

The PC1500PFB, PCI1500PFB, PCI2000PFB, CPCI1000PFB and PC104PFB boards include:

• the class 1 DP master functionalities for optimized exchange of input/output data and
equipment diagnostics,

• the class 2 DP master functionalities for access to equipment belonging to other masters
and reading the DP slave input/output configurations,

• multimaster operation, to enable several profibus masters to run on the same network (for
example: a class 2 DP master and a class 1 DP master). This operation is based on the token ring.
It is a logical ring where each master station passes in a defined order (of increasing address), the
token giving the right to transmit or pass its turn.

The PCI2000PFB, CPCI1000PFB and PC104PFB boards include:

• the functionality master and DP slave simultaneously, for data exchange with another
master in the network.

The information required for equipment configuration is contained in a file of type XXXXXX.GSD
which is supplied by the manufacturer. It is recommended to import the GSD file in the applicom®
configurator, however, the various configurator fields can be entered manually.

The format of the GSD file is described in the standard EN 50170, volume 2, PROFIBUS.

Profibus •9• - Functionality

 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead
- Local DP slave functionality

This functionality, only available on CPCI1000PFB, PCI2000PFB and PC104PFB boards, provides
data exchange with another master in the network. The size of the input and output data can be
configured and enables all exchange combinations (0 to 244 bytes). The slave can ensure data
consistency up to sizes of 122 bytes.
Allocation of an equipment number during configuration enables access to data in the local slave
identically to that of a remote slave.

Caution:
Data transmitted by the remote master (output variables) refreshes the input variables in the
applicom® interface.
The data received by the remote master (input variables) corresponds to the output variables of the
applicom® interface.

applicom®
Library interface

DP Slave DP Master

Read functions INPUT INPUT

DATA DATA

Write functions
OUTPUT OUTPUT
DATA DATA

The statuses of applicom® functions guarantee refreshing of data with the remote master as long
as it sets the "Bus Time-out" (Watchdog control) parameter.
The remote master will include the applicom® DP slave in its configuration through the use of the
description files associated with the board used.
PC104PFB board : App088F.GSD,
PCI2000PFB board : App087A.GSD.
CPCI1000PFB board : App0592.GSD.
These files are available in the directory where the applicom® product is installed.

Profibus • 10 • - Functionality
 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead
- Supported functions

DP applicom® Exchange type Corresponding applicom® function

Variable addressing (cyclic modes) (library/DLL access)
Input bits (BIx) x Read input bits READPACKIBIT, READDIFIBIT
Output bits (BOx) x Read output bits READPACKQBIT, READDIFQBIT
Write output bits WRITEPACKQBIT, WRITEDIFPACKQBIT
Input bytes (OIx) x Read packed input bytes READPACKIBYTE, READDIFIBYTE
Output bytes (OOx) x Read packed output bytes READPACKQBYTE, READDIFQBYTE
Write packed output bytes WRITEPACKQBYTE, WRITEDIFPACKQBYTE
Input word (WIx) x Read input words READIWORD, READDIFIWORD
Output word (WOx) x Read output words READQWORD, READDIFQWORD
Write output words WRITEQWORD, WRITEDIFQWORD
Input double words (DIx) x+0x01000000 Read input double words READDWORD, READDIFDWORD
Output double words (DOx) x+0x02000000 Read output double words READDWORD, READDIFDWORD
Write output double words WRITEDWORD, WRITEDIFDWORD
Input floating words (FIx) x+0x01000000 Read input floating words READFWORD, READDIFFWORD
Input floating words (FOx) x+0x02000000 Read output floating words READFWORD, READDIFFWORD
Write output floating words WRITEFWORD, WRITEDIFFWORD

x : Variable number

The address argument of read and write bit primitives is calculated according to the following
equation:

(byte number transmitted * 8) + rank of the bit.

The address argument of read and write bytes, words, double words and floating words
corresponds to the number of the byte transmitted.

Remarks

The applicom® card uses the SRD (DATA EXCHANGE) services which refresh the inputs/outputs
asynchronously with respect to your application program. So, the read/write functions read and modify the
buffers asynchronously with respect to the refresh cycle.
The SYNC commands allows to synchronize the slaves according to the events. If the line
« Sync_Mode_supp = 1 » appears in the GSD file, it will be necessary to validate the check-box in the
configuration equipment of the applicom® configurator.

Profibus • 11 • - Functionality
 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead
- Communications

- Equipment dedicated to a single master

Communication between a DP master and the remote stations is in « Polling » mode. All dedicated
equipment present is interrogated in a « Polling » cycle. As soon as the last slave has been interrogated a
new cycle starts. This method guarantees data update.

• Equipment initialization :
For the dedicated equipment, the applicom® DP master uses the function DDLM_Slave_Diag to
detect the presence of equipment connected on the network. On acknowledgment of this question the
master transmits the parameters entered or from the GSD files to the equipment with the function
DDLM_Set_Prm. The input/output configuration phase then takes place. With manual configuration, the
configuration from the console is sent via the function DDLM_Chk_Cfg. For automatic configuration, the
configuration sent is that contained in the equipment; it is obtained by calling the function DDLM_Get_Cfg
(function class 2).

• Data access :
For dedicated equipment, the data exchange is cyclic. It is based on the Profibus
DDLM_Data_Exchange function. It is used to transmit to the equipment the output data and receive in
return its input data. If the equipment has inputs only, an empty frame is sent, if the equipment has
outputs only an empty frame is received.

Profibus • 12 • - Functionality
 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead
- Equipment shared between two masters

In multimaster configuration a DP slave can communicate with two masters:

One is the main master which configures and initializes the equipment, then makes the data
exchanges (DDLM_Data_Exchange). The equipment will then be considered by the master as being
dedicated.
The other is a secondary master accessing in read the inputs/outputs via class 2 functionalities.
The equipment will then be considered by the master as being shared.

Example :

PC1500PFB PC1500PFB
1 2

4 5 6 7

In this configuration:
• slaves 4 and 5 are dedicated to master 1,
• slaves 6 and 7 are dedicated to master 2,
• slave 5 is shared, the main master is master 1, the secondary master is master 2,
• master 1 can read and write on equipment 5, whereas master 2 can simply read
the slave's input/output data.

• Equipment initialization :

For shared equipment, initialization is carried out by the main master of the equipment. The
mechanism is then the same as for equipment dedicated to a single master

• Data access :
For the main master, the equipment is seen as a dedicated slave. The mechanism is then the same
as for equipment dedicated to a single master

For the secondary master, the data exchange is acyclic. It is based on the Profibus class 2
functions DDLM_Read_Input and DDLM_Read_Output. This operation does not allow writing of outputs.
On Profibus DP, only the main master can write the outputs.
The input/output data can be accessed in read by the same applicom® functions as those used for
the dedicated slaves (ReadPackIByte, ReadPackQByte, etc.), and by the same DDE and OPC items.

Profibus • 13 • - Functionality
 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead
- Remarks on access request to the variables

The PROFIBUS DP standard does not specify the organization of data in a frame. For 16 bit data
words, the standard specifies that the most significant byte is transmitted first.The program supports
access to 16 bit data words, to 32 bit data words and IEEE floating data words.

- Addressing mode of input/output bytes

applicom® allows an addressing mode on byte (see table below).

Bits Bytes
address address
0-7 0
8 - 15 1
16 - 23 2
24 - 31 3
32 - 39 4
40 - 47 5
48 - 55 6
56 - 63 7
... ...

Profibus • 14 • - Functionality
 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead
- Addressing mode of input/output words

Input and output words are based on a byte addressing mode (see table below).

Bits Bytes Word address

address address Even Odd
0-7 0 0
8 - 15 1 1
16 - 23 2 2
24 - 31 3 3
32 - 39 4 4
40 - 47 5 5
48 - 55 6 6
56 - 63 7 7
... ... ...

applicom® proposes, by configuration, two types of alignments :

• Alignment on word :

This mode returns, during a reading of several words, contiguous words of even or odd
address.
Example :
A reading of 3 words from address 0 will return the words 0, 2 and 4.
A reading of 3 words from address 1 will return the words 1, 3 and 5.

During a writing, the same addressing mode is applied.

Example :
A writing of 3 words from address 0 will affect the words 0, 2 and 4.
A writing of 3 words from address 1 will affect the words 1, 3 and 5.

• Alignment on byte :

This mode has the advantage, during a reading of several words, of returning the words of
even and odd address.
Example :
A reading of 4 words from address 1 will return the words 1, 2, 3 and 4.

During a writing of several words, "the alignment on word address" is applied.

Profibus • 15 • - Functionality
 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead
- Addressing mode of input/output double words or floating words

Input and output double words or floating words are based on a byte addressing (see table below).

Bytes
address Double words addresses
0 0
1 1
2 2
3 3
4 4
5 5
6 6
7 7
8 8
9 9
10 10
11 11
12
... ...

applicom® proposes, by configuration, two types of alignments :

• Alignment on double word :

This mode returns, during a reading of several double words, contiguous double words with
an address step of 4.
Example :
A reading of 3 double words from address 0 will return the double words 0, 4 and 8.
A reading of 3 double words from address 1 will return the double words 1, 5 and 9.
A reading of 3 double words from address 2 will return the double words 2, 6 and 10.

During a writing of several double words, "the alignment on double word address" is applied.

• Alignment on word :

This mode returns, during a reading of several double words, contiguous double words of
even or odd address.
Example :
A reading of 3 double words from address 0 will return the words 0, 2 and 4.
A reading of 3 double words from address 1 will return the words 1, 3 and 5.

During a writing of several double words, "the alignment on double word address" is applied.

Profibus • 16 • - Functionality
 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead
• Alignment on byte :

This mode has the advantage, lors d’une lecture de plusieurs mots doubles, of returning
double words of even and odd address.
Example :
A reading of 4 words from address 1 will return double words 1, 2, 3 and 4.

During a writing of several double words, "the alignment on double word address" is applied.

Profibus • 17 • - Functionality
 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead
- MPI interface (Multi-Point-Interface)
The physical interface of MPI protocol is identical to the Profibus one (RS485, pinout conformed to
the DIN 19245 part 1) standard. It replaces the PG interface (programming console). The baud rate is
fixed to 187.5 Kbauds. The maximal distance is of 50 meters (between two stations). With repeaters, the
distance is 1000 meters between 2 repeaters. The applicom® software is always Client and the PLCs are
always servers. The Profibus address and the highest MPI station address (HSA) of the PLCs are defined
thanks to the Siemens Step 7 software. The default PLC configuration is address 2, the address 0 is used
by the programmation console and the address 1 by the operator console.

The use of Siemens items descriptors is identical in MPI and S7.

- Simatic® S7 protocol
The S7 functions allows the PLCs communication between themselves in client and server mode.
The communication with applicom® is only in client mode, it allows to free the PG interface because we
connect directly on the coupler connection.
The variables of the Siemens S7 series are numbered by byte and not by 16 bit word as the DB
variables of the Siemens S5 series. So it’s nevertheless possible to access to words, double words or
floating words which addresses start on even or odd addresses. A request of reading several words must
allow the user to access to a word array, whatever their physical addresses. To solve this problem, the
PROFIBUS task with a protocol S7 equipment returns the variables according the configuration (byte,
word or double word).

Example 1 : An application wants to read in one request, the words MW11 and MW13. So It will
use a reading request of 4 words from the address 11. The content of the response will be presented as
followed :

• if the alignment is on byte address :

User array offset S7 variable Physical address in the PLC

0 MW11 11 and 12
1 MW12 12 and 13
2 MW13 13 and 14
3 MW14 14 and 15

• if the alignment is on word address :

User array offset S7 variable Physical address in the PLC

0 MW11 11 and 12
1 MW13 13 and 14
2 MW15 15 and 16
3 MW17 17 and 18

Of course, this addressing principle can not be applied to the writing of more than one variable in
one request.
Writing of 2 words from the address 11

User array offset S7 variable Physical address in the PLC

0 MW11 11 and 12
1 MW13 13 and 14

Profibus • 18 • - Functionality
 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead

Example 2 : An application wants to read in one request the words MD10 and MD16. It will use a
reading request from the address 11. The content of the response will be presented as followed :

• if the alignment is on byte address :

User array offset S7 variable Physical address in the PLC

0 MD10 from 10 to 13
1 MD11 from 11 to 14
2 MD12 from 12 to 15
3 MD13 from 13 to 16
4 MD14 from 14 to 17
5 MD15 from 15 to 18
6 MD16 from 16 to 19

• if the alignment is on word address :

User array offset S7 variable Physical address in the PLC

0 MD10 from 10 to 13
1 MD12 from 12 to 15
2 MD14 from 14 to 17
3 MD16 from 16 to 19
4 MD18 from 18 to 21
5 MD20 from 20 to 23
6 MD22 from 22 to 25

• if the alignment is on double word address :

User array offset S7 variable Physical address in the PLC

0 MD10 from 10 to 13
1 MD14 from 14 to 17
2 MD18 from 18 to 21
3 MD22 from 22 to 25
4 MD26 from 26 to 29
5 MD30 from 30 to 33
6 MD34 from 34 to 37

Writing of 2 double words from the address 10

User array offset S7 variable Physical address in the PLC

0 MW10 from 10 to 13
1 MW14 from 14 to 17

Profibus • 19 • - Functionality
 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead
Addressing mode :

The functions which can be used on a PROFIBUS S7 channel and a S7 equipment allow the
access to the variables defined in the table below.
Sometimes, the variable address must be calculated with the « applicom® addressing » column.

Variable applicom® Exchange type Corresponding applicom®

S7-300 S7-400 addressing (cyclic mode) function (library/DLL access)
My.z y*8+z Read bits READPACKBIT
DBx.DBXy.z x*524288+y*8+z Write bits WRITEPACKBIT
Ey.z y*8+z Read input bits READPACKIBIT
Ay.z y*8+z Read output bits READPACKQBIT
Write output bit WRITEPACKQBIT
MBy y Read bytes READPACKBYTE
DBx.DBBy x*65536+v Write bytes WRITEPACKBYTE
EBy y Read input bytes READPACKIBYTE
ABy y Read output bytes READPACKQBYTE
Write output bytes WRITEPACKQBYTE
MWy y Read words READWORD
DBx.DBWy x*65536+y Write words WRITEWORD
EWy y Read input words READIWORD
AWy y Read output words READQWORD
Write output words WRITEQWORD
MDy y Read double words READDWORD
DBx.DBDy x*65536+y Write double words WRITEDWORD
MDyF y Read floating words READFWORD
DBx.DBDyF x*65536+y Write floating words WRITEFWORD
Tn n Read timers READTIMER
Write timers WRITETIMER
Zn n Read counters READCOUNTER
Write counters WRITECOUNTER

x : DB number
y : Byte number
z : Number of the bit in the byte (0 to 7)
n : Timer or counter number (0 to 99)

Addressing limits :

Every variable in DB can be addressed from the byte 0 to the byte 65535.
For the bits in DB, only the DBs numbered from 1 to 8191 can be addressed.
For the bytes, words, double words and floating words, only the DBs from 1 to 32767 can be
addressed

Remark :
• At present, the PROFIBUS S7 communication is validated on the CP 342-5 and CP 443-5 couplers
• Only current value (CV) of timers and counters can be reached (read and write).

Profibus • 20 • - Functionality
 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead
- Maximum numbers of variables by exchange with the library

Object Max. quantity in read Max. quantity in write

Alignment byte word double word
Bit 1600 12
Byte 200 200
Word 128 100 100
Double word, floating 64 64 50 50
word
Timer/counter 100 100

- Maximum numbers of variables by exchange with PCDDE

Object Max. quantity in read Max. Quantity in write

Alignment byte word double word
Bit 1600 1
Byte 200 1
Word 128 100 1
Double word, floating 64 64 50 1
word
Timer/counter 100 1

The number given for read frames corresponds to the maximum number of points (as imposed by
the server and/or the protocol) which can be grouped together during dynamic optimization of the frames
carried out by the server. However, this number can be reduced to suit a specific item of equipment by
configuring the length of frames in the topic (see chapter "Implementation/Topics configuration/Advanced
options").
Where write operations are concerned, a variable automatically entails the formation of a frame.

Caution, the table and matrix mode requires some precautions. In addition, for alignment on byte
addresses when reading 16 bit words or for alignment on byte or word addresses when reading 32 bit
words, writing continues to take place in word addressing for 16 bits word and double word for 32 bits. In
case of array and matrix mode, an item symbolizing for example a word array (WOx_n_l) does not
designate the same variables in write as in read. Array and matrix mode can therefore only be used in
read.

Profibus • 21 • - Functionality
 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead
- Maximum numbers of variables by exchange with OPC server

Object Max. Quantity in read Max. Quantity in write

Alignment byte word double word
Bit 1600 12
Byte 200 200
Word 128 100 100
Double word, floating 64 64 50 50
word
Timer/counter 100 100

The number given for read frames corresponds to the maximum number of points (as imposed by
the server and/or the protocol) which can be grouped together during dynamic optimization of the frames
carried out by the server. However, this number can be reduced to suit a specific item of equipment by
configuring the length of frames in the topic (see chapter "Implementation/Topics configuration/Advanced
options").
For the write frames, see chapter "OPC Server/Optimization of synchronous and asynchronous
requests".

Caution, the table and matrix mode requires some precautions. In addition, for alignment on byte
addresses when reading 16 bit words or for alignment on byte or word addresses when reading 32 bit
words, writing continues to take place in word addressing for 16 bits word and double word for 32 bits. In
case of array and matrix mode, an item symbolizing for example a word array (WOx_n_l) does not
designate the same variables in write as in read. Array and matrix mode can therefore only be used in
read.

Profibus • 22 • - Functionality
 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead
- PROFIBUS FDL protocol
The PROFIBUS network can be used outside the messaging systems by using the FDL services.
These services are used to send messages in the SDA and SDN type Profibus requests.
The choice of the Profibus FDL protocol allows for message transmission in waiting, deferred and
cyclic mode. Reception is carried out automatically in a word zone configured in the applicom® database.

- Profibus FDL transmission

The choice of Profibus FDL messaging system allows transmission of messages in point to point or
broadcast mode. This choice and the definition of the SAP (local and remote) are established for each
equipment during the configuration.
The content and size of the message within the limit of 244 bytes are fully user-defined using the
functions below.

applicom® Exchange type applicom® function

addressing
(adr) (library/DLL access)
0 Write packed byte WRITEPACKBYTE,
WRITEDIFPACKBYTE
0 Write word (Intel convention) WRITEWORD,
WRITEDIFWORD
10000(hexa) Write word (Motorola convention) WRITEWORD,
WRITEDIFWORD
0 Write double word (Intel convention) WRITEDWORD,
WRITEDIFDWORD
10000(hexa) Write double word (Motorola convention) WRITEDWORD,
WRITEDIFDWORD
0 Write floating word (Intel convention) WRITEFWORD,
WRITEDIFFWORD
10000(hexa) Write floating word (Motorola convention) WRITEFWORD,
WRITEDIFFWORD

The functions handling the word, double word and floating word type variables are used to ensure
automatically the conversion to the Intel format or Motorola format according to the value of the address
argument sent in the applicom® functions below.
Address = 0, for the Intel format
Address = 65536 or 10000 (hexa), for the Motorola format.

Notice for the use under DDE and OPC: the emission is possible by the DATA-BASE and the
activation of cyclic functions (see chapter Access to the parameters of the cyclic functions in the
handbook of reference).

Profibus • 23 • - Functionality
 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead
- Profibus FDL reception

This function ensures the reception and storage of the messages in a word zone in the applicom®
database.

For this management, a reception zone must be configured for each transmitting item of equipment. Each
transmitting item of equipment is identified by its address on the Profibus network, its local SAP and its
remote SAP.
This definition authorizes, for the same transmitting Profibus station, different reception zones
according to the value of the SAP (local and remote) of each message.

The applicom® Profibus FDL server stores 2 service words at the start of each reception zone.
These words indicate zone refresh and the size of the last message received.

Take care during the configuration to define a size that is sufficient for the storage of the message
and the 2 service words.

During the configuration, you can define in the applicom® database, the address of a table of 100
words corresponding to the 100 applicom® equipment devices that can be configured (0 to 99). On each
reception, the word corresponding to the transmitter equipment is automatically incremented.

rst Information word increasing automatically for each reception

1 word
nd Information word indicating the size in bytes of the last message received
2 word
rd
3 word
… message storage
… zone
th
N word

Notes:
• If a message bigger than the size of the configured zone is received, it will be truncated. However, the
2nd service word indicating the length of the message is completed with the actual size of the
message.
• It is the responsibility of the user to consult the applicom® database more frequently than the
message arrival frequency. If a message arrives at a higher frequency, it overwrites the previous
message before its consultation by the application.

Profibus • 24 • - Functionality
 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead

3. - Configuration

- Channel configuration

Configuring the Profibus channel

Multimaster operation

Certain channel parameters must be set for multimaster operation. The following table summarizes
recommended parameter values according to the baud rate used for cards PC1500PFB and
PCI1500PFB:

9.6 kbaud 19.2 kbaud 93.75 kbaud 187.5 kbaud 500 kbaud 1,5 Mbaud
TSL 100 120 240 400 1000 3000
TTR 9134 9154 31274 31414 51414 30000

You must also enter the HSA so that it is greater than or equal to the highest address of the active
stations and check that the other masters in the network have been configured.

Baud rate
To consult the baud rates supported by your applicom® card, refer to the chapter "- List of the
applicom® materials supporting the PROFIBUS protocol" on page 96.

Profibus • 25 • - Configuration
 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead
Highest station address "HSA"
Specifies the active station highest address. Passive stations (slaves) can have an address higher
than HSA. Range of values: 2 to 126.

FDL address of this station "TS"

The station is active (master), TS must therefore be between 0 and 126 and be less than or equal
to HSA. Range of values: 0 to 126.

Retry counter "RETRY_CTR"

Number of telegram repetitions if the addressee does not react. Range of values: 1 to 8.

Slot time "TSL"

Maximum time between the last character of the requesting equipment frame and the reception of
the responding equipment first character.
The slot time cannot be less than 2 ms.

Minimum value according to the speed for card PC1500PFB, PCI1500PFB, PC1500S7 and
PCI1500S7 :
9600 baud : 100 187.5 kbaud : 400
19200 baud : 120 500 kbaud : 1000
93.75 kbaud : 240 1,5 Mbaud : 3000

Minimum value according to the speed for card PCI2000PFB, CPCI1000PFB and PC104PFB :
9600 baud : 100 1,5 Mbaud : 300
19200 baud : 100 3 Mbaud : 400
93,75 Kbaud : 100 6 Mbaud : 600
187,5 Kbaud : 100 12 Mbaud : 1000
500 Kbaud : 200

Setup time "TSET"

The "dead time" is the time that can elapse between an event (e.g. character reception or passage
of an internal monitoring time) and the reaction to this event. Range of values: 1 to 255 b/s.

Smallest station delay time "MIN_TSDR" :

Minimum space of time between the reception of the last bit of a telegram and the transmission of
the first bit of the next telegram. Range of values: 10 to 65535 b/s.

Largest station delay time "MAX_TSDR"

Maximum space of time between the reception of the last bit of a telegram and the transmission of
the first bit of the next telegram.

Minimum values according to transmission speed for card PC1500PFB, PCI1500PFB, PC1500S7
and PCI1500S7 :
9600 baud : 40 500 kbaud : 360
19200 baud : 65 750 kbaud : 560
93.75 kbaud : 200 1,5 Mbaud : 980
187.5 kbaud : 380

Minimum values according to transmission speed for card PCI2000PFB, CPCI1000PFB and
PC104PFB :
9600 baud : 60 1,5 Mbaud : 150
19200 baud : 60 3 Mbaud : 250
93,75 Kbaud : 60 6 Mbaud : 450
187,5 Kbaud : 60 12 Mbaud : 800
500 Kbaud : 100

Profibus • 26 • - Configuration
 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead
Token rotation time "TTR" : (TTR = Target- Rotation-Time)

This parameter has a critical influence on the system performance characteristics. These values
determine the maximum token rotation time for all the active stations on the logic ring. Upon token
reception, this time is compared with the cycle time actually elapsed. According to the result of this
comparison, the system determines if the considered stations can send telegrams "priority" messages
prevail).

"G" Gap update factor

The range of addresses between 2 consecutive active stations is called GAP. This GAP is
submitted to a cyclic check during which the system identifies the station condition ("not ready", "ready" or
"passive"). The "ready" condition means that this is a new active station that will receive the token. The
GAP updating factor is a multiple of the token rotation Time (TTR). The time space between two updates
is given by the following formula: TTR * G
(Token rotation time)*( GAP updating factor)
Range of G values according to transmission speed:
9.6 to 93.75 kbps => G ranges from 1 to 20.
187.5 to 1500 kbps => G ranges from 20 to 100.

Default value for card PCI2000PFB, CPCI1000PFB and PC104PFB : G = 10

Number of repeaters on the network

This parameter is valid only on channel 0 of card PCI2000PFB, CPCI1000PFB and PC104PFB. A
repeater is necessary if more than 32 stations are connected to the bus or if the maximum wire length of a
bus segment is exceeded.

Address Words indicating FDL access in DATA-BASE

Address of the start of the storage of the "Words indicating FDL access" in the word zone of the
applicom® database
The address can change from (0 to 31900).
If this management is not used, enter value -1.
Each message reception from a configured PROFIBUS FDL equipment will be indicated by the
incrementing of a word in DATA-BASE. The address of this word corresponds to the address configured
plus an offset defined by the applicom equipment number from 0 to 99.
This field is only available for configurations with PROFIBUS FDL equipment.

Words indicating FDL access in DATA-BASE

rst Equipment 0
1 word
nd Equipment 1
2 word
rd
3 word
….
th Equipment 99
100 word

Example:
Address Words indicating FDL access in DATA-BASE = 200.
Reception of data for equipment 58 will increment word 258 in DATA-BASE.

Profibus • 27 • - Configuration
 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead

- Configuring the local DP slave

You can define 1 device numbered from 0 to 99.

Configuring the local DP slave

Equipment number
Allocate a device number, which will be used in the applicom® functions to access the slave
variables.

Number of input bytes

Define the size of the inputs.

Number of output bytes

Define the size of the outputs.

Data format
Specify the data feedback format when reading 16-bit or 32-bit words.
"Little-Indian" or Intel format: the high order byte is on the right of a word.
"Big-Indian" or Motorola format: the high order byte is on the left of a word.

Active configuration
Checkbox to activate the equipment configuration in the applicom® interface: used to delete
a device from the applicom® interface whilst keeping its configuration in the console.

Profibus • 28 • - Configuration
 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead
- Equipment configuration
Up to 100 peers numbered from 0 to 99 can be defined.

For each equipment item, indicate :

To consult the list of protocols supported by your applicom® card, refer to the chapter "- List of the
applicom® materials supporting the PROFIBUS protocol" on page 96.

Device types available in the library

S5 : PLC equipped with S5 protocol.
L2 DP : Decentralized Periphery, remote input/output.
MPI : Multi Point Interface
S5 for S7 : S7 PLC equipped with S5 protocol.
S7 : S7 PLC.

Profibus • 29 • - Configuration
 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead

Configuring equipment with « S5 » messaging

Configuring equipment with S5 messaging

Equipment physical address (0-126)

Remote station physical address.

The local SAP (LSAP) (0-61)

SAP that transmits the request.
For the S5-115U/135U/155U :
- Local SAP must be different to physical PLC address
For the 95U:
- Local SAP = Physical PLC address (parameter TLN) + 1.

Remote SAP (DSAP) (0-62)

For S5-115U/135U/155U
- Remote SAP = LSAP ( Service Access Point Local) cpu job.
For the 95U:
- Remote SAP = Physical address of the applicom® channel (parameter TS) + 1.

Profibus • 30 • - Configuration
 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead
Priority
For S5-115U/135U/155U :
- Priority = LOW or HIGH
For the 95U:
- Priority = LOW (obligatory)
Warning: Priority must be identical between PLC and PC.

Active configuration
Check box to activate the device configuration in the applicom® interface : used to delete a
device from the applicom® interface whilst keeping its configuration in the console.

Profibus • 31 • - Configuration
 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead

Equipment configuration with « PROFIBUS DP » messaging

Configuring equipment with Profibus DP messaging

Remote station physical address (0-126)

Remote equipment address.

Bus time-out in 100 ms (0-255)

The bus Time-out parameter is used to switch the remote equipment into error (all outputs
are set to « 0 ») if no transaction has been made during this period.
The value 0 deactivates this monitoring.

Data alignment for 16 bits words reading

This parameter allows to align 16 bits data in byte (equal to 1) or word (equal to 2) address
for the reading of word arrays. The default value is 1.

See chapter - Remarks on access request to the variables

Data alignment for 32 bits words reading

This parameter allows to align 32 bits data in byte (equal to 1), word (equal to 2), double
word (equal to 4) address for the reading of double word arrays. The default value is 1.

Profibus • 32 • - Configuration
 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead
See chapter - Remarks on access request to the variables

Slave identification number

The module identification number supplied by the manufacturer of the DP slave station will
be compared to the module actually on the network. If they are different, the connection will
be refused. The value 0 disables this verification.

Station type
Indicates the name of the equipment corresponding to the "Model_Name" field contained in
the GSD file.

Data format
Allows to specify the format of data feedback when reading 16 bits words or 32 bits words.
Byte ordering:
Big-Endian: the most significant byte is on the left end of a word.
Little-Endian: the most significant byte is on the right end of a word.

Synchronous compatible
Indicates whether the slave can execute the SYNC command from the master.
When it receives the SYNC command, the DP master orders the normalized slave to freeze
the output statuses at the instantaneous value.

Shared equipment
This option must be activated when the equipment belongs to another DP master in the
network. This other master initializes the equipment and performs the data exchange with
this slave. However, via the applicom® functionalities, we can access its inputs and outputs
in read using the class 2 functions (DDLM_Read_Input and DDLM_Read_Output).

Number of parameters
Indicates the number of data items in the parameter telegram to be sent to the device during
its initialization phase.

Parameters
Zone where you define, if the slave type requests this, the contents of the parameter
telegram, for example the diagnostic authorizations or zones for analog DP slaves. The
parameters are in hexadecimal format separated by spaces.

Input/output configuration
Indicates whether the input/output configuration must be automatic or manual. With
automatic configuration, the configuration used is that present in the equipment, and with
manual configuration, you must enter the input/output configuration. To help you solve any
problems, the DP diagnostic utility is available.

Button : By default
Gives the contents of the parameter telegram with the default values if the GSD file supplied
with the equipment is not present and if the equipment is held in the list of equipment
recognized by applicom®.

Button : Import GSD

Used to import a GSD file to include new equipment. Used to complete the fields « Slave
Identification Number », « Number of parameters » and the parameters. The user must then
modify them according to the hardware documentation supplied by the equipment
manufacturer.

Profibus • 33 • - Configuration
 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead
Customized input/output configuration
Offers customized configuration of the format and size of the slave's inputs/outputs, either via
modules from the GSD file, or by direct input. With direct input, you need to know the byte
series accepted by the equipment.

Active configuration
Check box to activate the device configuration in the applicom® interface : used to delete a
device from the applicom® interface whilst keeping its configuration in the console.

Profibus • 34 • - Configuration
 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead
Module manual configuration for a DP equipment

GSD information
Indicates the limits concerning the size of data and the maximum number of modules
accepted by the equipment and specified in the GSD file.

Module information
Indicates the size of the data and the number of modules corresponding to the selected
module(s).

Modules from the GSD

Validates the entry of the modules from the GSD file specified opposite.

Customized module
Several byte series can be entered, corresponding to modules, and added as required in the
table of selected modules. With this functionality you need to know the series expected by
the slave. You can also "paste"(CTRL + V) the configuration copied in module display of the
DP diagnostic utility.

Profibus • 35 • - Configuration
 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead
Selected modules
Represents the modules selected with the format description and the data size. This data is
limited if the GSD file is specified. This data will be sent each time the equipment is
initialized. If the equipment does not accept the configuration, it will be impossible to perform
the data exchange.
To help you diagnose any malfunctions, the DP diagnostic utility is available.

Select a GSD file

This button is used to select a GSD file to display the modules it contains. N.B : the slave
identification number must correspond with that contained in the GSD file.

Add a module
This button is used to add a module entered or from the GSD file. Caution, the order of the
modules is important, it may lead to a configuration error

Delete a module
This button is used to delete a selected module.

Move selected module upwards

This button is used to move a selected module upwards.

Move selected module downwards

This button is used to move a selected module downwards.

Delete selected modules

This button is used to delete all selected modules.

Import the module configuration from the apdiag diagnostic utility

This button is used to import the module configuration from the apdiag diagnostic utility.

Profibus • 36 • - Configuration
 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead

- Configuring equipment with « MPI » messaging:

Configuring equipment with MPI messaging

Equipment physical address (0-126)

MPI equipment address.

The local SAP (LSAP) (0-61)

Local SAP must be different to physical PLC address

Data alignment for 16 bits words reading in the DB (1-2)

This parameter allows to align 16 bits data in byte (equal to 1) or word (equal to 2) address
for the reading of word arrays. The default value is 1.

Word X Word X+1

byte 1 byte 2 byte 3 byte 4
first array word
second array word alignment = 1
third array word
first array word second array word alignment = 2

Profibus • 37 • - Configuration
 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead
Data alignment for 32 bits words reading in the DB (1-4)

This parameter allows to align 32 bits data in byte (equal to 1), word (equal to 2), double word
(equal to 4) address for the reading of double word arrays. The default value is 1.

Double Word X Double Word X+1

byte 1 byte 2 byte 3 byte 4 byte 5 byte 6 byte 7 byte 8
first array double word
second array double word
third array double word alignment = 1
fourth array double word
fifth array double word
first array double word
second array double word alignment = 2
third array double word
first array double word second array double word alignment = 4

Active configuration
Check box to activate the device configuration in the applicom® interface : used to delete a
device from the applicom® interface whilst keeping its configuration in the console.

Profibus • 38 • - Configuration
 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead

- Configuring equipment with Protocol S7

Configuring equipment with Protocol S7 messaging

Equipment physical address (0-126)

Equipment S7 address.

The local SAP (LSAP) (0-61)

Local SAP must be different to physical PLC address
Range of values: 0 ... 54 for card PCI2000PFB (channel 0),CPCI1000PFB and PC104PFB,
0 ... 61 for other cards.

Profibus • 39 • - Configuration
 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead
Data alignment for 16 bits words reading in the DB (1-2)
This parameter allows to align 16 bits data in byte (equal to 1) or word (equal to 2) address
for the reading of word arrays in the DB. The default value is 1.

Word X Word X+1

byte 1 byte 2 byte 3 byte 4
first array word
second array word alignment = 1
third array word
first array word second array word alignment = 2

Data alignment for 32 bits words reading in the DB (1-4)

This parameter allows to align 32 bits data in byte (equal to 1), word (equal to 2), double
word (equal to 4) address for the reading of double word arrays in the DB. The default value
is 1.

Double Word X Double Word X+1

byte 1 byte 2 byte 3 byte 4 byte 5 byte 6 byte 7 byte 8
first array double word
second array double word
third array double word alignment = 1
fourth array double word
fifth array double word
first array double word
second array double word alignment = 2
third array double word
first array double word second array double word alignment = 4

Rack Number
Value from 0 to 7, 0 by default.

Number of the rack where the CPU module to be polled is located.

CPU Slot
Value from 2 to 31, 2 by default.

These numbers (rack and CPU) must be identical to those defined in the PLC hardware
configuration using the Step7 utility. They will be transmitted to the server equipment during the
connection phase to establish the connection.

Link type
This parameter is used to define the link type that the applicom® interface must use for the S7
connection.
Value:
Standard: link available for the applications, it permits several simultaneous requests.
PG: link reserved for the programming console but can be used in S7 with the applicom®
interface in a single simultaneous request.
OP: link reserved for the operator panel but can be used in S7 with the applicom® interface
in a single simultaneous request.

Remark: depending on the PLC type and the CPU type, the number of standard links available
may vary.

Profibus • 40 • - Configuration
 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead
S7-300 S7-400 S7-400 S7-400
CPU 314, 315 CPU 412, 413 CPU 414 CPU 416
Standard 2 14 30 62
PG 1 1 1 1
OP 1 1 1 1

If all connections are taken (Standard, PG and OP), no new connection will be accepted (status
65).

Active configuration
Check box to activate the device configuration in the applicom® interface : used to delete a
device from the applicom® interface whilst keeping its configuration in the console.

For others informations concerning PLC configuration, report to the SIEMENS documentations.

Profibus • 41 • - Configuration
 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead
- Configuration of an item of equipment with "PROFIBUS FDL"
messaging system

Configuration of an item of equipment with "Profibus FDL" messaging system

For each item of equipment, you will indicate:

Physical address of the remote station (0-126)

The physical address of the remote station is a number between 0 and 126.
This number corresponds to the PROFIBUS transmitter and recipient station number (if the
"Multicast transmission" option has been disabled).
If the "Multicast transmission" option is validated, this number is used exclusively for reception, the
transmissions will automatically target the Profibus distribution address (namely address 127).
This number must be less than or equal to the HSA parameter.

Profibus • 42 • - Configuration
 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead
Local SAP (LSAP 0-53, 63)
Local Service Access Point of the contract.
This value is used:
• On transmission to inform the remote station of the transmitter service.
• On reception to authorize the reception of messages on this service. Only the messages targeting this
SAP will be stored in the applicom® database.

Value 63 is used to validate broadcast reception. On transmission, the value of the local SAP
is initialized with the value of the remote SAP.

Remote SAP (DSAP 0-53, 63)

Remote Service Access Point of the contract.
This value is used:
• On transmission, to select the service of a remote station.
• On reception to authorize the reception of messages from this service. Only the messages sent with
this SAP will be stored in the applicom® database.

Value 63 associated with validation of the "multicast transmission" option allows transmission
in broadcast.

Priority
This value is used to indicate the importance of the message to send. The PROFIBUS standard
indicates two levels (LOW-HIGH) thereby allowing the transmission of priority messages.

Multicast transmission
This choice is used to multicast to all equipment present on the bus. In this context, no acknowledgement
is returned by the receiving equipment.
The message is sent in an SDN type request with address Profibus 127 (global address).

Data format
Specify the data format for 16-bit words in applicom® database.
"Little-Indian" or Intel format: the high order byte is on the right of a word.
"Big-Indian" or Motorola format: the high order byte is on the left of a word.

.Reception zone in Data-Base: Start address

Address of the reception zone in the applicom® database.
This address targets the word zone of the applicom® database for storing messages as well as
the 2 associated service words. This zone is organized as follows:
- the 1st word contains a counter that is incremented on each reception.
- the 2nd word contains the length of the message in bytes.
- the 3rd word corresponds to the start of the message received.
The address can change from (0 to 31876).
If this management is not used, enter value -1.

.Reception zone in Data-Base: Size in words

This value is used to define the size of the reception zone in the applicom® database.
This size corresponds to the number of words needed for the storing of the message plus 2 for the
storing of the 2 service words, namely:
Size in words = Maximum message size (in words) + 2
The size can change from (3 to 124 words).
If a message is received with a size greater than the configured zone, it will be truncated. However,
the 2nd service word indicating the message length is completed with the actual size of the message sent.

.Reception zone in Data-Base : End address

This value indicates the address of the end of the reception zone configured in the applicom®
database. It can be useful for determining the next available address in the database.

Profibus • 43 • - Configuration
 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead
.Reception zone in Data-Base: Maximum message size in bytes
This value indicates, according to your configuration, the maximum size of the messages (in bytes)
that can be stored in the applicom® database.
Namely: (Size of the words zone – the 2 service words) * 2 bytes per word.

Active configuration
This is used to disable an item of equipment when it is no longer physically present on the network
while retaining its configuration.

Profibus • 44 • - Configuration
 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead

4. - SIEMENS equipment configuration

- PROFIBUS PLC (SINEC® L2), S5 messaging

- Connection between computer and SIEMENS PLC

The PC is connected to the SINEC® L2 bus with the PC1500PFB or PCI1500PFB board. A
SIEMENS PLC can be connected to the SINEC® L2 network by installing a special communication
processor, ref. CP5430 TF or CP5431 FMS, that is directly connected to the SIMATIC® S5 PLC
backplane bus. Communication processor can be used with any S5 system from S5 115U and higher.
There are two physical interfaces on CP5430 TF or CP5431 FMS, one for connecting the SINEC® L2
field network and the other for accessing the coupler configuration and adjustment. The traffic on the L2
network is managed independently by Communication processor which thus relieves the S5 PLC CPU.

- Communication between S5 processor and CP 5430 coupler

Communication between the PLC processor and the CP5430 coupler is achieved through a dual
access RAM which thus provides very fast exchanges. This data exchange is carried out by means of
communication blocks which are PLC subroutines supplied partly with the applicom® server. The
supported CPU are 95U,928, 928B, 942, 943, 943B, 944, 944B, 945, 946, 947, 948, 948B.

These subroutines are in the install\simatic\simatic.s5 directory of the applicom® CD-ROM .

These files are in MS-DOS format. You must therefore convert them into PCPM format with the PCOPY
utility supplied with your software.

Files in the install\simatic\simatic.s5 directory of the applicom® CD-ROM

L2BI55ST.S5D MS-DOS software for Siemens PLC 155U

L2RW15ST.S5D MS-DOS software for Siemens PLC 115U
L2RW35ST.S5D MS-DOS software for Siemens PLC 135U
L2RW95ST.S5D MS-DOS software for Siemens PLC 95U
L2RW945ST.S5D MS-DOS software for Siemens PLC 945
PCOPY.EXE Translator PCPM MS-DOS
PCOPY.WRI PCOPY Help
S5 \ Q5431S5 sample configuration of CP 5431 with S5 messaging

If you are using a 115U PLC, you must convert the "L2RW15ST.S5D" file, for the 135U PLC, the
"L2RW35ST.S5D" file, for the 115U PLC with CPU945, the "L2R945ST.S5D" file, and for a 95U PLC, the
"L2RW95ST.S5D" file. You must then transfer this file into the PLC CPU. When this block is called, you
must enter the following 3 parameters:

In the case of S5-115U, 135U or 155U PLCs :

- SSNR: no. identical to that defined in "SYSID" data field with COM5430 utility or COM5431
with initializing CP
- ANR : contract no. identical to that defined in the COM5430 "LINK" data field or identical to
that defined in the COM5431 « Layer two free ».
- ANZW: address of the double status word associated to the connection. Format: KY A,B
with A= DB no. of ANZW or 0 if memo.

Profibus • 45 • - SIEMENS equipment configuration

 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead
In the case of S5-95U PLC:
- ADDR: PC SINEC® L2 address
- STBS: SEND function status byte
- STBR: RECEIVE function status double byte.

Among the communication blocks used, one block is of the PLC standard type (SYNCHRON
function for S5-115U/135U PLCs), and the other blocks are specific blocks developed by SIEMENS
France

SYNCHRON
Initialization and synchronization between CPU and CP.

The SIEMENS specific program (FB100) is called.

L2@RW15 for 115U PLC
L2@RW35 for 135U PLC
L2@RW95 for 95U PLC
L2@RW55 for 155U PLC
L2@RW45 for 115U PLC with CPU 945

This block calls the functions SEND and RECEIVE, a data block DB150.(which cannot be modified)
and a Memo MB255,MB0,MB1,MB2,MB3,(MW0et MW2).

Note : The « FB100 » of the S5-95U uses another specific program « FB101 » integrated in the
L2RW95ST.S5D.

SEND
Data transmission from the S5 PLC processor to the CP5430 coupler.

RECEIVE
Data reception from the network to the PLC program through the CP5430 coupler.

Note:
The SINEC® L2 (FB100) FB server is called in the same PLC cycle as many times as there are
different connections to 1 or several PC, by referring to different contract numbers.

The example below shows how these function blocks must be called if you use a PLC of the 115U
family. Please note that the function block number is different according to the PLC type. The
SYNCHRON block must be called by the PLC program at every PLC warm or cold restart.

Example :

OB21 and OB22 (Organization blocks 21 and 22 )

JU FB 249 ;Call block FB249.

NAME: SYNCHRON ;The block name is displayed.
SSNR: KY O,0 ;Memory area reserved for coupler access.
BLGR: KY 0,0 ;Size of the data area used for CPU<->CP
communication.
0 = maximum size.
PAFE: MB 255 ;Diagnostic byte.

In block OB1 you must call block FB100. This special block links the SINEC® L2 reception request
to the PLC data area.

Profibus • 46 • - SIEMENS equipment configuration

 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead
Example on S5-115U/135U PLC :
OB1
SPA FB100 ; this block is included in file L2RW15ST.S5D. Caution, this block
uses DB150 , SEND and RECEIVE data blocks.
NAME: L2@RW15
SSNR: KF +0 ;no. of the interface defined in the COM5430 utility "SYSID" data field
or COM5431
ANR : KF +150 ;no. of contract defined in the COM5430 "LINK" data field
or COM5431
ANZW: KY 0,0 ;report

Example on S5-95U PLC :

OB1
SPA FB100 ; This block is included in file L2RW95ST.S5D. Caution, this block
uses DB150 , SEND and RECEIVE data blocks.
NAME: L2@RW95
ADDR: KF +1 ;SINEC® L2 address of PC=1
STBS: MB150 ;SEND status byte = MB150
STBR: MB151 ;RECEIVE status double byte = MB151 et MB152

Profibus • 47 • - SIEMENS equipment configuration

 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead
- SIEMENS CP5430 configuration with COM5430

The configuration is performed with the COM5430 software supplied by SIEMENS. When the
software is activated and open, you must select F2 to configure each part of the CP5430 board. You must
then configure the system identification. In "SYSID" data field, you must enter the SSNR number which is
entered as a parameter when the FB100 managing block is called.
To configure the SINEC® L2 bus parameters, you must select "INIT". You must then create a logic
link with "LINK". The following window is displayed:

The PROFIBUS L2 DDE server uses the access to layer 2. The service used is SDA (Send Data
with Acknowledge).

TYPE
To define an access to layer 2, TYPE must be OPEN (open link).

PRIO
The access on SINEC® L2 can be defined in high or low priority.

SSNR
You must enter SSNR (memory page area) = ( 0 to 3)

ANR
Configurable according to your choice, "job number" is used for direct accesses to layer 2,
ANR must be in the range 134-186., the ANR parameter of the SIEMENS (FB100) special
block will have to be initialized at this value.

SAP
SAP (Service Access Point) is an address extension. All the frames are received/transmitted
via this SAP.

Profibus • 48 • - SIEMENS equipment configuration

 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead
- SIEMENS CP5430-TF configuration with S5 Messaging

The configuration is performed with the program COM5430 Sinec® NCM supplied by SIEMENS.
When the software is running and open, you must configure each part of the CP5430 board. You must
configure the system identification "SYSID" via the menu option Edit\Init CP. In this you should enter the
L2 Station Address, the Station Type (which must be Open), the base No-I, the interface number
(CP5430) and supplementary parameters for your project. You must then configure the network
parameters before creating a logic link via the menu option Edit\Links. Then choose Free Layer 2 link and
you will see the following window :

The applicom® PROFIBUS server uses layer 2access. The service used is SDA (Send Data with
Acknowledge).

Local station address

This parameter is not accessible to write requests and informs you of the address for the
station currently being configured.

PRIO
SINEC® L2 access can be set at high or low priority.

SSAP
The local Service Access Point is an address extension. All frames are sent and received by
this SAP.

No_I
You must enter the SSNR number (memory page area) = ( 0..3).

No_O
This "job number" can be configured as you wish and is used for direct layer 2 access, No-O
must be in the range 134 to 186. The ANR parameter of the special SIEMENS (FB100) block
must be initialized at this value.

Profibus • 49 • - SIEMENS equipment configuration

 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead
- S5 Messaging (SINEC® L2) for CP 5431 FMS .

A CP 5431 FMS sample configuration is available in directory install\simatic\simatic.s5\s5 of the

applicom® CD-ROM.
The configuration is carried out with the help of COM 5431 FMS software under SINEC® NCM
supplied by SIEMENS. When the program runs, you must configure each part of the CP5431 board as
below.

1) You must configure the system identification «SYSID» via the menu Editr\Init CP. In this you
should enter the L2 Station Address, the Station Type (which must be Open), the base SSNR, the
interface number (CP5431) and supplementary parameters for your project.

2) You must then configure the network parameter before creating a logic link via the menu option
Edit\Param.Local Network, you will see the following window :

3) Then choose Free Layer 2 Link via the menu option Edit\Layer. You will see the following
window:

The applicom® PROFIBUS server uses layer 2 access. The service used is SDA (Send Data
with Acknowledge).

Local station address :

Thus parameter is not accessible to write request and informs you of the address for the station
currently being configured.

Profibus • 50 • - SIEMENS equipment configuration

 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead
PRIO (H/L) :
SINEC® L2 access can be set at high or low priority.

SSAP :
The local Service Access Point is an address extension. All frames are sent and received by this
SAP.

SSNR :
You must enter the SSNR (memory page area) = 0.

ANR :
This "job number" can be configured as you wish and is used for direct layer 2 access, No-O must
be in the range 134 to 186. The ANR parameter of the special SIEMENS (FB100) block must be
initialized at this value.

Profibus • 51 • - SIEMENS equipment configuration

 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead
- Parameters of S5-95U SINEC® L2 integral interface

Parameters are set through DB1 in the parameter block called "SL2". Whichever the selected
transmission mode may be, you must define a number of parameters in DB1. For the definition of the
various fields, you must refer to the manufacturer's literature ( ref. 6ES5-998-8MB31 ).

DB1 Bloc in L2RW95ST.S5D (paragraph "SL2").

156: KC =';# SL2: TLN 2 STA AKT';

168: KC =' BDR 500 HSA 10 TRT ';
180: KC ='30000 SET 1 ST 1000 ';
192: KC ='SDT 1 12 SDT 2 360 SF';
204: KC =' DB6 DW0 EF DB7 DW0 ';
216: KC =' KBS MB62 KBE MB63 ';
228: KC ='STBS 1 MB150 STBR 1 MB15';
240: KC ='1 STBS 3 MB160 STBR 3 MB';
252: KC ='161 ; END ';

Default parameters in file L2RW95ST.S5D :

TLN : 2 ;address of 95U on the network

STA : AKT ;active station (obligatory)
BDR : 500 Kbauds ;transmission speed
HSA : 10 ;HSA address
TRT : 30000 ;Target-Rotation-Time
SET : 1 ;Setup-Time
ST : 1000 ;Slot-Time
SDT1 : 12 ;minimal time for executed program
SDT2 : 360 ;maximal time for executed program
STBS : 1 MB150 :no. of contract and SEND status byte.
STBR : 1 MB151 :no. of contract and RECEIVE status double byte.

The contract no is equivalent to ADDR parameter (Remote station address @ PC), passed during
FB100 function bloc calling.
For more information on the DB1 parameters, you must refer to the manufacturer documentation.

Notes:
The link type must be AGAG,
ADDR contract no. = PC SINEC® L2 address.

Profibus • 52 • - SIEMENS equipment configuration

 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead
- Siemens SIMATIC S7 equipments configuration with S7 protocol

- Description

In this example, the applicom® card is client of a SIMATIC S7_400 PLC.

CPU SLOT :3

- PLC configuration with Step7

The configuration is made thanks to Step7 soft supplied by SIEMENS. For more information, report
to the SIEMENS documentation.

First, create a project in the environment.

Then, declare hardware configuration of your PLC. We must declare :

1 Rack
1 Alimentation
1 CPU (note the slot number for the configuration in the server equipment)
1 « PROFIBUS » CP443-5 coupler.

Profibus • 53 • - SIEMENS equipment configuration

 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead
Then, click on the line corresponding to the coupler in order to choose his Profibus address.

Click on «PROFIBUS»

Profibus • 54 • - SIEMENS equipment configuration

 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead
Choose this network profile :

Then load the configuration in the PLC in « Stop » mode, then use it in « Run ».
The green led of the UC and the coupler must be switch on fixedly.
Run the applicom® configuration loader PCINIT. Then, the coupler is ready to work and connect

Note :
When equipments are disconnected from the network, communication errors may appear (status 54
or 55). To avoid this problem you must choose « user defined » profile, and adjust the parameter Tslot.

Profibus • 55 • - SIEMENS equipment configuration

 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead

5. - applicom® functions usable on the master

channel

- Wait mode

- Standard functions

WAIT L2 S7
MODE S5 DP MPI
READPACKBIT X X
READPACKIBIT X X X
READPACKQBIT X X X
READBYTE X
READIBYTE X
READQBYTE X
READPACKBYTE X X
READPACKIBYTE X X X
READPACKQBYTE X X X
READWORD X X
READIWORD X X X
READQWORD X X X
READWORDBCD X
READDWORD X X X
READFWORD X X X
READTIMER X
READCOUNTER X
READIDENT X

WRITEPACKBIT X X
WRITEPACKQBIT X X X
WRITEBYTE X
WRITEQBYTE X X
WRITEPACKBYTE X X
WRITEPACKQBYTE X X X
WRITEWORD X X
WRITEQWORD X X
WRITEWORDBCD X
WRITEDWORD X X X
WRITEFWORD X X X
WRITETIMER X
WRITECOUNTER X

AppConnect
AppUnconnect
WATCHDOG X X X
AppGetWatchDog X X X
ACCESSKEY X X X
AppIniTime X X X

Profibus • 56 • - applicom® functions usable on the master channel

 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead

- Deferred mode

DEFERRED Profibus
MODE L2 S7
FUNCTIONS S5 DP MPI

READDIFBIT X X
READDIFIBIT X X X
READDIFQBIT X X X
READDIFBYTE X X
READDIFIBYTE X X X
READDIFQBYTE X X X
READDIFWORD X X
READDIFIWORD X X X
READDIFQWORD X X X
READDIFDWORD X X X
READDIFFWORD X X X

TESTTRANSDIF X X X
TRANSDIF X X X
TRANSDIFPACK X X X

WRITEDIFPACKBIT X X
WRITEDIFPACKQBIT X X X
WRITEDIFPACKBYTE X X
WRITEDIFPACKQBYTE X X X
WRITEDIFWORD X X
WRITEDIFQWORD X X X
WRITEDIFDWORD X X X
WRITEDIFFWORD X X X

Profibus • 57 • - applicom® functions usable on the master channel

 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead
- Cyclic mode

CYCLIC Profibus
MODE L2 S7
FUNCTIONS S5 DP MPI

CREATECYC X X X
STARTCYC X X X
STOPCYC X X X
ACTCYC X X X
TRANSCYC X X X
TRANSCYCPACK X X X

CYCLIC READ Profibus

TYPE OF VARIABLE L2 S7
IN EQUIPMENT S5 DP MPI

PACKED BITS X X
INPUT PACKED BITS X X X
OUTPUT PACKED BITS X X X

PACKET BYTES X X
BYTES X
INPUT PACKED BYTES X X X
INPUT BYTES X
OUTPUT PACKED BYTES X X X
OUTPUT BYTES X
X
WORDS X
BCD WORDS X
INPUT WORDS X X X
OUTPUT WORDS X X X

32-BIT DOUBLE WORDS X X X

32-BIT IEEE FLOATING WORDS X X X

CYCLIC READ Profibus

TYPE OF VARIABLE IN L2 S7
THE EQUIPMENT S5 DP MPI
PACKED BITS X X
OUTPUT PACKED BITS X X X
PACKED BYTES X X
BYTES X
OUTPUT PACKED BYTES X X X
OUTPUT BYTES X
WORDS X X
BCD WORDS X
OUTPUT WORDS X X X
32-BIT DOUBLE WORDS X X X
32-BIT IEEE FLOATING WORDS X X X

Profibus • 58 • - applicom® functions usable on the master channel

 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead

6. - Item of image variables

- Presentation
The "item of image variables" are the syntaxes which allow to access to the variables through the
DDE server "PCDDE" or the OPC server.

Report you to sections "DDE server/Principles regarding access to Data" or "OPC server/Data
Access Principle

According to the configuration of the equipment, the descriptor is determined by default by the server.

Messaging or protocol Descriptor advised

S5 messaging S5 PLC descriptor - English syntax- German (D) and French syntax
MPI and S7 messaging Siemens series 7 PLCs descriptor
PROFIBUS DP messaging DP descriptor

Caution, if you change the default descriptor, certain optimizations of access to the equipment will
be invalidated and the performances could be modified.

You however have the possibility of using another descriptor (in particular the applicom® standard
descriptor) by the means of the advanced options.

Profibus • 59 • - Item of image variables

 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead
- Standard descriptor
The standard descriptor can be used for access to the equipments which have not specific
descriptors. The address field of the item name may be 10 digits long. It allows to compose a linear
address from 0 to 4 giga.

Unitary mode Table Mode, Matrix Mode

Bits Bx Bx_n, Bx_n_l
Input bits BIx BIx_n, BIx_n_l
Output bits BOx BOx_n, BOx_n_l
Bytes Ox Ox_n, Ox_n_l
Input bytes OIx OIx_n, OIx_n_l
Output bytes OOx OOx_n, OOx_n_l
ASCII string in internal bytes M_Ox_n
Words Wx Wx_n, Wx_n_l
Input words WIx WIx_n, WIx_n_l
Output words WOx WOx_n, WOx_n_l
ASCII string in internal words M_Wx_n
Internal double words Dx Dx_n, Dx_n_l
Internal floating words Fx Fx_n, Fx_n_l

Remark: Limits values for n and l parameters are depending on the protocol. However, in case of
PCDDE, limits cannot never be superior than 128 for bits and bytes, 64 for words, 32 for double words
and floating words.

For variable addressing, refer to the sections:

"- S5 messaging" on page 4 for the S5 messaging.
"- Supported functions" on page 11 for the DP messaging.
"- Simatic® S7 protocol" on page 18 for the MPI and S7 messaging.

To consult the read and write limits, refer to sections:

S5 messaging
"- Maximum number of variables per frame with PCDDE" on page 6
"- Maximum number of variables per frame with OPC server" on page 7

MPI, Simatic S7
"- Maximum numbers of variables by exchange with PCDDE" on page 21
"- Maximum numbers of variables by exchange with OPC server" on page 22

Profibus • 60 • - Item of image variables

 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead
- Bits => Bx (type: BIT)
(not supported in PROFIBUS DP messaging)

x: Number of the first bit.

Example: B4

- Bits => Bx_n, Bx_n_l

(not supported in PROFIBUS DP messaging)

n: Number of bits.
l: Number of bits per line (Matrix mode only).
Examples: B4_10, B4_10_5

- Input bits => BIx (type: BIT)

x: Number of the first bit.

Example: BI4

- Input bits => BIx_n, BIx_n_l

n: Number of bits.
l: Number of bits per line (Matrix mode only).
Examples : BI4_10, BI4_10_5

- Output bits => BOx (type: BIT)

x: Number of the first bit.

Example: BO4

- Output bits => BOx_n, BOx_n_l

n: Number of bits.
l: Number of bits per line (Matrix mode only).
Examples : BO4_10, BO4_10_5

- Bytes => Ox (type : BYTE)

(not supported in PROFIBUS DP messaging)

x: Number of the first byte.

Example: O4

- Bytes => Ox_n, Ox_n_l

(not supported in PROFIBUS DP messaging)

n: Number of bytes.
l: Number of bytes per line (Matrix mode only).

Profibus • 61 • - Item of image variables

 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead
Examples : O4_10, O4_10_5

- Input bytes => OIx (type: BYTE)

x: Number of the first byte.

Example: OI4

- Input bytes => OIx_n, OIx_n_l

n: Number of bytes.
l: Number of bytes per line (Matrix mode only).
Examples: OI4_10, OI4_10_5

- Output bytes => OOx (type: BYTE)

x: Number of the first byte.

Example: OO4

- Output bytes => OOx_n, OOx_n_l

n: Number of bytes.
l: Number of bytes per line (Matrix mode only).
Examples : OO4_10, OO4_10_5

- ASCII string in internal bytes => M_Ox_n (type: BYTE)

(not supported in PROFIBUS DP messaging)

For more information on the use of the ASCII string, you can consult the chapter "Use of message
mode".

x: Number of the first byte containing the string.

n: Number of potential bytes that could contain the ASCII string (1 to 131).
Example: M_O100_30

In the example, the byte array O100 to O129 can contain the string.

- Words => Wx (type: 16 bit WORD)

(not supported in PROFIBUS DP messaging)

x: Number of the first word.

Example: W4

- Words => Wx_n, Wx_n_l

(not supported in PROFIBUS DP messaging)

n: Number of words.
l: Number of words per line (Matrix mode only).

Profibus • 62 • - Item of image variables

 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead
Examples: W4_10, W4_10_5

- Input words => WIx (type: 16 bit WORD)

x: Number of the first word.

Example: WI4

- Input words => WIx_n, WIx_n_l

n: Number of words.
l: Number of words per line (Matrix mode only).
Examples: WI4_10, WI4_10_5

- Output words => WOx (type: 16 bit WORD)

x: Number of the first word.

Example: WO4

- Output words => WOx_n, WOx_n_l

n: Number of words.
l: Number of words per line (Matrix mode only).
Examples : WO4_10, WO4_10_5

- ASCII string in internal words => M_Wx_n (type: 16 bit WORD)

(not supported in PROFIBUS DP messaging)

For more information on the use of the ASCII string, you can consult the chapter "Use of message
mode".

x: Number of the first word containing the string

n: Number of potential words that could contain the ASCII string (1 to 65).
Example: M_W100_30

In the example, the word array W100 to W129 can contain the string.

- Internal double words => Dx (type: 32 bit WORD)

x: Number of the first double word.

Example: D4

- Internal double words => Dx_n, Dx_n_l

n: Number of double words.

l: Number of double words per line (Matrix mode only).
Examples : D4_10, D4_10_5

Profibus • 63 • - Item of image variables

 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead
- Internal floating words => Fx (type: 32 bit IEEE REAL)

x: Number of the first floating word.

Example: F4

- Internal floating words => Fx_n, Fx_n_l

n: Number of floating words.

l: Number of floating words per line (Matrix mode only).
Examples: F4_10, F4_10_5

Profibus • 64 • - Item of image variables

 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead
- DP descriptor
The DP descriptor has to be used for access to a DP equipment. Syntaxes are similar to the
standart descriptor ones. However, the use of this syntax allows the optimization of requests for the
PCDDE server or the OPC server.

This descriptor is the default descriptor determined by the OPC and DDE server in case of
PROFIBUS DP messaging.

Unitary mode Table Mode, Matrix Mode

Input bits BIx BIx_n, BIx_n_l
Output bits BOx BOx_n, BOx_n_l
Input bytes OIx OIx_n, OIx_n_l
Output bytes OOx OOx_n, OOx_n_l
Input words WIx WIx_n, WIx_n_l
Output words WOx WOx_n, WOx_n_l
Internal double words (Input) DIx DIx_n, DIx_n_l
Internal double words (Output) DOx DOx_n, DOx_n_l
Internal floating words (Input) FIx FIx_n, FIx_n_l
Internal floating words (Output) FOx FOx_n, FOx_n_l

Remarks:
Caution, the table and matrix mode requires some precautions. For alignment on byte addresses
when reading 16 bit words or for alignment on byte or word addresses when reading 32 bit words, writing
continues to take place in word addressing for 16 bits word and double word for 32 bits. In case of array
and matrix mode, an item symbolizing for example a word array (WOx_n_l) does not designate the same
variables in write as in read. Array and matrix mode can therefore only be used in read.

Limits values for n and l parameters are depending on the protocol. However, in case of PCDDE,
limits cannot never be superior than 128 for bits and bytes, 64 for words, 32 for double words and floating
words.

For variable addressing, refer to section:

"- Supported functions" on page 11 for the DP messaging.

Profibus • 65 • - Item of image variables

 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead

- Input bits => BIx (type: BIT)

x: Number of the first bit.

Example: BI4

- Input bits => BIx_n, BIx_n_l

n: Number of bits.
l: Number of bits per line (Matrix mode only).
Examples : BI4_10, BI4_10_5

- Output bits => BOx (type: BIT)

x: Number of the first bit.

Example: BO4

- Output bits => BOx_n, BOx_n_l

n: Number of bits.
l: Number of bits per line (Matrix mode only).
Examples : BO4_10, BO4_10_5

- Input bytes => OIx (type: BYTE)

x: Number of the first byte.

Example: OI4

- Input bytes => OIx_n, OIx_n_l

n: Number of bytes.
l: Number of bytes per line (Matrix mode only).
Examples: OI4_10, OI4_10_5

- Output bytes => OOx (type: BYTE)

x: Number of the first byte.

Example: OO4

- Output bytes => OOx_n, OOx_n_l

n: Number of bytes.
l: Number of bytes per line (Matrix mode only).
Examples : OO4_10, OO4_10_5

Profibus • 66 • - Item of image variables

 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead
- Input words => WIx (type: 16 bit WORD)

x: Number of the first word.

Example: WI4

- Input words => WIx_n, WIx_n_l

n: Number of words.
l: Number of words per line (Matrix mode only).
Examples: WI4_10, WI4_10_5

- Output words => WOx (type: 16 bit WORD)

x: Number of the first word.

Example: WO4

- Output words => WOx_n, WOx_n_l

n: Number of words.
l: Number of words per line (Matrix mode only).
Examples : WO4_10, WO4_10_5

- Internal double words (Input) => DIx (type: 32 bit WORD)

x: Number of the first double word.

Example: DI4

- Internal double words (Input) => DIx_n, DIx_n_l

n: Number of double words.

l: Number of double words per line (Matrix mode only).
Examples : DI4_10, DI4_10_5

- Internal double words (Output) => DOx (type: 32 bit WORD)

x: Number of the first double word.

Example: DO4

- Internal double words (Output) => DOx_n, DOx_n_l

n: Number of double words.

l: Number of double words per line (Matrix mode only).
Examples : DO4_10, DO4_10_5

Profibus • 67 • - Item of image variables

 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead
- Internal floating words (Input) => FIx (type: 32 bit IEEE REAL)

x: Number of the first floating word.

Example: FI4

- Internal floating words (Input) => FIx_n, FIx_n_l

n: Number of floating words.

l: Number of floating words per line (Matrix mode only).
Examples: FI4_10, FI4_10_5

- Internal floating words (Output) => FOx (type: 32 bit IEEE REAL)

x: Number of the first floating word.

Example: FO4

- Internal floating words (Output) => FOx_n, FOx_n_l

n: Number of floating words.

l: Number of floating words per line (Matrix mode only).
Examples: FO4_10, FO4_10_5

Profibus • 68 • - Item of image variables

 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead
- Siemens PLC descriptor - German (D) and French syntax
This descriptor can be used only for accessing Siemens Simatic S5 (or S7 serie) PLCs via the
applicom® PC1500PFB or PCI1500PFB interfaces in S5 messaging mode.

Caution:

SFlags and DX cannot be accessed with all Siemens CPUs.

For access to words in flag bytes or SFlags, to input words or output words, these are accessed in
a byte zone, word 1 being composed of bytes 1 and 2, word 2 of bytes 2 and 3, and so on. The words
thus overlap one another.

Where access to double words and floating words in flag bytes or in SFlags is concerned, these
variables are accessed in a byte zone, double word 1 being composed of bytes 1, 2, 3 and 4, double word
2 of bytes 2, 3, 4 and 5, and so on. The variables thus overlap one another.

Remark: Limits values for n and l parameters are depending on the protocol. However, in case of
PCDDE, limits cannot never be superior than 128 for bits and bytes, 64 for words, 32 for double words
and floating words.

To consult the read and write limits, refer to sections:

S5 messaging
"- Maximum number of variables per frame with PCDDE" on page 6
"- Maximum number of variables per frame with OPC server" on page 7

For variable addressing, refer to the sections:

"- S5 messaging" on page 4 for the S5 messaging.

Profibus • 69 • - Item of image variables

 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead

Unitary mode Table Mode, Matrix Mode

Bits in flag bytes Mx.y Mx.y_n, Mx.y_n_l
Bits in SFlags (internal bytes) Sx.y Sx.y_n, Sx.y_n_l
Input bits Ex.y Ex.y_n, Ex.y_n_l
Output bits Ax.y Ax.y_n, Ax.y_n_l
Bits of DB word DBxDy.z DBxDy.z_n, DBxDy.z_n_l
Bits of DX word DXxDy.z DXxDy.z_n, DXxDy.z_n_l
Flag bytes MBx MBx_n, MBx_n_l
SFlags (internal bytes) SYx SYx_n, SYx_n_l
Input bytes EBx EBx_n, EBx_n_l
Output bytes ABx ABx_n, ABx_n_l
ASCII string in flag bytes M_MBx_n
ASCII string in Sflags M_SYx_n
Words in flag bytes MWx MWx_n, MWx_n_l
Words in SFlags (internal bytes) SWx SWx_n, SWx_n_l
Input words EWx EWx_n, EWx_n_l
Output words AWx AWx_n, AWx_n_l
Words in DB DBxDWy DBxDWy_n, DBxDWy_n_l
Words in DX DXxDWy DXxDWy_n, DXxDWy_n_l
Right byte of a word in the DB DBxDRy
Left byte of a word in the DB DBxDLy
Right byte of a word in the DX DXxDRy
Left byte of a word in the DX DXxDLy
ASCII string in DB words M_DBxDWy_n
ASCII string in DX words M_DXxDWy_n
Double words in flag bytes MDx MDx_n, MDx_n_l
Double words in Sflags SDx SDx_n, SDx_n_l
Floating words in flag bytes MDxKG
Floating words in Sflags SDxKG
Double words in DB DBxDDy DBxDDy_n, DBxDDy_n_l
Double words in DX DXxDDy DXxDDy_n, DXxDDy_n_l
Floating words in the DB DBxDDyKG
Floating words in the DX DXxDDyKG
Timers TBx TBx_n, TBx_n_l
Counters ZBx ZBx_n, ZBx_n_l

Profibus • 70 • - Item of image variables

 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead
- Bits in flag bytes => Mx.y or Mx:y (type: BIT)

x: Flag byte number (0 to 255).

y: First bit range in flag byte (0 to 7).
Example: M94.7 or M94:7

- Bits in flag bytes => Mx.y_n or Mx:y_n, Mx.y_n_l or Mx:y_n_l

n: Number of bits.
l: Number of bits per line (Matrix mode only).
Examples : M94.7_24 or M94:7_24, M94.7_24_8 or M94:7_24_8

- Bits in SFlags (internal bytes) => Sx.y or Sx:y (type: BIT)

x: SFlag number (0 to 4095).

y: First bit range in SFlag (0 to 7).
Example: S94.7 or S94:7

- Bits in SFlags (internal bytes) => Sx.y_n or Sx:y_n, Sx.y_n_l or

Sx:y_n_l

n: Number of bits.
l: Number of bits per line (Matrix mode only).
Examples : S94.7_24 or S94:7_24, S94.7_24_8 or S94:7_24_8

- Input bits => Ex.y or Ex:y (type: BIT)

x: Number of the input byte (0 to 127).

y: Rank of the first bit in the input byte (0 to 7).
Example : E94.7 or E94:7

- Input bits => Ex.y_n or Ex:y_n, Ex.y_n_l or Ex:y_n_l

n: Number of bits.
l: Number of bits per line (Matrix mode only).
Examples : E94.7_24 or E94:7_24, E94.7_24_8 or E94:7_24_8

- Output bits => Ax.y or Ax:y (type: BIT)

x: Number of the output byte (0 to 127).

y: Rank of the first bit in the output byte (0 to 7).
Example: A94.7 or A94:7

- Output bits => Ax.y_n or Ax:y_n, Ax.y_n_l or Ax:y_n_l

n: Number of bits.

Profibus • 71 • - Item of image variables

 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead
l: Number of bits per line (Matrix mode only).
Examples: A94.7_24 or A94:7_24, A94.7_24_8 or A94:7_24_8

- Bits of DB word => DBxDy.z or DBxDy:z (type: BIT)

x: DB number (1 to 255).
y: First DB word number (0 to 255).
z: First bit range (0 to 15).
Example: DB94D10.7 or DB94D10:7

- Bits of DB word => DBxDy.z_n or DBxDy:z_n, DBxDy.z_n_l or

DBxDy:z_n_l

n: Number of bits.
l : Number of bits per line (Matrix mode only)
Examples : DB94D10.7_24 or DB94D10:7_24, DB2D3.7_24_8 or DB2D3:7_24_8

- Bits of DX word => DXxDy.z or DXxDy:z (type: BIT)

x: DX number (0 to 255).
y: First DX word number (0 to 255).
z: First bit range (0 to 15).
Example: DX94D10.7 or DX94D10:7

- Bits of DX word => DXxDy.z_n or DXxDy:z_n, DXxDy.z_n_l or

DXxDy:z_n_l

n: Number of bits.
l : Number of bits per line (Matrix mode only)
Examples : DX94D10.7_24 or DX94D10:7_24, DX2D3.7_24_8 or DX2D3:7_24_8

- Flag bytes => MBx (type: BYTE)

x: First flag byte number (0 to 255).

Example: MB4

- Flag bytes => MBx_n, MBx_n_l

n: Number of bytes.
l: Number of bytes per line (Matrix mode only).
Examples: MB4_10, MB4_10_5

- SFlags (internal bytes) => SYx (type: BYTE)

x: First SFlag number (0 to 4095).

Example: SY4

Profibus • 72 • - Item of image variables

 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead
- SFlags (internal bytes) => SYx_n, SYx_n_l

n: Number of bytes.
l: Number of bytes per line (Matrix mode only).
Examples: SY4_10, SY4_10_5

- Input bytes => EBx (type: BYTE)

x: Number of the first input byte (0 to 127).

Example: EB4

- Input bytes => EBx_n, EBx_n_l

n: Number of bytes.
l: Number of bytes per line (Matrix mode only).
Examples : EB4_10, EB4_10_5

- Output bytes => ABx (type: BYTE)

x: Number of the first output byte (0 to 127).

Example: AB4

- Output bytes => ABx_n, ABx_n_l

n: Number of bytes.
l: Number of bytes per line (Matrix mode only).
Examples: AB4_10, AB4_10_5

- ASCII string in flag bytes => M_MBx_n (type: BYTE)

For more information on the use of the ASCII string, you can consult the chapter "Use of message
mode".

x: Number of first flag byte containing the string (0 to 255).

n: Number of potential flag byte which can contain the ASCII string (1 to 131).
Example: M_MB100_10

In the example the byte array MB100 to MB109 can contain the string.

- ASCII string in SFlags => M_SYx_n (type: BYTE)

For more information on the use of the ASCII string, you can consult the chapter "Use of message
mode".

x: Number of first SFlag containing the string (0 to 4095).

n: Number of potential SFlags which can contain the ASCII string (1 to 131).
Example: M_SY100_10

Profibus • 73 • - Item of image variables

 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead
In the example the byte array SY100 to SY109 can contain the string.

- Words in flag bytes => MWx (type: 16 bit WORD)

x: Number of the first word (0 to 254).

Example: MW4

- Words in flag bytes => MWx_n, MWx_n_l

n: Number of words.
l: Number of words per line (Matrix mode only).
Examples : MW4_10, MW4_10_5

- Words in SFlags (internal bytes) => SWx (type: 16 bit WORD)

x: Number of the first word (0 to 4094).

Example: SW4

- Words in SFlags (internal bytes) => SWx_n, SWx_n_l

n: Number of words.
l: Number of words per line (Matrix mode only).
Examples : SW4_10, SW4_10_5

- Input words => EWx (type: 16 bit WORD)

x: Number of the first word (0 to 126).

Example: EW4

- Input words => EWx_n, EWx_n_l

n: Number of words.
l: Number of words per line (Matrix mode only).
Examples : EW4_10, EW4_10_5

- Output words => AWx (type: 16 bit WORD)

x: Number of the first word (0 to 126).

Example: AW4

- Output words => AWx_n, AWx_n_l

n: Number of words.
l: Number of words per line (Matrix mode only).
Examples: AW4_10, AW4_10_5

Profibus • 74 • - Item of image variables

 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead

- Words in DB => DBxDWy (type: 16 bit WORD)

x: DB number (1 to 255).
y: Number of the first word in the DB (0 to 255).
Example: DB4DW8

- Words in DB => DBxDWy_n, DBxDWy_n_l

n: Number of words.
l: Number of words per line (Matrix mode only).
Examples : DB4DW8_10, DB4DW8_10_5

- Words in DX => DXxDWy (type: 16 bit WORD)

x: DX number (0 to 255).
y: Number of the first word in the DX (0 to 255).
Example: DX4DW8

- Words in DX => DXxDWy_n, DXxDWy_n_l

n: Number of words.
l: Number of words per line (Matrix mode only).
Examples : DX4DW8_10, DX4DW8_10_5

- Right byte of a word in the DB => DBxDRy (type: BIT)

For this syntax, the maximum numbers of variables per frame are:
-in read: 128*2
- in write: 1

x: DB number (1 to 255).
y: Number of the word in the DB (0 to 255).
Example: DB4DR5

- Left byte of a word in the DB => DBxDLy (type: BIT)

For this syntax, the maximum numbers of variables per frame are:
- in read: 128*2
- in write: 1

x: DB number (1 to 255).
y: Number of the word in the DB (0 to 255).
Example: DB4DL5

- Right byte of a word in the DX => DXxDRy (type: BIT)

For this syntax, the maximum numbers of variables per frame are:

Profibus • 75 • - Item of image variables

 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead
- in read: 128*2
- in write: 1

x: DX number (0 to 255).
y: Number of the word in the DX (0 to 255).
Example: DX4DR5

- Left byte of a word in the DX => DXxDLy (type: BIT)

For this syntax, the maximum numbers of variables per frame are:
- in read: 128*2
- in write: 1

x: DX number (0 to 255).
y: Number of the word in the DX (0 to 255).
Example: DX4DL5

- ASCII string in DB words => M_DBxDWy_n (type: 16 bit WORD)

For more information on the use of the ASCII string, you can consult the chapter "Use of message
mode".

x: DB number (1 to 255).
y: Number of the first word in the DB containing the string (0 to 255).
n: Number of potential words that could contain the ASCII string (1 to 65).
Example: M_DB4DW0_10
In the example the word array DB4DW0 to DB4DW9 can contain the string.

- ASCII string in DX words => M_DXxDWy_n (type: 16 bit WORD)

For more information on the use of the ASCII string, you can consult the chapter "Use of message
mode".

x: DX number (0 to 255).
y: Number of the first word in the DX containing the string (0 to 255).
n: Number of potential words that could contain the ASCII string (1 to 65).
Example: M_DX4DW0_10
In the example the word array DX4DW0 to DX4DW9 can contain the string.

- Double words in flag bytes => MDx (type: 32 bit WORD)

x: First flag byte number (0 to 255).

Example: MD4

- Double words in flag bytes => MDx_n, MDx_n_l

n: Number of double words.

l: Number of double words per line (Matrix mode only).
Examples: MD4_10, MD4_10_5

Profibus • 76 • - Item of image variables

 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead
- Double words in SFlags => SDx (type: 32 bit WORD)

x: First SFlag number (0 to 4095).

Example: SD4

- Double words in SFlags => SDx_n, SDx_n_l

n: Number of double words.

l: Number of double words per line (Matrix mode only).
Examples: SD4_10, SD4_10_5

- Floating words in flag bytes => MDxKG (type: 32 bit IEEE REAL)

x: Number of the floating word (0 to 252).

KG: Suffix used to convert a word into KG format of Siemens PLCs to IEEE format.
Example: MD48KG

- Floating words in SFlags => SDxKG (type: 32 bit IEEE REAL)

x: Number of the floating word (0 to 4092).

KG: Suffix used to convert a word into KG format of Siemens PLCs to IEEE format.
Example: SD48KG

- Double words in DB => DBxDDy (type: 32 bit WORD)

x: DB number (1 to 255).
y: First DB word number (0 to 254).
Example: DB4DD8

- Double words in DB => DBxDDy_n, DBxDDy_n

n: Number of double words.

l: Number of double words per line (Matrix mode only).
Examples : DB4DD8_10, DB4DD8_10_5

- Double words in DX => DXxDDy (type: 32 bit WORD)

x: DX number (0 to 255).
y: First DX word number (0 to 254).
Example: DX4DD8

- Double words in DX => DXxDDy_n, DXxDDy_n

n: Number of double words.

l: Number of double words per line (Matrix mode only).
Examples : DX4DD8_10, DX4DD8_10_5

Profibus • 77 • - Item of image variables

 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead
- Floating words in DB => DBxDDyKG (type REEL IEEE 32 bits)

x: DB number (1 to 255).
y: First DB word number (0 to 254).
KG: Suffix used to convert a word into KG format of Siemens PLCs to IEEE format.
Example : DB4DD8KG

- Floating words in DX => DXxDDyKG (type REEL IEEE 32 bits)

x: DX number (0 to 255).
y: First DX word number (0 to 254).
KG: Suffix used to convert a word into KG format of Siemens PLCs to IEEE format.
Example : DX4DD8KG

- Timers => TBx (type: 16 bit WORD)

x: Number of the timer (0 to 255).

Example: TB4

- Timers => TBx_n, TBx_n_l

n: Number of timers.
l: Number of timers per line (Matrix mode only).
Examples : TB4_10, TB4_10_5

- Counters => ZBx (type: 16 bit WORD)

x: Number of the counter (0 to 255).

Example: ZB4

- Counters => ZBx_n, ZBx_n_l

n: Number of counters.
l: Number of counters per line (Matrix mode only).
Examples : ZB4_10, ZB4_10_5

Profibus • 78 • - Item of image variables

 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead
- Siemens S5 PLC descriptor - English syntax
This descriptor can be used only for accessing Siemens Simatic S5 (or S7 serie) PLCs via the
applicom® PC1500PFB or PCI1500PFB interfaces in S5 messaging mode.

For strings and matrices, the Descriptor checks for acceptable addressing limits, thus avoiding data
overlap.

Caution:

SFlags and DX cannot be accessed with all Siemens CPUs.

For access to words in flag bytes or SFlags, to input words or output words, these are accessed in
a byte zone, word 1 being composed of bytes 1 and 2, word 2 of bytes 2 and 3, and so on. The words
thus overlap one another.

Where access to double words and floating words in flag bytes or in SFlags is concerned, these
variables are accessed in a byte zone, double word 1 being composed of bytes 1, 2, 3 and 4, double word
2 of bytes 2, 3, 4 and 5, and so on. The variables thus overlap one another.

Remark: Limits values for n and l parameters are depending on the protocol. However, in case of
PCDDE, limits cannot never be superior than 128 for bits and bytes, 64 for words, 32 for double words
and floating words.

To consult the read and write limits, refer to sections:

S5 messaging
"- Maximum number of variables per frame with PCDDE" on page 6
"- Maximum number of variables per frame with OPC server" on page 7

For variable addressing, refer to the sections:

"- S5 messaging" on page 4 for the S5 messaging.

Profibus • 79 • - Item of image variables

 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead

Unitary mode Table Mode, Matrix Mode

Bits in flag bytes Fx.y Fx.y_n, Fx.y_n_l
Bits in SFlags (internal bytes) Sx.y Sx.y_n, Sx.y_n_l
Input bits Ix.y Ix.y_n, Ix.y_n_l
Output bits Qx.y Qx.y_n, Qx.y_n_l
Bits of DB word DBxDy.z DBxDy.z_n, DBxDy.z_n_l
Bits of DX word DXxDy.z DXxDy.z_n, DXxDy.z_n_l
Flag bytes FYx FYx_n, FYx_n_l
Sflags (internal bytes) SYx SYx_n, SYx_n_l
Input bytes IBx IBx_n, IBx_n_l
Output bytes QYx QYx_n, QYx_n_l
ASCII string in flag bytes M_FYx_n
ASCII string in SFlags M_SYx_n
Words in flag bytes FWx FWx_n, FWx_n_l
Words in SFlags (internal bytes) SWx SWx_n, SWx_n_l
Input words IWx IWx_n, IWx_n_l
Output words QWx QWx_n, QWx_n_l
Words in DB DBxDWy DBxDWy_n, DBxDWy_n_l
Words in DX DXxDWy DXxDWy_n, DXxDWy_n_l
Right byte of a word in the DB DBxDRy
Left byte of a word in the DB DBxDLy
Right byte of a word in the DX DXxDRy
Left byte of a word in the DX DXxDLy
ASCII string in DB words M_DBxDWy_n
ASCII string in DX words M_DXxDWy_n
Double words in flag bytes FDx FDx_n, FDx_n_l
Double words in SFlags SDx SDx_n, SDx_n_l
Floating words in flag bytes FDxKG
Floating words in SFlags SDxKG
Double words in DB DBxDDy DBxDDy_n, DBxDDy_n_l
Double words in DX DXxDDy DXxDDy_n, DXxDDy_n_l
Floating words in DB DBxDDyKG
Floating words in DX DXxDDyKG
Timers TBx TBx_n, TBx_n_l
Counters ZBx ZBx_n, ZBx_n_l

Profibus • 80 • - Item of image variables

 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead
- Bits in flag bytes => Fx.y or Fx:y (type: BIT)

x: Flag byte number (0 to 255).

y: First bit range in flag byte (0 to 7).
Example: F94.7 or F94:7

- Bits in flag bytes => Fx.y_n or Fx:y_n, Fx.y_n_l or Fx:y_n_l

n: Number of bits.
l: Number of bits per line (Matrix mode only).
Examples: F94.7_24 or F94:7_24, F94.7_24_8 or F94:7_24_8

- Bits in SFlags (internal bytes) => Sx.y or Sx:y (type: BIT)

x: SFlag number (0 to 4095).

y: First bit range in SFlag (0 to 7).
Example: S94.7 or S94:7

- Bits in SFlags (internal bytes) => Sx.y_n or Sx:y_n, Sx.y_n_l or

Sx:y_n_l

n: Number of bits.
l: Number of bits per line (Matrix mode only).
Examples: S94.7_24 or S94:7_24, S94.7_24_8 or S94:7_24_8

- Input bits => Ix.y or Ix:y (type: BIT)

x: Number of the input byte (0 to 127).

y: Rank of the first bit in the input byte (0 to 7).
Example: I94.7 or I94:7

- Input bits => Ix.y_n or Ix:y_n, Ix.y_n_l or Ix:y_n_l

n: Number of bits.
l: Number of bits per line (Matrix mode only).
Examples : I94.7_24 or I94:7_24, I94.7_24_8 or I94:7_24_8

- Output bits => Qx.y or Qx:y (type: BIT)

x: Number of the output byte (0 to 127).

y: Rank of the first bit in the output byte (0 to 7).
Example : Q94.7 or Q94:7

- Output bits => Qx.y_n or Qx:y_n, Qx.y_n_l or Qx:y_n_l

n: Number of bits.

Profibus • 81 • - Item of image variables

 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead
l: Number of bits per line (Matrix mode only).
Examples : Q94.7_24 or Q94:7_24, Q94.7_24_8 or Q94:7_24_8

- Bits of DB word => DBxDy.z or DBxDy:z (type: BIT)

x: DB number (1 to 255).
y: Number of the first word in the DB (0 to 255).
z: Rank of the first bit (0 to 15).
Example: DB94D10.7 or DB94D10:7

- Bits of DB word => DBxDy.z_n or DBxDy:z_n, DBxDy.z_n_l or

DBxDy:z_n_l

n: Number of bits.
l: Number of bits per line (Matrix mode only).
Examples : DB94D10.7_24 or DB94D10:7_24, DB2D3.7_24_8 or DB2D3:7_24_8

- Bits of DX word => DXxDy.z or DXxDy:z (type: BIT)

x: DX number (0 to 255).
y: Number of the first word in the DX (0 to 255).
z: Rank of the first bit (0 to 15).
Example: DX94D10.7 or DX94D10:7

- Bits of DX word => DXxDy.z_n or DXxDy:z_n, DXxDy.z_n_l or

DXxDy:z_n_l

n: Number of bits.
l: Number of bits per line (Matrix mode only).
Examples : DX94D10.7_24 or DX94D10:7_24, DX2D3.7_24_8 or DX2D3:7_24_8

- Flag bytes => FYx (type: BYTE)

x: First flag byte number (0 to 255).

Example: FY4

- Flag bytes => FYx_n, FYx_n_l

n: Number of bytes.
l: Number of bytes per line (Matrix mode only).
Examples : FY4_10 or FY4_10_5

- SFlags (internal bytes) => SYx (type: BYTE)

x: First SFlag number (0 to 4095).

Example: SY4

Profibus • 82 • - Item of image variables

 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead
- SFlags (internal bytes) => SYx_n, SYx_n_l

n: Number of bytes.
l: Number of bytes per line (Matrix mode only).
Examples : SY4_10 or SY4_10_5

- Input bytes => IBx (type: BYTE)

x: Number of the first input byte (0 to 127).

Example: IB4

- Input bytes => IBx_n, IBx_n_l

n: Number of bytes.
l: Number of bytes per line (Matrix mode only).
Examples : IB4_10, IB4_10_5

- Output bytes => QYx (type: BYTE)

x: Number of the first output byte (0 to 127).

Example: QY4

- Output bytes => QYx_n, QYx_n_l

n: Number of bytes.
l: Number of bytes per line (Matrix mode only).
Examples: QY4_10, QY4_10_5

- ASCII string in flag bytes => M_FYx_n (type: BYTE)

For more information on the use of the ASCII string, you can consult the chapter "Use of message
mode".

x: Number of first flag byte containing the string (0 to 255).

n: Number of potential flag byte that could contain the ASCII string (1 to 131).
Example: M_FY100_10

In the example the flag bytes array FY100 to FY109 can contain the string.

- ASCII string in SFlags => M_SYx_n (type: BYTE)

For more information on the use of the ASCII string, you can consult the chapter "Use of message
mode".

x: Number of first SFlag containing the string (0 to 4095).

n: Number of potential SFlags byte that could contain the ASCII string (1 to 131).

Profibus • 83 • - Item of image variables

 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead
Example: M_SY100_10

In the example the flag bytes array SY100 to SY109 can contain the string.

- Words in flag bytes => FWx (type: 16 bit WORD)

x: Number of the first word (0 to 254).

Example: FW4

- Words in flag bytes => FWx_n, FWx_n_l

n: Number of words.
l: Number of words per line (Matrix mode only).
Examples : FW4_10, FW4_10_5

- Words in SFlags (internal bytes) => SWx (type: 16 bit WORD)

x: Number of the first word (0 to 4094).

Example: SW4

- Words in SFlags (internal bytes) => SWx_n, SWx_n_l

n: Number of words.
l: Number of words per line (Matrix mode only).
Examples : SW4_10, SW4_10_5

- Input words => IWx (type: 16 bit WORD)

x: Number of the first word (0 to 126).

Example: IW4

- Input words => IWx_n, IWx_n_l

n: Number of words.
l: Number of words per line (Matrix mode only).
Examples : IW4_10, IW4_10_5

- Output words => QWx (type: 16 bit WORD)

x: Number of the first word (0 to 126).

Example: QW4

- Output words => QWx_n, QWx_n_l

n: Number of words.
l: Number of words per line (Matrix mode only).

Profibus • 84 • - Item of image variables

 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead
Examples: QW4_10, QW4_10_5

- Words in DB => DBxDWy (type: 16 bit WORD)

x: DB number (1 to 255).
y: Number of the first word in the DB (0 to 255).
Example: DB4DW8

- Words in DB => DBxDWy_n, DBxDWy_n_l

n: Number of words.
l: Number of words per line (Matrix mode only).
Example : DB4DW8_10, DB4DW8_10_5

- Words in DX => DXxDWy (type: 16 bit WORD)

x: DX number (0 to 255).
y: Number of the first word in the DX (0 to 255).
Example: DX4DW8

- Words in DX => DXxDWy_n, DXxDWy_n_l

n: Number of words.
l: Number of words per line (Matrix mode only).
Example : DX4DW8_10, DX4DW8_10_5

- Right byte of a word in the DB => DBxDRy (type: BIT)

For this syntax, the maximum numbers of variables per frame are:
- in read: 128*2
- in write: 1

x: DB number (1 to 255).
y: Number of the word in the DB (0 to 255).
Example: DB4DR5

- Left byte of a word in the DB => DBxDLy (type: BIT)

For this syntax, the maximum numbers of variables per frame are:
- in read: 128*2
- in write: 1

x: DB number (1 to 255).
y: Number of the word in the DB (0 to 255).
Example : DB4DL5

Profibus • 85 • - Item of image variables

 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead
- Right byte of a word in the DX => DXxDRy (type: BIT)

For this syntax, the maximum numbers of variables per frame are:
- in read: 128*2
- in write: 1

x: DX number (0 to 255).
y: Number of the word in the DX (0 to 255).
Example: DX4DR5

- Left byte of a word in the DX => DXxDLy (type: BIT)

For this syntax, the maximum numbers of variables per frame are:
- in read: 128*2
- in write: 1

x: DB number (0 to 255).
y: Number of the word in the DX (0 to 255).
Example : DX4DL5

- ASCII string in DB words => M_DBxDWy_n (type: 16 bit WORD)

For more information on the use of the ASCII string, you can consult the chapter "Use of message
mode".

x: DB number (1 to 255).
y: Number of the first word in the DB containing the string (0 to 255).
n: Number of potential words that could contain the ASCII string (1 to 65).
Example: M_DB4DW0_10
In the example the word array DB4DW0 to DB4DW9 can contain the string.

- ASCII string in DX words => M_DXxDWy_n (type: 16 bit WORD)

For more information on the use of the ASCII string, you can consult the chapter "Use of message
mode".

x: DX number (0 to 255).
y: Number of the first word in the DX containing the string (0 to 255).
n: Number of potential words that could contain the ASCII string (1 to 65).
Example: M_DX4DW0_10
In the example the word array DX4DW0 to DX4DW9 can contain the string.

- Double words in flag bytes => FDx (type: 32 bit WORD)

x: First flag byte number (0 to 255).

Example: FD4

- Double words in flag bytes => FDx_n, FDx_n_l

Profibus • 86 • - Item of image variables

 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead
n: Number of double words.
l: Number of double words per line (Matrix mode only).
Examples: FD4_10, FD4_10_5

- Double words in SFlags => SDx (type: 32 bit WORD)

x: First SFlag number (0 to 4095).

Example: SD4

- Double words in SFlags => SDx_n, SDx_n_l

n: Number of double words.

l: Number of double words per line (Matrix mode only).
Examples: SD4_10, SD4_10_5

- Floating words in flag bytes => FDxKG (type: 32 bit IEEE REAL)

x: Number of the floating word (0 to 252).

KG: Suffix used to convert a word into KG format of Siemens PLCs to IEEE format.
Example: FD48KG

- Floating words in SFlags => SDxKG (type: 32 bit IEEE REAL)

x: Number of the floating word (0 to 4092).

KG: Suffix used to convert a word into KG format of Siemens PLCs to IEEE format.
Example: SD48KG

- Double words in DB => DBxDDy (type: 32 bit WORD)

x: DB number (1 to 255).
y: First DB word number (0 to 254).
Example: DB4DD8

- Double words in DB => DBxDDy_n, DBxDDy_n_l

n: Number of double words.

l: Number of double words per line (Matrix mode only).
Examples : DB4DD8_10, DB4DD8_10_5

- Double words in DX => DXxDDy (type: 32 bit WORD)

x: DX number (0 to 255).
y: First DX word number (0 to 254).
Example: DX4DD8

Profibus • 87 • - Item of image variables

 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead
- Double words in DX => DXxDDy_n, DXxDDy_n_l

n: Number of double words.

l: Number of double words per line (Matrix mode only).
Examples : DX4DD8_10, DX4DD8_10_5

- Floating words in DB => DBxDDyKG (type: 32 bit IEEE REAL)

x: DB number (1 to 255).
y: First DB word number (0 to 254).
KG: Suffix used to convert a word into KG format of Siemens PLCs to IEEE format.
Example : DB4DD8KG

- Floating words in DX => DXxDDyKG (type: 32 bit IEEE REAL)

x: DX number (0 to 255).
y: First DX word number (0 to 254).
KG: Suffix used to convert a word into KG format of Siemens PLCs to IEEE format.
Example : DX4DD8KG

- Timers => TBx (type: 16 bit WORD)

x: Number of the timer (0 to 255).

Example: TB4

- Timers => TBx_n, TBx_n_l

n: Number of timers.
l: Number of timers per line (Matrix mode only).
Examples : TB4_10, TB4_10_5

- Counters => ZBx (type: 16 bit WORD)

x: Number of the counter (0 to 255).

Example: ZB4

- Counters => ZBx_n, ZBx_n_l

n: Number of counters.
l: Number of counters per line (Matrix mode only).
Examples : ZB4_10, ZB4_10_5

Profibus • 88 • - Item of image variables

 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead
- Siemens series 7 PLCs descriptor for MPI and S7
This descriptor can be used when accessing Siemens S7-300 and S7-400 PLCs for MPI and S7
messaging.

For MPI messaging and the S7 protocol, it is essential to use Siemens series 7 descriptor.

Unitary mode Table Mode, Matrix Mode

Marker bits Mx.y Mx.y_n, Mx.y_n_l
Input bits Ex.y Ex.y_n, Ex.y_n_l
Output bits Ax.y Ax.y_n, Ax.y_n_l
Bits of bytes in the DB DBx.DBXy.z DBx.DBXy.z_n, DBx.DBXy.z_n_l
Marker bytes MBx MBx_n, MBx_n_l
Bytes in the DB DBx.DBBy DBx.DBBy_n, DBx.DBBy_n_l
Input bytes EBx EBx_n, EBx_n_l
Output bytes ABx ABx_n, ABx_n_l
ASCII string in the marker bytes M_MBx_n
ASCII string in the DB bytes M_DBx.DBBy_n
Words in the markers MWx MWx_n, MWx_n_l
Words in the DB DBx.DBWy DBx.DBWy_n, DBx.DBWy_n_l
Input words EWx Ewx_n, Ewx_n_l
Output words AWx Awx_n, Awx_n_l
Double words in the markers MDx MDx_n, MDx_n_l
Double words in the DB DBx.DBDy DBx.DBDy_n, DBx.DBDy_n_l
Floating words in the markers MDxF MDxF_n, MDxF_n_l
Floating words in the DB DBx.DBDyF DBx.DBDyF_n, DBx.DBDyF_n_l
Timers Tx Tx_n, Tx_n_l
Counters Zx Zx_n, Zx_n_l

Remarks:

Caution, the table and matrix mode requires some precautions. For alignment on byte addresses
when reading 16 bit words or for alignment on byte or word addresses when reading 32 bit words, writing
continues to take place in word addressing for 16 bits word and double word for 32 bits. In case of array
and matrix mode, an item symbolizing for example a word array (WOx_n_l) does not designate the same
variables in write as in read. Array and matrix mode can therefore only be used in read.

Limits values for n and l parameters are depending on the protocol. However, in case of PCDDE,
limits cannot never be superior than 128 for bits and bytes, 64 for words, 32 for double words and floating
words.

To consult the read and write limits, refer to sections:

MPI, Simatic S7
"- Maximum numbers of variables by exchange with PCDDE" on page 21
"- Maximum numbers of variables by exchange with OPC server" on page 22

For variable addressing, refer to the sections:

"- Simatic® S7 protocol" on page 18 for the MPI and S7 messaging.

Profibus • 89 • - Item of image variables

 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead
- Marker bits => Mx.y (type: BIT)

x: Number of the marker (0 to 65 535).

y: Rank of the first bit in the marker (0 to 7).
Example : M94.7

- Marker bits => Mx.y_n, Mx.y_n_l

n: Number of bits.
l: Number of bits per line (Matrix mode only).
Examples : M94.7_24, M94.7_24_8

- Input bits => Ex.y (type: BIT)

x: Number of the input byte (0 to 65 535).

y: Rank of the first bit in the input byte (0 to 7).
Example : E94.7

- Input bits => Ex.y_n, Ex.y_n_l

n: Number of bits.
l: Number of bits per line (Matrix mode only).
Examples : E94.7_24, E94.7_24_8

- Output bits => Ax.y (type: BIT)

x: Number of the output byte (0 to 65535).

y: Rank of the first bit in the output byte (0 to 7).
Example : A94.7

- Output bits => Ax.y_n, Ax.y_n_l

n: Number of bits.
l: Number of bits per line (Matrix mode only).
Examples : A94.7_24, A94.7_24_8

- Bits of bytes in the DBs => DBx. DBXy.z (type: BIT)

x: DB number (1 to 8191).
y: Number of the first word in the DB (0 to 65535).
z: Rank of the first bit (0 to 7).
Example : DB94.DBX3.7

- Bits of bytes in the DBs => DBx. DBXy.z_n, DBx.DBXy.z _n_l

n: Number of bits.

Profibus • 90 • - Item of image variables

 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead
l: Number of bits per line (Matrix mode only).
Examples : DB94.DBX3.7_24, DB94.DBX3.7_24_8

- Marker bytes => MBx (type: BYTE)

x: Number of the first marker (0 to 65535).

Example : MB4

- Marker bytes => MBx_n, MBx_n_l

n: Number of bytes.
l: Number of bytes per line (Matrix mode only).
Examples : MB4_10, MB4_10_5

- Bytes in the DBs => DBx.DBBy (type: BYTE)

x : DB number (1 to 32 767).
y : Byte number (0 to 65 535).
Example : DB4.DBB5

- Bytes in the DBs => DBx.DBBy_n, DBx.DBBy _n_l

n: Number of bytes.
l: Number of bytes per line (Matrix mode only).
Examples : DB4.DBB5_10, DB4.DBB5_10_2

- Input bytes => EBx (type: BYTE)

x: Number of the first input byte (0 to 65535).

Example : EB4

- Input bytes => EBx_n, EBx_n_l

n: Number of bytes.
l: Number of bytes per line (Matrix mode only).
Examples : EB4_10, EB4_10_5

- Output bytes => ABx (type: BYTE)

x: Number of the first output byte (0 to 65535).

Example : AB4

- Output bytes => ABx_n, ABx_n_l

n: Number of bytes.
l: Number of bytes per line (Matrix mode only).
Examples : AB4_10, AB4_10_5

Profibus • 91 • - Item of image variables

 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead

- ASCII string in the marker bytes => M_MBx_n (type: BYTE)

For more information on the use of the ASCII string, you can consult the chapter "Use of message
mode".

x: Number of the first byte containing the string (0 to 65535).

n: Number of potential bytes that could contain the ASCII string (1 to 131).
Example : M_MB100_10
In the example the byte array MB100 to MB109 can contain the string.

- ASCII string in the DB bytes => M_DBx.DBBy_n (type: BYTE)

For more information on the use of the ASCII string, you can consult the chapter "Use of message
mode".

x : DB number (0 to 32 767).
y: Number of the first byte containing the string (0 to 65535).
n: Number of potential marker bytes that could contain the ASCII string (1 to 131).
Example : M_DB1.DBB5_10
In the example the byte array DB1.DBB5 to DB1.DBB14 can contain the string.

- Words in the markers => MWx (type: 16 bit WORD)

x: Number of the first word (0 to 65534).

Example : MW4

- Words in the markers => MWx_n, MWx_n_l (type: 16 bit WORD)

n: Number of words.
l: Number of bytes per line (Matrix mode only).
Example : MW4_10, MW4_10_5

- Words in the DB => DBx.DBWy (type: 16 bit WORD)

x : DB number (0 to 32 767).
y: Number of the first word (0 to 65 534).
Example : DB4.DBW6

- Words in the DB => DBx.DBWy_n, DBx.DBWy_n_l (type: 16 bit

WORD)

n: Number of words.
l: Number of bytes per line (Matrix mode only).
Example : DB4.DBW6_10, DB4.DBW6_10_5

Profibus • 92 • - Item of image variables

 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead
- Input words => EWx (type: 16 bit WORD)

x: Number of the first word (0 to 65 534).

Example : EW4

- Input words => Ewx_n, Ewx_n_l (type: 16 bit WORD)

n: Number of words.
l: Number of bytes per line (Matrix mode only).
Example : EW4_10, EW4_10_5

- Output words => AWx (type: 16 bit WORD)

x: Number of the first word (0 to 65 534).

Example : AW4

- Output words => Awx_n, Awx_n_l(type: 16 bit WORD)

n: Number of words.
l: Number of bytes per line (Matrix mode only).
Example : AW4_10, AW4_10_5

- Double words in the markers => MDx (type: 32 bit WORD)

x : Byte number (0 to 65 532).

Example : MD4

- Double words in the markers => MDx_n, MDx_n_l (type: 32 bit WORD)

n: Number of words.
l: Number of bytes per line (Matrix mode only).
Example : MD4_10, MD4_10_5

- Double words in the DB => DBx.DBDy (type: 32 bit WORD)

x : DB number (0 to 32 767).
y : Byte number (0 to 65 532).
Example : DB1.DBD4

- Double words in the DB => DBx.DBDy_n, DBx.DBDy_n_l (type: 32 bit

WORD)

n: Number of words.
l: Number of bytes per line (Matrix mode only).
Example : DB1.DBD4_10, DB1.DBD4_10_5

Profibus • 93 • - Item of image variables

 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead
- Floating words in the markers => MDxF (type: 32 bit IEEE REAL)

x: Number of the first byte (0 to 65 532).

Example : MD4F

- Floating words in the markers => MDxF_n, MDxF_n_l (type: 32 bit

IEEE REAL)

n: Number of words.
l: Number of bytes per line (Matrix mode only).
Example : MD4F_10, MD4F_10_5

- Floating words in the DB => DBx.DBDyF (type: 32 bit IEEE REAL)

x : DB number (1 to 32 767).
y: Number of the first byte in the DB (0 to 65 532).
Example : DB4.DBD8F

- Floating words in the DB => DBx.DBDyF_n, DBx.DBDyF_n_l (type: 32

bit IEEE REAL)

n: Number of words.
l: Number of bytes per line (Matrix mode only).
Example : DB4.DBD8F_10, DB4.DBD8F_10_5

- Timers => Tx (type: 16 bit WORD)

x: Number of the timer (0 to 255).

Example: T4

- Timers => Tx_n, Tx_n_l

n: Number of timers.
l: Number of timers per line (Matrix mode only).
Examples : T4_10, T4_10_5

- Counters => Zx (type: 16 bit WORD)

x: Number of the counter (0 to 255).

Example: Z4

- Counters => Zx_n, Zx_n_l

n: Number of counters.
l: Number of counters per line (Matrix mode only).
Examples : Z4_10, Z4_10_5

Profibus • 94 • - Item of image variables

 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead

7. - Appendices

- List of extra files for this protocol

APPPFBPC. Profibus channel management task
NET5480A. Profibus channel management task
NETPFBPC Profibus channel management task

BTPFB. System time base

APDIAG.EXE PROFIBUS DP diagnostic utility

APPFBOLE.DLL DLL used by APDIAG.EXE

Files in the directory install\simatic\simatic.s5 of the CD-ROM:

L2BI55ST.S5D MS-DOS program for Siemens 155U PLC

L2RW15ST.S5D MS-DOS program for Siemens 115U PLC
L2RW35ST.S5D MS-DOS program for Siemens 135U PLC
L2RW95ST.S5D MS-DOS program for Siemens 95U PLC
L2RW945ST.S5D MS-DOS program for Siemens 945 PLC
PCOPY.EXE Translator PCPM MS-DOS
PCOPY.WRI PCOPY help
READ.ME PLC parametering description

File s5s7.exe in the directory install\simatic\simatic.s7 of the CD-ROM.

- Evolution / compatibility
EPROM of the applicom® interfaces.
The protocol necessitates a version EPROM minimum V3.2 with an applicom® product>=2.6.

• Since V2.7 of the applicom® product, L2 DP is no longer supported.

• PC1500S7 with S7 and MPI protocols: from 3.6 version.
• PCI2000PFB, improved indicator lights management: from 3.7 version.

Profibus DP
• From version applicom® V2.8.1, the software supports 16 bit data words.
• From version applicom® V3.0.0, the software supports access to 32 bits data words and
IEEE floating.
• From version applicom® V3.1.0, the software:
◊ manages access to equipment shared by other DP masters,
◊ manages multimaster operation,
◊ includes a tool to diagnose and read the DP slave input/output configuration.

Profibus S7 and MPI

• From version applicom® V3.2.0, The software supports the write of several bits in a field
(12 maximum).

Profibus • 95 • - Appendices
 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead
- List of the applicom® materials supporting the PROFIBUS protocol

Protocols supported:

S5 S7 MPI DP DP-Slave FDL

PCI2000PFB (Channel 0) X X X X

PC1500PFB X X X X X
PC1500S7 X X
PC104PFB X X X X
PCI4000 X X X X X
PC4000 X X X X X
CPCI1000PFB X X X X

baud rates supported:

9.6 Kb 19.2 Kb 93.75 Kb 187.5 Kb 375 Kb 500 Kb 1.5 Mb 3 Mb 6 Mb 12 Mb

PCI2000PFB X X X X X X X X X

PC1500PFB X X X X X X
PC1500S7 X X X X X X
PC104PFB X X X X X X X X X
PCI4000 X X X X X X
PC4000 X X X X X X
CPCI1000PFB X X X X X X X X X

Restrictions :

PC4000 / PCI4000 :
1 port at 500 KBauds (port 0 or 1), the others at 9600 Bds with MODBUS and BR4000
(DP protocol excepted : 187.5 KBauds).
4 ports at 93.5 KBauds BR4000 or BX4010.
For higher speed or other protocols, consult us.
Warning: PCI2000PFB, PC1500PFB, PCI1500PFB, PC1500S7, PCI1500S7, PC104PFB and
boards have a female SUB D9 points connector. For the others boards, a 5PFB485 module or 6PFB485
module (module with galvanic insulation) will be necessary and a male-female adapter will be supply.

Profibus • 96 • - Appendices
 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead

Access to the Profibus DP services

- Description

The function allowing use of the Profibus DP services can be accessed via the DLL functions
library: "applicom.DLL".

- Using the AuWriteReadMsg function.

The "AuWriteReadMsg" function lets you use the specific Profibus DP services:
- Read the configuration in the equipment (Get Config = SAP_59).
- Read the inputs in the equipment (Read Input = SAP_56).
- Read the outputs in the equipment (Read_Output = SAP_57).
- Read the diagnostic in the equipment (Slave Diag = SAP_60).
This function requires the following 8 parameters:
- wChan : 16 bit word indicating the applicom® target channel, it is determined using the
CARD2CHAN macro which transforms the card number into a channel number (channel = (card-1)*4).
- wEquip : 16 bit word indicating the applicom® target equipment number.
- dwMsgParam : 32 bit word indicating the service.

Service Function
56 Read Input
57 Read_Output
59 Get Config
60 Slave Diag

- wNbTx : number of bytes to send in the lpbyBufTx buffer.

- lpbyBufTx : near pointer on the transmission buffer. Up to 244 data bytes can be placed in the
transmission message.
- pwNbRx : near pointer on the number of bytes received. The return value indicates the number of
bytes received, if the variable pointed by pdwStatus is equal to zero.
- lpbyBufRx : near pointer on the reception buffer. Up to 244 data bytes can be received in the
buffer.
- pdwStatus : near pointer on an applicom® error status1 32 bit word.

- Changing station address

The "AuWriteReadMsg" function is used to change the address of a Profibus DP

station (Set Slave Address = SAP_55) only on non configured stations.

This function requires the following 8 parameters:

- wChan : 16 bit word indicating the applicom® target channel, it is determined using the
CARD2CHAN macro which transforms the card number into a channel number (channel = (card-1)*4).
- wEquip : 16 bit word indicating the target Profibus DP station physical address.
- dwMsgParam : 32 bit word initialized at hexadecimal value 0x00010037 .
- wNbTx : number of bytes to send in buffer lpbyBufTx.
- lpbyBufTx : near pointer on the transmission buffer. Up to 244 data bytes can be placed in the
transmission message.
- pwNbRx : near pointer on the number of bytes received. The return value indicates the number of
bytes received, if the variable pointed by pdwStatus is equal to zero.

Profibus • 97 • - Appendices
 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead
- lpbyBufRx : near pointer on the reception buffer. Up to 244 data bytes can be received in the
buffer.
- pdwStatus : near pointer on an applicom® error status1 32 bit word.

Profibus • 98 • - Appendices
 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead
- Example in ANSI C language

The following example is used to read the Profibus Dp diagnostic on applicom equipment number 5 from
applicom interface card number 1.

#include "applicom.h" /* Declarations file*/

unsigned short wChan; /* Channel number */

unsigned short wEquip; /* applicom equipment number */
unsigned long dwMsgParam; /* Mode + service */
unsigned short wNbTx; /* Number of bytes to send*/
unsigned short wNbRx; /* Number of bytes received
unsigned char byTxBuf[244]; /* Transmission buffer */
unsigned char byRxBuf[244]; /* Reception buffer */
unsigned long dwStatus; /* applicom return code */

wChan = CARD2CHAN(1); /* determination of the card 1 channel */

wEquip = 5; /* pointing to applicom equipment 5 */
wNbTx = 0; /* no data to send */
dwMsgParam = 60 /* service SAP_60 */
wNbRx = size of(byRxBuf); /* maximum return size init */

/* Transmission of the Profibus DP service */

AuWriteReadMsg(wChan, /* Channel number */

wEquip, /* applicom number */
dwMsgParam, /* Mode + service*/
wNbTx, /* Number of bytes to send */
byTxBuf, /* Data to send buffer */
&wNbRx, /* address of number of bytes received */
byRxBuf, /* Received data buffer */
&dwStatus); /* return code address */

if (dwStatus == 0) /* read function return code */

{ /* if no error */
/* Analysis of the reception buffer */
}
else
{/* Analysis of the error code returned by the function */
}

A complete example is available in the "DLL\MSVC\Sample LibApplicom\ProfibusDP" folder from the

folder in which applicom® has been installed.
It includes a source file in ANSI C: ProfibusDPAuWriteReadMsg.c, and an executable file:
ProfibusDPAuWriteReadMsg.exe.
To be integrated in a working project or compiled on-line, this file requires access to the following files:
applicom.h and applicom.lib.

Note: During the inclusion of file "applicom.h" in a project in C++, you must include the file in extern "C"
as follows:

extern "C"
{
#include "applicom.h"
}

Profibus • 99 • - Appendices
 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead
The applicom functions can only be used after initialization of the DLL
"applicom.dll". Therefore, the "initbus" function must be executed before
using the applicom functions and the "exitbus" function executed before
closing the application.

Profibus • 100 • - Appendices

 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead

8. - Return status of applicom® functions

- Introduction
The various applicom® functions return a status word that:
- Guarantees the request quality.
- Can be used to diagnose the cause of a failure.
The significance of the status word value is given in the following tables. As well as the general
significance, « Further details » allow you to guide your diagnostic according to the protocol used.

- applicom® general statuses

-6 The TRANSCYC (or TRANSCYCPACK) function is used with a cyclic function number that is no longer
activated.
-5 The user program tries to perform a TRANSDIF (or TRANSDIFPACK) deferred transfer although the deferred
request in progress is not completed.
-1 TRANSDIF (or TRANSDIFPACK) deferred transfer request related to a write that took place correctly.
0 No anomaly detected. The function took place correctly.
1 Unknown function.
The requested function is not supported.
2 Incorrect address.
The address of the variable you are soliciting is incorrect.
3 Incorrect data.
Further details :
Function: BINBCD, BCDBIN.
- At least one of the accessed values is not in BCD format (0 ≤ value ≤ 9999).
4 Irretrievable data.
32 Bad parameter passed into the function.
Incorrect number of variables.
35 Data not available in cyclic read.
Attempt to transfer data with TRANSCYC (or TRANSCYCPACK) before it has been read in the equipment.
40 Deferred read or write attempt when the deferred request register is full.
Another task must free the resources by making an exitbus.
41 Deferred read or write attempt when the deferred request register is full
Perform deferred request transfers with TRANSDIF (or TRANSDIFPACK) in order to release the register (64
positions).
42 Deferred request transfer attempt with TRANSDIF (or TRANSDIFPACK) when the latter is empty (no deferred
requests in progress).
45 Non-resident communication software.
Initialize the applicom® interface before using it by typing command applicom (or PCINIT under Windows ).
46 Board number not configured, or Master/client applicom® function aiming at a channel configured as
slave/server, or vice versa.
47 No applicom® interface.
51 Driver system problem.
59 Protection key missing on the applicom® interface..
Using applicom® function without INITBUS function.
66 Insufficient applicom® interface memory.

Profibus • 101 • - Return status of applicom® functions

 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead
255 Used by the « PCDDE » MS-Windows server. Initial value of « STATUS_READ » and « STATUS_WRITE ».
This value indicates that no transaction has been made between « PCDDE » and applicom® interface.

Comments :
Negative status codes are information codes.

Profibus • 102 • - Return status of applicom® functions

 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead
- Statuses according to the protocol
0 No anomaly detected. The function took place correctly.
1 Unknown function.
The requested function is not supported.
2 Incorrect address.
The address of the variable you are soliciting is incorrect.
Further details :
Profibus S5 Protocol:
- Returned by the destination coupler equipment. Undeclared DB.
3 Incorrect data.
Further details :
Profibus Protocol:
- Inconsistent frame content.
Profibus DP protocol :
- Wrong initialization of the parameters related to the configuration of the equipment.
- Start the configuration again and import the GSD file.
Profibus S5 Protocol:
- Inconsistent frame content.
- Domain too short (example: DB badly dimensioned).
Function: BINBCD, BCDBIN, READWORDBCD, WRITEWORDBCD.
- At least one of the accessed values is not in BCD format (0 ≤ value ≤ 9999).
4 Irretrievable data.
Further details :
Profibus S5 Protocol:
- Non-existent peripheral (for example: input or output card not present in the PLC).
6 Layer 2 negative acknowledgement from the equipment (NACK).
Further details :
Profibus DP protocol:
- NO (Not Ok) , remote equipment is missing or defective.
10 Layer 2 negative acknowledgement from the equipment (NACK).
Further details :
Protocol Profibus:
- UE (User Error), Error in remote equipment.
11 Layer 2 negative acknowledgement from the equipment (NACK).
Profibus Protocol:
- RR (Remote Resource), Not enough resources in remote equipment.
Or invalid initialization parameters.
12 Layer 2 negative acknowledgement from the equipment (NACK).
Further details :
Profibus Protocol:
- RS (Remote Service), The layer 2 service used is not authorized on the SAP or the SAP is not activated.
13 Layer 2 negative acknowledgement from the equipment (NACK).
Further details :
Profibus Protocol:
- RDL (Response FDL/FMA1/2 Data Low), Not enough resources in remote equipment to reply in low priority.
14 Layer 2 negative acknowledgement from the equipment (NACK).
Further details :
Profibus Protocol:
- RDH (Response FDL/FMA1/2 Data High), Not enough resources in remote equipment to reply in
high priority.
Or invalid initialization parameters.
15 Profibus Protocol:
- LS (Local Service), local SAP not activated.
16 Profibus Protocol:
- NO (Not OK), Significance dependent on layer 2 service.

Profibus • 103 • - Return status of applicom® functions

 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead
21 Profibus Protocol:
- IV (InValid parameter in request),
Further details :
TS applicom® = adr equipment.
TS or adr equipment > to HSA
32 Bad parameter passed into the function.
Incorrect number of variables.
33 Response time fault (Time-Out).
Further details :
Profibus S5 Protocol:
- The remote equipment is not in the logic ring.
34 Parity fault in reception or of control word (CRC16, BCC).
Check the configuration of the channel and target equipment.
Check the wiring (RC at end of line for the RS485).
36 Equipment not configured.
Define the equipment configuration with the console and start again the applicom® product.
Protocol PROFIBUS DP :
- Status fed back in case of write access on shared equipment.
54 Profibus Protocol:
- The address of the PROFIBUS applicom® channel is not in the logical ring.
55 Time-Out elapsed, Message Lost
Further details :
Profibus S5 Protocol:
- Wait time longer than configured "response Time-out ". The question was acknowledged beforehand. CPU in
stop, the CPU does not run the communication FB (FB100). In the case of 95U you are trying to access non-
existent data (for example: DB not configured, ...).
65 Refused connection.
Further details :
Bad wire.
Bad configurations of the remote stations.
67 Bad frame received
68 Access to non-existent object
Further details :
Profibus Protocol:
- Error class - clause 3.16.1.4.4, Error class ACCESS: OBJECT_NON_EXISTENT
69 Access to object of incompatible type
Further details :
Protocol Profibus:
- Error class - clause 3.16.1.4.4, Error class ACCESS: TYPE_CONFLICT
70 Communication terminated by remote user
Further details :
Profibus Protocol:
- Abort - clause 3.4.4.2, USER identifier.
71 Communication terminated
Further details
Profibus Protocol:
- Abort - clause 3.4.4.2
72 Communication terminated.
Further details :
Profibus Protocol:
- Abort - clause 3.4.4.2, LLI identifier except status 80, 81 and 82.
73 Layer 2 communication terminated.
Further details :
Profibus Protocol:
- Abort - clause 3.4.4.2, LAYER 2 identifier. The remote equipment closed the communication after layer 2 error.
74 Communication refused.
Further details :
Profibus Protocol:
- Initiate-error PDU - clause 3.16.4.2 error code MAX-PDU-SIZE-INSUFFICIENT. The maximum frame length
that the remote equipment can receive is less than the maximum length configured. See the field « maximum
PDU sent for low (or high) priority » of configurator.

Profibus • 104 • - Return status of applicom® functions

 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead
75 Communication refused.
Further details :
Profibus Protocol:
- Initiate-error PDU - clause 3.16.4.2, error code FEATURE-NOT-SUPPORTED. Feature not
supported by the equipment.
76 Communication refused.
Further details :
Profibus Protocol:
- Initiate-error PDU - clause 3.16.4.2, error code VERSION-OD-INCOMPATIBLE. Incompatible object dictionary
version.
77 Communication refused.
Further details :
Profibus Protocol:
- Initiate-error PDU - clause 3.16.4.2, error code USER-INITIATE-DENIED. Communication denied by the user
of the remote equipment.
78 Communication refused.
Further details :
Profibus Protocol:
- Initiate-error PDU - clause 3.16.4.2, error code PASSWORD-ERROR. Wrong password.
79 Communication refused.
Further details :
Profibus Protocol:
- Initiate-error PDU - clause 3.16.4.2, error code PROFILE-NUMBER-INCOMPATIBLE. Profile number
incompatible.
80 Communication refused.
Further details :
Profibus Protocol:
- Abort - clause 4.7.7.3. LLI identifier reason code ABT_RC1: LLI-LLI context check negative.
Check parameters « Communication type (MMAC or MSAC), max. SCC, max. RCC, max. SAC,
max. RAC, Time-out ACI »
81 Communication terminated.
Further details :
Profibus Protocol:
- Abort - clause 4.7.7.3. LLI identifier reason code ABT_RC2: Unallowed LLI PDU received in
the connection establishment phase or release phase. Frame received although communication not
established.
82 Communication terminated.
Further details :
Profibus Protocol:
- Abort - clause 4.7.7.3. LLI identifier reason code ABT_RC3: Unallowed LLI PDU received in
the data transfer phase. Equipment trying to connect when communication has already been made.
83 Profibus Protocol:
- Error class - clause 3.16.1.4.4. Error class VFD-STATE.
84 Profibus Protocol:
- Error class - clause 3.16.1.4.4. Error class APPLICATION-REFERENCE.
85 Profibus Protocol:
- Error class - clause 3.16.1.4.4. Error class DEFINITION.
86 Profibus Protocol:
- Error class - clause 3.16.1.4.4. Error class RESOURCE.
87 Profibus Protocol:
- Error class - clause 3.16.1.4.4. Error class SERVICE.
88 Profibus Protocol:
- Error class - 3.16.1.4.4. Error class ACCESS except status 68 and 69.
- When the double word indicator (ANZW defined in the coupler) is a zone not defined in the PLC.
Example: ANZW in DB10 DW20 and DW20 (and/or DW21) do not exists.
- Write attempt on a object in "read only".
89 Profibus Protocol:
- Error class - clause 3.16.1.4.4. Error class OD.
90 Profibus Protocol:
- Error class - clause 3.16.1.4.4. Error class OTHER.

Profibus • 105 • - Return status of applicom® functions

 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead
91 Frame refused by remote equipment .
Further details :
Profibus Protocol:
- Error class - clause 3.16.1.4.4. Error class REJECT_PDU.

Comments :
Negative status codes are information codes.

Profibus • 106 • - Return status of applicom® functions

 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead

9. - Glossary of terms

applicom® interface
Communication card, ISA or PCI type, with the applicom® real time multi-task kernel.

ASCII
American Standard Code for Information Interchange

Bauds
Bits per second

BX4010
4 channels distribution box, with galvanic insulation.

Channel
Physical output of an applicom® card.

Client
Node which has communication initiative.

Coupler
Communication interface

CP
Communication processor

CSRD
Cyclic Send and Request Data.

Data Bloc (DB)

Internal memory.

DATA-BASE
applicom® database, with 32 kbits and 32 kwords.

DP
Decentralized periphery.

DX
Extended data bloc

EN 50170
European Norm describing fieldbus : PROFIBUS, WORLDFIP and P-NET.

EPROM
Read only memory on applicom® interfaces which contains programs.

Profibus • 107 • - Glossary of terms

 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead
FB
Function Bloc

FDL
Fieldbus Data Link

FMA
Fieldbus Management.

FMS
Fieldbus Messaging Specification

GSD file
File including DP equipment parameters supplied by the manufacturer.

HSA
Highest Station Address

Item
Defines an element

L2
Profibus layer 1 and 2 of the OSI model in SIEMENS terminology

Master
On a master-slaves network, characterises the device which initiates the exchanges.

Memo
Siemens word to describe internal memory of a PLC

MMAC
Master - Master Acyclic

MPI
Multipoint Interface

MSAC
Master - Slave Acyclic

OPC
Ole for Process Control.

OSI
Open Systems Interconnect

PCDDE
applicom® DDE server.

SAP
Service Access Point

Profibus • 108 • - Glossary of terms

 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead
Slave
On a Master-slaves bus, characterises devices which have none initiative on the bus. They answer
only to the master requests.

SDA
Send Data with Acknowledge

SDN
Send Data with No Acknowledge

SRD
Send and Request Data with Acknowledge

STEP7
Programming software of SIEMENS PLC serie 7

Profibus • 109 • - Glossary of terms

 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead

10. - Index

115U, 45
135U, 45
155U, 45
95U, 45
active stations, 2
addressaging, 4
Addressing
input/output words, 15, 16
Addressing (MPI), 20
Adressing
input/output bytes, 14
AGAG link, 52
ANR, 45
ANZW, 45
Cards supporting PROFIBUS, 96
Channel configuration, 25
characteristics of the MPI bus, 18
Communication block, 45
Configuration
baud rate, 25
GAP, 25
HSA, 25
Max_TSDR, 25
Min_TSDR, 25
retry counter, 25
SAP, 25
TS, 25
TSET, 25
TSL, 25
TTR, 25
Configuration DP
Bus Time-out, 32
GSD, 32
Ident Number, 32
PROFIBUS address, 32
Synchronous compatible, 32
User_param_data, 32
Configuration MPI
Data alignment, 37
local SAP, 37
PROFIBUS address, 37
Configuration PROFIBUS FDL
priorité, 42
SAP distant, 42
SAP local, 42
Configuration PROFIBUS FDL adresse PROFIBUS, 42
Configuration S5
Local SAP, 30
priority, 30
PROFIBUS address, 30
Remote SAP, 30
Configuration S7

Profibus • 110 • - Index

 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead
CPU slot, 39
Data alignment, 39
Local SAP, 39
PROFIBUS address, 39
CP 5430, 48
CP 5430 TF, 49
CP 5430TF, 45
CP 5431 FMS, 50
CP5431 FMS, 45
DB1, 52
DP communication principle, 12
DP equipment, 9
Equipments configuration, 29
Error, 101
FB100, 45
Functions (DP messaging), 11
functions usable
cyclic mode, 58
deferred mode, 57
wait mode, 56
Funtionality, 18
GAP, 2
GSD file, 9
input/output bytes
Adressing, 14
Input/output words
Addressing, 15, 16
Item
Siemens PLC descriptor - German (D) and French syntax, 69
Siemens S5 PLC descriptor - English syntax, 79
Siemens series 7 PLCs descriptor for MPI and S7, 89
standard Descriptor, 60, 65
Item descriptor
Siemens PLC descriptor - German (D) and French syntax, 69
Siemens S5 PLC descriptor - English syntax, 79
Siemens series 7 PLCs descriptor for MPI and S7, 89
standard descriptor, 60, 65
Limits with MPI
Library, 21
Library, 21
PCDDE, 21
PCDDE, 21
Limits with S5 messaging
library, 6
OPC, 7
PCDDE, 6
Maximum number of variables per frame with S5 messaging
library, 6
OPC, 7
PCDDE, 6
Messaging on PROFIBUS, 1
Messaging types (configuration), 29
MPI, 18
Network management, 2
OSI model, 1
passive station, 2
REPROM, 95
S5 messaging, 8
S5-95U, 52
S7 protocol, 53

Profibus • 111 • - Index

 electrical & safety · industrial connectivty · software & electronics · advanced connectivity

Woodhead
SAP, 2
SDA, 50
services, 2
Services, 1
Services (DP messaging), 11
SINEC l2, 45
SSNR, 45
Status, 101
Step S7, 53
Supported CPU, 45
SYNCHRON, 45
token, 2
ttr, 2
validated CPU, 8
Variable type, 4
Variables access (MPI), 20
Variables alignment, 18
Word access with DP, 14

Profibus • 112 • - Index