Arduino OOP - Debounce the Button Inside the Class

The video tutorial addresses the common issue of button bounce in hardware push buttons. It explains how to implement debounce functionality in software to ensure accurate button state readings. The tutorial covers adding private attributes, initializing them in the constructor, and modifying the read state method to incorporate debounce logic. The implementation is designed to be transparent to users, maintaining the public interface unchanged. The tutorial concludes with finalizing and verifying the class implementation.

What is the main issue with push buttons that requires debouncing?

• They can get stuck in one state.

• They require a lot of power.

• They can bounce between states rapidly.

• They can only be pressed once.

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

• To store the initial state of the button.

• To track the last time the button was pressed.

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

• To keep track of when the button state last changed.

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

• To ensure the code runs faster.

• To avoid mixing time units and causing errors.

• To make the code easier to read.

• To reduce memory usage.

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

• The state is updated to a default value.

• The state is reset to zero.

• The state remains unchanged.

• The state is stored as a new state.

What is the initial action taken in the init method regarding the button state?

• The state is set to high.

• The state is ignored.

• The state is read using digitalRead.

• The state is set to a default value.

How does the debounce functionality affect the public interface of the class?

• It makes the public interface more complex.

• It requires changes to the public interface.

• It simplifies the public interface.

• It does not affect the public interface.

What is the main benefit of implementing debounce functionality in software?

• It reduces hardware costs.

• It increases the speed of the button.

• It ensures accurate state readings without hardware changes.

• It allows for more button presses.