Troubleshooting
PanelView Plus 600 With No Config Button and Full Flash
Short answer
No key combination opens Configuration Mode on a PanelView Plus — those keystrokes belong to PanelView Standard. Touch the white box in the bottom-left corner during boot; if the runtime loads anyway and the flash is too full for a download, delete the .MER and .MRK runtimes with a CompactFlash autoexec batch so the terminal boots into Configuration Mode. Back the runtimes up with the transfer utility first.
On this page
- Why the key combinations do nothing
- Try the white startup box first
- Back up the runtimes before deleting anything
- Download a replacement runtime with a Configuration button
- Delete the runtimes with a CompactFlash autoexec
- Worked example: recovering a full-flash PanelView Plus 600
- Clear the orphaned files once you are in
- When recovery is not worth it
- Questions asked
No key combination will open Configuration Mode on a PanelView Plus 600. Left+Right, Left+Right+Enter and F1+Up are PanelView Standard firmware shortcuts, and a PanelView Plus ignores them. Two conditions locked this terminal: the running .MER contains no Configuration button (often labeled Goto Config), and the onboard flash is too full to accept another runtime download. The recovery is to back up the onboard runtimes with the transfer utility, then delete the .MER and .MRK files so the terminal boots with no valid runtime and lands in Configuration Mode. One try comes first: touch the white box that flashes in the bottom-left corner during startup.
Why the key combinations do nothing #
PanelView Standard terminals interpret keystrokes in firmware, which is why Left+Right or F1+Up opens their configuration screens. A PanelView Plus boots a Windows CE image and hands control to whatever runtime the startup configuration names. The Configuration button is an object the application developer places on a screen; nothing in the terminal's firmware creates one. When the shipped .MER omits it, or application security hides it from the operator role, there is no on-screen path back to Configuration Mode and no keystroke substitutes for it.
Try the white startup box first #
During power-up, before the runtime takes the screen, a small white box appears for a few seconds in the bottom-left corner. Touch it while it is visible and the terminal opens Configuration Mode instead of the startup application; this is the documented entry point when the runtime offers no button. If the box never appears on your unit, reaching HMI config mode with no startup square covers the causes. If the box shows but the runtime loads over it before you can touch it, power-cycle and try again, then move to the recovery paths below.
Back up the runtimes before deleting anything #
The deletion below removes every runtime in the terminal's flash, including orphaned old .MER files that are sometimes the only surviving copy of an application. Run the FactoryTalk View Machine Edition transfer utility (the RSView ME transfer tool on the oldest releases) and upload the runtimes from the terminal to .MER files on your computer before touching anything else. The discipline is the same as backing up an HMI with a scratched touchscreen before replacement: get the program off the hardware before you change the hardware's state.
Download a replacement runtime with a Configuration button #
When at least one communication channel still reaches the terminal and the flash has room, this is the fastest fix:
- In FactoryTalk View Studio, build a one-screen Machine Edition application with a Configuration Mode button on that screen.
- Download it with the transfer utility over whichever channel still works, and tick "Run Application when Download Completes" so the terminal resets straight into the new runtime.
- Press the Configuration button and set the terminal back up: network settings, RSLinx Enterprise communication setup, and the real startup application.
The recovery .MER must match what the terminal's firmware can run; if the download is refused as a version error, fixing an MER runtime version mismatch walks that error. When the download is refused because the flash is full, stop here and delete instead.
Delete the runtimes with a CompactFlash autoexec #
The boot manager starts the designated startup .MER if it finds one; with no runtime present it opens Configuration Mode, and that is the whole trick. A CompactFlash card carrying an autoexec.bat in its root runs at startup before the shell loads, deletes the runtime files, and resets the terminal.
PanelView Plus 400 and 600 terminals take the card in the external slot on the back of the unit. Use a Type I or Type II card formatted FAT16, with this batch as autoexec.bat:
@echo off
REM PanelView Plus 400/600 - force Configuration Mode
del /q "\Flash\Windows\*.MER"
del /q "\Flash\Windows\*.MRK"
del /q "\Flash\Windows\ProjectView\*.MER"
del /q "\Flash\Windows\ProjectView\*.MRK"
reset
PanelView Plus 700, 1000, 1250 and 1500 terminals boot from an internal CompactFlash card on the logic module, so the recovery card goes there and the unit has to be opened following the disassembly instructions in the PanelView Plus Terminals User Manual (publication 2711P-UM001). The file paths differ:
@echo off
REM PanelView Plus 700/1000/1250/1500 - force Configuration Mode
del /q "\Storage Card\Windows\*.MER"
del /q "\Storage Card\Windows\*.MRK"
del /q "\Storage Card\ProjectView\*.MER"
del /q "\Storage Card\ProjectView\*.MRK"
reset
Do the wipe while the machine can run without its HMI: after the deletion the terminal sits in Configuration Mode with no operator screens until you load a runtime.
Worked example: recovering a full-flash PanelView Plus 600 #
Inputs, from the field case: a keypad/touch PanelView Plus 600; the running .MER has no Configuration button; Left+Right, Left+Right+Enter and F1+Up were tried at startup with no effect; a new runtime download is refused because the flash is full of old files. Media on hand: a Type I or II CompactFlash card formatted FAT16.
Rule in words: the boot manager starts the configured startup runtime when it finds one, and opens Configuration Mode when it finds none — so remove every runtime it could start.
Arithmetic: the runtime it could start is one file, with either of 2 extensions (.MER or .MRK), in either of 2 locations (the Windows folder or its ProjectView subfolder). 2 x 2 = 4 delete patterns, which is exactly the four del lines in the 400/600 batch above — nothing startable survives.
Walkthrough: write the 400/600 autoexec.bat to the card root, insert the card in the terminal's external slot, power-cycle, and let it run. The batch deletes the four patterns, the reset line restarts the terminal, the boot manager finds no runtime, and the Configuration Mode menu opens.
Decision: the moment a download is refused for full flash, skip the replacement-runtime path and go straight to this deletion — the full flash blocks the easy route and nothing about that changes until files are removed. Once Configuration Mode opens, clear the orphans as below so a full flash never blocks you again, then load the production runtime.
Clear the orphaned files once you are in #
From Configuration Mode, go to Terminal Settings > File Management > Delete Files > Delete Applications, press Source to choose the storage location, and delete the old .MER applications that filled the flash — the PanelView Plus Compact Terminals manual (publication 2711PC-UM001) documents this path. Then remove autoexec.bat from the CompactFlash card before the terminal returns to service; while that file sits in the card root, every power-up deletes the runtimes again. Load the production runtime, set it as the startup application, and reboot once to confirm it starts cleanly.
When recovery is not worth it #
If the terminal will not hold a runtime after recovery or the platform is being retired, the operator station moves to industrial panel PCs running the PC-based HMI runtime at the machine.
Questions asked
Can I back the runtimes up to the CompactFlash card instead of uploading them?
Yes. The File Management screens in Configuration Mode copy applications to the storage card, and the vendor's documented copy procedure for MER runtime files uses exactly that path. Upload over the network with the transfer utility is faster when a channel works, but a card copy is a valid backup when nothing else talks to the terminal.
Why does deleting the runtime files drop the terminal into Configuration Mode?
The boot manager looks for the startup .MER or .MRK file and starts it. When none exists, it cannot launch an application and opens the Configuration Mode menu instead, which is where network settings, RSLinx Enterprise communication setup and the startup application are configured. The terminal stays there until you load a runtime.
What happens if the autoexec.bat stays on the CompactFlash card?
The batch runs at every power-up and deletes the runtimes each time, so the terminal can never hold a startup application. Delete autoexec.bat from the card before the terminal returns to normal service, and keep the recovery card FAT16 in a Type I or Type II slot when you rebuild it.
The replacement runtime download was refused as a version mismatch. What now?
The recovery .MER has to be built by a FactoryTalk View Studio release the terminal's firmware supports. Rebuild the single-screen application at the version the terminal already runs, or bring the terminal firmware up to the revision the .MER targets, and retry the download before falling back to the deletion path.
Is it safe to wipe the runtimes on a running machine?
Only when the process can run without its HMI. After the deletion the terminal sits in Configuration Mode with no operator screens until you load a runtime, so operators lose start, stop and alarm visibility for that window. Schedule the wipe for a break or a planned outage.