MP277 Recipe Limits: Loading 1000+ Records via WinCC RT

Problem Overview: MP277 Recipe Capacity Ceiling

The Siemens SIMATIC MP277 10-inch Multi Panel ships with WinCC Flexible 2008 SP5 (or WinCC in the TIA Portal from V13 SP1 onward) and is constrained to a small slice of integrated Flash memory for recipe handling. The Siemens ST catalog / product datasheet rates the panel at 64 kByte integrated Flash, expandable for recipe data, with a published upper bound of 500 data records per recipe. In field practice, however, the runtime routinely refuses additional writes well before that ceiling — typically between 300 and 350 records — depending on tag widths, internal record overhead, project indexing, and the directory structure of the recipe CSV files stored under \Flash\Recipes or the configured data medium.

This reference walks through the three engineering paths that move the recipe database off the panel's internal Flash and onto media that can scale to 1000 or more records:

1. Run WinCC Runtime Advanced on an industrial PC connected to the MP277 over PROFINET/Industrial Ethernet — the panel becomes a thin client and the PC holds the recipe database.
2. Redirect the MP277 recipe Data Medium \ Path to a USB stick, MMC card, or network share so that the runtime streams records to a much larger volume.
3. Export the recipe to CSV on an external medium, edit / extend it off-line, and re-import through the standard recipe transfer sequence.

MP277 Hardware and Memory Specifications

The MP277 platform (6AV6 643-0xxxxx-xxxx order numbers, 10" Touch variant) has the following characteristics relevant to recipe handling:

The catalog value "500 records" is a marketing headline — it assumes a minimal tag configuration. Siemens documents it as "Recipe memory: 64 kByte integrated Flash, expandable" rather than a hard record count, because the real ceiling scales with the byte width of each tag in the recipe plus per-record file-system and index overhead. A recipe tag of type Real (4 bytes) consumes twice the bytes of a Bool or Int tag, and a String tag of length 50 consumes 52 bytes on disk plus delimiter overhead.

Root Cause Analysis: Why 336 Records Load Instead of 500

Three factors combine to drop the practical record count below the datasheet figure:

1. Per-record CSV overhead. The runtime serializes every record as one CSV line. Each line carries the record number, all tag values, a CR/LF pair, and a per-record metadata block in the file's index. Empirically, this adds 8 – 12 bytes of overhead per record on top of the raw tag bytes.
2. Flash file-system fragmentation. The integrated 64 kByte Flash uses a wear-aware file system. As free blocks shrink, the runtime stops allocating new records long before the byte counter hits zero to leave room for administrative blocks, the directory, and the file allocation table.
3. Project overhead. The compiled WinCC Flexible / TIA project image, text lists, alarm logs, and audit trails share the same Flash volume. A heavy project eats into the 64 kByte budget the catalog allots to recipes, so a project that uses 30 kByte for images leaves only ~34 kByte for recipes, which at typical 100-byte records caps the count near 340.

Path 1 — WinCC Runtime Advanced on an Industrial PC

The cleanest engineering path is to stop loading recipes into the MP277's internal Flash and load them into a WinCC Runtime Advanced instance on an industrial PC. The MP277 then connects to the runtime over PROFINET/Industrial Ethernet and operates as a client for recipe display and operator interaction.

Topology

+-------------------+    PROFINET / Ethernet    +--------------------------+
|   SIMOTION /      | <----------------------> |   Industrial PC          |
|   SINAMICS (PLC)  |                          |   WinCC RT Advanced      |
+-------------------+                          |   - Recipe DB (unbounded)|
                                               |   - CSV on local disk    |
                                               +-----------+--------------+
                                                           |
                                                           | Ethernet (HMI client link)
                                                           v
                                               +--------------------------+
                                               |   MP277 10" Touch        |
                                               |   (client display only)  |
                                               +--------------------------+

Configure the PC Runtime Connection

Follow the official Siemens procedure for setting up a WinCC RT Advanced connection to an S7 / SIMOTION controller over PROFINET, documented in Siemens Support entry 89852595 — Configuring a WinCC RT Advanced to S7 connection over PROFINET. The high-level steps are:

1. Open the TIA Portal project that contains the PC station.
2. In Devices & Networks, add the SIMATIC PC station and select WinCC RT Advanced as the HMI runtime.
3. Drag a HMI connection between the PC station and the S7 / SIMOTION controller on the network view.
4. Set the connection parameters: IP address of the controller (e.g., 192.168.0.10), Rack/Slot (typically 0 / 1 for an S7-300/400, or the PROFINET device name for SIMOTION), and the access point S7ONLINE.
5. Configure the MP277 as a secondary HMI device or as a separate SmartClient panel pointing to the PC runtime's IP.
6. Compile the PC station and download the runtime to the PC.

Recipe Storage on the PC

With the runtime on a PC, the recipe database is stored as CSV under a folder chosen at runtime, typically:

C:\ProgramData\Siemens\Automation\WinCCRTAdv\Recipes\<RecipeName>\<DataRecordName>.csv

This removes every Flash-imposed ceiling. A 1 GB CSV file holds on the order of 5 – 10 million records depending on tag width. The PC runtime reads and writes records directly to disk and the MP277 merely displays and edits them through the HMI client link.

Path 2 — USB / MMC Data Medium on the MP277

If the panel must remain the runtime (no PC in the cabinet), the next-best path is to redirect the recipe Data Medium \ Path to an external medium. This is the documented mechanism for "expandable" recipe memory.

Configure the Data Medium Path

1. In the WinCC Flexible / TIA Portal project, open the recipe properties.
2. Set Storage media to Data medium instead of Internal Flash.
3. Set the Data medium \ Path to the USB stick or MMC card root, for example:

   \Storage Card USB\Recipes\<RecipeName>\
   

   or for a network share reached through the panel's Ethernet port:

   \\<ServerIP>\RecipeShare\<RecipeName>\

4. Ensure the path exists on the medium and the runtime user has write access (for a network share, the panel must authenticate with a Windows or SMB credential).
5. Recompile and transfer the project to the panel.

CSV Format Expected by the Runtime

The runtime writes one CSV file per data record. The format is fixed:

<RecipeTag1>;<RecipeTag2>;<RecipeTag3>;...
<Value1>;<Value2>;<Value3>;...

• Field separator: ; (semicolon) by default in the EU locale; , in the US locale. The locale is set in the project's Project > Language & Font settings.
• Decimal separator: , in EU locale (so a value of 12.5 is written as 12,5).
• String values that contain the separator character must be quoted with ".
• Encoding: ASCII or UTF-8 without BOM.

Path 3 — Export / Import Through External Medium

The third path keeps the panel as the runtime, keeps the recipes in internal Flash for performance, but uses an external medium as an off-line archive and staging area. This is the workflow that the source's export_USB.jpg attachment attempted.

Export a Recipe to USB

1. On the MP277, open the recipe view.
2. Select the recipe and trigger Export. The runtime writes the records as CSV to the configured Export path, typically \Storage Card USB\Export\<RecipeName>.csv.
3. Remove the USB stick and edit the CSV on a PC (Excel, Notepad++, scripted Python parser).

Re-import the Extended CSV

1. Save the modified CSV back to the USB stick under the path the runtime expects, typically \Storage Card USB\Import\<RecipeName>\<DataRecordName>.csv.
2. Plug the USB stick back into the MP277.
3. Trigger Import from the recipe view or via the configured Import path.

Operator-Initiated Transfer Sequence

Whether the recipe lives in internal Flash, USB, or on a network share, the operator-driven transfer sequence is identical. The canonical flow is documented in the TIA Portal help under "Sequence of a transfer started by the operator in the recipe display" — see TIA Documentation Cloud — Recipe transfer sequence (Basic Panels, Panels, Comfort Panels, RT Advanced).

1. Operator opens the recipe display on the panel.
2. Operator selects New (create record) or selects an existing record and edits values.
3. Operator presses Save. Runtime writes the values to the tags of the connected PLC (one-shot Read from PLC, write back to PLC on Save).
4. Runtime persists the record to the configured data medium (Flash, USB, network share, or PC runtime disk).
5. Runtime updates the record index so the new record shows in the recipe view list.

The PLC tag values flow in this order: PLC → HMI tag → CSV file → display on Read; HMI tag → PLC → CSV file on Save. If the PLC is offline when the operator hits Save, the runtime will queue the write until the connection re-establishes, but only if the connection-loss behavior is set to "Buffer records" in the recipe properties.

Tag Sizing and Record-Count Math

Use the following formulas to estimate how many records will fit before reaching the panel's internal ceiling. Adjust the constants based on your project's measured overhead.

BytesPerRecord = Sum(TagWidths) + RecordOverhead
AvailableFlash = 64 * 1024 - ProjectOverhead - FileSystemReserve
MaxRecords    = floor(AvailableFlash / BytesPerRecord)

Siemens-specific tag widths:

For a 20-tag recipe of 5 Int, 10 Real, 3 String[20], and 2 Bool tags:

Sum(TagWidths) = (5*2) + (10*4) + (3*22) + (2*1) = 10 + 40 + 66 + 2 = 118 bytes
RecordOverhead = ~10 bytes
BytesPerRecord = 128 bytes

AvailableFlash (after ~25 kByte project)  = 39 * 1024 = 39 936 bytes
MaxRecords                                  = floor(39 936 / 128) = 312 records

This matches the field observation of ~336 records being the practical ceiling for a typical 20-tag recipe. The discrepancy between 312 and 336 reflects project-specific overhead and Flash wear-leveling blocks.

Troubleshooting Matrix

Verification Steps

1. Confirm the storage medium path with Recipe view > Properties > Storage media on the panel.
2. Save a test record and inspect the medium (USB on a PC, network share via SMB, or panel's \Flash via the ProSave tool).
3. Open the CSV in a text editor and confirm the header row matches the recipe tag list.
4. Insert 1000 records via the import workflow and verify the recipe view lists all 1000.
5. Trigger Read on a record and confirm the values land in the connected PLC tags.
6. Trigger Save and confirm the values round-trip back to the CSV on the medium.
7. Reboot the panel and verify the records persist after power cycle.

Safety and Operational Notes

• Always keep a backup of the recipe CSV before editing it off-line. A malformed CSV can render the recipe unusable until the project is recompiled and re-transferred.
• If the MP277 is part of a safety-related application, recipe data records are not safety-certified storage. Critical setpoints must be validated by the F-CPU after each Save.
• Industrial USB sticks with SLC NAND and an operating-temperature rating of -25 °C to +75 °C are required for cabinet-mounted panels.
• The MP277 USB port is specified for low-power devices; do not connect bus-powered hard disks or high-current peripherals.

Frequently Asked Questions