Difference between revisions of "Wall of Faces"
(→Code) |
(some strong opposition (as you must already know)) |
||
| Line 1: | Line 1: | ||
| − | =Overview= | + | == Overview == |
| − | The wall of faces will have members photos and names on it. They will light up if a member is within the space. | + | The wall of faces will have members' photos and names on it. They will light up if a member is within the space. |
This was started as we grew and people could not put names to faces of members. | This was started as we grew and people could not put names to faces of members. | ||
Obviously a high-tech touch has been added. | Obviously a high-tech touch has been added. | ||
| Line 12: | Line 12: | ||
This will probably be in the form of a kit which members get the chance to build - including laser cut pieces and soldering the board. | This will probably be in the form of a kit which members get the chance to build - including laser cut pieces and soldering the board. | ||
| − | =Boxes= | + | == Boxes == |
| − | |||
The boxes will be 60(h) x 60(l) x 30mm(w).<br> | The boxes will be 60(h) x 60(l) x 30mm(w).<br> | ||
The design was created using [http://boxmaker.rahulbotics.com/ BoxMaker].<br> | The design was created using [http://boxmaker.rahulbotics.com/ BoxMaker].<br> | ||
| Line 23: | Line 22: | ||
[[File:walloffaces4.jpeg|300px]]<br> | [[File:walloffaces4.jpeg|300px]]<br> | ||
| − | =Circuit= | + | == Circuit == |
* Use 4 RGB LED's [http://www.rapidonline.com/Electronic-Components/Piranha-Rgb-Led-72-8998] | * Use 4 RGB LED's [http://www.rapidonline.com/Electronic-Components/Piranha-Rgb-Led-72-8998] | ||
** Phenoptix have these in either Common Anode or Cathode | ** Phenoptix have these in either Common Anode or Cathode | ||
| Line 35: | Line 34: | ||
* I2C communications protocol | * I2C communications protocol | ||
| − | =Code= | + | == Code == |
Simple code - when a command comes through (a unique identifier) then the light swicthes ON (also can send an OFF command). | Simple code - when a command comes through (a unique identifier) then the light swicthes ON (also can send an OFF command). | ||
| Line 45: | Line 44: | ||
* http://arduino.cc/playground/Code/USIi2c Playground article on the ATtiny I2C | * http://arduino.cc/playground/Code/USIi2c Playground article on the ATtiny I2C | ||
| − | =I2C Command structure= | + | == I2C Command structure == |
Need to define the command system for turning on and off the RGB led's<br /> | Need to define the command system for turning on and off the RGB led's<br /> | ||
Needs to be simple so that changes down the line to add more functionality are only needed at the Main Controller rather than re-flashing every module<br/> | Needs to be simple so that changes down the line to add more functionality are only needed at the Main Controller rather than re-flashing every module<br/> | ||
| Line 56: | Line 55: | ||
*More on this to follow --[[User:Lwk|'RepRap' Matt]] 18:47, 1 April 2012 (EST) | *More on this to follow --[[User:Lwk|'RepRap' Matt]] 18:47, 1 April 2012 (EST) | ||
| − | =Main Controller= | + | == Main Controller == |
A controller will be required to take the info from gatekeeper (which knows when an RFID tag has been read) and output a command to turn on the correct box. | A controller will be required to take the info from gatekeeper (which knows when an RFID tag has been read) and output a command to turn on the correct box. | ||
| Line 62: | Line 61: | ||
Posible a nanode with [https://github.com/njh/NanodeMQTT NanodeMQTT] to decode the MQTT and then send commands out via the I2C bus.<br/> | Posible a nanode with [https://github.com/njh/NanodeMQTT NanodeMQTT] to decode the MQTT and then send commands out via the I2C bus.<br/> | ||
| − | =Cost= | + | == Cost == |
| − | |||
* ATtiny85 from RS ATTINY85V-10PU 696-2339P | * ATtiny85 from RS ATTINY85V-10PU 696-2339P | ||
** 10+ £1.74 | ** 10+ £1.74 | ||
| Line 79: | Line 77: | ||
* Laser time | * Laser time | ||
| + | == Strong objections == | ||
| + | '''It reinforces feelings of social exclusion''' - A wall of white male faces is inevitable, at least in the short term, and this will evoke feelings of exclusion. To have a diverse community, we need to make people feel they belong, and a Wall of Faces is unhelpful here. | ||
| + | |||
| + | '''It contributes to an ego-rich environment''' - Where people project their egos into the space, and pat themselves on the back for doing it in an elaborate way. | ||
| + | |||
| + | '''It is not appropriate for our environment''' - A wall of mugshots is typical on a school, university, or 'rugby club' wall. The hackspace should appeal to people who want to get away from the conventions of institutions like this. | ||
| + | |||
| + | '''You already know this Wall of Faces will upset some regular users of the hackspace''' - These objections have already been expressed for a long time, so it's not clear why these elaborate (and apparently pointless) plans have been made. Disputes like this are sapping energy from more worthwhile projects. | ||
[[Category:Projects]] | [[Category:Projects]] | ||
[[Category:Current Projects]] | [[Category:Current Projects]] | ||
Revision as of 21:07, 3 April 2012
Overview
The wall of faces will have members' photos and names on it. They will light up if a member is within the space. This was started as we grew and people could not put names to faces of members. Obviously a high-tech touch has been added.
The wall will comprise of a number of boxes. Each box will have the members photo and name. The boxes will be laser cut and all fit together to build a whole wall. Each box will also contain a circuit board. This will have LED backlighting and a microcontroller (probably an ATtiny48/85). When a member is in the space (via their RFID tag) then their image will light up. Members do not swipe out, so at the end of every day then all the backlighting will reset. This will give a record of who was in the space that day.
This will probably be in the form of a kit which members get the chance to build - including laser cut pieces and soldering the board.
Boxes
The boxes will be 60(h) x 60(l) x 30mm(w).
The design was created using BoxMaker.
More on making project boxes is here http://support.ponoko.com/entries/20344437-laser-cut-project-box-tutorial.
The initial prototype is here:
Circuit
- Use 4 RGB LED's [1]
- Phenoptix have these in either Common Anode or Cathode
- http://www.phenoptix.com/index.php/through-hole/superflux-piranha/superflux-piranha-led-5mm-dome-rgb-ca.html
- http://www.phenoptix.com/index.php/through-hole/superflux-piranha/superflux-piranha-led-5mm-dome-rgb-cc.html
- Transistor to control LEDs
- ATtiny45/85
- I've ordered up 5 ATTINY85V-10PU for testing --'RepRap' Matt 18:18, 1 April 2012 (EST)
- 4 way connector (male on 2 edges, female on 2 edges), so they can plug together as a grid.
- 4 wire: +5V , GND, CLOCK, DATA
- I2C communications protocol
Code
Simple code - when a command comes through (a unique identifier) then the light swicthes ON (also can send an OFF command).
Firmware available here
https://github.com/NottingHack/Wall-of-Faces
- http://code.google.com/p/arduino-tiny/ ATtiny core project, for using Arduino IDE
- http://code.google.com/p/arduino-tiny/wiki/TWIMasterLibrary I2c/TWI master Library for use with above, first glance might be out of date
- http://arduino.cc/playground/Code/USIi2c Playground article on the ATtiny I2C
I2C Command structure
Need to define the command system for turning on and off the RGB led's
Needs to be simple so that changes down the line to add more functionality are only needed at the Main Controller rather than re-flashing every module
May follow BlinkM command structure http://thingm.com
Using the 10bit addressing with I2C
http://www.i2c-bus.org/addressing/10-bit-addressing/
Standard TWI/I2C on avr uses 7 bit address space this allows for 0-127 devices on a single bus, its possible to use a 10 bit address space but its going to need some custom code for both the ATmega328 and the ATtiny85 :(
- More on this to follow --'RepRap' Matt 18:47, 1 April 2012 (EST)
Main Controller
A controller will be required to take the info from gatekeeper (which knows when an RFID tag has been read) and output a command to turn on the correct box.
The Gatekeeper process on Holly will send ON commands with unique member id's
Posible a nanode with NanodeMQTT to decode the MQTT and then send commands out via the I2C bus.
Cost
- ATtiny85 from RS ATTINY85V-10PU 696-2339P
- 10+ £1.74
- 25+ £1.59
- ATtiny45 from RS ATTINY45V-10PU 696-2320P
- 10+ £1.38
- 25+ £1.26
- RGB led's
- Headers
- PCB
- Capacitor
- Transistor
- Wood
- 2 per box's per A4 sheet aprox
- Laser time
Strong objections
It reinforces feelings of social exclusion - A wall of white male faces is inevitable, at least in the short term, and this will evoke feelings of exclusion. To have a diverse community, we need to make people feel they belong, and a Wall of Faces is unhelpful here.
It contributes to an ego-rich environment - Where people project their egos into the space, and pat themselves on the back for doing it in an elaborate way.
It is not appropriate for our environment - A wall of mugshots is typical on a school, university, or 'rugby club' wall. The hackspace should appeal to people who want to get away from the conventions of institutions like this.
You already know this Wall of Faces will upset some regular users of the hackspace - These objections have already been expressed for a long time, so it's not clear why these elaborate (and apparently pointless) plans have been made. Disputes like this are sapping energy from more worthwhile projects.