How-to
Convert an MT500 Project to EasyBuilder 8000 and Resize It
Short answer
EasyBuilder 8000 converts an MT500 .eob into a new .mtp project through the Tools menu; the converter selects the terminal with the nearest dimensions, so you must then select the real destination model on the Model tab and work through the resize dialog it triggers. Verify page geometry and live controller data before the panel returns to service.
On this page
- What do I need before converting an MT500 project?
- How does the Tools menu turn the .eob into a new project?
- Why does the converted project open with the wrong terminal?
- How do I resize the pages for the new model's resolution?
- What happens to the layout when the resolution changes?
- How do I compile and download the migrated project?
- What must pass before the panel goes back into service?
- Questions asked
EasyBuilder 8000 converts an MT500 project in one pass: start any new project, run the MT500 conversion command from the Tools menu, point it at the .eob file, and it writes a new .mtp project you open with File → Open. The converter then selects the terminal whose dimensions are closest to the original, so the next mandatory step is selecting the terminal you are actually installing, which triggers the resize dialog when the pixel dimensions differ. The steps below cover the conversion, the model change, the resize decision, and the two-level test that signs the migration off.
What do I need before converting an MT500 project? #
You need EasyBuilder 8000 or a current EasyBuilder Pro release, the original project's .eob file, and the exact destination terminal model with its pixel resolution; those three inputs decide every later step.
EasyBuilder 8000 is Weintek's single engineering tool, one program covering all of the vendor's terminal series, which is what makes this conversion possible without the old EasyBuilder 500 installation.
Protect the source before touching anything. Copy the .eob into the migration folder, mark the original read-only, and confirm it is the last revision that actually ran on the machine — when several .eob files exist, the filename and date decide, not memory. If the migration is wider than this one project, importing legacy HMI screens when migrating to a new panel covers the broader path.
How does the Tools menu turn the .eob into a new project? #
Start EasyBuilder 8000 with any throwaway project, run the MT500 conversion command from the Tools menu, select the .eob file, and the converter writes a new .mtp file — that file is the migration project.
- Launch EasyBuilder 8000 and create a new project with any terminal type; this project only exists to reach the menu.
- Open the Tools menu and select the command for converting an MT500 project; the wording follows the interface language.
- In the conversion window, select the .eob file of the MT500 project and check the filename before proceeding.
- Run the conversion; at completion a new .mtp file has been created.
- Open that .mtp with File → Open and treat it as the working copy from here on.
Edit only after step 5. Anything changed in the throwaway project stays there, because the converter writes a separate output file.
Why does the converted project open with the wrong terminal? #
The converter automatically selects the terminal with dimensions closest to the original project — a starting point, never the hardware you are installing — so read the model immediately after opening the .mtp and change it before any layout work.
The model lives in system parameters under the Edit menu, on the Model tab. Selecting the real destination there is also the trigger for the resize step, so it belongs before any object editing. If the terminal you are installing does not appear in the model list, stop at this step: a look-alike model is not a substitute for the correct target, and when an HMI model is missing from the programming software, that page covers what to check first. If the destination is a PC-based HMI rather than another terminal, that is a separate selection made on its own merits, and industrial panel PCs cover the machine-side end of that path.
How do I resize the pages for the new model's resolution? #
Select the destination model in system parameters (Edit menu, Model tab): when the new model's pixel dimensions differ from the current ones, the [Resize pop-up windows / objects] dialog opens and you choose the adaptation rules there.
Two rules from the documentation govern the geometry. The resize decision is offered exactly when the model change changes the pixel dimensions, and a base window's resolution must equal the HMI's — pages are built in the terminal's coordinate space, so you do not fix a page by dragging its edges independently of the model.
Conversion and resizing solve different problems, and passing one does not pass the other. Conversion translates the EasyBuilder 500 project into the current format; resizing adapts page geometry to the new coordinate space. A project can convert cleanly and still not fit the destination display.
What happens to the layout when the resolution changes? #
Moving an illustrative 320 × 240 pixel page to an 800 × 480 destination gives a horizontal ratio of 2.5 and a vertical ratio of 2.0, and those unequal numbers — not the physical screen size — decide how much manual layout you face.
Read both resolutions off the model information before deciding; the figures here are a labeled example, not a specification of your terminal. The arithmetic:
- Horizontal: 800 px ÷ 320 px = 2.5
- Vertical: 480 px ÷ 240 px = 2.0
- A 60 × 60 px round indicator, stretched per axis: 60 px × 2.5 = 150 px wide, 60 px × 2.0 = 120 px tall — an ellipse
- The same indicator scaled uniformly at 2.0: 60 px × 2.0 = 120 × 120 px, still a circle, and the page fills 320 px × 2.0 = 640 px of the 800 px width, leaving 800 px − 640 px = 160 px to fill by hand
| Object on the 320 × 240 page | Per-axis stretch (2.5 / 2.0) | Uniform scale (2.0) |
|---|---|---|
| 60 × 60 px round indicator | 150 × 120 px, an ellipse | 120 × 120 px, still round |
| 16 px text height | 40 px | 32 px |
| 20 px high touch button | 50 px | 40 px |
| Page width used | 800 of 800 px | 640 of 800 px |
The decision for unequal ratios: take the option that keeps proportions and re-lay out the leftover strip, rather than stretching a hand-positioned page into ellipses, distorted images and drifting spacing. Both example directions scale up, which grows a 20 px touch target to 40–50 px and text from 16 px to 32–40 px, so operation gets easier, not harder. After any resize choice, walk every page: edges, spacing between objects, pop-up windows and conditionally opened windows are where automatic scaling leaves work behind.
How do I compile and download the migrated project? #
Compile the .mtp and clear every compilation message before downloading to the terminal, and confirm first that the terminal's firmware matches what the software expects for that model.
Compilation proves project consistency, not correctness — messages about missing objects or unsupported settings must be resolved, but a clean compile says nothing about whether a display reads the right variable. Before the transfer, verify the project and the terminal identity on the download screen so an old application does not go to the wrong panel. A legacy panel that has fallen behind on firmware often blocks the download at this point; getting the right firmware file for a legacy HMI panel covers that recovery path.
What must pass before the panel goes back into service? #
Pass two levels before the panel returns to service: a geometry pass over every page and a function pass that compares displayed values and command destinations against the live controller.
- Geometry: every page, including pages reached through conditional navigation, checked for clipped controls, overlapping labels, unreadable fields and distorted graphics.
- Live values: for representative displays, the value on the panel agrees with the controller's own monitoring tool; a wrong number is a configuration fault, while a missing sign is a formatting fault, and they are fixed differently.
- Commands: each tested control writes to its intended variable, and the touch area is still practical to operate after scaling.
- Records: failures logged by page, object, expected behavior and observed behavior, so repeatable migration defects stay separated from machine-state and communication problems.
While operator commands are under test, keep the machine's outputs in a controlled state — motion inhibited or the machine isolated — so a write to the wrong variable cannot move anything.
The migration is done when both passes are clean on the destination terminal, not when the compile succeeds.
Questions asked
Does the conversion or the resize change PLC addresses?
Neither step edits addressing: the resize moves pixels only, and the conversion carries the original object configuration into the .mtp. That is exactly why a screen can look correct while writing to the wrong variable, so the acceptance pass compares representative displays and commands against the controller instead of trusting a clean compile.
Can I resize pages without changing the HMI model?
The documented route to the resize rules is the model change itself. Select a different model in system parameters on the Model tab, and when its pixel dimensions differ the resize dialog for pop-up windows and objects opens. Because a base window must match the HMI resolution, correct geometry comes from the model selection, not from dragging page edges by hand.
What if the new terminal has a lower resolution than the original?
Everything shrinks. At a 0.5 ratio a 20 px touch button becomes 10 px, hard to hit with a finger, and 16 px text drops to 8 px. Prefer a destination resolution at least equal to the original; if you must go smaller, plan to enlarge touch targets and re-lay out pages manually before commissioning.
Do I still need the .eob file after converting?
Yes. Keep the original read-only as the rollback and the behavior baseline: the .mtp is the copy you edit and recompile, while the untouched .eob answers later questions about how a screen or address originally behaved, and it is the input you would start from again if the migration is ever redone.