Arduino Sketch with millis() instead of delay()
ฝัง
- เผยแพร่เมื่อ 18 พ.ค. 2024
- 🤩 Check out this Free Arduino Course 👇
bit.ly/get_Arduino_skills
**If you like this, I think you'll like the premium Arduino training we offer. Check it out here** bit.ly/3nSBPUs
We designed this circuit board for beginners!
Kit-On-A-Shield: amzn.to/3lfWClU
SHOP OUR FAVORITE STUFF! (affiliate links)
---------------------------------------------------
Get your Free Trial of Altium PCB design Software
www.altium.com/yt/programming...
We use Rev Captions for our subtitles
bit.ly/39trLeB
Arduino UNO R3:
Amazon: amzn.to/37eP4ra
Newegg: bit.ly/3fahas8
Budget Arduino Kits:
Amazon:amzn.to/3C0VqsH
Newegg:bit.ly/3j4tISX
Multimeter Options:
Amazon: amzn.to/3rRo3E0
Newegg: bit.ly/3rJoekA
Helping Hands:
Amazon: amzn.to/3C8IYXZ
Newegg: bit.ly/3fb03X1
Soldering Stations:
Amazon: amzn.to/2VawmP4
Newegg: bit.ly/3BZ6oio
AFFILIATES & REFERRALS
---------------------------------------------------
►Audible Plus Free trial: amzn.to/3j5IGrV
►Join Honey- Save Money bit.ly/3xmj7rH
►Download Glasswire for Free:bit.ly/3iv1fql
FOLLOW US ELSEWHERE
---------------------------------------------------
Facebook: / programmingelectronics...
Twitter: / progelecacademy
Website: www.programmingelectronics.com/
**Arduino Sketch with millis() instead of delay() written tutorial**
www.programmingelectronics.co...
****If you like this, I think you'll like the premium Arduino training we offer. You can check it out here**** bit.ly/3lHyzcB
please make a video on arduino sensor kit i need help on it btw your videos are amazing
Using
previousTime = currentTime;
will introduce an accumulating error. The time to process the code within the if statement will add to the time and accumulate. For just blinking LEDs or some other none critical stuff, no big deal.
But if you simply use:
previousTime += interval;
You've just gotten rid of the cumulative error.
Thanks for bringing this up Steve!
@@programmingelectronics It probably won't affect most of what people will use this for, but it is just the sort of thing to drive you crazy later when you can't figure out why your timing is slipping.
This is a great explanation. The visuals really help wrap your head around the concept. Thanks for the vid!
Thanks for watching!
Thank you for a wholesome explanation! Great stuff!
I have always struggled with this, even with your videos from years ago. I have watched numerous videos and still struggled. This video is simply THE BEST!
You have done so well as an experienced programmer to be able to explain to us newby's how this work is such an easy to understand way.
I have been copying & pasting other peoples bits of code randomly getting results and as my projects get more complicated, that approach does not work.
Well done, you are the best teacher on TH-cam for Arduino.
No.1
Numero uno!
It becomes very easy to learn from you. You make everything looks so simple. Thanks
Very clear explanation - I like that. I have taught some stuff in my one past life...Good job!
Very clear and simple explanation . Thank you!!
You are my favourite teacher.
Thanks a bunch 😀
The best explanation I've ever seen about millis()
true
The way you show it will usually work nicely. However, the interval at which you trigger your event will be at least eventInterval, but often just a little bit longer. This is because the loop also takes a little time. Sometimes you may want to be more sure that you always trigger your timed event at an 'exact' multiple of 'eventInterval'. In such cases it's better to update your 'previousTime' with the 'eventInterval', like so:
previousTime = previousTime + eventInterval;
That's a fantastic point - thanks for that adding that Jan!
love the simplicity you bring into the explanation..... i had been reading up on example codes to understand millis function and scratching my head over and over. I wish i had found this video earlier...
Glad it helped!
This is a great explanation.
what a Legend ! i wish i would of found your videos earlier! Absolutely the best explanation of things. Thank you Sir!
Thanks a ton! Glad they were helpful.
thankyou, I needed this
😄 The millis code was smart. I love that logic
You make everything look simple .
Thanks
I hope it helped! Timing stuff can get confusing quick!
These lessons are so well done!!
Thanks so much Chad - really appreciate that!
Wow.. That was the greatest tutorial I have ever seen on youtube...Thank you...
Glad you enjoyed it!
Thanks for this great explanation..it really helps a lot...
Great. first time explained, first-time understood. thank you very much
Awesome!
this is legendary! massive Thanks
Thanks!
why cant every tutorial be like this. Love it best
Thanks you make it so easy to learn
Thanks - much appreciated!
I found your video very helpful. Thank you!
Thanks so much for watching Anita!
enjoying this lessons. motivated to keep moving further. thanks a bunch.
Great to hear!
You are awesome, I can't wait for the next video! 👍👍
Thanks!
very informative...thanks a lot...
This is the best "millis()" tutorial I have ever seen. Thanks so much for explaining everything clearly.
Glad it was helpful! Thanks so much for the note!
When you saved me I really love that tutorial it's actually the best thing I've ever watched in the history of our doing it Tori old and I'm not even being hilarious that's the truth thanks man keep up the good work !
Thanks a lot man!
I watched numerous videos, but wasn't able understand the concept of space time along with black holes.
But now I'm confident enough to derive E=mc².💪
Glad it helped :)
Great video! Going to implement it to my project ASAP
Thank you! I am glad it helped - best of luck!
Great video. Thanks a lot for making this video.
Thank you! Thanks so much for watching!
Very Cool!!
You come out with this video just in time for me to use millis() to toggle between volts and amps on an OLED display (without using delays, delays that long when added up would have made the loop way too long for this project).
It took me a bit to figure out how to write the second section (like this:) (currentTime - previousTime >= interval + interval_1) I added the second interval time so I could set the volts code to display less time than the amps code since that's the one that needs to be read the most, but I got it. I'm sure I will eventually figure out an easier way but it's good for now and I'm proud of it! :-D
The most valuable information in your video series is the fact that the timer continues to count up until the microcontroller is reset or turned off and on again.
I now also realize that I can run more than one program from the same millis() function.
It's kind of like calculating what needs to happen at different times of the day with a certain amount of time for each task. Yeah, I know, probably a screwed up analogy but there it is LOL :-)
Until now I thought that the timer reset each time it was called for.
Thanks!!
Joe
Thanks also for sharing your addition on the code - very cool!
the best tutorial on millis() ever... thanks...
Thank you!
I'm an 'old timer', and after a year of struggling with the theory and even the basic concept of 'millis', I've finally 'got it'!
Thank you for the best Arduino 'millis' tutorial, and it's been my good fortune to find it..I look forward to watching more of your videos in future.
John.. Bristol.. UK
Excellent! Great to hear John!
the best explain tutorial lesson thanks a lot 👍
Simply grand.
The best lesson!
Really a great video.great people behind this Job...The visuals make everything so simple.thanks millions
Really appreciate that! Thanks!
You really have easily way to explain each point,thanks
Thank you! I hope it helped!
Thanks, very clear
thankyou so much ,it was a really big help
Great to hear!
Best explanation ever on millis. Thanks alot bro
Thanks! Glad it helped!
Wow, you're the best!!! thanks!
Excellent explanation and coding, with great visuals 👏
Thanks so much!
I think this is good idea if you need to step multiple stepper motors at the same time. When using delay() for moving stepper motors you can only move one stepper motor at a time
Very entertaining channel, love your videos, keep them coming
Thanks - much appreciated!
Great explanation sir thank you 😁❤
fantastic video!thank you!
Thanks for watching!
Tyyyy this was such a good video 😄
Glad you liked it!! Thanks so much for watching!
Very nice and easy to understand video, thanks!
Thanks for watching!
Oh you did great. This will help me on the annoying issue between RF transmitter not sending data because pulse sensor eats all the event
Great! Glad it helped!
Muchas gracias, At last someone took the time to explain this, I really needed it thank you kind GOD of code..
Glad it helped!
Thank you sir i really appreciate that....😎😎
Thank you so much!
love it
Wow mate thanks it amazing lessons
Such a nice video 🙂
wow that's awesome and well explained ! The presentation is very nice and clean and understandable ! but... what is it again ? ah, needs to rewind this utube vlog again & again.
This is awesome! the best explanation ever about millis function. Thanks a lot... Poor millis can't catch the carrot XD
You're mean, Emmanuel!
Nice info, well done, thanks for sharing it :)
Thanks for watching!
The best explanation ever... the carrot example was just epic... every noob can understand..... thank you so much for the great tutorial.
Glad it helped!
thank you
This is very informative
Glad it was helpful!
Great video, thank you. Question, will that code work correctly when millis() overflows and starts counting up from zero?
One thing that should be added to the code is a trap for when the value of the millis() function rolls over. Consider if your Arduino is being used on a long term basis exceeding the long int value maximum. The user would want a way to handle that condition and continue the event timer. One quick way would be to check if the new millis() time is less than the previous time then the event timer loop can be reset.
The way the code is written, by subtraction of unsigned longs, it compensates for roll over. No additional checks are needed.
I was just wondering about rollover
@@Ruudrad please explain a bit please. Is it in the code in your face code or firmware side that you simply do not see. As in...
If I am using millis to run a tachometer on an engine, and using that tach value to hold ignition on (interlock if you will, if RPM drops it cuts ignition) it will not get the math wrong in seeing the correct rpm?
The long term use case here is; the arduino is going to be powered on indefinitely monitoring a signal from inverter to start generator. Once the inverter calls, the arduino will sequence and start the generator. I dont want the roll over to cause am issue with a tach calculation inadvertently shutting down the generator.
@@wadebrewer7212 I initially also thought roll over would cause problems, however if you use longs _and_ subtract the unsigned longs (holding the output of the millis() function and/or the millis() function itself) the calculation will also work when millis() rolls over (I.E. goes from almost its maximum to just over zero). Strange but true thanks to how subtraction works on a microprocessor, which is NOT exactly the same as mathematical subtraction.
@Ruudrad Thank you tons. I was about to start researching for a work around. The community around this stuff is pretty great. Every once in a while you get the tool that talks down or "why do you want to do that project"....because I can....and at least for now...I am allowed.....lol.
Even in my situation....reading and counting every quarter or half second for revolutions....even if it did send a call to shut off the system, the cycles are so quick I don't think it would actually shut down. But...sounds is like it's non issue anyway.
Again, thank you for the input and much appreciated.
Sweet explanation :) Thank you
Glad it was helpful! Thanks for watching!
I think Micheal is THE BEST TRAINER out there to learn the basics of programming in Arduino!!! I've spent many hours watching all kinds of Arduino videos before I found Micheal's - Programming Electronics Academy. I signed up and watched ALL of his videos and it was well worth the money!!!
I highly recommend it to anyone that is getting into Arduino programming. He is really, really good!!!
Thanks so much for the kind words John! I am glad you are finding the training helpful!
Thank you,
That saved my life ❤
Glad it helped!
GOD BLESS YOU! You saved me from days of suffering! You are my Hero!!!
Glad it helped!
Very nice explaination. Thanks
Glad you liked it! Thanks for watching!
Thank you so much 🤍
+ extra points from ice ice baby
It was very useful information thanks
Glad it was helpful!
First off, thank you for your very informative video. I know this video is a few years old but I just came across it so my apologies for such a late comment.
From your video, and from others, I understand that millis() starts as soon as the Arduino starts running and it keeps running, and increasing, as long as the Arduino is up, at least until it reaches its maximum value and restarts. I'm not sure that you actually CAN reset millis() from within code but everyone seems to say you shouldn't. Apparently doing so can break some libraries that rely on it.
In order to understand millis() better I made a little project using code similar to yours to blink the built-in LED on and off at a preset interval while displaying current_elapsed_time (read from millis()) and previous_time, something similar to what you did in your code, and everything ran as expected. However, I noticed that every time I closed the serial monitor and reopened it the current_elapsed_time, which should display the current millis() value, returned to its starting value. The LED continues to blink at the proper interval while the monitor is closed, so I know the code is still running properly.
Thinking there was a bug in my code I created a new, stripped-down program which only makes a call to millis() and prints the retrieved value to the serial monitor (see code below) and ran my test again. Same behavior. The code calls for the millis() value to be sent to the serial monitor directly - no massaging or assigning to a variable - and every time I close and reopen the serial monitor it appears to reset millis(). Not sure what is happening.
Here is the simplified code I used to test:
void setup() {
Serial.begin(115200);
}
void loop() {
Serial.println(millis());
}
The program runs as expected and, as you can see, there is nothing but the call to print the current value of millis() but millis() seems to be affected by the status of the serial monitor window. Is this normal? Am I missing something? 🤔
Appreciate your help on this.
Thank you.
Thank you very much Sir... Great Video
Thanks!
so nicely explain thank you :)
Thanks for watching!
extremely helpfull!!!
Glad it helped!
thank you very much
Great video
Thanks!
very interesting, a good teacher
Thank you!
wow its amazing...
Thanks for watching!
What a great video.
Thank you! I hope it helped!
it was taking me forever to figure out why mine wasn't working, then i found out i had "==" instead of ">=" lol
thanks for the very clear and concise explanation!
Thanks a ton for watching - I am glad it helped!
great video!!
Thank you!! If there are other types of videos you would like to see, I'd love to get your advice/feedback/recommendations Lalo!
haha.. being mean with the carrot and millis() function. love it.
Thanks so much for watching!!
Thanks mate
I hope it helped!
Smoooth animation bro. I love the homey type design, backdrop is really chill. Casually printing ice ice bb to the serial monitor lol. Explained it fantstic with the carrot comparison. Sending money but more importantly encouragment. Your great at this! keep going - seriously
God Bless ;)
- J. T
Appreciate that - thanks for your generosity J.T.!
I like to imagine the millis being waves in the ocean and we are the Surfers trying to ride those waves.
Amazing explanation, great thanks. Thus, there is something I don't manage to understand. If I want a start point not equal to the interval, I mean for example an event to start at 30 seconds, and to be repeated 60 seconds later on. Do I need one more variable to be created? Kind regards.
amazing explanationnnnnn
Thanks!
Very helpfull! , but how it looks when you have a Button with some conditions? Thanks!
Great video, thanks! One comment though, I think we could also use a modulus operator to manage the event intervals. This would also cause it to run at millis() == 0, but we can use an additional clause to limit this. Perhaps something like:
if( currentTime > 0 && currentTime % eventInterval == 0 ) { ...
Actually, it seemed like this would work in theory, but there needs to be a buffer, as the code would run multiple times at each interval. I guess this is why the lastTime variable is introduced, so that we can ensure the code runs only once per interval. Makes sense - I stand corrected!
fantastic
Thanks a ton for the note!
Is it possible to make delay function in separate tab and use millis single line command like delay? For make code more simpler
Fantastic 😉
Thanks! I am glad you liked it.
This is great! However, how could i for example programme an event to take readings of from a temperature sensor for 1 minute? do i use debounceDelay?
This detail on the mills() function has been very helpful to me, explains why a program I wrote a few years ago doesn't quite work as expected.
Awesome - I am glad it helped!
@5:31 Aah, I see what you did there: The Neutron Dance! 😆
very nice video
Thanks Peter!