Need to run RPi.GPIO as root, why??

[Jonners49]

Hi-

Running into a two-pronged problem:
If I need to use the line:

Code: Select all

from Tkinter import *

I need to run IDLe as a normal user, otherwise I get the error - ImportError: no module names Tkinter

If I use the line:

Code: Select all

import RPi.GPIO as GPIO

I need to run IDLE as root. otherwise I get the error - NameError : name "GPIO" is not defined

This must be something others have run up against!

Jon.

[r3d4]

Could be wrong but, I think it is because think because every thing is a file and root own's the gpio files .

[Jonners49]

I've just read that Linux likes to be running as root when accessing the GPIO. Seems a little odd, but there you go. Therefore have to work out how to overcome Tkinter problem. May re-post with a title that describes this approach.

[jamesh]

It's the security model.

Linux will not let you access hardware directly unless you have the right permissions. This is a 'good thing'. Stops hackers getting direct access to the HW from a normal account otherwise they could cause complete chaos. GPIO's are HW when accessed directly rather than through a driver.

[DougieLawson]

Try running sudo idle

[PiGraham]

WiringPi or Joan's pigpiod (access via python interface library) will allow user code to run without elevated priveledges and talk to GPIO. Run a daemon from startup and you can control gpio from user code that way.