millis vs. delay Part 4 | A mini-series on Timing Events with Arduino Code

This video tutorial explores the use of Arduino's Millis and delay functions to create repetitive timed events. It discusses the challenges of using the delay function when events overlap or when inputs are needed. The tutorial includes a project setup with LEDs and a button, highlighting issues with timing and input responsiveness. It concludes with a recap and introduces the Millis function as a solution for more complex timing needs.

What is the primary goal of using the Arduino Millis and Delay functions in this video series?

• To create repetitive timed events

• To develop a web server

• To control a robot

• To create a light show with LEDs

In the project example, what was the initial issue with using the delay function?

• The code was too complex

• The timing of events overlapped

• The LEDs were not bright enough

• The servo motor was too slow

What change was made to the project to address the timing issue?

• Increased the delay time

• Removed the servo motor

• Used a different microcontroller

• Added more LEDs

What problem arises when trying to read a button input with the current code setup?

• The button is not connected properly

• The LED does not turn on at all

• The LED response is delayed

• The button breaks the circuit

Why is the current loop not considered a 'tight loop'?

• It has too many variables

• It is too short

• It includes blocking code with delays

• It uses too much memory

What is a potential solution for handling inputs more effectively in the code?

• Using the Millis function

• Adding more LEDs

• Using a larger microcontroller

• Increasing the delay time

When is it appropriate to use the delay function according to the recap?

• When events overlap

• When events are sequential and non-overlapping

• When handling multiple inputs

• When using complex algorithms