Difference between revisions of "Debouncing Microcontroller Inputs"
Russ hensel (talk | contribs) (→Links) |
Russ hensel (talk | contribs) |
||
| Line 15: | Line 15: | ||
== Method 2: Do not Ignore it == | == Method 2: Do not Ignore it == | ||
| − | + | Fix in hardware, software or both.... more comming, but see links for now | |
Latest revision as of 14:04, 3 January 2013
Debouncing[edit]
under construction
Debouncing is used on switches that are providing digital input to a device like a micro controller – here we will assume that the input is a micro controller. When the state of the switch is changed from open to closed and vise versa there is often a short period of time when the switch make many rapid transitions between open and closed. These transitions are called bouncing and they often cause problems in the application where the assumption is made that actuating the switch once caused only one transition. Getting rid of the effect of the transitions is called debouncing.
There are two general way of getting rid of the bounces, one called hardware debouncing add circuitry that actually gets rid of the unwanted transitions, the other is called software debouncing and causes the application to ignore the bounces.
Note: if the button press triggers an interrupt then the bounce may cause more problems than code that just polls the button state.
Method 1: Ignore it[edit]
This is actually a method that can work under some conditions. Suppose you have a lid you want opened when a button is pressed. Bounce may not matter for a couple of reasons: the lid can only be opened once so a bounce will not open it twice ( but bad code may be confused by the bounce ), the delay involved in opening the the lid will give time for the bouncing to end.
Method 2: Do not Ignore it[edit]
Fix in hardware, software or both.... more comming, but see links for now
