Troubleshooting
When an HMI download asks for a username and password
Short answer
A username and password prompt during a project download is transfer protection working, not a failed panel. Confirm the target model and project revision, download with the owner's authorized credentials, and reserve the documented XBT GT serial recovery cable procedure for a terminal that cannot start or transfer at all.
On this page
- Why does the HMI ask for a username and password during download?
- How do you tell a protected transfer from a failing panel?
- Where do the download credentials come from?
- What should you verify before retrying the download?
- When is recovery the right step for an XBT GT?
- How do you run the XBT GT recovery procedure?
- What must you confirm after a recovery or a successful download?
- When is replacing the terminal the better decision?
- Questions asked
A username and password dialog in the middle of a project download is the terminal's transfer protection asking who is allowed to overwrite the running application. It is an access-control event, not a fault, and it is not by itself a reason to start a low-level recovery. On a Magelis XBTGT5330 that still boots to its operator screens, the working decision is short: prove the panel runs, prove the project and target are right, download with the owner's authorized credentials, and keep the documented XBT GT recovery procedure in reserve for a terminal that cannot start or transfer at all.
Why does the HMI ask for a username and password during download? #
Because the download path is protected: the terminal or the project's transfer settings demand an authenticated account before anyone overwrites the running application, and the dialog is that demand, not an error.
The setting can live in the terminal's transfer configuration or in the engineering project's access configuration. Which one applies does not change your first move, because both are satisfied the same way: with the account this installation was commissioned with. The protection exists for machine safety as much as data security — a different project on the same panel can change how the machine starts, stops and alarms — so the dialog is a gate you are meant to pass legitimately.
Record when the dialog appears: at the moment the PC connects, when the transfer starts, or during panel startup. The first two are authorization checks. The third is a different symptom and belongs on the service path, not the credential path.
How do you tell a protected transfer from a failing panel? #
Power the terminal on its own, before the programming PC is connected: if the existing application reaches its operator screens, the panel boots, its runtime executes, and the credential prompt is isolated to the transfer attempt.
One power cycle buys you the single observation that rules out a dead terminal. Classify what you have against this table:
| What you observe | What it means | Next move |
|---|---|---|
| Panel reaches its operator screens; dialog appears when the download starts | Healthy panel, restricted transfer access | Authorized credentials, then verify target and revision |
| Dialog appears the moment the PC connects | Same protection, triggered at connection | Same path: authorized credentials |
| Panel stops on a system screen or never starts | Startup fault, separate from any credential question | Record the fault text and take the service path |
| Credentials rejected, or nobody holds them | Access control working as designed | Equipment owner or integrator of record; no guessing |
Capture three things while you are there: the exact dialog text and the operation in progress when it appeared; how far the panel's own startup gets with nothing attached; and whether this PC and this cable ever transferred to this panel before.
Where do the download credentials come from? #
From the machine's commissioning records and the people who own them — the equipment owner, the integrator of record, or the project administrator — not from the terminal, a default list, or trial and error.
Pull the records before you touch the keyboard again, and do not cycle through guesses: repeated failures can end in a lockout, and clearing one means the project goes back on afterward, the sequence covered in redownloading an HMI project after a user lockout.
Illustrative example, not a measured benchmark: put one failed credential attempt plus its reconnect cycle at about 2 minutes of bench time, and the full project redownload that a lockout forces at about 15 minutes. Three guesses then cost 3 × 2 + 15 = 21 minutes and still leave you without access, while the commissioning binder and one phone call typically produce the credential in about 5 minutes. That arithmetic is the decision: records first, every time.
If the documentation chain is genuinely broken and nobody holds the credentials, the legitimate route is the owner's documented access recovery, never a bypass — start from recovering access to a password-protected HMI panel without a backup.
What should you verify before retrying the download? #
Three things, in order: that the project targets the exact terminal model, that you hold the approved project revision, and that the transfer channel matches the one the installation was commissioned with.
Read the target from the project's own device configuration and match it to the model on the door — here, the XBTGT5330. Match the revision to the machine documentation so a credential fix does not become an untested edit. Match the channel: these terminals took projects over serial, USB or Ethernet, and the XBT GT host serial interface is an 8-pin RJ45 carrying RS-232C per the user manual. A different cable does not produce credentials; it only fails differently.
Confirm which file you hold, too. A runtime download and the editable Vijeo Designer source are different objects, and rebuilding the source is its own task, covered in recovering a Magelis HMI project with Vijeo Designer.
When is recovery the right step for an XBT GT? #
Only when the terminal cannot start or cannot accept any transfer: recovery is a low-level service operation that replaces the runtime, and a credential prompt on a panel that still runs never meets that bar.
Scope is model-bound. Schneider Electric's runtime-recovery FAQ (FA332820) states it plainly: the Magelis HMIGTO and STU devices do not have the serial recovery cable option that the XBT GT series has. Confirm any service note covers your exact terminal before you plan around it.
Have four things on the bench before recovery is even discussed:
- The panel's part number and label data.
- The exact symptom or fault text, captured independently of the credential dialog.
- The backup status of the project currently loaded on the panel.
- The owner's explicit approval for an operation that can replace data on the terminal.
How do you run the XBT GT recovery procedure? #
Per Schneider Electric's FAQ "How to use the Serial recovery cable for XBTGT terminals" (FA195930): set DIP switch 3 on the terminal to ON, then connect the terminal to the PC with the serial recovery cable and an Ethernet or USB cable at the same time.
That is two simultaneous links — the serial recovery cable on the terminal's serial interface, plus Ethernet or USB — and one switch position, before any software step. On the programming PC, the sequence continues with the vendor's recovery software from the Schneider Electric program group in the Windows Start menu, in the order the note gives.
The cable's construction, pinout and use come from the technical note itself, so obtain that document from Schneider Electric's documentation or support rather than reconstructing it. Do not substitute a generic serial lead: service connections made without the documented pin map fail for the same reason a USB HMI transfer cable cannot be hand built, and a recovery port is a worse place to learn it. If the note or the specified cable is not to hand, stop and get them.
What must you confirm after a recovery or a successful download? #
That the panel completes startup to its operator screens, that the application on it is the approved revision, and that the machine's HMI functional checks pass — displayed values and operator actions verified against the commissioning procedure — before the station goes back to service.
Split the check to match the path you took. After a credential-resolved download: the dialog does not recur, the transfer completes, and the displayed application is the one you intended. After a recovery: confirm the recovery result first — the terminal starts and reaches a defined state — then restore the approved application through the authorized transfer, because recovery reinstalls the runtime; it does not grant the right to load a project.
When is replacing the terminal the better decision? #
When the panel will not recover, or when the access route and the project source are both gone with no owner path to rebuild them: repair has stopped being the answer, and the station moves to current hardware.
The XBT GT family is a discontinued generation, so a terminal that fails both the credential route and the service route is a dead end rather than a repair candidate. The practical move is industrial panel PCs running the rebuilt visualization at the machine. Design the replacement's access control deliberately, so the next technician is one phone call from the credentials: the pattern is in designing HMI user access levels for operators and maintenance.
Questions asked
Does the username and password prompt mean the XBTGT5330 firmware is corrupted?
No. Corruption shows at power-up: the terminal stops on a system screen, loops, or never reaches its application. If your panel boots to its running screens and only the download raises the dialog, the runtime is fine and the only problem in front of you is transfer authorization.
Can the transfer password be removed from the terminal itself?
Not by any route that respects the protection. Transfer access belongs to the project and target configuration, so it is changed through the engineering software with the owner's authorization, not by a keystroke on the panel. Treat any credential that did not come from the machine records as wrong rather than trying variants of it.
Which Magelis terminals support the serial recovery cable?
The XBT GT series. Schneider Electric's FAQ FA332820 states that the Magelis HMIGTO and STU devices do not have the runtime recovery option the XBT GT series has. That matters for substitution: replacing a failed XBT GT with an HMIGTO removes the recovery path you may be counting on.
Will the recovery procedure wipe the application on the panel?
Plan as if it will. Recovery reinstalls the terminal's runtime at a low level, and anything loaded on top of it should be considered at risk, so capture the part number, the exact symptom and any existing project backup first, and start only with the owner's approval. Recovery also does not hand you download authorization afterward.
What if no one at the plant has the download credentials?
Escalate before you experiment. The equipment owner or the integrator of record is the legitimate source, and machine documentation sometimes holds the account where nobody remembers it. If that chain is truly broken, the honest options are an owner-authorized access recovery or retiring the terminal and rebuilding the application on current hardware with properly documented access control.