IMDTouchKnowledge BaseShop main store

Explainer

Why a USB Joystick Cannot Drive PanelView Tags

HMI and touchscreens Published 6 min read

Short answer

No. PanelView documentation supports USB flash drives, keyboards and mice, and the Plus 7 Performance host ports add removable drives and a printer — no game-controller class and no runtime mechanism that maps an input device to tags. The joystick belongs on PLC inputs or on a PC-based panel.

On this page
  1. What the USB ports are documented to accept
  2. The four layers between a joystick and a tag
  3. Why the mouse works and the joystick does not
  4. The runtime file cannot create the missing layer
  5. Where joystick control does belong
  6. The decision for each case
  7. Questions asked

No — a USB joystick cannot write PanelView tags through any documented path. The hardware compatibility list covering PanelView Plus 6 and 7 terminals names USB flash drives, keyboards and mice as the compatible peripherals, and the PanelView Plus 7 Performance user manual adds removable USB drives and a USB printer on the host ports. No game-controller class appears in either document, and the runtime exposes its tags to on-screen objects and to controller data, never to raw input devices. The decision follows directly: do not build project logic around a joystick on these terminals. If the machine needs joystick-style control, the input belongs on the PLC side or on a PC-based panel.

What the USB ports are documented to accept #

Two documents set the limit, and both speak in device classes rather than connector capability. The hardware compatibility list for PanelView Plus 6 and 7 terminals supports USB flash drives, keyboards and mice. The PanelView Plus 7 Performance terminals user manual states that the USB host connection supports removable USB drives and a USB printer, supplying 0.5 A at 5 V DC. A port that accepts a keyboard is not a port that accepts every HID device: the terminal is documented to receive those classes and nothing more.

USB device Documented where What the runtime receives
USB flash drive Plus 6/7 compatibility list Files for storage and runtime transfer, no input events
USB keyboard Plus 6/7 compatibility list Keystrokes, delivered to the object with focus
USB mouse Plus 6/7 compatibility list Pointer movement and clicks on the runtime's own objects
Removable drive, USB printer Plus 7 Performance user manual Storage and print output
Game controller, joystick Nowhere in either document Nothing: no documented receiver exists

The four layers between a joystick and a tag #

A joystick command reaches a tag only if four layers pass in series. Layer 1 is USB enumeration, where the device announces its class and the port powers it. Layer 2 is a driver in the terminal's Windows CE-family platform that turns device traffic into input events. Layer 3 is delivery of those events to the HMI runtime process. Layer 4 is a mechanism inside the runtime that maps an input event to a tag write. Break any one layer and the command never arrives.

Count the states to see how fragile the chain is. Each layer either passes or fails, so the combinations number 2 × 2 × 2 × 2 = 16, and exactly one of those sixteen — every layer passing — ends in a tag write. Fifteen of the sixteen states give you nothing. PanelView documentation fails layer 4 before you unpack the controller: there is no supported controller class and no documented mapping mechanism, so no amount of work on layers 1 through 3 changes the outcome.

Power deserves one calculation, because it is the layer people test first and the layer that is usually fine. The Plus 7 Performance host connection supplies 0.5 A at 5 V DC, so the port budget is 0.5 A × 5 V = 2.5 W. Take a controller whose label reads 300 mA as an illustrative input: 0.3 A × 5 V = 1.5 W, inside the budget with margin. A controller that lights up on the port has been enumerated and powered, and it still writes no tags. The failure was never at the connector.

Why the mouse works and the joystick does not #

The runtime is a receiver for exactly the input classes it draws itself. Pointer movement and clicks land on runtime objects — push buttons, lists, input fields — because those objects consume pointer events, and keystrokes land on whichever object holds focus. That design is why a USB mouse is a supported peripheral, which is also why a panel with a damaged touch surface stays usable through using a mouse and VNC when an HMI touchscreen fails. Mouse support is evidence about the mouse class and stops there.

The same logic explains why a barcode scanner works: a scanner built to enumerate as a USB keyboard inherits the keyboard's documented path and arrives as keystrokes. A joystick axis has no consuming object anywhere in the runtime. A controller programmable to emulate a keyboard delivers, at best, keystrokes to the focused field — discrete presses, never a proportional axis, and still not a tag write unless your runtime version documents a keystroke-to-action mechanism you can configure in the project.

The runtime file cannot create the missing layer #

Project programming works above layer 4, not below it. The runtime file the terminal loads is built by the engineering software and executes inside the platform's input delivery; if the platform hands the runtime no controller events, no screen object, macro or tag configuration can consume them. Before spending an hour here, record the exact catalog number and runtime version, then confirm what is running using how to find the runtime file an HMI terminal actually loads; the compatibility question is answered per model and runtime, not per connector.

If the documentation for that combination lists no controller input, stop there. Loading third-party drivers into the terminal's operating system is outside its documented operation, and even a driver that loaded would only repair layer 2 while layer 4 stayed missing. The legitimate escalation is the manufacturer's support channel, taken with the catalog number, runtime version, controller model and the result of your enumeration test.

Where joystick control does belong #

Three routes have a real input path end to end.

  • Controller side. Wire the joystick to the PLC as analog or digital inputs and drive the functions in logic — the approach walked through in connecting a PS2 mouse or joystick to a ControlLogix for motor speed control. The controller scans it like any other input, and interlocks stay where they belong.
  • PC-based HMI. If the interface itself must read a game controller, run the visualization on industrial panel PCs, where the operating system's input stack and the HMI software's documented input configuration decide the question instead of a terminal image you cannot extend.
  • On the panel. If the four joystick points are really four discrete commands, on-screen push buttons do that job with documented devices and no driver questions.

Test any new motion input against non-hazardous, observable actions first, and keep enabling and interlocks in the safety-rated control — an HMI input is not a safety device.

The decision for each case #

  • Existing PanelView, four discrete functions from a gamepad: use on-screen buttons. Do not map joystick directions to tags; the mapping layer does not exist and project code cannot add it.
  • Proportional axis control of motion: joystick on PLC inputs, interlocks in the controller, HMI for display and acknowledgment.
  • Controller already lights up on the terminal: enumeration and power have passed, which is layers 1 and at best 2. It stops at the runtime. Unplug it and route the function per the cases above.
  • Specifying the station now, with game-controller input as a requirement: choose a PC-based panel at specification time instead of discovering the missing layer after commissioning.

Questions asked

Can a gamepad that emulates a USB keyboard control PanelView tags?

Only what a keyboard delivers: keystrokes to whichever object has focus. That yields discrete button presses, never a proportional axis, and the presses still do not become tag writes unless your runtime version documents a keystroke-to-action mechanism you can configure. Verify that documentation for your exact runtime before relying on it; four D-pad points mapped to four keys is the ceiling of this approach.

Can I install a joystick driver in the terminal's Windows CE operating system?

The PanelView operating system is a Windows CE-family image shipped with the terminal, and loading third-party drivers into it is not part of its documented operation. Even a driver that loaded would only fix enumeration at layer 2; the runtime still has no mechanism mapping controller events to tags. The manufacturer's support channel, with catalog number, runtime version and controller model, is the legitimate route.

Does the PanelView USB port have enough power for a game controller?

Usually yes, and that is not the problem. The PanelView Plus 7 Performance USB host connection supplies 0.5 A at 5 V DC, a budget of 2.5 W; a controller labeled 300 mA draws 0.3 A times 5 V = 1.5 W and fits with margin. A controller that lights up has been enumerated and powered — and it still writes no tags, because the failing layer is the runtime mapping, not the port.

What is the supported way to get four joystick directions as machine functions?

Wire the joystick to the PLC as analog or digital inputs and let controller logic drive the functions, with the HMI displaying state. If the four points are only discrete commands, on-screen push buttons on the panel do the same job with documented peripherals. For an interface that must read a game controller directly, a PC-based HMI is the platform where that input stack exists.

Keep reading

  • How-to

    How to find the runtime file an HMI terminal actually loads

    The startup configuration, not the file list, selects the loaded .MER. Cycle power and press the white box in the lower-left corner (touch, firmware 5.0 or later) or hold F1 on a directly connected USB keyboard to reach the configuration screen and read the loaded runtime name. Copy every stored runtime off before deleting anything in File Management.

    HMI and touchscreens

  • Troubleshooting

    Reaching HMI Config Mode With No Startup Square

    Test the documented USB keyboard path once - Ctrl+Shift+Alt+Windows held for a few seconds - because on terminals that never show the startup square it is the supported route in. A password-protected GO TO CONFIG button is application access control: get the credentials or the project from the owner, never a reset file. If you only need the IP address, discover it on an isolated link and skip configuration mode entirely.

    HMI and touchscreens

  • How-to

    How to Enter Configuration Mode on a Touch HMI

    On a touch-only operator terminal you enter Configuration Mode by cycling power and pressing the small filled box that appears briefly in the lower-right corner during startup, while hold-both-arrow-keys instructions apply to keypad terminals with physical keys. An application button labeled GoTo Config. Screen reaches the same menu without a reboot.

    HMI and touchscreens