Im trying to use the arduino pushbutton to have a seperate function to be called when interrupted. Im having three push buttons and I have three functions respectively. Each pushbutton push should call its functions. I'm having difficulties executing this, because all the arduino interrupt can do is make a LED set high or low. Any info on this would be helpful.

 

I'm having difficulties executing this, because all the arduino interrupt can do is make a LED set high or low. Any info on this would be helpful.

Where did you ever get that idea?

I think you need to study interrupts on Arduino a bit more.

Bob

 

The Arduino interrupt calls some Arduino code and that code can do anything that an Arduino can do.

 

Normally good practice using interrupts is to enter the ISR,
set a flag, and return. Then based on flag status process that
interrupt request in main().

Reason for this is to get good/fast response by ISR request.
If you execute code, and f() calls inside ISR, you get a lot of stack
push/pop handling variables which is wasted machine cycles.


Regards, Dana.

 

Arduino has article about it: https://www.arduino.cc/reference/en/language/functions/external-interrupts/attachinterrupt/

 

If you can write a function for the Arduino to do what you want, then it can be attached to an interrupt. The function is called an ISR or Interrupt Service Routine.

In your case, an interrupt can be defined for a pushbutton.

It’s advisable to have the interrupt do as little as possible. One reason is that other interrupts that occur while the ISR is processing, are ignored. Another reason is that delay()s don’t work. Programmers set a flag and test that in the main loop.

The Uno and Nano only have 2 interrupt pins. You have three pushbuttons, so I’d advise using regular digit pins and diode Or them to an interrupt pin (2 or 3).

Are these mechanical pushbuttons? If you need to debounce then do so in the main loop when a flag has been set.

 

De-bouncing causes another headache. 20 mS is probably enough to have the button settle. You can consider hardware debouncing or even peripheral chips that will do it for you.

 

If you can write a function for the Arduino to do what you want, then it can be attached to an interrupt. The function is called an ISR or Interrupt Service Routine.

In your case, an interrupt can be defined for a pushbutton.

It’s advisable to have the interrupt do as little as possible. One reason is that other interrupts that occur while the ISR is processing, are ignored. Another reason is that delay()s don’t work. Programmers set a flag and test that in the main loop.

The Uno and Nano only have 2 interrupt pins. You have three pushbuttons, so I’d advise using regular digit pins and diode Or them to an interrupt pin (2 or 3).

Are these mechanical pushbuttons? If you need to debounce then do so in the main loop when a flag has been set.

Arduino can in fact have nested interrupts -

https://stackoverflow.com/questions/5111393/do-interrupts-interrupt-other-interrupts-on-arduino


Regards, Dana.

 

Approaches for debounceing, attached.


Regards, Dana.

 

Approaches for debounceing, attached.


Regards, Dana.

Thanks dana.

 

If you can write a function for the Arduino to do what you want, then it can be attached to an interrupt. The function is called an ISR or Interrupt Service Routine.

In your case, an interrupt can be defined for a pushbutton.

It’s advisable to have the interrupt do as little as possible. One reason is that other interrupts that occur while the ISR is processing, are ignored. Another reason is that delay()s don’t work. Programmers set a flag and test that in the main loop.

The Uno and Nano only have 2 interrupt pins. You have three pushbuttons, so I’d advise using regular digit pins and diode Or them to an interrupt pin (2 or 3).

Are these mechanical pushbuttons? If you need to debounce then do so in the main loop when a flag has been set.

Thanks for the info djsfantasi

 

Check out Nick Gammon's thorough treatise on interrupts on his own website gammon.au.
Covers all the obvious and not so obvious