Siemens MP277 S7-300 Recipe Management: OPC Batch Buffer in SCL

Overview

This reference documents a production recipe and batch management architecture built around a Siemens SIMATIC MP277 multi-panel, a CPU 317-2 PN/DP controller, and an office-level MS Access database. The pattern is deliberately PLC-centric: all recipes and batch jobs live in the S7-300 work memory so that a loss of network connectivity to the office PC cannot corrupt the production schedule. The HMI acts as a thin client, and OPC DA on the MP277 acts as the bridge between the office network and the automation cell.

The design answers three engineering questions that typically come up on this hardware generation:

1. Should the recipe data live on the MP277 (WinCC Flexible recipe system) or in the S7-300 CPU?
2. How do you expose the S7 tags to an office PC without paying for a separate OPC server?
3. How much load memory and work memory does a custom PLC recipe buffer actually consume, and when does the design break down?

The remainder of the article gives a defensible answer to each, with parameter tables, SCL code fragments, commissioning checks, and a migration path forward to the S7-1500 generation.

System Architecture

The reference cell follows a strict three-layer model. Layering matters because the office PC, the HMI, and the PLC all have different availability and ownership characteristics, and a recipe system that crosses all three must be designed around the weakest link.

The MP277 317-2PN/DP variant integrates both PROFINET and PROFIBUS DP interfaces, which is the exact part cited on Siemens migration guidance for the S7-300 generation. For the historical context and known caveats when moving from a CPU 318-2 DP to the 317-2 PN/DP architecture, see the official entry "What should you watch out for when migrating from the CPU 318-2 DP to the CPU 317-2 DP and CPU 317-2 PN/DP?".

The data flow is intentionally one-way authoritative on the office side and one-way authoritative on the control side. The HMI only caches; it never holds the only copy of a recipe.

Hardware Bill of Materials

Recipe Storage: WinCC Flexible Native vs PLC-Stored

This is the central architectural decision. The MP277 running WinCC Flexible 2008 ships with a built-in recipe system that stores records in a CSV file on the panel's internal flash. There is also the option of treating the PLC DB as the recipe store and using the panel as a view.

For this design the choice is the PLC-stored buffer because the operator is not authorized to edit parameters. Recipes are engineered in the office, released to the cell, and the operator only starts jobs. Native WinCC Flexible recipes invite parameter edits the procedure is trying to prevent.

Memory Sizing Calculation

Before writing any code, size the DB. The rule of thumb in STEP 7 V5.x is: every REAL consumes 4 bytes, every INT consumes 2 bytes, every BOOL consumes 1 byte but pads to the next even byte, and every STRING[n] consumes (n + 2) bytes for the S7-300 string header.

Use the closed-form estimate:

DB_size_bytes = N_records * ( SUM(REALS) * 4 + SUM(INTS) * 2 + SUM(STRINGS_i) * (LEN_i + 2) + 2 )

Reference example from a deployed system: 99 records x 50 REALs = 99 * (50*4) = 19,800 bytes, plus 99 x STRING[20] = 99 * 22 = 2,178 bytes. Total approximately 22 kB. That fits comfortably inside the 1 MB work memory of the 317-2 PN/DP with 99.7 percent of memory still free for cyclic tasks and diagnostic buffers.

Examine the scaling limit. If the design ever needs 1,000 records with 200 REALs each, that is 800 kB plus string overhead, which still fits the 317-2 PN/DP work memory but consumes more than 80 percent of usable space and is the point at which migration to a 317-2 DP with 4 MB or an S7-1500 becomes mandatory. The Siemens migration guide "Guide for Migrating SIMATIC S7-300/S7-400 to SIMATIC S7-1500" covers the sizing and topology change in detail.

SCL Implementation: Batch Buffer

The SCL below implements three structures: an in_buffer that holds the next batch job pushed by the office, a batch_list with 50 fixed slots, and a current_job that mirrors the slot the operator has armed. SCL is preferred over ladder for the index-based scan because a FOR loop over an array of UDTs is far shorter than 50 rungs of indirect addressing.

// DB901 - Recipe Definitions (UDT 901 = 10 REALs + STRING[20])
// DB902 - Batch List (ARRAY[1..50] OF UDT 901)
// DB903 - In Buffer (UDT 901)
// DB904 - Current Job (UDT 901)

FUNCTION_BLOCK FB901 "BatchManager"
VAR
    i         : INT;                // loop index
    emptySlot : INT;                // first free slot in batch_list
    armedSlot : INT := 0;           // slot operator has armed
END_VAR

BEGIN

    // --- 1. ACCEPT IN_BUFFER INTO BATCH_LIST ---
    IF "in_buffer_valid" = TRUE AND "office_release" = TRUE THEN
        emptySlot := 0;
        FOR i := 1 TO 50 DO
            IF "batch_list".slot[i].used = FALSE AND emptySlot = 0 THEN
                emptySlot := i;
            END_IF;
        END_FOR;

        IF emptySlot > 0 THEN
            "batch_list".slot[emptySlot] := "in_buffer";
            "batch_list".slot[emptySlot].used := TRUE;
            "in_buffer".used := FALSE;        // clear handshake
            "in_buffer_valid" := FALSE;        // office may now write the next
        ELSE
            "alarm_batch_list_full" := TRUE;   // raise operator alarm
        END_IF;
    END_IF;

    // --- 2. ARM A BATCH (operator button) ---
    IF "cmd_arm_batch" = TRUE THEN
        armedSlot := "hmi_selected_slot";
        "current_job" := "batch_list".slot[armedSlot];
        "cmd_arm_batch" := FALSE;
        "cmd_machine_reset" := TRUE;          // machine adjusts to new params
    END_IF;

    // --- 3. RELEASE A BATCH (after last piece) ---
    IF "cmd_release_batch" = TRUE THEN
        IF armedSlot > 0 AND armedSlot <= 50 THEN
            // zero the slot so it can be reused
            FOR i := 1 TO 10 DO
                "batch_list".slot[armedSlot].param[i] := 0.0;
            END_FOR;
            "batch_list".slot[armedSlot].name := '';
            "batch_list".slot[armedSlot].used := FALSE;
        END_IF;
        armedSlot := 0;
        "current_job".used := FALSE;
        "cmd_release_batch" := FALSE;
    END_IF;

END_FUNCTION_BLOCK

Three implementation rules to keep this code maintainable:

1. Use a UDT for the recipe record, not parallel arrays. A change in parameter count then propagates to every slot automatically.
2. Handshake with the office through two booleans (in_buffer_valid + office_release), not by polling the same byte. This protects against partial writes if the OPC link drops mid-record.
3. Never let the office overwrite an armed slot. Either freeze the slot from office writes while armedSlot <> 0, or copy in_buffer to the slot on accept as shown above and never expose the slot itself to OPC.

OPC Communication Layout

The MP277 317-2PN/DP runs an OPC DA 2.05 server internally. The office PC acts as an OPC DA client, and the S7-300 is reachable from the panel as a tagged connection. The minimum tag surface for the office is shown below.

Recommended update rates on the OPC client: 100 ms for state flags and 1,000 ms for full slot lists. The MP277 OPC server is comfortable at this rate; pushing 50 slot records at 100 ms saturates the panel's user interface thread and causes screen redraw stalls.

HMI Integration with WinCC Flexible

The operator screen set is intentionally minimal: a Batch Overview that lists all 50 slots, an Arm button, a Release button, and a parameter view that mirrors DB904.current_job.

To make the 50-row list manageable, build it with multiplex tags in WinCC Flexible. Define an index tag list_index (INT) and an array of pointer tags, then refresh on a 500 ms schedule. The alternative of manually placing 50 list views is brittle and consumes panel area memory.

Migration to S7-1500 / TIA Portal

When the recipe count grows, the office network expands, or the MP277 enters its end-of-service window, plan the migration. The STEP 7 V5.x project that owns FB901 and DB902..DB904 can be converted with the TIA Portal migration tool, but the UDT syntax and OPC surface require manual re-work.

Step-by-step:

1. Open the STEP 7 V5.6 project and run File > Migration > TIA Portal. This produces a .am20 file the TIA Portal can read. See the official guide "Migration of STEP 7 projects (S7-300, S7-400) - TIA Portal".
2. Replace the S7-300 STRING[20] S7 string header with the S7-1500 variant. The byte length is identical (n + 2) but the optimized block access setting will re-pack the DB.
3. Re-validate the FB901 loop bounds; the 1500 CPUs accept 32-bit loop counters natively and skip the implicit INT-to-DINT conversion warnings.
4. Migrate the WinCC Flexible 2008 project to WinCC Comfort / TIA Portal. The OPC server surface remains OPC DA on the Comfort Panel, but item IDs change to the TIA Portal syntax.
5. Update the office MS Access VBA client to point at the new OPC item names.

For a forward-looking reference of the 1500 hardware, the migration guide "Guide for Migrating SIMATIC S7-300/S7-400 to SIMATIC S7-1500" provides a complete catalog of removed and changed features.

Verification and Commissioning

Run this 10-point checklist before handing the cell to production.

1. Power up the CPU 317-2 PN/DP with the MMC inserted. Verify SF / BF LEDs are off and RUN is solid green.
2. In STEP 7, download HW Config and the S7 program. Open DB902 online and confirm 50 slots of zeros.
3. Force in_buffer_valid FALSE; push 51 records from the office OPC client. Verify slot 51 raises alarm_batch_list_full and is not stored.
4. Force in_buffer_valid TRUE for one record; verify the slot populates and the in_buffer.used flag clears within one OB1 cycle.
5. From the MP277, select slot 3 and press Call Batch. Verify current_job mirrors slot 3 and that cmd_machine_reset pulses for one cycle.
6. Run the machine through the full batch; verify the piece counter increments and the slot becomes free after Release.
7. Pull the office network cable mid-batch. Verify the running batch completes and cmd_release_batch still works locally.
8. Reconnect the office network. Verify the next released batch appears in the next free slot.
9. Force a power loss on the MP277 only. Verify the PLC still has all 50 slots intact in DB902 after restoration.
10. Force a power loss on the PLC. Verify after restart that DB902 is reloaded from MMC with the last persisted state and the MP277 OPC server reconnects within 30 s.

Troubleshooting Matrix

Field-Proven Caveats

Three observations from deployed systems that are not in the manuals.

1. MMC wear. Every recipe release triggers a DB write. With 200 batches per shift, the work memory write is not the issue, but if the project also uses recipes for trace logging, prefer to keep the recipe DB in work memory and copy to a separate log DB only on batch close. This avoids unnecessary MMC writes that shorten card life.
2. STRING[20] alignment. The S7-300 places STRING[20] at even byte boundaries inside a DB. If a recipe record mixes REALs and STRINGs without a UDT, the layout can be 2 bytes off. Always define a UDT and use the UDT as the DB row type to keep alignment automatic.
3. OPC DA vs OPC UA. The MP277 OPC DA server does not speak OPC UA. If the office network is required to use OPC UA, install a third-party DA-to-UA bridge (for example, a Softing dataFEED OPC Suite or Kepware) rather than trying to add a UA server to the panel.

Frequently Asked Questions