Understanding Digital Input Flutter Suppression: Pcs7DiIn Message Filtering vs MonDiL Signal Debouncing

In SIMATIC PCS 7 APL, the flutter suppression parameters (FlutEn and FlutTmIn) on the channel driver block Pcs7DiIn are designed exclusively to suppress high-frequency hardware diagnostic alarm messages from flooding WinCC Alarm Logging; they do not filter or delay the physical boolean process signal PV_Out. To achieve true process signal debouncing and filter fluctuating field contacts, engineers must use the technological monitoring block MonDiL, where FlutTmIn introduces a configurable on/off delay timer on the process signal (Out), and FlutFactor supervises maximum allowable state transitions per minute before flagging a flutter alarm.

Channel Driver Alarming vs Technological Signal Debouncing

In industrial process plants, mechanical field contacts (such as vibrating limit switches, float switches in turbulent vessels, or pressure switches with mechanical contact bounce) frequently experience rapid, transient chattering between 0 and 1.

If unaddressed, contact chattering introduces severe operational disruptions:
1. Process Logic Instability: Chattering inputs can trip motor interlocks, restart sequence timers, or cause erratic controller behavior.
2. Alarm Flooding: Each state transition can generate a timestamped process alarm, inundating WinCC Alarm Logging with thousands of nuisance events per minute.

A common engineering error in SIMATIC PCS 7 is attempting to solve physical signal chattering by enabling FlutEn and FlutTmIn on the channel driver block Pcs7DiIn, only to discover that the process signal PV_Out continues to fluctuate instantaneously with zero dampening.

Pcs7DiIn Flutter Suppression Mechanics (Diagnostic Alarms Only)

The channel driver block Pcs7DiIn operates at the hardware abstraction layer, directly reading peripheral I/O words:

How `Pcs7DiIn` Handles Fluttering

Purpose: Pcs7DiIn flutter suppression is engineered strictly for hardware diagnostic alarm management (such as wire-break or module fault alarms chattering between 'Incoming' and 'Outgoing').
Behavior of FlutEn = 1: When enabled with a delay time FlutTmIn, the block monitors hardware diagnostic fault transitions. If diagnostic faults chatter faster than FlutTmIn, the block suppresses repeated alarm telegrams to WinCC.
Impact on PV_Out: Zero impact. The physical process measurement is transferred immediately to PV_Out every CPU execution cycle. The channel driver does not implement low-pass filtering, debounce delays, or signal smoothing on the process value.

MonDiL Signal Debouncing Mechanics (Process Value Filtering)

To filter, debounce, and stabilize the physical digital signal feeding automation logic, engineers must route Pcs7DiIn.PV_Out into the technological monitoring block MonDiL (Digital Process Value Monitoring):

How `MonDiL` Implements Signal Debouncing

MonDiL incorporates a dual-action digital filter and flutter supervision engine:
1. Signal Transition Delay (FlutTmIn):
* Introduces an on-delay and off-delay filter directly onto the process output Out.
* When input In transitions from 0 -> 1, Out remains 0 until In has stayed high continuously for the full duration of FlutTmIn.
* When In transitions from 1 -> 0, Out remains 1 until In has stayed low continuously for FlutTmIn.
* If FlutTmIn = 0.0, filtering is disabled and Out follows In immediately.
2. Frequency Monitoring (FlutFactor and FlutAct):
* FlutFactor sets the maximum allowable state transitions permitted within a 1-minute rolling window (e.g., FlutFactor = 5).
* If the input fluctuates more than 5 times within one minute, MonDiL asserts FlutAct = 1 and dispatches the process alarm: 'Flutter limits violated'.
* FlutAct automatically resets when the fluctuation rate drops below half the configured FlutFactor.

APL Digital Filtering Parameter and Function Comparison Matrix

The following table summarizes the functional differences between channel driver flutter suppression and technological monitoring:

Functional ParameterChannel Driver (Pcs7DiIn)Technological Block (MonDiL)Primary Architectural LayerHardware Channel Abstraction LayerProcess Automation Application LayerParameter Enabling FlutterFlutEn := 1FlutEn := 1Filter Delay ParameterFlutTmIn (seconds)FlutTmIn (seconds)Delays Physical Signal PV_Out/Out?NO (Passes raw signal instantly)YES (Delays transitions 0->1 and 1->0)Suppresses Alarm Flooding?Yes (Hardware diagnostic alarms)Yes (Process limit alarms)Fluctuation Frequency LimitNoneFlutFactor (transitions per minute)Flutter Alarm GeneratedModule fault suppression'Flutter limits violated' via FlutMsgEnRecommended Use CaseNoisy hardware diagnostic channelsChattering mechanical switches & level floats

Utilizing MonDiL provides complete protection against mechanical contact bounce.

Verification

To verify digital signal debouncing in CFC Test Mode:
1. Interconnect Pcs7DiIn.PV_Out to MonDiL.In.
2. On MonDiL, set FlutEn = 1, FlutTmIn = 3.0 (seconds), and FlutFactor = 5.
3. In CFC Test Mode, simulate contact bounce by toggling the input between 0 and 1 every 500 ms.
4. Observe MonDiL.Out: verify that the output remains completely stable at 0 because pulses are shorter than 3.0 seconds.
5. Hold the input high continuously for >3.0 seconds; verify that Out transitions to 1.
6. Rapidly toggle the input 6 times in 30 seconds; verify that FlutAct asserts 1 and the flutter alarm appears in WinCC Alarm Logging.

Limitations and Operational Precautions

Adding FlutTmIn delays process response; never apply long debounce delays to safety-critical inputs (e.g., emergency stop buttons, burner flame scanners, or high-pressure relief trips).
For extreme contact bounce on high-speed counting circuits, implement hardware RC filtering or use specialized digital input modules with configurable input delay in HW Config (e.g., 0.5 ms to 20 ms).
Ensure MonDiL is scheduled in an appropriate cyclic interrupt task (e.g., OB35 at 100 ms); setting FlutTmIn lower than the task execution cycle will result in zero filtering.
Always enable FlutMsgEn if operating personnel need visibility of deteriorating mechanical switches before total contact failure occurs.

Engineer FAQ

Why did `FlutTmIn` on `Pcs7DiIn` not stop my motor from chattering?

Pcs7DiIn only suppresses hardware diagnostic alarm messages from being sent to the OS; it does not delay or filter the physical process value (PV_Out). Use MonDiL to debounce the process signal.

Can I debounce digital inputs directly in HW Config without using `MonDiL`?

Yes. Many SIMATIC digital input modules (e.g., SM 321 / SM 421) allow configuring an 'Input Delay' (e.g., 3 ms or 20 ms) directly in HW Config module properties, which filters contact bounce at the hardware ASIC level.

What does `FlutAct` indicate on `MonDiL`?

FlutAct indicates that the digital input has exceeded the maximum allowable switching transitions per minute defined by FlutFactor, signaling a fluttering or chattering field contact.

Technical References

Related Tags

Pcs7DiIn
MonDiL
Flutter_Suppression
Signal_Debounce
Contact_Chatter

6 respuestas

Understanding Digital Input Flutter Suppression: Pcs7DiIn Message Filtering vs MonDiL Signal Debouncing