Open GoogleCodeExporter opened 9 years ago
Having the same issue.
Original comment by sksell
on 24 Feb 2015 at 2:28
WebIOPI is not working yet on Raspberry Pi 2.
There are things that You can do to change it.
You must change two files located in /python/native directory.
First change setup method in gpio.c file
Second change get_cpuinfo_revision method in cpuinfo.c
I've attached two needed files.
When you replace files in sources You must install it once again.
Then it should work on RPI 2! :)
Original comment by lukasz...@gmail.com
on 24 Feb 2015 at 7:26
Attachments:
I can't find /python/native where is it located ?
Original comment by MisterLo...@gmail.com
on 25 Feb 2015 at 10:07
it is in sources when you untar downloaded archives.
Original comment by lukasz...@gmail.com
on 25 Feb 2015 at 1:07
Got it working after replacing the said files.
Noticed that GPIO list shows only up to pin 26. Pins 27 to 40 is not present.
Also use RPi 2...
Original comment by aln1...@yahoo.com
on 25 Feb 2015 at 1:22
Do you know when the WebIOPi 0.7.2 will appear ??
Original comment by MisterLo...@gmail.com
on 25 Feb 2015 at 7:57
to use pins 27 to 40 you must change a lot in WebIOPi...
First You must change version.py to handle new pins.
second you must do some changes in webiopi.js
Original comment by lukasz...@gmail.com
on 25 Feb 2015 at 8:32
Sorry i wasn't able to post an update earlier.
I got it to show all pins the other night by modifying the mentioned files
(namely version.py under python/webiopi/utils folder and webiopi.js under
htdocs folder).
Everything seems ok except that I noticed pins #29 (GPIO 5) and #31 (GPIO 6)
were not as the same as the rest in terms of default status.
Under GPIO header, it shows that GPIO 5 has a default status of OUT,HIGH, while
GPIO 6 has IN,HIGH.
I don't know if it means anything. Just wanted to share what I experienced.
Thanks for the help by the way regarding the two attached files under
python/native folder...
Original comment by aln1...@yahoo.com
on 26 Feb 2015 at 11:26
Can you post your modified version.py I will see what mine has for status for 5
and 6 this weekend and report back
Original comment by sksell
on 26 Feb 2015 at 11:32
Alright. Here you go...
Original comment by aln1...@yahoo.com
on 26 Feb 2015 at 11:51
Attachments:
in my pi gpio #5 and #6 are in default state IN and HIGH signal...
there is a config file where you can change the start state of pins..
just sudo nano /etc/webiopi/config
Original comment by lukasz...@gmail.com
on 26 Feb 2015 at 3:59
Can someone please post the modified webiopi.js
Thanks
Original comment by oasha...@gmail.com
on 28 Feb 2015 at 6:11
Thanks a lot.
It's working perfectly on my Pi2 :)
-Mikael
Original comment by mwin...@gmail.com
on 28 Feb 2015 at 8:53
Yes cross fingers that a new version will be released soon...
Would also be intrested in the modified webiopi.js
Thanks
Original comment by week...@googlemail.com
on 28 Feb 2015 at 12:32
Here as requested...
Original comment by aln1...@yahoo.com
on 28 Feb 2015 at 3:09
Attachments:
After replacing the two files in the source and reinstall worked for me. Thank
you.
Original comment by sutoand...@gmail.com
on 9 Mar 2015 at 9:45
Thanks for posting the files. they work perfectly on my pi2.
i do also have the pins 5/6 in IN and HIGH state, but that actually doesnt
bother me.
Original comment by DaMal...@gmail.com
on 23 Mar 2015 at 8:19
This worked for me too. Just to make it a little easier for the next person,
download the above files and then, with those in your home directory, and with
your current working directory in $HOME/WebIOPi-0.7.1, assuming you've
extracted the sources there, the following are the mv commands to put these
files into place:
pi@raspberrypi ~/WebIOPi-0.7.1 $ mv ../gpio.c python/native/gpio.c
pi@raspberrypi ~/WebIOPi-0.7.1 $ mv ../cpuinfo.c python/native/cpuinfo.c
pi@raspberrypi ~/WebIOPi-0.7.1 $ mv ../version.py
python/webiopi/utils/version.py
pi@raspberrypi ~/WebIOPi-0.7.1 $ mv ../webiopi.js htdocs/webiopi.js
Adjust your paths if you've got things in different places. Then run setup.sh
and you're good to go.
Thanks to everyone who has contributed to this - very cool!
Original comment by v...@zymsys.com
on 4 Apr 2015 at 10:39
Original issue reported on code.google.com by
MisterLo...@gmail.com
on 23 Feb 2015 at 5:57