Troubleshooting
E200 HMI recovery when the supplied file is a GOT project
Short answer
The E200 is an E-series terminal programmed with E-Designer, and it accepts only a native E-Designer project file with the .MPA extension. GT Designer3 opens GOT projects and can convert E-Designer projects toward the GOT, never the reverse, so recovery means obtaining the original .MPA from the machine builder or a backup, then downloading it over the documented serial cable.
On this page
- Which software actually programs an E200?
- Why does GT Designer3 not list the E200 as a GOT type?
- Can the G1 file be converted back into an .MPA?
- What exactly do you request from the machine builder?
- Where does an .MPA come from when the builder is gone?
- Which cable connects E-Designer to the E200?
- How do you transfer the restored project without making things worse?
- Questions asked
An E200 that has lost its application, with only a G1 file on hand that opens in GT Designer3 but has no path onto the terminal, points at a tool mismatch rather than a failed cable. An E200 is programmed exclusively with E-Designer from a native .MPA project, and GT Designer3 cannot download to it or turn its GOT project back into one. Recovery means obtaining the original .MPA and transferring it over the documented serial cable, not renaming the file you were sent.
Which software actually programs an E200? #
E-Designer is the only tool that builds and transfers a project to an E200, because the E200 belongs to the E-terminal family, while GT Designer3 inside GT Works3 serves GOT terminals and cannot open, target or download to one.
The two tool families look interchangeable from a distance and are not. A file that opens in GT Designer3 has therefore told you which family it belongs to before you have checked anything else. Take the terminal identity from the nameplate on the E200 itself, not from the screens inside the file, then sort the recovery into its three parts: the hardware, the E-Designer workstation, and the native project.
| What you hold | Opens in | Can it restore an E200? |
|---|---|---|
| G1 GOT project | GT Designer3 | No, it belongs to the GOT tool family |
| projectname.MPA with its projectnameFiles folder | E-Designer | Yes, once the project target is the E200 |
| G1 file renamed to .MPA | No editor converts it | No, an extension change does not translate the data |
The supplier's remark that the program runs only under GT Works3 is the same signal in words: the file they sent was built on the GOT side, and the terminal on the machine is on the E-terminal side. Decision: keep GT Designer3 for reading the file as reference and move the recovery to E-Designer.
Why does GT Designer3 not list the E200 as a GOT type? #
The E200 is absent from the GOT type list because it is not a GOT; the missing entry is the correct result, and no cable, driver or GT Works3 setting will make GT Designer3 accept the terminal as a target.
The GOT type list enumerates GOT terminals only, so the absence of the E200 says nothing is wrong with your installation, your license or your cabling; it says you are holding the wrong tool for the terminal. Changing serial ports, reinstalling drivers or hunting through GT Works3 versions cannot add a target that the tool family does not contain.
Read the nameplate before anything else. If the plate on the bezel names the terminal as an E200, the engineering path is E-Designer and the GOT list is irrelevant to this job. A genuine GOT model that still fails to appear in the type list is a different fault with its own fix, and the missing GOT type in GT Designer3 page works through one such case.
Can the G1 file be converted back into an .MPA? #
No documented converter turns a GOT project into an E-Designer .MPA; conversion runs one way, from an E-Designer project toward a GOT, so the G1 file is a dead end for recovery and renaming its extension changes nothing.
The documented converter chain runs toward the GOT: GT Converter2 prepares project data, GT Designer3 opens the result, checks it and saves it as package data for a GOT download. Every step of that documented path ends on the GOT side of the fence, and no step produces an .MPA.
Renaming is not conversion. Changing the letters after the dot relabels the file but leaves the screen objects, controller addressing and communications configuration inside untouched, and E-Designer has no way to interpret GOT data as an E-terminal project. Keep an unchanged copy of the G1 file regardless: it becomes your reference material if the native project never surfaces, as described below. Decision: stop trying to convert the G1 file and spend the effort on locating the native project.
What exactly do you request from the machine builder? #
A complete E-Designer project consists of a projectname.MPA file plus a projectnameFiles folder, or of a single ZIP that contains both, so request exactly those two components and accept a ZIP only when it holds both of them.
A project saved normally by E-Designer lands on disk as two components that share the project's name: projectname.MPA, the project itself, and projectnameFiles, the folder beside it. E-Designer can also save the project as a ZIP, and the ZIP is acceptable only because both components sit inside it.
Worked example: the builder's archive for your machine, call it PumpLine, is checked before any transfer is booked.
- The archive holds PumpLine.MPA and a PumpLineFiles folder. Count the components: 1 + 1 = 2, the project is complete and will restore in E-Designer.
- Instead there is a single PumpLine.zip. Open it: a ZIP counts as complete when its contents are the same 2 components, so 1 archive = 2 components inside means restore as well.
- The archive holds only PumpLine.MPA. That is 1 of 2 components; the restore will not complete, so ask for the missing folder before booking time on the machine.
If the builder has closed, as it had in the reported case, search old engineering workstations, backup servers and any handover archive for those two names before concluding the project is gone.
Where does an .MPA come from when the builder is gone? #
When the machine builder is unreachable and no .MPA backup exists, the remaining options are a rebuild in E-Designer using the G1 project and the machine documentation as references, or replacement of the terminal, because no tool extracts an E-Designer project from the hardware.
Start with the search: a machine that ran an E200 for years usually had an engineering PC somewhere that saved the project, so check its disks and every backup location for projectname.MPA and projectnameFiles. If the search comes up empty, the honest options are two, and neither is a converter: rebuild the application in E-Designer, using the screens and tags visible in the G1 project together with the machine's electrical drawings as the reference, or retire the terminal.
The rebuild is the same discipline described in how to recover an HMI program when the source file is lost, applied tool for tool in E-Designer. If the machine's age makes that rebuild uneconomic, industrial panel PCs take over the operator station role and put the next project change back on supported software. Decision: no source found means rebuild from reference material or replace the terminal; a conversion does not exist to rescue this case.
Which cable connects E-Designer to the E200? #
E-Designer's own help file documents the serial programming cable for E-terminals down to the pin pairs, and that document is the authority; a lead that merely fits the connectors, such as a generic null-modem cable, is not guaranteed to carry a transfer.
The terminal carries more than one serial connector, and the port used for controller communications in normal operation is not necessarily the port E-Designer transfers through. The help file in E-Designer and the terminal's cable documentation identify the programming connector and print the pin pairs, including which handshake pins are linked at each end; the cable guide published for the E-series and E1000-series terminals is the same kind of reference.
Check the hardware before blaming the software:
- With both devices powered down, ring out the cable against the documented connector views and confirm every pin pair, because transmit, receive and handshake wiring decide the link, not the shape of the shell.
- If a serial adapter sits between the PC and the cable, confirm the workstation recognizes it and note the COM port Windows assigns.
- Select that port in E-Designer's transfer dialog and use the transfer settings documented for the terminal.
The CAB 5 lead that would not communicate in the reported case shows the trap: a named cable is not a wiring specification, and a connector that fits proves nothing. The transfer itself, from port selection to download, is walked through step by step on the E200 programming with E-Designer page. Decision: communication counts as established only when E-Designer talks to the terminal through its documented programming port.
How do you transfer the restored project without making things worse? #
A restore is a download, PC to terminal, from the .MPA opened in E-Designer, and before it starts the machine goes into its approved maintenance state so a half-configured project cannot command live outputs on arrival.
The transfer dialog asks for a direction, and the words matter: retrieval copies from the terminal to the PC, download copies from the PC to the terminal, and only download restores anything here. Retrieval cannot recreate the lost application because the terminal no longer holds it; whatever it can still return belongs in a separate folder next to the known-good backups. Before writing, confirm the project's target terminal is the E200 and its controller driver matches the machine's PLC, and record both as found so a wrong guess can be traced later.
After the download, read the screen before declaring success, because the failure pattern tells you where the fault lives:
- Every value dead while the screens render points to the common communications path: the driver, the station settings or the controller cable.
- One value wrong while its neighbours update points to that object's address or data type in the project.
Decision, case by case: a native projectname.MPA with its projectnameFiles folder, a licensed E-Designer, the documented cable and a PC-to-terminal download bring the E200 back; a G1 file alone never does, so with no .MPA anywhere, rebuild from the reference material or replace the terminal.
Questions asked
Which E-Designer versions have been used for E-series transfers on Windows 10?
Walkthroughs document E-series and E1000-series uploads and downloads with E-Designer 6.13 and 7.52 running on Windows 10. Support is terminal specific, so before installing anything, check that the version you plan to use lists the E200 among its supported terminals in its own documentation.
Is it safe to install E-Designer from a link someone sends you?
No. E-Designer is licensed software, so the legitimate source is the terminal vendor or an authorized distributor. Copies passed around on public links can be outdated, incomplete or tampered with, and a build that does not match the terminal will fail the transfer in confusing ways.
What should a handover archive from the builder contain besides the project?
Alongside projectname.MPA and projectnameFiles, ask for the E-Designer version that produced the project, the cable documentation for the terminal, and the controller driver and station settings as commissioned. With those in the handover, a restore can be checked against the machine instead of hoped for.