Accessing S7 F-Systems Safety Engineering in Legacy SIMATIC PCS 7

Accessing S7 F-Systems Safety Engineering in Legacy SIMATIC PCS 7

In legacy SIMATIC PCS 7 versions (such as PCS 7 V6.1 with S7 F-Systems V5.2), the 'Edit Safety Program' icon does not appear automatically as a dedicated button on the main SIMATIC Manager toolbar. In these earlier releases, safety program administration is accessed strictly through the menu bar via Options -> Edit Safety Program (or from within a Continuous Function Chart via Options -> F-System). Automatic placement of the prominent yellow safety helmet and shield icon onto the SIMATIC Manager main toolbar was introduced in subsequent PCS 7 releases (V7.0 and later).

Table of Contents

Evolution of S7 F-Systems Toolbar Integration

In SIMATIC PCS 7, failsafe process automation (Burner Management Systems, Emergency Shutdown Systems, Fire & Gas) is engineered using the optional package S7 F-Systems. S7 F-Systems introduces certified failsafe blocks (F-Library), failsafe communication protocols (PROFIsafe), and specialized safety compilation routines that generate safety signatures and CRC checksums.

Control engineers accustomed to modern PCS 7 versions (V7.x, V8.x, V9.x) expect a prominent yellow safety helmet or shield icon on the primary SIMATIC Manager toolbar. When maintaining or commissioning older legacy installations running PCS 7 V6.1 with S7 F-Systems V5.2, engineers often assume the software installation is corrupted because this toolbar button is missing.

Menu Bar Access Paths in Legacy PCS 7 V6.1

The absence of the toolbar icon in PCS 7 V6.1 is completely normal and by design:

  1. Toolbar Architecture in STEP 7 V5.3: In the STEP 7 V5.3 generation underlying PCS 7 V6.1, third-party and optional package toolbar hooks were not fully dynamic. S7 F-Systems V5.2 registered its management utilities into the menu structure rather than the graphical icon bar.

  2. Menu Access Path: The safety administration dialog is located under menu Options -> Edit safety program (Extras -> Sicherheitsprogramm bearbeiten).

  3. CFC Editor Path: Inside the Continuous Function Chart editor, safety parameters, F-runtime groups, and safety shutdown groups are managed via menu Options -> F-System.

S7 F-Systems Safety Architecture and Compilation

Managing safety programs in legacy PCS 7 requires understanding the F-execution pipeline:

  1. F-Runtime Groups: Failsafe logic blocks (F_CH_DI, F_CH_AI, F_SWC_BO) must reside in dedicated failsafe runtime groups executed within cyclic organization blocks (OB35).

  2. F-Compiler (F-Call): When compiling CFC charts, the standard compiler calls the F-compiler. The F-compiler automatically inserts communication blocks (F_PS_12), checks data integrity, generates the F-runtime structure (F_SHUTDN), and computes the overall Safety Program Signature.

  3. Safety Password: Accessing the safety administration dialog requires the authorized Safety Password, preventing accidental modifications by non-certified personnel.

Comparison of Safety Program Access across PCS 7 Generations

The table below contrasts S7 F-Systems user interface integration across major PCS 7 versions.

PCS 7 VersionUnderlying S7 F-SystemsSIMATIC Manager Toolbar IconPrimary Navigation PathF-Matrix IntegrationPCS 7 V6.0 / V6.1S7 F-Systems V5.1 / V5.2Not Present (Menu Only)Options -> Edit safety programStandalone Matrix toolPCS 7 V7.0 / V7.1S7 F-Systems V6.0 / V6.1Yellow Safety Shield IconToolbar button or Options menuIntegrated Safety Matrix V6PCS 7 V8.0 / V8.1S7 F-Systems V6.1 SP2Yellow Safety Shield IconToolbar button or Options menuSafety Matrix V6.2PCS 7 V9.0 / V9.1S7 F-Systems V6.2 / V6.4Modern High-Contrast Safety IconToolbar button or Options menuSafety Matrix V6.3 with CPU 410-5H

Step-by-Step Procedure to Administer F-Systems in Legacy PCS 7

Follow this procedure to access and administer safety programs in PCS 7 V6.1:

  1. Verify S7 F-Systems Installation:
    - In SIMATIC Manager, select Help -> About -> Installed Software.
    - Verify that S7 F-Systems V5.2 (or V5.2 SP1) is listed with an active license in Automation License Manager.

  2. Open Safety Program Editor via Menu:
    - Highlight the target S7-400F/FH station or CPU in Component View.
    - Click menu Options -> Edit safety program (Extras -> Sicherheitsprogramm bearbeiten).
    - When prompted, enter the authorized Safety Password.

  3. Inspect Safety Signatures and Runtime Groups:
    - Review the dialog displaying: 'F-Program Name', 'Collective Signature', 'Compilation Date', and 'F-Blocks'.
    - Inspect configured F-Runtime groups to ensure cycle times and max execution limits are within safety tolerances.

  4. Compile and Download Safety Logic:
    - Open the safety CFC chart: execute changes using failsafe blocks from F-Blocks.
    - Compile the chart: verify that the F-compiler generates a new collective signature.
    - Download the safety program: confirm safety password authorization before downloading to the F-CPU.

Verification

Verify safety engineering functionality through the following checks:
1. Open Options -> Edit safety program: confirm that the dialog displays the active collective signature and compilation status.
2. In HW Config online view, confirm that fail-safe I/O modules (ET 200M F-DI/F-DO) communicate over PROFIsafe without bus faults.
3. Test a safety trip: force an emergency stop input to zero; verify that the failsafe output de-energizes within the certified safety response time.
4. Print the Safety Acceptance Report: ensure that the documented safety signature matches the online controller checksum.

Limitations and Operational Precautions

Modifications to safety logic must adhere strictly to IEC 61508 / IEC 61511 functional safety life-cycle procedures. Any modification to an F-chart alters the collective safety signature, requiring formal re-verification and safety validation testing before returning the plant to active operation. Never share or bypass the Safety Password, and never operate safety logic with forced inputs in production.

Engineer FAQ

Can I customize the SIMATIC Manager toolbar in PCS 7 V6.1 to add the F-Systems icon?

No. The STEP 7 V5.3 shell does not support user-customizable toolbar icons for optional packages; accessing the editor via the Options menu is the standard method.

Does S7 F-Systems V5.2 require a separate engineering license?

Yes. S7 F-Systems requires a dedicated engineering license key in Automation License Manager (or AuthorsW in older systems) to enable compilation.

Can I run S7 F-Systems V5.2 on a standard non-failsafe S7-400 CPU?

No. S7 F-Systems requires certified fail-safe controllers (such as CPU 414-4H, CPU 417-4H, or CPU 410-5H) operating under safety runtime licenses.

Technical References

Related Articles

Related Tags

  • S7 F-Systems
  • PCS 7 V6.1
  • Safety Integrated
  • Edit Safety Program
  • PROFIsafe
  • Safety Signature
6 respuestas