IMDTouchKnowledge BaseShop main store

Troubleshooting

Why COROS COMED Rejects S5L Files Before a WinCC Migration

HMI and touchscreens Published 6 min read

Short answer

The COMED error means the editor cannot decode the file's internal structure: the S5L lists came from another editor or COROS release, or were renamed. Open them in the COROS version that created them, then import through the WinCC Dynamic Wizards, reconciling every variable against the recovered source count.

On this page
  1. What the error actually says
  2. Classify the failure before touching WinCC
  3. Recover the lists in the release that wrote them
  4. Run the WinCC import
  5. Reconcile the import against the source count
  6. Field and runtime checks
  7. When no COROS release reads the files
  8. Questions asked

The COMED message is a source-read failure, not a WinCC fault. COMED names two causes — the file did not come from this editor, or a created file was renamed — which in practice means your S5L lists came from a different editor or an older COROS release than the COROS LS-B_WIN V2.11 you are opening them in, or that a filename was changed without converting the content. The data is not proven lost. Recover the lists in the COROS release that created them, then import through the WinCC Dynamic Wizards — the route Siemens documents in support entry 2566777 — and reconcile the imported count against the recovered source count before the old station is retired.

What the error actually says #

The dialog opens with an invalid-format statement and then names the two causes the editor recognizes: "Either the file has not been created with this editor or a created file has been renamed." COMED validates the file's internal structure — identifying bytes, record layout, version-specific fields — before it displays anything, and "format" here means that internal structure, not the three-letter extension.

Three things follow from that:

  • Your COROS LS-B_WIN V2.11 installation is the reader, not necessarily the writer. An older COROS release can produce files V2.11 refuses to decode, and that is the usual branch when every list from one project fails identically.
  • A renamed file keeps its original internals. Renaming rewrites the directory entry only; headers, records, and references stay in the layout of the tool that wrote them.
  • The failure happens before WinCC participates. Nothing in the WinCC project can repair a source file that COROS itself cannot decode, so source recovery is the first gate and WinCC work waits behind it.

Classify the failure before touching WinCC #

Observed result Controlling cause Decision
Every S5L file from the project fails identically in V2.11 Editor or release mismatch Identify the creating COROS release and open the lists there
Only one file of several fails Isolated origin, rename, or damage to that file Test an untouched archived copy of that one list
The files open in an older COROS environment Version compatibility confirmed Keep that environment as the conversion station and export from it
No available COROS release reads them Wrong content under the extension, or damage Retrieve another archived copy before any manual rebuild

When all three lists from one project fail with the identical message, commit to the first branch and stop debugging on the WinCC side: three independently damaged files producing one identical validation error is far less likely than a single version mismatch explaining all of them.

Recover the lists in the release that wrote them #

  1. Set the complete COROS project aside as a read-only reference and run every open, conversion, or export attempt on duplicates. This is the same discipline as reading an old HMI program before panel replacement: the source leaves the exercise intact or not at all.
  2. Identify the creating release from what the project itself records — installation notes, media labels, companion files in the project directory, the workstation's documentation. The version printed in the editor you happen to be running describes your reader, not their writer.
  3. Test one duplicate list in the candidate release before touching the rest. If it opens, that release reads the format; use it for all the lists, and never save over or upgrade the only recoverable copy.
  4. Record what the readable screen shows: list name, entry count, and any diagnostics the editor reports. That entry count is the number you will reconcile the import against.
  5. Export or stage the lists in the form the WinCC import expects, carrying every symbol, controller address, data type, description, and message assignment across with them.

Run the WinCC import #

The documented route is Siemens support entry 2566777, "Migration of COROS LS-B/FlexOS or COROS LS-B/WIN to WinCC," whose Dynamic Wizards and Import functions transfer three categories of COROS mass data: the connection list, the message list, and static image parts. The WinCC V7.5 import functions documentation describes the same wizard for importing a COROS LS-B message list. Everything else — dynamics, logic, scripts — is rebuilt in WinCC rather than converted.

  1. Import into a staging WinCC project with a backup, never directly into the production project.
  2. Work the categories in the order the wizards present them: connection list, then message list, then image parts.
  3. Resolve every exception the wizard raises — duplicate names, unsupported records, a missing connection — and record each one. An exception you resolve is a documented entry; one you never saw is a silent drop.
  4. Keep the wizard's report with the project records, because it is the input to the reconciliation.

The WinCC runtime needs a PC-class operator station, so when the old COROS terminal retires, its replacement is one of the industrial panel PCs that host HMI runtime and visualization software at the machine.

Reconcile the import against the source count #

The rule is one line: imported variables plus documented exceptions must equal the recovered source count, list by list. A wizard that finishes without a fatal error can still leave out records it could not map, so the exception list is the evidence and the exit code is not.

An illustrative example with a three-list project: the recovered lists show 86, 54, and 74 entries, so the source count is 86 + 54 + 74 = 214. The wizard imports 205 variables and lists 9 exceptions — say 4 duplicate tag names and 5 unsupported data types. The check: 205 + 9 = 214. The import is complete, and the 9 exceptions are rebuilt by hand and logged. If instead the tag browser shows 198 tags against the same 9 exceptions, then 198 + 9 = 207 and 214 − 207 = 7 entries are unaccounted for. That import is not acceptable, and the 7 get found before cutover, not after.

The count discipline is the general one for moving a tag base between platforms, the same check applied when validating HMI variables during a software migration.

Field and runtime checks #

  • Sampled identity: tag names, controller addresses, data types, and descriptions in WinCC match the recovered records line for line, on a sample drawn from every list.
  • Message behavior: sampled messages from the imported list arrive on their conditions. The message list is the operator's notification layer — a message that did not migrate is an alarm that no longer announces itself — so the WinCC station does not replace the COROS station until the message count reconciles.
  • Runtime values: known process states and controlled test changes produce the expected readings, the same pass performed when testing HMI simulation against a live PLC.

When no COROS release reads the files #

Go back to the archives first: another copy of the project, its original backup media, or the engineering workstation it came from. If no readable copy exists anywhere, the remaining routes are recovery through official Siemens support channels for legacy COROS project data, or a controlled manual rebuild from the PLC program and the surviving documentation. Commit to that order — archives, support, rebuild — and hold a manual rebuild to the same count rule: every hand-built tag maps to a source record or to a written exception.

Questions asked

Will renaming an S5L file to a different extension help COMED open it?

No. Renaming rewrites only the directory entry; the header and records keep the original layout, so the same validation fails again, and you lose the original extension as evidence of which tool wrote the file. Keep the file as it is and find the COROS release that created it.

The imported graphics appear in WinCC but nothing on them moves. Is that a fault?

No, it is the expected result. The documented route imports static image parts plus the connection and message lists; the dynamics that animated the originals are not converted. Each object's animation is rebuilt in the WinCC editor against the imported variables — the import gives you the tags, not the behavior.

Is there an automatic migration from COROS LS-B to another vendor's HMI?

No. The Dynamic Wizards route ends in WinCC, and no other manufacturer ships a converter for COROS project data. A different platform means building a new application against the recovered variable and message lists, the PLC program, and the process description — the recovered lists are still worth producing, because they become the tag database for any target.

If nothing reads the files, can I rebuild the variables from the PLC program alone?

Partly. The PLC program gives you addresses, data types, and symbols, so the tag database can be rebuilt from it. Message texts are different: they live in the HMI project, not the controller, so they survive only in the archived COROS project or the original paper documentation. Recovering a readable copy of the project matters most for the message list.

Keep reading

  • Checklist

    Checking HMI engineering software before a panel replacement

    Vijeo Designer's current line is 6.2, ending at service pack SP12 (version 6.2.12, 26 January 2024). Newer HMI panels are engineered only in Operator Terminal Expert and cannot be added to Vijeo Designer by updating it. Before ordering a replacement, record your installed version, match the target designation exactly, and let the replacement's documentation decide between a drop-in and a migration.

    HMI and touchscreens

  • How-to

    Reading an old HMI program before panel replacement

    The software family that programs the replacement panel cannot read the old one: an EA9-family release such as C-more 6.40 will not open or upload a project from an EA7-T8C. Install the EA7-family software, read the project with it, keep the original upload untouched, and convert only a copy through the documented path to the EA9-T8CL.

    HMI and touchscreens

  • Troubleshooting

    Fixing a PCS 7 OS download that fails with SQL errors

    The transfer fails because the target-side WinCC SQL databases, the CC_* copies, stay attached to SQL Server or sit in RECOVERY_PENDING, so WinCCOM cannot replace them. Close Runtime and all editors, reboot the target, remove the obsolete CC_* databases through the SQL administration layer rather than by deleting .mdf files, delete the stale CC_OM DSN, then run one clean download.

    HMI and touchscreens