C135 PCS 7 (PCS7)
6C
6 Cielo Ciencia y Tecnología
·Publicada en C135 PCS 7 (PCS7)

Resolving Error Compiling OS in SIMATIC PCS 7 Open OS Database Automation

Resolving Error Compiling OS in SIMATIC PCS 7 Open OS Database Automation

In SIMATIC PCS 7 / Open OS environments using Database Automation (DBA) to integrate third-party controllers or S7-1500 package units, the generic compilation failure 'Error Compiling OS PCS 7 OS (Server/Single Station)' occurs when technological hierarchy folders in DBA have not been mapped to a target WinCC OS project. To resolve this, open DBA, navigate to 'Plant View', right-click the root technological hierarchy node, select 'Assign OS', map the folder structure to the target WinCC OS Server or Single Station, and execute 'Compile > Entire OS' from within DBA.

Table of Contents

Executive Summary

Package units, skid machinery, and third-party control systems (such as Siemens S7-1500, S7-1200, or non-Siemens PLCs communicating via OPC) are frequently integrated into the central SIMATIC PCS 7 operator supervisory layer using SIMATIC PCS 7 / Open OS. Within this architecture, the Database Automation (DBA) tool serves as the bridge: it parses controller symbol tables or DB export files, creates technological hierarchy folders, maps process variables into WinCC tag management, and automatically generates APL-style block icons and faceplates.

During initial engineering or following skid modifications, automation engineers frequently configure objects in DBA, assign graphic symbols, and click 'Start compilation', only to be halted by a fatal, non-descriptive error: Error Compiling 'OS' PCS 7 OS (Server/Single Station). Because the error log provides minimal diagnostic context, engineers often assume project corruption. In reality, DBA cannot compile tags into WinCC without an explicit relational binding linking the technological hierarchy to a physical OS project object in SIMATIC Manager. This guide details the exact DBA assignment workflow and compilation requirements to eliminate this error.

Architecture and Fundamental Mechanics

The PCS 7 / Open OS architecture operates through synchronized database translation layers:

  1. Role of Database Automation (DBA):
    - DBA is a standalone engineering utility that bridges non-PCS 7 data sources into the PCS 7 Plant Hierarchy and WinCC CS database.
    - It imports controller data definitions (e.g., S7-1500 TIA Portal exports, OPC DA/UA server address spaces) into an internal XML repository.
    - In DBA, engineers define technological types (motors, valves, analog monitors) and assign graphical block icons.

  2. The Technological Hierarchy to OS Binding Requirement:
    - In standard PCS 7, SIMATIC Manager Plant View directly dictates which hierarchy folder belongs to which OS Server.
    - In Open OS DBA, this relationship must be explicitly configured in the DBA 'Plant View' pane.
    - If technological folders exist in DBA without an assigned target OS, the DBA compiler (DBA.exe) attempts to generate WinCC tags and messages into a null database pointer, crashing the compilation engine with Error Compiling 'OS'.

  3. DBA Compilation Workflow:
    - When 'Compile OS' is executed with valid bindings:

    • DBA creates WinCC process tags and internal structures.
    • It injects alarm messages into WinCC Alarm Logging via the Open OS messaging engine.
    • It places block icons onto assigned WinCC process pictures (.pdl).

Step-by-Step Implementation Procedure

Follow these steps to configure OS station assignments in DBA and resolve compilation errors:

  1. Verify PC Station Configuration in SIMATIC Manager:
    - In SIMATIC Manager Component View, ensure the target PC Station exists and contains a valid WinCC OS application (e.g., WinCC Appl. or WinCC Appl. (Server)).
    - Confirm that the OS project name and storage path are valid.

  2. Open Project in Database Automation (DBA):
    - Launch the DBA utility from the Windows Start menu or within SIMATIC Manager ('Options > SIMATIC PCS 7 Open OS > Database Automation').
    - Open your existing DBA project (.dba).

  3. Assign OS to the Technological Hierarchy in DBA Plant View:
    - In the left pane of DBA, switch to the 'Plant View' tab (representing the plant hierarchy structure).
    - Locate the root folder (or individual skid hierarchy folders containing imported controllers).
    - Right-click the root hierarchy folder > select 'Assign OS...'.
    - In the selection dialog, browse and select the target WinCC OS project defined in your PCS 7 multiproject.
    - Confirm that the hierarchy folder icon updates to reflect the active OS binding.

  4. Verify Picture and Block Icon Assignments:
    - In the DBA Plant View, select each hierarchy folder containing technological objects.
    - In the properties pane, ensure each folder has an assigned WinCC process picture name (e.g., Skid_Overview.pdl).
    - Confirm that imported technological instances have valid block icon type attributes assigned.

  5. Execute Full OS Compilation from DBA:
    - In the DBA tree, right-click the target OS node under 'PC Stations'.
    - Select 'Compile > Entire OS' (for initial compilation) or 'Compile > Changes Only'.
    - In the compilation options, ensure 'Tags', 'Alarms', and 'Block Icons' are selected.
    - Click 'Start'. The compiler will now parse the data structures cleanly and generate all WinCC runtime objects without aborting.

Verification

  1. In DBA, inspect the compilation progress log: confirm that it completes with 0 Errors and reports successful tag and message generation.
  2. Open the WinCC project in WinCC Explorer: open Tag Management and verify that tags from the external S7-1500 / skid are populated under the Open OS communication channel.
  3. Open the target process picture in WinCC Graphics Designer: confirm that block icons for the package unit appear on the screen.
  4. Start WinCC Runtime: verify that live process data updates and alarms trigger correctly.

Limitations and Operational Precautions

Ensure that the version of PCS 7 / Open OS matches the installed WinCC version; mixing incompatible Open OS service packs can cause tag table schema mismatches. Large tag import files from TIA Portal should be pre-filtered to avoid importing thousands of unneeded internal PLC variables. Software licenses for SIMATIC PCS 7 / Open OS and WinCC Runtime Process Objects should be verified through an authorized Siemens distributor or the Siemens Industry Mall.

Engineer FAQ

What causes 'Error Compiling OS' in Database Automation (DBA)?

The technological hierarchy folders in DBA have not been assigned to a target WinCC OS project, leaving the compiler with no destination database.

Where is the OS assigned inside the DBA tool?

In the DBA 'Plant View' tab, by right-clicking the root hierarchy folder and selecting 'Assign OS...'.

Can DBA import data from S7-1500 controllers?

Yes, DBA natively parses S7-1500 symbol exports and data blocks to generate WinCC tags and faceplates.

Does Open OS support automated block icon placement?

Yes, DBA automatically places block icons onto assigned WinCC process pictures during compilation.

Do Open OS process tags consume WinCC Process Object licenses?

Yes, tags mapped to technological block icons consume standard WinCC OS Runtime Process Objects.

Technical References

Related Articles

Related Tags

  • Open OS
  • Database Automation
  • DBA
  • Error Compiling OS
  • S7-1500 Integration
  • PCS 7 V9.1
20 respuestas