Troubleshooting
HMI shows Text instead of captions after a project download
Short answer
When every new text box, button and text list shows the placeholder word Text after a download — and older objects show captions in a different language — the panel's active runtime language no longer matches the project language the text was entered in. Switch the panel back to that language; no re-download, font change or factory reset is needed. A caption that shows Text under every enabled language was never entered and needs a transfer.
On this page
- Why does every new text box and button show Text after a download?
- How do you confirm a language mismatch instead of a corrupted project?
- Which language was the project text actually entered in?
- How do you set the panel back to the matching language?
- What should the panel show once the languages match?
- When is a re-download or factory reset actually needed?
- How do you stop the language from drifting again?
- Questions asked
When a freshly downloaded project fills your new text boxes, button captions and text lists with the literal word Text — while a handful of older objects suddenly speak another language — nothing on the panel is broken and the project is not corrupted. The panel's active runtime language no longer matches the project language you typed the text in. A multilingual HMI project stores one string per configured language for every object; the panel renders the column belonging to the language it is currently set to, and an empty column renders as the placeholder Text. Switch the panel back to the editing language and the captions return immediately, with no re-download, font change or factory reset. The sections below give the symptom pattern that proves it, the exact checks, a worked example, and the one case where a transfer really is needed.
Why does every new text box and button show Text after a download? #
Because the panel is running in a different language than the one you typed the text in: every object you created under the editing language shows the placeholder word Text, while objects already translated into the panel's active language show that language's captions.
A multilingual project keeps its texts like a spreadsheet: one column per configured language, one row per object. Text you type lands in the column of the editing language selected at the time — the vendor documents that all project texts are created in whichever editing language is selected. At runtime the panel reads the column belonging to its own active language, so when someone changes the language on the panel itself, the lookup switches columns.
- Objects with a filled cell in the active language render that language — the 'wrong text' on older captions.
- Objects with an empty cell render the placeholder string Text — every new object, because new text exists only in the editing language.
- Fonts, restarts and identical re-downloads change nothing, because the strings were transferred and are rendering correctly; the panel is simply reading a different column than the one you filled.
Do not confuse this with missing numbers: a numeric field with no room renders ####, which points at field width, as covered in why rebuilt HMI runtime files show #### for PLC tags. A missing string renders Text, which points at the language column.
How do you confirm a language mismatch instead of a corrupted project? #
Confirm it in one screen: if every new object shows Text, an older object shows another language, and fonts, restarts and a re-download change nothing, you have a language mismatch, not corruption — a corrupt project cannot produce clean text in a third language.
Run the check on one screen that contains an old caption, a new button and a new text list:
- Every new object shows Text — the text exists only in the editing language, and the panel is displaying a different, empty column.
- Some existing objects show captions in another language — that column is filled, so the panel renders whatever it finds there.
- Changing font type or size does nothing — formatting was never the fault.
- Restarting the panel and the engineering PC does nothing — the strings are on the panel and correct.
- Re-downloading the identical project changes nothing — the transfer is not the fault, so a reset has nothing to repair.
Two or more of these together confirm the mismatch. If instead the caption appears but is clipped after the download, that is a layout fault, not a language fault — see HMI text runs off the screen after downloading the project.
Which language was the project text actually entered in? #
Open the project, look at the editing language shown in the project settings, and compare it with the list of runtime languages — the captions you typed live in the editing language column, and that is the language the panel must be set to at runtime.
Two lists decide it, and both live in the project, not on the panel:
- The editing language, set through the Editing language selection in the project's language settings, is the column every caption you typed was written into.
- The runtime languages, enabled for the HMI device under Runtime settings > Language & Font, are the choices the panel actually offers.
The mismatch lives between them. If the panel's active language is a runtime language but not the editing language, you get this exact symptom. If only one runtime language is enabled and it differs from the editing language, every new object shows Text with no exception. If several are enabled, any of them can be the one someone selected on the panel. Write the editing language down before touching the panel — that value is the target the fix aims at.
How do you set the panel back to the matching language? #
Change the active runtime language on the panel to the editing language — no project change, no re-download and no reset is required — then reopen the affected screen; the new captions appear immediately because they were on the panel the whole time.
The correction happens on the panel, not in the project:
- On the panel, open the language selection the machine exposes — a language switch object in runtime, or the language entry in the panel's own settings, depending on how the machine builder set it up.
- Note the active language before changing it; that is the mismatch, and it is worth a line in the shift log.
- Select the language that matches the editing language you wrote down.
- Reopen the screen with the new text boxes, buttons and text lists — no transfer in between.
- If the needed language is not offered on the panel, enable it under Runtime settings > Language & Font and download once; that is the only transfer this fault justifies.
In the documented case, the language setting in the HMI itself had been changed, and matching it back restored every caption. If the panel's language keeps reverting between shifts, treat that as a separate persistence fault and work through resolving a control's language setting that keeps reverting.
What should the panel show once the languages match? #
Every object resolves: in a two-language project with English typed and German active, all 10 new buttons and 3 new text lists show Text on German and their captions on English, while the 6 objects already translated into German show German on German and English on English.
Worked example with illustrative numbers — a two-language project, English as the editing language, German enabled at runtime:
- Objects added in the last download: 10 buttons + 3 text lists, all typed under English, so 10 + 3 = 13 objects with an empty German column.
- Objects already translated into German: 6.
- Panel set to German: 13 objects render Text, the same 6 objects render their German captions, and 13 + 6 = 19 objects checked with the pattern accounting for all 19.
- Panel set back to English: the 13 placeholders resolve to their English captions and the 6 translated objects resolve to English — 19 of 19 correct, with no byte of the project changed and no transfer.
Verify by stepping through every enabled runtime language: each object must resolve to the string intended for that language, and any object that shows Text under every language has no entry anywhere — that one object needs the transfer described in the next section. Safety note: before the machine runs again, open a screen with alarm text and confirm the messages render in the active language, because a placeholder where an alarm message belongs is a missing warning, not a cosmetic fault.
When is a re-download or factory reset actually needed? #
Only when the language check fails: a re-download is needed if a caption shows Text under every enabled language (the string was never entered), and a factory reset is not justified by this symptom at all — the documented case cleared with a language change alone.
Decide case by case:
- Captions show under one language, Text under the others: language mismatch. Switch the panel language as in the steps above — no transfer, no reset.
- Text under every enabled language: the string was never entered. Type it under the editing language and download once.
- The needed language is not selectable on the panel: enable it in the project's runtime language settings and download once.
- Language columns verified and captions still wrong: escalate. First confirm which project the panel is actually running by verifying the HMI project version on the panel, and consider a reset only after that check.
A reset cannot move a string from one language column to another, and the documented case cleared with a language change alone — prove the columns first, and keep the reset for faults that actually need one.
How do you stop the language from drifting again? #
Limit the panel's choices: enable only the runtime languages your crew actually needs, keep the editing language and the default panel language identical, and restrict the language switch behind user access so an operator cannot flip it mid-shift.
Three locks prevent a repeat:
- Enable only the runtime languages the crew actually maintains — an enabled but untranslated language is a Text placeholder waiting for an operator to select it.
- Keep the default panel language equal to the editing language on any replacement panel or after a service visit that rewrites settings, so the machine starts in the language the texts were typed in.
- Where the panel supports user management, put the language switch behind a higher access level so the selection survives the shift.
When a second language is added later, translate every caption into it before anyone can select that language at runtime. The same discipline applies to PLC-side text, as in translating RSLogix 5000 comments to another language.
Questions asked
Is this a touchscreen hardware fault?
No. A failing touchscreen shows drift, dead zones or no touch response while the picture itself still renders normally; here the picture renders the wrong string, which is a software lookup result. Display and touch hardware are working whenever the panel consistently substitutes Text or another language for your captions.
Does the wrong language affect alarms and other project text too?
Yes. In a multilingual project every translatable string — screen captions, button labels, text list entries, alarm messages — is stored per language, so a panel running the wrong language substitutes text across the whole runtime, not just on the screen you edited. Anything rendering as Text is an empty cell in the language the panel is currently showing.
Why did the problem start right after a project download?
The download is timing, not cause. Project modifications are usually loaded around the same time someone has been working in the panel's settings, and the objects added by those modifications are exactly the ones whose text exists in only one language. The transfer wrote the strings correctly; the panel's active language decides how they render.