IMDTouchKnowledge BaseShop main store

Troubleshooting

Why HDMI Video Works but USB Touch Does Not on a Panel

Panel PCs and displays Published 7 min read

Short answer

A stable HDMI image with dead touch is a USB-path fault. Power the panel from its own supply or an externally powered hub, confirm the host enumerates a supported touch controller family, set the visualization to TargetVisu, and treat misplaced touches as a coordinate-mapping error rather than a touch failure.

On this page
  1. The picture and the touch take different cables
  2. Give the touch circuit its own power
  3. Prove the host sees the touch device
  4. Set the visualization target to TargetVisu
  5. When touches land in the wrong place
  6. Work the fault in this order
  7. Questions asked

A steady HDMI picture with dead touch is not a video fault, so stop adjusting the display. The image travels in the HDMI cable; touch coordinates travel in a separate USB cable, and the touch circuit often needs power the host will not supply. Work the USB side in this order: power the panel from its own supply or an externally powered hub, confirm the host enumerates the touch device, confirm the touch controller family is supported, and check that the visualization target receives local pointer events. Touches that register but land in the wrong place are a coordinate-mapping fault, not a touch fault.

The picture and the touch take different cables #

An industrial touch panel is three devices in one housing. The display takes video over HDMI. The touch controller enumerates on USB as a HID digitizer and reports coordinates. The power input feeds both. In this arrangement the HDMI link carries the picture and nothing else: extenders, switches and splitters on the video side cannot deliver a single touch event, and if you do switch or split the video, HDMI switch topologies for manual, auto and powered splitter designs stay on the picture side of that split.

That split is your first decision. A dark, unstable or wrong-resolution image is a video-path fault: start with troubleshooting a panel PC HMI dark screen after reboot instead. A stable, correctly scaled image that ignores your finger is a USB-path fault, and everything below is that branch.

Function Carried by What a fault here looks like
Video HDMI cable and connector Dark, unstable or mis-scaled image
Touch data USB cable from the panel touch controller Picture fine; no pointer or misplaced pointer
Panel power Own AC/DC supply or a powered USB hub Dead panel, or a touch circuit that browns out

Give the touch circuit its own power #

On the Edge Controller (752-8303) in the Opto 22 EPIC family the documented behavior is blunt: the controller will not power a panel through its USB port. The same trap exists on any host with current-limited ports. Pick one fix per panel:

  • Self-powered panel: it runs from its own AC or DC supply and the USB cable carries touch data only.
  • USB-powered panel: put an externally powered hub between the host and the touchscreen. That is what broadens the working list to almost anything with HDMI video plus USB touch.

The deciding numbers come from two specifications. A USB 2.0 data port, on a host or a self-powered hub, is rated 5 V at 500 mA: 5 V × 0.5 A = 2.5 W. A USB 3.x data port is rated 5 V at 900 mA: 5 V × 0.9 A = 4.5 W. A bus-powered hub delivers less per port; leave it out of this job.

Worked example with an illustrative label, so read your own: a small panel marked 5 V DC 0.9 A draws 5 V × 0.9 A = 4.5 W. It will not enumerate reliably on a 2.5 W USB 2.0 port, and on a 900 mA port it consumes the entire 4.5 W budget with no margin for start-up peaks. Decision: run that panel from its own DC input, or from a hub port rated for charging currents (1.5 A under USB Battery Charging 1.2), with USB carrying touch only. Also add up what else shares the hub; a hub feeding cameras and dongles is how a panel that worked on the bench dies on the machine.

One safety note: a panel with a 120 VAC supply is mains equipment, so isolate the circuit and follow the panel wiring instructions before connecting power.

Prove the host sees the touch device #

Power first, then enumeration. Open the host USB device list, Device Manager on Windows or the controller system information screen on the Edge Controller, and find the touch device. What you see picks the branch:

  • Listed, pointer follows contact: the transport is healthy; move on to the visualization target and mapping.
  • Listed, no pointer: host-side driver. On a Windows host, updating BIOS and chipset drivers has restored USB controllers that stopped enumerating devices.
  • Not listed: power, cable or port. Reseat the USB cable, try another port, repeat.
  • Port reports an over-current trip: the device draws more than the port allows or the cable is shorted. Fix power and cable before touching any setting; repeated trips with a known-good cable point to panel hardware.

On the Edge Controller the compatibility boundary is the touch controller family, not the panel model. Listed in the release notes from firmware FW24 onward, the supported display types are Waveshare, Ilitek, PixCir, Elotouch and QDtech, and FW26 has given the best reported results across panel options. A panel can pair a supported touch controller with any display assembly and power arrangement, so verify the USB identification rather than the name on the bezel. Record the installed firmware before changing anything, or a firmware update and a panel swap become indistinguishable variables. For the full setup sequence on this controller family, see configuring HDMI touchscreens on an edge controller HMI setup guide.

Use these checks when selecting a candidate panel:

Check Where to inspect Required result
Video interface Panel datasheet and connector HDMI input present
Touch interface Panel datasheet and USB device list USB carries the touch data
Touch family USB identification or panel documentation Waveshare, Ilitek, PixCir, Elotouch or QDtech on FW24 or later, or a passed test
Power source Rating label and manual Own supply, or powered hub with margin
Firmware Controller system information FW24 minimum; FW26 for best results

Set the visualization target to TargetVisu #

On the Edge Controller with a third-party touchscreen, the visualization must be TargetVisu, not WebVisu: the local target receives and applies the USB pointer events of the attached display, and the browser-oriented path does not. The trap is that WebVisu still renders pages over HDMI, so the screen looks configured while presses do nothing. Test by pressing one visible control and watching both its visual state and the controller-side tag. If the tag follows a USB mouse but never a touch, the input path is aimed at the wrong target, not the graphic.

When touches land in the wrong place #

A panel that maps accurately on Windows but misses by inches on the controller has already proven its sensor generates valid coordinates. The remaining suspects are the host touch driver, coordinate scaling, orientation and any calibration the runtime applies. Read the error shape before changing anything:

Symptom Likely branch Deciding check
No response anywhere Power, cable, enumeration or unsupported family Does the host list the touch device?
Constant offset everywhere Origin or calibration offset Compare contact and response at centre and all four corners
Error grows toward an edge Scaling or active-area mismatch Measure error at centre and opposite edges
Axes reversed or rotated Orientation or axis mapping Drag horizontally and vertically; watch pointer direction
Right on Windows, wrong here Host driver or mapping Same panel and cable on both hosts

Worked example with illustrative inputs: a 1920×1080 panel driven at 1280×720, with touch coordinates mapped onto the full 1920-wide logical screen. Every touch lands right of the finger by 1920 ÷ 1280 − 1 = 0.5 times its displayed x-position: 640 px × 0.5 = 320 px off at the displayed centre, 1280 px × 0.5 = 640 px off at the right edge, exact at the left edge. Zero error at one edge growing to the other is the scaling signature. Decision: set the controller output to the panel native 1920×1080, or scale the touch coordinates by 1280 ÷ 1920 = 0.667.

Never compensate by moving HMI objects to where touches land; that masks the error and leaves every other control wrong. Record panel resolution, output resolution, orientation, firmware and the detected device before and after the change.

Work the fault in this order #

  1. Confirm a stable, correctly scaled picture. If it is not, this is the video path, not touch.
  2. Confirm panel power: own supply, or a powered hub whose per-port budget exceeds the panel label draw.
  3. Reseat the USB touch cable and try another port. An over-current trip means fix power and cable first.
  4. Confirm the host lists the touch device.
  5. Match the detected family against Waveshare, Ilitek, PixCir, Elotouch and QDtech on FW24 or later, and record the firmware.
  6. Confirm the visualization target is TargetVisu.
  7. Touch the centre of the screen. No event anywhere: return to steps 2 through 4. Events in the wrong place: fix scaling, orientation or calibration.
  8. Retest the centre and all four corners before closing the door.

Questions asked

How far can the USB touch cable run?

The USB 2.0 specification caps a cable at about 5 m; beyond that use an active extension or place a powered hub at the panel end. Route the USB run away from drive and motor cabling, because coupled noise on a long touch line shows up as phantom touches or dropped contact.

Which panel makes have been reported working?

Hope Industrial Systems and ViewSonic panels have been reported working on this controller, with no specific model numbers documented. Hope Industrial lists panels powered from 120 VAC and 24 VDC supplies with several video input options, which removes the USB power question entirely. Any panel with HDMI video plus USB touch whose controller family the host recognizes is a candidate.

The port reports an over-current trip when the touch panel is plugged in. What does that mean?

USB ports carry over-current protection, and a trip means the attached device draws more than the port allows or its cable is shorted. Move the panel to its own supply, swap the cable, and retest on another port. If the trip repeats with a known-good cable on a self-powered panel, treat the panel as a hardware fault, not a configuration problem.

Calibration is fine on Windows but wrong on the controller. Is the panel faulty?

No. Accurate touches on a Windows PC prove the sensor produces valid coordinates; the fault sits on the host side. Windows applies its own calibration and driver stack, and none of that carries over to the controller runtime. Compare the panel native resolution with the controller video output first, because a mismatch alone produces the growing-toward-the-edge error pattern.

Keep reading

  • Troubleshooting

    Troubleshooting a Panel PC HMI Dark Screen After Reboot

    Treat the dark screen as a startup-chain fault and measure first: the 24 VDC feed at the HMI terminals under load, then the flashlight test. A faint image means the backlight path; no image anywhere with a good feed means board startup or graphics. The replaced SSD only rules out worn flash if the restored image itself was healthy.

    Panel PCs and displays

  • Troubleshooting

    Industrial PC Will Not Boot: Video, POST or SSD Fault

    A blank screen proves nothing on a CPU card with no onboard video. Yes, you can clear CMOS without a monitor, but only through the board's documented jumper and only after video works. Split the fault into power, video or SSD boot before changing parts: fit a basic ISA VGA card in a verified slot, read the BIOS, then decide between a settings reset and SSD recovery.

    Panel PCs and displays

  • Troubleshooting

    Fixing startup splash screen errors on legacy panel PCs

    Corrupted splash screens at power-up on a legacy panel PC come from two graphics-heavy programs initializing in the same boot window. Keep the HMI runtime shortcut in the Startup folder, move the remote-access utility to the desktop, and launch it by hand once the runtime has painted. Then verify flash-disk free space and RAM headroom before trusting the unit in production.

    Panel PCs and displays