IMDTouchKnowledge BaseShop main store

Troubleshooting

PanelView Plus 7 Name and Password Setup Error Fix

HMI and touchscreens Published 7 min read

Short answer

The Name and Password setup error on a PanelView Plus 7 is a setup-state failure, not a rejected password, when compliant entries keep failing at the same transition. Read the exact message, run one simplified-entry validation test, capture the catalog number, firmware revision, error text, application copy and network settings, then use the documented factory reset for your catalog number and re-run setup.

On this page
  1. Read the exact message before touching the credentials
  2. Separate an entry rejection from a setup-state failure
  3. Capture five things before any reset
  4. Run the documented factory reset for your catalog number
  5. Working a PanelView Plus 7 that fails at the name and password screen
  6. Prove the setup survives a restart
  7. Questions asked

A PanelView Plus 7 that errors at the Name and Password setup screen, with entries that meet the displayed rules, is not arguing about your password: the terminal is failing to complete its initial setup operation. That is the case this article works, and a documented factory reset cleared it. Work it in this order: photograph the exact message, run one validation test with a simplified name and a fresh compliant password, and if a second compliant entry still fails at the same transition, stop editing credentials — capture the five commissioning items, run the factory reset documented for your catalog number, and re-run setup. A restart alone normally retains the persistent configuration, so cycling power is not the recovery step. The sections below separate the faults that look alike, list what to capture before a reset, and give the reset sequence and the proof checks.

Read the exact message before touching the credentials #

The exact text decides the branch, and a screenshot of a dialog does not travel — you need your own terminal's wording. Photograph the dialog first and record three things: the full wording, which field the message names, and the action that triggers it — submitting the setup screen, opening setup, or finishing setup.

Three faults hide behind an error at the name screen:

  • The message names the name field, a character or a length rule. That is entry validation: compare the entry against the requirements printed on the screen itself, then correct to those rules.
  • The message names the password field or the confirmation. Re-enter both fields once, watching for a mismatch between the two fields and for a USB keyboard whose layout does not match what you think you are typing.
  • The message reports an operation failure, a timeout or an internal fault rather than a rule. That is the setup operation failing, not the typing. As presented, this fault sits here: no rule is named and the entries look compliant.

Stop after one clean pass through spelling, confirmation and the displayed requirements. Repeated password changes help only when an entry actually violates a displayed rule; they do not repair a terminal that cannot complete its setup operation.

Separate an entry rejection from a setup-state failure #

The setup screen does two jobs. It validates the text, and it completes the configuration operation that creates the user. An error there can come from the entered data or from the state of the configuration being created, and the message wording tells you which side to work.

Keep runtime authentication out of this scope. A login failure inside an already-running application involves that application's own user accounts, and a factory reset is not the first diagnostic for it — running one destroys the very accounts you are trying to reach. This procedure is for the initial setup transition that will not complete.

Capture five things before any reset #

A factory reset is a recovery action, not a credential test: it changes persistent terminal state and discards configuration. Before running one, record:

  • The full catalog number from the terminal's identification label. It selects the correct documentation and reset procedure.
  • The installed firmware revision from the terminal's system information, if that screen is reachable without completing the failing setup.
  • The complete error text, the setup screen and the sequence that triggers the failure, photographed with no credentials in frame.
  • Whether a usable copy of the application exists outside the terminal. If the only copy is on the terminal and its configuration menu is reachable, run the documented backup before resetting.
  • The network and communications settings needed for recommissioning: IP address, subnet mask, gateway and the controller path the application uses.

If the terminal is mounted on a running machine, put the machine in its approved maintenance condition before you reset: the reset erases the setup that guards operator access, and the machine can be left without its operator interface mid-shift.

One caution on firmware: no firmware revision or firmware-specific defect is established for this fault. Choose an update only when the manufacturer's guidance for your catalog number calls for it or requires it for recovery — the release notes for each firmware package list the anomalies fixed, and this fault would have to appear there first. Check the revision limits described in when the firmware upgrade utility cannot upgrade an HMI terminal before attempting one.

Run the documented factory reset for your catalog number #

Factory reset cleared this fault in the case worked below, and it is the documented recovery for a terminal whose setup state is wedged. Use the procedure published for your exact variant and firmware; do not borrow a sequence from another terminal family.

For PanelView Plus 7 terminals, the published reset-to-defaults sequence attaches a USB keyboard, cycles power while holding F1, and continues through the reset menu that appears. Read the data-loss consequences in your terminal's own user manual before you start — the PanelView Plus 7 Performance terminals user manual and the PanelView Plus 7 Standard terminals user manual both cover configuration and recovery.

Then:

  • Run the reset on stable power and do not interrupt it while it writes terminal configuration.
  • Re-run the initial setup and enter a name and a password that meet the screen's displayed rules.
  • Record whether setup advances past the transition that previously failed.
  • Restore the application, the network settings and the operator credentials from the capture records using the documented commissioning workflow, and confirm the terminal loads the runtime file you expect, as described in finding the runtime file an HMI terminal actually loads.

Do not guess key combinations, hidden menus or recovery credentials. If the documented sequence does not reach the reset menu on your terminal, take the catalog number, series, firmware revision and captured error text to the manufacturer's support channel — Series B terminals with initial-setup failures are a documented knowledgebase topic of their own, so include the series when you search.

Working a PanelView Plus 7 that fails at the name and password screen #

The case: a PanelView Plus 7 errors the moment the Name and Password setup screen is submitted, with entries that meet the screen's displayed rules.

Inputs, each with its source:

  • Error site: the Name and Password setup screen, on submit (the fault as presented).
  • Entry quality: the name and password pass the displayed rules as far as the operator can tell (the operator's own check).
  • Validation entry: one simplified name and one fresh compliant password (the validation test).
  • Reset path: USB keyboard attached, F1 held through power-up, reset menu completed (the published reset-to-defaults procedure for the PanelView Plus 7).
  • What the reset discards: applications, network settings and the credentials created at setup (the terminal's data-loss documentation).

The rule, in words: one compliant entry that fails proves nothing by itself. A second, different compliant entry that fails at the same transition removes the entry text as the variable; the fault moves to the setup operation, and the documented reset becomes the next action — but only after the five capture items are recorded.

The arithmetic, written out:

  • Attempt 1, original entries: error at submit.
  • Attempt 2, different compliant entries: error at the same transition.
  • State changes between attempts: 0 — a power cycle retains persistent configuration, so nothing else moved.
  • Compliant inputs ruled out: 2. Transitions that failed: the same 1. The one constant across both failures is the terminal's setup state.
  • Capture items recorded: 5. Documented resets run: 1.
  • Attempt 3, original entries, after the reset: setup advances past the transition; errors at it: 0.

Result: setup completed on the first attempt after the documented reset — the terminal accepted the entries and the error was gone.

Decision: two compliant failures at the same transition is the threshold at which you stop editing credentials and reset. A single failure stays in the message-reading branch, because one failure cannot separate a bad entry from a wedged setup, and no reset runs before the five capture items are on paper.

Prove the setup survives a restart #

Clearing the message is not the acceptance test. After the reset and recommissioning:

  • Submit the credentials and confirm setup advances with no error.
  • Complete the remaining setup screens and reach the terminal's operating state.
  • Perform a controlled restart and confirm the same setup error does not return; a reset that only hides the fault until the next power cycle is not a fix.
  • Check the restored network settings against the capture records by confirming the terminal communicates with the controller.
  • Open the application and confirm displayed values update and permitted operator functions respond, under the site's commissioning controls.
  • If the error returns before the application is restored, the reset did not fix the fault: collect a fresh set of evidence and take the terminal to the manufacturer's support channel.

Questions asked

Does a factory reset delete the PanelView Plus 7 application and network settings?

Yes. Resetting to factory defaults returns the terminal to its delivered state, so the application, the IP configuration and the name and password created during setup are all discarded. That is why the catalog number, firmware revision, error text, application copy and network settings are captured before the reset. Once the terminal is commissioned again, use the documented backup function so a future reset is a restore instead of a rebuild.

What are the password rules at the setup screen, and is there a default account?

The length and character rules are printed on the terminal's own setup screen, and the Standard terminals user manual recommends changing the default password and its challenge question and answer to something unique for your installation. The manual itself documents the defaults, so change them rather than leaving them in service. If you used a deliberately simple name and password for the validation test, replace them with your real credentials as soon as setup completes.

My PanelView Plus 7 application login now fails. Should I factory reset it?

No. A login failure inside a running application involves that application's own user accounts, not the terminal's setup state, so a factory reset destroys the accounts you are trying to reach. Recreate or restore the application's users through the documented commissioning workflow instead. Reserve the factory reset for the initial setup transition that cannot complete with compliant entries.

Does the keyboard reset work on older PanelView Plus terminals?

Treat reset procedures as specific to the terminal family and generation. The USB-keyboard sequence with the key held through power-up applies to the PanelView Plus 7 generation; older PanelView Plus hardware and other terminal families document different paths. Get the procedure for the exact catalog number from the manufacturer's documentation, and never try undocumented key combinations on a terminal that is otherwise working.

What if the documented reset sequence does not reach the reset menu?

Stop before experimenting. Confirm the keyboard is attached before power-up and try the documented sequence once more; if the menu still does not appear, take the catalog number, the firmware revision, the captured error text and the capture list to the manufacturer's support channel. Undocumented recovery attempts risk turning a recoverable setup fault into a terminal that cannot boot its configuration.

Keep reading

  • Troubleshooting

    Reaching HMI Config Mode With No Startup Square

    Test the documented USB keyboard path once - Ctrl+Shift+Alt+Windows held for a few seconds - because on terminals that never show the startup square it is the supported route in. A password-protected GO TO CONFIG button is application access control: get the credentials or the project from the owner, never a reset file. If you only need the IP address, discover it on an isolated link and skip configuration mode entirely.

    HMI and touchscreens

  • Troubleshooting

    Fixing Vijeo Designer Error 1850 Secondary Drive Not Found

    Error 1850 on an HMIG3U appears because the project assigns a data file to a Secondary or Optional drive this target does not define; it supports only the Main drive with an SD card. Move the data file's location to Main, rebuild, and the download completes. No hardware switch enables the missing locations.

    HMI and touchscreens

  • How-to

    How to find the runtime file an HMI terminal actually loads

    The startup configuration, not the file list, selects the loaded .MER. Cycle power and press the white box in the lower-left corner (touch, firmware 5.0 or later) or hold F1 on a directly connected USB keyboard to reach the configuration screen and read the loaded runtime name. Copy every stored runtime off before deleting anything in File Management.

    HMI and touchscreens