IMDTouchKnowledge BaseShop main store

Explainer

How Password Security Carries From EasyBuilder 8000 to Pro

HMI and touchscreens Published 6 min read

Short answer

Weintek password management is not substantially changed in EasyBuilder Pro: a login sets an authorization state and each protected object checks it, exactly as in EasyBuilder 8000. Convert the MT8050iV2 password example on a copy, recompile it, and verify each protected object through three login states — the conversion cannot be reversed.

On this page
  1. The model that did not change
  2. Where the security settings live in EasyBuilder Pro
  3. Two routes to a reference project
  4. The conversion runs one way
  5. Reading the symptoms before touching accounts
  6. Where to attach protection
  7. Worked example: verifying the MT8050iV2 example on an MT8070iE
  8. What HMI passwords do not replace
  9. Questions asked

Weintek password management did not gain a new mechanism in EasyBuilder Pro. A login still writes an authorization state into the runtime, and every protected object still compares that state with the access it demands — the model you already run from EasyBuilder 8000. Moving from an MT8050iV2-era application to an MT8070iE programmed in EasyBuilder Pro is a configuration and verification job, not a relearn: the security settings sit on the [Security] tab of the system parameters, and two reference routes shorten the work — a password example built for the MT8050iV2 that opens and recompiles in EasyBuilder Pro, and the manufacturer's own password-management example with its explanation manual.

The model that did not change #

Authentication and authorization are separate checks, and the panel keeps them separate. Authentication asks whether the entered credentials identify an accepted user. Authorization asks whether that user may perform this specific operation. A successful login proves only the first: it does not prove that a protected button, recipe or screen carries the right requirement, and a value displaying correctly proves a working read path, not permission to write it.

Because one login state serves every object on the screen, a single password can satisfy several requirements at once. That is the arithmetic behind why one HMI password opens buttons at two security levels, and it behaves identically before and after conversion.

Where the security settings live in EasyBuilder Pro #

In EasyBuilder Pro, click [Home] » [System Parameters] and open the [Security] tab. That tab holds the user passwords and security classes, and it is where the authentication mode is chosen: General Mode, or Enhanced Security Mode enabled by selecting [Enhanced security mode] in the same tab. The EasyBuilder Pro User Manual documents the security parameters; the Product Security User Manual documents the enhanced settings in depth, so read it before switching modes. Weintek issues the manuals as versioned chapters — the download listing shows Version 6.10.02 among them — so match the chapter to your installed release. Take projects, manuals and software from Weintek or its distributors only.

Two routes to a reference project #

Route What it demonstrates What to check before reuse
Open the MT8050iV2 password example in EasyBuilder Pro and recompile it An existing EasyBuilder 8000 password implementation carrying into the new tool Target panel, screen layout, device connections, converted [Security] settings
Use the manufacturer's password-management example with its explanation manual The intended login and protection behavior, documented end to end Supported target model and the software version the example matches

Use the manufacturer's example as the primary reference, because it comes with the explanation of intended behavior. Use the MT8050iV2 example when the task is comparing familiar EasyBuilder 8000 behavior with the converted result. Neither route replaces your production project wholesale: run the example apart, identify its login control, its logout control and its protected objects, then reproduce that pattern deliberately in the MT8070iE application.

The conversion runs one way #

Weintek's documented limitation is strict: migration goes from EasyBuilder 8000 to EasyBuilder Pro only, and once a project has been converted it cannot be reverted. Convert a copy and keep the unconverted original as the fallback. The manufacturer documents the move under "How to compress, uncompress, or translate an EB8000 Project to EBPro"; after converting, recompile and read every conversion message, because a project that opens cleanly is not yet a project that migrated cleanly. A password that was simply lost is a different problem: follow recovering access to a password-protected HMI panel without a backup on the vendor's documented route rather than the converter's.

Reading the symptoms before touching accounts #

What you observe Inspect first What it separates
Credentials rejected at the login control Account and password definitions on the [Security] tab Authentication: the user is not accepted
Login accepted, operation still refused The protected object's own security setting Authorization: the login does not meet this object's requirement
Button responds visually, controller value never changes Object address, device connection, driver A write-path fault security cannot cause or fix
Access survives an operator change Logout control and session handling The previous authorization state was never cleared
A converted screen acts differently from the original Conversion messages and that object's properties A migration change, not a credential problem

Do not diagnose a refused write from the button's appearance. Watch three things separately: the active login state, whether the object's requirement is met, and whether the requested value arrives in the controller. Security explains the first two; only the third points at address, device or driver.

Where to attach protection #

Protect the operation, not only the screen. A restricted navigation button limits one path into a screen; object-level protection stops the command or data entry at the point of request, whichever route the operator takes. The same controller address can appear on several screens, so every duplicate control needs the same requirement. Deciding which objects carry a requirement at all is the same planning work as designing HMI user access levels for operators and maintenance: list the operations that need restriction first, then assign classes.

Worked example: verifying the MT8050iV2 example on an MT8070iE #

Inputs:

  • 1 password-management example project, built in EasyBuilder 8000 for the MT8050iV2 — the reference route for exactly this transition.
  • 1 production target: the MT8070iE panel, programmed in EasyBuilder Pro.
  • 2 authentication modes offered on the [Security] tab: General Mode and Enhanced Security Mode (EasyBuilder Pro User Manual).
  • 1 conversion direction: EasyBuilder 8000 to EasyBuilder Pro, with no return path (Weintek's documented conversion limitation).

Rule in words: checks per protected object = authentication modes you will ship × login states in the ladder. The ladder used here has 3 states — logged out, logged in below the object's requirement, logged in at or above it.

The arithmetic:

  • Converted example as shipped, running 1 of the 2 modes: 1 × 3 = 3 checks per protected object.
  • Qualifying both modes: 2 × 3 = 6 checks per protected object.
  • Files on disk: 1 converted working copy + 1 retained EasyBuilder 8000 original = 2, because the one-way conversion leaves no fallback otherwise.

Result: one recompile with its messages read, then 3 checks per protected object for a single-mode project, or 6 when both modes must be qualified.

Decision: treat 3 checks per protected object as the minimum after any conversion, and budget 6 per object the moment you select [Enhanced security mode] for the delivered project. Never convert the only copy.

What HMI passwords do not replace #

An HMI password gates one thing: the application running on that panel. It does not protect the controller program, whose protection is set on the controller itself — a separate discipline from how protected PLC blocks are modified with authorization — and it does not gate other interfaces to the same machine. Treat logins as access control and nothing more: interlocks belong in the controller, and a machine safety function never depends on an operator being logged in.

Questions asked

Do the passwords live in the panel or in the project?

In the project. The accounts and security classes are part of the security configuration in System Parameters, which is why a converted copy carries them and why downloading the project installs them on the panel. Change the project and you change the accounts that unit accepts; restore an older project and its older passwords come back with it.

What is the difference between General Mode and Enhanced Security Mode?

General Mode is the password-and-class model the panels have used since EasyBuilder 8000: you define passwords and security classes, and each protected object checks the logged-in state against its own requirement. Enhanced Security Mode is selected with the [Enhanced security mode] option on the same [Security] tab and brings the additional protections documented in the Product Security User Manual. The two modes are not configured identically, so read that manual before switching.

Can I reopen the converted project in EasyBuilder 8000 if something goes wrong?

No. The documented migration path runs one way, from EasyBuilder 8000 to EasyBuilder Pro, and a converted project cannot be reverted. Keep the unconverted original as the fallback and make any late corrections in the EasyBuilder Pro copy — moving the project back to the old tool is not an option.

Login succeeds but a button still refuses to operate — where do I look?

At the object, not the account. If the button carries no security requirement at all, security is not the suspect and the fault is in the address, the device or the driver. If it does carry one, compare the requirement with the level the active login actually holds. Watch the controller value, not the button animation, to tell the two cases apart.

Do these passwords protect the PLC program as well?

No. They control what the panel's application permits an operator to do. The controller's program protection is configured on the controller with its own authorization, other interfaces to the machine are unaffected, and machine safety functions stay in the safety logic or hardwired — never behind an HMI login.

Keep reading

  • Explainer

    Why one HMI password opens buttons at two security levels

    On a Delta DOP-B, security is one hierarchy from level 0 to level 7: a password registered at level 5 authorizes elements at level 5 and every level below it, including level 3. Two momentary buttons on this panel therefore cannot carry mutually exclusive passwords. Keep the ladder when a senior operator may press both buttons; move to a platform that assigns permissions per user when credentials must be exclusive.

    HMI and touchscreens

  • How-to

    Adding Flowmeter and Sensor Graphics to an EasyBuilder Pro Screen

    EasyBuilder Pro has no dedicated flowmeter or temperature-sensor object, and it does not need one. Put a picture from the Shape or Picture Library (or your own imported image) on the screen to identify the instrument, then add a separate numeric object bound to the device address for the live measurement — the picture never carries the data connection.

    HMI and touchscreens

  • Troubleshooting

    Keeping PanelView Plus User Passwords After an MER Download

    There is no download option that leaves terminal users intact: a .mer replaces the runtime's users and passwords with the project's accounts. The working path is to upload the running runtime, restore it in FactoryTalk View Studio ME 8.00 or higher, which returns the terminal's current users to the project, then edit, rebuild and download, qualified once per terminal family. If downloads must never touch accounts, manage them with FactoryTalk Administration Console instead.

    HMI and touchscreens