Connecting Sensors/Actuators
7.2 Connecting I/O via PROFIsafe
PROFIsafe clock cycle overruns
Even if the parameterized software operates error–free in normal operation, run
time fluctuations in the PLC operating system (e.g. processing diagnostic alarms)
can mean that the processing of the OB40 interrupt was not able to be completed
before the start of the next PROFIsafe clock cycle.
In this particular case, the NCK attempts, up to a limit of 50 ms after the last cor-
rectly processed PROFIsafe clock cycle, to initiate an OB40 interrupt. The re-
peated attempts to initiate the OB40 interrupt are no longer executed in the PRO-
FIsafe clock cycle but in the IPO clock cycle.
After this 50 ms limit value is exceeded,
S Alarm: 27253 "PROFIsafe communications error F master components %1,
error %2"
is displayed and the configured Stop response (Stop D or E) is output to the safety
axes.
Further, an attempt is still made to initiate the OB40 interrupt and to maintain PRO-
FIsafe communications.
The time up to initiating the next OB40 interrupt is displayed in the following NCK
machine data:
S MD 10099: $MN_INFO_PROFISAFE_CYCLE_TIME
(PROFIsafe, communications clock cycle)
If the PROFIsafe clock cycle is continuously exceeded and just not sporadically,
then the following alarm is displayed:
S Alarm: 27256 "PROFIsafe actual cycle time %1 [ms] > parameterized cycle
time"
7.2.6
Parameterizing the SPL–SGE interface
A bitwise assignment can be made using machine data to better link the SPL inter-
faces to the net (useful) data of the F modules.
Note
The examples, now listed, to parameterize the SPL–SGE interface are based on
the following specifications:
F–DI module
– F address: 114 = 90H
– F net data length: 8 bytes
Machine data
– MD10386 $MN_PROFISAFE_IN_ADDRESS[5]
– MD13300 $MN_PROFISAFE_IN_FILTER[5]
– MD10388 $MN_PROFISAFE_IN_ASSIGN[5]
7-210
SINUMERIK 840D sl/SINAMICS S120 SINUMERIK Safety Integrated (FBSI sl) – 05.2008 Edition
= 05 00 0090
= 000F 000F
= 008 001
© Siemens AG 2008 All Rights Reserved
05.08