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

How to Resolve SCL String Length Limits When Mapping Large STRUCTs to PCS 7 OS

How to Resolve SCL String Length Limits When Mapping Large STRUCTs to PCS 7 OS

In SIMATIC S7-SCL, applying the operator control and monitoring attribute S7_xm_c to a large user-defined structure (STRUCT) triggers compiler error 'String literal too long (over 254 characters)' when the comma-separated member transfer string exceeds 254 characters. The S7-SCL compiler enforces a hard architectural limit of 254 bytes for string literals and attribute parameters. To resolve this error and successfully transfer data to WinCC OS, you must refactor the monolithic structure into smaller modular sub-structures (each with its own S7_xm_c attribute within the 254-character ceiling) or declare critical process variables as individual block I/O parameters tagged with S7_m_c := 'true'.

Table of Contents

Root Cause: The 254-Character SCL String Literal Ceiling

When engineering custom function blocks in SIMATIC S7-SCL for PCS 7, developers use attributes to tell the compiler which variables should be automatically created as WinCC tags during the Compile OS run.

For elementary data types (such as REAL or BOOL), the attribute syntax is compact:

MyInput { S7_m_c := 'true' } : REAL;

However, for structured variables (STRUCT), PCS 7 requires the extended attribute S7_xm_c. The compiler requires a formatted string literal that specifies which individual internal members of the struct should be compiled to the OS:

MyLargeStruct { S7_xm_c := 'Val1,true;Val2,true;Val3,true;...' } : STRUCT

Because the S7-SCL compiler enforces a fundamental language ceiling restricting any string literal to a maximum of 254 characters, defining a structure with dozens of members causes the assignment string to exceed 254 bytes, immediately aborting compilation with:
Error: String literal too long (maximum 254 characters).

How PCS 7 and WinCC Process Structure Attributes

The PCS 7 OS compiler processes block structures differently than standard PLC data blocks:
* APL Standard Structure Format: In the Advanced Process Library (APL), structures are intentionally kept minimal. Standard structures typically contain only two elements: Value (the process value, such as REAL) and ST (the 8-bit signal status byte).
* Tag Multiplexing: WinCC compiles structured block tags as structured types (Structure Types) containing child tags. Transferring monolithic structures with hundreds of mixed variables creates massive, unoptimized DB communication records that overburden AS-OS cyclic communication buffers.

Attempting to force an entire machine or data table into a single STRUCT with S7_xm_c violates the distributed architecture of PCS 7.

Architectural Comparison: Monolithic STRUCT vs. Modular Sub-STRUCTs

Engineering ApproachSCL Compiler SupportOS Compilation EfficiencyMaintenance & ReuseSingle Monolithic STRUCTFails if S7_xm_c string > 254 charactersHigh communication overhead, unoptimized WinCC tag packingRigid; modifying one element re-indexes entire structureModular Sub-STRUCTsFully supported (each sub-struct has own S7_xm_c string < 254 char)Balanced communication; groups related variables into logical subsetsFlexible; allows independent reuse of functional groupsIndividual Block Pins (S7_m_c)Fully supported without string limitsOptimal; PCS 7 driver generator groups tags dynamicallyRecommended by Siemens APL Style Guide for direct faceplate binding

Method: Refactoring SCL Code to Comply with OS Mapping Limits

To resolve the 254-character compiler limitation, choose one of the following two approved patterns:

Pattern A: Partitioning into Modular Sub-Structures (Recommended for Grouped Data)

Divide the large structure into smaller logical groupings (such as Setpoints, Status, Diagnostics), ensuring each attribute string remains well below 200 characters:

VAR_INPUT
    Setpoints { S7_xm_c := 'Speed,true;Temp,true;Pressure,true;' } : STRUCT
        Speed : REAL;
        Temp : REAL;
        Pressure : REAL;
    END_STRUCT;

    Status { S7_xm_c := 'Run,true;Trip,true;Ready,true;' } : STRUCT
        Run : BOOL;
        Trip : BOOL;
        Ready : BOOL;
    END_STRUCT;
END_VAR

Pattern B: Exposing Individual Block Parameters (Recommended for Faceplate Integration)

If the values must be displayed on standard PCS 7 faceplates or connected via CFC charts, declare them directly as block input/output variables:

VAR_INPUT
    SP_Speed { S7_m_c := 'true'; S7_unit := 'rpm' } : REAL := 0.0;
    SP_Temp { S7_m_c := 'true'; S7_unit := '°C' } : REAL := 0.0;
    Act_Run { S7_m_c := 'true' } : BOOL := FALSE;
END_VAR

Verification

To verify that the refactored SCL block compiles and maps successfully to WinCC:

  1. In S7-SCL, execute File > Compile (Ctrl+B). Verify that the compilation window reports: 0 Errors, 0 Warnings.
  2. In SIMATIC Manager, open a CFC chart and insert an instance of your newly compiled block.
  3. Verify that the sub-structures or individual pins appear properly on the CFC block margin.
  4. In SIMATIC Manager, right-click the OS project and select Compile OS (Scope: Changes only).
  5. Open WinCC Explorer > Tag Management.
  6. Expand your AS driver connection (Named Connections). Verify that WinCC successfully instantiated the structured tags or individual process tags with their configured hierarchical paths.

Limitations and Operational Precautions

  • AS-OS Download Synchronization: Changing block interfaces from a monolithic structure to multiple sub-structures alters the internal block signature (checksum). This requires a CPU download in STOP mode or careful Configuration in Run (CiR) planning if existing chart instances are modified.
  • UDT Compatibility: If using User-Defined Data Types (UDTs) in SCL, remember that attributes applied inside the UDT definition do not automatically transfer to WinCC. The S7_m_c or S7_xm_c attribute must be explicitly declared on the block interface variable where the UDT is instantiated.
  • WinCC Tag Licensing: Every individual variable exposed to the OS with true consumes a WinCC process tag license, unless configured within raw data blocks.

Engineer FAQ

Can I use multiple lines in SCL to break up a long S7_xm_c string?
No. Line breaks or string concatenation operators inside compiler attributes are not parsed by the S7-SCL preprocessor. The entire attribute string must be a single continuous literal.

What is the difference between S7_m_c and S7_xm_c?
S7_m_c applies to elementary data types (REAL, BOOL, INT) and takes a simple boolean value ('true' or 'false'). S7_xm_c applies to complex STRUCT types and requires an explicit mapping list defining which struct members to transfer.

Why does Siemens APL avoid large user structs in CFC blocks?
APL avoids large structures to maintain deterministic execution and allow CFC chart interconnections between individual pins. Monolithic structs prevent interconnection of individual values in the CFC editor.

Technical References

  • Siemens Industry Online Support Entry ID 109742323: SIMATIC S7-SCL V5.3 for S7-300/400 Manual
  • S7-SCL for S7-300 and S7-400 Programming Manual (Document No. 6ES7811-1CA02-8BA0)
  • Siemens Industry Online Support Entry ID 109765887: APL Style Guide for Developing Reusable Process Blocks

Related Articles

Related Tags

  • https://industrialautomation.net/search?query=s7-scl
  • https://industrialautomation.net/search?query=simatic+pcs7
  • https://industrialautomation.net/search?query=os-compile
  • https://industrialautomation.net/search?query=tag-management
20 respuestas