Scope and version constraint
The reported target is a PanelView 700 Plus application developed in FactoryTalk View Studio ME version 5. The available procedure was originally described for RSView Studio 4.0 using RSView 3.X accounts, so first confirm that the version 5 project exposes the same account type and A-through-P security-code fields. The evidence does not establish that both versions handle security identically.
Reported account and display-access model
The procedure assigns lettered security rights to users and then assigns a security code to a display. Its intended access matrix is:
| Account | Enabled security codes | Intended access |
|---|---|---|
| Engineer | A through P | All letter-coded displays |
| Calibration | A through P | All letter-coded displays |
| Operator | A only | Displays assigned code A |
| Default | Project-dependent | Initial session before login |
The reported workflow states that the application starts as the default user on its first run and after a shutdown and restart. Therefore, the startup path must remain usable by that account long enough to reach the login controls.
Configure and verify display security
- Open User Accounts in the project explorer. If the version 5 project provides the referenced account mode, select the RSView 3.X account option.
- Create Engineer and Calibration accounts, assign passwords, and enable security codes A through P.
- Create an Operator account, assign a password, enable code A, and leave codes B through P disabled.
- Add Login and Logout controls to an accessible display. Add a user display indicator so testing shows which account is active.
- For a touchscreen terminal, provide the project's popup keyboard so users can enter credentials.
- Open the settings of the display that requires protection and assign code B or another code not granted to Operator.
- Run the application. Confirm that Operator can open code-A displays but cannot open the protected display, while Engineer and Calibration can open it.
Troubleshoot an immediate exit during testing
If removing a security right causes the test to exit before showing the application, inspect the startup display and every navigation step needed to reach Login. A supported diagnostic hypothesis is that the active default account loses access to an initial display or required navigation path; the evidence does not confirm this as a FactoryTalk View ME version 5 defect.
Retest after making the login surface reachable by the default session. Verify the active username in the user display indicator, then test Operator and Engineer separately. The evidence describes display-level security only and does not establish a valid method for applying a password directly to an individual button.
FAQ
How do I password-protect a display in FactoryTalk View ME?
Create password-protected user accounts, assign their A-through-P security rights, and set the target display's security code to a letter granted only to authorized accounts.
Why does my PanelView 700 Plus application exit after I disable a security code?
Check whether the default account can still access the startup display and the navigation path to Login. The reported symptom is consistent with an inaccessible startup path, but the evidence does not confirm the exact cause.
Can I apply FactoryTalk View ME security directly to one button?
The available evidence supports assigning security codes to displays, not directly to individual buttons. Verify button-level security capabilities in the exact FactoryTalk View Studio ME version 5 configuration before relying on that design.