TIA Portal V11 SP2. SIMATIC Safety V11. For internal use only / Siemens AG All Rights Reserved.

Transcription

1 TIA Portal V11 SP2 SIMATIC Safety V11

2 Seamless Integration of Safety in the STEP 7-Engineering System Do I need an additional engineering system for Safety? Safety-related engineering is completely integrated into the standard automation system. One engineering for standard- and safety-related programs Intuitive operation and the same workflow for developing like for standard programs All feature from STEP 7 V11 are also available for the option package STEP 7 Safety V11 with the programming languages FBD and LAD New: Support of DINT-Data types (32 Bit) Integrated, certified library for most safety functions Controller ET 200 F-CPU ET 200S & ET 200pro CPU 315F/317F/319F CPU 414F/416F EC31-RTX F IPC 427/477C-RTX F WinAC RTX F Engineering STEP 7 Safety V11 PROFINET & PROFIsafe Peripherie ET 200M ET 200S PROFIBUS & PROFIsafe ET 200pro ET 200isp ET 200eco Page 3

3 Seamless Integration of Safety in the STEP 7-Engineering System Is Safety always complicated? Configuration Common look-and-feel for all failsafe modules Storage of modules with customer specific parameters in a library Own signature for parameters of a module ready-to-start: F-runtime group will be generated automatically for each safety PLC No F-Call necessary Connecting tags from program editor to modules via Drag & Drop Safety printout Page 4

4 Seamless Integration of Safety in the STEP 7-Engineering System How do I recognize Safety-related resources in my Program? Safety-relevant resources are colored yellow in the Network view Device view Project tree Hardware catalog Safety program Clear separation of user- and system-specific blocks All blocks automatically generated by the system are saved in a system blocks folder Page 5

5 Seamless Integration of Safety in the STEP 7-Engineering System How do I recognize safety-related resources in my program? Network view Devices/Slaves with fail-safe modules are marked with a small E-STOP symbol Tag table and watch table Safety variables are shown in yellow in the tag- and watch table Page 6

6 Seamless Integration of Safety in the STEP 7-Engineering System Safety library What other innovative features are included? Module descriptions are displayed in the Safety Library upon Mouse over New: independent numbering for all safety blocks from library Data access New: DIAG-outputs could be connected directly to standard operands New: Standard access to F-Data is marked on the fly as error New: Access to standard data blocks from within F-Program Page 7

7 Seamless Integration of Safety in the STEP 7-Engineering System What other innovative features are included? Handling Undo Module-parking feature Storing of inconsistent blocks Same operational concept as Standard, i.e. identical compile and identical download Unconnected slaves and devices won t be deleted Page 8

8 Safety Administration Editor F-PLC F-periphery Safety Administration Editor Migration Access protection Libraries Safety printout Where could I find the Safety Administration Editor? For all F-PLC with safety mode activated 1. Open the project navigation of the F-CPU. 2. You could open the Editor via double click on "Safety Administration or choose in the context menu the Safety Administration Editor after right click. Page 16

9 Safety Administration Editor F-PLC F-periphery Safety Administration Editor Migration Access protection Libraries Safety printout What is the Safety Administration Editor? The Safety Administration Editor is responsible for following operations Displaying the current status and signature of your safety program Displaying the status of the safety mode Creating/Organizing the F-runtime groups Display information for each safety block Creating/Changing access protection Common settings for the safety program could be defined herein Page 17

10 Migration from S7 Distributed Safety to STEP 7 Safety F-PLC F-periphery Safety Administration Editor Migration Access protection Libraries Safety printout Can existing S7 Distributed Safety Projects be reused? In STEP 7 Safety V11 you can reuse existing S7 Distributed Safety V5.4 SP5 projects. Older projects must be first compiled in S7 Distributed Safety V5.4 SP5 and then migrated. Page 18

11 Migration from S7 Distributed Safety to STEP 7 Safety F-PLC F-periphery Safety Administration Editor Migration Access protection Libraries Safety printout What happens during Migration? As a result of the migration, you will have a complete STEP 7 Safety Project, including a Safety Program. The program structure of S7 Distributed Safety and the signature are intact. The migrated project can be loaded into the F-CPU directly without further translation. For a migrated project, it is not possible to produce a Safety Printout from STEP 7 Safety V11. Printouts generated by S7 Distributed Safety V5.4 SP5 and associated documents are still valid. OB35 F-Call F-FB If the migrated project is translated by STEP7 Safety, a new program structure and common signature will be applied. OB35 Main- Safety Page 19

12 Libraries F-PLC F-periphery Safety Administration Editor Migration Access protection Libraries Safety printout How are the libraries used? Fail-safe modules, stations, blocks, variable tables, etc. can be stored in Global libraries or in the Project library. Elements stored in Global libraries are available to all projects. These Global Libraries must be created explicitly. The Project library stores elements which can be re-used throughout a single project. The Project Library is automatically created and stored within the project. Page 24

13 Restrictions for safety program Program structure Restrictions F-runtime groups Compiling Download In the safety program you could not use all data- and parameter types, also there are restrictions regarding supplied instructions. Supported Data- und Parameter types: BOOL INT New: DINT WORD TIME Not supported Data- and Parameter types: elementary Data types not above-named (e. g. BYTE, REAL) composed Data types (e. g. STRING, ARRAY, STRUCT, UDT) Parameter types (e. g. BLOCK_FB, BLOCK_DB, ANY) Page 33

14 Restrictions for safety program Program structure Restrictions F-runtime groups Compiling Download Access to operands as follows: Data of data type BOOL, in bits Data of data type INT, in words Data of data type WORD, in words Data of data type DINT, in double words Data of data type TIME, in double words New: The PROFIsafe driver now supports DINT-Data types! Page 34

15 Data exchange between standard and safety program Program structure Restrictions F-runtime groups Compiling Download Which accesses to the process image are allowed? In standard program Reading Writing Reading In failsafe program writing Standardprocess image Inputs Outputs not allowed not allowed Failsafe process image Inputs Outputs not allowed not allowed not allowed not allowed Page 38

16 Data exchange between standard and safety program Program structure Restrictions F-runtime groups Compiling Download Which data accesses are allowed for data blocks? In standard program Reading Writing Reading In failsafe program writing Standard- Data block NEW: NEW: Failsafe Data block not allowed Page 39

17 Thank you for your attention!