IMDTouchKnowledge BaseShop main store

How-to

How to Size HMI Touch Buttons in a Dense Button Matrix

HMI and touchscreens Published 7 min read

Short answer

On a graphics HMI there is no fixed touch-cell grid: the button you draw is the touch target. Lay out all 42 elements — 32 matrix buttons, 5 feedback displays, 5 navigation keys — with at least a 6 mm gap between touch areas, keep any pixel deadband small, then press every target on the actual terminal before sign-off.

On this page
  1. The drawn button is the touch target
  2. Read two numbers from the technical data before you draw
  3. Laying out the 42 elements
  4. Sizing an 8 x 4 matrix on a 10.4-inch, 211 x 158 mm touch area
  5. Verifying every press on the terminal
  6. When to revise instead of shrinking
  7. Questions asked

On a graphics HMI terminal nothing fixes the touch cell: the button you draw is the touch target, and a per-button pixel deadband is the only thing that shrinks it. That makes the requested screen — an 8 x 4 button matrix plus 5 feedback displays plus 5 page-navigation buttons, 42 objects on a 10-inch-class display — a millimetre-budgeting job, not a cell-counting one. Read the terminal's active area and resolution from its technical data, keep at least 6 mm between touch areas, keep the deadband small, then press every target on the real terminal before sign-off. Below: the rule, the worked arithmetic for a 211 x 158 mm touch area, and the pass criteria.

The drawn button is the touch target #

PanelView standard terminals of the membrane era laid buttons out on a fixed touch-cell grid, and layouts were planned in cells. The PanelView Plus graphics generation dropped the grid. The rectangle you draw around a button object is the entire area that accepts a press, so the technical data for these terminals publishes the display active area and pixel resolution but no cell size: the cell size is whatever you draw.

Two consequences follow. First, every object on the screen draws from the same physical area — buttons, displays and page keys compete for the same millimetres, so the matrix count alone understates the layout. Second, the editor offers a per-button edge deadband measured in pixels: the operator must press closer to the center of the button for it to actuate. The deadband exists to stop one press actuating two closely spaced neighbors at once; it is not a substitute for spacing, because the pixels it consumes come straight out of the button's active area.

Read two numbers from the technical data before you draw #

Two documented numbers set the whole layout: the touch active area in millimetres, which is the drawing budget, and the pixel resolution, which converts the deadband back into physical width. Both are in the terminal's technical data sheet. Take them from the sheet for the exact model on the door — a screen with the same diagonal but a different active area changes every result that follows.

The spacing rule comes from published human-factors research on touch screens: keep at least 6 mm between touch-sensitive areas. Call that value g and apply it to every gap in the layout. Below that gap, a press aimed at one button lands close enough to actuate its neighbor, which is the classic doubled-press symptom on dense matrices. Resolution alone tells you nothing about comfort — the same pixel count sits on different physical widths — so budget in millimetres and convert to pixels only when you set the deadband.

Laying out the 42 elements #

  1. Draw the matrix as 32 individual button objects — 8 columns x 4 rows = 32 — not as one grouped graphic, so each keeps its own touch area and deadband.
  2. Reserve a horizontal strip for the 5 numeric feedback displays. They consume millimetres but accept no press, so they shrink the button rows without adding targets.
  3. Place the 5 page-navigation buttons in a single row along the bottom edge.
  4. Apply the gap rule g everywhere two touch areas meet: between matrix buttons, between matrix and displays, and around the navigation row.
  5. Give each button a small edge deadband. Its active area is drawn width minus twice the deadband, left and right, and drawn height minus twice the deadband, top and bottom — compute it, do not eyeball it.
  6. Inspect the assembled screen at final size: labels legible at arm's length, feedback values readable next to the matrix, no object overlapping another's touch area.
  7. Download to the terminal, calibrate the touch screen, then press all 42 targets — every corner, every row end, every navigation key — with the people who will run the machine.

Sizing an 8 x 4 matrix on a 10.4-inch, 211 x 158 mm touch area #

Inputs, with sources: touch active area 211 x 158 mm (8.3 x 6.2 in) and resolution 1280 x 800 px, published technical data for the 10.4-inch PanelView Plus 7 Performance touch screen; read the two numbers from your own model's data sheet, because the arithmetic reruns in seconds. Spacing rule: g, the 6 mm minimum already stated, between touch-sensitive areas. Elements: 8 x 4 = 32 matrix buttons, 5 feedback displays, 5 navigation keys.

The rules, in words: buttons across a row share whatever width the gaps leave, so button width = (active width − number of internal gaps x g) ÷ buttons across. Pixels per millimetre = horizontal pixels ÷ active width. Active width after deadband = drawn width − 2 x deadband.

Arithmetic, horizontal: 8 matrix buttons have 7 internal gaps, 7 x g = 42 mm, leaving (211 − 42) ÷ 8 = 169 ÷ 8 = 21.1 mm per matrix button. The 5 navigation keys have 4 gaps, 4 x g = 24 mm, leaving (211 − 24) ÷ 5 = 187 ÷ 5 = 37.4 mm per key.

Arithmetic, vertical: 4 matrix rows of 21.1 mm take 4 x 21.1 = 84.4 mm, plus 3 gaps x g = 18 mm, for 102.4 mm. The rest of the column is 158 − 102.4 = 55.6 mm; subtract the 2 remaining gaps of g (12 mm) and 43.6 mm is left for the display strip and the navigation row, 43.6 ÷ 2 = 21.8 mm each. Check: 84.4 + 18 + 6 + 21.8 + 6 + 21.8 = 158.0 mm — the column closes exactly on the active height.

Arithmetic, pixels: 1280 px ÷ 211 mm = 6.07 px/mm. The gap g is about 36 px; a 21.1 mm button is about 128 px wide. Each deadband pixel on one edge costs 1 ÷ 6.07 = 0.16 mm of active width, so 5 px per side removes almost 1.7 mm from a 21.1 mm button — keep the deadband to single-digit pixels unless the press test shows doubled actuations.

Row of the screen Targets across Gaps Resulting size
Matrix buttons, 4 rows 8 7 x g 21.1 x 21.1 mm each
Feedback display strip 5 readouts, no press area — 21.8 mm tall
Navigation buttons 5 4 x g 37.4 x 21.8 mm each
Column total 42 objects g between rows 158.0 mm, exactly the active height

Decision: on a 211 mm wide touch area the requested matrix returns 21.1 mm square buttons with the full gap g between every pair of targets, so build the screen as drawn and confirm it with the press test. The same arithmetic sets the cut-off: (W − 42) ÷ 8 = g solves to W = 90 mm, so a touch area narrower than 90 mm cannot hold 8 columns at the required spacing — split the matrix over two pages instead of compressing the gaps.

Verifying every press on the terminal #

Editor geometry is a plan; the terminal is the test. Before the trial, run the terminal's touch calibration — the entry steps are in How to Enter Configuration Mode on a Touch HMI — because a digitizer off by a few millimetres produces exactly the symptom a sizing mistake produces.

Then press every target and hold the layout to three pass criteria: each press actuates exactly the one object pressed; a press aimed between two buttons actuates neither; and operators reach every target, corners included, without deliberately aiming at a button's center to make it fire.

Two failures have different fixes. Edge misses that disappear when the operator aims inward mean the deadband is eating the active area — reduce it before touching the geometry. One target that never responds while the other 41 work is not a sizing problem at all; that is the single-target fault described in When Only One Touchscreen Icon Responds to Press.

Sign-off rule: the screen ships only after all 42 targets pass with the real operators. A layout the editor likes and the operators miss does not ship.

When to revise instead of shrinking #

If the budget lands below the worked example's floor for your terminal, do not shave the gaps below g and do not stack deadband to fake the missing separation — dense 4 x 4 matrices on compact terminals are exactly where missed and doubled presses concentrate first. Split the matrix over two pages and let the navigation row carry the page changes: the same elements, more room each.

If the arithmetic passes but operators still fumble the screen, the problem is hierarchy, not button millimetres: trim the screen to what the operator actually decides at that station, using the principles in Designing HMI Screens for Clear Operator Decisions.

And if the terminal itself is due for replacement, carry only the method across: element count, the gap g, the millimetre budget, the press test. The selection criteria in Planning an HMI Terminal Replacement From an Older Operator Panel start from the same technical-data numbers — active area and resolution — so read them before choosing the new screen, not after.

Questions asked

Do the five feedback displays need touch margins too?

No. A display or indicator that no one presses creates no touch target, so the gap rule applies only between the 37 pressable objects: 32 matrix buttons and 5 navigation keys. The displays still consume the same millimetre budget, which is why the worked example reserves a 21.8 mm strip for them. Keep the display strip clear of the button rows so a press aimed at a readout can never land inside a neighboring button's active area.

Can I copy the finished layout to a smaller terminal later?

No numbers carry over. Read the smaller terminal's active-area millimetres and pixel resolution from its own technical data and rerun the same budget; every button width, gap and deadband changes with them. The deadband needs re-checking first, because the same pixel value is a much larger fraction of a smaller button. The only things that transfer are the method and the minimum gap: element count, gap rule, then a press test on the new terminal.

Should touch calibration be checked before judging the layout?

Yes, and treat it as part of the test, not a fix. Calibration aligns the digitizer's reported position with the drawn geometry; off by even a few millimetres, a correct layout produces the same symptom as undersized buttons: presses that land on a neighbor or miss an edge. Recalibrate, then repeat the press test unchanged. If misses keep occurring in the same spots after calibration, the geometry or the deadband is the cause, not the touch surface.

Does a bigger deadband fix accidental double presses?

Only partially, and it costs active area. The deadband shrinks the region that accepts a press on all four sides, so a mis-press aimed between two buttons is less likely to land in either active zone. But every pixel of border comes out of the button's usable center, and an operator who presses near an edge starts to feel unreliable targets. Widen the real gap toward the minimum first; keep the deadband for the last few pixels of separation.

Keep reading

  • Troubleshooting

    Fixing Goto Display Buttons Locked by HMI Global Connections

    While the Global Connections remote display number is active — its DINT tag still holding 21 — FactoryTalk View ME disables every other form of navigation, so Goto Display buttons stay dead whether or not the popup is visible. Write 21 with a one-shot on bit A and let a startup macro on display 21 reset the tag to 0; the popup stays up and the buttons respond.

    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

  • Troubleshooting

    When Only One Touchscreen Icon Responds to Press

    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.

    HMI and touchscreens

When popup calendar buttons are too small for touch panels