
39
8. Profinet IO
Dual port ethernet option board installation manual
MN032004EN October 2017 www.eaton.com
8.4.3.3.2. Actual data
Vendor specific telegram 1 – actual data
Table 72. Vendor-specific telegram 1 – actual data
Vendor-specific telegram 1
Additional process data (16-bit each)
FB Fixed
SW
(16-bit)
FB Speed
Actual
(16-bit)
PDO1 PDO2 PDO3 PDO4 PDO5 PDO6 PDO7 PDO8
FB Fixed SW (16-bit) (See 8.4.3.1.7. Vendor-specific
FBFixedStatusWord) FB Speed Actual (16-bit) (See 8.4.3.1.8.
Vendor-specific FBSpeedActual) PDO1-PDO8 (See 8.4.3.1.11.
Vendor-specific Process Data)
8.4.3.4 Vendor-specific telegram 2 and its variants
These telegrams use the vendor-specific fixed and general
control word, status word, speed setpoint value and
speed actual value. It is also possible to use up to eight
vendor-specific Process Data fields. Using these telegrams,
the process data fields are communicated as 32-bit values.
Table 73. Vendor-specific telegram 2
Telegram no.
Telegram
117
Vendor-specific Telegram 2
118
Vendor-specific Telegram 2 + PD1
119
Vendor-specific Telegram 2 + PD[1..2]
120
Vendor-specific Telegram 2 + PD[1..3]
121
Vendor-specific Telegram 2 + PD[1..4]
122
Vendor-specific Telegram 2 + PD[1..5]
123
Vendor-specific Telegram 2 + PD[1..6]
124
Vendor-specific Telegram 2 + PD[1..7]
125
Vendor-specific Telegram 2 + PD[1..8]
8.4.3.4.1. Setpoint data
Vendor-specific telegram 2 – setpoint data
Table 74. Vendor-specific telegram 2 – setpoint data
Vendor-specific telegram 2
Additional process data (32-bit each)
FB Fixed
CW
(16-bit)
FB Gen
CW
(16-bit)
FB
Speed
Reference
(16-bit)
PDI1 PDI2 PDI3 PDI4 PDI5 PDI6 PDI7 PDI8
otee:
N
32 bit data not supported in current version.
See chapter 5.
FB Fixed CW (16-bit) (See 8.4.3.1.5. Vendor-specific
FBFixedControlWord)
FB Gen CW (16-bit) (See 8.4.3.1.9. Vendor-specific
FBGeneralControlWord)
FB Speed Reference (16-bit) (See 8.4.3.1.6. Vendor-specific
FBSpeedReference)
PDI1-PDI8 (See 8.4.3.1.11. Vendor-specific Process Data)
8.4.3.4.2. Actual data
Vendor-specific telegram 2 – actual data
Table 75. Vendor-specific telegram 2 – actual data
Vendor-specific telegram 2
Additional process data (32-bit each)
FB Fixed
SW
(16-bit)
FB Gen
SW
(16-bit)
FB Speed
Actual
(16-bit)
PDO1 PDO2 PDO3 PDO4 PDO5 PDO6 PDO7 PDO8
otee:
N
32 bit data not supported in current version.
See chapter 5.
FB Fixed SW (16-bit) (See 8.4.3.1.7. Vendor-specific
FBFixedStatusWord)
FB Gen SW (16-bit) (See 8.4.3.1.10. Vendor-specific
FBGeneralStatusWord)
FB Speed Actual (16-bit) (See 8.4.3.1.8. Vendor-specific
FBSpeedActual)
PDO1-PDO8 (See 8.4.3.1.11. Vendor-specific Process Data)
8.4.3.5 Vendor-specific telegram 3 and its variants
These telegrams use a mix of PROFIDrive and
vendor-specific data. It is possible to use also up to eight
vendor-specific Process Data fields. Using these telegrams,
the process data fields are communicated as 32-bit values.
Table 76. Vendor-specific telegram 3
Telegram no.
Telegram
126
Vendor-specific telegram 3
127
Vendor-specific telegram 3 + PD1
128
Vendor-specific telegram 3 + PD[1..2]
129
Vendor-specific telegram 3 + PD[1..3]
130
Vendor-specific telegram 3 + PD[1..4]
131
Vendor-specific telegram 3 + PD[1..5]
132
Vendor-specific telegram 3 + PD[1..6]
133
Vendor-specific telegram 3 + PD[1..7]
134
Vendor-specific telegram 3 + PD[1..8]
8.4.3.5.1. Setpoint data
Vendor-specific telegram 3 – setpoint data
Table 77. Vendor-specific telegram 3 – setpoint data
Vendor-specific telegram 3 Additional process data (32-bit each)
STW1
(16-bit)
FB Gen
CW
(16-bit)
NSOLL
_A
(16-bit)
PDI1 PDI2 PDI3 PDI4 PDI5 PDI6 PDI7 PDI8
otee:
N
32 bit data not supported in current version.
See chapter 5.
STW1 (16-bit) (See 8.4.3.1.1. STW1 – Control Word 1 31)
FB Gen CW (16-bit) (See 8.4.3.1.9. Vendor-specific
FBGeneralControlWord)
NSOLL_A (16-bit) (See 8.4.3.1.3. PROFIDrive speed setpoint