PiFace Problems

Keith, you are not alone. The 'documentation' with the piface is worse than useless. I particularly like the typo on page 2 of the 'instructions' (etc/ which should be /etc/) and that if the emulator fails (I can't get it to work – ends with 'segmentation fault') the 'instructions' that follow are, again, useless. I will get it working in the end, but no thanks to the fools at man.ac.uk. How difficult would it have been to provide basic instructions in the box? Good luck with it - I'll reply back when I've finished arm-wrestling with it and got it doing something (I have a job in mind).

... not sure if urls are allowed here - if they are, here's some documentation for piface ...

https://docs.google.com/folder/d/0B-UAZ9CyJCLGQjJ3RDlqa2pqaDg/edit?pli=1

Wow, brilliant (the google docs). Lot's of reading, I'll give it another try.

... if it helps, here's what I found useful to go alongside the google docs (see above) ...

https://github.com/thomasmacpherson/piface/blob/master/README.md

All the piface software with quite a good explanation of how to download and what to download  (useful if downloading the man.ac.uk 4GB SD card image is an issue – which it probably is if you're not plugged into the HE backbone).

https://projects.drogon.net/raspberry-pi/wiringpiface/

Wiringpiface - some alternative software which is quite well explained.

https://projects.drogon.net/raspberry-pi/wiringpi/the-gpio-utility/

… and from the same place a gpio utility which I found a good starting point for simply turning lights on etc. The proviso with the two links above is that there are wrinkles and gotchas here and there (but I found it worth persevering).

And lastly, 'documentation' (almost) for the RPi gpio pins

http://elinux.org/Rpi_Low-level_peripherals

What I didn't find useful, in fact the biggest time-waster, was the RPi Foundation forum.

Nevertheless, I have got the first part of my project working now - when its above 20c in the conservatory a fan turns on to blow warm air around the house (all done with RPi, sensors and a relay). In the process, I've come to realise that piface (and the gertboard) are hardware 'solutions' (to stop school kids from frying their RPis) and that an easy-to-use software companion simply doesn't exist. That's the frustrating part, and one which will most likely stymie the growth of the idea that got me interested - 'physical computing'.

Hi,

I maintain and develop the software for PiFace (for the moment at least). The GitHub is pretty much the goto with regards to information from me since it's kept up to date. Is there anything in particular I can help with? You said that PiFace isn't an easy-to-use software companion? Apart from installation, what problems are there? I'd very much like to improve it so your input is invaluable!

As for installation, it's not perfect. We're working on getting a more streamlined method. Are the instructions on the GitHub clear? Can I make them any better?

Oh and just for reference, here is everything PiFace: https://github.com/thomasmacpherson/piface

Thanks.

Hi,

I've installed everything according to the PiFaceDigital_Get_Started_140213v1.pdf and commented out #blacklist spi-bcm2708, etc...

sudo ... piface-emulator says: "Could not connect to the SPI module (check privileges)..."

What do you think is going on and how might I fix this?

Thanks,

Adrian

The PiFace software talks to the board through the SPI interface device. All devices in Linux are presented as files in /dev/ and the SPI interface is presented as /dev/spidev0.0 and /dev/spidev0.1. That error is because PiFace is struggling to connect to the SPI device. During testing this was most likely because the user pi did not have the permissions to access the file, hence the check privileges suggestion. Or the file did not exist, meaning that the Linux kernel hasn't created it because the SPI kernel module wasn't loaded correctly.

To figure out which, let's take a look at the SPI files in /dev, run the command:

$ ls -l /dev/spidev*

crw-rw----T 1 root spiuser 153, 0, Jan   1   1970  /dev/spidev0.0

crw-rw----T 1 root spiuser 153, 1, Jan   1   1970  /dev/spidev0.1

This will long-list all of the spidev files in /dev.

If the ls command returns nothing then Linux probably hasn't loaded the SPI module. Try listing all the currently loaded modules with:

$ lsmod

and see if spi_bcm2708 is there. If it isn't try loading it with:

$ sudo modprobe spi_bcm2708

and then check the SPI files again. If that works then double check that you have commented out the blacklist command in /etc/modprobe.d/raspi-blacklist.conf. Make sure you edit it as root! Also, make sure you've fully updated Raspbian (sudo apt-get update && sudo apt-get upgrade).

If the ls command returns something like the above then the Linux kernel is doing it's job correctly. See the first column of output from ls -l (the crw-rw----T bit)? That describes user permissions. The third and fourth columns describe the owner and group, respectively. The output needs to be exactly as I have above otherwise only root will be able to access the SPI interface. Try running the spidev-setup script again from the scripts/ directory in piface and reboot.

If non of this works, get back to me and I'll see what else I can do.

Thanks for the quick response...

There's "No such file or directory" spidev* in /dev

$ lsmod shows spi_bcm2708     4815     0

I note that the PiFaceDigital_Get_Started_140213v1documentation for the raspi-blacklist.conf file and $ sudo modprobe spi-bcm2708 shows a hyphen in the name while your message and lsmod show an _

I tried $ sudo modprobe with both the - and the _ but still no spidev

TIA

Hi

Not sure if appropriate but I downloaded new version of  WHEEZY came out dated 9th Feb and found that it fixed a few of the problems I had.

Its hard keeping up with these updates.

Feel the whole of the Raspberry Pi project suffers from this.

Hi

Not sure if appropriate but I downloaded new version of  WHEEZY came out dated 9th Feb and found that it fixed a few of the problems I had.

Its hard keeping up with these updates.

Feel the whole of the Raspberry Pi project suffers from this.