Skip to content

DigitalOsc guides

One Press Counts Twice: Check Switch Bounce

DigitalOsc editorial team · Updated 19 November 2026

Capture a switch input during one press and separate contact bounce from repeated presses reported by firmware.

Observe the pin the firmware reads

Use a low-voltage button circuit with a known input bias. Look at the microcontroller pin, not just the switch terminals. A floating input is a different fault: if the open switch does not produce a stable idle level, inspect the pull-up or pull-down and wiring before calling anything bounce.

Capture one event

On one deliberate press, capture both the first transition and the final stable level. In a teaching example, the trace crosses between high and low for the first 4 ms and then stays low. That supports applying a debounce decision to the measured switch; it does not prove every press behaves the same. Take a few slow and quick presses and include release edges. A press that reports twice when the pin makes one clean transition suggests checking firmware edge selection and event handling.

Decide before replacing parts

Use a single channel for the pin if you can repeat the symptom. Add a second to a debug output only if you need to see whether firmware produced duplicate events for one transition. Treat the longest observed chatter as a test input for the debounce window, and check the required response time before lengthening it.

Useful next steps

References