PID Faceplate Operator Controls Greyed Out in PCS 7 V6.1 FB61

Problem: Operator Cannot Change Setpoint or Mode on PCS 7 PID Faceplate

A configured PID loop in a SIMATIC PCS 7 V6.1 project generates a WinCC faceplate correctly, but the faceplate prevents the operator from selecting the operating mode, modifying the setpoint, or changing the manipulated value. The Mode and Setpoint input fields do not show the expected drop-down arrows, and the SP and MAN fields stay grey rather than switching to a white background that would indicate writable state. The same symptoms occur even when the user logs on to WinCC with an account that holds the Process controlling authority (level 5), and the Q_SP_OP and AUT_ON_OP status bits on the FB61 instance are already set high.

This symptom is one of the most reported operational issues on PCS 7 V6.1 with the APL (Advanced Process Library) controller block FB61 CTRL_PID, and it almost always traces to one of three configuration gaps: a missing operator enable input, an incorrect operator authorization level, or a WinCC user administration that has not been synchronized with the project.

Affected Environment

Technical Background: FB61 CTRL_PID Operator Path

FB61 CTRL_PID is the standard PID block of the PCS 7 APL. It exposes two parallel paths for the operator: one to drive the setpoint, one to switch the operating mode. Both paths are guarded by dedicated boolean enable inputs that are evaluated inside the block before the corresponding output bits are written. WinCC reads those output bits and toggles faceplate interactivity through the C-script logic embedded in the standard APL faceplate.

The faceplate evaluates SP_OP_EN, MANOP_EN, and AUTOP_EN against the controller's current state and against the operator's authority level. If any of those three values is FALSE, the corresponding faceplate control remains disabled and is rendered with a grey background. The standard WinCC scripts in the APL faceplate raise a system message (operator note 10110 / 10111) and update the icon and the right-hand status column to indicate that operator control is blocked.

Technical Background: WinCC Authority Levels in PCS 7

PCS 7 inherits WinCC's user administration model, which assigns each user an authority level from 0 to 9. The level used by the PID faceplate is set in the block instance via the AUTH_OME parameter, and WinCC compares this against the logged-in user's level. The default mapping used by the standard APL PID faceplate is:

The faceplate compares the user's assigned highest level against the level encoded in AUTH_OME. For the standard APL PID faceplate, the typical default value of AUTH_OME is 5 (Process controlling). If the user has been granted at least that level, operator setpoint and mode writes are accepted at the faceplate level. If the user is below that level, every operator write is rejected and the field stays grey.

Root Cause Analysis

Three independent root causes - and any combination of them - can produce the exact symptom set described (greyed Setpoint field, greyed Mode field, no drop-down on either, but the status bits Q_SP_OP and AUT_ON_OP already TRUE):

Root Cause A: Operator Enable Inputs Are Not All TRUE

The most common root cause is that one or more of SP_OP_EN, MANOP_EN, and AUTOP_EN is FALSE on the FB61 instance. The faceplate reads these directly to decide whether to render the input field as interactive. If MANOP_EN is FALSE, the faceplate cannot transition the block to manual from the operator path, so the MAN field stays grey. If AUTOP_EN is FALSE, the same applies for the auto transition. If SP_OP_EN is FALSE, the operator cannot write the setpoint even if the controller is already in auto.

The Q_SP_OP and AUT_ON_OP bits can both be TRUE because the block continues to hold the previously-acknowledged operator state, even though a fresh write from the faceplate would now be refused. Bits being TRUE is therefore not a sufficient indicator that the faceplate path is open.

Root Cause B: WinCC User Administration Is Not Synchronized

PCS 7 V6.1 stores the user database in the WinCC project. The supervisor account shown in the symptom report has been configured in SIMATIC Manager, but the WinCC OS project must be re-transferred and re-started for the WinCC-side user table to pick up the change. If the OS was not re-compiled and re-started after the user was added, the logged-in session may be authenticating against the old user table, in which case the user is unknown and is treated as level 0.

Root Cause C: Authority Level Required by the Block Is Higher Than the User Holds

If AUTH_OME on the FB61 instance was customized to a value higher than 5 (for example, 6 for Higher process controlling), the supervisor user at level 8 is fine, but if the block uses a default of 6 and the user only has level 5 enabled, the faceplate refuses. The most reliable check is to look at the actual AUTH_OME value on the instance DB, not at the level displayed in the WinCC user administrator.

Step-by-Step Resolution

Step 1: Verify FB61 Operator Enable Inputs

1. Open the SIMATIC Manager and navigate to the S7 program that owns the FB61 instance.
2. Open the instance DB (for example, DB701) in the LAD/FBD/ST editor.
3. Switch the view to Data View (or to Instance DB - All if you need to see the offline values).
4. Confirm the following structure entries are all TRUE:

DBxy.SP_OP_EN     := TRUE;   // operator may write setpoint
DBxy.LMNOP_EN    := TRUE;   // operator may write MV
DBxy.MANOP_EN    := TRUE;   // operator may switch to MAN
DBxy.AUTOP_EN    := TRUE;   // operator may switch to AUT

5. If any value is FALSE, trace the upstream logic that drives it. In a stock APL project these are usually hard-wired to TRUE or driven by a process-enable tag. Many V6.1 installations wire them through a Operator Enable CFC chart that needs to be set to TRUE before operator control is released.
6. Download the corrected instance DB to the AS.

Step 2: Verify AUTH_OME on the Instance

1. In the same instance DB, locate the AUTH_OME entry (WORD or INT type, depending on APL revision).
2. Confirm it is set to a value of 5 or lower if you want a level-5 user to be able to operate the loop. PCS 7 V6.1 ships with a default of 5.
3. If it has been raised, either lower it to 5, or add the missing authority level to the user account (see Step 3).

Step 3: Verify WinCC User Configuration

1. In the WinCC Explorer of the OS server, open User Administrator.
2. Confirm the user supervisor exists and that the Authorization column on the Authorizations tab shows a numeric value greater than or equal to the AUTH_OME of the block (typically 5).
3. If the user is in the AS project (SIMATIC Manager) but not in the OS project (WinCC), right-click the OS, choose Object Properties > OS > User Administrator, and confirm the user table source.
4. Re-compile the OS and re-transfer the runtime to the OS server. The OS user database is part of the runtime files; changes made on the engineering station only reach the OS after a delta or full transfer.
5. Restart WinCC Runtime on the OS server.

Step 4: Verify the Password Level Setting on the Faceplate

1. Open the WinCC Graphics Designer and the PID faceplate (for example, @PG_PID_TYPE1.PDL).
2. Open the Properties dialog of the Mode and Setpoint I/O field objects.
3. Confirm the Password Level on the operator input is set to a value of 5 or lower, matching the user authorization. In PCS 7 the standard template uses level 5 for the operator setpoint field.
4. Save the picture, close the Graphics Designer, and re-transfer the OS pictures.

Step 5: Hot-Reload the Faceplate and Re-Test

1. On the OS client, log out the test user.
2. Log back in as supervisor with the same password.
3. Open the loop's standard view. The Setpoint and Mode fields should now be white with the drop-down button visible on the right edge.
4. Switch the controller to MAN, then to AUT, then write a new setpoint. Each change should generate an operator message in the WinCC Alarm Logging and the corresponding Q_SP_OP / MAN_ON_OP / AUT_ON_OP bits should flip accordingly.

Verification Checklist

Troubleshooting Matrix

Common Pitfalls in PCS 7 V6.1

Pitfall 1: Bits vs. Inputs

Q_SP_OP and AUT_ON_OP are outputs of the block. They report what the block believes is the current state of the operator path. They do not enable the faceplate. The enable path is SP_OP_EN, MANOP_EN, AUTOP_EN, LMNOP_EN — those are inputs, and they are the ones that must be TRUE. Engineers often fixate on the status bits being correct and miss the fact that the enable inputs have never been raised since the last AS download.

Pitfall 2: User Administration Mismatch Between AS and OS

PCS 7 has two distinct user stores: the AS-side user table (managed from SIMATIC Manager under AS Object > User) and the OS-side user table (managed from WinCC Explorer). In V6.1 the OS side is the authoritative source at runtime; the AS-side table is for WinCC login validation and is checked by the OS only when configured to do so. If the user was added only to the AS, the OS still uses the old user table. Re-compile the OS and re-transfer the runtime to refresh.

Pitfall 3: AUTH_OME Hidden Behind a Custom Default

The PCS 7 APL allows per-instance override of the operator authorization threshold. If someone set AUTH_OME := 6 for this controller (for example, to require Higher process controlling for tuning access), the user must hold level 6 or higher. A level-5 user cannot write setpoints even if all enable bits are TRUE. The fix is either to lower AUTH_OME or to grant the user the additional level.

Pitfall 4: Password Level on the Picture Object

The WinCC I/O field on the faceplate picture has its own Password Level property. The standard APL template sets it to 5, but customized pictures sometimes leave it at 0 or at a higher value. If the picture-level value is higher than the user, the field stays grey. Open the picture in Graphics Designer, click the field, and verify the property in Object Properties > Miscellaneous > Password Level.

Pitfall 5: Re-Download Re-Initializes Enables

A full AS download with Reset re-initializes instance DBs to the value stored in the offline DB. If the offline DB has SP_OP_EN = FALSE because it was never edited offline, the post-download runtime will be FALSE even if the online view once showed TRUE. The fix is to edit the offline instance DB, set the enables to TRUE, save, and download.

Related Siemens Tools and Documentation

For projects that combine PCS 7 with add-on faceplates (for example, CEMAT libraries in cement applications), the server name on the picture's properties dialog may need to be explicitly set to the correct CTRL_PID block instance. The Siemens support article 23898368 covers the configuration of multiple faceplate types on the same OS. The same pattern (Servername property pointing at the wrong block) is worth checking when a greyed-out faceplate is paired with a working identical loop on the same OS.

Cross-Vendor Note: Similar Faceplate Patterns

The greyed-out faceplate pattern is not unique to PCS 7. PlantPAx faceplates for the Rockwell Logix-based Process Controller use a similar layered model with faceplate-level authorization (FactoryView security), faceplate-level enable, and a controller-level operator enable. The PlantPAx faceplate instructions at PROCES-RM203 describe the CV entry field enable, which corresponds to the same enable-input concept as LMNOP_EN on FB61. The fix pattern (raise the enable bit, raise the user authority, re-transfer the runtime) is identical across vendors. C-more faceplates from AutomationDirect (see C-more PID Faceplate Bar Meter) follow a similar two-level model.

Field-Proven Sequence to Apply in V6.1

1. Open the instance DB, set SP_OP_EN, LMNOP_EN, MANOP_EN, AUTOP_EN to TRUE.
2. Confirm AUTH_OME is 5 (or matches the user level).
3. Compile the OS, transfer the runtime, restart WinCC Runtime on the OS server.
4. Re-distribute the picture package to all OS clients.
5. On the OS client, log in as the supervisor user, open the loop's standard view, verify the field is white.
6. Test mode change MAN→AUT and a setpoint change. Confirm Q_SP_OP and AUT_ON_OP follow.
7. If only the tuning tab is grey, grant the user level 6 (Higher process controlling).

FAQ