IMDTouchKnowledge BaseShop main store

Troubleshooting

Why the Touchscreen Number Pad Fails on One HMI Table

HMI and touchscreens Published 4 min read

Short answer

When the on-screen number pad opens on every table but one, the fault is that table's stored configuration, not the project. Script-generated column attributes corrupted the touchscreen settings in the case behind this article: clear the column attributes data, rebuild the columns manually, and verify a numeric cell opens the pad. Replacing the table object does not fix it.

On this page
  1. What one failing table tells you
  2. Two faults this is not
  3. Three checks before you change anything
  4. Why replacing the table does not help
  5. Rebuild the table by hand
  6. If the project needs generated columns
  7. Verify the repair
  8. Questions asked

When a numeric cell on one table in a Vision project will not open its on-screen number pad while every other table does, the fault sits in that table's stored configuration, not in the project. In the case behind this article, a column created by script instead of by hand had corrupted the table's touchscreen settings, so the number pad never appeared no matter what the Touchscreen Mode property said. Clearing the column attributes data and building the columns manually restored the pad. Work the three checks below in order, then rebuild; replacing the table object does not correct this failure.

What one failing table tells you #

A keypad that works everywhere except one table is the strongest clue this symptom gives you. Every table in the project shares the same project-level touchscreen mode setting, so a fault there would close the keypad on all of them at once.

Take a project with eight tables as an example: the pad opens on seven and fails on one. Those seven working tables clear the project setting and the display path in a single pass, and the arithmetic — eight tables, seven working, one failing — leaves exactly one suspect: what that table stores internally. Two tables can also render identically in the editor while their stored attributes differ, so how the columns were created matters more than how the table looks.

Two faults this is not #

If the on-screen keyboard is missing for every scripted input dialog in the project, that is a project-wide invocation problem rather than a table problem — start with fixing a missing on-screen keyboard from scripted input dialogs.

If the keypad worked until a software update, that version change is its own fault with its own fix — see why the Vision Text Area touch keyboard stops after 7.8.0.

Three checks before you change anything #

  1. Confirm the modes. Check that touchscreen mode is enabled at the project level and record the failing table's Touchscreen Mode property value before editing it. A disabled project mode fails every table, not one. If the property reads Automatic, the setting is not the cause — keep going.
  2. Hunt the override. Search bindings and scripts for anything that writes the table's Touchscreen Mode property at runtime. An override reproduces this exact symptom on one table, and if you find one, fix that logic first: a rebuilt table will not stop an override from taking effect again.
  3. Trace column creation. Open any script that builds this table's columns and check whether a column's attributes are generated rather than configured by hand. Generated column attributes are what corrupted the touchscreen settings in the case behind this article, so this is the check that finds the cause.

If checks one and two come back clean, commit to generated column data as the cause and move to the rebuild.

Why replacing the table does not help #

Replacing the table object and matching the root container and window settings changed nothing in the reported case, and the mechanism explains why. A replaced or copied table either inherits the generated column attributes or has them regenerated by the same script on its next run, so the new object lands in the same corrupted state. The fault travels with the column-generation path, not with the table object. Stop swapping objects and repair the stored data instead.

Rebuild the table by hand #

  1. Record the intended column definitions, bindings, and the table's Touchscreen Mode value so you can restore them exactly.
  2. Clear the column attributes data on the affected table.
  3. Create every column manually, including the editable numeric column, and set Touchscreen Mode back to Automatic or your intended value.
  4. Re-check the scripts and bindings from the second check: nothing may overwrite the property or regenerate the attributes behind your back.
  5. Save and test in the same runtime context where the failure appeared — same window, same container, same navigation path.

Make the edit on a development copy of the project and test against a harmless numeric tag first, so a bad rebuild cannot leave an operator unable to enter a value on a running line.

If the project needs generated columns #

When generation is a requirement rather than a habit, reintroduce it only after the manually rebuilt table has proven itself at runtime. Compare the attributes the script writes against the known-good set you just built by hand; the differences are what disable the number pad. Retest the numeric-cell interaction after every script change that rebuilds columns or their attributes — successful column creation does not prove the touchscreen settings survived it. If touchscreen mode keeps fighting the component, building a complete on-screen keyboard from bitmap HMI assets puts the keypad fully under project control.

Verify the repair #

Click a numeric cell on the rebuilt table and confirm the number pad appears. Close and reopen the saved project, then repeat the click — persistence across a save-and-reload cycle is the pass condition. Click a cell on one other table to confirm project-wide behavior is unchanged. If the pad still fails, inspect the Touchscreen Mode property at runtime and trace what writes it; at that point the override from the second check is the live suspect.

Questions asked

Could a project-level touchscreen setting fail on only one table?

No. The project's Touch Screen Mode setting and the Touch Screen Keyboard Width setting are project-wide, and the width controls both the alphanumeric keyboard and the numeric keypad. A fault there closes the keypad on every table at once. One failing table exonerates the project settings and points at the table's own stored configuration.

Does setting Touchscreen Mode to Automatic guarantee the number pad opens?

No. Automatic lets the table request the keypad when a cell takes input, but corrupted column attributes data can still disable it, and a binding or script writing the property at runtime overrides it. Click a numeric cell to test; if the property reads Automatic and the pad stays closed, clear the column attributes data and rebuild the columns by hand.

Does this failure pattern apply to Perspective sessions too?

Not as a table-attribute corruption. Perspective handles touch input through the session's Touchscreen Mode property, which presents the browser's native numeric keypad for numeric entries, so a missing keypad there is a session-property question. The single-table corruption described here is a Vision component configuration fault.

When is a manual rebuild not enough?

When a binding or script still writes the table's Touchscreen Mode property at runtime, or when a script regenerates the column attributes after your rebuild. Fix that logic first and test again; otherwise the override or the corruption simply returns on the next run.

Keep reading

  • Troubleshooting

    Why swipe scrolling fails on a touchscreen web HMI page

    When other browser windows scroll but a scrollable region on the HMI page will not swipe, the touch panel and driver are fine and the fault is layered: the browser is not delivering touch events (Chrome stopped exposing them by default), the visualization object has no gesture handling enabled, or an overlapping object swallows the swipe. Fix all three, then verify with a finger only — a mouse wheel hides the fault.

    HMI and touchscreens

  • Troubleshooting

    Fixing EasyBuilder Pro simulation failure on Windows XP

    When online and offline simulation stop working for every EasyBuilder Pro project on Windows XP after an upgrade, the installed build is the defect: 5.05.02.093 fails simulation on Windows XP while running on Windows 7, and 5.05.02.108 is the corrective release. Read the build number before touching the project, the PLC settings or EB8000.

    HMI and touchscreens

  • Troubleshooting

    Why a WinCC Advanced SQL Read Script Returns Nothing

    The read script fails for faults the working INSERT never meets: a missing space turns SELECT * FROM into FROMKayitlar, a dangling ORDER BY has no column, and MoveFirst after MoveNext pins the cursor on row one. Clear them in order: DSN visible to the runtime, SQL text valid, recordset non-empty, value inside the DInt range. Each fault masks the next.

    HMI and touchscreens