Siemens SIMATIC S7-1200 Інструкція з програмування безпеки - Сторінка 14

Переглянути онлайн або завантажити pdf Інструкція з програмування безпеки для Перемикач Siemens SIMATIC S7-1200. Siemens SIMATIC S7-1200 48 сторінок. Controlling several fans (ebm-papst) via modbus rtu
Також для Siemens SIMATIC S7-1200: Посібник (30 сторінок), Інструкція з експлуатації Посібник з експлуатації (36 сторінок), Посібник (40 сторінок), Посібник (17 сторінок), Посібник (31 сторінок), Посібник (49 сторінок), Посібник (20 сторінок)

Siemens SIMATIC S7-1200 Інструкція з програмування безпеки

3 Methods for Safety Programming

Methods for Safety Programming
3
3.1

Program structures

3.1.1

Defining a program structure

Recommendation
Modularly divide the program code, e.g.,
into subparts for detecting, evaluating, reacting or
plant sections.
In the preliminary stages, create a specification for each module (based on the
risk assessment requirements).
Avoid complex signal paths.
Advantages
Minimizes complexity.
Reduces programming errors.
Allows the program code to be analyzed/tested without running the program
(e.g., code review or PLCSIM).
Easily expandable. Simplifies renewed acceptance.
Reuse of program parts without renewed acceptance.
Allows advance testing and acceptance of finished program parts.
Example
The following figure shows a safety application that is divided into three machine
areas (safety zones).
As some of the sensor signals are interconnected across areas (e.g., emergency
stop functions that act globally), they are grouped into a "Sensors" FB (they could
also be split up into physical or logical areas). The respective sensors are
evaluated using standardized function blocks (e.g., "GuardDoor").
The Mobile Panels' blocks are also called here.
Separate logic and actuator FBs are created for each machine area. The actuators
are controlled using standardized function blocks (e.g., "ContactorControl").
Safety Programming Guideline
Entry ID: 109750255,
V1.0,
10/2017
14