C135 PCS 7 (PCS7)
6C
6 Cielo Ciencia y Tecnología
·Publicada en C135 PCS 7 (PCS7)

Troubleshooting 'Hide Parameter' Visibility Overrides in SIMATIC BATCH WinCC OCX Recipe Views

Troubleshooting 'Hide Parameter' Visibility Overrides in SIMATIC BATCH WinCC OCX Recipe Views

In SIMATIC BATCH (v8.0, v8.1, v8.2, and newer), when recipe parameters configured with the 'Hide parameter' option in the Master Recipe continue to remain visible to operators within the WinCC BATCH OLE Custom Control (OCX) viewer during runtime, the condition is caused by parameter visibility inheritance rules within hierarchical recipe objects or cached Process Cell data on the OS. Even if the 'Hide parameter' checkbox is selected in the master recipe header, if the parameter is configured as a mandatory setpoint at the Recipe Operation (ROP) or Equipment Phase (EPH) interface, or if the BATCH OS control properties are set to display all engineering parameters, the OCX control overrides hiding. To resolve this, engineers must update the parameter attribute across all recipe levels, perform an 'Update Process Cell' in Batch Control Center, and compile the BATCH OS objects.

Table of Contents

Hierarchical Parameter Inheritance in SIMATIC BATCH (ISA-88)

SIMATIC BATCH models recipe execution adhering strictly to the ISA-88 standard. In this hierarchy, recipe parameters cascade through multiple technological layers:
1. Equipment Phase (EPH / SFC Type): Defined on the S7 controller layer; establishes physical parameter limits, data types, and interface attributes.
2. Recipe Operation (ROP): Groups equipment phases into operational sequences.
3. Unit Procedure (UP): Coordinates operations within a physical processing vessel.
4. Recipe Procedure (RP) / Master Recipe: The top-level master recipe orchestrated by the batch server.

The 'Hide parameter' feature allows recipe authors to suppress internal calculation variables, tuning multipliers, or engineering constants, presenting operators with a clean, uncluttered setpoint interface in the WinCC Batch OCX Viewer (@pg_@batch_*.pdl).

Why the 'Hide Parameter' Option Fails to Conceal Variables in OCX Views

When an engineer checks 'Hide parameter' on a Master Recipe and finds that the parameter still appears in the runtime OCX control:

  1. Parameter Defined as Mandatory at Lower Layer: If the underlying SFC Type or Recipe Operation (ROP) has the parameter marked as 'Mandatory' or 'Operator input required', the lower-layer requirement takes precedence over the master recipe hide flag to prevent missing setpoints.
  2. Cached Process Cell Data on the OS: When master recipes are modified, the newly released recipe does not automatically update active WinCC OCX control caches until the OS server receives updated Batch OS Components.
  3. WinCC Batch OCX Property Override: The WinCC Batch ActiveX control properties (BatchRecipeView.ocx) possess an internal view filter setting: 'Show hidden parameters for privileged users'. If the logged-in operator account possesses engineering permissions, the OCX intentionally unhides all parameters for diagnostic auditing.

Equipment Phase (EPH) Interface Attributes vs Recipe Properties

To ensure consistent behavior, parameter properties must be aligned across both AS and BATCH:
- In the Master Data Library SFC Type: In the characteristics view, inspect the parameter attributes. If the attribute Hide in recipe is disabled, the SFC Type advertises the parameter as universally visible.
- In Batch Control Center (BCC): Open the Process Cell view. Under the Phase definition, verify that the parameter is not configured as a mandatory formula tag.

Step-by-Step Procedure: Enforcing Parameter Hiding Across the System

Follow this procedure to ensure parameters are hidden reliably:

Step 1: Configure Parameter in the Master Recipe

  1. In Batch Control Center (BCC), open the target Master Recipe.
  2. Double-click the target Recipe Operation or Phase.
  3. In the parameter table, check the box Hide parameter for the desired variable.
  4. If the parameter is linked to a formula, ensure the formula does not force operator input.

Step 2: Validate Recipe and Update Process Cell

  1. Select menu Recipe > Validate. Ensure 0 errors and 0 warnings are logged.
  2. Select Recipe > Release for production.
  3. In BCC, select the plant Process Cell root, right-click and choose PLC Data > Update Process Cell.
  4. Confirm synchronization with the S7-400 controllers.

Step 3: Compile and Download Batch OS Objects

  1. On the Engineering Station, open SIMATIC Manager.
  2. Right-click the BATCH object, select Compile.
  3. Check Transfer Messages and Compile OS Objects.
  4. Download the updated batch configuration to the active BATCH Server and OS Servers.

Step 4: Verify WinCC OCX Control Settings

  1. In Graphics Designer on the OS project, open the picture hosting the Batch OCX control.
  2. Double-click the Batch Recipe View OCX control to open properties.
  3. In the Display tab, ensure the checkbox 'Always show hidden parameters' is unchecked.
  4. Save the picture and deploy to runtime.

Comparative Visibility Matrix: SIMATIC BATCH Parameter Configurations

The table below outlines parameter visibility states:

SFC Type AttributeMaster Recipe SettingWinCC User RoleOCX Display StateMandatory InputHide Parameter CheckedOperatorVisible (Mandatory overrides hide)Optional ParameterHide Parameter CheckedOperatorHidden (Suppressed from operator)Optional ParameterHide Parameter CheckedEngineer / AdminVisible (Diagnostic privilege)Optional ParameterHide Parameter UncheckedAny RoleVisible (Standard setpoint)

Verification

To confirm that the parameter is properly hidden:
1. Batch Order Release Test: In BCC, create a new batch order using the released master recipe; release the order.
2. Operator Runtime Audit: Log in to WinCC Runtime under a standard Operator user account; open the Batch Control faceplate.
3. OCX Parameter Inspection: Verify that the parameter table omits the hidden variable while displaying all standard operational setpoints.

Limitations and Operational Precautions

Engineering teams must observe the following precautions:
- Never hide safety-critical setpoints (e.g., maximum reactor pressure or emergency vent temperature) from operators; hidden parameters cannot be intervened upon manually during emergencies.
- Active batches that were already released before the master recipe was modified will continue to execute with their original parameter visibility rules; parameter hiding takes effect only on newly created batch orders.
- Always validate final license quantities and MLFBs against the applicable Siemens catalog and authorized distributor quotation when scaling SIMATIC BATCH systems.

Engineer FAQ

Can operators unhide parameters dynamically during runtime?

No. Standard operators cannot unhide parameters. Only users with higher authorization levels (such as Production Supervisor or System Engineer) can toggle hidden parameter visibility in the OCX viewer.

Does hiding a parameter prevent it from being logged in the batch report?

No. Hidden parameters continue to be recorded in the electronic batch record (EBR) and historical SQL archives; hiding strictly conceals the value from the runtime operator display.

What happens if a hidden parameter value falls outside physical limits?

If a hidden parameter causes a limit violation, the equipment phase halts and triggers an alarm, but the operator will be unable to modify the value directly unless given engineering access.

Technical References

Related Articles

Related Tags

  • SIMATIC BATCH
  • OCX Controls
  • Hide Parameter
  • Master Recipe
  • WinCC BATCH
6 respuestas