How to Troubleshoot FOUNDATION Fieldbus DO Block Command Rejection on Actuators in PCS 7 and SIMATIC PDM

In PCS 7 FOUNDATION Fieldbus (FF) installations, Discrete Output (DO) function blocks on actuators (such as Rotork motorized valves) reject open/close commands sent to CAS_IN_D because the block's operational mode is set to AUTO instead of Cascade (CAS). Under the FF specification, an output block in AUTO mode only responds to its internal setpoint (SP_D), ignoring external cyclic commands. To resolve this, open SIMATIC PDM, navigate to the actuator DO function block, set MODE_BLK.TARGET to CAS, ensure PERMITTED mode includes CAS, download the parameterization, and verify that the CAS_IN_D interconnection delivers a Good_Cascade signal status from the CFC chart.

FOUNDATION Fieldbus Architecture and Function Block Mode Machine

SIMATIC PCS 7 integrates FOUNDATION Fieldbus (FF) H1 field devices via the Compact FF Link or FDC 157 coupler modules. In an FF architecture, intelligence is distributed directly into field instrumentation: actuators, positioners, and transmitters execute standardized function blocks (such as AI, AO, DI, DO, and PID) locally within the device firmware.

Central to all FF function blocks is the Mode Machine (MODE_BLK), which governs how the block processes setpoints and commands:
* Target Mode (MODE_BLK.TARGET): The desired operational state assigned by the engineer or supervisory system.
* Actual Mode (MODE_BLK.ACTUAL): The current operating mode calculated by the block based on device health, schedule execution, and signal status.
* Permitted Mode (MODE_BLK.PERMITTED): The set of allowable modes defined during engineering to prevent unauthorized mode shifts.
* Normal Mode (MODE_BLK.NORMAL): The expected baseline operating state for normal plant conditions.

Why DO Function Blocks Reject Commands via CAS_IN_D in AUTO Mode

When an automation engineer links PCS 7 CFC chart logic to an FF actuator DO block:
* The cyclic control command from the AS is mapped to the input parameter CAS_IN_D (Cascade Input Discrete) or RCAS_IN_D (Remote Cascade Input Discrete).
* If the actuator DO function block is configured with its Target Mode set to AUTO, the block algorithm exclusively evaluates the internal operator setpoint SP_D.
* The block completely ignores all data arriving at CAS_IN_D while in AUTO mode.
* To force the DO function block to accept dynamic cyclic commands sent from the PCS 7 controller across the fieldbus link, the block's Target Mode must be set to CAS (Cascade).
* Furthermore, if the device's local selector switch (e.g., on the Rotork actuator local control panel) is set to LOCAL rather than REMOTE, the hardware override forces the DO block into MAN (Manual) or LO (Local Override) mode, discarding both AUTO and CAS commands.

Signal Status (Quality Code) Requirements for Fieldbus Interconnections

In FOUNDATION Fieldbus, every data value is accompanied by a mandatory Status Byte conforming to IEC 61804. A value is not accepted merely because its boolean state is 1 or 0; its status byte must validate the signal:

CAS_IN_D requires a status of Good_Cascade (Quality Byte value 16#C0 to 16#C8) or Good_NonCascade (16#80).
If the PCS 7 CFC chart outputs a command with a Bad status (e.g., 16#00), the DO block detects a transmission failure.
Upon detecting bad quality, the DO block automatically initiates its configured failsafe response:
FSAFE_TYPE: Defines the behavior on communication loss (e.g., Use FSAFE_VAL_D, Hold Last Value, or Go to Failsafe State).
FSAFE_VAL_D: The discrete failsafe value applied to the actuator (0 = Close, 1 = Open).
If the AS fails to refresh the cyclic schedule within the configured communication timeout (SHED_TIME), the block transitions from CAS to MAN or AUTO automatically.

Step-by-Step Procedure to Parameterize DO Blocks in SIMATIC PDM

To configure a Rotork actuator or any FF discrete output device to accept PCS 7 control commands, follow this procedure:

Open SIMATIC PDM:
* In SIMATIC Manager, locate the FF device in the Plant View or Process Device Network View.
* Right-click the actuator device and select Open Object to launch SIMATIC PDM.
Navigate to the Discrete Output (DO) Block:
* In the PDM tree, expand the device parameter hierarchy and select DO Block (or DO1).
Configure Mode Parameters (MODE_BLK):
* Locate MODE_BLK.PERMITTED. Ensure that both AUTO and CAS (and optionally OOS, MAN) are selected.
* Change MODE_BLK.TARGET from AUTO to CAS.
* Verify that MODE_BLK.NORMAL is set to CAS.
Configure Failsafe Behavior:
* Inspect parameters FSAFE_TYPE and FSAFE_VAL_D. Set them according to plant safety requirements (e.g., Fail-Closed or Fail-Last).
Download to Device:
* In SIMATIC PDM, select menu Device > Download to Device....
* Choose Entire Device or Selected Object and confirm the download.
Verify Physical Actuator State:
* Check the local control display on the actuator housing.
* Ensure the local padlock/selector key switch is turned to REMOTE or AUTO mode.

Comparison of FOUNDATION Fieldbus Function Block Modes

The table below outlines the behavior of FF output function blocks across different operating modes.

Operating ModeAbbreviationCommand SourceSetpoint HandlingApplication ContextOut of ServiceOOSNoneBlock execution haltedMaintenance, commissioning, firmware updatesManualMANPDM / LocalOperator writes directly to OUT_DEmergency manual override, testingAutomaticAUTOPDM / OperatorBlock algorithm evaluates internal SP_DAutonomous local setpoint controlCascadeCASAS ControllerBlock accepts cyclic command via CAS_IN_DStandard PCS 7 closed-loop automated controlRemote CascadeRCASSupervisory HostBlock accepts setpoint via RCAS_IN_DAdvanced supervisory control / MESLocal OverrideLOPhysical SwitchLocal hardware interlock drives OUT_DValve maintenance handwheel or trip contact

Verification

To confirm that the DO block accepts open/close commands:
1. In SIMATIC PDM, check the online view of the DO block: verify that MODE_BLK.ACTUAL reports CAS.
2. In the PCS 7 CFC chart, toggle the digital control output connected to CAS_IN_D.
3. Verify that the actuator initiates movement (motor engages, valve stem travels toward open or closed position).
4. Monitor the Discrete Input (DI) feedback blocks in CFC: confirm that end-position switches (POS_OPEN, POS_CLOSE) update to reflect the physical travel of the actuator.
5. In WinCC Runtime, open the valve faceplate and verify that command transit alarms extinguish and the valve icon transitions to the commanded state.

Limitations and Operational Precautions

Never change fieldbus function block modes from SIMATIC PDM while the process unit is actively operating, as changing mode targets can trigger immediate actuator motion.
Ensure that the FOUNDATION Fieldbus macrocycle schedule downloaded from Fieldbus Builder leaves sufficient communication bandwidth for cyclic publisher-subscriber exchanges.
Verify that physical bus segment termination and spur lengths conform to the FF-816 physical layer specification (maximum segment length 1900 m, maximum spur length 120 m).
Verify that write protection (WRITE_LOCK) is disabled in the actuator parameters prior to attempting PDM configuration downloads.

Engineer FAQ

Why does MODE_BLK.ACTUAL remain in MAN even when TARGET is set to CAS?

If MODE_BLK.ACTUAL cannot achieve CAS, a blocking condition exists. Common causes include: the physical actuator selector switch is set to LOCAL, an active hardware interlock contact is open, or the quality status of CAS_IN_D is Bad, forcing the block into failsafe mode.

What is the difference between CAS_IN_D and SP_D?

SP_D (Setpoint Discrete) is the internal setpoint used when the block operates in AUTO mode, typically entered manually by an operator via PDM. CAS_IN_D (Cascade Input Discrete) is the external communication channel used in CAS mode to receive automated commands from the PCS 7 AS chart.

Why did the feedback signals work while output commands failed?

Feedback signals originate from Discrete Input (DI) or Analog Input (AI) blocks. In these input blocks, values are published cyclically to the AS without requiring cascade mode transitions. Output blocks (DO/AO) require strict mode synchronization (CAS) before they permit external logic to drive physical outputs.

Technical References

Related Tags

FOUNDATION Fieldbus
SIMATIC PDM
Rotork Actuator
CAS_IN_D
MODE_BLK

How to Troubleshoot FOUNDATION Fieldbus DO Block Command Rejection on Actuators in PCS 7 and SIMATIC PDM