IMDTouchKnowledge BaseShop main store

Troubleshooting

PanelView Plus 7 ActiveX replacement fails to load

HMI and touchscreens Published 7 min read

Short answer

On a like-for-like PanelView Plus 7 swap, a matching model and firmware 12.108 do not carry ActiveX components with the production .MER. Components are file-copied and registered in the terminal's operating-system layer, so read the OS identity on both terminals first: a Windows CE 6.0 pair needs the component install and registration redone on the new terminal, while a CE-to-Windows 10 IoT move means the CE procedure does not apply and the component supplier has to confirm IoT support or you source an OS-matched terminal.

On this page
  1. Firmware rules the runtime, the OS rules the components
  2. Windows CE 6.0 and Windows 10 IoT are different targets
  3. What the second .MER can and cannot install
  4. Branch the fault by its first failure point
  5. Compare the SD card before you re-run anything
  6. Worked example: two identity reads and their decisions
  7. The decision for each case
  8. Questions asked

Your replacement PanelView Plus 7 Performance carries the same model and the same firmware 12.108 as the old unit, yet the ActiveX components will not load — because those components never travel inside the .MER or the firmware number. They are copied to the terminal and registered in its operating-system layer, and the operating system is the one identity you have not matched: the new unit reports a newer OS number, and PanelView Plus 7 hardware spans two environments, Windows CE 6.0 and Windows 10 IoT. Park the integrator's 20-page procedure for an hour and read the OS identity on both terminals first. If both units sit in the same environment, the fault is in the component install and registration, and you re-execute those steps with verification at each one. If the environments differ, the CE-targeted procedure cannot succeed, and the component needs an OS-matched source.

Firmware rules the runtime, the OS rules the components #

The firmware revision governs the FactoryTalk View ME runtime and project compatibility, not the component store, so 12.108 on both terminals cancels out as an explanation. Read the full identity on both units — product identity, hardware series, firmware revision, OS version — exactly as the identification screens display them, and photograph both screens so nothing is lost to abbreviation. Then sort what you see:

  • Model or hardware series differs: stop loading and check the platform's application and component compatibility first; the selection criteria in Planning an HMI Terminal Replacement From an Older Operator Panel cover what else has to line up before a swap works.
  • Firmware differs: confirm the runtime target version against each terminal before touching components; sourcing the right file for an older terminal is its own job, as in Getting the Right Firmware File for a Legacy HMI Panel.
  • Firmware matches and only the OS number differs: keep the OS difference as the lead suspect and move to the component inventory.

A newer OS number inside the same environment is a lead, not a verdict. Do not downgrade or reimage either terminal to erase it before you know what the component install actually writes and registers.

Windows CE 6.0 and Windows 10 IoT are different targets #

PanelView Plus terminals do not all share one execution environment. The vendor's migration literature documents the standard models as running Windows CE version 6.0, with ActiveX controls among that platform's supported features alongside FTP and a PDF reader. The OS reference for the family also lists Windows 10 IoT among the operating systems these models run, and field practice puts Windows 10 IoT on the newest Performance hardware, series B and up.

The two environments are not interchangeable for components. A control built and registered under CE 6.0 is not portable to the Windows 10 IoT environment, and the documented ActiveX support statement belongs to the CE-based models. The plain runtime is another matter: the compatibility FAQ confirms application versions 5.10, 6.00, 6.10 and 7.0 Compact run on the PanelView Plus 7 Standard, and it qualifies that yes the moment an application uses features beyond the plain runtime — which is exactly what an ActiveX-dependent project is.

Decision: read the OS line on the replacement. If it still reports a CE version, you are in the component-install case. If it reports Windows 10 IoT while the original reports CE 6.0, you are at the platform boundary: obtain the component's deployment for that environment from the integrator or component supplier, or match the environment with a CE-based terminal. Do not port CE registration steps onto the IoT unit.

What the second .MER can and cannot install #

A .MER is a compiled FactoryTalk View ME runtime: loading one places displays and objects on the terminal, and it does not register COM components. The vendor's quick-start literature shows what a genuine component install looks like on these terminals — for its example control, SBCP, the procedure copies the contents of a versioned component folder, VVCE41 in that example, and then installs and registers the control on the CE terminal. File copy plus registration, done in the terminal's OS layer.

Treat the second .MER and its 20-page procedure as an application-specific package built around that pattern. Read until you can name the step that writes files to the terminal and the step that registers them, plus each step's expected completion indication. With the editable project, inventory every ActiveX object and record the control name, version and the displays that use it; with .MER files only, get the project and deployment package from the integrator. The separate .MER may initialize the control, run a deployment helper or stage configuration files — its logic, not its extension, tells you which.

Branch the fault by its first failure point #

Record the first visible failure, not just that the procedure did not work: which runtime was selected, which display was open, what action preceded it, and the complete message text. Then branch:

  • Runtime not found or not selectable — compare storage location, filename and card folder layout with the working terminal.
  • Runtime fails before any ActiveX display opens — suspect runtime compatibility or startup configuration; read the startup diagnostic and compare the runtime target with the terminal environment.
  • Ordinary displays and communications work, only the control-bearing display fails — the component, its registration or its dependencies; re-run the registration step on its own and capture its result.
  • Loading runtime reports success, production runtime still fails — the loading action did not produce an installed, registered state; verify the files and registration on the terminal instead of trusting the completion banner.
  • Control appears but its values or actions misbehave — property configuration, data binding or communications; compare the object's properties against the working application.

If everything except the control-bearing display works, stop changing the terminal's network address — the fault sits on the component layer. One safety note: until the replacement's control is proven against the working terminal, treat its displayed values and commands as unverified, and exercise them only with the machine in a safe state.

Compare the SD card before you re-run anything #

The integrator runs everything from the SD card, and the working terminal's card was assembled over years — the replacement's copy can be partial. Take an unmodified backup of the original card and both .MER files first, so the machine can always return to its last known-good state. Then compare folder names, filenames, file sizes and timestamps against the deployment package, read the paths the procedure writes to, and confirm the replacement can read the card and write wherever the install expects to leave files. List which files the procedure is supposed to create or change, so a finished run is checked against evidence rather than against a banner.

Worked example: two identity reads and their decisions #

Your replacement reads like this:

Reading Original terminal Replacement terminal Result
Model and hardware series original identical pass — no platform question
ME runtime firmware 12.108 12.108 pass — 12.108 = 12.108
Operating system Windows CE 6.0 CE 6.0, newer OS number same environment — component install becomes the suspect

Line by line: the model matches, so the platform question is closed; firmware 12.108 equals 12.108, so the runtime layer cancels out; CE 6.0 versus CE 6.0 means the boundary is not crossed, and the newer OS number stays a lead rather than a verdict. Decision for this case: run the procedure on the replacement one step at a time, verify each copy and each registration against the working terminal's file set, and if a registration fails on the newer OS number, send the component back to its supplier for a build that supports that OS.

The case that changes the answer: the same table with Windows 10 IoT on the replacement's OS line. The boundary is then crossed, the CE package does not carry over, and the decision becomes a component deployment for the IoT environment or an OS-matched CE terminal — not another pass at the CE procedure.

The decision for each case #

  • Same model, same firmware 12.108, both terminals on CE 6.0 with a newer OS number on the new unit: the fault is in the component install and registration. Execute each step individually, verify files and registration after each, and return any failing registration to the integrator or component supplier for an OS-matched build.
  • Replacement on Windows 10 IoT, original on CE 6.0: the CE package does not carry over. Require the component's deployment for the IoT environment in writing, or use a CE-environment terminal.
  • Custom control: only the integrator's package defines its OS support. Get that requirement from them before reimaging or ordering anything.
  • Terminal not worth further bench time: a PC-based panel runs FactoryTalk View ME runtime on Windows, where components register through the standard desktop mechanism and can be serviced directly; that makes industrial panel PCs the fallback platform. On a Windows target the same job appears as registration fix for ActiveX controls that fail to add on a runtime PC.

Questions asked

Could the integrator have created custom ActiveX components for this machine?

Yes, and it is common on machine builds. You can usually tell from the control's identity: a name that matches no component vendor's catalog, files that exist only on the SD card or deployment package, and no vendor documentation for it. A custom control has exactly the operating-system support its author built and tested, so the integrator's package is the only legitimate source for the control, its dependencies and its OS requirements.

Does firmware 12.108 have anything to do with the ActiveX failure?

Only indirectly. The firmware revision governs the FactoryTalk View ME runtime and project compatibility, and both terminals report 12.108, so it cancels out. ActiveX components are installed and registered in the operating-system layer below the runtime, which is why ordinary screens behave while only the control-bearing displays fail. The OS number, and the CE-versus-IoT environment behind it, is the variable that actually differs between the two units.

How do you keep production running while the replacement is debugged?

Put the original terminal back in service if it still runs, because it already has the components installed and registered. Bench the replacement with its SD card copy, reproduce the install there step by step, and only swap it back in after the control-bearing displays behave identically to the original. That keeps the machine on known-good hardware and gives you a side-by-side comparison for every verification.

Where is ActiveX support documented for PanelView Plus terminals?

In the vendor's PanelView Plus literature. The migration application note for the PanelView Plus 6 to 7 move lists ActiveX controls among the features supported on the Windows CE 6.0 standard models, and the quick-start literature walks an install-and-register procedure for a named example control. The OS reference for the family lists the Windows versions each model range runs, including Windows 10 IoT on newer units.

Keep reading

  • How-to

    DH-485 Wiring for HMI Replacement: RS-232 Pin Map

    DH-485 is a protocol, not one electrical standard: it runs over RS-232 or RS-485. The serial version on a 9-pin PanelView port is RS-232, and a replacement HMI connects pin-for-pin on pins 2, 3 and 5 to the controller's channel 0.

    HMI and touchscreens

  • 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

    Fixing RS-232 Cable Disconnected Errors on a Replacement HMI

    Jumper RTS to CTS and DTR to DSR at the HMI end of the RS-232 cable before touching communication settings — that pair cleared 'cable is disconnected' and 'response timed out' on a replacement panel polling a Host Link PLC. The different first command, @00MS5E versus @00MM40, is not the fault: both are valid reads and the PLC answers either one passively.

    HMI and touchscreens