Troubleshooting
When Only One Touchscreen Icon Responds to Press
Short answer
If only one of several icons answers a press, the others are most likely status indicators: they display state but never accept input. Read each object's role in the configuration tool before touching hardware — a healthy screen shows exactly as many responsive icons as it has assigned press actions, and a silent indicator is correct behavior, not a dead touch area.
On this page
Several icons share the screen and only one answers a press: in most cases the panel is healthy and the project is doing exactly what it says. An icon configured as a status indicator will light, change color and follow a tag, but it carries no press action, so it registers zero touches by design — a three-icon screen with a single command button should show exactly one responsive icon. Two faults copy that picture: the press action sits on the wrong icon, or a touch area really is dead. A short press test plus a read of the object properties in the configuration tool separates all three, and only the last one justifies opening the glass.
Why an indicator never answers a press #
Touchscreen objects come in two families. An input control — pushbutton, selector, numeric entry — carries a press action: when the touch controller reports contact inside its rectangle, the runtime writes a value, sets a bit or runs a macro. An output indicator carries only a state mapping: it reads a tag and paints an appearance for each value. Nothing in an indicator accepts a touch, so it never fires no matter how hard you press, and that division is the basic building block of every HMI package, not a defect in one.
The glass does not decide which symbols respond; the project does. A layout seen on machine stations and door panels alike puts one command button in the middle with a status annunciator on each side, and on that screen one working icon is the correct count. Two icons ignoring every press is expected behavior when both are indicators, and a replacement panel will reproduce the same "fault." Never read an icon's shape as proof of its role: two identical bell symbols can be a button on one screen and an indicator on the next.
The press test that separates role from hardware #
Work through this at the panel with the machine available:
- Drive each indicator's source condition through its normal control path — start and stop the motor, trip and clear the alarm — and watch the icons. An icon that tracks a real condition is wired as an indicator and is supposed to ignore you. An icon that neither responds nor ever changes state points at the tag link rather than the touch layer; see Why HMI Indicators Stay Off Over Modbus RTU Polling.
- Press each icon five times, deliberately, with full finger contact, and record what answers: a beep, a flash, or the action's visible result.
- Press the silent areas and watch their neighbors. A press that fires the adjacent icon means the touch is landing offset — a registration problem, not a role problem.
- Confirm which icon the design names as the button, and compare that with the icon that actually responds.
If every silent icon tracks its condition and the one responsive icon is the intended button, the panel is healthy. The diagnosis is indicators doing their job, and no hardware gets touched.
A worked example with the arithmetic #
Example screen: three icons — Run and Fault as status indicators, Start as the command button. Five presses per icon gives 3 × 5 = 15 presses total. The two indicators ignore their presses by design: 2 × 5 = 10 presses produce nothing, and the remaining 15 − 10 = 5 should all land on Start.
| Icon | Role | Presses | Registered | Verdict |
|---|---|---|---|---|
| Run | Indicator | 5 | 0 | Correct — displays state only |
| Fault | Indicator | 5 | 0 | Correct — displays state only |
| Start | Button | 5 | 5 | Correct — carries the press action |
Five of fifteen registered is exactly what a one-button screen should produce, so nothing is broken and no glass gets ordered. Two variants change the verdict: if the five registered presses land on Run instead of Start, the press action sits on the wrong icon — a swapped assignment, fixed in software; if Start answers only 2 of 5, input is dropping intermittently and the touch layer, its cable or its controller becomes the suspect.
Reading the assignment in the configuration tool #
- Open the project that belongs to the affected panel — this machine, this screen — and save a copy before editing anything.
- Select each icon and read its properties. What decides the behavior is whether the object has any press action at all: an input section listing a write, a set-bit or a macro, momentary or latched. An indicator instead shows a tag and a mapping of tag values to appearances.
- Property names differ between packages, so judge by the object's behavior class — accepts input versus displays state — not by the label on the tab.
- Confirm the panel is running the project you are reading; an edited copy on the workstation proves nothing until the transfer completes.
An icon with no press action configured will never respond, on any glass, and that is the whole diagnosis. A power cycle will not add an input role to a display object.
Correcting a swapped assignment #
- In the saved project copy, move the press action to the icon the design names as the button, and leave the other icons' state mappings alone.
- Transfer the revised project with the documented download procedure, and check the completion result at the panel, not only in the editor.
- Repeat the press test afterward and confirm each indicator still follows its condition through its control path.
If one of the icons acknowledges alarms or resets a safety-related state, verify the corrected assignment against the machine's interlock documentation before returning the panel to service — a working button on the wrong symbol can silence an annunciation someone depends on. If the assignment is already correct and the press still does nothing, configuration elsewhere can be overriding the object; global connections are one documented cause, covered in Fixing Goto Display Buttons Locked by HMI Global Connections.
When it really is the touch layer #
Role problems follow objects; layer problems follow coordinates. A dead touch area stays silent in the same physical spot no matter which object is drawn there, and it typically fades in intermittently — 2 or 3 answers out of 5 — before going quiet. A registration fault shows as neighbor activation: press the silent icon, the one beside it fires.
Prove the layer with a test screen holding one full-screen button that toggles a visible bit, then press each corner and the center once, covering the whole active area. Every press registering means the layer is sound and any remaining silence belongs to the project. Presses that vanish in one region mean the glass, the cable or the touch controller; on a panel with bonded glass that becomes a removal job of its own, starting with How to Remove a Bonded HMI Touchscreen Glass From the Bezel.
The decision, case by case #
- Every silent icon tracks its condition and the responsive icon is the intended button: healthy panel, change nothing.
- The responsive icon is the wrong one: move the press action in the project and transfer it again.
- A correctly assigned button answers intermittently, or a fixed screen region swallows presses: touch layer, cable or controller — take the hardware path.
- Presses land on the neighboring icon: registration and calibration path, not assignment.
Questions asked
Can one tag drive both an indicator and a button on the same screen?
Yes, and it is a common pattern. A momentary button writes a bit on press; an indicator reads the same bit and shows the resulting state, so the icon confirms the command only after the controller acts on it. Keep the two roles in separate objects: the button needs the write action, the indicator needs a mapping of tag values to appearances. If the indicator never follows what the button writes, the fault is in the tag link or the controller logic, not the touch layer.
What if the operator needs one icon to show state and accept presses?
Where the interface genuinely needs one symbol to do both, use a combined object if your configuration tool offers one — often named a multistate pushbutton or a set/reset button — or place a transparent button exactly over the indicator and assign the action there. Make the combination a deliberate design decision. Converting indicators into buttons only so that every symbol answers a press adds unwanted commands and changes the interface operators were trained on.
Will touch recalibration fix icons that ignore presses?
No, not when the icons are configured as indicators. Calibration corrects where touches land, not whether an object accepts input. The symptom that does point to calibration is different: you press one icon and its neighbor fires, because drift shifts every touch by roughly the same offset. If nothing at all activates in the pressed area and the silent icons track their conditions, leave calibration alone and read the assignment.
Why does a press work but the state drop straight back off?
That is a latching problem, not a touch problem. A momentary button writes its value on press and restores it on release, so the run state has to be held by controller logic — a sealing contact or a set instruction in the PLC. A latched button holds what it writes on its own. If the icon flashes and the state disappears the instant you lift your finger, the assignment is momentary where the design intended latching, or the holding logic is missing.