PROFIBUS-DP interface
3–14
1070 066 091-102 (01.08) GB
3.3.2
Structure of the configuration data
The configuration data determine the structure and allocation of the cyclic
telegrams. All telegrams used later on are initialized accordingly by ”identifi-
cation bytes” sent by the master during the configuration phase to the DP
slave.
Servodyn-D drives with a PROFIBUS-DP interface always expect to receive
the identification bytes in the following order:
D
Identification byte for the cyclic actual value telegrams
and then
D
Identification byte for the cyclic setpoint telegrams.
.
The configuration data and parameterization data must match each
other!
The selection of the desired drive mode (for parameterization data, re-
fer to page 3–13; defined in the GSD file) always requires the definition
of a suitable telegram configuration (by the configuration data).
The structure of the telegrams required for the individual drive modes
is described in section 3.4 on page 3–16 ff.
MSB
Bit no.
LSB
Description
7
6
5
4
3
2
1
0
Description
Length of data.
0000: 1 byte or word
0001: 2 bytes or words
:
1111:
16 bytes or words
Input-output.
00: special identification formats
01: Input (telegram from slave to master)
10: Output (telegram from master to slave)
11: Input-output
Format length.
0:
Byte (byte structure)
1:
Word (word structure)
When transmitting words, first the high byte and then the low byte is transmitted with
PROFIBUS-DP. If ”Word (word structure)” has been specified as format length, the mas-
ter may exchange the bytes within the word if required by the target system.
Consistency through
0:
Byte or word length
1:
Total length
Example:
Identification byte = 60
H
= 0110 0000
B
MSB
Bit no.
LSB
Description
7
6
5
4
3
2
1
0
Description
0
1
1
0
0
0
0
0
60
H
Length of data.
0:
1 word (bit 6=1)
Input-output.
2:
Output (telegram from master to slave)
Format length.
1:
Word (word structure)
Consistency through
0:
Word length
LSA Control S.L. www.lsa-control.com [email protected] (+34) 960 62 43 01
