Resolving KTP700 Recipe Corruption Error in TIA Portal V13

Problem Overview

The runtime alarm "Recipes are corrupt or do not match your configuration data" appears on Siemens SIMATIC Basic Panels (KTP400, KTP700, KTP900, KTP1200) and Comfort Panels (TP700, TP900, TP1200, TP1500, TP1900, TP2200) when the recipe data record stored on the HMI's internal flash or on an external storage medium (USB stick, SD card) no longer matches the recipe definition compiled into the panel project. On KTP700 Basic Panels programmed with TIA Portal V13 (WinCC Basic V13) and connected to an S7-1200 CPU (firmware V4.x), the fault is most often triggered after a recipe write is interrupted by power-down, after a project download without the Overwrite all option, or after a partial project migration that changes tag lengths, array bounds, or recipe element offsets.

The fault is non-fatal to the PLC scan but blocks the HMI recipe view and recipe transfer functions. Operators see a frozen screen, the alarm line in the bottom status bar reads Recipes are corrupt or do not match your configuration data, and the panel refuses to load or save records until the recipe data set is reconciled with the engineering project.

Affected Components and Versions

Root Cause Analysis

The alarm text is generated by the WinCC Runtime recipe manager when the CRC-16 stored in the recipe header on the panel does not match the CRC-16 calculated from the current recipe element definition in the loaded project. Five distinct root causes have been observed on KTP700 + S7-1200 + TIA Portal V13 systems:

1. Power loss or stop mode during recipe write. The panel writes the recipe header first, then the data elements. If the 24 V supply collapses or the panel is switched off between header commit and payload write, the file on flash memory retains a stale header. On next boot, the integrity check fails.
2. Project download without Overwrite all. When the engineering station performs a partial download (only the HMI software, not the recipe DB), the panel keeps its existing recipe file but receives a new project binary. The two are out of sync and the runtime declares them corrupt.
3. Tag-length mismatch between PLC DB and recipe element. If a PLC tag linked to a recipe element is resized (for example DInt → LReal, or String[10] → String[20]), the panel's compiled recipe offsets no longer match the S7-1200 DB layout. The recipe manager refuses to load the record.
4. Project migration without recipe recompilation. Upgrading a V13 project to V14 or V15 using the TIA Portal migration tool without selecting Recompile all recipe entries preserves the old recipe element metadata. New compile produces new offsets; runtime detects mismatch.
5. Firmware/HMI image version skew. A V13 SP1 project downloaded into a panel whose firmware was flashed to a V14 or V15 image retains a recipe layout from the older compiler while the runtime now expects the newer one. Siemens documents this in entry ID 109749634.

Diagnostic Procedure

Before applying any fix, determine which root cause applies. Follow the steps in order and stop at the first matching result.

1. Capture the panel diagnostics buffer. On the KTP700, open Control Panel > Diagnostics > Diagnostics Buffer. Note any entries containing RECIPE, CHECKSUM, or IO fault. Cross-reference timestamps with the operator log.
2. Check PLC tag references in the recipe definition. In TIA Portal, open HMI > Recipes > [recipe name] > Elements. Right-click each element and select Go to > Used tag. Confirm the tag points to a DB element of the correct length and type. Any BOOL tagged as WORD, or any WString instead of String, is a mismatch.
3. Inspect the panel file system via ProSave. Use Siemens ProSave (bundled with TIA Portal) or the panel's Control Panel > Backup/Restore to export the recipe folder. Compare the binary file size against the size recorded in the project under HMI > Recipes > [recipe] > Properties > Record length.
4. Read the panel event log via WinCC Tag Logging / Alarm Viewer. Trigger a recipe save from the runtime; the AlarmViewer text will report the specific recipe name and record index that failed. Typical entry: Recipe "BatchParams", record 7: Data does not match configuration.
5. Verify the panel image version. In Control Panel > System > About, record Image Version and HMI RT Version. Match against the TIA Portal installation: C:\Program Files\Siemens\Automation\Portal V13\HmiRtm\Versions.txt.

Recipe Storage Architecture

Understanding where the panel stores recipe data is essential to a permanent fix. The following table summarises the canonical paths used by TIA Portal V13 / V14 / V15.

Each recipe record consists of a 32-byte header (recipe name, record name, CRC-16, timestamp, length) followed by the serialized element payload. The header CRC covers both the recipe name string and the payload bytes. Any modification to element order, type, or length invalidates the stored CRC.

Solution A: HMI Overwrite Download (Temporary)

The forum workaround of Download to device > Overwrite all is a valid short-term recovery but does not address the underlying cause. Apply it as follows:

1. Open the TIA Portal V13 project containing the panel and PLC stations.
2. Select the KTP700 in the project tree.
3. Right-click and choose Download to device > Software (all).
4. In the download dialog, tick Overwrite all.
5. Click Continue and enter the panel transfer password if prompted.
6. Wait for the panel to restart; the runtime will rebuild the recipe index from the new project and existing records will either be accepted (if structure matches) or marked invalid and discarded.

This solves the immediate symptom but the alarm typically returns within days if root cause is not addressed.

Solution B: Permanent Fix — Align Recipe Elements to PLC DB

1. Open the S7-1200 PLC station in TIA Portal and locate the DB used as recipe source.
2. For each recipe element, verify:
   • PLC DB element length equals recipe element length.
   • PLC DB element type is supported by the HMI recipe manager (BOOL, INT, DINT, REAL, STRING, WSTRING, ARRAY of these).
   • No POINTER, ANY, VARIANT, or UDT references exist inside the recipe element list.
3. If any element is mismatched, modify the DB first, then update the recipe element accordingly, then compile the HMI software (not just "Save and compile all").
4. Recompute the recipe record length. Right-click the recipe > Properties > Record length. The displayed byte count must equal the sum of all element byte lengths.
5. Delete the existing recipe records on the panel: open Control Panel > Recipes, select each record, choose Delete. Confirm the panel no longer reports the corruption alarm after a warm restart.
6. Perform a clean Overwrite all download from TIA Portal.

Solution C: Migrate to TIA Portal V14 / V15

Migrating the project to a newer TIA Portal version resolves the recipe-element-offset bug fixed in WinCC Comfort/Advanced V14 SP1 (entry 109751391).

1. Open the V13 project in TIA Portal V14 (or V15) and accept the migration prompts.
2. Open Project > Compile > Software (rebuild all). Do not skip the recipe rebuild.
3. In HMI > Recipes > [recipe], right-click each recipe and choose Recompile recipe.
4. Compare record lengths before and after migration. A delta of zero confirms structural integrity.
5. If record length changes, manually re-export production recipes from the HMI as CSV (if Comfort Panel) or binary (if Basic Panel), then re-import after the new download completes.
6. Download the migrated project to the panel with Overwrite all enabled.

Solution D: Power-Failure Hardening

If root cause is interrupted writes during recipe save, configure the panel to use a buffered storage medium and enable UPS-backed 24 V supply.

1. Switch the recipe storage path to a USB stick rated for industrial use (Siemens 6AV2 181-1LA00-0AA0 or equivalent). USB provides greater write-cycle endurance than internal flash.
2. In TIA Portal: HMI > Runtime settings > Recipes > Storage location set to USB storage.
3. Enable Save recipe records synchronously on the recipe view. This forces a complete commit before acknowledging success to the operator.
4. Add a UPS (e.g., SITOP UPS1600 6EP4134-3AB00) on the 24 V supply feeding the panel so the panel has at least 5 seconds of ride-through to finalize a write in progress.

Verification

After applying any of the four solutions, run the following verification sequence to confirm the fault is resolved:

1. Cycle power to the panel (24 V off for at least 10 seconds).
2. Wait for the boot screen to clear and the project to load. Confirm no recipe alarm appears within 60 seconds of runtime start.
3. From the recipe view, create a new record with name VERIFY_TEST, set non-default values, save, and read back. Confirm the read values match the written values.
4. Restart the panel a second time and repeat step 3. The record must survive a power cycle.
5. Force a PLC tag change (e.g., toggle a BOOL recipe element from the PLC watch table), refresh the recipe view, and confirm the runtime reports the new value.
6. Run the panel for 72 hours under normal production load. If the alarm does not recur, mark the fault closed in the maintenance log.

Troubleshooting Matrix

Preventive Measures

• Lock the TIA Portal project version used in production. Avoid ad-hoc upgrades of V13 projects without a regression test plan that includes recipe cycle testing.
• Standardize the recipe element list in a project template. All new recipes must inherit from the template DB structure.
• Always perform Overwrite all downloads during commissioning and after firmware updates.
• Schedule a quarterly recipe backup via ProSave. Archive the Recipes folder for each panel along with the project archive.
• Implement a UPS on the panel supply to prevent recipe header corruption from AC mains events.
• Train operators to wait for the recipe-write confirmation before toggling the panel off. Add a flashing status indicator next to the recipe view to make write-in-progress obvious.

Related Siemens Documentation

• Entry 109749634 — Recipe errors on WinCC Basic Panels after project migration
• Entry 109751391 — Recipe element offsets in TIA Portal V14 SP1
• Entry 109751605 — KTP700 Basic firmware compatibility matrix
• SIMATIC HMI KTP700 Basic manual
• SIMATIC S7-1200 Programmable Controller system manual