Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revisionLast revisionBoth sides next revision | ||
uberbus:moodlamp [2011/03/13 19:15] – ubd link added 9r | uberbus:moodlamp [2015/12/02 20:32] – [Preparations] 9r | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | To use moodlamps with the IPv6 enabled uberbus you have to follow the steps outlined on this page. | + | To use moodlamps with the IPv6 enabled |
====== Preparations ====== | ====== Preparations ====== | ||
Line 5: | Line 5: | ||
To use the lamp with the uberbus a new firmware has to be flashed. To build your new firmware follow these steps on a Debian based Linux computer: | To use the lamp with the uberbus a new firmware has to be flashed. To build your new firmware follow these steps on a Debian based Linux computer: | ||
+ | |||
+ | :!: Note: There seems to be an obscure issue with current versions (tested with 4.9.2 and 5.2.0) of gcc that results in non-functional firmware even though the build process finishes successfully. Working firmware can be build using gcc 4.5.3 included in e.g. ubuntu precise. | ||
< | < | ||
- | apt-get install gcc-avr avr-libc avrdude make subversion | + | apt-get install gcc-avr avr-libc avrdude make git |
- | svn co https://brezn.muc.ccc.de/svn/uberbus/ | + | git clone git://github.com/muccc/uberbus.git |
- | cd uberbus/trunk/ | + | cd uberbus/ |
make | make | ||
</ | </ | ||
Line 45: | Line 47: | ||
< | < | ||
- | cd uberbus/trunk/ | + | cd uberbus/ |
./ | ./ | ||
</ | </ | ||
Line 91: | Line 93: | ||
Currently there are two folders with example scripts for lamps attached to the uberbus: | Currently there are two folders with example scripts for lamps attached to the uberbus: | ||
===== Python clients ===== | ===== Python clients ===== | ||
- | Under uberbus/trunk/ | + | Under uberbus/ |
See the Readme file included in this directory on how to use those scripts. TODO: create Readme file | See the Readme file included in this directory on how to use those scripts. TODO: create Readme file | ||
Line 97: | Line 99: | ||
A simple example to fade a lamp to a specified color in a specified time is fade.py. You can use it the following way: | A simple example to fade a lamp to a specified color in a specified time is fade.py. You can use it the following way: | ||
< | < | ||
- | uberbus/trunk/ | + | uberbus/ |
</ | </ | ||
The fadeexample script fades a lamp in a loop by sending fade commands to an IPv6 address associated with a lamp. | The fadeexample script fades a lamp in a loop by sending fade commands to an IPv6 address associated with a lamp. | ||
< | < | ||
- | uberbus/trunk/ | + | uberbus/ |
</ | </ | ||
Line 111: | Line 113: | ||
===== bash clients ===== | ===== bash clients ===== | ||
- | Under uberbus/trunk/ | + | Under uberbus/ |
The blink script blinks a lamp by sending color commands via UDP to an IPv6 address associated with a lamp. | The blink script blinks a lamp by sending color commands via UDP to an IPv6 address associated with a lamp. | ||
< | < | ||
- | uberbus/trunk/ | + | uberbus/ |
</ | </ | ||
When using this script with the simplelamp server all lamps connected via RS485 or in reach of the wireless transmitter will start to fade if | When using this script with the simplelamp server all lamps connected via RS485 or in reach of the wireless transmitter will start to fade if | ||
they receive the commands. | they receive the commands. |