Siemens SIMATIC S7 Configuration And Programming Manual
  1. Manuals
  2. Brands
  3. Siemens Manuals
  4. Controller
  5. SIMATIC S7
  6. Configuration and programming manual

Siemens SIMATIC S7 Configuration And Programming Manual

Hide thumbs Also See for SIMATIC S7:
Table of Contents

Advertisement

Quick Links

Download this manual
s
SIMATIC S7
Product Information
Manual S7 Distributed Safety,
Configuring and Programming
Scope
This product information document supplements the S7 Distributed Safety,
Configuring and Programming manual, A5E00109537-01,
Edition 03/2002.
Documentation Package
The manual indicated above and this product information document are included in
the documentation package S7 Distributed Safety, 6ES7 988-8FB10-8BA0.
Organization of Product Information Document
This product information document is organized in two parts. The first part
describes all the changes to the optional package S7 Distributed Safety, V 5.2 +
Service Pack 1 compared with Version V 5.1.
The second part presents corrections to the S7 Distributed Safety, Configuring and
Programming manual, A5E00109537-01, Edition 03/2002, that could not be made
prior to publication. These corrections apply to versions V 5.1, V 5.2 and V 5.2 +
Service Pack 1 of the S7 Distributed Safety optional package.
Cross-References in this Product Information
For the sake of brevity, references to sections of the manual mentioned above do
not include the name of the manual (for example, "see manual, Section 6.3").
All cross-references that do not indicate a specific publication refer to this product
information documentation (for example, "see Section 1.2.2").
Copyright  Siemens AG 2002-2003
Subject to change without prior notice
Siemens Aktiengesellschaft
A5E00169432-02
Edition 07/2003
A5E00109537-01

Advertisement

Table of Contents
loading

Related Manuals for Siemens SIMATIC S7

Summary of Contents for Siemens SIMATIC S7

  • Page 1: Converting From S7 Distributed Safety, V 5.1 To V 5.2 + Service Pack

    (for example, "see manual, Section 6.3"). All cross-references that do not indicate a specific publication refer to this product information documentation (for example, "see Section 1.2.2"). Copyright  Siemens AG 2002-2003 Subject to change without prior notice Siemens Aktiengesellschaft...

  • Page 2: Table Of Contents

    Contents Converting from S7 Distributed Safety, V 5.1 to V 5.2 + Service Pack 1 Configuration ....................... 7 1.1.1 Configuring Safety-Related Master to I-Slave Communication ......7 1.1.2 Safety-Related CPU-CPU Communication ............12 1.1.3 Configuring Safety-Related Master to I-Slave Communication ......13 1.1.4 Configuring Safety-Related I-Slave to I-Slave Communication......
  • Page 3 Converting from S7 Distributed Safety, V 5.1 to V 5.2 + Service Pack 1 What's New in S7 Distributed Safety, V 5.2 Compared with V 5.1? The major innovations in S7 Distributed Safety, V 5.2 compared with V 5.1 are listed below: •...
  • Page 4 Software Requirements for S7 Distributed Safety, V 5.2 + Service Pack 1 The following software package (at least) must be installed on the PC or programming device: STEP 7, V 5.1 + Service Pack 6 or higher or: Please note that use of the following functions is possible only with higher STEP 7 versions: Function Required STEP 7 Version...
  • Page 5 Note When you install S7 Distributed Safety, V 5.2 + SP 1, the Excel file for V 5.1 or. V 5.2 (...\Siemens\STEP7\S7Manual\s7fco\s7fcotib.xls) supplied with the optional package is overwritten. If you made your response time calculations directly in this file rather than in a copy of the file that you created in a different folder, save the V 5.1 or V 5.2 file in another folder before installing S7 Distributed Safety,...
  • Page 6 Conversion of S7 Distributed Safety from V 5.1 to V 5.2 + SP 1 Reading a Safety Program with S7 Distributed Safety V 5.2 + SP 1: If you would like to use S7 Distributed Safety V 5.2 +SP 1 to read, but not change, a safety program created with S7 Distributed Safety V 5.1, open the "Safety Program"...

  • Page 7: Configuration

    Configuration 1.1.1 Configuring Safety-Related Master to I-Slave Communication Overview Note This section is only relevant if you are using S7 Distributed Safety V 5.2 + SP 1 with STEP 7, ≤ V 5.2. If you use STEP 7, ≥ V 5.2 + SP 1, the information in Sections 1.1.2 through 1.1.4 is relevant to you.
  • Page 8 Configuring Input/Output Data Areas You must configure both an output data area and an input data area in HW Config for each communication connection between two F-CPUs. In the figure below, each of the two F-CPUs is supposed to be able to send and receive data. You must therefore configure two output data areas and two input data areas for each F-CPU.
  • Page 9 Procedure for Configuring Master to I-Slave Communication The same procedure is used to configure safety-related communication master to I- slave communication as is used to configure master to I-slave communication in a standard system. The figure below illustrates the configuration procedure for the address areas in the previous figure.
  • Page 10 10. Confirm your entries with "OK." Product Information for the S7 Distributed Safety, Configuring and Programming Manual A5E00169432-02...
  • Page 11 11. Continue following steps 8 and 9 until all output and input data areas are defined. This results in four configuration rows for this example: Note Be sure to use identical values for the start addresses of the output and input data areas.

  • Page 12: Safety-Related Cpu-Cpu Communication

    1.1.2 Safety-Related CPU-CPU Communication Note This section and the following sections 1.1.3 and 1.1.4 are valid only if you are using S7 Distributed Safety V 5.2 + SP 1 with STEP 7, ≥ V 5.2 + SP 1. If you are using STEP 7, ≤ V 5.2, the information in Section 1.1.1 applies. Overview The schematic below shows you an overview of the 3 options for safety-related CPU-CPU communication in S7 Distributed Safety F-systems.

  • Page 13: Configuring Safety-Related Master To I-Slave Communication

    1.1.3 Configuring Safety-Related Master to I-Slave Communication Overview Safety-related master to master communication is described in the manual. The following section describes the configuration of an additional safety-related communication option, that is, safety-related communication between safety programs in different F-CPUs. As in a standard system, safety-related communication between the safety program of the F-CPU of a DP master and the safety program(s) of the F-CPU(s) of one or more intelligent DP slaves (I-slaves) is handled over master to I-slave connections.
  • Page 14 You specify the configuration of the following in the object properties dialog of the I-slave: • to send to the DP master, a local address (I-slave) and a partner address (DP master) • to receive from the DP master, a local address (I-slave) and a partner address (DP master) You assign the configured addresses to the LADDR parameter of the corresponding F application blocks F_SENDDP and F_RCVDP in the safety...
  • Page 15 How to Configure Master to I-Slave Communication The figure below illustrates the configuration procedure for the address areas in the previous figure. Requirement: You have created a project in STEP 7. 1. Create a station in your project (in SIMATIC Manager, for example, an S7-300 station).
  • Page 16 10. Confirm your entries with "OK." 11. In the "F-Configuration" tab of the Object Properties of the I-slave, select "New." 12. In the next dialog, make the following entries for the send connection to the DP master for our example: For "Mode: F-MS-S"...
  • Page 17 Note In the object properties of the I-slave, entries are automatically made in the "Configuration" tab based on the configuration in the "F-Configuration" tab. These entries must not be modified. Otherwise, safety-related master to I-slave communication is not possible. The assigned address areas on the DP master and I-slave can be seen in the "Configuration"...

  • Page 18: Configuring Safety-Related I-Slave To I-Slave Communication

    1.1.4 Configuring Safety-Related I-Slave to I-Slave Communication Overview The manual describes safety-related master to master communication. The following section describes the configuration of an additional safety-related communication option, that is, safety-related communication between safety programs in different F-CPUs. As in standard systems, safety-related communication between the safety program of the F-CPUs of intelligent DP slaves involves direct data exchange.
  • Page 19 You specify the configuration of the following in the object properties dialog of I- slave 1: • to send to I-slave 2, a local address (I-slave 1) and a partner address (I-slave 2) • to receive from I-slave 2, a local address (I-slave 1) and a partner address (I-slave 2) No further configuration of communication is necessary in the object properties dialog of I-slave 2.
  • Page 20 How to Configure I-Slave to I-Slave Communication The figure below illustrates the configuration procedure for the address areas in the previous figure. Requirement: You have created a project in STEP 7. 1. Create a station in your project (in SIMATIC Manager, for example, an S7-300 station).
  • Page 21 The dialog appears as shown below: 12. Confirm your entries with "OK." 13. In the "F-Configuration" tab of the Object Properties of I-slave 1, select "New." 14. In the next dialog, make the following entries for the send connection to I-slave 2 for our example: For "Mode: F-DX-S"...
  • Page 22 Note In the object properties of the relevant I-slave, entries are automatically made in the "Configuration" tab based on the configuration in the "F-Configuration" tab. These entries must not be modified. Otherwise, safety-related I-slave to I-slave communication is not possible. The assigned address areas on the DP master and I-slaves can be seen in the "Configuration"...

  • Page 23: Configuring The F-Cpu

    Safety Note The calculated maximum runtime of the safety program using the MS Excel file in the directory (...\Siemens\STEP7\S7Manual\s7fco\s7fcotib.xls) is no longer be correct in this case, because the calculation assumes sufficient F-local data are available.
  • Page 24 Note Note that the maximum possible amount of F-local data depends on the following: • Local data requirement of your higher-level standard user program For this reason, you should call the F-CALL block directly in the OB (cyclic interrupt OB35, if possible) and not declare any additional local data in the cyclic interrupt OB.
  • Page 25 Comment: You can derive the local data requirement of the OB from the program structure. In SIMATIC Manager, select the Options > Reference Data > Display menu command (Setting: "Program structure" selected). This shows you the local data requirement in the path or for the individual blocks (see also STEP 7 Help). Case 2: F-CALL not called directly in the OB Standard...
  • Page 26 Local Data Requirement for the Automatically Added F-Blocks According to Local Data Requirement of User Safety Program The information below must be taken into account only if the amount of local data available for your safety program is insufficient and you received a message from S7 Distributed Safety to that effect.
  • Page 27 Use of Local Data in an F-FB or F-FC Note F-blocks are automatically added when the safety program is compiled to create an executable safety program from your safety program. If you use the local data memory area in an F-FB/F-FC, remember the following limit (irrelevant for F-CPUs from the S7-400 range): Local data requirement<...

  • Page 28: Programming The Safety Program

    Programming the Safety Program 1.2.1 Differences between F-Programming Languages and Standard Programming Languages Access to Data Blocks Data blocks should always be accessed with "fully qualified DB access" to ensure that the correct data block is opened. The initial access to data of a data block in an F-FB/F-FC must always be a "fully qualified DB access,"...

  • Page 29: Fbd/Lad Operations

    1.2.2 FBD/LAD Operations New Operations Supported You can use the operations listed in the table below in the safety program. Operation Function Description F-FBD F-LAD --( JMP ) Jump operation Unconditional jump in block Jump in block if 1 (conditional) JMPN --( JMPN ) Jump operation Jump in block if 0 (conditional)
  • Page 30 OV bit, the execution time of the operation influencing the OV bit is prolonged (see also Excel file for calculating the response time in the ...\Siemens\STEP7\S7Manual\s7fco\s7fcotib.xls folder). Safety Note If an OV bit scan is programmed in the network following the operation that...

  • Page 31: F I/O Db

    1.2.3 F I/O DB Default Settings for QBAD and PASS_OUT Contrary to the description in Section 5.3.2 of the manual, the default setting for the tags QBAD and PASS_OUT of the F-I/O DB is "1". The default setting of "1" has no effect on safety programs that were created with S7 Distributed Safety V 5.1.

  • Page 32: Implementing A User Acknowledgment

    1.2.5 Implementing a User Acknowledgment This section supplements Section 5.3.9 of the manual. 1.2.5.1 Implementing a User Acknowledgment in the Safety Program of the F-CPU of a DP Master See manual, Section 5.3.9. 1.2.5.2 Implementing a User Acknowledgment in the Safety Program of the F-CPU of an Intelligent DP Slave Options for User Acknowledgment You can implement a user acknowledgment in one of the following ways:...
  • Page 33 1. User acknowledgment using an operator control and monitoring system with which you can access the F-CPU of the I-slave To implement a user acknowledgment using an operator control and monitoring system, you require the F application block F_ACK_OP from the F-library Distributed Safety (V1) (see manual, Section 5.7.3.7).
  • Page 34 Procedure for Programming User Acknowledgment by Means of an Acknowledgment Key at an F-I/O with Inputs that is Assigned to the F-CPU of the DP Master 1. Call the F-application block F_SENDDP in the safety program in the F-CPU of the DP master (see manual, Section 5.4).

  • Page 35: Programming Safety-Related Master To I-Slave Communication And I-Slave To I-Slave Communication

    1.2.6 Programming Safety-related Master to I-Slave Communication and I-Slave to I-Slave Communication Overview The manual describes safety-related master to master communication. The procedure for programming safety-related master to I-slave communication or safety-related I-slave to I-slave communication is exactly the same as for programming safety-related master to master communication.
  • Page 36 How to Assign F-CPUs to F_SENDDP/F_RCVDP Assign the F-CPUs to F_SENDDPs/F_RCVDPs as follows: • Configure the address areas (local and partner addresses) for the DP master and the I-slave(s) in HW Config (see Sections 1.1.1, 1.1.3 and 1.1.4) • Specify the following for master to I-slave communication in the safety program of the F-CPU of the DP master: in F_SENDDP for input parameter LADDR, the partner address for sending ("F-Configuration"...
  • Page 37 DP Master I-slave 1 F-CPU 1 F-CPU 2 Safety Program Safety Program F_SENDDP: DP_DP_ID = 1 F_RCVDP: DP_DP_ID = 1 F_RCVDP: DP_DP_ID = 2 F_SENDDP: DP_DP_ID = 2 F_SENDDP: DP_DP_ID = 3 F_RCVDP: DP_DP_ID = 5 F_RCVDP: DP_DP_ID = 4 F_SENDDP: DP_DP_ID = 6 I-slave 2 F-CPU 3...
  • Page 38 Limits for Data Transfer If the amount of data to be transmitted is greater than the capacity of a F_SENDDP/F_RCVDP block pair, you can use additional F_SENDDP/ F_RCVDP block pairs. These require further communication connections. Remember the maximum limit of 244 bytes of input and 244 bytes of output data for transfer between an I-slave and a DP master.

  • Page 39: F-Shared Db

    1.2.7 F-Shared DB F-Shared DB In addition to the items specified in Section 5.5 of the manual, you can read out the following in the standard user program or by means of an operator control and monitoring system: • Compile data of the safety program (tag "F_PROG_DAT", data type DATE_AND_TIME) Note Starting with S7 Distributed Safety V5.2, the collective signature of the safety...

  • Page 40: Creating F-Blocks In F-Fbd/F-Lad

    1.2.8 Creating F-Blocks in F-FBD/F-LAD "Check Block Consistency" Function The "Check block consistency" function can be found in SIMATIC Manager in the "Edit" menu, if you have selected a block container. The "Check block consistency" function rectifies many of the time stamp conflicts and block inconsistencies.
  • Page 41 Setting Know-how Protection Requirements: You have created F-FBs or F-FCs and you want to protect the know-how they contain. The F-FBs/F-FCs you want to protect are not open in the FBD/LAD Editor. Follow the steps outlined below: 1. Open the "Safety Program" dialog in the SIMATIC Manager. 2.
  • Page 42 Note Assign a unique name for the backup copy so that you can later identify the F-FB/F-FC and the protected F-FB/F-FC (for example, same name, comment on F-FB/F-FC). Do not save the backup copy in the project containing the protected F-FB/F-FC (otherwise an unprotected copy of the F-FB/F-FC is available).

  • Page 43: Distributed Safety F-Library (V1)

    1.2.10 Distributed Safety F-Library (V1) Introduction This section supplements Section 5.7 of the manual and describes the changes to the Distributed Safety F-library (V1) in S7 Distributed Safety V 5.2 + SP 1. 1.2.10.1 Changes Changing F-Application Block Numbers Note Contrary to what is stated in the manual, you are permitted to change the F-application block numbers.
  • Page 44 F_SENDDP and F_RCVDP The following information supplements Section 5.7.3.10 of the manual. The F-application blocks F_SENDDP and F_RCVDP are used as follows: • for safety-related master to master communication • for safety-related master to I-slave communication • for safety-related I-slave to I-slave communication The information in Section 5.7.3.10 of the manual also applies.

  • Page 45: Fb 179 "F_Sca_I": Scaling Values Of Data Type Int

    1.2.11 FB 179 "F_SCA_I": Scaling Values of Data Type INT Connectors Parameter Data Description Default Type Inputs Input value to be scaled in physical units HI_LIM Upper limit value in physical units LO_LIM Lower limit value in physical units Outputs Result of scaling OUT_HI BOOL...

  • Page 46: Fc 178 "F_Int_Wr": Writing A Value Of The Data Type Int Indirectly Into An F-Db

    1.2.12 FC 178 "F_INT_WR": Writing a Value of the Data Type INT indirectly into an F-DB Connectors Parameter Data Type Description Inputs Value to be written to the F-DB ADDR_INT POINTER Start address of the INT area in an F-DB END_INT POINTER End address of the INT area in an F-DB OFFS_INT INT...

  • Page 47: Fc 179 "F_Int_Rd": Reading A Value Of The Int Data Type From An F-Db

    Examples of the Parameter Assignment of ADDR_INT, END_INT, and OFFS_INT Declaration Type Initial Value Comments Address Name Example 1 Example 2 Example 3 1.2.13 FC 179 "F_INT_RD": Reading a Value of the INT Data Type from an F-DB Connectors Parameter Data Type Description Inputs...
  • Page 48 Mode of Operation This F application block reads the tag addressed by ADDR_INT and OFFS_INT of the data type INT in an F-DB and applies it to the OUT output. Via the ADDR_INT input, the start address of the area with tags of the data type INT in an F-DB from which the tag will be read is transferred.

  • Page 49: Fb 190 "F_1Oo2Di": 1Oo2 Evaluation With Discrepancy Analysis

    1.2.14 FB 190 "F_1oo2DI": 1oo2 Evaluation with Discrepancy Analysis Connectors Parameter Data Description Default Type Inputs BOOL Sensor 1 BOOL Sensor 2 DISCTIME TIME Discrepancy time (0 ... 60 s) T# 0 ms ACK_NEC BOOL 1 = acknowledgment necessary for discrepancy error BOOL Acknowledgment of discrepancy error...
  • Page 50 Activating inputs IN1 and IN2 The two inputs IN1 and IN2 must be activated so their positive state is 0. Example For non-equivalent signals, you have to negate the input (IN1 or IN2), which you have assigned the positive state 1 for the sensor signal . You must also OR the sensor signal with the QBAD tags of the corresponding F-I/O DB, so that signal state 0 is applied to input IN1 or IN2 (after the negation), if substitute values are output.
  • Page 51 Startup Behavior Note If the sensors at the inputs IN1 and IN2 are assigned to different F-I/Os, it is possible that the substitute values are output for different lengths of time following startup of the F system due to different startup response of the F-I/Os. If the signal states of the two inputs IN1 and IN2 remain different after the discrepancy time DISCTIME has elapsed, a discrepancy error is detected after the F system starts If ACK_NEC = 1 you must acknowledge the discrepancy error with a rising edge...
  • Page 52 DIAG Output The DIAG output provides non fail-safe information on errors for service purposes. You can read this out using the operator control and monitoring system or evaluate it in your standard user program. The DIAG bits remain stored until you acknowledge at the ACK input.

  • Page 53: User-Created F-Libraries

    1.2.15 User-Created F-Libraries User-Created F-Libraries As of S7 Distributed Safety, V 5.2 + SP 1, you can create your own F-libraries for S7 Distributed Safety. These "user-created F-libraries" can include only the following: • F-FBs and F-FCs created by users in F-FBD/F-LAD •...
  • Page 54 Note if your new F-library is not displayed in the FBD/LAD editor, open and close the FBD/LAD editor. By repeating the steps outlined above, you can create as many F-libraries for S7 Distributed Safety as you wish. Working with User-Created F-Libraries To use F-FBs/F-FCs/application templates from user-created F-libraries, you must have the S7 Distributed Safety version installed on your PC/PG with which the F-FBs, F-FCs or application templates were created.

  • Page 55: Compiling The Safety Program

    1.2.16 Compiling the Safety Program Note Before you compile the safety program, close the LAD/STL/FBD editor, Display S7 Reference Data, and Check Block Consistency applications. 1.2.17 Complete Function Test of Safety Program or Protection through Program Identification Introduction The following two sections replace the corresponding sections in the Section 5.8.5 of the manual.
  • Page 56 Safety Note If more than one F-CPU is accessible over a network (such as MPI) from one programming device or PC, you must take the following additional measures to ensure that the safety program is downloaded to the correct F-CPU: Use passwords specific to each F-CPU, such as a uniform password for the F-CPUs having the respective MPI address as an extension: "Password_8".
  • Page 57 Safety Note If more than one F-CPU is accessible over a network (such as MPI) from one programming device or PC, you must take the following additional measures to ensure that the safety program is downloaded to the correct F-CPU: Use passwords specific to each F-CPU, such as a uniform password for the F-CPUs having the respective MPI address as an extension: "Password_8".

  • Page 58: Transferring The Safety Program To The F-Cpu Using A Memory Card

    1.2.17.2 Transferring the Safety Program to the F-CPU Using a Memory Card Use of MMC or Flash Card The following safety note applies to use of the following: • Flash card (for example with CPU 416F-2) • MMC (for example with CPU 317F-2 DP, CPU 315F-2 DP or IM 151-7 F-CPU) Safety Note If the function of the safety program is not tested in the target F-CPU, you must comply with the following procedure when transferring the safety program to the...

  • Page 59: Deactivating Safety Mode

    1.2.18 Deactivating Safety Mode Safety operating mode/evaluating deactivated safety mode If you wish to evaluate the safety operating mode or deactivated safety mode in the safety program, you can evaluate the "MODE" tag in the F-shared DB (1 = deactivated safety mode). These tags are accessed fully qualified ("F_GLOBDB".MODE).

  • Page 60: Comparing Safety Programs

    1.2.19 Comparing Safety Programs "Compare Program" Dialog Box The following information supplements Section 5.10.2 of the manual. The "Compare Program" dialog box has been expanded to include the following two columns: • "Function in the Safety Program" • "Interface Different" The "Function in the Safety Program"...

  • Page 61: Printing Out Project Data Of The Safety Program

    1.2.20 Printing Out Project Data of the Safety Program Printing Out Additional Project Data with S7 Distributed Safety V 5.2 + SP 1 In addition to the project data indicated in Section 5.11 of the manual, the following project data are printed out for the safety program: •...

  • Page 62: Corrections To The S7 Distributed Safety, Configuring And Programming Manual, A5E00109537-01, Edition 03/2002

    Corrections to the S7 Distributed Safety, Configuring and Programming Manual, A5E00109537-01, Edition 03/2002 Introduction This section presents corrections to the above-indicated edition of the manual that could not be made prior to publication. The corrections are associated with the corresponding sections of the manual. The corrections apply to versions V 5.1 and V 5.2 +SP 1 of the optional package S7 Distributed Safety.
  • Page 63 Section 3.4, Configuring the F I/Os Safety Note The switch setting on the address switch of the F I/O, in other words, its PROFIsafe target address must be unique within the network* and station** (throughout the system). You can assign a maximum of 1022 PROFIsafe target addresses in a system, in other words, a maximum of 1022 F I/Os can be addressed over PROFIsafe.
  • Page 64 Section 5.1.3, Supported Data and Parameter Types Note TIME input/output parameters of a calling F-FB/F-FC may not be assigned as the current parameters for formal parameters of a called F-FB/F-FC. In the safety program, read and write access to block parameters of the data type TIME in instance DBs of F-FBs is not permitted.
  • Page 65 Section 5.1.3, Access to Formal Parameters of an F-FB/F-FC Note Note that you can only read the input parameters in an F-FB/F-FC and only write to its output parameters. Use an input/output parameter if you wish to read and write. If you wish to use a formal parameter of an F-FB/F-FC for the edge memory bits of the operations query edge (N, P) or query signal edge (NEG, POS) or for the address of the operations flip-flop (SR, RS), set output (S) or reset output (R),...
  • Page 66 Section 5.1.3, DIV_I Operation Note If the divisor (input IN2) of a DIV_I operation = 0, the quotient of the division (result of division at output OUT) = 0. The result behaves like the same operation in a standard user program. The F-CPU does not change to STOP. This is the response regardless of whether there is OV-bit scan programmed in the next network.
  • Page 67 Section 5.3.3, Fully Qualified DB Access In contrast to the information in the manual, Section 5.3.3 access to F I/O DBs of the F I/O of which no channel is used in the safety program, does not lead to an F-CPU STOP.
  • Page 68 Section 5.5, Data Transfer from Safety to Standard User Program Note The process image input table of the F I/O is updated not only at the start of the F run-time group before processing the F-program block, but also by the standard operating system.
  • Page 69 Block size of all automatically generated F blocks To make sure that the automatically compiled F-blocks do not exceed the maximum possible size in the particular F-CPU, remember the following: • The maximum size of an F-FB/F-FC/F-PB should be a quarter of the max. size of the FBs or FCs (see Technical Specifications in the manual of the F-CPU you are using).
  • Page 70 Section 5.7.3.8, F_2HAND: Two-Hand Monitoring The following paragraph replaces the note on the functionality of F_2HAND in the manual: Note: With an F application block, only one signal per button can be evaluated. With suitable configuration (type of sensor wiring: antivalent sensor) the discrepancy monitoring of the NC and NO contact of the IN1 and IN2 button is performed directly by the F I/O with inputs.

Table of Contents