Troubleshooting
Why Gas Dispenser Screens Show the Wrong Prompt or Overlapping Text
Short answer
A stale prompt such as LIFT LEVER on a lever-less handle comes from a mismatch between the installed hardware and the configured message mapping, not from a communications fault. Correct the profile first, then screen composition, and touch the communications path only where diagnostics show stale or rejected data.
On this page
- Why does the screen say "LIFT LEVER" when the handle has no lever?
- Which check tells a layout fault from a configuration fault?
- Why are the PIN asterisks hidden behind other text?
- What makes text run off the edge of the screen?
- Why does a prompt point to a soft button that is not there?
- How do I trace a message back to the module that owns it?
- How do I apply the fix without breaking the dispenser?
- When is the display module itself the problem?
- Questions asked
A dispenser screen that tells the operator to lift a lever the handle no longer has is showing a configuration mismatch, not a communications fault. The same family of displays produces three more familiar defects: PIN asterisks hidden behind other text, message text that runs past the screen edge, and prompts that point to soft buttons that do not exist. A dispenser is usually assembled from separate modules — payment, user interaction, dispensing — each with its own controller, so a software update to one function does not automatically revise instructions owned by another. The four symptom classes below each have one deciding check, and the correction order is fixed: hardware profile first, screen composition second, communications last.
Why does the screen say "LIFT LEVER" when the handle has no lever? #
The prompt comes from the dispenser's configured equipment profile or its state-to-message mapping, and it is wrong because the selected operating mechanism does not match the installed handle — a configuration mismatch that no communications work will fix.
Every visible instruction on these displays is either a static string or a string selected from a message table by an operating state. A static string has nothing live to diagnose; it is wrong because someone typed it. A state-selected string can go wrong three ways: the wrong state arrives, the binding reads the wrong state, or the message assigned to a valid state describes hardware that is not installed.
The decision: when a valid message set exists for the installed hardware, select the matching equipment profile rather than rewording one string, because the profile change aligns every related instruction and button action at once. Edit the single string only when the profile already matches the installed mechanism.
Which check tells a layout fault from a configuration fault? #
Match the symptom to one of four fault classes before changing anything — stale prompt, hidden feedback, clipped text, phantom button — because each class has its own correction path and one deciding check that separates it from the others.
| What the operator sees | Correction path | Deciding check |
|---|---|---|
| Instruction names a control that is not installed | Correct the hardware profile or the state-specific message | Compare the installed mechanism with the selected configuration and message mapping |
| PIN masking appears behind another message | Correct object layering, visibility or screen-state coordination | Confirm the input event was accepted while another object covers the feedback field |
| Text runs past the screen edge | Correct layout, font or text-container sizing | Render the longest configured message at the installed display dimensions |
| Prompt points to a missing soft button | Correct the action binding or the coordinated visibility rules | Compare the instruction, button visibility and enabled action in the same operating state |
| Input feedback never changes | Trace input handling and communications before editing graphics | Check whether the receiving module accepted the input |
A display can receive valid state information and still present the wrong instruction; the reverse also holds, with a correctly positioned object showing stale data because its binding or communications path failed. That is why every deciding check compares two things — what the physical equipment does against what the configuration says, or what one module did against what another shows.
Why are the PIN asterisks hidden behind other text? #
The keypad is probably registering the digit while a prompt, banner or transition object covers the masking field, so treat it as a screen-composition fault and confirm input acceptance before touching any graphics.
The module that accepts keypad input is often not the module that renders the masked-entry object, and the two can disagree in both directions: the digit is accepted while the feedback stays covered, or the entry animation advances while the payment module never received the keypress. Use the approved service or test workflow for this check, never a live customer payment session.
- Identify which module owns keypad input and which owns the masked-entry object.
- Confirm acceptance in that module's permitted status indicators or diagnostics, and keep actual PIN values out of logs, screenshots and captures.
- Inspect the feedback object's visibility, bounds, stacking order and active-screen membership.
- Check whether a prompt, status banner or screen transition leaves an object drawn over the entry area.
If acceptance fails, trace the keypad and the module communications path. If acceptance succeeds and the feedback is hidden, correct the composition — the same layering repair used for overlapping graphics hiding HMI symbols on machine panels.
What makes text run off the edge of the screen? #
Text runs off the edge because the container was never sized for the longest configured message: a 128-pixel line with a 6-pixel character cell holds only 21 characters, and one arithmetic check proves it before anything is edited.
Worked example, with illustrative values typical of small monochrome display modules — a 128-pixel-wide panel and a 5×7 dot-matrix font whose character cell advances 6 pixels (a 5-pixel glyph plus 1 pixel of spacing):
- Line capacity: 128 px ÷ 6 px per character = 21.3, so 21 whole characters fit per line.
- Message under test: "LIFT LEVER TO DISPENSE" = 22 characters.
- Required width: 22 × 6 px = 132 px, which is 132 − 128 = 4 px more than the line, so the final character loses its last columns.
The same sum gives the fix: "LIFT NOZZLE TO START" is 20 characters and needs 20 × 6 px = 120 px, leaving 8 px of margin while also naming a control the handle actually has — one edit corrects the clipping and the stale mechanism reference together. Repeat the calculation whenever the font changes, because a substituted font moves the per-character width and today's fitting message clips tomorrow. On machine HMIs, the same symptom appearing right after a project download has its own checklist in HMI text runs off the screen after downloading the project.
Why does a prompt point to a soft button that is not there? #
The prompt and the button are driven by different settings — the prompt by the message mapping, the button by visibility rules and an enabled action — so at least one of them is bound to the wrong operating state.
An instruction is only correct if the action it names is available at that moment. Align the prompt's visibility with the corresponding button's visibility and enabled state, and account for disabled, unavailable and transition states: a button hidden during an authorization wait should not carry a prompt inviting a press. Remove references to controls the installed equipment does not have. Holding every screen to the discipline of designing HMI screens for clear operator decisions is what keeps prompt and action from drifting apart at the next revision.
How do I trace a message back to the module that owns it? #
Trace each instruction backward through five stops — display object, message selection, state binding, communications driver, supplying module — and the first stop where the observed value disagrees with physical reality is where the fault lives.
- Display object: confirm which object is drawn, and its visibility, bounds and stacking.
- Message selection: determine whether the string is static or selected from a message table.
- State binding: identify the state or tag that drives the selection and the value it currently holds.
- Communications driver: check that tag's diagnostics for presence, freshness and quality.
- Supplying module: compare the state the module reports with the physically observed condition.
Separate a tag fault from a binding fault as you go: a tag fault concerns the value or its availability, a binding fault concerns how the interface object uses that value. Replacing communications hardware will not repair an object linked to the wrong state.
How do I apply the fix without breaking the dispenser? #
Fix the profile first, then the screen composition, and only then the communications path, deploying each change as an approved package with a recovery copy of the previous configuration kept on the bench.
- Capture the current configuration before anything else: installed display dimensions, operating mechanism, module identities and software versions, from configuration screens or labels.
- Reproduce each defect and record the operating state in which it appears, without recording payment credentials.
- Compare the physical handle operation with the configured equipment profile, and correct a profile mismatch before changing any message.
- Locate the owner of each defective message: display application, payment interface or another module.
- Make each instruction describe the action actually available in that state.
- Align prompt visibility with button visibility and enabled state across disabled, unavailable and transition states.
- Resize or reposition text containers against the installed display and font settings, checking wrapping with the longest configured messages.
- Correct masking-object placement and conflicting visibility rules so input feedback stays clear of prompts and overlays.
- Deploy the approved change package and retain the recovery copy of the previous configuration.
A graphics-only repair is right for clipping or overlap when state selection and input handling check out. A configuration repair is right when the interface describes different hardware. A communications repair belongs only where diagnostics identify missing, stale or rejected information.
When is the display module itself the problem? #
When the overlap or distortion moves, flickers or smears across every screen instead of repeating a fixed pattern, the display module itself is the suspect rather than the application drawing it.
Compare the rendered interface with the panel's visible output using the manufacturer's approved diagnostic method; that comparison separates damaged display output from an application genuinely drawing overlapping objects. A defect that repeats identically on every screen is layout. When the module itself is failing and the repair is not worth it, the station can be rebuilt around industrial touchscreen monitors while the controller stays where it is.
Questions asked
Why did the wrong prompt appear only after the chip-card upgrade?
The payment module's software update does not revise strings owned by the interface module. When a dispenser's modules end up on mixed versions, a new payment flow can drive states that the older interface module's message table still describes with the previous mechanism's wording. Record every module's software version before editing text, and re-align the message set to the installed hardware rather than to the newest module.
How many characters fit on a 128-pixel display line with a 5×7 font?
Twenty-one. Each character cell advances 6 pixels — a 5-pixel glyph plus 1 pixel of spacing — and 128 ÷ 6 = 21.3, so only 21 whole cells fit on the line. A 22-character message such as LIFT LEVER TO DISPENSE needs 22 × 6 = 132 pixels and loses the final 4 pixels. Shorten the wording or drop to a smaller font before blaming the panel.
Should I rewrite the message text or fix the equipment profile?
Fix the profile when more than one prompt references the removed mechanism, because a profile correction re-aligns every related instruction and button action in one change. That keeps you from repairing one visible string while the same mismatch lives on in the next screen.
Can a screen that shows overlapping text actually be failing hardware?
Yes. Overlap that repeats the same fixed pattern on every screen is layout, but artifacts that wander, flicker or smear across screens point to the display module. Compare the drawn interface with the panel's output using the manufacturer's approved diagnostic method before replacing anything, because the two faults are corrected in different places: one in the project, one on the bench.