Troubleshooting
EasyBuilder Pro bit lamp blink lost after upgrade
Short answer
Bit lamps that still follow the bit state but never blink after the EasyBuilder Pro update show a software-version regression, not an address or driver fault. Reinstall 6.09.02.510 from Weintek or an authorized distributor, reopen the pre-update project backup, and prove the fix with a local-memory bit toggle test before any 6.10.0x editor builds the project again.
On this page
When every bit-lamp blink in an EasyBuilder Pro project stops the moment the editor moves from 6.09.02.510 to 6.10.01.217, and returns when 6.09.02.510 is reinstalled, the fault is a software-version regression in the blink animation — not a PLC address, driver, or cable problem. That is the reported case, and the local-memory toggle test below proves it on your own bench with no controller connected. The recovery is a version-for-version rollback: reinstall 6.09.02.510 with an installer from Weintek or an authorized distributor and reopen the project backup saved before the update. Keep any 6.10.0x editor off the machine until it passes the same test, because newer builds are already published and nothing available to us documents a blink fix in them.
What the symptom pattern proves #
A bit lamp does two separate jobs: it displays the state of one bit, and it animates that display. The reported failure kills only the second job — the lamps still follow their bits, they just never blink. That combination rules out most of the usual suspects, because the address, the device connection, and the driver all sit in the state path, and the state path works.
Blink is a display property of the object itself, unlike an EasyBuilder Pro animation loop that needs an address-driven position to move at all, so a correct address proves nothing about the animation path. Read what you observe against this table before changing a single communication setting.
| Observation with a test bit | What it proves | Next move |
|---|---|---|
| Lamp follows the bit but never blinks | State delivered, animation broken | Version comparison |
| Lamp stays fixed while the monitored bit changes | Addressing, mapping, or communications fault | Fix the state path first |
| A local-memory lamp also fails to blink | No PLC, cable, or driver is in the failed path | Editor comparison only |
| Nothing changes, lamp or bit | The test stimulus reaches nothing | Fix the test before diagnosing |
Trace the bit before you touch communications #
- Open the affected lamp's properties and record the source device, the bit address, and whether that source is a controller or the HMI's own local memory.
- Watch the same address where it lives: the controller's online monitoring, or the HMI's local-memory view.
- Change the bit under controlled conditions and compare what you observe with what the lamp shows. Toggle a bit that commands nothing — a production bit can start motion or open a valve.
- Score two things separately: whether the lamp shows every state change, and whether it blinks while the bit is on.
- Move to the version comparison only after the state path is proven. Editing network settings cannot repair an animation that fails on a local-memory bit with no network attached.
The three versions and the one that matters #
Three version numbers are in play, and only one of them is your rollback target.
| Version | Role in the comparison | Decision |
|---|---|---|
| 6.09.02.510 | Blink worked before the update and returned after reinstalling it | Rollback target |
| 6.10.01.217 | Every bit-lamp blink function stopped after updating to it | Barred from this machine until it passes the toggle test |
| 6.09.02.353 | Cited separately as a tested multilingual release | Not the demonstrated fix; test it on its own if you need it |
Your rollback target is 6.09.02.510, because it is the version this exact project demonstrably worked on. An upgrade fault that sits in communications announces itself differently — polled data freezes outright — as in the EasyBuilder Pro V5 to V6 upgrade that shows HMI no response; the state-path check above is what separates that class of fault from this one.
Record the installed editor version from its version-information dialog, and the panel's model and runtime version from the device itself, so an editor change is never confused with a device-runtime change.
Worked example: 6.09.02.510 against 6.10.01.217 on one local-memory lamp #
Inputs, each with its origin:
- Editor A: EasyBuilder Pro 6.09.02.510, the version the reported case worked on before and after rollback.
- Editor B: EasyBuilder Pro 6.10.01.217, the version the reported case failed on.
- One bit lamp on an isolated test screen, source set to the HMI's local-memory bit device, blink enabled exactly as the production object has it.
- Ten toggles of that bit, one every 2 s, in each editor. The count and interval are this test's own protocol; the versions come from the reported case.
Rule in words: a build passes only if the lamp displays all ten state changes and blinks for the whole time the bit is on. Score state delivery and animation separately, each out of ten.
Arithmetic, written out:
- 6.09.02.510: 10 toggles → 10 state changes displayed → 10 blink periods → state 10/10, animation 10/10.
- 6.10.01.217: 10 toggles → 10 state changes displayed → 0 blink periods → state 10/10, animation 0/10.
Result: state delivery is 10 of 10 in both editors, while animation is 10 of 10 in one and 0 of 10 in the other, on the same object with no controller in the path.
Decision: the pass limit is 10/10 on both counts, and that limit is an example limit for this test, not a vendor specification. Any editor that delivers every state change but fewer than ten blinks fails, and it does not build the project for the machine. Reinstall 6.09.02.510 and rerun until both counts are 10/10.
Rolling back to 6.09.02.510 #
A reinstall that brings the lost function straight back is itself the diagnosis: it isolates the fault to the software layer, the same isolation at work when reinstalling ARwin restores APC910 runtime startup on that platform.
- Back up the current project files and record the panel's configuration.
- Obtain the 6.09.02.510 installer from Weintek or the authorized distributor behind your panels, never a third-party mirror.
- Reinstall, then confirm the version shown in the editor's version information.
- Open the pre-update backup. A project saved by 6.10.01.217 may not reopen cleanly in the older editor, so the backup, not the newest save, is the rollback input.
- Recheck the target HMI selection, device connection, addresses, and the affected lamp properties, then build and download under your commissioning procedure if the panel must be reloaded.
Until the vendor confirms a fix #
Keep the minimal reproduction: one screen, one local-memory lamp, the two version numbers, and the two toggle scores. Report it to Weintek or your distributor with those numbers — a reproduction that needs no PLC is the easiest kind to act on.
Weintek's download page already lists newer editors, 6.10.02.470 among them. Nothing available to us documents a blink fix in those builds, so they remain untested for this fault. When a later release gives you a reason to move up, run the same toggle test on a bench copy of the project first; a build that passes both counts has cleared this fault for your project.
Questions asked
Should I roll back to 6.09.02.353 instead, since it was recommended as a tested release?
No. That version was only cited as a separately tested multilingual release; the version this project demonstrably worked on is 6.09.02.510, and that is the rollback target. If you need the multilingual build for another reason, run the same ten-toggle local-memory test on it before it touches the machine.
Where does an older EasyBuilder Pro installer come from?
From Weintek or the authorized distributor that supplied your panels. The public download page lists current builds such as 6.10.02.470, so an older installer like 6.09.02.510 normally comes through Weintek support or your distributor on request. Do not install an editor obtained from a third-party mirror, because there is no way to verify what was changed in it.
Might the blink fault already be fixed in the 6.10.02 builds?
Possibly, and that is exactly why it stays untested rather than assumed. Nothing in the material available to us documents a blink fix in 6.10.02.470 or the builds near it. When you have a reason to move up, run the ten-toggle local-memory test on a bench copy of the project; if it scores ten of ten on both state and blink, that build clears this fault for your project.
After rolling back the editor, do I have to reload the panel?
Only if the failing behavior was observed on a downloaded application. Rebuild from the pre-update backup and download under your commissioning procedure, then repeat the toggle test on the panel itself. If the failure appeared only in simulation on the PC, the editor reinstall is the demonstrated fix and the panel need not be touched.