IMDTouchKnowledge BaseShop main store

Troubleshooting

E-Designer to Exter Project Conversion and Transfer Path

HMI and touchscreens Published 7 min read

Short answer

E-Designer cannot download to an Exter T150: the terminal accepts applications only from Information Designer. Convert the .mpa project through the maker's conversion service or a licensed Information Designer seat, verify the target, driver and objects, then export a .Dat project transfer file to USB or CF card that the T150 loads automatically. Replace the terminal with current hardware only when the terminal itself is the failing part.

On this page
  1. Can E-Designer download to an Exter T150?
  2. Which file does which job in the conversion?
  3. How do you convert the .mpa project the documented way?
  4. How does the finished project get onto the T150?
  5. What do you verify in the converted project before transfer?
  6. When is one Information Designer seat worth it for a single screen?
  7. When does replacing the terminal beat converting the project?
  8. Questions asked

Your E-Designer project can reach an Exter T150, but only through the documented conversion-and-transfer chain. E-Designer stays the editor for E-series terminals and their .mpa projects; Information Designer becomes the .cpa editor and the only tool that downloads to an Exter; the terminal itself accepts the finished application as a .Dat project transfer file loaded from a USB stick or CF card. Below are the tool-to-terminal rule, the two documented conversion routes, the export steps, the checks that keep the application honest, and the decision for one aging screen that does not justify a large spend.

Can E-Designer download to an Exter T150? #

No — E-Designer writes .mpa projects for E-series terminals and has no transfer path to the Exter family, so your Exter T150 accepts applications only from Information Designer, the editor that owns the .cpa format and every documented download route.

The split is a pairing rule, not a fault in either package: each editor transfers only to the terminal family it was built for. The same rule tells you which editor to open for any other panel in the plant, and the page Which HMI software works with which HMI panel hardware maps those pairings panel by panel.

Watch what an open project actually proves. An unlicensed Information Designer installation will open a converted project and even let you edit it; the license is what unlocks the send. A project that opens, accepts changes and saves is still a project that cannot reach the terminal.

This is also why the shortcut that circulates — a renamed extension or a quietly edited file — buys nothing. It is a licensing workaround rather than a documented route, and it ends at the same wall: the terminal accepts only what Information Designer transfers or exports. The routes below are the ones the manufacturer documents.

Which file does which job in the conversion? #

Three files matter: the E-Designer source project (.mpa), the Information Designer working project (.cpa), and the .Dat project transfer file the terminal loads — renaming one extension into another converts none of them.

File Created by Role
.mpa E-Designer Editable source for E-series terminals; input to every conversion and your only master copy
.cpa Information Designer Editable Exter project; the only format Information Designer can transfer or export
.Dat Information Designer export Project transfer file on removable media; the T150 loads it when the media is inserted

Treat the extensions as identifiers, not labels you can swap. A .mpa renamed to .cpa changes the filename only; the project structure inside still belongs to the other editor. The .cpa format trips up many teams meeting it for the first time, and the guide to opening .cpa HMI project files shows what Information Designer expects when such a project is opened.

Keep the original .mpa untouched and copied before anything else touches it. It remains the only editable record of the application and the input any future conversion run needs.

How do you convert the .mpa project the documented way? #

Two documented routes exist: the panel maker or its distributor converts the .mpa into an editable .cpa on request, and the automatic conversion in iX Developer turns an E-Designer or Information Designer application into an iX project for X2 hardware.

Route 1, keeping the T150:

  1. Copy the .mpa and archive the original; from here on you work only on copies.
  2. Request the conversion from the manufacturer or its distributor, naming the Exter T150 as the target panel.
  3. Open the returned .cpa in Information Designer and inspect it before changing anything.
  4. Run the verification checks below, then produce the deployment file as described in the transfer section.

Route 2, moving to current hardware: the automatic conversion in iX Developer takes an existing E-Designer or Information Designer application into an iX project for X2 panels, and it converts as much of the application as the tool can. Whatever it cannot convert is finished by hand in iX Developer, so the same object-level verification applies. Choose this route when the plan is new hardware, not another year on the T150.

How does the finished project get onto the T150? #

A licensed Information Designer does the sending: the documented export writes a .Dat project transfer file to external memory, and the T150 loads that file automatically from the USB stick or CF card — E-Designer never performs any part of this step.

  1. Connect the USB stick or CF card to the PC running the licensed Information Designer.
  2. Open the converted .cpa project.
  3. Run the project transfer file export — the documented menu path is Transfer/Export Project Transfer File — and select the external memory as the destination.
  4. Move the media to the T150; the terminal loads the project from it without further input.

Run the load with the machine in a safe, attended state: a failed or partial transfer can leave the operators without a usable screen on a live line.

Editing the project and exporting the transfer file both live in the licensed seat, and the page on how to obtain Information Designer for an Exter HMI covers the legitimate ways to put that tool on your bench.

What do you verify in the converted project before transfer? #

Verify four things before the first transfer: the target model set to Exter T150, the controller driver and its connection settings, a spot-check of representative screen objects, and the alarm definitions — a converted file that opens is not yet a converted application.

  • Target: open the project's terminal settings and confirm the selected model is the Exter T150, not just any panel the editor would accept.
  • Driver and connection: compare the controller driver and connection settings against the machine's documentation or the working controller; a driver or connection fault breaks every object on that connection at once, which is the fastest fault pattern to recognise.
  • Objects: pick one numeric display, one status indicator, one input field and one navigation control; compare controller address, data type, scaling and access level against the original project or the controller itself.
  • Alarms and persistent values: confirm the alarm definitions and anything that must survive a restart arrived intact.

A plausible number on a screen proves nothing: read the same value in the controller and compare before you sign the conversion off.

When is one Information Designer seat worth it for a single screen? #

Count the edits the terminal still owes you: a licensed seat wins from two changes onward because every edit and export then happens on your bench, while a single final change is cheaper as a conversion request that returns a ready .Dat.

Worked example. One Exter T150 on an older machine; three changes planned this year (new alarm text, one revised setpoint limit, one added logged value), none expected afterwards.

  • Licensed seat: 3 edits + 3 exports = 6 operations, each on your bench, run when you choose.
  • No seat: 3 change requests → 3 returned .Dat files, each waiting on someone else's queue, with zero editing capability left on site.

The arithmetic is one bench operation per change with the seat against one external round trip per change without it. Decision: two or more changes across the terminal's remaining life, buy the seat; exactly one final change, fold it into the conversion request and take the .Dat.

When does replacing the terminal beat converting the project? #

Replace the terminal when the hardware is the risk rather than the project: the Exter family is end-of-life, so a failing T150 justifies current hardware with a converted application, while a healthy terminal on a retiring machine justifies the one-shot conversion.

End-of-life is a documented status here: the manufacturer publishes the Exter and E1000 families in its end-of-life guide, and its stated migration path is the iX conversion to X2 panels described above. That route reuses the application instead of starting over, which is why it is the default when a T150 fails.

If the replacement is a PC-based operator station rather than another dedicated terminal, industrial panel PCs take the visualization runtime at the machine and talk to the same controller.

Where the keep-or-replace line sits — cut-out size, environment, support life, the state of the machine itself — is laid out in Planning an HMI terminal replacement from an older operator panel.

Decision, all cases: healthy T150 and years of machine life ahead, conversion service or licensed seat, then the .Dat export; terminal failing, migrate the converted application to current hardware through iX or move the visualization onto a PC-based panel; machine near retirement, one-shot conversion and nothing more.

Questions asked

Can I edit the converted project without buying Information Designer?

No. The .cpa project and the .Dat export are both Information Designer files, so every change after conversion either happens in a licensed seat or goes back through the conversion service as a change request. E-Designer cannot open the .cpa, and it has no download to the T150 in any case.

What should I archive alongside the original .mpa file?

The .mpa itself, unchanged, plus the controller addressing sheet and the machine's communication settings. Those papers let a future conversion, a support engineer or an E-series swap start from complete records instead of reverse-engineering addresses from a converted screen.

Can the T150 take the project over a cable instead of USB?

The route documented here is the exported .Dat project transfer file on a USB stick or CF card. Whether your Information Designer seat also offers a direct transfer to an Exter T150 depends on the installation and its connection options, so check its transfer menu once the license is active.

Does the iX conversion use the original E-Designer file?

Yes. The automatic conversion in iX Developer accepts an existing E-Designer or Information Designer application as its input and converts as much of it as possible into an iX project for X2 panels. Whatever the tool cannot convert is finished by hand, so allow checking time even on a clean run.

Keep reading

  • Troubleshooting

    Fixing an HMI Project That Fails After a Git Clone

    The clone is broken because a referenced bitmap .PLK was never committed, not because of an ignore rule. Read the HMI Output tab for the exact filename, prove the file is untracked with git check-ignore followed by git ls-files, then restore and commit it and re-test from a clean clone. Track the .tgt and .def files for the HMI BIOS version as well.

    HMI and touchscreens

  • Troubleshooting

    When an HMI project fails to open: recovery and backup

    A Vijeo Designer project that no longer opens is recovered from the editor's local project storage on the PC, not from the panel. Save never creates a portable backup: close the project in the manager, export it and keep that export as a zip after every working session, then prove the zip by importing it into a clean editor and building.

    HMI and touchscreens

  • Troubleshooting

    Why an HMI Is Detected but Project Download Fails

    Automatic LAN detection proves the panel answers on the network, not that the transfer function works. When USB and LAN both end in "failed to connect to the display unit", work the shared conditions in order: the exact system error code, supply voltage measured during the transfer, transfer settings in the engineering software, and the software version against the project target.

    HMI and touchscreens

Why FactoryTalk View Studio Cannot Save the Tag Database