Skip to main content

Extension of RPi.GPIO with interrupts, and command line GPIO multitool for the Raspberry Pi

Project description

RPIO extends RPi.GPIO with easy interrupt handling, and provides a command
line tool `rpio` which allows you to inspect and manipulate gpio's even if
they are owned by another process. The easiest way to install RPIO on a
Raspberry Pi is either with `pip`::

$ sudo pip install RPIO

or `easy_install`::

$ sudo easy_install RPIO

You can also clone the repository from Github and build it yourself:::

$ git clone
$ cd RPIO
$ sudo python install

After the installation you can `import RPIO` as well as use the command-line tool


Interrupts are used to receive notifications from the kernel when GPIO state
changes occur. Advantages include minimized cpu consumption, very fast
notification times, and the ability to trigger on specific edge transitions
(`'rising|falling|both'`). This is an example of how to use RPIO::

import logging
log_format = '%(levelname)s | %(asctime)-15s | %(message)s'
logging.basicConfig(format=log_format, level=logging.DEBUG)
import RPIO

def do_something(gpio_id, value):"New value for GPIO %s: %s" % (gpio_id, value))

RPIO.add_interrupt_callback(17, do_something, edge='rising')
RPIO.add_interrupt_callback(18, do_something, edge='falling')
RPIO.add_interrupt_callback(19, do_something, edge='both')

If you want to receive a callback inside a Thread (which won't block anything
else on the system), set `threaded_callback` to True when adding an interrupt-
callback. Here is an example:::

RPIO.add_interrupt_callback(17, do_something, edge='rising', threaded_callback=True)

Make sure to double-check the value returned from the interrupt, since it
is not necessarily corresponding to the edge (eg. 0 may come in as value,
even if edge="rising"). To remove all callbacks from a certain gpio pin, use
`RPIO.del_interrupt_callback(gpio_id)`. To stop the `wait_for_interrupts()`
loop you can call `RPIO.stop_waiting_for_interrupts()`.

If an interrupt occurs while your callback function does something blocking
(like `time.sleep()` outside a thread), events will not arrive until you
release the block. Only one process can receive interrupts for a specific GPIO
pin, since the read on `/sys/class/gpio/gpio<N>/value` destroys the value for
subsequent reads. RPIO uses `epoll` to receive interrupts from the kernel.


You can use all of RPi.GPIO's functionality through RPIO. Note that RPIO uses GPIO.BCM pin numbering by default::

import RPIO

# set up GPIO output channel
RPIO.setup(17, RPIO.OUT)

# set gpio 17 to high
RPIO.output(17, True)

# set up output channel with an initial state
RPIO.setup(18, RPIO.OUT, initial=RPIO.LOW)

# set up input channel with pull-up control
# (pull_up_down be PUD_OFF, PUD_UP or PUD_DOWN, default PUD_OFF)
RPIO.setup(19, RPIO.IN, pull_up_down=RPIO.PUD_UP)

# read input from gpio 19
input_value = RPIO.input(19)

# change to BOARD GPIO numbering

# reset every channel that has been set up by this program. and unexport gpio interfaces

rpio, the command-line multitool
The RPIO package includes a command line tool called `rpio` which allows you to
inspect and manipulate GPIO's system wide; including gpios used by other processes:::

Inspect the function and state of gpios (with -i/--inspect):

$ rpio -i 17
$ rpio -i 17,18,19
$ rpio -i 2-24

# Example output for `rpio -i 4-10`
GPIO 4 : INPUT [0]
GPIO 5 : ALT0 [0]
GPIO 7 : INPUT [0]
GPIO 8 : INPUT [0]
GPIO 9 : INPUT [0]
GPIO 10: INPUT [1]

Set GPIO 17 to either `0` or `1` (with -s/--set):

$ rpio -s 17:1

You can only write to pins that have been set up as OUTPUT. You can
set this yourself with `--setoutput <gpio-id>`.

Show interrupt events on GPIOs (with -w/--wait_for_interrupts;
default edge='both'):

$ rpio -w 17
$ rpio -w 17:rising,18:falling,19
$ rpio -w 17-24

Setup a pin as INPUT (optionally with pullup or -down resistor):

$ rpio --setinput 17
$ rpio --setinput 17:pullup
$ rpio --setinput 17:pulldown

Setup a pin as OUTPUT:

$ rpio --setoutput 18


Chris Hager (<>)

- [ ] `GPIO.input(...)` can set a pullup/pulldown resistor, which is not yet part
of the interrupt extension (since there is no option for it in /sys/class/gpio/...).
Note to self: A possible solution is to replicate the function from `RPi.GPIO.input()`.

- [ ] BCM numbering scheme is used by default, BOARD is not supported for interrupts

Project details

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Files for RPIO, version 0.5.1
Filename, size File type Python version Upload date Hashes
Filename, size RPIO-0.5.1-py2.7-linux-armv6l.egg (31.3 kB) File type Egg Python version 2.7 Upload date Hashes View hashes
Filename, size RPIO-0.5.1-py3.2-linux-armv6l.egg (32.0 kB) File type Egg Python version 3.2 Upload date Hashes View hashes
Filename, size RPIO-0.5.1.tar.gz (18.1 kB) File type Source Python version None Upload date Hashes View hashes

Supported by

Elastic Elastic Search Pingdom Pingdom Monitoring Google Google BigQuery Sentry Sentry Error logging AWS AWS Cloud computing DataDog DataDog Monitoring Fastly Fastly CDN SignalFx SignalFx Supporter DigiCert DigiCert EV certificate StatusPage StatusPage Status page