HMI and touchscreens
Earlier articles
How-to
Show an HMI Button Only When a PLC Bit Is High
Bind the button's visibility property to the Boolean PLC tag and map true/high to visible, false/low to hidden, then test both states on the panel in runtime. Combine several conditions into one tag in the PLC, and keep process permissives in the controller because a hidden button is only a display change.
Troubleshooting
Why a PanelView 300 cannot talk to a Mitsubishi FX PLC
No. A PanelView 300 runs only Allen-Bradley protocols — DF1 and DH-485 — because PanelBuilder32 offers it nothing else, and a Mitsubishi FX implements neither. Replace the terminal with a multivendor HMI that lists an FX driver, use a PanelView Plus configured for the FX, or add a protocol converter only if the PanelView 300 must stay.
Explainer
Reading raw PLC tags as diagnostics in WinCC over OPC
No. An OPC server does not limit WinCC to slave diagnostics: WinCC reads every item the server publishes, process tags included. A raw tag is only an undecoded value — match its type to the server item, decode packed words at the tag level, and drive configured alarms and displays instead of C scripts in each graphic object.
Explainer
Connecting WinCC to an external database: direct options
Yes — classic WinCC on a PC runtime reaches an external database by itself: a VBScript or C script over ODBC, the C-API, or OPC when the source publishes tags. Add a second application only when the runtime cannot open the connection or a measured retrieval misses the required cycle.
How-to
Keep WinCC dual-monitor navigation inside picture windows
Keep the 2560 x 1024 parent picture loaded as the permanent start picture and retarget each navigation button's direct connection so its open-picture action lands on the picture window object instead of the full screen. Only the selected 1280 x 1024 window changes; the other monitor and the parent layout survive every press.
Explainer
Does One Shared Script Speed Up WinCC Screen Animations
No for screen changes: opening a picture loads graphics, dynamic bindings and initial tag values, and consolidating animation scripts into one does not reduce that. Yes for steady-state runtime, but only when the grouped animations share one frame rate and phase, the trigger is scoped to the picture, and the shared counter has exactly one writer. Expect the visible running cycle to be three times the trigger interval.
Troubleshooting
Create a desktop shortcut for WinCC Runtime Advanced
The .fwx prompt means the shortcut starts the runtime executable with no project attached. Start runtime once from the engineering software so the HMI subfolder receives the generated runtime file and a working runtime shortcut, then copy that shortcut's Target into your desktop shortcut. Verify the same runtime release and license exist on any other computer before copying it there.
Troubleshooting
C-more Micro Alarm Control Setup Ignores Double-Clicks
C-more Micro binds the double-click that launches a Navigation window item to its text label, so a double-click on the icon does nothing. Aim at the words 'Alarm Control Setup' in the Function tab, or use the Setup menu's Alarm Control Setup command; reinstalling will not change anything.
How-to
Migrating an HMI serial connection from RS-232 to RS-485
Yes — when the controller's RS-485 port already runs its built-in Modbus slave, rewire the pair and switch the panel's device entry to Modbus RTU two-wire with the same 115200 baud, even parity, 8 data bits and 1 stop bit; no PLC reprogramming. Verify A/B polarity before wiring, power-cycle the controller only if you change its port settings, and accept the migration when a known register returns a valid reply.
How-to
Sharing One USB Host Port With a Powered Hub on an HMI
Yes: a four-port USB hub on the CMT-FHDX-820's single host port carries the touchscreen interface and the 32 GB DataLog stick together. Use an independently powered hub — two devices budgeted at 500 mA each draw 5.0 W, more than the 4.5 W a bus-powered hub shares — then commission touch and logging one at a time through the hub before accepting the shared link.
Troubleshooting
Why WebIQ 2.13 Publishing Hangs After a 2.12 Project Update
The never-moving publishing screen is a workspace lock on the ctrlX, not a slow transfer. Run the migration with Designer 2.13 against a 2.13 runtime, confirm the connection target with --ws-host and --ws-port, and read %APPDATA%/webiq-designer/designer.log for the active-workspace ApiError. The release is a restart of the complete ctrlX device; uninstalling Designer leaves the ctrlX workspace directory untouched.
How-to
Run WinCC 7.0 PC Runtime over a PROFIBUS card
No panel-versus-PC switch exists: launch WinCC Runtime on the PC, but the PROFIBUS link only works after the card driver is installed, the PC interface points at that card, and the WinCC connection carries the PLC's station address, rack and slot — then a moving tag value proves the link.