IMDTouchKnowledge BaseShop main store

How-to

Editing WinCC Flexible Recipes From a PC Without the Engineering Tool

HMI and touchscreens Published 5 min read

Short answer

Recipe values and new data records can be edited from any PC when the WinCC flexible runtime exports a CSV to MMC or USB and imports it back; the .dat, .rdf and .vdf files inside the panel have no supported external editor. Adding or removing recipe parameters always needs the engineering project.

On this page
  1. What you can change at runtime and what you cannot
  2. Why the .dat, .rdf and .vdf files stay closed
  3. The CSV export and import workflow
  4. Worked case: a client panel that stores recipes as .dat, .rdf and .vdf
  5. When the runtime gives you no export button
  6. Verifying the restored data
  7. Questions asked

You can edit recipe values and add data records from any PC, but only through a CSV file that the WinCC flexible runtime itself writes to an MMC or USB flash drive. Edit that CSV in any spreadsheet or text editor, then load it back through the runtime's import function or a ProSave restore. The .dat, .rdf and .vdf files inside the panel are never your edit surface. If the project was built without an export control, or the change touches recipe parameters, the engineering project has to be opened once.

What you can change at runtime and what you cannot #

Two different things live under the word "recipe". Parameters define which fields a record holds; data records are the filled instances of those fields. Only the second kind of change happens outside the engineering project.

Change you need Where it happens Possible without the engineering tool
Edit values in an existing data record Runtime recipe screen, or CSV round trip Yes, when edits are enabled or an export control exists
Add a new data record Runtime button that creates a record, or CSV import Yes, when the control or the export exists
Add or remove a recipe parameter Engineering project only No

Before planning any PC round trip, touch a value on the recipe screen. If the panel accepts a typed value, editing is enabled and the simplest path is right there at the screen. If it refuses, the control was configured read-only or restricted by user group, and an authorized login is the first thing to try.

Why the .dat, .rdf and .vdf files stay closed #

Those three extensions are the panel's internal recipe storage, and no supported external editor, documented file structure, or conversion utility exists for them. A file that opens in a hex or text editor proves nothing: the runtime is not documented to load those files back after you modify them, and a changed record the runtime cannot parse is a record you can no longer use. Every supported editing path starts with an export the runtime itself created.

The CSV export and import workflow #

  1. Open the recipe screens and look for two controls: a button that creates a new data record, and an export control — many projects label it "Save Data to SD Card". Neither is created by default; the original developer had to add them.
  2. Put an MMC or USB flash drive in the panel and trigger the export. The runtime's export function writes the recipe data to the device as a CSV file.
  3. Move the device to the PC and open the CSV in any spreadsheet or text editor. Change values and add records, keeping the existing column structure intact.
  4. Return the device to the panel and trigger the configured import or read function so the records load back into the runtime.
  5. Export a fresh copy before every editing session, so the file you change always starts from the panel's current data.

If the project has no export control at all, ProSave is the remaining supported way to move recipe data off the panel and back: its backup and restore cover operator panel data including recipes.

Worked case: a client panel that stores recipes as .dat, .rdf and .vdf #

The inputs:

  • The goal, from the client's requirement: edit existing recipes and add new ones from a PC, without Siemens engineering software.
  • The observation from the panel: the recipe data sits in files with .dat, .rdf and .vdf extensions.
  • The deciding input, unknown until checked: which controls the recipe screens actually expose.
  • Out of scope: recipe parameters stay exactly as they are.

The rule in words: the internal files are never edited directly, so the entire decision turns on what the runtime exposes. An export control or a ProSave recipe backup puts an editable CSV in your hand; nothing puts a parameter editor there.

The check, written out:

  1. Touch a value on the recipe screen. If it accepts a typed change, edits are enabled, and records can be maintained at the screen without any PC round trip.
  2. Look for the export control. If it is present, the five-step workflow above meets the client's requirement with any PC and any editor.
  3. If it is absent, ProSave backup and restore remains for moving records, or one project session adds the missing buttons.

The result and the decision: for this panel, .dat, .rdf and .vdf are storage, not documents, and nothing done on the PC touches them directly. The "edit from any PC" requirement is met the day the runtime carries an export control; until then, no external editor meets it.

When the runtime gives you no export button #

Adding the export and import controls is a project edit, and like any HMI edit it needs a new runtime download before the panel carries the buttons. Whoever holds the project makes that change once and the CSV workflow stays open for good.

When nobody can locate the project at all, start from recovering the HMI program when the source file is lost. And if migration is on the roadmap, recipe data exported from a WinCC flexible panel can be imported into a WinCC (TIA Portal) project later, so today's CSVs stay usable on the path covered in migrating a WinCC flexible project to TIA Portal.

Verifying the restored data #

After the import, open each edited record on the recipe screen and confirm every value before the record is activated for production. Restored values reach the machine the moment it runs, so one wrong cell is a process change, not a display glitch.

If an import fails or records look wrong, repeat from a fresh export. Do not repair the situation by touching the internal files.

Questions asked

Does ProSave edit recipe values?

No. ProSave backs up and restores operator panel data, recipes included, so it moves records between the panel and a storage device, but it is not a value editor. Change values in the exported CSV or at the recipe screen, then let the restore carry the data back. It is the fallback when the project was built without export controls.

Why can I see recipe values on the screen but not type new ones?

The recipe control was either configured read-only or restricted by user group. One common design overlays a locked recipe control on an identical editable one, with the locked layer hidden after a sufficiently authorized login. Log in with higher access first; if edits stay blocked, the restriction sits in the project configuration and only changes there.

Will a CSV import change the recipe's parameters?

No. The CSV carries data records, which are the filled-in values. The parameters that define which fields a record holds live in the engineering project and only change there. An import fills records into the existing definition; it can neither add a field to a recipe nor remove one.

Can the edited CSV go into a TIA Portal project later?

Yes. Siemens documents exporting recipe data records from a WinCC flexible panel and importing them into a WinCC (TIA Portal) project through the import function in the Recipes area. If the station will eventually be migrated, keep the exported CSV files together with the project documentation so the records survive the move.

Keep reading

  • How-to

    How to Recover an HMI Program When the Source File Is Lost

    If an editable backup was stored on the HMI at download time, upload it and open it as a project. If the terminal holds only the compiled runtime, no upload can recreate the source: document every screen and tag behavior from the running unit, rebuild against the controller project, and convert the runtime only where the vendor documents a path.

    HMI and touchscreens

  • How-to

    Importing a PLC Tag CSV into an Existing HMI Tag Database

    A PLC tag CSV imports only when its columns match the format your HMI software documents — .csv for one package, .xlsx for another. Never import into the production project: run it on a copy, use the tag count to tell merge from replace, spot-check one revised address, and confirm each affected tag against live PLC values before download.

    HMI and touchscreens

  • Troubleshooting

    Why an HMI Edit Needs a New Runtime Download

    An HMI panel executes a compiled runtime file, not the open project, so a saved display edit never reaches the screen by itself. The edit goes live only after you build the runtime, transfer it to the terminal, launch it and verify the new build is the one running.

    HMI and touchscreens