A single-touch HMI panel reports one coordinate per contact, so shift cannot work as a held key while a letter is tapped. Use the built-in text entry keypad with its CAP key first. When the keyboard must sit on the process screen, make caps a mode: two identical screens, the shift key swaps between them, and every key keeps its position.
A shift key that works like a typewriter fails on a single-touch touch panel, and no project setting will change that. The touch screen reports one coordinate per contact, so the panel never sees shift and the letter at the same time. The fix is to stop holding anything and make caps a mode. The fastest route on most panels is the built-in keypad that pops up from a text entry object, because it carries a CAP key already. When the keyboard has to sit permanently on the process screen, build the strip twice, once in lowercase and once in capitals, and let the shift key swap between the two screens.
Why a held shift key cannot work
These panels use 4-wire or 5-wire resistive touch cells. The controller drives the film, reads one voltage and reports one X-Y position. Two contacts on the cell give one averaged point or a wandering point, so the panel cannot see shift and the letter as two events. Most capacitive kits sold for this class of panel report a single point too, and the touch controller datasheet states it.
The limit sits in the sensor, so a bigger shift button, a tighter layout or a fresh project download changes nothing. Only a controller that reports two independent points makes a held shift key possible, and that datasheet line decides it.
What you need
- The panel's programming software and the current project.
- Two screens, or one screen you can copy, so the strip exists in lowercase and in capitals.
- A text entry object, if the typed string feeds a tag or a recipe field.
- The physical panel for the final test, with the gloves the operators actually wear.
- The datasheet line giving active area and resolution, for the sizing arithmetic.
If the string already exists on a label or a work order, let a scanner type it. A scanner wired into a text entry object skips capitals completely, and USB barcode scanner setup for an HMI text entry object covers the hookup.
Cell size, spacing and press feedback decide whether the strip survives gloves on the floor. The layout rules are collected in touchscreen HMI keyboard design.
Steps
- Confirm single presses work. Touch every key of a test grid once, at each corner of the screen. If presses miss or land offset, recalibrate touch first. The screen-swap design only works on repeatable coordinates.
- Try the built-in keypad before building anything. Place a text entry object where the operator types the string and set its keypad style to Style 1. Download the project: the popup keypad includes a CAP key, so capitals need no custom logic. Stop here unless the keyboard must stay on the process screen.
- Build the lowercase strip on a base screen region at the bottom: letters A to Z, space, backspace and enter.
- Copy the strip to a second screen and change every letter to its capital. Keep each key's X-Y position identical, key for key, so a tap lands on the same target in both modes.
- Give the shift key on each screen a screen-change action to the other screen. Show the active mode clearly, for example a filled shift key on the capitals screen.
- Decide the caps behavior. For caps lock, the operator taps shift again to drop back down. For one-shot capitals, add a return action to the lowercase screen on every capital key.
- Download to the panel and test by hand. An offline simulation has no touch hardware, so it cannot show a dropped second press.
A custom numeric keypad follows the same mode logic. Linking a user-defined keypad to an HMI numeric entry object covers how the keys feed the entry object.
How to check it worked
- Tap shift, then a letter. The capital appears in the entry field and the screen shows the capitals mode.
- Tap shift again on the caps-lock design. The strip returns to lowercase.
- Type a mixed-case word quickly, one tap after another. No letter disappears between releasing one key and touching the next.
- Hold one key and tap a second. The second press is ignored. That is the single-point limit working as built, not a fault.
- Tap one key in each corner of the strip. All four respond, so no dead zone hides at the bezel edge.
If the string sets a speed, a dose or a setpoint, let the project logic check the value and require a separate confirm key before anything moves on it. A mis-typed entry must never act as a command.
Worked example: sizing a keyboard strip on a 7-inch panel
Scenario: a packing line needs a batch code typed with one capital letter, on a 7-inch panel with an 800 × 480 pixel screen. The datasheet gives an active area of 155 × 87 mm, so one pixel is 155 / 800 = 0.194 mm.
Bare hands. A 10-key row with 80 px cells is 80 × 0.194 = 15.5 mm wide, and a 52 px row height is 52 × 0.194 = 10.1 mm, which takes a bare fingertip pad of 10 to 12 mm. The 3-row strip is 3 × 52 = 156 px tall and leaves 480 - 156 = 324 px for the process graphic.
Gloves. A 20 mm cell needs 20 / 0.194 = 104 px. Ten columns of 104 px span 1040 px, wider than the 800 px screen, so a QWERTY strip cannot meet the 20 mm target here. Seven columns of 104 px fit in 728 px, but 26 letters then need 4 rows: 4 × 104 = 416 px, leaving only 480 - 416 = 64 px for the line graphic.
Decision. Bare-handed stations get the permanent two-screen strip at 15.5 mm cells. Gloved stations get no permanent strip: the text entry object calls the built-in popup keypad, and the process graphic keeps its space. One measurement, the 20 mm gloved fingertip, picks between the two designs.
Cells that still end up below the fingertip on a high-resolution panel are a layout fault of their own, and an HMI numeric keypad that is too small on a high-res panel names the causes and fixes.
Recommendation
Recommendation: Use the built-in text entry keypad with its CAP key for every string an operator types into an entry object, because it needs no custom shift logic. Build the two-screen caps strip only for a keyboard that must stay on the process screen. Size its cells to the hands on the line, about 10 to 12 mm bare and 20 mm gloved, and keep every key in the same position on both screens.
Questions
Why does holding shift and tapping a letter fail?
The touch controller reports a single X-Y position. Two contacts on an analog resistive cell give one averaged point or a wandering one, so the panel never sees two events. Hold the mode in the displayed screen, or in one bit your logic toggles to swap the strip on a single screen. Never hold it in a finger.
Can a capacitive panel in this class register two keys at once?
Read the touch controller datasheet, which states single-point or multi-touch. Resistive cells report one point. Some capacitive kits report two, which would allow a held shift, but capacitive sensing loses accuracy through work gloves, so the screen-swap mode still behaves better on a line where gloves are worn.
What if single presses are unreliable after the redesign?
Stop editing the project. Recalibrate touch, then check that the bezel is not squeezing the active area, because a pinched resistive cell reports drifting coordinates. If a known-good project still misses touches in the same spots, the film is worn. Contact the panel maker's support with the panel model and the programming software version.
Does the strip need a QWERTY layout for operators to accept it?
No. Operators who type two or three strings a shift accept an alphabetical layout faster than a cramped QWERTY. An A-to-Z grid also allows wide cells, which matters with gloves, and it puts space, backspace and the confirm key in corners where a stray tap cannot erase or send the entry.
Planning information, not legal or engineering advice. Rules differ by place: check codes and permits with your local authority and your licensed trades.