Monday, March 04, 2013
Updating RPi.GPIO-0.5.0a
So I am going to try RPIO 0.8.0 - GPIO toolbox for the Raspberry Pi. But before that I first need to update my old RPiGPIO-0.4x to 0.5.0a. I forgot how to do the installation. So I googled the following.
Installing RPi.GPIO
$ wget http://pypi.python.org/packages/source/R/RPi.GPIO/RPi.GPIO-0.5.0a.tar.gz
$ tar zxf RPi.GPIO-0.5.0.tar.gz
$ cd RPi.GPIO-0.5.0a
$ sudo python setup.py install
The installation is OK. Then I read the update which says the following.
Added new edge detection events (interrupt handling) -
Added add_event_detect() -
Added remove_event_detect() -
Added add_event_callback() -
Added wait_for_edge()
I am not too sure if the interrupt handling this is mature. I have the feeling that RPIO 0.8.0 is better. So I will move on to RPIO 0.8.0.
RPi.GPIO 0.5.0a
https://pypi.python.org/pypi/RPi.GPIO
RPi.GPIO-0.5.0a.tar.gz
A module to control Raspberry Pi GPIO channels
This package provides a class to control the GPIO on a Raspberry Pi.
Note that this module is unsuitable for real-time or timing critical applications. This is because you can not predict when Python will be busy garbage collecting. It also runs under the Linux kernel which is not suitable for real time applications - it is multitasking O/S and another process may be given priority over the CPU, causing jitter in your program. If you are after true real-time performance and predictability, buy yourself an Arduino http://www.arduino.cc !
Note that the current release does not support SPI, I2C, PWM or serial functionality on the RPi yet. This is planned for the near future - watch this space! One-wire functionality is also planned.
Example Usage :
import RPi.GPIO as GPIO
# to use Raspberry Pi board pin numbers
GPIO.setmode(GPIO.BOARD)
# set up GPIO output channel
GPIO.setup(12, GPIO.OUT)
# set RPi board pin 12 high
GPIO.output(12, GPIO.HIGH)
# set up GPIO output channel with an initial state
GPIO.setup(26, GPIO.OUT, initial=GPIO.LOW)
# set up GPIO input with pull-up control
# (pull_up_down be PUD_OFF, PUD_UP or PUD_DOWN, default PUD_OFF)
GPIO.setup(11, GPIO.IN, pull_up_down=GPIO.PUD_UP)
# input from RPi board pin 11. Will return GPIO.HIGH==1 or GPIO.LOW==0
input_value = GPIO.input(11)
# Enable edge detection events
# can be RISING, FALLING or BOTH
GPIO.add_event_detect(11, GPIO.RISING)
# Check to see if an event has occurred since the last time we checked (poll)
if GPIO.event_detected(11):
print('Rising edge has occurred!')
# Add a threaded callback for an edge detection event. Note that event detection must be enabled first using add_event_detect()
def my_event_callback_function():
print('Callback function called!')
GPIO.add_event_callback(11, my_event_callback_function)
# Remove edge detection events for a channel
GPIO.remove_event_detect(11)
# Another way of adding edge detection events with a threaded callback
def my_event_callback_function():
print('Callback function called!')
GPIO.add_event_detect(11, GPIO.RISING, callback=my_event_callback_function)
# wait for a button press without polling (uses negligable CPU)
GPIO.wait_for_edge(11, GPIO.RISING)
# to change to BCM GPIO numbering
GPIO.setmode(GPIO.BCM)
# to reset every channel that has been set up by this program to INPUT with no pullup/pulldown and no event detection.
GPIO.cleanup()
Change Log
0.5.0a
Added new edge detection events (interrupt handling) - Added add_event_detect() - Added remove_event_detect() - Added add_event_callback() - Added wait_for_edge()
Removed old experimental event functions - Removed set_rising_event() - Removed set_falling_event() - Removed set_high_event() - Removed set_low_event()
Changed event_detected() for new edge detection functionality
input() now returns 0/LOW == False or 1/HIGH == True (integers) instead of False or True (booleans).
Fix error on repeated import (issue 3)
Change SetupException to a RuntimeError so it can be caught on import (issue 25, Chris Hager <chris@linuxuser.at>)
Improved docstrings of functions
.END
No comments:
Post a Comment