Troubleshooting
HMI boots to black screen instead of browser favorite
Short answer
Boot-to-black on a browser-based HMI is a startup-priority conflict, not a display fault. Confirm the Browser Favorite opens the PLC page manually, enable its Startpage flag, then check whether a local application calling an empty TargetVisu is taking the foreground at boot on a Visu or Control Panel. Match firmware to the exact order number before any reset.
On this page
Your panel is not broken. When a TP600 touchscreen opens the PFC200 web visualization fine from the swipe-down menu but boots to a black screen, the display, the touch layer, the Ethernet path and the favorite's destination have all just proven themselves. What fails is the hand-off at boot: either no Browser Favorite carries the Startpage flag, or a local application calling an empty TargetVisu claims the screen first and draws nothing. Work the checks below in order. Each one ends in a decision, and most units return to unattended boot after one flag change and one clean power-cycle.
Prove the display, the network and the favorite first #
Run this sequence before touching any setting, because each step eliminates a whole fault class:
- Apply power, let the panel finish booting, then swipe down from the top edge. If the system menu appears, the display, backlight, touch layer and panel operating system are all working.
- In that menu, open the Browser Favorites entry you created for the PFC200 web visualization.
- Expect the PLC login page. If it appears, three things are proven at once: the panel-to-controller Ethernet link, the favorite's destination, and the controller actually serving the web visualization.
Decision by result. Menu and favorite both open: the fault is startup priority alone, so continue below. Favorite fails to open: the problem sits ahead of startup priority — fix the destination or the controller side first; in the CODESYS programming environment the visualization startup choice lives in the Target system settings dialog, opened from the Resources tab, so check it when a reused project refuses to serve the page. No menu at all and no touch response after a full power-cycle: display or firmware failure, and none of the steps below apply.
Read the full order number before changing anything #
Two hardware roles share the TP600 housing and they boot differently. A browser terminal runs only its browser. A Visu Panel or Control Panel also runs local CODESYS or e!COCKPIT applications. The role is coded in the order designation, not in the screen size.
Worked example. The panel in this fault is marked TP 600 10.1, order number 0762-5204. Read the complete designation from the rating plate — base number plus suffix — and apply one rule. A designation ending in /8000-00X marks a Visu Panel or Control Panel: a loaded application calling TargetVisu can take the screen at boot, so the TargetVisu check below applies and the Startpage flag is still worth setting. Any other ending marks a pure browser terminal: no local application can run and the entire fault lives in the Browser Favorites configuration. Read the plate itself, not the purchase order — suffixes are where variants hide.
That is the same identity discipline you use when you verify an obsolete HMI replacement before ordering: firmware packages and project files match the exact order number, never just the screen diagonal.
Set the Startpage flag, then power-cycle properly #
Startpage is the checkbox that marks the Browser Favorite the panel opens by default at boot. WAGO documents the panel's boot behavior and browser operation in dedicated TP 600 manuals, so match your firmware version when you consult them. The sequence itself is short:
- Open the panel's browser settings and its Browser Favorites list — the same configuration where the favorite was created.
- Select the favorite that opens the PFC200 login page.
- Enable Startpage on that favorite.
- Apply or save the panel configuration.
- Remove power, wait several seconds, restore power, and watch the complete boot. Opening the favorite from the menu does not test the startup path; only a real power-cycle does.
Decision by result. The panel boots to the login page unattended: done — confirm it again after the next power interruption. Screen still black while the menu and manual favorite work: on a /8000-00X panel that points straight at a local application; on a suffix-free browser terminal, recheck the favorite's destination and the installed firmware version before moving on.
Clear the TargetVisu that outranks the favorites #
On a Visu Panel or Control Panel, a loaded application that calls TargetVisu at startup takes the foreground ahead of Browser Favorites. An empty TargetVisu draws nothing, which is the exact fingerprint of this fault: black screen at boot, swipe-down menu alive, favorite loads fine on demand. The browser setting was never wrong — it never received the screen.
- Connect to the panel with the engineering environment used for it, CODESYS or e!COCKPIT.
- Read the application inventory from the panel itself, not from your offline project; the loaded program is what claims the boot.
- Identify any application that starts or references TargetVisu.
- If the panel is meant to be browser-only, remove or disable that application through the tool's supported workflow.
- Power-cycle and confirm the Browser Favorite now owns the boot.
Removing an application — and the reset in the next section — takes any local control program offline. If that program drives outputs on the machine, plan it as a stoppage, and back the project up before you delete anything.
Firmware and reset recovery #
Use this branch only after the checks above, and record the state you are about to risk first: full order number, installed firmware version, loaded applications, Browser Favorites settings.
Compare the installed firmware version against the package released for the exact order number and update through the engineering tool's device-update workflow if they differ. The update is a controlled step here, not a substitute for finding the TargetVisu that is actually claiming the boot. If you cannot lay hands on a matching file, getting the right firmware file for a legacy HMI panel starts from the same order number you just recorded.
If the configuration stays indeterminate after a matched firmware, reset the Visu Panel with e!COCKPIT, then rebuild the minimum: recreate the PFC200 Browser Favorite, enable Startpage, confirm the favorite still opens the login page by hand, and only then power-cycle into unattended boot. A reset removes loaded applications and retained settings — which is why the record and the backup come before it.
The decision for each ending #
After the final power-cycle, the screen itself tells you which case you are in:
| After the final power-cycle | Cause | Action |
|---|---|---|
| Boots straight to the PLC login page | Startpage set, nothing outranks the favorite | Done — confirm it survives the next power interruption |
| Black screen; menu and manual favorite still work | Startpage missing, or a local TargetVisu owns the boot on a /8000-00X panel | Set the flag; remove the local application if the panel is browser-only |
| Favorite fails even opened by hand | Destination, Ethernet, or controller-side visualization settings | Fix the network or destination first; check the Target system settings on the controller |
| No swipe-down menu at all | Display, backlight or firmware failure | Leave this procedure — recover or replace the panel |
The committed end state for a browser-only panel: the favorite opens the PLC login page by hand, Startpage is enabled on that favorite, and no local application is loaded. Power-ups then reach the web visualization with nobody swiping a menu open. If a legacy panel refuses a matched firmware or its configuration cannot be recovered, replacing the terminal is the remaining fix — a station built on industrial panel PCs that boot straight into a browser serves the same visualization without the startup fight.
Questions asked
Does the Startpage flag also log me into the PLC automatically?
No. Startpage only chooses which page the browser opens at boot. Reaching the PLC login screen proves the panel can talk to the controller and that the web visualization is being served; signing in afterwards is handled by the visualization's own user management, which is a separate setting. Automating the page and automating the login are two independent configurations.
If I delete the local application, do I lose the PLC project too?
No. The application lives on the panel, not in the PLC. Deleting it changes only the panel's own startup behavior; the PFC200 keeps its project and keeps serving the web visualization. Back up the panel-side project before deleting so you can restore it if the panel later needs its local runtime again.
Can I fix this from the swipe-down menu alone?
No. The menu is your diagnostic, not your fix: it proves the display and system are alive and lets you open the favorite by hand. The two startup-priority repairs live elsewhere. The Startpage flag is a saved panel setting, and a local TargetVisu can only be removed from the CODESYS or e!COCKPIT engineering environment.
If one of the two fixes seems to work, do I still need the other?
On a /8000-00X panel, do both in the same session. An enabled Startpage behind a resident TargetVisu still boots black, because the application takes the screen first; a deleted application with no Startpage set leaves no defined start page at all, which is the black boot you started with. Confirm the order number, clear the TargetVisu path and set the flag before you call the job closed.