IMDTouchKnowledge BaseShop main store

Troubleshooting

EasyBuilder Pro V5 to V6 Upgrade Shows HMI No Response

HMI and touchscreens Published 5 min read

Short answer

Compiling in EasyBuilder Pro V6 changed the Allen-Bradley CompactLogix EtherNet/IP driver from v1.50 to Device ID 156, v1.80, under the same ALLEN_BRADLEY_EIP_COMPACTLOGIX.e30 file name. Remove the copied V5 DLL, restore the V6 driver package, recompile and download, then verify the PLC address and one tag at a time.

On this page
  1. What changed between V5 and V6
  2. Why the copied DLL is not a fix
  3. Restore the V6 driver set
  4. Worked example: the MT8150XE to CompactLogix driver check
  5. Separate a driver fault from a network fault
  6. When to escalate
  7. Questions asked

The no-response error is the driver change, not your PLC and not your wiring. Moving the project from EasyBuilder Pro V5.01.04 to V6.05.01.565 swapped the Allen-Bradley CompactLogix EtherNet/IP driver from v1.50 to v1.80 under the same file name, and the MT8150XE stopped answering. Delete the DLL you copied from the V5 folder, restore the driver package that belongs to your V6 installation, recompile and re-download, then check the PLC address and one known tag at a time.

What changed between V5 and V6 #

The link worked until the project was compiled and downloaded from the newer software, and the only reported difference is the driver line. The V5 project showed V1.50 with the file name ALLEN_BRADLEY_EIP_COMPACTLOGIX.e30. The V6 project shows Device ID: 156, v.1.80 with the identical file name, so the selection looks unchanged while the driver behind it is not.

EasyBuilder Pro ships with a library of more than 400 PLC drivers, and those driver files belong to the software build they arrived with. The vendor's V6.08.01 release notes list new supported models and additional driver support, which shows the driver set keeps changing even between V6 builds. The package inside your installation is therefore the only one your build was released against.

Read the file name as the driver family, meaning which protocol the HMI will speak, and the device ID and version as the actual driver build. Two projects can carry the same name and still contain different driver code, which is exactly the situation on your bench.

Why the copied DLL is not a fix #

A driver is a package of files, not a single DLL. Copying the V5 file into the V6 folder leaves that folder holding pieces of two packages that were never released together, and a link that only occasionally comes up after the copy is the signature of that mixed set: the connection sometimes completes and then drops under polling.

Treat the copied file as damage rather than a workaround. Remove it, and do not edit PLC logic or network settings while a known inconsistency sits in the tool that builds your downloads. The link broke at the moment the software and driver changed, so that is where the repair starts.

The download puts a finished, compiled project on the panel, the same principle behind where compiled code resides in embedded systems, so repairing files on the PC changes nothing on the MT8150XE until you recompile and download again.

Restore the V6 driver set #

  1. Delete the copied DLL from the V6 driver folder so the folder holds only files that came with your V6 installation.
  2. Reinstall or repair EasyBuilder Pro V6 from the vendor's official download, so the driver package matches the build you compile with.
  3. Open the project in that installation, reselect the Allen-Bradley CompactLogix EtherNet/IP device, and read the driver line: it should show Device ID: 156, v.1.80, ALLEN_BRADLEY_EIP_COMPACTLOGIX.e30.
  4. Compile and download from that one workstation, so the compiled project and its driver set come from the same build.
  5. Confirm the panel runs the download you just made; verifying the HMI project version running on a panel removes an old project from the hunt.
  6. Put one simple, known controller tag on screen and watch it, nothing else.

Worked example: the MT8150XE to CompactLogix driver check #

Inputs, each taken from the machine and the two project windows:

  • Panel: MT8150XE, the unit on the machine.
  • Controller: Allen-Bradley CompactLogix, reached over Ethernet.
  • Before: EasyBuilder Pro V5.01.04, driver line V1.50, ALLEN_BRADLEY_EIP_COMPACTLOGIX.e30, the state the link worked in.
  • After: EasyBuilder Pro V6.05.01.565, driver line Device ID: 156, v.1.80, ALLEN_BRADLEY_EIP_COMPACTLOGIX.e30.
  • Symptom: every object reports no response, and the link only occasionally comes up after the V5 DLL was copied across.

Rule in words: two projects use the same driver only when the version and the device ID match. The file name alone proves nothing.

The arithmetic:

  • Version difference: 1.80 - 1.50 = 0.30. Any difference other than zero means different driver code.
  • Identity fields that changed: file name, zero; version, +0.30; device ID, added at 156. Two of the three fields differ.

Result: the V6 build polls the CompactLogix with v1.80 driver code the panel has never run against, and the copied DLL leaves the installation a mix of v1.50 and v1.80 pieces.

Decision: a version gap of any size between the project's driver line and the package in the installation, 0.30 here, makes the driver the fault to clear first. Restore the package, recompile, download, and only then move on to the network checks below.

Separate a driver fault from a network fault #

With a consistent driver set on the PC, check the path from the panel to the controller:

  • No response on every object, immediately after download: the driver line and the PLC destination address first.
  • Panel and controller both reachable, tags still dead: the endpoint fields and the tag addresses next.
  • Link comes and goes: mixed driver files, or a second device on one of the addresses.

Read the configured IP address and subnet mask from the panel and from the controller, compare them with the network plan, and check the link lights at both ends. Test reachability from a device on the same segment, and clear any duplicate address before judging the protocol. For the controller-side fields, connecting a CompactLogix PLC to an HMI over EtherNet/IP walks through the address and path settings this driver uses.

Then test tags one at a time. Confirm the address, data type and controller scope of one simple tag against the controller project, and watch it update. A failure across every object points at the connection or driver; a failure on isolated objects points at addressing. Test a write only under your site's approved control procedure, and confirm the controller receives the value you sent.

When to escalate #

If the driver line matches the V6 package, the endpoint is reachable, and one known-good tag still returns no response after a clean compile and download, stop swapping files. Open a case with Weintek support carrying both project versions, the full driver line and the captured diagnostic text; at that point the versions you recorded are the evidence, and the mixed DLL state must already be removed.

Questions asked

Does the matching e30 file name mean the v1.50 and v1.80 drivers are interchangeable?

No. The file name identifies the driver family, while the device ID and version identify the actual build. Your V5 line read V1.50 with no device ID shown; the V6 line reads Device ID 156, v.1.80. Treat any difference in those values as a different driver, and record both values exactly as displayed whenever you contact support, because they are the first thing asked for.

The link came up once after I copied the DLL. Is that good enough?

No. An occasional online state after a partial file swap is the signature of a mixed driver set, not a repair. Call it fixed only when several known tags update through repeated reads across a normal operating period, the displayed values match the controller, and the no-response error does not return. Then remove the copied file and confirm the link stays up without it.

Can I keep compiling this project in V5 for now?

Yes, if the machine must run today. A project compiled and downloaded with V5.01.04 keeps the v1.50 driver set the panel already worked with, so the link should behave as before. Treat it as a stopgap: schedule the V6 move and the driver check as one task, because the version jump is the change that broke the link.

What should I collect before opening a support case?

Both EasyBuilder Pro build numbers, the full driver line with device ID and version from each project, the panel model, the CompactLogix controller type, the IP address and subnet on both ends, the exact error text with a timestamp, and a note of everything you changed. Send the two project files as well, because support compares them directly.

Will repairing the V6 installation damage my project files?

No. A repair or reinstall replaces the software and its driver package in the program folder; the project files stay where you saved them. Copy them to a backup location first anyway, and keep the V5 project untouched as your known-good reference for comparing driver lines and addresses.

Keep reading

  • Troubleshooting

    Why an MER Download Shows No Live Data on the HMI

    The terminal runs the new MER against the communication configuration already stored on it, because the transfer skipped Replace Communications. Every tag returns Bad quality, so screens draw but show no live data. Re-download with Replace Communications checked, let the terminal reboot once, then prove the path with a heartbeat count.

    HMI and touchscreens

  • Troubleshooting

    Why C-More Shows Tag Addresses You Cannot Set in Productivity

    That address is the System ID the Productivity controller assigned to the tag, not a field you can type into Productivity Suite. View it in the Tag Database column headers, and keep the workflow one-way: create and name tags in Productivity, export, then import into C-More.

    HMI and touchscreens

  • How-to

    Adding a Modbus RTU Driver and External Variables in Vijeo Designer

    Add one Modbus RTU equipment driver on the HMI serial port, set the baud, parity and stop bits every slave shares, and give each device a unique slave address. Then create one external variable per value, pointing it at that device and its documented register with the matching data type. Mismatched serial settings or duplicate addresses show up as read timeouts, so commission one device at a time.

    HMI and touchscreens