Let’s do that with polling first, using Python and the RPi.GPIO module. So, we want to get to know when the user presses the button, by printing something on the screen.
Connect another leg to GPIO 16 (no need for pull up resistor, there is an internal one that we’ll use in the code). Make sure all 4 legs of the push button are separated on the breadboard. Here’s the hardware setup (if needed: Raspberry Pi pinout guide): Let’s now come back to real GPIOs on our Raspberry Pi.įor the beginning of this tutorial we’ll use a simple push button connected to the Raspberry Pi board. Note that interrupts (notifications) are not the solution to all problems, it really depends on the situation. When dealing with interrupts, think “notification”. Or you can activate a notification bell so you get a popup on your screen as soon as the email arrives.Īs you can guess, the second method is much more efficient in this case. Check your emails every 5 minutes, or 1 minutes, or even 10 seconds until you get it. Here’s the difference through a real life example: imagine you’re waiting for an important email and want to open it as soon as it arrives. There are two main ways to check input pin states: polling and interrupts. Why interrupts? A quick real life analogy Going further with GPIO interrupts on your Raspberry Pi. RPi.GPIO interrupts application example #3. 
RPi.GPIO interrupts application example #2. 
RPi.GPIO interrupts application example #1.A few applications with Raspberry Pi GPIO interrupts.Improvement: detect both rising and falling signals.Interrupts with add_event_detect() and threaded callback.Interrupts with RPi.GPIO wait_for_edge().
0 kommentar(er)
