Interrupts may require some state machine if the algorithm gets bigger and bigger. Saying "don't use digitalread" is misleading, because interrupts do not solve every problem. You know this, but you prefer the clickbait.
@@RoboCircuits you should say that, then. "digitalRead is not always the best idea", or "alternatives to digitalRead", or "when digitalRead is not the fastest solution".
I am really happy to see a video on some slightly advanced interrupt handling, but as far as I know, using `delay()` in the ISR definition is not a good practice. In fact, the watchdog timer would ideally run out way before something like `delay(150000)` executes. I have experienced this while using a few `Serial.println()` calls in my ISR definition. Printing data a few times onto the serial monitor takes long enough to exhaust the watchdog timer, causing the microcontroller to reset. 😂 Am I right? Or am I missing something?
Sir, I am designing a working model of lift. In that I am using push buttons. For that, I incorporated all three solutions provided by you. But the code is giving error- Compilation error. Expected initializer before 'extern'. What does it mean? Should I 'include' some function from library?
@@ClaudioParraGonzalez suppose you use delay in program of 5ms and controller executing that delay and that time any button pressed then controller will not accept that button bcz it have only one core and we cant do multitasking solution is use external hardware interrupt but pins are isr pins limited on arduino then solution for this only one that is dont use delay in program use millis, find out how millis replace dalay, checkout my channel Mr tech inventor
Sure, but still you will mess with code scalability, hence interrupts is still better than polling and mils... That's only good to know how long the key is pressed for special purposes in the code for example...
Applying a 10nF capacitor would solve most of the issues. I was actually expecting way much more. Reading one button is easy... Reading several is another thing... You will have interrupt overlap and might break something... I would do a totally different approach...
1. Nice explanation of interrupts. I have a question , you have explained about how to use interrupt for a BUTTON ( single button). but in real system , there are 3-5 buttons .....like MENU Button , UP button, DOWN button , ENTER button . How to deal with this situation ? 2. suppose I want to use a keypad of size 4x4 or 4x5, how to deal with this situation. can a interrupt will be generated for any key pressed ?
During keypads, you need to check 2 pins at the same time.. there you can use interrupt. But you need to be a little creative. I never tried but i will try and let you know.
@@RoboCircuits From your statement I got any idea to use interrupt for keypad. 2 pins can be given to any logic gate and output of logic gate will be single.
i dont like useing interrupts for this i use it for more important stuff. i use if(buttonstate != prevbuttonstate){ if(buttonstate == HIGH){ //do stuff..... } } prevbuttonstate = buttonstate; and the longer de code gets the bounce issue manly disapears and if i doesnt, i use millis(). but DONT USE delay its bad in most cases.
You hit a very important nerve here: interrupts are difficult to learn, and if you use 2 or more sources of interrupts you will need some state machine to keep track of what the program is doing. Some problems requires interrupts and interrupts are the only solution. But you have to think your program very well.
Nice video. You should realy use a good microphone, lose the music, it's not mixed well, and maybe talk a bit slower, so people who are not nThanks anyway.
hello, this is cienna from Beijing DWIN Technology company, I visited your youtube platform,I believe there is a strong possibility for us to work with you, we are LCD manufacturer for 19 years，we have hundreds kind of LCD display,and our products could connect with Arduino, ESP32,STM32 etc, so I believe there is a strong possibility for us to work with you.
this is one of the basics in all programming languages in microchip assembly hardware interrupt can be used for many things including reading buttons as long as there are no delay loops in interrupt routine it is very effective and fast way . I use interrupt to read switches set variable I=100 in the main declaration for variables and in in hardware interrupt routine also set I=100 as soon as it finishes the interrupt and returns back to main program then I do a software interrupt using call subroutine and put a counter example I=I-1 and disable hardware interrupt in this loop then checks I if =0 then enable hardware interrupt and set I =100 if not exit subroutine I do not use any delay in the software subroutine and rely on instructions delay when the program counter is executing every instruction in main program (depends on the clock frequency used by your MCU ) the benefits are no impact on main program and my MCU ignores any button until 100 main program loops are done . another note I=100 is for example demo not a fix value it depends on the main program how long are the instructions and normal delay loops in it . use delay loops only when necessarily needed . I hope that helps .
Interrupts may require some state machine if the algorithm gets bigger and bigger. Saying "don't use digitalread" is misleading, because interrupts do not solve every problem. You know this, but you prefer the clickbait.
But its a point worth learning for a lot of people
@@RoboCircuits you should say that, then. "digitalRead is not always the best idea", or "alternatives to digitalRead", or "when digitalRead is not the fastest solution".
I am really happy to see a video on some slightly advanced interrupt handling, but as far as I know, using `delay()` in the ISR definition is not a good practice. In fact, the watchdog timer would ideally run out way before something like `delay(150000)` executes. I have experienced this while using a few `Serial.println()` calls in my ISR definition. Printing data a few times onto the serial monitor takes long enough to exhaust the watchdog timer, causing the microcontroller to reset. 😂
Am I right? Or am I missing something?
Really useful video 👌😁
Thank you
very nice
Thank you
Great efforts👍🏻🔥
Thank you for supporting
Sir, I am designing a working model of lift. In that I am using push buttons. For that, I incorporated all three solutions provided by you. But the code is giving error- Compilation error. Expected initializer before 'extern'. What does it mean? Should I 'include' some function from library?
Nicely done. Thank you!
Standard practice use millis insted delay then no need of external interrrupt bcz less pins to use.
Could you please elaborate?
@@ClaudioParraGonzalez suppose you use delay in program of 5ms and controller executing that delay and that time any button pressed then controller will not accept that button bcz it have only one core and we cant do multitasking solution is use external hardware interrupt but pins are isr pins limited on arduino then solution for this only one that is dont use delay in program use millis, find out how millis replace dalay, checkout my channel Mr tech inventor
Yes its true… but if code is big then we can miss the press of button if not implemented properly
Sure, but still you will mess with code scalability, hence interrupts is still better than polling and mils... That's only good to know how long the key is pressed for special purposes in the code for example...
Properly explained, why and how. Thankyou sir. But can you make vdo in Hindi language for 100% understanding.
Brow I2C communication interrupt tutorial in ESP32
Its similar
Bro when i give high at pin 10 high and read pin 10 and pin 11input and both get high(1) value . So why this occur you can say.
Good to know. Thanks for sharing.
You are welcome… thanks for appreciation
Applying a 10nF capacitor would solve most of the issues. I was actually expecting way much more. Reading one button is easy... Reading several is another thing... You will have interrupt overlap and might break something... I would do a totally different approach...
I will try using a 10nf capacitor… it was a simple tutorial you can use multiple buttons as well
Thanks
Welcome 😀 thanks for appreciation
thanks, good video
Welcome 😄😄😄😄
You need a cap to denounce. Depending on what edge you care about, you can just use a cap, or a cap and resistor
Very good
Thank you
Do you know how to use a note acceptor machine if you know can you teach me I will also pay you money for this
Note acceptor?
1. Nice explanation of interrupts. I have a question , you have explained about how to use interrupt for a BUTTON ( single button).
but in real system , there are 3-5 buttons .....like MENU Button , UP button, DOWN button , ENTER button .
How to deal with this situation ?
2. suppose I want to use a keypad of size 4x4 or 4x5, how to deal with this situation.
can a interrupt will be generated for any key pressed ?
During keypads, you need to check 2 pins at the same time.. there you can use interrupt. But you need to be a little creative. I never tried but i will try and let you know.
Using multiple interrupts is fine. Just make sure isr should be as small as possible
@@RoboCircuits I wish to know your viewpoint, how to implement and use interrupt when there are multiple BUTTONS.
In case of keypad.. i never tried. But i have tried 4 pushbuttons and 4 interrupts and it works
@@RoboCircuits From your statement I got any idea to use interrupt for keypad. 2 pins can be given to any logic gate and output of logic gate will be single.
i dont like useing interrupts for this i use it for more important stuff. i use
if(buttonstate != prevbuttonstate){
if(buttonstate == HIGH){
//do stuff.....
}
}
prevbuttonstate = buttonstate;
and the longer de code gets the bounce issue manly disapears and if i doesnt, i use millis(). but DONT USE delay its bad in most cases.
True… i will implement it
Thanks for sharing
You hit a very important nerve here: interrupts are difficult to learn, and if you use 2 or more sources of interrupts you will need some state machine to keep track of what the program is doing. Some problems requires interrupts and interrupts are the only solution. But you have to think your program very well.
👍👍
Thank you
nice
Thank you
@@RoboCircuits so brilliant you are after a month replied 🤣🤣
Bro where are you now job?
A little busy with other things… but will get back soon
I will teach you...
Indian guys 😁
🤣
Nice video. You should realy use a good microphone, lose the music, it's not mixed well, and maybe talk a bit slower, so people who are not nThanks anyway.
Why annoying music
hello, this is cienna from Beijing DWIN Technology company, I visited your youtube platform,I believe there is a strong possibility for us to work with you, we are LCD manufacturer for 19 years，we have hundreds kind of LCD display,and our products could connect with Arduino, ESP32,STM32 etc, so I believe there is a strong possibility for us to work with you.
I replied to your mail
😂
and i send you email today, pls check it and thank you😀😀
Your email address
this is one of the basics in all programming languages
in microchip assembly
hardware interrupt can be used for many things including reading buttons
as long as there are no delay loops in interrupt routine it is very effective
and fast way .
I use interrupt to read switches
set variable I=100 in the main declaration for variables
and in in hardware interrupt routine also set I=100 as soon as it finishes the interrupt and returns back to main program
then I do a software interrupt using call subroutine and put a counter
example I=I-1
and disable hardware interrupt
in this loop
then checks I if =0
then enable hardware interrupt
and set I =100
if not exit subroutine
I do not use any delay in the software subroutine
and rely on instructions delay
when the program counter is
executing every instruction in main program (depends on the clock frequency used by your MCU )
the benefits
are no impact on main program
and my MCU ignores any button
until 100 main program loops are done .
another note I=100 is for example demo not a fix value it depends on the main program how long are the instructions and normal delay loops in it .
use delay loops only when necessarily needed .
I hope that helps .
I completely agree with you… the method you suggested is even better
Awesome video… best explanation of interrupts i have seen
Thank you
Nice explanation 🎉keep it up
Any RTOS tutorials?
Semaphore
Mutex
Threads?