HMI and touchscreens
Earlier articles
Selection guide
Choosing an External HMI Architecture for a Robot Controller
Connect the HMI directly over Modbus TCP only when the controller's server option is enabled, the documented register map covers every needed value, and the panel has a matching client driver. Otherwise use a PLC gateway that exchanges fieldbus I/O or TCP messages with the robot and publishes normalized tags. Direct PROFINET fits only with the fieldbus board installed and a display side that consumes cyclic data.
Selection guide
Running Third-Party HMI Software on a Marine Display Host
Keep the marine monitor: it only displays what the industrial PC host draws, so the software decision belongs on the host. Test whether the installed Infilink runtime can deliver the graphics and the smartphone or tablet access; where it cannot, select a replacement runtime with documented operating-system support, licensing and a Modbus TCP driver, and prove it on an isolated bench before rebuilding screens.
Troubleshooting
Why PanelView Error 436 Says the Remote Device Has Screen Control
Error 436 means the PLC, the remote device, still owns screen selection on the PanelView. Zero the configured Screen Number Tag in the controller and unset the control bits still set; a restart cannot clear a PLC value that stays above 0. Fix the PLC logic that returns the word to 0 so the error cannot return.
Troubleshooting
When an HMI download asks for a username and password
A username and password prompt during a project download is transfer protection working, not a failed panel. Confirm the target model and project revision, download with the owner's authorized credentials, and reserve the documented XBT GT serial recovery cable procedure for a terminal that cannot start or transfer at all.
Troubleshooting
Why WinCC Flexible Logging Fails to Create Oracle Tables
Oracle is not among the databases tested and released for WinCC flexible, so the table-definition and insert statements the runtime generates were never validated there. The startup message covers only initialization. Archive to a released database and transfer committed records to Oracle with a separate, restart-safe service.
Troubleshooting
Separating PLC scan time from real HMI communication faults
Scan time is the wrong first suspect for a lost HMI or Modbus update: a 10 ms scan cannot trip a 500 ms timeout. Commission the programming link, the PLC-to-HMI link, remote I/O and Modbus peers separately, read the error counters while the fault is present, and treat scan time as the cause only when the measured scan approaches the smallest communication timeout on the system.
Comparison
Choosing Free Modbus HMI Software for a Windows Panel PC
For a Windows panel PC that must show Modbus TCP data and alarms, Ignition Maker Edition and VTScada Lite are the only candidates with a free tier and a specific Modbus TCP claim on record. Maker Edition is documented free for non-commercial use only, so production machines bench-test VTScada Lite first or fall back to code-based AdvancedHMI.
Troubleshooting
Why a WinCC Professional Button Does Not Write to the PLC
A pressed button proves only that the screen handled the pointer event. Diagnose in order: the Professional runtime connection, the tag binding, then the command duration — a bit set on press and reset on release can be shorter than the tag's 2-second default update cycle, so the PLC never observes it. The fix is to let PLC logic clear the request after evaluating it.
Troubleshooting
Fix a Vijeo Designer project version mismatch by updating the build
The project version mismatch error means the project was saved by a newer Vijeo Designer build than the 6.3.0.103 you have installed, so copying the file locally cannot fix it. Update through Schneider Electric Software Update to a later 6.3-series build such as the reported 6.3.1.32, confirm the version inside the running application, then retest.
Troubleshooting
Connecting a Pro-face HMI to a Q02HCPU Over RS-232
A Pro-face HMI and a Mitsubishi Q02HCPU communicate over RS-232 only when four things match: the Q-series driver in the HMI project, the exact port used (CPU or module), the cable wiring from both manuals, and identical serial settings on both ends. Verify all four from the documentation before changing any configuration.
How-to
How to Make Arrow Bitmap Buttons in WinCC Touch Panels
Export each arrow as a 24-bit BMP at the button's exact pixel size, 64×64 px on a 320×240 TP177B, put it on a Button or an invisible button over a Graphic, and wire Press to SetBit and Release to ResetBit on discrete bits V100.0 to V100.3. The dot you see is a bitmap much larger than the button being clipped, not a broken import.
How-to
How to Build Two-Level Tab Navigation With Child Screens in WinCC
Build two-level navigation in WinCC with one persistent main picture, a picture window for content, and visibility-controlled child menus. Each main-tab press must set three things at once: the tab's own selected state, the matching child menu, and the initial child picture. A graphics group only bundles objects in the editor and creates no runtime navigation.