IMDTouchKnowledge BaseShop main store

Troubleshooting

Using a Mouse and VNC When an HMI Touchscreen Fails

HMI and touchscreens Published 5 min read

Short answer

Yes: on a Windows-based panel a wired USB mouse works directly, while on a panel running Automation Runtime you can count on keyboards and mass storage over USB, so test the mouse with the machine stopped and plan on VNC, which works only when the machine's project has the server enabled. Accept an input path only when a pointer completes a screen action, not pointer movement alone.

On this page
  1. What the Screen Tells You Before You Touch It
  2. Establish Which Environment Runs the Panel
  3. Test a Wired USB Mouse
  4. VNC: Input From a Connected Computer
  5. Worked Example: How Much of the Glass Still Answers
  6. The Decision for Each Case
  7. Questions asked

A pen-damaged touch surface does not have to stop the machine. If the panel is a Windows-based unit, a wired USB mouse plugged into a USB host port works immediately. If it is a Power Panel 500 running Automation Runtime — the usual configuration for that panel — USB support counts on keyboards and mass storage, so a mouse is tested rather than assumed, and the dependable route is a VNC session, which exists only when the machine's project has the server enabled. Test every input path with the machine stopped, and accept a path only when a pointer completes a screen action, not when it merely moves.

What the Screen Tells You Before You Touch It #

Separate a touch-layer fault from a visualization or controller fault before you add any input device. The pattern you observe picks the branch:

  • Live values, but touches fail in one physical area of the glass: display and data path work, the fault is the touch layer, and mouse or VNC applies.
  • A button changes appearance but the machine does not react: input reached the application; the problem is command binding or machine permissives, not the input device.
  • Displayed values freeze or go stale: the visualization or controller link is down, and no mouse or viewer restores it.
  • Commands appear that nobody entered: the damaged layer is generating inputs, and the panel stops being a trusted source from that moment.

Safety note: a damaged touch layer remains a live command source, so put the machine in a safe stopped state before connecting or testing anything.

Establish Which Environment Runs the Panel #

Automation Studio is the engineering tool on the desk; Automation Runtime is what executes on the panel, so "it runs Automation Studio" is not an identification. The mouse route depends on one answer: Windows on the panel, or Automation Runtime with its visualization (VC4 on this generation). Establish it from:

  • The full model number on the panel's identification label, not just the family name.
  • System or startup information, read only while navigation is still reliable.
  • The machine builder's project records, including the installed software versions.

Where the glass is too unreliable to navigate menus, use the records; do not work system dialogs through a touch layer that invents inputs.

Test a Wired USB Mouse #

  1. Stop the machine and put it in a safe state.
  2. Find a free USB host port and leave storage devices and machine interfaces undisturbed.
  3. Connect a standard wired mouse. On Automation Runtime, install nothing: USB device support is part of the platform configuration, not a driver you download, and on Windows the standard driver loads on its own.
  4. Watch for a pointer, then click a harmless page-navigation control.

The result decides the route:

  • Pointer appears and the navigation completes: usable local input, with no new network dependency.
  • Pointer appears but clicks are ignored: the visualization does not accept mouse input in this configuration; go to VNC.
  • No pointer at all: the runtime does not enumerate mice on this hardware; go to VNC.

On Automation Runtime, keyboards and mass storage are the USB device classes to count on; mice are not part of that set, so whether a pointer appears depends on the runtime version and the hardware. Connecting a standard mouse does not damage the panel, so the test costs a minute and settles the question.

VNC: Input From a Connected Computer #

VNC sends the panel's screen to a viewer program and returns keyboard and pointer input, so your mouse works on the viewing computer and the panel never needs its touch layer. One condition governs everything: the server must be enabled in the machine's project on the panel. It is not enabled by default, and connecting your laptop does not switch it on. The viewing computer needs only a VNC client program — Automation Studio plays no part in viewing.

  1. Get the panel's IP address and the authorized remote-access details from machine documentation or the responsible controls engineer.
  2. From the viewing computer, run a TCP connection test to that address on port 5900. A refused connection means nothing is listening: that is a project condition, not a viewer problem.
  3. Connect, confirm the remote screen is live, then perform one navigation click.
  4. Confirm the session permits control rather than view-only, and never let a local operator and a remote operator command at the same time.

If no server is enabled, the change lives in the project: whoever maintains it enables the server and downloads the updated application to the panel. Keep the session on the machine network, never exposed directly to the internet.

Worked Example: How Much of the Glass Still Answers #

The panel in question has a 10.4-inch touchscreen in 4:3 format; the damaged patch below is an illustrative 45 mm by 35 mm corner. Put your own measured patch into the same arithmetic.

  • Width: 10.4 in × 4/5 = 8.32 in, and 8.32 in × 25.4 mm/in = 211.3 mm.
  • Height: 10.4 in × 3/5 = 6.24 in, and 6.24 in × 25.4 mm/in = 158.5 mm.
  • Active area: 211.3 mm × 158.5 mm = 33,491 mm².
  • Dead patch: 45 mm × 35 mm = 1,575 mm².
  • Dead share: 1,575 ÷ 33,491 = 0.047, so 4.7% of the surface fails and 95.3% still answers.

The decision those numbers force: coverage is not the problem, trust is. A 45 mm patch takes out every control placed in that corner, and the same crack can register contacts nobody made. At 95.3% coverage the machine still does not run from the damaged glass — mouse or VNC carries the commands until the panel is repaired or replaced.

The Decision for Each Case #

  • Windows-based panel: connect a wired USB mouse, confirm one completed screen action, and run.
  • Automation Runtime, pointer appears: use the mouse locally; it adds no network dependency, and keep machine commands off the damaged touch layer.
  • Automation Runtime, no pointer: use VNC. With the server enabled, connect and run; with it disabled, the project change enables it, and until then a USB keyboard covers entries where the visualization accepts one — a supplement, not full operation.

While the machine runs on alternate input, get the project out of the panel: backing up an HMI with a scratched touchscreen is worth doing while part of the glass still answers. When repair stops being worth it, planning an HMI terminal replacement from an older operator panel gives the migration its order. The hardware that then takes the terminal's place at the machine is industrial panel PCs, running the visualization as a PC-based operator station.

Questions asked

Does plugging a mouse into the panel risk damaging it?

No. A standard wired mouse connected to a USB host port either gets enumerated or ignored; it does not harm the panel or the running application. Use a wired mouse rather than a wireless dongle for the test, because a dongle presents itself as a composite device and adds a variable the runtime may treat differently. Keep the machine stopped while you test.

Do I need Automation Studio on my computer to view the panel over VNC?

No. The viewing computer needs only a VNC client program connected over the machine network. Automation Studio is the engineering environment that builds the project; it becomes relevant only when the VNC server has to be enabled in the application. That change is made in the project and downloaded by whoever maintains it, usually the machine builder.

How can I tell from my desk whether the panel has a VNC server running?

Run a TCP connection test from the viewing computer to the panel's address on port 5900. A refused or timed-out connection means nothing is listening, so the project does not have the server enabled and no viewer will change that. A connection that opens tells you a server is present, and any remaining problem sits in your viewer or the network path.

The touch still works over most of the screen. Can I just carry on with it?

Not for machine commands. A cracked or pen-damaged layer can register touches nobody made, so the panel is an untrusted input source until it is replaced. In the worked example 95 percent of the surface still answered, and that is exactly the trap: coverage looks fine while one dead corner or one phantom input is enough to stop or restart a machine.

Will a USB keyboard work if the mouse does not?

On Automation Runtime, keyboards are among the USB devices you can count on, so a keyboard is worth testing for numeric entries and password fields. Check that a field has focus before typing. Accept that many touch buttons have no keyboard equivalent: a keyboard supplements mouse or VNC input, it does not replace full operation.

Keep reading

  • How-to

    Making Remote HMI Access Read-Only Over RDP

    RDP forwards keyboard and pointer input, so no setting inside the remote session makes a PanelView read-only. Replace the launch chain: publish a read-only FactoryTalk ViewPoint client, or enforce view-only mode in the VNC server, then verify from the operator account that every visible control leaves the controller untouched.

    HMI and touchscreens

  • How-to

    How One Spare HMI Panel Covers Seven Machines

    Yes. Keep one backup archive per machine on a USB stick or memory card, and restore the needed archive to the single spare panel at the panel itself. This works without WinCC flexible only if the backup transfer option was enabled when each project was downloaded; otherwise you need a PC with ProSave, and archives restore only to the same panel model.

    HMI and touchscreens

  • How-to

    How to Back Up an HMI With a Scratched Touchscreen Before Replacement

    A deep scratch usually destroys only the touch layer, while the application keeps running in the panel. Confirm the display still updates, bridge input with a USB mouse or keyboard, upload the project with the model-matched engineering software before disturbing anything, then download it to the identical replacement. If the upload is password-protected, get the credentials or the original project from the machine builder instead of guessing.

    HMI and touchscreens