IMDTouchKnowledge BaseShop main store

How-to

Reading an old HMI program before panel replacement

HMI and touchscreens Published 6 min read

Short answer

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.

On this page
  1. Why the new panel's software cannot read the old one
  2. What to have ready before you connect anything
  3. Reading the program from the EA7-T8C
  4. Keep the original upload untouched
  5. Converting the copy for the EA9-T8CL
  6. Working the two-panel EA7-T8C to EA9-T8CL swap
  7. When the EA7 software cannot read the panel
  8. Questions asked

If the panels being replaced are EA7-T8C units and the PC already runs the EA9-family software — C-more 6.40 in the swap this article answers — that release will not read the program inside the old panels. The two generations are two software families: the EA9 family carries no device entry for the EA7, so a connection attempt stops before any transfer starts. Read each old panel with the software family released for it, keep the original upload untouched, and convert only a working copy for the EA9-T8CL. The order matters, because until it has been read, the EA7 program exists in exactly one place.

Why the new panel's software cannot read the old one #

A panel generation and its programming software are a matched pair. The EA9-family software lists the panels it was released for; the EA7-T8C is not on that list, so the software sees an unknown device and the transfer never begins. A missing model in the device list is a family mismatch, not a cabling fault — the same distinction drawn in When an HMI model is missing from the programming software.

Upload does not bridge the gap. Asked whether an editable project can be pulled off a panel into newer software, one major HMI vendor's published answer is no: the engineering project cannot be uploaded from the HMI to the PC to alter it, and runtime files cannot be converted into editable ones. The read has to come from the software family that owns the panel generation — the EA7-family software for an EA7-T8C — not from a newer release that happens to be installed.

What to have ready before you connect anything #

  • The panel label: confirm the unit really is an EA7-T8C and write the model down. The whole procedure keys off that family.
  • The EA7-family programming software, installed from the panel maker's own download area in the release the maker publishes for EA7 panels — never a release guessed from a version number. For this swap the maker's licensing note is that the keycode which installed the EA9-family software also installs the EA7-family software, so one keycode covers both installations; treat that as an installation note, not as evidence that one program serves both families.
  • The transfer cable, driver and communication settings the EA7-family documentation gives for the EA7-T8C. The newer software and the label tell you none of this.
  • Any project file maintenance already holds. If a source file exists, back it up first and the panel upload becomes a cross-check instead of a rescue; the general workflow is the one in How to Upload a Program From an Old Touchscreen HMI.
  • A PC that meets the EA7 panels only through EA7-family software, with the EA9-family release closed during every connection to the old units.

Reading the program from the EA7-T8C #

Run the read panel by panel, in this order:

  1. Confirm the label reads EA7-T8C and record it, along with anything printed about project or revision.
  2. Install the EA7-family software and activate it with the keycode already used for the EA9-family installation, which the maker's licensing note allows for this case.
  3. Connect the EA7-T8C to the PC with the cable and settings the EA7-family documentation specifies, and let the software identify the panel before doing anything else.
  4. Run the upload or read function the EA7-family software provides for a connected panel, and let it finish without interruption.
  5. Save the result immediately as the original archive in the EA7-family project format, then open it and check that the screens and tags match the machine in front of you.
  6. Duplicate the archive and edit only the duplicate; from that copy, run the documented conversion into the EA9-family project format.
  7. Repeat the whole sequence on the second EA7-T8C. Two panels of the same model can carry different projects, so each gets its own read and its own archive.
  8. Never download, restore or initialize an EA7 panel during this work. The read is one-way; everything that writes to the old panel stays off the table until the replacement is running.

If a transfer test is ever unavoidable, do it with the machine out of service: a wrong or partial download to a panel running a live process can leave operators with no screens.

Keep the original upload untouched #

The original archive is the only editable record of what the panel actually runs, so it is never edited, converted or overwritten. Panel restore documentation is explicit about the stakes: confirming a restore deletes the data already in the panel's flash before anything new is written. A wrong download to the EA7-T8C therefore does not merely fail — it erases the program, and the upload archive becomes the only copy in existence. If that ever happens with no archive on hand, the remaining options are the documented recovery routes in How to Recover an HMI Program When the Source File Is Lost, not another upload attempt against a panel that no longer holds the project.

Converting the copy for the EA9-T8CL #

A successful read does not by itself give a runnable EA9 project; reading and migrating are two separate jobs. Conversion starts from the editable EA7-family project — runtime files cannot be converted — and goes through the migration path the EA9-family software documents. Review the converted result against the machine before trusting it: screens, variables, alarms and communications, the same checks as in Validating HMI variables during a software migration.

Settle the physical swap before the first EA7-T8C comes out of the door. Whether an EA9-T8CL fits the opening an EA7-T8C leaves is its own documented check, and the EA7-T8C to EA9-T8CL panel mounting compatibility guide covers it — before a panel is pulled, not after.

Working the two-panel EA7-T8C to EA9-T8CL swap #

Inputs, with their sources: 2 EA7-T8C panels to migrate and 2 EA9-T8CL replacements, one per panel (the swap this article answers); 1 installation of the EA9-family software already on the PC, C-more 6.40 (the software in hand); 1 EA7-family installation to add, activated with that same keycode (the maker's licensing note); 3 files per panel — the untouched original archive, a working copy and the converted EA9 project (the keep-the-original rule applied to a live edit).

The rule in words: one software family per panel generation, one untouched original per panel, and conversion from copies only — nothing converts until its original exists and opens.

The arithmetic: software installations, 1 existing + 1 new = 2, one per generation. Project files, 2 panels × 3 files per panel = 6 files. Untouched originals, 2 panels × 1 archive = 2. EA9-family connection attempts against an EA7 panel, 2 panels × 0 attempts = 0.

The result: a two-installation, six-file migration in which both EA7-T8C units hold an unread original archive from the moment their reads finish.

The decision: the migration holds while untouched originals = 2, one per panel still in service. Every restore, initialize or wrong download drops that count — 2 to 1 to 0 — and a panel whose original reaches 0 has no re-read left, so work on it stops and moves to source-file recovery. Above zero, continue to the next panel; at zero, recover.

When the EA7 software cannot read the panel #

A refusal is still information. If the EA7-family software cannot identify the panel or the transfer stops with an error, stop there: record the exact panel model, the software release and the error text, and do not experiment with write, initialize or conversion actions against the production panel. Upload protection and a version complaint look alike from the outside; a version complaint means the panel's firmware and the software release must match, the same file-matching discipline as in Getting the Right Firmware File for a Legacy HMI Panel. With no readable upload and no source file, the program survives only as the screens on the glass, and the recovery routes in the lost-source guide are what remains.

Questions asked

Does the EA9-family software need to be removed before installing the EA7-family software?

Nothing in the maker's licensing note for this case requires removing the EA9-family installation; the note says the keycode that activated it also installs the EA7-family software. What matters during the read is which program you open: the EA7 family for the old panel, the EA9 family for the new one.

Can one archive serve both EA7-T8C panels?

No. Reading one panel proves nothing about the other: identical model numbers do not guarantee identical projects, revisions or recipes. Give each EA7-T8C its own read and its own untouched archive, so either panel can be re-read or rebuilt later without depending on its twin.

Can the converted project be tested on the EA9-T8CL before the old panel is removed?

Yes, and that is the safe order. Convert a copy, download it to the EA9-T8CL while that panel is still out of service, and exercise its screens before the EA7-T8C is decommissioned. Keep the old panel powered and untouched until the converted project has actually run, because it remains the only editable record of the machine's interface.

What if the upload finishes but the project will not open?

Treat the archive as suspect rather than forcing it open. Compare it against a fresh read of the panel, confirm the software release is the one published for EA7 panels, and leave the panel untouched meanwhile. A completed transfer is not a verification; the archive counts only once it opens and its screens match the machine.

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

    How to Upload an HMI Program Without the Right Cable Pinout

    Upload an HG3F with the documented programming cable HG9Z-XCM1A, which runs from a 9-pin RS-232 port on the PC to Serial Interface 2 on the panel. Do not fabricate a pinout, and confirm the installed WindOI-NV2 version permits upload before you connect.

    HMI and touchscreens

  • How-to

    Making Remote HMI Access Read-Only Over RDP

    RDP forwards keyboard and pointer input, so no setting inside the remote session makes a PanelView read-only. Replace the launch chain: publish a read-only FactoryTalk ViewPoint client, or enforce view-only mode in the VNC server, then verify from the operator account that every visible control leaves the controller untouched.

    HMI and touchscreens

Why COROS COMED Rejects S5L Files Before a WinCC Migration