Hook up the raspberry pi as per this diagram:
http://learn.adafruit.com/light-paintin ... i/hardware
Ensure you use a common ground when wiring up. I found the LEDs did not work if i powered the RPI and LEDs seperately. I found an old 5V 2A PSU I had lying around and that is fine for my WS2801 104 LEDs.
LED strip or Pixel chains work fine as long as you have either WS2801 or LPD8806 or LPD6803 IC's in you LEDs. Avoid the LPD6803 if you can as it doesn't support as many colours.
Install Python and Git on your raspberry pi (via apt-get).
These are the python libraries i have installed, some may already be installed on your Pi, can't remember which ones were 100% required. Ask the author of PixelPi if you get stuck with python related stuff.
ii idle-python2.7 2.7.3~rc2-2.1 all IDE for Python (v2.7) using Tkinter
ii idle-python3.2 3.2.3-2 all IDE for Python (v3.2) using Tkinter
ii libpython2.7 2.7.3~rc2-2.1 armhf Shared Python runtime library (version 2.7)
ii python 2.7.3~rc2-1 all interactive high-level object-oriented language (default version)
ii python-cwiid 0.6.00+svn201-3 armhf library to interface with the wiimote
ii python-dbus 1.1.1-1 armhf simple interprocess messaging system (Python interface)
ii python-dbus-dev 1.1.1-1 all main loop integration development files for python-dbus
ii python-gi 3.2.2-1 armhf Python 2.x bindings for gobject-introspection libraries
ii python-gobject-2 2.28.6-10 armhf deprecated static Python bindings for the GObject library
ii python-imaging 1.1.7-4 armhf Python Imaging Library
ii python-imaging-tk 1.1.7-4 armhf Python Imaging Library - ImageTk Module
ii python-minimal 2.7.3~rc2-1 all minimal subset of the Python language (default version)
ii python-numpy 1:1.6.2-1 armhf Numerical Python adds a fast array facility to the Python language
ii python-pygame 1.9.1release+dfsg-6 armhf SDL bindings for games development in Python
ii python-smbus 3.1.0-2 armhf Python bindings for Linux SMBus access through i2c-dev
ii python-support 1.0.15 all automated rebuilding support for Python modules
ii python-tk 2.7.3-1 armhf Tkinter - Writing Tk applications with Python
ii python2.7 2.7.3~rc2-2.1 armhf Interactive high-level object-oriented language (version 2.7)
ii python2.7-dev 2.7.3~rc2-2.1 armhf Header files and a static library for Python (v2.7)
ii python2.7-minimal 2.7.3~rc2-2.1 armhf Minimal subset of the Python language (version 2.7)
I also have RPi.GPIO-0.4.0a installed (I had to download it and build it from source - you may find the raspbian package works but it stopped working for me after I did an apt-get upgrade on my pi, grr.
Download my code from github (or fork it and download your own fork):
git clone git://github.com/hydra/PixelPi.git
git checkout ambipi
If you've not used git before then visit gitready.com or other git sites
run PixelPi in my new AmbiPi mode (only available from my fork currently), set your chip, ip/port and leds as appropriate. sudo is required because of the way the python gpio libraries work.
sudo python pixelpi.py ambipi --chip WS2801 --udp-ip 192.168.1.142 --udp-port 20434 --num_leds 104
You can use the fade, chase, all_on and all_off modes to test your LED and wiring first.
If you use the all_on mode of pixel pi to test you can see if you need more power as the lights might not be bright enough or your Pi might suffer from low voltage due to the load. I also applied power at BOTH ENDS of each chain/strip. otherwise the lights at one end are not as bright as the other end.
Then for the XBMC side of things... Ideally you'll want to be able to download and build XBMC yourself but that is the best way. You'll need visual studio (the free one works) and a git client.
Fork my XBMC repository and checkout the appropriate branch and build it.
You'll need to make sure the dependency dll's are copied to the right place in order to run it.
I'll package up my work-in-progress build and attempt to attach it to this thread in a few minutes.
Once you've got XBMC up and running find the AmbiPi options in the menus - System/Input Devices/Peripherals/AmbiPi.
Enable it and set the IP address of the Pi. the default port should be kept at port 20434.
Ensure your Pi and your PC can talk to each other via UDP on that port. i.e. check your firewalls!
Once you've done that the LED's should light up and you're good to go!
After that you may wish to ensure that PixelPi starts automatically on your Pi when it starts up. That I'll leave as an exercise to the reader but if you create any shell scripts or similar please share them with me and I can include them with the project.