Troubleshooting
Reaching HMI Config Mode With No Startup Square
Short answer
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.
On this page
- Read the symptom before you change anything
- The keyboard shortcut is the documented alternate
- A password on GO TO CONFIG is access control, not a fault
- Find the IP address without configuration mode
- Worked example: setting the laptop after the browse
- Recovery media and firmware come last, if at all
- The decision for each case
- Questions asked
You are locked out of a touch HMI at runtime: no startup square appeared during boot, the application's GO TO CONFIG button asks for a password you do not have, and the keyboard shortcut did nothing. None of that is a fault. Whole generations of terminals never draw the square, the shortcut can be switched off in terminal settings, and the password is access control the application designer set on purpose. Decide first what you actually need: if it is only the terminal's IP address, configuration mode is unnecessary, because the address is discoverable on an isolated link. If you must change terminal settings, the path runs through the owner: the credential, the application project, or a vendor-documented recovery.
Read the symptom before you change anything #
Four different conditions produce this one complaint, and each has a different next step:
- No startup square during boot. The terminal starts the runtime directly, by configuration. Watch one complete power-up, corner to corner, before concluding it never appears, because it can show only briefly. Absent for a whole boot, it is a display behavior, not a dead touch surface.
- GO TO CONFIG visible but password-protected. The designer locked the runtime exit on purpose. The button works; you are simply not on its user list.
- The keyboard shortcut does nothing. Terminal input settings can stop the keys from being recognized at all. One clean, failed test means the path is closed on this installation, not that you pressed wrong.
- You need only the IP address. Configuration mode is the long way around. The Ethernet port answers network discovery on its own.
Confirm touch works inside the running application before you treat any of this as hardware failure.
The keyboard shortcut is the documented alternate #
On terminals that do show the square, tapping it during boot is the normal entry; the full startup procedure is in how to enter configuration mode on a touch HMI. On the ones that never show it, the documented route is a USB keyboard: plug it into the terminal's USB port, let the runtime come up, then press and hold Ctrl, Shift, Alt and the Windows key together for 3 to 5 seconds.
Give it one careful test. If configuration mode opens, do what you came for, and while you are in there open Terminal Settings>Input Devices>Keyboard. That setting decides whether keyboard keys are recognized, which is why a shortcut that works on one terminal can be dead on the next. If nothing happens, do not cycle keyboards or hold the keys longer; the outcome will not change. Move to the next branch.
A password on GO TO CONFIG is access control, not a fault #
The GO TO CONFIG button you found while paging through the screens belongs to the application, and so does its password: it is stored in the application project, not in the terminal's firmware. The machine owner, OEM, or integrator who holds the project can open it in the development software, read the password, or clear it and issue you a new one. That is the legitimate path, and it is usually the fastest one: a request to the owner beats every recovery procedure ever written.
Restricting who may leave runtime is the same deliberate design decision as setting granular user access on a touch panel on any other platform. What is never legitimate is the third-party route: a reset executable or memory-card image circulated for the express purpose of stepping over that password. Refuse it even when it is offered freely, and read the recovery section below before touching anything of that kind.
Find the IP address without configuration mode #
If the address is the only objective, close the application question and work the network. PanelView Plus terminals speak EtherNet/IP on their Ethernet port, which makes discovery a short job:
- Isolate. Put the terminal and a maintenance laptop alone on one small switch, or cable laptop to terminal directly. Never bridge a terminal whose address you do not know onto a production VLAN: if its static address duplicates a live device, you take two machines down at once.
- Browse, do not guess. Create an EtherNet/IP driver in RSLinx and browse. The driver sends a broadcast query that every local EtherNet/IP device answers with its own IP, so the terminal appears in the tree even when its subnet does not match the laptop's.
- Sweep only as the fallback. A ping or ARP scanner reaches devices in the laptop's own subnet and no further. An empty sweep means the terminal sits in another subnet; change the laptop address and sweep again rather than declaring the port dead.
- Verify by link state. Unplug the terminal's Ethernet lead and watch the entry vanish; reconnect and watch it return. A response proves that some node owns the address; the cable test proves which node.
Worked example: setting the laptop after the browse #
The browse lists the terminal at 192.168.10.201. To reach it directly, put the laptop in the same subnet with a static address. Assume mask 255.255.255.0, which is /24: 24 bits of network leave 32 - 24 = 8 host bits, so the subnet holds 2^8 - 2 = 256 - 2 = 254 usable addresses, 192.168.10.1 through 192.168.10.254. Choose 192.168.10.55 for the laptop: it lies inside the range, it is not the terminal's .201, and it is neither the .0 network address nor the .255 broadcast. Set the laptop to 192.168.10.55, mask 255.255.255.0, no gateway, because the link is point to point.
Ping 192.168.10.201 and four replies come back. Pull the terminal's lead and the replies stop; reconnect and they return. The address is confirmed, you document it with the hardware address and switch port, and configuration mode was never opened. A later sweep of 192.168.10.1 through 192.168.10.254 would cover all 254 addresses with nothing skipped.
Recovery media and firmware come last, if at all #
A factory reset is not a discovery tool. It wipes the running application and its communication configuration, so afterwards you need the application project and the comm setup before the panel runs again, which is the slowest possible way to learn an address you could have browsed for. A firmware update does not remove the GO TO CONFIG password, because the password lives in the project, not the firmware; it only adds compatibility and recovery risk on a terminal whose backup you have not verified.
If recovery truly is required, use only the manufacturer's documented procedure for the exact catalog number on the terminal's label, obtained from the manufacturer or the machine owner. Reject any reset package named for a whole terminal size range or circulated as an executable that promises to go to config: files that broad cannot match one hardware and software generation, and executing the wrong one converts an access question into a dead terminal.
The decision for each case #
- You need only the IP address. Isolated link, EtherNet/IP browse, cable-pull verification. Done at the panel, with no reset, no firmware work and no password.
- The keyboard shortcut works. Make your change, and check
Terminal Settings>Input Devices>Keyboardwhile you are in there, so the next technician's keyboard works too. - The shortcut fails and GO TO CONFIG is password-protected. Get the credential or the application project from the owner. That is the entire legitimate path.
- The owner has neither, and the terminal must be reconfigured. Vendor-documented recovery for the exact catalog number, with a verified application backup taken first.
Questions asked
Is there a different keyboard shortcut on newer PanelView Plus 6 terminals?
Yes. On PanelView Plus 6 terminals with firmware v4, press Ctrl+Alt+F1 during boot to reach configuration mode. That combination is specific to that terminal and firmware generation; on the terminals described in this article the documented combination remains Ctrl+Shift+Alt plus the Windows key held for 3 to 5 seconds.
Will the EtherNet/IP browse still find the terminal if its IP is in a different subnet than my laptop?
Yes. The browse works by broadcast: the laptop sends an EtherNet/IP list request that every device on the local link answers, and the terminal replies with its own IP whatever subnet it sits in. A ping or ARP sweep does not share that property, because it only reaches the laptop's own subnet, which is why the browse is the first tool on an isolated link.
Who can give me the GO TO CONFIG password?
The machine owner, the OEM, or the integrator that built the application. The password is stored in the application project, so the owner can open the project in the development software, read the password, or clear it and issue a new one. Asking for the credential or the project is faster and safer than any recovery procedure.
Would a firmware update remove the GO TO CONFIG password?
No. The password is a property of the application running on the terminal, not of the firmware, so updating firmware leaves it exactly where it was. A firmware update also adds compatibility and recovery risk on a terminal whose application backup you have not verified, which makes it the wrong first move for an access-control question.