object has no attribute 'setmode'

[dchurch24]

Hi all,

I'm working through this tutorial:

http://www.rpiblog.com/2012/09/using-gp ... k-led.html

...but I keep getting the error:

Code: Select all

sudo python test.py                                Traceback (most recent call last):
  File "test.py", line 11, in <module>
    GPIO.setmode(GPIO.BOARD)
AttributeError: 'module' object has no attribute 'setmode'

I've reinstalled the gpio stuff and I still get this error.

I'm using the latest Wheezy from the RPi site (download about 2 hours ago).

Any ideas as to why I'm getting this?

[dchurch24]

Ok, opening the __init.py in the RPi/GPIO folder confirms that 'setmode' doesn't exist.

Is the install broken for the latest Wheezy?

[dchurch24]

Bizarre. I reinstalled the SD card, again, and now it works out of the box.

It was the same image that was pushed to the card.

[cae2100]

try adding "GPIO.setmode(BCM)" or "GPIO.setmode(board)" without quotes towards the top of the code, before setting up the pin's as input/outputs. the pins change depending on the mode, so make sure you have the one you need. I have a short tutorial here:
http://cae2100.wordpress.com/2013/01/10 ... in-python/

[metachris]

Perhaps you were using an old version of RPi.GPIO. You can update it with `sudo easy_install -U RPi.GPIO`, and print the version with `import RPi.GPIO; print RPi.GPIO.VERSION`.

[dchurch24]

Hi, thanks chaps. I did try (some of) those things before I reinstalled. I updated the RPi.GPIO and it was 1.0.
It's the same version I'm using now.
I must have installed something that buggered it up I guess.
All working now though, thanks guys!

[Alveena]

>>> import RPi.GPIO as GPIO
>>> GPIO.setmod(GPIO.BCM)
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
AttributeError: 'module' object has no attribute 'setmod'


help me regarding this

[hippy]

>>> GPIO.setmod(GPIO.BCM)

Try GPIO.setmode(GPIO.BCM)

[Houtkamp]

years and years later, STILL no solution for this...

[Paeryn]

years and years later, STILL no solution for this...

No solution to what? The original poster apparently fixed their problem by re-installing the library. Then 2.5 years later somebody else resurrected the thread with a (slightly) different problem - in that it looks like they had typed setmod rather than setmode, and which we have no evidence to say that the given solution (to spell the function name properly) hasn't worked.