Don't get my interrupt registered unless change "rising" "falling" or "both" when launch my script about rpio

[metachris]

I will take a look at it! Can you post your full script?

[johnlauer]

#!/usr/bin/env python
from time import sleep
#import RPi.GPIO as GPIO
import RPIO

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

RPIO.setmode(RPIO.BCM)

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

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

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

do_something(17, -1)
logging.info("About to wait for interrupts")
RPIO.wait_for_interrupts()

[metachris]

OK! Can you replace the line RPIO.wait_for_interrupts() with this and see if it helps?

try:
    RPIO.wait_for_interrupts()

except KeyboardInterrupt:
    RPIO.cleanup()

[johnlauer]

Ok. That seemed to do the trick. I’m just not sure I’ll always be able to do a perfect cleanup in all cases. This script will be running in an espresso machine and if the script dies for some random reason it is brought back up through a watchdog process. So a forced override when registering the callback is likely best. I suppose I could always do a cleanup first and then try to register the callback. You think that will work?

From: Chris Hager [mailto:[email protected]]
Sent: Saturday, February 23, 2013 12:51 PM
To: metachris/RPIO
Cc: John Lauer
Subject: Re: [RPIO] Don't get my interrupt registered unless change "rising" "falling" or "both" when launch my script (#1)

OK! Can you replace the line RPIO.wait_for_interrupts() with

try:

RPIO.wait_for_interrupts()

except KeyboardInterrupt:

RPIO.cleanup()

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/1#issuecomment-13997469.

[metachris]

Okay great -- I will update the documentation and add a fix to the next update which should go out tomorrow morning. After the update you won't have to do the cleanup manually anymore.

Thanks a lot for the feedback!

PS: You don't need to setup the gpio as input before using it for interrupts, so you can remove the RPIO.setup(17, ...) line.

[johnlauer]

Ok, great.

If I don’t have to setup the PIN for interrupts, how can I set the pull up or down resistor on the pin?

From: Chris Hager [mailto:[email protected]]
Sent: Saturday, February 23, 2013 12:58 PM
To: metachris/RPIO
Cc: John Lauer
Subject: Re: [RPIO] Don't get my interrupt registered unless change "rising" "falling" or "both" when launch my script (#1)

Okay great -- I will update the documentation and add a fix to the next update which should go out tomorrow morning. After the update you won't have to do the cleanup manually anymore.

Thanks a lot for the feedback!

PS: You don't need to setup the gpio as input before using it for interrupts, so you can remove the RPIO.setup(17, ...) line.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/1#issuecomment-13997604.

[metachris]

You cannot set software pullups or pulldowns for interrupts as of yet. I'm working on it and hope to be able to include that soon. In the meantime please use a hardware resistor.

Edit: I was wondering -- did using setup(..) with a pullup or -down have the desired effect?

[johnlauer]

Hmm. Ok. My circuit board design is already wrapped, but I might be able to pull off a hardware resistor.

From: Chris Hager [mailto:[email protected]]
Sent: Saturday, February 23, 2013 1:04 PM
To: metachris/RPIO
Cc: John Lauer
Subject: Re: [RPIO] Don't get my interrupt registered unless change "rising" "falling" or "both" when launch my script (#1)

You cannot set software pullups or pulldowns as of yet. I'm working on it and hope to be able to include that soon. In the meantime please use a hardware resistor.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/1#issuecomment-13997723.

[metachris]

I've just released RPIO v0.7.1 which also automatically cleans up the interfaces. Using this you won't need to call cleanup() related with interrupts anymore. You can update to 0.7.1 like this:

$ rpio --update-rpio

or with easy_install:

$ sudo easy_install -U RPIO