This is an old revision of the document!
The rear wall of the main brmlab room faces the street around the building.
There is a row of 23 square glass blocks at the top of the wall that are
translucent and visible from the outside.
We would like to make a 23×1 pixel RGB display out of these glass blocks,
showing cool animations and funky patterns 'round the clock, possibly also
indicating open/closed brmlab status. It could be controlled by custom
programs, over the net or interactively using e.g. a hacked music keyboard!
Indicator of brmdoor status
Simple patterns - progress bar, Nightrider KITT-like animation, …
Binary clock, morse code transmissions
Simple rainbow - shifting, but only very slowly (e.g. barely perceptible if brmlab is closed, much faster if open)
Fancy full-color animations - no limit for your imagination!
MIDI keyboard control for interactive creative pattern-making (“play light”)
Part of an interactive brmlab geocache
1D cellular automaton (modification of game-of-life or some similar random-patterns)
1D digital lavalamp (multiple blocks are slowly moving from left to right and backwards)
by adding few infra detectors react to the feet movements of the people going around
As of 20.8.2012, we have 20 LEDs hooked up and working, connected to the sargon computer, with good prospects of getting the rest working too. You can control these LEDs over the LAN, see roadmap for details for now.
[HW] In all LED boxes, replace 4ohm resistor by 8ohm resistor on LED channel
[SW] Port remaining C animations to Python
[SW] Improve Python ledbar class to reduce redundancy in animation scripts
Each glass block will be illuminated by a single RGB LED node; 23 nodes shall
be chained together with possibility of individual control.
Each node consists of three LEDs (R, G, B) with sufficient
luminiscence. Each LED is hooked to PWM-capable control for smooth
brightness control. The node needs to hold the LEDs in stable position and
direct most of the light at the glass block, also dispersing it evenly.
The node chain needs to be hooked up to a microcontroller. The LEDs might
require non-trivial current, so intermediate transistors are
required. We need to PWM-control 23*3 = 69 individual outputs.
The microcontroller will be connected to a computer (e.g. sargon) and some
simple control software.
Version 2 is based on TLC59116 constant-current sink LED driver with I2C interface. TLC59116F could be also used, but circuit must be slightly modified (PNP → NPN + base pull-up resistors). Power distribution design is not ideal, current combination (RJ-45 + UTP cable) is not designed for high-current (up to 5 A) applications. In the next version, proper cables and connectors should be used.
TLC59116 allows up to 15 boards on one I2C bus.
Schematics and boards are to be found in Git repository.
Driver board v2.2 part list
Verify your wiring. In twisted pair, if you have the wrong wire connected, for a single TLC it will work because the signal will induce to the other wire in the pair. For anything further a single TLC, the rest of the other wire will work as antenna and a lot of other mess will induce on it too.
Verify your traces, and double check. The other problem was found to be due to etching bug - we have verified and fixed couple of interrupted trace on that board before, but missed this one.
Arduino Wiring library should be supplied with only 7-bit address.
The software is in Git: http://github.com/brmlab/ledbar
Two versions of firmware are available; standalone firmware with some builtin animations, and controlled firmware accepting raw RGB pixel value blocks on the serial.
The control software can either just show pixels on the display, or when given a device name (/dev/ttyUSB0), it will also send pixel values to the Arduino.
GitHub, last commits
[DONE] Try out various kinds of LEDs for a single node
We have a power RGB LED from DealExtreme, but we do not trust DealExtreme enough for 23 LEDs operated non-stop, heavy duty, for at least few years.
We have decided on http://www.gme.cz/cz/l-lxhl-hprgb-p511-558.html
; we are capable of driving them by 250-400mA per channel, green is the one most difficult to feed with enough current. However, it seems there is minimal difference in brightness between 250mA and 350mA for any channel, so we will drive with reduced PWM now (and be prepared to increase it in case of too high resistance in wires etc.).
[DONE] Try out various node construction designs, build all 23 node boxes
[DONE] Get final amount of LEDs
[DONE] We have two test LEDs, plus one from TomSuch that may be the same kind
[DONE] All LEDs are bought, resistor values tuned. (2.7ohm for each channel)
[DONE] One of the pixels is broken, we need new LED for it (and reuse / rebuild casing)
[IN PROGRESS] Design and build the control circuit
[SCRAPED] We used TLC5940 and built all control boards too, but it was impossible to drive five TLC5940 using few meters of cable - too high signal distortion, also the circuits are very fragile.
[DONE] Arduino shield for TLC connectivity.
[DONE] Power distribution board, hooked up to strong 5V current source (ATX PSU).
[WIP] New TLC59116 boards.
[DONE] Implement the control firmware for the microcontroller
[TODO] We need to tune the pixel brightness and color profiles.
[TODO] Figure out how to solidly mount the pixels on the wall.
[IN PROGRESS] Write and continue improving the computer control software
[WIP] Network-based animation dispatcher.
[SCRAPED] brmlab@blinkenlight screen runs network → arduino link, listening for 23*3 R,G,B byte sequences on UDP port 17740
brmlab@blinkenlight screen runs ledbar control software
Default: audio spectrogram of our main mixer speaker output; you can use alsamixer to switch it to microphone (brmlab ambient noise), but you will want to recalibrate the spectrogram to frequencies 100..2000.
TODO: Proper multiplexing of default animation and network traffic, perhaps also status-based and noise-level based? (Show sound spectrum in case music is playing.)
[TODO] Interface for creating animations.
[TODO] Web user interface for controlling animations.
(DONE) 24 RGB LEDs - 23 pixels, one spare. L-LXHL-HPRGB
(DONE) LED holders - something sturdy and wide enough; we are cutting and gluing them from Club Mate boxes.
(IN PROGRESS) Wiring, transistors, resistors, etc.
(DONE) PWM drivers
(DONE) Arduino hooked up to a PC that controls the animation
We need to get 24 LEDs (23 + 1 spare). The money required is CZK 150 per LED - it is a bit expensive, but it covers an extremely bright RGB LED, well visible through the glass even in bright daylight and from reliable origin. A bit of extra change is welcome to cover the supporting electronics (transistors alone cost 300CZK).
The LEDs you donated will have your nick written on the back of their boxes, to keep eternal memory of your contribution!
| nick || LEDs || CZK amount ||
| pasky || 2 || 300 || (paid)
| chido || 2 || 300 || (paid)
| TomSuch || 4 || 610 || (paid)
| niekt0 || 1 || 160 || (paid)
| kxt || 2 || 300 || (paid)
| AyM || 2 || 300 || (paid)
| Kiki || 2.6 || 400 || (paid)
| stick || 1.3 || 200 || (paid)
| Nephirus || 1.3 || 200 || (paid)
| biiter || 1 || 160 || (paid)
| johny || 2 || 300 || (paid)
| dzoe || 2 || 407+93 || (paid)
| AxTheB || 1 || 160 || (paid)
Total LEDs sponsored: 24
LEDs to go: 0
Sargon will donate brmduino + FTDI to replace current pasky's arduino to drive the circuit!
Later, we can extend the display also to the storage room (extra 9-pixel
row, and half of the second row visible too).
We might also try to split a single glass block to 2×2 pixel matrix.
But let's start simple!
Sargon arranged TI samples of TLC5940. These are fancy serial-controllable, daisy-chainable LED drivers, each has 16 PWM current sink outputs. Each output is hooked up to the base of a PNP power transistor (part TODO), with LED cathode on the emitor. TLC current is limited to less than 10mA per channel using a 2k7 resistor on the current control pin. 100nF bypass capacitor per chip.
We need five TLCs to drive 23 RGB LEDs; we have a bunch, slightly less than we need. They are very fragile if too much current is drawn or there is bad connection where there shouldn't be, so we need to monitor them carefully anytime a change in circuit is made. During development (probably mostly due to low-quality breadboard), we destroyed about six pieces.
We already had all five TLCs set up on a breadboard, daisy chaining set up and working transistor drive.
Connectors: We use RJ45 connectors and ethernet cables for all interconnects. Should handle the currents fine and it is robust, easy to get and quick to crimp.
ledbar v2: ledbar.sch ledbar.brd
ledbar DC interconnect v2: ledbar-dc.sch ledbar-dc.brd
ledbar brmduino shield v2: Eagle files
Current is now sourced in ATX supply. We consider replacing it with: http://www.djoro.cz/store/goods-G583---.html
69 I/O pins is a lot. We will need to separate the outputs to segments (“cycles”) and also have one pin per cycle to switch between them. And rely on persistence of vision; we need to have at least 50hz frame-rate (i.e. all cycles finishing in 1/50s).
Classic charlieplexing probably will not work well with PWM at all. But with just five cycle control PINs required, something simpler could work nicely:
`--(LED)--. | (LED) is
| | transistor
PWM1 o-*--(LED)--+-* plus LED
| | |
C0 o-----------|< |
Microcontrollers generally do not have interestingly large number of hardware PWMs, but since we will be doing little else than driving the LEDs in our software, we can simply do the PWMs in software with more than enough resolution (8-bit ideally, but 5-bit would be probably already fine). E.g. ArduinoMega2560 has 54 output PINs, so just two cycles per frame would do, with some spare time to receive pixmap updates.
Price for seeeduino mega: ~900CZK.
Plus: Not much soldering required. Single board = easy debugging.
Minus: Relies on POV (can flicker slightly and such). Limited time to receive pixmap updates. *Huge* amount of *very long* wires, operating at high frequencies = hard debugging. High price.
Each few pixels will be controlled by a separate microcontroller. All LEDs will be lit at once. The microcontrollers will share just a data bus (e.g. TWI).
The cheapest we can go is probably ATTiny26L, single microcontroller can operate three pixels (12 outputs). One uC would operate just two pixels = spare pins + time for serial-TWI interface.
In this case, it would be probably worth it having a PCB fabbed too.
Price for 7 microcontrollers: ~210CZK.
Plus: Low price. Few wires = easy debugging. No POV reliance. Much less sensitive to pixel reprogramming interference.
Minus: A lot more soldering. Many boards = hard debugging.