Debounce the Button Inside the Class

The video tutorial addresses the common issue of button bounce in hardware push buttons, which can cause incorrect readings. The instructor explains how to implement a debounce functionality in software to solve this problem. The solution involves adding private attributes to track state changes and debounce delay, initializing these in the constructor, and modifying the read state method to incorporate debounce logic. The implementation ensures that the debounce functionality is transparent to the user, maintaining the public interface unchanged.

What is the primary issue with push buttons that necessitates debouncing?

• They require a lot of power to operate.

• They can only be pressed once.

• They can bounce between high and low states rapidly.

• They can get stuck in a pressed state.

How does the software debouncing approach affect the main code and public interface?

• It requires additional hardware components.

• It requires significant changes to the main code.

• It adds private attributes without changing the public interface.

• It alters the public interface significantly.

What is the purpose of the 'last time state changed' attribute in the debounce implementation?

• To track when the button was last pressed.

• To count the number of times the button is pressed.

• To store the current state of the button.

• To keep track of the last time the pin state changed.

What is the role of the 'debounce delay' in the debounce functionality?

• To decrease the power consumption of the button.

• To increase the speed of state reading.

• To set a time period to ignore state changes after a bounce.

• To determine the maximum time the button can be pressed.

Why is it important to use the same time function (Millis or Micros) consistently in the debounce implementation?

• To ensure the code runs faster.

• To avoid mixing time units and ensure accurate time calculations.

• To reduce the memory usage of the program.

• To make the code easier to read.

What happens if the state of the button does not change during the debounce check?

• The state is stored as a new state.

• The button is reset to its initial state.

• The state remains unchanged and is not updated.

• The state is updated to a default value.

What adjustment is made during initialization to ensure the debounce functionality works correctly?

• The debounce delay is set to zero.

• The button is disabled temporarily.

• The state is read directly using digital read.

• The state is set to a default value.