Sound Sabre

From FamiLAB Wiki
(Difference between revisions)
Jump to: navigation, search
(Component Ideas)
(Design Tradeoffs)
 
(6 intermediate revisions by 2 users not shown)
Line 10: Line 10:
 
* Individually addressable
 
* Individually addressable
 
* RGB
 
* RGB
* PWM
+
* PWM (Constant current would be nice)
 +
* Wifi / bluetooth would be nice
 +
* Accelerometer
 +
* All through-hole would make for a better kit
 +
* Voltage regulation each board?
  
 
== Design Details ==
 
== Design Details ==
 
* Round PCB for light nodes
 
* Round PCB for light nodes
 
* I2C for communications bus
 
* I2C for communications bus
 +
 +
== Design Tradeoffs ==
 +
* Making each board fully functional as a stand-alone kit makes the complexity / price of the Sabre more expensive
 +
* Using a networking protocol like i2c vs. shift registers or direct wiring or charlieplexing provides more flexibility, but also more complexity
 +
* The LED density increases resolution, but increases cost and complexity
 +
* Adding a wireless protocol like wifi or bluetooth allows multi-sabre connection (BATTLE!) but makes the sabre more expensive
 +
* More LEDs / Higher Brightness LED = more current = larger battery (size / weight considerations) or shorter battery life
 +
* Is the Sabre a product? Are the individual boards a product? Is the goal to have fun & learn, or make money? - they may be mutually excusive
 +
* Through-hole construction makes for a better kit, but drives size / cost up
  
 
== Component Ideas ==
 
== Component Ideas ==
 
* Attiny2313 SOIC
 
* Attiny2313 SOIC
 
* SMD RGB LEDS
 
* SMD RGB LEDS
* [http://www.sparkfun.com/products/10468|MSGEQ7] or FFT
+
* [http://www.sparkfun.com/products/10468 MSGEQ7] or  
 +
** [http://skoba.no-ip.org/msgeq7/ MSGEQ7 Instructions]

Latest revision as of 12:49, 24 September 2011

Contents

Purpose

Requirements

Design Details

Design Tradeoffs

Component Ideas

Personal tools
Namespaces
Variants
Actions
Navigation
Toolbox