Closed lobermann closed 8 years ago
Strange.... And you have RPi.GPIO version greater than 0.6.0 ?
Yes, version is greater.
pi@octopi ~ $ python
Python 2.7.3 (default, Mar 18 2014, 05:13:23)
[GCC 4.6.3] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import RPi.GPIO as GPIO
>>> print GPIO.VERSION
0.6.2
Sorry, I was reading this on a smartphone and I didn't noticed the obvious:
chmod a+rw /dev/gpiomem
Yes, but there is no such device on my octopi. And also the plugin wants to access /dev/mem instead of /dev/gpiomem . Maybe there are differences between versions? My Octopi, the underlaying system, is at least a year old already, maybe a change there?
maybe...
can you do a uname -a
?
I'm running quite a new version as I am on RPi3 with jessie ("4.1.21-v7+ #872 SMP Wed Apr 6 17:34:14 BST 2016 armv7l GNU/Linux"
I'm not sure whats worse.. running OctoPrint as root or attempting an upgrade and possible complications. A backup SD card would be advisable in case you decide to upgrade.
Runnin a bit older version:
Linux octopi 3.18.11+ #781 PREEMPT Tue Apr 21 18:02:18 BST 2015 armv6l GNU/Linux
I will organize a new SD card and try the latest octopi, see if there is a difference.
Hi there,
just started using your plugin, very awesome I have to say! Didn't get it running in Marlin directly, but this is a much nicer approach.
Anyway, I want to share with you a small issue I encountered. The problem is with the access rights on the Pi for /dev/mem. As you describe it correctly you have to change the permissions, but this still does not allow you to access the device on the Pi.
Where the device is having the correct permissions
Only way I got it running was by starting Octoprint as root, by modifying following lines in the the /etc/default/octoprint:
and then copying the .octoprint folder from /home/pi to /root , so that all my stuff is still there.
Just want to let you know that, not sure if there is a workaround for that, I couldn't find one in the short time I searched.
Cheers, Lukas