Communication PROFIBUS DP/PROFINET IO 10.2 Communication via PROFIBUS DP

Commissioning in STARTER

Slave-to-slave communication is configured in HW Config and is simply an extension of an existing telegram. Telegrams can be extended in STARTER (e.g. p0922 = 999).

Figure 10-40 Configuring the slave-to-slave communication links in STARTER

In order to terminate the configuration of slave-to-slave communication for the DOs, the telegram data of the DOs in STARTER must be matched to those in the HW Config and must be extended. The configuration is made centrally via the configuration of the respective CU.

Procedure

1.In the overview for the PROFIBUS telegram, you can access the telegrams of the drive objects, here SERVO_02. Select the telegram type "Free telegram configuration" for the configuration.

2.Enter the telegram lengths for the input data and output data according to the settings in HW Config. For slave-to-slave communication links, the input data comprise the standard telegram and the slave-to-slave communication data.

3.Then set the telegram in the telegram selection to the standard telegram for drive objects (in the example: standard telegram 2), which results in a split display of the telegram types (standard telegram + telegram extension). The telegram extension represents the telegram portion of slave-to-slave communication.

Drive Functions

431

Function Manual, (FH1), 07/2007 Edition, 6SL3097-2AB00-0BP4

Page 431
Image 431
Efficient Networks S120 manual Commissioning in Starter, Procedure