I am using the GPIO pins on my Raspberry Pi with a PIR sensor to detect motion. When the sensor detects motion I want to then move the software onto other functions.
At the moment, to detect motion I have my program constantly running in a loop while it is waiting for motion to be detected. While this works at the moment, for use in the future this will be incredibly inefficient and am hoping to improve on this by assigning it to an event.
Is there any way to bind my GPIO input to an event that is detected by the program without manually running a loop.
Here is my current loop for detection motion:
var = 1
counter = 0
while var == 1:
if GPIO.input(7):
counter += 1
time.sleep(0.5)
else:
counter = 0
time.sleep(1)
if counter >= 3:
print "Movement!"
captureImage()
time.sleep(20)
The counter and detecting motion multiple times is used to reduce the number of false positives that the sensor picks up.
You could wrap the GPIO-code into it's own thread and have the rest of your program do something else while the GPIO is waiting for input. Check out the threading module
First I'd wrap your code into a function
And then in your main program you could something like this
There are plenty of questions on SO concerning python threading, so you might want to dig them up. Please note that there are also plenty of things to consider when using threads, especially in python which has a global interpreter lock (GIL) which allows only one process to run at a time. It might also be smart to check out the multiprocessing module with which one can route around the GIL.
Now the RPi GPIO library has inbuilt interrupt driven GPIO control which can happen in separate thread freeing up resources. You may wish to read the following http://raspi.tv/2013/how-to-use-interrupts-with-python-on-the-raspberry-pi-and-rpi-gpio-part-3
The RPi.GPIO Python library now supports Events, which are explained in the Interrupts and Edge detection paragraph.
So after updating your Raspberry Pi with
sudo rpi-update
to get the latest version of the library, you can change your code to:I chose the Threaded callbacks method because I suppose that your program does some other things in parallel to change the value of
var
.kapcom01 gives some great ideas but it's better to make not make a lot of instructions in the a interrupt.
Usually you put a flag to 1 when the callback is call and you make the processing in the main function. In thes manner there is no risk of freesing the programm.
Somethings like this :