Debounce & Filtering for Proximity Sensors in Oily Roll Forming Environments

Introduction — Why Proximity Sensors Become Unreliable in Roll Forming Lines

Roll forming machines operate in a harsh environment for sensors. Even on clean lines, proximity sensors are exposed to:

• rolling oil
• metal dust
• swarf
• vibration
• electrical noise
• changing strip positions
• mechanical shock

In oily environments, proximity sensors often produce unstable signals. A sensor may appear to switch on and off rapidly even though the target is present continuously. In PLC terms, this creates false transitions, double triggers, missed events, and unreliable sequence behavior.

Typical symptoms include:

• double counting panels
• random punch triggers
• shear sequence faults
• stacker miscounts
• interlocks that flicker
• machine start permissives that come and go
• nuisance alarms

This is why debounce and signal filtering are so important in roll forming PLC programs.

A properly designed debounce strategy makes dirty real-world sensor signals behave like clean machine logic. Without it, even a mechanically sound machine can feel unstable and difficult to troubleshoot.

What Debounce Means in PLC Control

Debounce is the process of preventing the PLC from reacting to very short unwanted signal changes.

In simple terms, the PLC does not accept a sensor transition immediately. Instead, it waits to see whether the signal remains stable for a minimum time.

This is important because a proximity sensor in an oily machine may produce a short false pulse due to:

• oil film movement
• edge vibration
• misalignment
• cable noise
• mechanical chatter in the sensed object

Debounce prevents that short pulse from being treated as a real machine event.

Why Filtering Is Different from Debounce

Debounce and filtering are related, but they are not exactly the same.

Debounce

Debounce is usually used for discrete transitions.
Example: only accept the sensor ON state if it stays ON for 30 ms.

Filtering

Filtering is a broader concept. It may include:

• on-delay filtering
• off-delay filtering
• pulse rejection
• signal averaging for analog values
• edge qualification
• noise suppression logic

In roll forming PLCs, the most common form is discrete on/off filtering for digital proximity sensors.

Why Oily Environments Make Sensors Worse

Oil creates several real problems for proximity sensing.

Oil Film Changes the Sensed Edge

If the sensor is detecting a passing metal edge, the oil layer can slightly alter the transition behavior. The edge may not appear crisp to the sensor.

Oil Carries Dirt and Metal Dust

Oil often collects fine metallic debris. That debris can affect inductive sensing, especially where clearance is already marginal.

Oil Encourages Mechanical Vibration Effects

Slippery surfaces and changing strip behavior can create slight flutter near the sensor target zone.

Oil Hides Mechanical Misalignment

A sensor that is only barely aligned may still work sometimes, but the oil contamination makes the switching point inconsistent.

Because of this, the PLC should never assume that a raw field signal is perfect.

Common Places Where Debounce Is Needed in Roll Forming Machines

Not every sensor needs the same filtering, but certain sensors almost always benefit from debounce logic.

Strip Presence Sensors

Used at entry sections, levelers, punch lines, and coil end detection points.

Problems may include:

• strip flutter
• oily reflective surfaces
• unstable leading or trailing edge detection

Shear Home and Shear Down Sensors

These sensors often sit near hydraulic motion, vibration, and oil mist.

Problems may include:

• false transitions during mechanical impact
• rapid flicker near the switching point
• contamination around mounting brackets

Punch Position Sensors

Punch systems are exposed to vibration and impact.

Problems may include:

• multiple transitions from a single stroke
• false “home” or “down” detection
• noisy return signals

Stacker and Panel Count Sensors

Panel edges may vibrate or pass unevenly.

Problems may include:

• double counts
• missed counts
• unstable trailing edge detection

Guide Position and Setup Confirmation Sensors

These signals often affect permissives and machine readiness.

Problems may include:

• flickering start conditions
• false not-ready alarms
• setup mode confusion

Typical Signal Problems Seen in PLC Logic

When raw proximity signals are not filtered properly, the PLC may show several patterns.

Flickering Input Bit

The online PLC input changes between 0 and 1 rapidly when the target is near the sensor.

Multiple Event Counts from One Physical Event

One panel passes once, but the PLC counts it twice or three times.

Sequence State Faults

The machine enters a sequence state expecting one transition, but receives several unstable changes instead.

Interlock Instability

A permissive such as “shear home” becomes true, false, true, false within a short period, preventing the next action.

Why You Should Not Rely Only on Hardware Sensor Settings

Some sensors include built-in response adjustment or filtering. That can help, but it is usually not enough on its own.

Reasons include:

• field devices vary by supplier
• replacement sensors may not be set identically
• hardware filtering may not match machine sequence timing
• PLC logic still needs consistent event qualification

The best practice is:

Use good sensor hardware and good PLC debounce logic together.

Basic PLC Debounce Pattern

The most common digital debounce pattern is simple:

• when raw input turns ON
• start a timer
• only set filtered input ON if raw input stays ON until timer completes

The same can be done for OFF transitions if required.

This gives you a filtered signal such as:

• Raw sensor input
• Filtered sensor input

The PLC should then use the filtered signal for machine logic, not the raw signal.

ON-Delay Filtering Pattern

ON-delay filtering is used when false short ON pulses are the problem.

Example:

A strip presence sensor briefly flickers ON because oil or vibration causes a temporary detection.
You do not want the PLC to react unless the signal stays ON long enough to be real.

Typical logic:

• Raw input goes ON
• Start ON-delay timer
• If raw input remains ON for preset time, set filtered input ON
• If raw input drops before timer completes, reset timer

This is very effective for rejecting short false detections.

OFF-Delay Filtering Pattern

OFF-delay filtering is used when the signal momentarily drops out but should still be considered valid.

Example:

A home sensor is active, but slight vibration causes the signal to disappear for 10 ms.
You do not want the PLC to think the actuator left home.

Typical logic:

• Raw input goes OFF
• Start OFF-delay timer
• If raw input remains OFF for preset time, set filtered input OFF
• If raw input returns before timer completes, keep filtered signal ON

This is useful for stability in permissive logic.

Combined ON and OFF Filtering

In many roll forming applications, the best solution is to filter both transitions.

That means:

• require ON to be stable for X ms
• require OFF to be stable for Y ms

This creates a much cleaner signal for the PLC sequence.

Typical use cases include:

• shear home sensors
• punch home sensors
• panel detect sensors
• stacker ready sensors

How Much Debounce Time Should You Use?

This is one of the most important practical questions.

If the debounce time is too short:

• nuisance signals still get through

If it is too long:

• real machine response becomes sluggish
• high-speed events may be missed

Typical practical starting points:

5 to 15 ms

Good for fast, fairly clean sensors with minor electrical noise.

20 to 50 ms

Common for oily proximity sensor applications in hydraulic and forming environments.

50 to 100 ms

Useful where vibration is severe or where the signal is only used as a permissive and not for high-speed counting.

The correct value depends on the function of the sensor.

Match the Filter to the Function

Not all sensors should use the same debounce value.

Safety-Related Status Signals

These are often handled by dedicated safety hardware, not normal PLC debounce logic. Do not casually delay safety behavior in standard logic.

Sequence Permissives

Examples:

• shear home
• punch ready
• stacker home

These can often tolerate slightly longer filtering because they are not ultra-fast dynamic events.

Panel Counting Sensors

These often need shorter, carefully tuned filtering because the machine may be running at speed and you do not want to miss a real event.

Position Event Triggers

Examples:

• punch window detect
• notch trigger confirm

These usually need careful engineering so the filter does not distort timing.

One-Shot Logic After Filtering

A filtered signal alone is not always enough.

If the PLC needs to react only once per event, you should also use edge detection or a one-shot after filtering.

Example:

• raw panel sensor flickers
• filtered panel sensor becomes stable
• one-shot generates one count only

This prevents one long sensor signal from causing repeated counts across multiple scan cycles.

A very common best practice is:

Raw input → Filtered input → One-shot → Sequence logic

Debounce for Panel Counting Sensors

Panel count sensors are a good example of why both filtering and one-shot logic matter.

Without filtering:

• one vibrating panel edge may create multiple transitions

Without one-shot logic:

• one long sensor ON state may count repeatedly if the logic is poorly written

A robust pattern is:

1. Filter the panel sensor
2. Detect rising edge only
3. Count once
4. Optionally lock out additional counts until the sensor fully clears

That last step is important for preventing double counts on overlapping or vibrating edges.

Debounce for Shear Home Sensors

Shear home sensors are often heavily affected by:

• impact
• vibration
• oil mist
• sensor bracket flex

A good shear home strategy often uses:

• ON filtering to confirm home is truly reached
• OFF filtering to prevent nuisance dropout
• timeout supervision if home is not reached within expected time

This means the PLC does not just trust one raw flicker of the sensor.

It waits for a stable confirmation.

Debounce for Punch Home and Punch Down Signals

Punch systems often generate harsh mechanical shock.
That means punch home and punch down sensors can chatter.

A robust punch signal strategy often includes:

• filtered home input
• filtered down input
• one-shot sequence acceptance
• cycle timeout supervision
• state-based signal expectations

For example, the PLC should only care about punch down during the correct sequence state. That alone reduces nuisance responses.

State-Based Filtering Logic

This is a higher-level best practice.

Sometimes the best filtering is not just time filtering, but also state-aware logic.

Example:

• only accept punch down signal if the PLC is currently in PunchCycleActive state
• only accept shear home return if the PLC is in WaitForHome state
• only accept stack complete sensor if stacker cycle is active

This reduces the chance that noise on a sensor will affect unrelated parts of the machine sequence.

Filtering vs Missed High-Speed Events

This is a real engineering tradeoff.

If you over-filter a sensor used for a fast event, the PLC may react too late or miss the event entirely.

Examples where this matters:

• high-speed panel counting
• fast edge detect for print marking
• flying shear synchronization reference signals

In these cases, do not blindly use a long debounce timer. Instead, use:

• cleaner hardware installation
• shorter filtering
• one-shot logic
• state-based qualification
• high-speed input modules where needed

Filtering is not a substitute for correct sensor selection and installation.

Hardware Practices That Reduce PLC Filtering Problems

Software filtering works best when the hardware is already good.

Recommended field practices include:

Mount Sensors Rigidly

Flexible brackets create vibration-induced switching instability.

Keep Sensing Distance Sensible

Do not mount the sensor right at the limit of its switching range.

Protect from Direct Oil Spray

Where possible, shield the sensor from constant oil splash.

Use Proper Cable Routing

Keep sensor cables away from motor cables, VFD output wiring, and noisy hydraulic solenoids.

Use Shielding and Grounding Correctly

Bad wiring practice can create signal noise that no reasonable debounce logic can fully solve.

Choose the Right Sensor Type

Inductive, capacitive, photoelectric, or laser sensors all behave differently in oily environments. The PLC cannot fully fix the wrong sensor choice.

Recommended PLC Programming Pattern

A strong standard pattern for a proximity input in a roll forming machine is:

Step 1 — Raw Input Mapping

Map the hardware input to a raw internal tag.

Example concept:
Raw_ShearHome

Step 2 — Filtering Layer

Create a filtered signal with ON and/or OFF filtering.

Example concept:
Filt_ShearHome

Step 3 — Edge Detection Layer

Generate rising or falling edge bits if the sequence needs one-time reactions.

Example concept:
ShearHome_Rise

Step 4 — Sequence Use

Only then use the filtered or edge-detected signal in machine logic.

This layered approach makes troubleshooting much easier.

Standard Signal Naming Recommendation

To keep programs clean, use consistent naming.

Example structure:

• Raw_PanelDetect
• Filt_PanelDetect
• Rise_PanelDetect
• Fall_PanelDetect

Or for a specific function:

• Raw_PunchHome
• Filt_PunchHome
• Rise_PunchHome

This makes the signal path obvious to anyone troubleshooting the PLC online.

Common Programming Mistakes

Using Raw Inputs Directly in Sequence Logic

This is one of the most common mistakes. It makes the sequence vulnerable to every bit of sensor instability.

Using the Same Filter Time for Every Sensor

Different sensors have different jobs. One fixed debounce time across the whole machine is rarely correct.

Filtering Too Much

If the timer is too long, real events become delayed or missed.

No One-Shot After Filtering

This often causes repeated counts or repeated sequence actions.

No State Qualification

A noisy input should not be able to affect every part of the machine at every moment.

Troubleshooting Sensor Noise Problems

When diagnosing unstable proximity signals, check in this order:

Step 1 — Watch the Raw Input Online

Does it flicker while the machine is stable?

Step 2 — Watch the Filtered Input

Does the filtered version behave correctly?

Step 3 — Inspect the Sensor Mechanically

Check alignment, bracket rigidity, distance, and contamination.

Step 4 — Check Cable Routing

Look for nearby VFD cables, motors, and hydraulic valve wiring.

Step 5 — Review Filter Time

Is it too short for the real environment, or so long that the machine response is delayed?

Step 6 — Check Edge Logic

If counts are still wrong, the problem may be repeated triggering after a valid filtered event.

Commissioning Checklist for Debounced Proximity Sensors

When commissioning a roll forming line, each important sensor should be checked with filtering in mind.

Verify Raw Sensor Operation

Confirm the target can be detected reliably.

Confirm Filtered Signal Behavior

Make sure filtered signal transitions cleanly and predictably.

Test at Low Speed and Production Speed

Some noise problems only appear at full operating speed.

Simulate Oily / Real Conditions

A sensor that works on a dry machine may behave differently after lubrication and production start.

Verify Sequence Stability

Ensure one physical event causes one PLC event.

Record Final Filter Settings

Document the debounce times used for each important sensor.

Best Practice Summary

For roll forming machines in oily environments, the best practical rule is:

Do not trust raw proximity signals directly in sequence logic.

Instead:

• map raw input
• filter it
• edge-detect it if needed
• qualify it by machine state
• then use it in the sequence

This produces cleaner machine behavior, fewer nuisance faults, and much easier troubleshooting.

FAQ — Debounce & Filtering for Proximity Sensors

Why do proximity sensors give false triggers in roll forming machines?

Because oily, vibrating, noisy environments can cause unstable switching, especially near metal edges, hydraulic motion, and moving strip material.

What is debounce in PLC logic?

Debounce is a delay-based method that only accepts a sensor change if the signal remains stable for a minimum time.

Should all proximity sensors use the same debounce time?

No. The debounce time should match the sensor’s job. Fast counting sensors need different treatment from static permissive sensors.

Why is one-shot logic important after filtering?

Because filtering stabilizes the signal, but one-shot logic ensures the PLC reacts only once to each physical event.

What is better for a noisy sensor: more filtering or better hardware?

Both matter, but better hardware installation should come first. PLC filtering should clean up the remaining real-world instability, not compensate for poor installation.

What is the best standard pattern for a proximity sensor in PLC code?

A strong pattern is: raw input, filtered input, edge detection if needed, then sequence logic. This makes the signal reliable and easier to troubleshoot.