EUCHNER AS-i 3.0 PROFIBUS Gateway with integrated Safety Monitor for 2 AS-i circuits - Manual (Page 162)

162 Subject to reasonable modifications due to technical advances Id.-No.: 103329 Issue date - 24.10.2008 EUCHNER GmbH + Co. KG
Kohlhammerstraße 16 • D-70771 Leinfelden-Echterdingen Tel. +49/711/75 97-0 • Fax. +49/711/753316
AS-i 3.0 PROFIBUS Gateway with integrated Safety Monitor
Appendix: Example for startup on a Siemens S7
17.2.4.3 Hex parameterizing
DPV1_Status
Hexadecimal representation of the data resulting from the settings for parameter
bytes 0 to 2.
User_Prm_Data
Hexadecimal representation of the data resulting from the settings for parameter
bytes 3 to 37.
17.2.5 SIMATIC Step7 blocks
After the hardware has been configured, these can be sent to the CPU. Since
data transmission of the AS-i data is done in this example directly to the process
image, no additional Step7 program is needed for data refreshing. Therefore
there is no program code in OB1.
OB1: Cyclical program block. Access to the AS-i data is via the parameterized
address space in the in-/outputs process image.
OB82: PROFIBUS diagnostic alarm. This OB is invoked as soon as a PROFI-
BUS slave has set the ExtDiag flag in the telegram reply. This ExtDiag flag allows
a PROFIBUS slave to report an error condition to a PROFIBUS master. If OB82 is
not present, the CPU is stopped when a PROFIBUS slave sets the ExtDiag flag.
OB86: PROFIBUS peripheral error. This OB is invoked when the PROFIBUS
master detects a PROFIBUS slave failure.
OB100: Startup OB. This OB is run once when the CPU starts up.