Dp State Of The Slaves; Profibus Mc - Beckhoff FC3102 Documentation

3.4.5

DP State of the Slaves

Valu Description
e
0 No Error - station is exchanging data
1 Station deactivated - slave has been deactivated, temporary state during StartUp
2 Station not exists - slave does not reply on the bus -> check whether slave is switched on, whether
PROFIBUS plug is in, correct station address or bus cables
3 Master lock - slave is exchanging data with another master -> remove other master from bus or
release slave again by other master
4 Invalid slave response - incorrect answer from slave, occurs temporarily if slave has ceased data
exchange as a result of a local event
5 Parameter fault - check whether Bus Coupler / GSD file is correct, that station address is correct or
that UserPrmData settings are correct
6 Not supported - DP function is not supported -> check whether GSD file is correct or whether station
address is correct
7 Config fault – configuration fault -> check whether the added terminals / modules are correct
8 Station not ready -> station starting up, temporarily displayed during StartUp
9 Static diagnosis - slave signaling static diagnosis and cannot deliver valid data at present -> check
operating state at the slave
10 Diagnosis overflow - slave signaling a diagnosis overflow -> check diagnostic data (using ADS-Read,
see below) and operating state at the slave
11 Physical fault - physical fault interfering with slave response -> check cables
13 Severe bus fault -> check cabling
14 Telegram fault - slave responding with an invalid telegram -> must not occur
15 Station has no resources -> slave has insufficient resources for the telegram -> check that GSD file is
correct
16 Service not activated -> temporary fault when slave ceases data exchange due to a local event,
otherwise check whether DP functions are disabled at the slave
17 Unexpected telegram -> can occur temporarily if two PROFIBUS networks are connected together or
check whether bus times for the second master are set identically.
18 Station ready -> can occur temporarily during StartUp and until the task is started
19 DPV1 StartUp -> occurs temporarily after the DP has started up if there is still data to be sent by
DPV1 Write
128 FC310x in slave mode, waiting for data transfer -> slave was parameterized and configured but has
not yet received a Data_Exchange telegram
129 FC310x in slave mode, waiting for configuration -> slave was parameterized, but has not yet received
a Chk_Cfg telegram
130 FC310x in slave mode, waiting for parameters -> slave was not yet parameterized, waiting for
Set_Prm (Lock) telegram
3.5

PROFIBUS MC

The difference between PROFIBUS MC and PROFIBUS DP is that the PROFIBUS cycle is constant, with a
jitter of a few microseconds (for PROFIBUS DP, the jitter is greater than 100 µs), and at the start of the cycle
a broadcast global control telegram is sent, which can be used by the MC slaves for synchronization. This
enables precise synchronization of drive control loops with the NC.
However, this precise synchronization means that bus disturbances, switching off of slaves, pulling of bus
plugs etc. will usually lead to a loss of synchronicity between master and slave, since the bus timing is
changed.
FC310x with Simodrive 611U has Plug&Play functionality
The following steps are required for operating a Simodrive 611U on a FC310x:
FC3101 and FC3102 Version: 3.0
FC310x as master
25