https://www.noisebridge.net/api.php?action=feedcontributions&user=Elgreengeeto&feedformat=atomNoisebridge - User contributions [en]2024-03-19T01:43:11ZUser contributionsMediaWiki 1.39.4https://www.noisebridge.net/index.php?title=Homebrew_PCB&diff=6566Homebrew PCB2009-07-29T17:09:49Z<p>Elgreengeeto: /* Next */</p>
<hr />
<div>=Homebrew Printed Circuit Boards=<br />
<br />
==What Where When==<br />
<br />
We met at Noisebridge on Saturday, July 25th at 3pm and designed some circuit boards.<br />
<br />
We planned to follow a procedure not unlike this:<br />
<br />
http://www.make-digital.com/make/vol02/?pg=166&pm=2&u1=friend<br />
<br />
==Who==<br />
* [[User:elgreengeeto|Adam Skory]]<br />
* [[User:MCT|Michael Toren]]<br />
* Peter<br />
<br />
==Progress==<br />
<br />
===Saturday, July 25th, 2009===<br />
<br />
We ended up spending most of the time just designing the circuit. We based it on the [[Logo|Noisebridge logo]], incorporating a series of resistors, a speaker, and for fun, an ATTiny25, an LED, and a micro switch. It's powered by a coin-cell, located on the back of the board. It can be programmed to do things! Look! Here's the [http://fuzzybunny.s3.amazonaws.com/meep/useless.sch Eagle CAD schematic], the [http://fuzzybunny.s3.amazonaws.com/meep/useless.brd Eagle board layout], or, if you don't have Eagle, a [http://fuzzybunny.s3.amazonaws.com/meep/useless.pdf PDF].<br />
<br />
<br />
[[Image:Useless.png|400px]]<br />
<br />
<br />
There are a few ideas floating around for how the ATTiny25 can be programmed. One is for the LED to always be on, and for the speaker to make noise when the center button is pressed. It has also been suggested that the speaker play a song (London Bridges Falling Down?).<br />
<br />
<br />
We then tried transferring it to a solid copper board by printing onto magazine paper and then ironing that onto the board (we lacked the proper transfer film). This sorta worked, but not good enough. We subsequently learned that the magazine paper method works best if, after the paper is ironed to the copper, one wets the magazine with soapy water, loosening the fibers and leaving more toner stuck as you pull the paper off.<br />
<br />
==Monday, July 27, 2009==<br />
<br />
Skory got some supposed transfer transparencies at Fry's (they're now somewhere at NB if anyone else wants to try using one). MCT used up a couple minutes of company time, toner, and coffee getting one the sheets printed on. Not without some mishaps, the deed was done - success was achieved.<br />
<br />
Without further ado, a pictorial account:<br />
<br />
[[Image:IMG_7732.jpg]]<br />
[[Image:IMG_7734.jpg]]<br />
[[Image:IMG_7739.jpg]]<br />
[[Image:IMG_7742.jpg]]<br />
[[Image:IMG_7749.jpg]]<br />
[[Image:IMG_7750.jpg]]<br />
[[Image:IMG_7754.jpg]]<br />
[[Image:IMG_7764.jpg]]<br />
[[Image:IMG_7771.jpg]]<br />
[[Image:IMG_7776.jpg]]<br />
[[Image:IMG_7778.jpg]]<br />
[[Image:IMG_7781.jpg]]<br />
[[Image:IMG_7782.jpg]]<br />
[[Image:IMG_7787.jpg]]<br />
<br />
==After next==<br />
<br />
Profit.</div>Elgreengeetohttps://www.noisebridge.net/index.php?title=File:IMG_7787.jpg&diff=6565File:IMG 7787.jpg2009-07-29T17:01:15Z<p>Elgreengeeto: </p>
<hr />
<div></div>Elgreengeetohttps://www.noisebridge.net/index.php?title=File:IMG_7782.jpg&diff=6564File:IMG 7782.jpg2009-07-29T17:00:57Z<p>Elgreengeeto: </p>
<hr />
<div></div>Elgreengeetohttps://www.noisebridge.net/index.php?title=File:IMG_7781.jpg&diff=6563File:IMG 7781.jpg2009-07-29T17:00:47Z<p>Elgreengeeto: </p>
<hr />
<div></div>Elgreengeetohttps://www.noisebridge.net/index.php?title=File:IMG_7778.jpg&diff=6562File:IMG 7778.jpg2009-07-29T17:00:35Z<p>Elgreengeeto: </p>
<hr />
<div></div>Elgreengeetohttps://www.noisebridge.net/index.php?title=File:IMG_7776.jpg&diff=6561File:IMG 7776.jpg2009-07-29T17:00:22Z<p>Elgreengeeto: </p>
<hr />
<div></div>Elgreengeetohttps://www.noisebridge.net/index.php?title=File:IMG_7771.jpg&diff=6560File:IMG 7771.jpg2009-07-29T17:00:09Z<p>Elgreengeeto: </p>
<hr />
<div></div>Elgreengeetohttps://www.noisebridge.net/index.php?title=File:IMG_7764.jpg&diff=6559File:IMG 7764.jpg2009-07-29T16:59:47Z<p>Elgreengeeto: </p>
<hr />
<div></div>Elgreengeetohttps://www.noisebridge.net/index.php?title=File:IMG_7754.jpg&diff=6558File:IMG 7754.jpg2009-07-29T16:59:24Z<p>Elgreengeeto: </p>
<hr />
<div></div>Elgreengeetohttps://www.noisebridge.net/index.php?title=File:IMG_7750.jpg&diff=6557File:IMG 7750.jpg2009-07-29T16:59:09Z<p>Elgreengeeto: </p>
<hr />
<div></div>Elgreengeetohttps://www.noisebridge.net/index.php?title=File:IMG_7749.jpg&diff=6556File:IMG 7749.jpg2009-07-29T16:58:57Z<p>Elgreengeeto: </p>
<hr />
<div></div>Elgreengeetohttps://www.noisebridge.net/index.php?title=File:IMG_7742.jpg&diff=6555File:IMG 7742.jpg2009-07-29T16:58:46Z<p>Elgreengeeto: </p>
<hr />
<div></div>Elgreengeetohttps://www.noisebridge.net/index.php?title=File:IMG_7739.jpg&diff=6554File:IMG 7739.jpg2009-07-29T16:58:36Z<p>Elgreengeeto: </p>
<hr />
<div></div>Elgreengeetohttps://www.noisebridge.net/index.php?title=File:IMG_7734.jpg&diff=6553File:IMG 7734.jpg2009-07-29T16:58:17Z<p>Elgreengeeto: </p>
<hr />
<div></div>Elgreengeetohttps://www.noisebridge.net/index.php?title=File:IMG_7732.jpg&diff=6552File:IMG 7732.jpg2009-07-29T16:58:05Z<p>Elgreengeeto: </p>
<hr />
<div></div>Elgreengeetohttps://www.noisebridge.net/index.php?title=Homebrew_PCB&diff=6494Homebrew PCB2009-07-26T03:38:29Z<p>Elgreengeeto: </p>
<hr />
<div>=Homebrew Printed Circuit Boards=<br />
<br />
==What Where When==<br />
<br />
We met at Noisebridge on Saturday, July 25th at 3pm and designed some circuit boards.<br />
<br />
We planned to follow a procedure not unlike this:<br />
<br />
http://www.make-digital.com/make/vol02/?pg=166&pm=2&u1=friend<br />
<br />
==Who==<br />
*Skory<br />
* [[User:MCT|Michael Toren]]<br />
* Peter<br />
<br />
==Progress==<br />
<br />
We ended spending most of the time just designing the circuit. Here is the [http://fuzzybunny.s3.amazonaws.com/meep/useless.sch Eagle CAD schematic], the [http://fuzzybunny.s3.amazonaws.com/meep/useless.brd Eagle board layout], or, if you don't have Eagle, a [http://fuzzybunny.s3.amazonaws.com/meep/useless.pdf pdf] of it. It has an ATTiny, a button, an led, and a speaker. It can be programmed to do things. Look!<br />
<br />
[[Image:Useless.png|400px]]<br />
<br />
We then tried transferring it to a solid copper board by printing onto magazine paper and then ironing that onto the board (we lacked the proper transfer film). This sorta worked, but not good enough. We subsequently learned that the magazine paper method works best if, after the paper is ironed to the copper, one wets the magazine with soapy water, loosening the fibers and leaving more toner stuck as you pull the paper off.<br />
<br />
==Next==<br />
<br />
We try to get some real transfer sheets or, failing that, try the magazine method with the extra soapy water bath stage. Failing both, we get as far as we can with the magazine, then touch up the print with a sharpie and finally etch these dang boards!<br />
<br />
We will try to meet Monday evening and do some super elite circuit hacking of our own! You are welcome to join. Time is only so far defined as vague eveningish.<br />
<br />
==After next==<br />
<br />
Profit.</div>Elgreengeetohttps://www.noisebridge.net/index.php?title=File:Useless.png&diff=6493File:Useless.png2009-07-26T03:36:21Z<p>Elgreengeeto: </p>
<hr />
<div></div>Elgreengeetohttps://www.noisebridge.net/index.php?title=Homebrew_PCB&diff=6436Homebrew PCB2009-07-22T06:39:13Z<p>Elgreengeeto: New page: =Homebrew Printed Circuit Boards= ==What Where When== We will be meeting at Noisebridge on Saturday, July 25th at 3pm to design and etch some circuit boards. We’ll follow a procedure n...</p>
<hr />
<div>=Homebrew Printed Circuit Boards=<br />
<br />
==What Where When==<br />
<br />
We will be meeting at Noisebridge on Saturday, July 25th at 3pm to design and etch some circuit boards. We’ll follow a procedure not unlike this:<br />
<br />
http://www.make-digital.com/make/vol02/?pg=166&pm=2&u1=friend<br />
<br />
==Who (and what they can bring)==<br />
*Skory (doesn’t have any specific supplies but will purchase as needed since this was his idea).<br />
<br />
==What else we need==<br />
(Dunno yet.)</div>Elgreengeetohttps://www.noisebridge.net/index.php?title=Hack_Notes_CVA_090712&diff=6224Hack Notes CVA 0907122009-07-14T09:54:31Z<p>Elgreengeeto: </p>
<hr />
<div>=hack notes 090712=<br />
<br />
Our v1.0 boards are in! Here are some notes from initial testing:<br />
<br />
*Everything solders in fine, nothing too notable. Start with shorter things and move to taller. Care must be taken to solder compass sockets in the correct order.<br />
*Code uploaded fine, but there were no compass readings the first time<br />
**Solved:<br />
**No compass readings was due to having the compass headers on the backwards! (The de-soldering of which led to the pulling out of a pad and holy sheisse was that an hour long pain in the ass to fix!). So, 2x3 header must be ON TOP and the 1x3 ON BOTTOM of the board. The compass is then oriented with the "RoHS" facing towards the center of the board. In future, the pin labeled "1" on the bottom of the HM55B should be matched with a "1" on our silk screen.<br />
*Added code to set T1 to high all the time.<br />
**A0 as digital out is pin 14, A1 is pin 15<br />
*LED testing thing works as well as it should. (Needs to be re-built for new 16 motor design.)<br />
*First design failure: with the extra clip on, the motor jack does not fit. (The oversize tabs on the clip stick into the edge of the enclosure.) They are not necessary anyway, so the world is not ended.<br />
*Second design failure: the power plug is backwards! The CENTER must be GROUND for it to wor know. Don't know how this happened, and it is annoying.<br />
<br />
<pre><br />
/* Skory & Eric<br />
July 12, 2009<br />
*/<br />
<br />
<br />
/* Some code from:<br />
* 2009-03-24, pager motor test, lamont lucas<br />
*/<br />
/*<br />
Some Hitachi HM55B Compass reading code copied from: kiilo kiilo@kiilo.org<br />
License: http://creativecommons.org/licenses/by-nc-sa/2.5/ch/<br />
*/<br />
<br />
<br />
// define the pins used to run the shift register<br />
int enable_low = 3;<br />
int serial_in = 7;<br />
int ser_clear_low = 5;<br />
int RCK = 4;<br />
int SRCK = 6;<br />
<br />
// define pins for transitors<br />
int transistor_1 = 14; //14 = A0<br />
int transistor_2 = 15; //15 = A1<br />
<br />
#include <math.h><br />
<br />
//// define pins used to operate the digital compass (HM55B)<br />
byte CLK_pin = 10;<br />
byte EN_pin = 9;<br />
byte DIO_pin = 8;<br />
int X_Data = 0;<br />
int Y_Data = 0;<br />
int angle;<br />
int status;<br />
<br />
//timing vars<br />
unsigned long counter = 0;<br />
int prev_motor = 1;<br />
int curr_motor = 1;<br />
int cycles_per_second = 15; //board and compass specific - must measure<br />
int count;<br />
int activity = 100;<br />
int max_activity = 200;<br />
<br />
unsigned long serialTimer = millis();<br />
<br />
int max_motor_strength = 220; // 255 = full power<br />
int min_motor_strength = 90; //point under which motors don't run or are unfeelable<br />
int motor_strength = 210; // holds changing motor strength vals<br />
<br />
void setup() {<br />
pinMode(enable_low, OUTPUT); // set shift register pins as outputs<br />
pinMode(serial_in, OUTPUT);<br />
pinMode(ser_clear_low, OUTPUT);<br />
pinMode(RCK, OUTPUT);<br />
pinMode(SRCK, OUTPUT);<br />
<br />
//set transistors as digital outputs<br />
pinMode(transistor_1, OUTPUT);<br />
pinMode(transistor_2, OUTPUT);<br />
digitalWrite(transistor_1, HIGH); //keep T1 high to control just 8 motors<br />
<br />
// use some serial for debugging<br />
Serial.begin(57600);<br />
Serial.println("Setting up board");<br />
<br />
// make sure we start out all off<br />
digitalWrite(enable_low, HIGH);<br />
// this should wipe out the serial buffer on the shift register<br />
digitalWrite(ser_clear_low, LOW);<br />
delay(100); //delay in ms<br />
<br />
// the TPIC6 clocks work on a rising edge, so make sure they're low to start.<br />
digitalWrite(RCK, LOW);<br />
digitalWrite(SRCK, LOW);<br />
<br />
digitalWrite(ser_clear_low, HIGH); //we are now clear to write into the serial buffer<br />
<br />
Serial.println("Board is setup");<br />
<br />
// setup for HM55B compass chip<br />
pinMode(EN_pin, OUTPUT);<br />
pinMode(CLK_pin, OUTPUT);<br />
pinMode(DIO_pin, INPUT);<br />
<br />
HM55B_Reset();<br />
<br />
//set intial motor strength<br />
analogWrite(enable_low, 255-max_motor_strength);<br />
<br />
}<br />
<br />
<br />
void loop() {<br />
// make the compass get a reading<br />
<br />
HM55B_StartMeasurementCommand(); // necessary!!<br />
delay(40); // the data is ready 40ms later<br />
status = HM55B_ReadCommand();<br />
// Serial.print(status); // read data and print Status<br />
// Serial.print(" ");<br />
X_Data = ShiftIn(11); // Field strength in X<br />
Y_Data = ShiftIn(11); // and Y direction<br />
X_Data = X_Data * -1; // In current rig, chip<br />
Y_Data = Y_Data * -1; // is upside-down; compensate<br />
Serial.print("X: ");<br />
Serial.print(X_Data); // print X strength<br />
Serial.print(" Y: ");<br />
Serial.print(Y_Data); // print Y strength<br />
Serial.print(" ANG: ");<br />
digitalWrite(EN_pin, HIGH); // ok deselect chip<br />
angle = 180 * (atan2(-1 * Y_Data , X_Data) / M_PI); // angle is atan( -y/x) !!!<br />
if (angle < 0) angle = (360 + angle); //offset neg angles<br />
Serial.print(angle); // print angle<br />
Serial.print(" ");<br />
<br />
<br />
//Turn on the appropriate motor while keeping track of time and varying motor strength<br />
curr_motor = CalcMotor(8, angle);<br />
if (curr_motor != prev_motor) { //if we changed angle enough<br />
TurnOnMotor(curr_motor); //turn on the new motor<br />
counter = 0; //reset counter<br />
if (activity < max_activity){<br />
activity = activity + 1; //increase activity level up to 200<br />
motor_strength = (((float)activity / (float)max_activity) * (max_motor_strength - min_motor_strength) + min_motor_strength); //set m_strength proportianately to activity<br />
} // within range of min_ms-max_mas<br />
} else { //if angle hasn't changed<br />
if (counter < (activity / 10) * cycles_per_second) { //only keep same motor on for<br />
analogWrite(enable_low, 255-motor_strength); //less than cycles * activity level<br />
TurnOnMotor(curr_motor);<br />
while (motor_strength < ((float)activity / (float)max_activity) * (max_motor_strength - min_motor_strength) + min_motor_strength){ //if m_strength is low (motors off)<br />
motor_strength++; //crescendo the m_strength<br />
Serial.print(" MS: ");<br />
Serial.println(motor_strength);<br />
analogWrite(enable_low, 255-motor_strength);<br />
delay(50);<br />
}<br />
} else { //if counter runs to upper limit<br />
while (motor_strength > 50){ //if m_strength is high (motors on)<br />
motor_strength--; //decrescendo the m_strength<br />
analogWrite(enable_low, 255-motor_strength); //50 seems like point motor<br />
Serial.print(" MS: "); //stops running<br />
Serial.println(motor_strength);<br />
delay(50);<br />
}<br />
TurnOnMotor(0); //then turn all motors off<br />
}<br />
counter++; //increment counter<br />
if (counter > (600 * cycles_per_second) / activity ){<br />
counter = 0; //reset counter<br />
if (activity > 13){ //lower activity level<br />
activity = activity - 13; //max val(s) 0-12<br />
}<br />
}<br />
}<br />
<br />
analogWrite(enable_low, 255-motor_strength);<br />
prev_motor = curr_motor;<br />
<br />
Serial.print("ACT: ");<br />
Serial.print(activity);<br />
<br />
Serial.print(" CNT: ");<br />
Serial.print(counter);<br />
<br />
Serial.print(" MS: ");<br />
Serial.println(motor_strength);<br />
<br />
<br />
// Serial.print("counter: ");<br />
// Serial.print(counter);<br />
// Serial.print(" activity: ");<br />
// Serial.println(activity);<br />
<br />
/*<br />
//Debug wacky motor wiring disorder <br />
count++;<br />
TurnOnMotor(count);<br />
Serial.print(count); // print angle<br />
Serial.println(" ");<br />
delay(2000);<br />
if (count >= 8)<br />
{<br />
count = 0;<br />
delay(2000);<br />
}<br />
*/<br />
<br />
}<br />
<br />
<br />
<br />
//// FUNCTIONS<br />
<br />
void TurnOnMotor(int which){<br />
// accept which from 1 to 8<br />
// send message to shift register as appropiate<br />
digitalWrite(enable_low, HIGH);<br />
delayMicroseconds(100); //slow and steady<br />
// Serial.print("Motor ");<br />
// Serial.println(which); // print angle<br />
switch(which){<br />
case 5:<br />
shiftOut(serial_in, SRCK, LSBFIRST, B00000010);<br />
break;<br />
case 6:<br />
shiftOut(serial_in, SRCK, LSBFIRST, B00000001);<br />
break;<br />
case 7:<br />
shiftOut(serial_in, SRCK, LSBFIRST, B00000100);<br />
break;<br />
case 8:<br />
shiftOut(serial_in, SRCK, LSBFIRST, B00001000);<br />
break;<br />
case 1:<br />
shiftOut(serial_in, SRCK, LSBFIRST, B10000000);<br />
break;<br />
case 2:<br />
shiftOut(serial_in, SRCK, LSBFIRST, B01000000);<br />
break;<br />
case 3:<br />
shiftOut(serial_in, SRCK, LSBFIRST, B00100000);<br />
break;<br />
case 4:<br />
shiftOut(serial_in, SRCK, LSBFIRST, B00010000);<br />
break;<br />
case 9:<br />
shiftOut(serial_in, SRCK, LSBFIRST, B11111111);<br />
break;<br />
case 10:<br />
shiftOut(serial_in, SRCK, LSBFIRST, B11110000);<br />
break;<br />
case 11:<br />
shiftOut(serial_in, SRCK, LSBFIRST, B00001111);<br />
break;<br />
default:<br />
// turn them all off<br />
shiftOut(serial_in, SRCK, LSBFIRST, B00000000);<br />
} <br />
//in all cases, pulse RCK to pop that into the outputs<br />
delayMicroseconds(100);<br />
digitalWrite(RCK, HIGH);<br />
delayMicroseconds(100);<br />
digitalWrite(RCK, LOW);<br />
}<br />
<br />
<br />
<br />
<br />
int CalcAngle(int howMany, int which)<br />
{ // function which calculates the "switch to next motor" angle<br />
// given how many motors there are in a circle and which position you want<br />
// assume which is 1-indexed (i.e. first position is 1, not zero)<br />
// assume circle is 0-360, we can always offset later...<br />
<br />
return (360/howMany*(which-0.5));<br />
}<br />
<br />
int CalcMotor(int howMany, int angle)<br />
{ // function to calculate which motor to turn on, given<br />
// how many motors there are and what the current angle is<br />
// assumes motor 1 = angle 0<br />
// assumes angle is from 0-360<br />
int i;<br />
for (i = 1; i<howMany;i++)<br />
{<br />
if ( (angle >= CalcAngle(howMany, i)) & (angle <= CalcAngle(howMany, i+1)) )<br />
return i+1; <br />
} <br />
// if we're still here, it's the last case, the loop over case, which<br />
// is actually motor 1 by assumption<br />
return 1;<br />
}<br />
<br />
<br />
<br />
<br />
//HM55B Functions<br />
<br />
void ShiftOut(int Value, int BitsCount) {<br />
for(int i = BitsCount; i >= 0; i--) {<br />
digitalWrite(CLK_pin, LOW);<br />
if ((Value & 1 << i) == ( 1 << i)) {<br />
digitalWrite(DIO_pin, HIGH);<br />
//Serial.print("1");<br />
}<br />
else {<br />
digitalWrite(DIO_pin, LOW);<br />
//Serial.print("0");<br />
}<br />
digitalWrite(CLK_pin, HIGH);<br />
delayMicroseconds(1);<br />
}<br />
}<br />
<br />
int ShiftIn(int BitsCount) {<br />
int ShiftIn_result;<br />
ShiftIn_result = 0;<br />
pinMode(DIO_pin, INPUT);<br />
for(int i = BitsCount; i >= 0; i--) {<br />
digitalWrite(CLK_pin, HIGH);<br />
delayMicroseconds(1);<br />
if (digitalRead(DIO_pin) == HIGH) {<br />
ShiftIn_result = (ShiftIn_result << 1) + 1; <br />
}<br />
else {<br />
ShiftIn_result = (ShiftIn_result << 1) + 0;<br />
}<br />
digitalWrite(CLK_pin, LOW);<br />
delayMicroseconds(1);<br />
}<br />
//Serial.print(":");<br />
<br />
// below is difficult to understand:<br />
// if bit 11 is Set the value is negative<br />
// the representation of negative values you<br />
// have to add B11111000 in the upper Byte of<br />
// the integer.<br />
// see: http://en.wikipedia.org/wiki/Two%27s_complement<br />
if ((ShiftIn_result & 1 << 11) == 1 << 11) {<br />
ShiftIn_result = (B11111000 << 8) | ShiftIn_result; <br />
}<br />
<br />
<br />
return ShiftIn_result;<br />
}<br />
<br />
void HM55B_Reset() {<br />
pinMode(DIO_pin, OUTPUT);<br />
digitalWrite(EN_pin, LOW);<br />
ShiftOut(B0000, 3);<br />
digitalWrite(EN_pin, HIGH);<br />
}<br />
<br />
void HM55B_StartMeasurementCommand() {<br />
pinMode(DIO_pin, OUTPUT);<br />
digitalWrite(EN_pin, LOW);<br />
ShiftOut(B1000, 3);<br />
digitalWrite(EN_pin, HIGH);<br />
}<br />
<br />
int HM55B_ReadCommand() {<br />
int result = 0;<br />
pinMode(DIO_pin, OUTPUT);<br />
digitalWrite(EN_pin, LOW);<br />
ShiftOut(B1100, 3);<br />
result = ShiftIn(3);<br />
return result;<br />
}<br />
</pre><br />
<br />
[[Category:Sensebridge]]</div>Elgreengeetohttps://www.noisebridge.net/index.php?title=Hack_Notes_CVA_090712&diff=6199Hack Notes CVA 0907122009-07-13T21:51:48Z<p>Elgreengeeto: New page: =hack notes 090712= Our v1.0 boards are in! Here are some notes from initial testing: *Everything solders in fine, nothing too notable. Start with shorter things and move to taller. Care...</p>
<hr />
<div>=hack notes 090712=<br />
<br />
Our v1.0 boards are in! Here are some notes from initial testing:<br />
<br />
*Everything solders in fine, nothing too notable. Start with shorter things and move to taller. Care must be taken to solder compass sockets in the correct order.<br />
*Code uploaded fine, but there were no compass readings the first time<br />
**Solved:<br />
**No compass readings was due to having the compass headers on the backwards! (The de-soldering of which led to the pulling out of a pad and holy sheisse was that an hour long pain in the ass to fix!). So, 2x3 header must be ON TOP and the 1x3 ON BOTTOM of the board. The compass is then oriented with the "RoHS" facing towards the center of the board. In future, the pin labeled "1" on the bottom of the HM55B should be matched with a "1" on our silk screen.<br />
*Added code to set T1 to high all the time.<br />
**A0 as digital out is pin 14, A1 is pin 15<br />
*LED testing thing works as well as it should. (Needs to be re-built for new 16 motor design.)<br />
*First design failure: with the extra clip on, the motor jack does not fit. (The oversize tabs on the clip stick into the edge of the enclosure.) They are not necessary anyway, so the world is not ended.<br />
<br />
[[Category:Sensebridge]]</div>Elgreengeetohttps://www.noisebridge.net/index.php?title=Alarm&diff=5873Alarm2009-06-25T03:08:16Z<p>Elgreengeeto: New page: Image:IMG_7412.JPG</p>
<hr />
<div>[[Image:IMG_7412.JPG]]</div>Elgreengeetohttps://www.noisebridge.net/index.php?title=File:IMG_7412.JPG&diff=5872File:IMG 7412.JPG2009-06-25T03:07:07Z<p>Elgreengeeto: </p>
<hr />
<div></div>Elgreengeetohttps://www.noisebridge.net/index.php?title=Hack_Notes_CVA_090619&diff=5738Hack Notes CVA 0906192009-06-20T05:50:22Z<p>Elgreengeeto: /* Velcro Enclosures */</p>
<hr />
<div>=North Paw Hack Notes, June 19th, 2009=<br />
<br />
==New Jack Part==<br />
<br />
Old jack part was 10mm tall, huge! New part is CP-036D-ND, only 5mm tall. Footprint was tricky - stat sheet is very misleading about the size of the contacts, and Eagle complained, and then we found real size...<br />
<br />
==Sample of Display Loop==<br />
<br />
I contacted Buy Loop and Hook today and they (a) don't have any "strips" or "ribbons" of the Display Loop material but (b) do send out samples of the material. We will be getting a 1'x1' piece of gray display loop, should be sufficient to evaluate whether it will work for us.<br />
<br />
==Searching for Small Enclosure==<br />
<br />
Turns out enclosures are very hard to search for. After much agony, I found only a couple of suitable parts. But first, some criteria: we wanted plastic (cheaper, doesn't short, lighter, etc), we needed at least one and preferably two "panels" (ends that are removable/customizable), and wanted small: <3x2x1, and we wanted some kind of mount points for a PCB. The hardest part was the height: almost everything is more than an inch in height. In fact we finally had to settle on this front.<br />
<br />
The part we chose finally: [http://www.pactecenclosures.com/Plastic-Enclosures/JM-22.html PanTec JM-22], 2.4 x 2.2 x 1 in, 2 screws, enclosure presses against PCB to hold it in place, 2 panels. $2.84 for <100, $2.20 >=100. Eric will try to get samples, or purchase several if necessary.<br />
<br />
Other parts and links that might be handy for other people: [http://www.industrial-enclosures.com/html/ks003-plastic-enclosures.html Industrial Enclosure] - too long for us, but they do have small heights. [http://www.hammondmfg.com/dwg8.htm Hammond Mfg] - either too tall, or too long. [http://www.polycase.com/category/kt-series.html PolyCase] - nice size, but lacks panels. [http://www.simcobox.com/ SimcoBox] - too big, lack of panels.<br />
<br />
==Velcro Enclosures==<br />
<br />
Eric proposed that the exposed side of the armature should just be made of a velcro strip, because we have so much velcro on it now anyway (for the closing mechanism, mounting for both the electronics and battery chamber). This would greatly simplify armature sewing, leaving basically only four steps:<br />
<br />
* zipper to rayon<br />
* zipper to velcro<br />
* velcro to rayon<br />
* velcro hook (small piece) to end of velcro<br />
<br />
We might also need to have velcro "latches" to go over the electronics and battery and hold them more firmly i place - this needs to be tested.<br />
<br />
Skory also found a velcro ribbon with sticky stuff on the back - perfect for use on the battery pack and electronics as part of the kit. Some distributors thereof:<br />
<br />
http://cableorganizer.com/velcro-adhesive/<br />
<br />
http://www.textol.com/t_stickyback.asp<br />
<br />
==Board Design==<br />
<br />
With the new low height jack, low height cap, and enclosure dimensions, we feel ready to move unto actual layout of the board. Skory says he's going to work at home on it this weekend.<br />
<br />
==Small Motors Anklet Works==<br />
<br />
I (Eric) finally have a complete working anklet again. I am using the smaller size motors that I got in China. I have to run them at full power (255) to feel them properly - they seem fine with full power. The battery is held with velcro, but the electronics I still have in a pocket. It's a genius idea to rotate the electronics board - the way it is now, the ribbon cable can't help but be way above the armature, making it look funny. Once we get the jack on the side, it'll be possible to internally route it and have only minimal exposure, which will be awesome. Same for the (now necessary) power wires.<br />
<br />
[[Image:NorthPaw_SmallMotors_Beta1PCB.jpg]]</div>Elgreengeetohttps://www.noisebridge.net/index.php?title=Hack_Notes_CVA_090617&diff=5690Hack Notes CVA 0906172009-06-18T01:45:07Z<p>Elgreengeeto: New page: =hacknotes 090617= ==An idea== Messing around with trying to fit two 595 power shift registers onto the next board design and with moving up to an 18-pin socket for the motors the followi...</p>
<hr />
<div>=hacknotes 090617=<br />
<br />
==An idea==<br />
Messing around with trying to fit two 595 power shift registers onto the next board design and with moving up to an 18-pin socket for the motors the following ocurred to me:<br />
*Given that we only want to be able to turn on one motor at a time, having two 595's is quite redundant.<br />
*An 18-pin socket is hella big.<br />
*If we used one 595 plus a switch controlling two separate power rails, we save money and board space and, best of all, control up to 16 motors with a 10-pin socket (assuming that we swap the always-ground pin with the second power rail).<br />
*The drawbacks of this design would be:<br />
**It further complicates the already complicated construction of the pager motor array when needing more than 8 motors<br />
**Using any arbitrary combination of multiple motors could only theoretically be done by switching really quickly between each half really quickly. Doing this with LEDs one would likely see the flickering, doing it with motors however may not be as noticeable?<br />
<br />
==Testing==<br />
I bread-boarded up a circuit with one 595 and two 2N2222 transistors (I don't know where to look for a single switch but I'm sure these exist). With the following code I was able to control 8 leds easily using only 4 sinks on the 595. I couldn't quite work out getting arbitrary combinations by rapid switching to work right.<br />
<br />
==Circuit==<br />
[[Image:IMG_7405.JPG]]<br />
<br />
==Code==<br />
<pre><br />
// define the pins used to run the shift registers <br />
int enable_low = 6; //STR<br />
int serial_in = 2;<br />
int ser_clear_low = 4;<br />
int RCK = 5;<br />
int SRCK = 7;<br />
<br />
//define transistor pins<br />
int T1 = 13;<br />
int T2 = 9;<br />
<br />
int count;<br />
int i;<br />
unsigned long serialTimer = millis();<br />
<br />
void setup() {<br />
pinMode(enable_low, OUTPUT); // set shift register pins as outputs<br />
pinMode(serial_in, OUTPUT);<br />
pinMode(ser_clear_low, OUTPUT);<br />
pinMode(RCK, OUTPUT);<br />
pinMode(SRCK, OUTPUT);<br />
<br />
// use some serial for debugging<br />
Serial.begin(115200);<br />
Serial.println("Setting up board");<br />
<br />
// make sure we start out all off<br />
digitalWrite(enable_low, HIGH);<br />
// this should wipe out the serial buffer on the shift register<br />
digitalWrite(ser_clear_low, LOW);<br />
delay(100); //delay in ms<br />
<br />
// work on a rising edge, so make sure they're low to start.<br />
digitalWrite(RCK, LOW);<br />
digitalWrite(SRCK, LOW);<br />
<br />
digitalWrite(ser_clear_low, HIGH); //we are now clear to write into the serial buffer<br />
<br />
Serial.println("Board is setup");<br />
<br />
<br />
}<br />
<br />
<br />
void loop() {<br />
<br />
<br />
Debug();<br />
<br />
//promising, but doesn't quite work!<br />
/* for(i=0;i<10000;i++){<br />
analogWrite(T2, 0);<br />
analogWrite(T1, 255);<br />
shiftOut(serial_in, SRCK, LSBFIRST, 00100000);<br />
delayMicroseconds(100);<br />
digitalWrite(RCK, HIGH);<br />
delayMicroseconds(100);<br />
digitalWrite(RCK, LOW);<br />
analogWrite(T1, 0);<br />
analogWrite(T2, 255);<br />
shiftOut(serial_in, SRCK, LSBFIRST, 10000000);<br />
delayMicroseconds(100);<br />
digitalWrite(RCK, HIGH);<br />
delayMicroseconds(100);<br />
digitalWrite(RCK, LOW);<br />
}*/<br />
<br />
<br />
<br />
<br />
}<br />
<br />
<br />
<br />
//// FUNCTIONS<br />
<br />
void Debug(){<br />
for(count=1;count<9;count++){<br />
TurnOnMotor(count);<br />
delay(500);<br />
}<br />
}<br />
<br />
void TurnOnMotor(int which){<br />
// accept which from 1 to 8<br />
// send message to shift register as appropiate<br />
digitalWrite(enable_low, HIGH);<br />
delayMicroseconds(100); //slow and steady<br />
Serial.print("Motor ");<br />
Serial.println(which); // print angle<br />
switch(which){<br />
case 1:<br />
analogWrite(T2, 0);<br />
analogWrite(T1, 255);<br />
shiftOut(serial_in, SRCK, LSBFIRST, 00010000);<br />
break;<br />
case 2:<br />
analogWrite(T2, 0);<br />
analogWrite(T1, 255);<br />
shiftOut(serial_in, SRCK, LSBFIRST, 00100000);<br />
break;<br />
case 3:<br />
analogWrite(T2, 0);<br />
analogWrite(T1, 255);<br />
shiftOut(serial_in, SRCK, LSBFIRST, 01000000);<br />
break;<br />
analogWrite(T2, 0);<br />
analogWrite(T1, 255);<br />
case 4:<br />
shiftOut(serial_in, SRCK, LSBFIRST, 10000000);<br />
break;<br />
case 5:<br />
analogWrite(T1, 0);<br />
analogWrite(T2, 255);<br />
shiftOut(serial_in, SRCK, LSBFIRST, 00010000);<br />
break;<br />
case 6:<br />
analogWrite(T1, 0);<br />
analogWrite(T2, 255);<br />
shiftOut(serial_in, SRCK, LSBFIRST, 00100000);<br />
break;<br />
case 7:<br />
analogWrite(T1, 0);<br />
analogWrite(T2, 255);<br />
shiftOut(serial_in, SRCK, LSBFIRST, 01000000);<br />
break;<br />
case 8:<br />
analogWrite(T1, 0);<br />
analogWrite(T2, 255);<br />
shiftOut(serial_in, SRCK, LSBFIRST, 10000000);<br />
break;<br />
case 0:<br />
shiftOut(serial_in, SRCK, LSBFIRST, 0);<br />
break;<br />
default:<br />
// turn them all off<br />
shiftOut(serial_in, SRCK, LSBFIRST, 0);<br />
} <br />
//in all cases, pulse RCK to pop that into the outputs<br />
delayMicroseconds(100);<br />
digitalWrite(RCK, HIGH);<br />
delayMicroseconds(100);<br />
digitalWrite(RCK, LOW);<br />
analogWrite(enable_low, 0);<br />
}<br />
</pre></div>Elgreengeetohttps://www.noisebridge.net/index.php?title=File:IMG_7405.JPG&diff=5689File:IMG 7405.JPG2009-06-18T01:44:06Z<p>Elgreengeeto: </p>
<hr />
<div></div>Elgreengeetohttps://www.noisebridge.net/index.php?title=Compass_Vibro_Anklet&diff=5688Compass Vibro Anklet2009-06-18T01:43:26Z<p>Elgreengeeto: /* Hack Notes */</p>
<hr />
<div>Eric and Skory are currently working on a vibro-tactile compass in anklet form.<br />
<br />
==The Idea==<br />
<br />
Like everyone, we are inspired by [http://www.wired.com/wired/archive/15.04/esp.html that German dude's belt], but think the big, clunky belt is too impractical. Skory thought of pairing an accelerometer with a compass to build a bracelet that responds to the relative difference in motion of the arm vs. direction to north. Eric suggested doing that instead in an anklet. Running into difficulties with the whole accelerometer business, we're starting simple just building a vibrating anklet, and teaching an Arduino to talk to it and some 2-axis compass chips (we are actively pursuing economical ways of upgrading to a 3-axis chip).<br />
<br />
==Eric's Comments==<br />
Other people have also been inspired by the wired article, see for instance the other Eric: [http://www.exothermia.net/monkeys_and_robots/2009/02/04/on-the-haptic-compass/ On the Haptic Compass] - I've worn this belt and it's actually very intuitive. Note that he used 12 motors. There are many helpful links to parts (sensors, cables, vibrators, Arduinos, etc) in both the article and the comments. I am especially intrigued by Todd's idea of a <i>"“foveated” motor distribution, where you have, say, three motors spaced narrowly across the forehead/belly, and the rest spread out around the less crucial sides and back. This might give you high accuracy where it counts (at the leading edge of most movement) without sacrificing too much function along the rest of the arc."</i><br />
<br />
==Hack Notes==<br />
<br />
[[Hack_Notes_CVA_090324|March 24, 2009]]<br />
<br />
[[Hack_Notes_CVA_090326|March 26, 2009]]<br />
<br />
[[Hack_Notes_CVA_090331|March 31, 2009]]<br />
<br />
[[Hack_Notes_CVA_090405|April 5, 2009]]<br />
<br />
[[Hack_Notes_CVA_090408|April 8, 2009]]<br />
<br />
[[Hack_Notes_CVA_090409|April 9, 2009]]<br />
<br />
[[Hack_Notes_CVA_090411|April 11, 2009]]<br />
<br />
[[Hack_Notes_CVA_090415|April 15, 2009]]<br />
<br />
[[Hack_Notes_CVA_090421|April 21, 2009]]<br />
<br />
[[Hack_Notes_CVA_090423|April 23, 2009]]<br />
<br />
[[Hack_Notes_CVA_090426|April 26, 2009]]<br />
<br />
[[Hack_Notes_CVA_090531|May 31, 2009]]<br />
<br />
[[Hack_Notes_CVA_090601|June 01, 2009]]<br />
<br />
[[Hack_Notes_CVA_090609|June 09, 2009]]<br />
<br />
[[Hack_Notes_CVA_090616|June 16, 2009]]<br />
<br />
[[Hack_Notes_CVA_090617|June 17, 2009]]<br />
<br />
==Directions==<br />
<br />
Ted talked with Skory about the steps to do this and made a document of [[Compass Vibro Anklet Directions]] with steps how to do this. So far it's an untested document but Ted intends to use these steps to try to make one himself.<br />
<br />
[[Category:Sensebridge]]</div>Elgreengeetohttps://www.noisebridge.net/index.php?title=Compass_Vibro_Anklet&diff=5687Compass Vibro Anklet2009-06-18T01:42:59Z<p>Elgreengeeto: /* Hack Notes */</p>
<hr />
<div>Eric and Skory are currently working on a vibro-tactile compass in anklet form.<br />
<br />
==The Idea==<br />
<br />
Like everyone, we are inspired by [http://www.wired.com/wired/archive/15.04/esp.html that German dude's belt], but think the big, clunky belt is too impractical. Skory thought of pairing an accelerometer with a compass to build a bracelet that responds to the relative difference in motion of the arm vs. direction to north. Eric suggested doing that instead in an anklet. Running into difficulties with the whole accelerometer business, we're starting simple just building a vibrating anklet, and teaching an Arduino to talk to it and some 2-axis compass chips (we are actively pursuing economical ways of upgrading to a 3-axis chip).<br />
<br />
==Eric's Comments==<br />
Other people have also been inspired by the wired article, see for instance the other Eric: [http://www.exothermia.net/monkeys_and_robots/2009/02/04/on-the-haptic-compass/ On the Haptic Compass] - I've worn this belt and it's actually very intuitive. Note that he used 12 motors. There are many helpful links to parts (sensors, cables, vibrators, Arduinos, etc) in both the article and the comments. I am especially intrigued by Todd's idea of a <i>"“foveated” motor distribution, where you have, say, three motors spaced narrowly across the forehead/belly, and the rest spread out around the less crucial sides and back. This might give you high accuracy where it counts (at the leading edge of most movement) without sacrificing too much function along the rest of the arc."</i><br />
<br />
==Hack Notes==<br />
<br />
[[Hack_Notes_CVA_090324|March 24, 2009]]<br />
<br />
[[Hack_Notes_CVA_090326|March 26, 2009]]<br />
<br />
[[Hack_Notes_CVA_090331|March 31, 2009]]<br />
<br />
[[Hack_Notes_CVA_090405|April 5, 2009]]<br />
<br />
[[Hack_Notes_CVA_090408|April 8, 2009]]<br />
<br />
[[Hack_Notes_CVA_090409|April 9, 2009]]<br />
<br />
[[Hack_Notes_CVA_090411|April 11, 2009]]<br />
<br />
[[Hack_Notes_CVA_090415|April 15, 2009]]<br />
<br />
[[Hack_Notes_CVA_090421|April 21, 2009]]<br />
<br />
[[Hack_Notes_CVA_090423|April 23, 2009]]<br />
<br />
[[Hack_Notes_CVA_090426|April 26, 2009]]<br />
<br />
[[Hack_Notes_CVA_090531|May 31, 2009]]<br />
<br />
[[Hack_Notes_CVA_090601|June 01, 2009]]<br />
<br />
[[Hack_Notes_CVA_090609|June 09, 2009]]<br />
<br />
[[Hack_Notes_CVA_090616|June 16, 2009]]<br />
<br />
[[Hack_Notes_CVA_090616|June 17, 2009]]<br />
<br />
==Directions==<br />
<br />
Ted talked with Skory about the steps to do this and made a document of [[Compass Vibro Anklet Directions]] with steps how to do this. So far it's an untested document but Ted intends to use these steps to try to make one himself.<br />
<br />
[[Category:Sensebridge]]</div>Elgreengeetohttps://www.noisebridge.net/index.php?title=Noisebridge&diff=5665Noisebridge2009-06-17T02:49:23Z<p>Elgreengeeto: </p>
<hr />
<div>__NOTOC__ __NOEDITSECTION__ [[Image:Noisebridge tools.jpg|thumb|right|A space to learn and create neat things]]<br />
[[Image:Noisebridge_Soldering_Workshop.jpg|thumb|right|Soldering workshop at Noisebridge]]<br />
[[Image:Skittlevodka.jpg|thumb|right|Hacking, it's more than just electronics]]<br />
[[Image:Noisebridge air.jpg|thumb|right|Members at Noisebridge]]<br />
[[Image:noisebridge.jpg|thumb|right|Front door to 83C]]<br />
[[Image:Starfive - q's noisebridge project.jpg|thumb|right|Craft hacking]]<br />
''Noisebridge is an infrastructure provider for technical-creative projects, collaboratively run by its members. We are incorporated as a non-profit educational corporation for public benefit.'' [[Noisebridge_Vision|Read more about Noisebridge...]]<br />
<br />
'''[[Mailinglist|Join the Noisebridge mailing list]] or hop on [[IRC]] to hear about upcoming events and to get involved.'''<br />
<br />
'''[[Noisebridge Membership|Become a member]]! -- [[New Member FAQ]]!'''<br />
<br />
'''[[Donate or Pay Dues| How to Donate money or Pay Membership Dues]].'''<br />
<br />
== [http://noisebridge.net/wiki/Category:Events Events] ==<br />
'''[http://www.google.com/calendar/embed?src=vo3i3c0qtjnkjr2ojasd0ftt8s%40group.calendar.google.com&ctz=America/Los_Angeles The unofficial Google calendar for Noisebridge]'''<br />
<br />
===Upcoming Planned Events===<br />
*'''Thursday 8pm june 18''' - [[Five Minutes of Fame]]<br />
* '''Tuesday June 30''' - [[Powerbocking Class|Powerbocking class]]<br />
<br />
=== Recurring Events ===<br />
* '''Monday'''<br />
**[[Circuit Hacking Mondays]] - Weekly workshop to solder stuff! Learn how to solder from some of the best out there.<br />
**[[PyClass]] - Learn how to program using the Python programming language.<br />
* '''Tuesday'''<br />
**[[Haskell/Haschool]] - The Haschool is a Haskell class, introducing the Haskell programming language.<br />
**[[#Meetings|Noisebridge Weekly Meeting]] - Happening every Tuesday at 8PM. Introducing new people to the space and general discussion.<br />
* '''Wednesday'''<br />
**[[Machine Learning]] - Weekly get-together about Machine Learning.<br />
**[[Adobe_Lightroom|Adobe Lightroom]] - Become a more organized photographer. Weekly class (mostly held off site).<br />
* '''Thursday'''<br />
**[[German]] - A weekly group to learn German for all levels.<br />
**[[Professional VFX Compositing With Adobe After Effects]] - Learn how to create photo realistic visual effects composites using After Effects. 7-10pm (skips the third Thursday of every month)<br />
** [[Five Minutes of Fame]] - Monthly set of lightning talks on diverse topics (third Thursday of each month)<br />
* '''Friday''' <br />
**[[Science, Engineering & Design Huddle]] - Weekly group to discuss design approach, share techniques, and solve any problem you may be having with your project(s). 7pm<br />
**[[Mandarin Corner]] - Weekly study group to practice Chinese language -- this class is on temporary hiatus until organizers such as yourself regroup and start it up!<br />
**[[CrazyCryptoCnight]] - Weekly night starting at 6pm for discussing cryptography. Novices and experts welcome alike!<br />
**[[Shop Class]] - Weekly class on safe and effective use of the tools in our little shop. Cover design and production and results in project after a month of sessions. Taught by John Magolske. 8pm<br />
* '''Sunday'''<br />
**[[Cyborg Group]] - 11AM (sorry) weekly gathering to work on projects like artificial senses (just go click the link)<br />
** [[Locks!]]<br />
== Info ==<br />
[[Getting Here]]: We're at 83C Wiese Street between Mission and Valencia just off 16th Street in San Francisco's Mission district. [http://openstreetmap.org/?mlat=37.765600&mlon=-122.420420&zoom=16 openstreetmap] [http://maps.google.com/?q=83C+Wiese+St,+94103 Google Maps]<br />
<br />
[[Planet Noisebridge]]: [https://www.noisebridge.net/planet/ Our blog aggregation service].<br />
<br />
[[The Space]]: Home sweet home (including our network drops [[Network]]).<br />
<br />
[[Noisebridge_Vision|Vision]]: Our vision - what our space is all about!<br />
<br />
[[Safety|Safety in the Space]]: What to do in case of an emergency.<br />
<br />
[[Infrastructure]]: Stuff we provide -- servers, bulk parts orders from Digikey/McMaster/Mouser, project spaces, specialized tools.<br />
<br />
[[Library]]: Information pertaining to projects we're working on.<br />
<br />
[[Concepts]]: A place to share your project ideas and to find like-minds.<br />
<br />
[[Donate or Pay Dues]]: Here is where you can see how easy it is to Donate to Noisebridge or to pay your monthly Membership Dues.<br />
<br />
[[Identity]]: Logos, stickers, t-shirts and stuff. <br />
<br />
[[Press Coverage]]: mentions of Noisebridge in the media (both blog and dead tree).<br />
<br />
[[Hackerspace Infos]]: Howtos, Background, and friendly Hackerspaces elsewhere.<br />
<br />
[[Board and Officers]]: Information about our formal organization.<br />
<br />
== Meetings ==<br />
'''Meetings every Tuesday at 8 PM US/Pacific at [[Getting Here|83 C Wiese St.]]''' This meeting is for members and non-members alike, everyone is welcome. Agenda items tend to typically include introductions, updates on projects happening in the space and upcoming events. Meetings normally end with general socializing and in depth discussion of any topics brought up earlier.<br />
* Prev: [[Meeting Notes 2009 06 09 | 2009-06-09]]<br />
* Next: [[Meeting Notes 2009 06 16 | 2009-06-16]]<br />
* ... (more in the [[:Category:Meeting Notes|Meeting Notes Archive]])<br />
<br />
== Get in Touch ==<br />
* [[IRC|IRC channel]] - irc://chat.freenode.net/#noisebridge <br />
* [[Mailinglist]] - Best way to keep informed of upcoming events<br />
* [[People]]<br />
* [https://www.facebook.com/group.php?gid=100998755576 Facebook group]<br />
* [[Twitter]]<br />
* [[MemoryHole|Legal Requests (information removal, etc)]]<br />
Or just [[Getting Here|drop by the space]]. We're here almost all the time, although evenings are best.<br />
<br />
== Status ==<br />
'''Noisebridge is up!''' We began building Noisebridge in Feb 2007. Since December 2007 we've had regular Tuesday meetings, and as of October 1st 2008, we have a physical space. We are currently awaiting our 501(c)(3) status.<br />
<br />
== Emergency ==<br />
<SPAN style="color: #ff0000; font-size: 18px;">[[Safety|In Case of Emergency]]</SPAN></div>Elgreengeetohttps://www.noisebridge.net/index.php?title=Noisebridge&diff=5664Noisebridge2009-06-17T02:49:09Z<p>Elgreengeeto: </p>
<hr />
<div>__NOTOC__ __NOEDITSECTION__ [[Image:Noisebridge tools.jpg|thumb|right|A space to learn and create neat things]]<br />
[[Image:Noisebridge_Soldering_Workshop.jpg|thumb|right|Soldering workshop at Noisebridge]]<br />
[[Image:Skittlevodka.jpg|thumb|right|Hacking, it's more than just electronics]]<br />
[[Image:Noisebridge air.jpg|thumb|right|Members at Noisebridge]]<br />
[[Image:noisebridge.jpg|thumb|right|Front door to 83C]]<br />
[[Image:Starfive - q's noisebridge project.jpg|thumb|right|Craft hacking]]<br />
''Noisebridge is an infrastructure provider for technical-creative projects, collaboratively run by its members. We are incorporated as a non-profit educational corporation for public benefit.'' [[Noisebridge_Vision|Read more about Noisebridge...]]<br />
<br />
'''[[Mailinglist|Join the Noisebridge mailing list]] or hop on [[IRC]] to hear about upcoming events and to get involved.'''<br />
<br />
'''[[Noisebridge Membership|Become a member]]! -- [[New Member FAQ]]!'''<br />
<br />
'''[[Donate or Pay Dues| How to Donate money or Pay Membership Dues]].'''<br />
<br />
== [http://noisebridge.net/wiki/Category:Events Events] ==<br />
'''[http://www.google.com/calendar/embed?src=vo3i3c0qtjnkjr2ojasd0ftt8s%40group.calendar.google.com&ctz=America/Los_Angeles The unofficial Google calendar for Noisebridge]'''<br />
<br />
===Upcoming Planned Events===<br />
*'''Monday 8pm june 15''' - [[AdvancedPy]]<br />
*'''Thursday 8pm june 18''' - [[Five Minutes of Fame]]<br />
* '''Tuesday June 30''' - [[Powerbocking Class|Powerbocking class]]<br />
<br />
=== Recurring Events ===<br />
* '''Monday'''<br />
**[[Circuit Hacking Mondays]] - Weekly workshop to solder stuff! Learn how to solder from some of the best out there.<br />
**[[PyClass]] - Learn how to program using the Python programming language.<br />
* '''Tuesday'''<br />
**[[Haskell/Haschool]] - The Haschool is a Haskell class, introducing the Haskell programming language.<br />
**[[#Meetings|Noisebridge Weekly Meeting]] - Happening every Tuesday at 8PM. Introducing new people to the space and general discussion.<br />
* '''Wednesday'''<br />
**[[Machine Learning]] - Weekly get-together about Machine Learning.<br />
**[[Adobe_Lightroom|Adobe Lightroom]] - Become a more organized photographer. Weekly class (mostly held off site).<br />
* '''Thursday'''<br />
**[[German]] - A weekly group to learn German for all levels.<br />
**[[Professional VFX Compositing With Adobe After Effects]] - Learn how to create photo realistic visual effects composites using After Effects. 7-10pm (skips the third Thursday of every month)<br />
** [[Five Minutes of Fame]] - Monthly set of lightning talks on diverse topics (third Thursday of each month)<br />
* '''Friday''' <br />
**[[Science, Engineering & Design Huddle]] - Weekly group to discuss design approach, share techniques, and solve any problem you may be having with your project(s). 7pm<br />
**[[Mandarin Corner]] - Weekly study group to practice Chinese language -- this class is on temporary hiatus until organizers such as yourself regroup and start it up!<br />
**[[CrazyCryptoCnight]] - Weekly night starting at 6pm for discussing cryptography. Novices and experts welcome alike!<br />
**[[Shop Class]] - Weekly class on safe and effective use of the tools in our little shop. Cover design and production and results in project after a month of sessions. Taught by John Magolske. 8pm<br />
* '''Sunday'''<br />
**[[Cyborg Group]] - 11AM (sorry) weekly gathering to work on projects like artificial senses (just go click the link)<br />
** [[Locks!]]<br />
== Info ==<br />
[[Getting Here]]: We're at 83C Wiese Street between Mission and Valencia just off 16th Street in San Francisco's Mission district. [http://openstreetmap.org/?mlat=37.765600&mlon=-122.420420&zoom=16 openstreetmap] [http://maps.google.com/?q=83C+Wiese+St,+94103 Google Maps]<br />
<br />
[[Planet Noisebridge]]: [https://www.noisebridge.net/planet/ Our blog aggregation service].<br />
<br />
[[The Space]]: Home sweet home (including our network drops [[Network]]).<br />
<br />
[[Noisebridge_Vision|Vision]]: Our vision - what our space is all about!<br />
<br />
[[Safety|Safety in the Space]]: What to do in case of an emergency.<br />
<br />
[[Infrastructure]]: Stuff we provide -- servers, bulk parts orders from Digikey/McMaster/Mouser, project spaces, specialized tools.<br />
<br />
[[Library]]: Information pertaining to projects we're working on.<br />
<br />
[[Concepts]]: A place to share your project ideas and to find like-minds.<br />
<br />
[[Donate or Pay Dues]]: Here is where you can see how easy it is to Donate to Noisebridge or to pay your monthly Membership Dues.<br />
<br />
[[Identity]]: Logos, stickers, t-shirts and stuff. <br />
<br />
[[Press Coverage]]: mentions of Noisebridge in the media (both blog and dead tree).<br />
<br />
[[Hackerspace Infos]]: Howtos, Background, and friendly Hackerspaces elsewhere.<br />
<br />
[[Board and Officers]]: Information about our formal organization.<br />
<br />
== Meetings ==<br />
'''Meetings every Tuesday at 8 PM US/Pacific at [[Getting Here|83 C Wiese St.]]''' This meeting is for members and non-members alike, everyone is welcome. Agenda items tend to typically include introductions, updates on projects happening in the space and upcoming events. Meetings normally end with general socializing and in depth discussion of any topics brought up earlier.<br />
* Prev: [[Meeting Notes 2009 06 09 | 2009-06-09]]<br />
* Next: [[Meeting Notes 2009 06 16 | 2009-06-16]]<br />
* ... (more in the [[:Category:Meeting Notes|Meeting Notes Archive]])<br />
<br />
== Get in Touch ==<br />
* [[IRC|IRC channel]] - irc://chat.freenode.net/#noisebridge <br />
* [[Mailinglist]] - Best way to keep informed of upcoming events<br />
* [[People]]<br />
* [https://www.facebook.com/group.php?gid=100998755576 Facebook group]<br />
* [[Twitter]]<br />
* [[MemoryHole|Legal Requests (information removal, etc)]]<br />
Or just [[Getting Here|drop by the space]]. We're here almost all the time, although evenings are best.<br />
<br />
== Status ==<br />
'''Noisebridge is up!''' We began building Noisebridge in Feb 2007. Since December 2007 we've had regular Tuesday meetings, and as of October 1st 2008, we have a physical space. We are currently awaiting our 501(c)(3) status.<br />
<br />
== Emergency ==<br />
<SPAN style="color: #ff0000; font-size: 18px;">[[Safety|In Case of Emergency]]</SPAN></div>Elgreengeetohttps://www.noisebridge.net/index.php?title=EagleCAD_workshop&diff=5631EagleCAD workshop2009-06-16T02:02:06Z<p>Elgreengeeto: </p>
<hr />
<div>'''[http://www.instructables.com/id/How-to-make-a-custom-library-part-in-Eagle-CAD-too/ TONIGHT'S TUTORIAL LINK CLICK HERE NOW]'''!!1!OMG!1!<br />
<br />
===EagleCAD===<br />
<br />
EagleCAD is a computer-aided tool for schematic capture and designing printed circuit boards<br />
that runs on Macs, Linux, and Windows. There is a free (as in beer) version available here:<br />
<br />
http://www.cadsoftusa.com/freeware.htm<br />
<br />
The free version is slightly crippled in terms of the size of the board you can design but is perfectly fine for most hobbyist use. <br />
<br />
===Next scheduled workshop===<br />
<br />
Following a very successful and popular Eagle CAD workshop back in April, we'll be having another one on Monday, June 15 at 7:00 pm.<br />
<br />
====Potential Topics====<br />
<br />
The following will be way too much for one and a half hours. Feel free to add topics, then let's use the [[Talk:EagleCAD_workshop|talk page]] to vote for what we want most to cover.<br />
<br />
*Review of last time<br />
**What is EAGLE, 15 minute refresher on making a schematic and laying out a board.<br />
*Expanding into new topics<br />
**Making custom devices and libraries<br />
***How to make the pin outs and footprints from a data sheet, possibly recycling someone else's similar part.<br />
***How to label the part correctly and control what layers show on the board view (this can be confusing!)<br />
**Autorouting design rules<br />
**Error checking<br />
** How to fab a board.<br />
***Exporting gerber and drill files using a CAM processor<br />
***Checking the gerber files in a non-Eagle viewer program<br />
***Uploading to fab houses<br />
** Panelizing (step-and-repeat copying) designs using [http://claymore.engineer.gvsu.edu/~steriana/Python/gerbmerge/ gerbmerge] (one way around EagleCad board size limitation)<br />
** More advanced tricks like logo images in the silkscreen layer<br />
<br />
<br />
<br />
===Tutorials===<br />
[http://online.sfsu.edu/~larryk/engr301/Waveform%20Generator/How%20to%20Make%20Circuit%20Boards.pdf Larry Klingenberg's Double Sided Board Tutorial]<br />
<br />
More info, tutorials, etc. from the SWARM wiki: http://wiki.orbswarm.com/index.php?title=The_PC_Board_Page<br />
<br />
===List of EagleCAD "gotchas"===<br />
<br />
I promised I would post my list of "gotchas;" hope this helps avoid some irritation! [[User:Jtfoote|Jtfoote]] 23:38, 27 April 2009 (PDT)<br />
<br />
# IF BOARD AND SCHEMATIC GET OUT OF SYNC, YOU ARE SCREWED. This can happen if updates on the schematic don't make it to the board. To avoid this, always keep board file open when editing schematic, and vice versa! Use "rip up" instead of "delete" on the board. DRC will tell you when you are not in sync, otherwise you won't know. Use it often, and save often.<br />
# Don't click on "Drop" button when adding a component. Hit "cancel." "Drop" "drops" the library (!)<br />
# tOrigin layers must be visible to move/rotate components.<br />
# Overlapping wires sometimes don't logically connect. Add junction (green dot) if a problem. Check by moving component and seeing if wire moves with it. <br />
# "Cut" (scissor icon) is really "copy to paste buffer" and only works on groups! Use "copy" for single items. In V5, use shift-right-click or menu item to copy/move groups. <br />
# Pay attention to messages in the status bar, they are often helpful. For example when trying to select things on top of each other, clicking will cycle through each and the status bar will tell you how to select the one you want.<br />
<br />
===Checking Gerber file output===<br />
<br />
You will want to check that things look OK. Use a gerber file viewer<br />
like ViewMate (reg req) <br />
http://www.pentalogix.com/Download/download.html#item8<br />
<br />
or GerbView (free, open source, a little buggy)<br />
http://sourceforge.net/projects/gerbv/<br />
<br />
<br />
===PCB Fab Houses===<br />
<br />
Where to get your printed circuit boards fabricated after you've designed them<br />
<br />
Lady Ada has a PCB cost calculator with most sources: http://www.ladyada.net/library/pcb/costcalc.html<br />
<br />
The following is a biased list from [[User:Jtfoote|Jtfoote]] 09:36, 5 May 2009 (PDT)<br />
<br />
* [http://www.goldphoenixpcb.biz/ Gold Phoenix]: cheapest, longer turn-around (sent from China), fine quality, no charge for "panelization," can submit multiple boards for one run. SparkFun uses them; so could we, if we want to combine orders. They don't have web upload; you email your gerbers to some dude, but it worked great for me. <br />
* [http://www.protoexpress.com Sierra Proto Express]: I found this best combination of price/turn around time for small orders and prototypes, and they're local (Sunnyvale). Silkscreen was a little smeary if that bugs you; still perfectly readable.<br />
* Advanced Circuits 4pcb.com (same as 33each.com and others) Good quality, slick marketing, more expensive than they seem (not-well-advertised setup charges and minimums). Avoid for small runs, but definitely use their free gerber file check site: http://www.freedfm.com/<br />
* Windell at EMSL recommends ourpcb and his boards always look great. Haven't personally tried. <br />
<br />
One reponse to [[User:Elgreengeeto|Skory]]'s list email said:<br />
<br />
<quote><br />
I have had good luck with both Sunstone Circuits (http://www.sunstone.com/) and Advanced Circuits (http://www.4pcb.com/). My order sizes have been 2, 100, and 350 boards.<br />
</quote></div>Elgreengeetohttps://www.noisebridge.net/index.php?title=EagleCAD_workshop&diff=5524EagleCAD workshop2009-06-11T17:17:40Z<p>Elgreengeeto: merged this and older "Eagle workshop" pages</p>
<hr />
<div>===EagleCAD===<br />
<br />
EagleCAD is a computer-aided tool for schematic capture and designing printed circuit boards<br />
that runs on Macs, Linux, and Windows. There is a free (as in beer) version available here:<br />
<br />
http://www.cadsoftusa.com/freeware.htm<br />
<br />
The free version is slightly crippled in terms of the size of the board you can design but is perfectly fine for most hobbyist use. <br />
<br />
===Next scheduled workshop===<br />
<br />
Following a very successful and popular Eagle CAD workshop back in April, we'll be having another one on Monday, June 15 at 7:00 pm.<br />
<br />
====Potential Topics====<br />
<br />
The following will be way too much for one and a half hours. Feel free to add topics, then let's use the [[Talk:EagleCAD_workshop|talk page]] to vote for what we want most to cover.<br />
<br />
*Review of last time<br />
**What is EAGLE, 15 minute refresher on making a schematic and laying out a board.<br />
*Expanding into new topics<br />
**Making custom devices and libraries<br />
***How to make the pin outs and footprints from a data sheet, possibly recycling someone else's similar part.<br />
***How to label the part correctly and control what layers show on the board view (this can be confusing!)<br />
**Autorouting design rules<br />
**Error checking<br />
** How to fab a board.<br />
***Exporting gerber and drill files using a CAM processor<br />
***Checking the gerber files in a non-Eagle viewer program<br />
***Uploading to fab houses<br />
** Panelizing (step-and-repeat copying) designs using [http://claymore.engineer.gvsu.edu/~steriana/Python/gerbmerge/ gerbmerge] (one way around EagleCad board size limitation)<br />
** More advanced tricks like logo images in the silkscreen layer<br />
<br />
<br />
<br />
===Tutorials===<br />
[http://online.sfsu.edu/~larryk/engr301/Waveform%20Generator/How%20to%20Make%20Circuit%20Boards.pdf Larry Klingenberg's Double Sided Board Tutorial]<br />
<br />
More info, tutorials, etc. from the SWARM wiki: http://wiki.orbswarm.com/index.php?title=The_PC_Board_Page<br />
<br />
===List of EagleCAD "gotchas"===<br />
<br />
I promised I would post my list of "gotchas;" hope this helps avoid some irritation! [[User:Jtfoote|Jtfoote]] 23:38, 27 April 2009 (PDT)<br />
<br />
# IF BOARD AND SCHEMATIC GET OUT OF SYNC, YOU ARE SCREWED. This can happen if updates on the schematic don't make it to the board. To avoid this, always keep board file open when editing schematic, and vice versa! Use "rip up" instead of "delete" on the board. DRC will tell you when you are not in sync, otherwise you won't know. Use it often, and save often.<br />
# Don't click on "Drop" button when adding a component. Hit "cancel." "Drop" "drops" the library (!)<br />
# tOrigin layers must be visible to move/rotate components.<br />
# Overlapping wires sometimes don't logically connect. Add junction (green dot) if a problem. Check by moving component and seeing if wire moves with it. <br />
# "Cut" (scissor icon) is really "copy to paste buffer" and only works on groups! Use "copy" for single items. In V5, use shift-right-click or menu item to copy/move groups. <br />
# Pay attention to messages in the status bar, they are often helpful. For example when trying to select things on top of each other, clicking will cycle through each and the status bar will tell you how to select the one you want.<br />
<br />
===Checking Gerber file output===<br />
<br />
You will want to check that things look OK. Use a gerber file viewer<br />
like ViewMate (reg req) <br />
http://www.pentalogix.com/Download/download.html#item8<br />
<br />
or GerbView (free, open source, a little buggy)<br />
http://sourceforge.net/projects/gerbv/<br />
<br />
<br />
===PCB Fab Houses===<br />
<br />
Where to get your printed circuit boards fabricated after you've designed them<br />
<br />
Lady Ada has a PCB cost calculator with most sources: http://www.ladyada.net/library/pcb/costcalc.html<br />
<br />
The following is a biased list from [[User:Jtfoote|Jtfoote]] 09:36, 5 May 2009 (PDT)<br />
<br />
* [http://www.goldphoenixpcb.biz/ Gold Phoenix]: cheapest, longer turn-around (sent from China), fine quality, no charge for "panelization," can submit multiple boards for one run. SparkFun uses them; so could we, if we want to combine orders. They don't have web upload; you email your gerbers to some dude, but it worked great for me. <br />
* [http://www.protoexpress.com Sierra Proto Express]: I found this best combination of price/turn around time for small orders and prototypes, and they're local (Sunnyvale). Silkscreen was a little smeary if that bugs you; still perfectly readable.<br />
* Advanced Circuits 4pcb.com (same as 33each.com and others) Good quality, slick marketing, more expensive than they seem (not-well-advertised setup charges and minimums). Avoid for small runs, but definitely use their free gerber file check site: http://www.freedfm.com/<br />
* Windell at EMSL recommends ourpcb and his boards always look great. Haven't personally tried. <br />
<br />
One reponse to [[User:Elgreengeeto|Skory]]'s list email said:<br />
<br />
<quote><br />
I have had good luck with both Sunstone Circuits (http://www.sunstone.com/) and Advanced Circuits (http://www.4pcb.com/). My order sizes have been 2, 100, and 350 boards.<br />
</quote></div>Elgreengeetohttps://www.noisebridge.net/index.php?title=Eagle_Workshop&diff=5523Eagle Workshop2009-06-11T17:09:55Z<p>Elgreengeeto: Redirecting to EagleCAD workshop</p>
<hr />
<div>#REDIRECT [[EagleCAD workshop]]</div>Elgreengeetohttps://www.noisebridge.net/index.php?title=Noisebridge&diff=5520Noisebridge2009-06-11T08:05:08Z<p>Elgreengeeto: </p>
<hr />
<div>__NOTOC__ __NOEDITSECTION__ [[Image:Noisebridge tools.jpg|thumb|right|A space to learn and create neat things]]<br />
[[Image:Noisebridge_Soldering_Workshop.jpg|thumb|right|Soldering workshop at Noisebridge]]<br />
[[Image:Skittlevodka.jpg|thumb|right|Hacking, it's more than just electronics]]<br />
[[Image:Noisebridge air.jpg|thumb|right|Members at Noisebridge]]<br />
[[Image:noisebridge.jpg|thumb|right|Front door to 83C]]<br />
[[Image:Starfive - q's noisebridge project.jpg|thumb|right|Craft hacking]]<br />
''Noisebridge is an infrastructure provider for technical-creative projects, collaboratively run by its members. We are incorporated as a non-profit educational corporation for public benefit.'' [[Noisebridge_Vision|Read more about Noisebridge...]]<br />
<br />
'''[[Mailinglist|Join the Noisebridge mailing list]] or hop on [[IRC]] to hear about upcoming events and to get involved.'''<br />
<br />
'''[[Noisebridge Membership|Become a member]]! -- [[New Member FAQ]]!'''<br />
<br />
'''[[Donate or Pay Dues| How to Donate money or Pay Membership Dues]].'''<br />
<br />
== [http://noisebridge.net/wiki/Category:Events Events] ==<br />
===Upcoming Planned Events===<br />
*'''Saturday and Sunday June 13 and 14''' - [[RoboGames 2009]]<br />
*'''Monday 7pm june 15''' - [[Eagle Workshop]], session number 2<br />
*'''Monday 8pm june 15''' - [[AdvancedPy]]<br />
* '''Tuesday June 30''' - [[Powerbocking Class|Powerbocking class]]<br />
<br />
[http://www.google.com/calendar/embed?src=vo3i3c0qtjnkjr2ojasd0ftt8s%40group.calendar.google.com&ctz=America/Los_Angeles The unofficial Google calendar for Noisebridge]<br />
<br />
==== Recurring Events ====<br />
* '''Monday'''<br />
**[[Circuit Hacking Mondays]] - Weekly workshop to solder stuff! Learn how to solder from some of the best out there.<br />
**PyClass - Learn how to program using the Python programming language.<br />
* '''Tuesday'''<br />
**[[Haskell/Haschool]] - The Haschool is a Haskell class, introducing the Haskell programming language.<br />
**[[#Meetings|Noisebridge Weekly Meeting]] - Happening every Tuesday at 8PM. Introducing new people to the space and general discussion.<br />
* '''Wednesday''' [[Machine Learning]] - Weekly get-together about Machine Learning.<br />
* '''Thursday'''<br />
**[[German]] - A weekly group to learn German for all levels.<br />
**[[Professional VFX Compositing With Adobe After Effects]] - Learn how to create photo realistic visual effects composites using After Effects. 7-10pm (skips the third Thursday of every month)<br />
** [[Five Minutes of Fame]] - Monthly set of lightning talks on diverse topics (third Thursday of each month)<br />
* '''Friday''' <br />
**[[Science, Engineering & Design Huddle]] - Weekly group to discuss design approach, share techniques, and solve any problem you may be having with your project(s). 7pm<br />
**[[Mandarin Corner]] - Weekly study group to practice Chinese language -- this class is on temporary hiatus until organizers such as yourself regroup and start it up!<br />
**[[CrazyCryptoCnight]] - Weekly night starting at 6pm for discussing cryptography. Novices and experts welcome alike!<br />
* '''Sunday''' [[Cyborg Group]] - 11AM (sorry) weekly gathering to work on projects like artificial senses (just go click the link)<br />
<br />
== Info ==<br />
[[Getting Here]]: We're at 83C Wiese Street between Mission and Valencia just off 16th Street in San Francisco's Mission district. [http://openstreetmap.org/?mlat=37.765600&mlon=-122.420420&zoom=16 openstreetmap] [http://maps.google.com/?q=83C+Wiese+St,+94103 Google Maps]<br />
<br />
[[Planet Noisebridge]]: [https://www.noisebridge.net/planet/ Our blog aggregation service].<br />
<br />
[[The Space]]: Home sweet home (including our network drops [[Network]]).<br />
<br />
[[Noisebridge_Vision|Vision]]: Our vision - what our space is all about!<br />
<br />
[[Safety|Safety in the Space]]: What to do in case of an emergency.<br />
<br />
[[Infrastructure]]: Stuff we provide -- servers, bulk parts orders from Digikey/McMaster/Mouser, project spaces, specialized tools.<br />
<br />
[[Library]]: Information pertaining to projects we're working on.<br />
<br />
[[Concepts]]: A place to share your project ideas and to find like-minds.<br />
<br />
[[Donate or Pay Dues]]: Here is where you can see how easy it is to Donate to Noisebridge or to pay your monthly Membership Dues.<br />
<br />
[[Identity]]: Logos, stickers, t-shirts and stuff. <br />
<br />
[[Press Coverage]]: mentions of Noisebridge in the media (both blog and dead tree).<br />
<br />
[[Hackerspace Infos]]: Howtos, Background, and friendly Hackerspaces elsewhere.<br />
<br />
[[Board and Officers]]: Information about our formal organization.<br />
<br />
== Meetings ==<br />
'''Meetings every Tuesday at 8 PM US/Pacific at [[Getting Here|83 C Wiese St.]]''' This meeting is for members and non-members alike, everyone is welcome. Agenda items tend to typically include introductions, updates on projects happening in the space and upcoming events. Meetings normally end with general socializing and in depth discussion of any topics brought up earlier.<br />
* Prev: [[Meeting Notes 2009 06 09 | 2009-06-09]]<br />
* Next: [[Meeting Notes 2009 06 16 | 2009-06-16]]<br />
* ... (more in the [[:Category:Meeting Notes|Meeting Notes Archive]])<br />
<br />
== Get in Touch ==<br />
* [[IRC|IRC channel]] - irc://chat.freenode.net/#noisebridge <br />
* [[Mailinglist]] - Best way to keep informed of upcoming events<br />
* [[People]]<br />
* [https://www.facebook.com/group.php?gid=100998755576 Facebook group]<br />
* [[Twitter]]<br />
* [[MemoryHole|Legal Requests (information removal, etc)]]<br />
Or just [[Getting Here|drop by the space]]. We're here almost all the time, although evenings are best.<br />
<br />
== Status ==<br />
'''Noisebridge is up!''' We began building Noisebridge in Feb 2007. Since December 2007 we've had regular Tuesday meetings, and as of October 1st 2008, we have a physical space. We are currently awaiting our 501(c)(3) status.<br />
<br />
== Emergency ==<br />
<SPAN style="color: #ff0000; font-size: 18px;">[[Safety|In Case of Emergency]]</SPAN></div>Elgreengeetohttps://www.noisebridge.net/index.php?title=Noisebridge&diff=5519Noisebridge2009-06-11T08:03:41Z<p>Elgreengeeto: </p>
<hr />
<div>__NOTOC__ __NOEDITSECTION__ [[Image:Noisebridge tools.jpg|thumb|right|A space to learn and create neat things]]<br />
[[Image:Noisebridge_Soldering_Workshop.jpg|thumb|right|Soldering workshop at Noisebridge]]<br />
[[Image:Skittlevodka.jpg|thumb|right|Hacking, it's more than just electronics]]<br />
[[Image:Noisebridge air.jpg|thumb|right|Members at Noisebridge]]<br />
[[Image:noisebridge.jpg|thumb|right|Front door to 83C]]<br />
[[Image:Starfive - q's noisebridge project.jpg|thumb|right|Craft hacking]]<br />
''Noisebridge is an infrastructure provider for technical-creative projects, collaboratively run by its members. We are incorporated as a non-profit educational corporation for public benefit.'' [[Noisebridge_Vision|Read more about Noisebridge...]]<br />
<br />
'''[[Mailinglist|Join the Noisebridge mailing list]] or hop on [[IRC]] to hear about upcoming events and to get involved.'''<br />
<br />
'''[[Noisebridge Membership|Become a member]]! -- [[New Member FAQ]]!'''<br />
<br />
'''[[Donate or Pay Dues| How to Donate money or Pay Membership Dues]].'''<br />
<br />
== [http://noisebridge.net/wiki/Category:Events Events] ==<br />
===Upcoming Planned Events===<br />
*'''Saturday and Sunday June 13 and 14''' - [[RoboGames 2009]]<br />
*'''Monday 7pm june 15''' - [[Eagle Workshop]], session number 2<br />
*'''Monday 8pm june 15''' - [[AdvancedPy]]<br />
* '''Tuesday June 30''' - [[Powerbocking Class|Powerbocking class]]<br />
* [http://www.google.com/calendar/embed?src=vo3i3c0qtjnkjr2ojasd0ftt8s%40group.calendar.google.com&ctz=America/Los_Angeles The unofficial Google calendar for Noisebridge]<br />
<br />
==== Recurring Events ====<br />
* '''Monday'''<br />
**[[Circuit Hacking Mondays]] - Weekly workshop to solder stuff! Learn how to solder from some of the best out there.<br />
**PyClass - Learn how to program using the Python programming language.<br />
* '''Tuesday'''<br />
**[[Haskell/Haschool]] - The Haschool is a Haskell class, introducing the Haskell programming language.<br />
**[[#Meetings|Noisebridge Weekly Meeting]] - Happening every Tuesday at 8PM. Introducing new people to the space and general discussion.<br />
* '''Wednesday''' [[Machine Learning]] - Weekly get-together about Machine Learning.<br />
* '''Thursday'''<br />
**[[German]] - A weekly group to learn German for all levels.<br />
**[[Professional VFX Compositing With Adobe After Effects]] - Learn how to create photo realistic visual effects composites using After Effects. 7-10pm (skips the third Thursday of every month)<br />
** [[Five Minutes of Fame]] - Monthly set of lightning talks on diverse topics (third Thursday of each month)<br />
* '''Friday''' <br />
**[[Science, Engineering & Design Huddle]] - Weekly group to discuss design approach, share techniques, and solve any problem you may be having with your project(s). 7pm<br />
**[[Mandarin Corner]] - Weekly study group to practice Chinese language -- this class is on temporary hiatus until organizers such as yourself regroup and start it up!<br />
**[[CrazyCryptoCnight]] - Weekly night starting at 6pm for discussing cryptography. Novices and experts welcome alike!<br />
* '''Sunday''' [[Cyborg Group]] - 11AM (sorry) weekly gathering to work on projects like artificial senses (just go click the link)<br />
<br />
== Info ==<br />
[[Getting Here]]: We're at 83C Wiese Street between Mission and Valencia just off 16th Street in San Francisco's Mission district. [http://openstreetmap.org/?mlat=37.765600&mlon=-122.420420&zoom=16 openstreetmap] [http://maps.google.com/?q=83C+Wiese+St,+94103 Google Maps]<br />
<br />
[[Planet Noisebridge]]: [https://www.noisebridge.net/planet/ Our blog aggregation service].<br />
<br />
[[The Space]]: Home sweet home (including our network drops [[Network]]).<br />
<br />
[[Noisebridge_Vision|Vision]]: Our vision - what our space is all about!<br />
<br />
[[Safety|Safety in the Space]]: What to do in case of an emergency.<br />
<br />
[[Infrastructure]]: Stuff we provide -- servers, bulk parts orders from Digikey/McMaster/Mouser, project spaces, specialized tools.<br />
<br />
[[Library]]: Information pertaining to projects we're working on.<br />
<br />
[[Concepts]]: A place to share your project ideas and to find like-minds.<br />
<br />
[[Donate or Pay Dues]]: Here is where you can see how easy it is to Donate to Noisebridge or to pay your monthly Membership Dues.<br />
<br />
[[Identity]]: Logos, stickers, t-shirts and stuff. <br />
<br />
[[Press Coverage]]: mentions of Noisebridge in the media (both blog and dead tree).<br />
<br />
[[Hackerspace Infos]]: Howtos, Background, and friendly Hackerspaces elsewhere.<br />
<br />
[[Board and Officers]]: Information about our formal organization.<br />
<br />
== Meetings ==<br />
'''Meetings every Tuesday at 8 PM US/Pacific at [[Getting Here|83 C Wiese St.]]''' This meeting is for members and non-members alike, everyone is welcome. Agenda items tend to typically include introductions, updates on projects happening in the space and upcoming events. Meetings normally end with general socializing and in depth discussion of any topics brought up earlier.<br />
* Next: [[Meeting Notes 2009 06 09 | 2009-06-09]]<br />
* Prev: [[Meeting Notes 2009 06 02 | 2009-06-02]]<br />
* ... (more in the [[:Category:Meeting Notes|Meeting Notes Archive]])<br />
<br />
== Get in Touch ==<br />
* [[IRC|IRC channel]] - irc://chat.freenode.net/#noisebridge <br />
* [[Mailinglist]] - Best way to keep informed of upcoming events<br />
* [[People]]<br />
* [https://www.facebook.com/group.php?gid=100998755576 Facebook group]<br />
* [[Twitter]]<br />
* [[MemoryHole|Legal Requests (information removal, etc)]]<br />
Or just [[Getting Here|drop by the space]]. We're here almost all the time, although evenings are best.<br />
<br />
== Status ==<br />
'''Noisebridge is up!''' We began building Noisebridge in Feb 2007. Since December 2007 we've had regular Tuesday meetings, and as of October 1st 2008, we have a physical space. We are currently awaiting our 501(c)(3) status.<br />
<br />
== Emergency ==<br />
<SPAN style="color: #ff0000; font-size: 18px;">[[Safety|In Case of Emergency]]</SPAN></div>Elgreengeetohttps://www.noisebridge.net/index.php?title=Noisebridge&diff=5518Noisebridge2009-06-11T07:59:59Z<p>Elgreengeeto: </p>
<hr />
<div>__NOTOC__ __NOEDITSECTION__ [[Image:Noisebridge tools.jpg|thumb|right|A space to learn and create neat things]]<br />
[[Image:Noisebridge_Soldering_Workshop.jpg|thumb|right|Soldering workshop at Noisebridge]]<br />
[[Image:Skittlevodka.jpg|thumb|right|Hacking, it's more than just electronics]]<br />
[[Image:Noisebridge air.jpg|thumb|right|Members at Noisebridge]]<br />
[[Image:noisebridge.jpg|thumb|right|Front door to 83C]]<br />
[[Image:Starfive - q's noisebridge project.jpg|thumb|right|Craft hacking]]<br />
''Noisebridge is an infrastructure provider for technical-creative projects, collaboratively run by its members. We are incorporated as a non-profit educational corporation for public benefit.'' [[Noisebridge_Vision|Read more about Noisebridge...]]<br />
<br />
'''[[Mailinglist|Join the Noisebridge mailing list]] or hop on [[IRC]] to hear about upcoming events and to get involved.'''<br />
<br />
'''[[Noisebridge Membership|Become a member]]! -- [[New Member FAQ]]!'''<br />
<br />
'''[[Donate or Pay Dues| How to Donate money or Pay Membership Dues]].'''<br />
<br />
== [http://noisebridge.net/wiki/Category:Events Events] ==<br />
===Upcoming Planned Events===<br />
*'''Monday 7pm june 15''' - [[Eagle workshop]], session number 2<br />
*'''Monday 8pm june 15''' - [[AdvancedPy]]<br />
*'''Saturday and Sunday June 13 and 14''' - [[RoboGames 2009]]<br />
* '''Tuesday June 30''' - [[Powerbocking Class|Powerbocking class]]<br />
* [http://www.google.com/calendar/embed?src=vo3i3c0qtjnkjr2ojasd0ftt8s%40group.calendar.google.com&ctz=America/Los_Angeles The unofficial Google calendar for Noisebridge]<br />
<br />
==== Recurring Events ====<br />
* '''Monday'''<br />
**[[Circuit Hacking Mondays]] - Weekly workshop to solder stuff! Learn how to solder from some of the best out there.<br />
**PyClass - Learn how to program using the Python programming language.<br />
* '''Tuesday'''<br />
**[[Haskell/Haschool]] - The Haschool is a Haskell class, introducing the Haskell programming language.<br />
**[[#Meetings|Noisebridge Weekly Meeting]] - Happening every Tuesday at 8PM. Introducing new people to the space and general discussion.<br />
* '''Wednesday''' [[Machine Learning]] - Weekly get-together about Machine Learning.<br />
* '''Thursday'''<br />
**[[German]] - A weekly group to learn German for all levels.<br />
**[[Professional VFX Compositing With Adobe After Effects]] - Learn how to create photo realistic visual effects composites using After Effects. 7-10pm (skips the third Thursday of every month)<br />
** [[Five Minutes of Fame]] - Monthly set of lightning talks on diverse topics (third Thursday of each month)<br />
* '''Friday''' <br />
**[[Science, Engineering & Design Huddle]] - Weekly group to discuss design approach, share techniques, and solve any problem you may be having with your project(s). 7pm<br />
**[[Mandarin Corner]] - Weekly study group to practice Chinese language -- this class is on temporary hiatus until organizers such as yourself regroup and start it up!<br />
**[[CrazyCryptoCnight]] - Weekly night starting at 6pm for discussing cryptography. Novices and experts welcome alike!<br />
* '''Sunday''' [[Cyborg Group]] - 11AM (sorry) weekly gathering to work on projects like artificial senses (just go click the link)<br />
<br />
== Info ==<br />
[[Getting Here]]: We're at 83C Wiese Street between Mission and Valencia just off 16th Street in San Francisco's Mission district. [http://openstreetmap.org/?mlat=37.765600&mlon=-122.420420&zoom=16 openstreetmap] [http://maps.google.com/?q=83C+Wiese+St,+94103 Google Maps]<br />
<br />
[[Planet Noisebridge]]: [https://www.noisebridge.net/planet/ Our blog aggregation service].<br />
<br />
[[The Space]]: Home sweet home (including our network drops [[Network]]).<br />
<br />
[[Noisebridge_Vision|Vision]]: Our vision - what our space is all about!<br />
<br />
[[Safety|Safety in the Space]]: What to do in case of an emergency.<br />
<br />
[[Infrastructure]]: Stuff we provide -- servers, bulk parts orders from Digikey/McMaster/Mouser, project spaces, specialized tools.<br />
<br />
[[Library]]: Information pertaining to projects we're working on.<br />
<br />
[[Concepts]]: A place to share your project ideas and to find like-minds.<br />
<br />
[[Donate or Pay Dues]]: Here is where you can see how easy it is to Donate to Noisebridge or to pay your monthly Membership Dues.<br />
<br />
[[Identity]]: Logos, stickers, t-shirts and stuff. <br />
<br />
[[Press Coverage]]: mentions of Noisebridge in the media (both blog and dead tree).<br />
<br />
[[Hackerspace Infos]]: Howtos, Background, and friendly Hackerspaces elsewhere.<br />
<br />
[[Board and Officers]]: Information about our formal organization.<br />
<br />
== Meetings ==<br />
'''Meetings every Tuesday at 8 PM US/Pacific at [[Getting Here|83 C Wiese St.]]''' This meeting is for members and non-members alike, everyone is welcome. Agenda items tend to typically include introductions, updates on projects happening in the space and upcoming events. Meetings normally end with general socializing and in depth discussion of any topics brought up earlier.<br />
* Next: [[Meeting Notes 2009 06 09 | 2009-06-09]]<br />
* Prev: [[Meeting Notes 2009 06 02 | 2009-06-02]]<br />
* ... (more in the [[:Category:Meeting Notes|Meeting Notes Archive]])<br />
<br />
== Get in Touch ==<br />
* [[IRC|IRC channel]] - irc://chat.freenode.net/#noisebridge <br />
* [[Mailinglist]] - Best way to keep informed of upcoming events<br />
* [[People]]<br />
* [https://www.facebook.com/group.php?gid=100998755576 Facebook group]<br />
* [[Twitter]]<br />
* [[MemoryHole|Legal Requests (information removal, etc)]]<br />
Or just [[Getting Here|drop by the space]]. We're here almost all the time, although evenings are best.<br />
<br />
== Status ==<br />
'''Noisebridge is up!''' We began building Noisebridge in Feb 2007. Since December 2007 we've had regular Tuesday meetings, and as of October 1st 2008, we have a physical space. We are currently awaiting our 501(c)(3) status.<br />
<br />
== Emergency ==<br />
<SPAN style="color: #ff0000; font-size: 18px;">[[Safety|In Case of Emergency]]</SPAN></div>Elgreengeetohttps://www.noisebridge.net/index.php?title=Category:Events&diff=5517Category:Events2009-06-11T07:59:04Z<p>Elgreengeeto: /* Upcoming Events */</p>
<hr />
<div>Official, Semi-Official, one-off and other events at the NoiseBridge space.<br />
<br />
=Event Calendar=<br />
All Noisebridge event datum are belong to gCal. View it [http://www.google.com/calendar/embed?src=vo3i3c0qtjnkjr2ojasd0ftt8s%40group.calendar.google.com&ctz=America/Los_Angeles here] or grab it in [http://www.google.com/calendar/feeds/vo3i3c0qtjnkjr2ojasd0ftt8s%40group.calendar.google.com/public/basic xml] and [http://www.google.com/calendar/ical/vo3i3c0qtjnkjr2ojasd0ftt8s%40group.calendar.google.com/public/basic.ics ical] formats. (If any wiki admins want to add a gCal mediawiki plugin so we can embed here, please go for it.)<br />
<br />
Also, not all events get on this page or the calendar. Most events are announced on the mailing list and or at the Tuesday meetings. Some events just happen. Pay attention!<br />
<br />
= Upcoming Events =<br />
:'''Saturday and Sunday June 13 and 14''' [[RoboGames 2009]]: Noisebridge will have a booth here and will need volunteers. It should be great fun!<br />
:'''Monday June 15 at 7pm''' [[Eagle Workshop]] Session two of the Eagle CAD workshop.<br />
<br />
= Recurring Events =<br />
:'''Monday''': [[Pyclass]] - Learn to how to write computer programs using Python! 6:30pm till 8pm<br />
:'''Monday''': [[Circuit Hacking Mondays]] - Weekly get-together to solder stuff! 8:30pm till ?? Learn to solder! Mitch will bring kits to make cool, hackable things that you can bring home after you make it. Of course, you can also bring your own projects to hack.<br />
:'''Tuesday''': [[Category:Meeting Notes]] - our weekly 8pm meeting generally gets 10-30 people; we try to keep the formal part under 1 hour and socialize the rest of the evening.<br />
:'''Wednesday''': [[Machine Learning]] - weekly get-together about Machine Learning<br />
:'''Thursday''': [[Five Minutes of Fame]] - third Thursday of each month.<br />
:'''Friday''': <strike>[[Mandarin Corner]] - Weekly getagether to practice Chinese language.</strike> On hiatus, [[User_talk:Elgreengeeto|contact]] if interested.<br />
:'''Friday''': [[CrazyCryptoNight]] - Discussion of cryptography for beginners through experts. 6-???<br />
:'''Sunday''': [[Sensebridge|Cyborg Group]] at 11 am. Brief discussion on wearable sensory interfaces and brain plasticity followed by collaborative hardware hacking.<br />
:'''Sunday''': [[Go]] Playing of the Go boardgame at 3pm. On nice days we often take the boards to Dolores part and play there.<br />
:'''Sunday''' : [[OpenEEG | OpenEEG Hacking]] Sundays, at 3-5pm.<br />
<br />
== Current workshops & classes ==<br />
(these recur but not indefinitely)<br />
:'''Tuesday''': [[Haskell/Haschool]] - Learn Haskell with Jason Dusek. 6PM - 7:30PM, from May until we're all experts.<br />
:'''Thursday''': [[Professional VFX Compositing With Adobe After Effects]] - Taught by [[User:SFSlim|Aaron Muszalski]]. 7:30PM - 10PM, most Thursdays in May & June & ? (click through dammit)<br />
<br />
= Planned Events =<br />
:'''(TBD)''': [[Introduction to the AVR Microcontroller]] - [[User:Mightyohm|Jeff]] and [[User:Maltman23|Mitch]] are planning an introductory class for people wanting to make cool projects with AVRs.<br />
:'''(TBD)''': [[Basic Chemistry Lab Techniques]]<br />
:'''(TBD)''': [[Cuddle Puddle for the Economy]] - Stress-hacking with informal massage exchange.<br />
:'''(TBD)''': [[Milk and Cookies]] - Come read your favorite selections out loud. With Milk and Cookies (and yeah, probably beer too).<br />
:'''(TBD)''': [[Processing Workshop 2]] - [[User:Scmurray|Scott]] is interested in teaching this, and is busy thinking about what, where, when, why, and how.<br />
:'''(TBD)''': [[Hack your Hardware]] -- We call BS on "no user-serviceable parts inside"<br />
<br />
:'''(TBD)''': [[Homebrew Instruction Class]] - The Wort (pt 1/3)<br />
:'''(TBD)''': [[Trip to Shooting Range]] - Field trip to a shooting range, to shoot guns. Express interest at [[Trip to Shooting Range]]<br />
:'''(TBD)''': [[Surface Mount Soldering Workshop]] - Learn how to solder cicuits with small surface mount parts. [[User:maltman23|Mitch Altman]] and Martin Bogomolni and others will show their tricks. [[User:maltman23|Mitch]] will bring hackable kits that uses surface mounts for you to solder.<br />
:'''(TBD)''' - [[Locksport and Lockpicking]]<br />
:'''(TBD)''' - [[Version control tutorial]]<br />
:'''(TBD)''' - [[Foreign language learning for rocket scientists]] - I'm near-native (fool people when I try) in (French and) Japanese, and a pro trans/terpreter and will share my shortcuts (skill-order, vocab, speed/articulation, translation≅grammar). No expertise on tonal languages yet... so if you know how to remember tones or how tone-sandhi interacts with speed and/or how nuances of speaker attitude are expressed in them (what we do with rythm/inflection/sentence-intonation and stress in Eng., and with particles and ??? in e.g. Cantonese) please chime in or call me (415-608-0564) so I can convey your wisdom. [also looking for a from-scratch Arabic partner]<br />
:'''(TBD)''': [[Getting started with Arduino]]<br />
:'''(TBD)''': [[Distributed Databases]]<br />
:'''(TBD)''': [[Adobe Lightroom]]<br />
<br />
= Past Events =<br />
:'''2009-05-21''': [[Five Minutes of Fame]]<br />
:'''2009-04-27''': [[EagleCAD workshop]] -- learn to use this CAD tool for printed circuit board design<br />
:'''2009-04-16''': [[Five Minutes of Fame]] April showers & flowers edition<br />
:'''2009-04-11''': [[RFID Hacking]] weekend workshop (this event moved from the original March date)<br />
:'''2009-04-05''': [[First aid and CPR class]] Learning how to not only not die, but also reduce scarring!<br />
:'''2009-04-03''': [[Sudo pop]] 2PM and on. Making the first batch of a Noisebridge label yerba mate-niated rootbrew, gratis and DIY<br />
:'''2009-03-26''': [[OpenEEG | OpenEEG Hacking]] first meet up for this new group: 8 pm<br />
:'''2009-03-19''': [[Five Minutes of Fame]]<br />
:'''2009-03-12''': [[OpenBTS and GSM]] talk by David Burgess<br />
:'''2009-02-14''': [[Open Heart Workshop]] Valentine's Day blinkyheart soldering party! <br />
:'''2009-02-13''': [[Time-t_Party|<tt>time_t</tt> Party]] to celebrate 1,234,567,890 since the Unix epoch.<br />
:'''2009-02-09''': [[Spanish learning at 8:30]]<br />
:'''2009-02-05''': [[PGP Key Workshop]]<br />
:'''2009-01-31''': [[Locksport and Lockpicking]]<br />
:'''2008-12-27''': [[25C3]] Chaos Computer Congress in Berlin<br />
:'''2008-12-20 & 21''': [[Creme Brulee]] Workshop on creating a french dessert, with bonus propane torch.<br />
:'''2008-12-17 20:00''': [[Machine Learning]] Birds-of-a-feather<br />
:'''2008-11-24''': [[Circuit Hacking Monday]] circuit design workshop<br />
:'''2008-11-21, 7pm''':[[Milk and Cookies]] -- [[User:Dmolnar|David Molnar]] hosts Milk and Cookies at 83C. Bring a short 5-7minute thing to read to others. Bring a potluck cookie/snack/drink if you like. David will bring milk and cookies.<br />
:'''2008-11-17, 7:30pm''': [[Basic Bicycle Maintain]] - [[User:rubin110|Rubin]] and [[User:rigel|rigel]] hate it when we see a bike that isn't maintained. Screechy chains and clacking derailleur can go to hell. Basic bike tune up, sharing the smarts on simple things you can do at home to make your ride suck a whole lot less.<br />
:'''2008-11-16, 5:00pm''': [[RepRap Soldering Party]] - help assemble RepRap! RSVPs required on wiki! [[User:Adi|adi]]<br />
:'''2008-11-16, 3:00pm''': [[Oscilloscopes]] - Learn how to use this versatile tool to test electronic circuits. Maximum 6 slots, please sign up ahead of time! [[User:dstaff|dstaff]]<br />
:'''2008-10-31''': [[Halloween Open House]] - NoiseBridge's own [[PPPC]] threw an awesome open house/halloween gala. Post pictures if you got 'em!<br />
:'''2008-10-25''': [[Soldering Workshop]] and Pumpkin Hackin' - Learn to solder for total newbies (or learn to solder better!), including surface mount. Additionally, carve your halloween pumpkins and enjoy some experimental pumpkin pie and/or soup.<br />
:'''2008-10-07''': (tuesday before meeting) - Etch a circuit board. I'll be trying a photo resist etching and a basic printed mask etching. This is step 1/3 for a project called "annoying USB thingie" which will execute pre-defined keystrokes by sneaking a tiny USB dongle onto a victim^h^h^h^h^h buddy's computer.<br />
:'''2008-09-13''': [[Processing Workshop]] — Learn this very easy-to-use programming language! - [[Processing Workshop Report]]<br />
:'''2008-02-16''': [[Brain Machine Workshop|Brain Machine Making Workshop]]: Our first hardware sprint!</div>Elgreengeetohttps://www.noisebridge.net/index.php?title=Talk:Eagle_Workshop&diff=5516Talk:Eagle Workshop2009-06-11T07:57:35Z<p>Elgreengeeto: New page: I think the next logical thing to practice would be custom part making. We should save gerber file export for another session. Also, I'd personally like to skip the review since time is so...</p>
<hr />
<div>I think the next logical thing to practice would be custom part making. We should save gerber file export for another session. Also, I'd personally like to skip the review since time is so limited and just request that people review on their own first. --[[User:Elgreengeeto|Skory]]</div>Elgreengeetohttps://www.noisebridge.net/index.php?title=Eagle_Workshop&diff=5515Eagle Workshop2009-06-11T07:51:08Z<p>Elgreengeeto: </p>
<hr />
<div>Following a very successful and popular Eagle CAD workshop back in April, we'll be having another one on Monday, June 15 at 7:00 pm.<br />
<br />
=Potential Topics=<br />
<br />
The following will be way too much for one and a half hours. Feel free to add topics, then let's use the talk page to vote for what we want most to cover.<br />
<br />
*Review of last time<br />
**What is EAGLE, 15 minute refresher on making a schematic and laying out a board.<br />
*Expanding into new topics<br />
**Making custom devices and libraries<br />
***How to make the pin outs and footprints from a data sheet, possibly recycling someone else's similar part.<br />
***How to label the part correctly and control what layers show on the board view (this can be confusing!)<br />
**Autorouting design rules<br />
**Error checking<br />
**Exporting gerber files and using a CAM processor<br />
***Checking the gerber files in a non-Eagle viewer program</div>Elgreengeetohttps://www.noisebridge.net/index.php?title=5MoF/2009-04-16&diff=50615MoF/2009-04-162009-05-19T19:18:50Z<p>Elgreengeeto: </p>
<hr />
<div> Slot 0: "The Reviewed Movies of John Waters" -- froggytoad<br />
Slot 1: "Find ha.sh: A search engine for files you already have" -- Asheesh Laroia & Jeffrey Malone<br />
Slot 2: "The Two Sides of Business Empathy and Power" -- Karl Long<br />
Slot 3: "Orb Swarm : Kinetic Art Breaks From the Machine" -- coreyfro<br />
Slot 4: "Integrating ZigBee into a project" -- nils<br />
Slot 5: "Charlieplexing" -- Josh Meyer<br />
Slot 6: "Rise of the Steamfucking Machines" -- Ani Niow<br />
Slot 7: "[http://fuzzybunny.s3.amazonaws.com/meep/hangeul_in_5_mins.odp Learn to Read: 한글 인 파이브 미느츠]" -- Skory<br />
Slot 8: "Watchuwant.tv" -- Arvind Narayanan, Adam Bossy, David Molnar<br />
Slot 9: "Safire's Magic" -- Safire<br />
<br />
Thanks to all the audience and participants, the event was held at 8PM at 83c Wiese.</div>Elgreengeetohttps://www.noisebridge.net/index.php?title=CVA_PCB_Beta_Rev0.1_Order&diff=4957CVA PCB Beta Rev0.1 Order2009-05-07T18:38:20Z<p>Elgreengeeto: </p>
<hr />
<div>OK. I just ordered 4 boards. More people than that expressed interest in a board, but I'm not confident enough in my PCB design skills to get too many of this Rev0.1.<br />
<br />
If you wanted one and the current is not enough, you should consider you might be best off waiting for Rev1. I can also of course send you the files and you can order one yourself.</div>Elgreengeetohttps://www.noisebridge.net/index.php?title=CVA_PCB_Beta_Rev0.1_Order&diff=4945CVA PCB Beta Rev0.1 Order2009-05-06T09:30:33Z<p>Elgreengeeto: </p>
<hr />
<div>'¡CAVEAT EMPTOR!'<br />
There ARE mistakes on this board! If I knew what they were I would have fixed them. But there's only so much use in staring at a schematic, sooner or later I have to have something physical to test out. Be prepared for a bit of pin-bending to make things fit, and - I hope unlikely but not impossible - getting out an x-acto knife and some jumper wires cuz I got a trace or two wrong. This is Beta Rev 0.1 for a reason.<br />
<br />
<br />
1. Check out the [http://sensebridge.net/cva/eagle/schematic090503.png schematic].<br />
<br />
2. Decide what of those components you do or don't want.<br />
<br />
3. Add a new row with your name, how many PCB panels you want, and what components you want (entering "ALL", "ALL except EEPROM" or the like is fine if it's clear what you mean).<br />
<br />
4. I will update with a price.<br />
<br />
5. Check back and confirm.<br />
<br />
6. Wait patiently.<br />
<br />
7. Be proud to be an elite beta tester.<br />
<br />
{| border="1" cellspacing="0" cellpadding="5" align="center"<br />
|-<br />
! Name<br />
! CVA PCB Beta Rev 0.1<br />
$15-$30?<br />
! Components<br />
< $45 w/compass?, <$15 w/o compass?<br />
|-<br />
|Skory<br />
|2<br />
| 2 x ALL except HM55B compass chip<br />
|-<br />
|Eric<br />
|1<br />
| 1 x ALL except HM55B compass chip<br />
|-<br />
<br />
|}</div>Elgreengeetohttps://www.noisebridge.net/index.php?title=CVA_PCB_Beta_Rev0.1_Order&diff=4927CVA PCB Beta Rev0.1 Order2009-05-06T02:30:45Z<p>Elgreengeeto: New page: '¡CAVEAT EMPTOR!' There ARE mistakes on this board! If I knew what they were I would have fixed them. But there's only so much use in staring at a schematic, sooner or later I have to hav...</p>
<hr />
<div>'¡CAVEAT EMPTOR!'<br />
There ARE mistakes on this board! If I knew what they were I would have fixed them. But there's only so much use in staring at a schematic, sooner or later I have to have something physical to test out. Be prepared for a bit of pin-bending to make things fit, and - I hope unlikely but not impossible - getting out an x-acto knife and some jumper wires cuz I got a trace or two wrong. This is Beta Rev 0.1 for a reason.<br />
<br />
<br />
1. Check out the [http://sensebridge.net/cva/eagle/schematic090503.png schematic].<br />
<br />
2. Decide what of those components you do or don't want.<br />
<br />
3. Add a new row with your name, how many PCB panels you want, and what components you want (entering "ALL", "ALL except EEPROM" or the like is fine if it's clear what you mean).<br />
<br />
4. I will update with a price.<br />
<br />
5. Check back and confirm.<br />
<br />
6. Wait patiently.<br />
<br />
7. Be proud to be an elite beta tester.<br />
<br />
{| border="1" cellspacing="0" cellpadding="5" align="center"<br />
|-<br />
! Name<br />
! CVA PCB Beta Rev 0.1<br />
$15-$30?<br />
! Components<br />
< $45 w/compass?, <$15 w/o compass?<br />
|-<br />
|Skory<br />
|2<br />
| 2 x ALL except HM55B compass chip<br />
|-<br />
|}</div>Elgreengeetohttps://www.noisebridge.net/index.php?title=EagleCAD_workshop&diff=4906EagleCAD workshop2009-05-05T21:22:28Z<p>Elgreengeeto: /* PCB Fab Houses */</p>
<hr />
<div>===EagleCAD===<br />
<br />
EagleCAD is a computer-aided tool for schematic capture and designing printed circuit boards<br />
that runs on Macs, Linux, and Windows. There is a free (as in beer) version available here:<br />
<br />
http://www.cadsoftusa.com/freeware.htm<br />
<br />
The free version is slightly crippled in terms of the size of the board you can design but is perfectly fine for most hobbyist use. <br />
<br />
====Tutorials====<br />
[http://online.sfsu.edu/~larryk/engr301/Waveform%20Generator/How%20to%20Make%20Circuit%20Boards.pdf Larry Klingenberg's Double Sided Board Tutorial]<br />
<br />
More info, tutorials, etc. from the SWARM wiki: http://wiki.orbswarm.com/index.php?title=The_PC_Board_Page<br />
<br />
====List of EacgleCAD "gotchas"====<br />
<br />
I promised I would post my list of "gotchas;" hope this helps avoid some irritation! [[User:Jtfoote|Jtfoote]] 23:38, 27 April 2009 (PDT)<br />
<br />
# IF BOARD AND SCHEMATIC GET OUT OF SYNC, YOU ARE SCREWED. This can happen if updates on the schematic don't make it to the board. To avoid this, always keep board file open when editing schematic, and vice versa! Use "rip up" instead of "delete" on the board. DRC will tell you when you are not in sync, otherwise you won't know. Use it often, and save often.<br />
# Don't click on "Drop" button when adding a component. Hit "cancel." "Drop" "drops" the library (!)<br />
# tOrigin layers must be visible to move/rotate components.<br />
# Overlapping wires sometimes don't logically connect. Add junction (green dot) if a problem. Check by moving component and seeing if wire moves with it. <br />
# "Cut" (scissor icon) is really "copy to paste buffer" and only works on groups! Use "copy" for single items. In V5, use shift-right-click or menu item to copy/move groups. <br />
# Pay attention to messages in the status bar, they are often helpful. For example when trying to select things on top of each other, clicking will cycle through each and the status bar will tell you how to select the one you want.<br />
<br />
===Possible topics for advanced tutorials===<br />
<br />
* How to design/edit custom parts using the library editor<br />
* How to fab a board. Converting EagleCAD designs to Gerber and drill files, checking output files and design rules, uploading to fab houses. <br />
* Panelizing (step-and-repeat copying) designs using http://claymore.engineer.gvsu.edu/~steriana/Python/gerbmerge/ (one way around EagleCad board size limitation)<br />
* Advanced tricks like logo images in the silkscreen layer<br />
<br />
===Checking Gerber file output===<br />
<br />
You will want to check that things look OK. Use a gerber file viewer<br />
like ViewMate (reg req) <br />
http://www.pentalogix.com/Download/download.html#item8<br />
<br />
or GerbView (free, open source, a little buggy)<br />
http://sourceforge.net/projects/gerbv/<br />
<br />
<br />
===PCB Fab Houses===<br />
<br />
Where to get your printed circuit boards fabricated after you've designed them<br />
<br />
Lady Ada has a PCB cost calculator with most sources: http://www.ladyada.net/library/pcb/costcalc.html<br />
<br />
The following is a biased list from [[User:Jtfoote|Jtfoote]] 09:36, 5 May 2009 (PDT)<br />
<br />
* [http://www.goldphoenixpcb.biz/ Gold Phoenix]: cheapest, longer turn-around (sent from China), fine quality, no charge for "panelization," can submit multiple boards for one run. SparkFun uses them; so could we, if we want to combine orders. They don't have web upload; you email your gerbers to some dude, but it worked great for me. <br />
* [http://www.protoexpress.com Sierra Proto Express]: I found this best combination of price/turn around time for small orders and prototypes, and they're local (Sunnyvale)<br />
* 4pcb.com (same as 33each.com and others) Good quality, slick marketing, more expensive than they seem (not-well-advertised setup charges and minimums). Avoid, but definitely use their free gerber file check site: http://www.freedfm.com/<br />
<br />
One reponse to Skory's list email said:<br />
<br />
<quote><br />
I have had good luck with both Sunstone Circuits (http://www.sunstone.com/) and Advanced Circuits (http://www.4pcb.com/). My order sizes have been 2, 100, and 350 boards.<br />
</quote></div>Elgreengeetohttps://www.noisebridge.net/index.php?title=EagleCAD_workshop&diff=4905EagleCAD workshop2009-05-05T21:21:42Z<p>Elgreengeeto: /* PCB Fab Houses */</p>
<hr />
<div>===EagleCAD===<br />
<br />
EagleCAD is a computer-aided tool for schematic capture and designing printed circuit boards<br />
that runs on Macs, Linux, and Windows. There is a free (as in beer) version available here:<br />
<br />
http://www.cadsoftusa.com/freeware.htm<br />
<br />
The free version is slightly crippled in terms of the size of the board you can design but is perfectly fine for most hobbyist use. <br />
<br />
====Tutorials====<br />
[http://online.sfsu.edu/~larryk/engr301/Waveform%20Generator/How%20to%20Make%20Circuit%20Boards.pdf Larry Klingenberg's Double Sided Board Tutorial]<br />
<br />
More info, tutorials, etc. from the SWARM wiki: http://wiki.orbswarm.com/index.php?title=The_PC_Board_Page<br />
<br />
====List of EacgleCAD "gotchas"====<br />
<br />
I promised I would post my list of "gotchas;" hope this helps avoid some irritation! [[User:Jtfoote|Jtfoote]] 23:38, 27 April 2009 (PDT)<br />
<br />
# IF BOARD AND SCHEMATIC GET OUT OF SYNC, YOU ARE SCREWED. This can happen if updates on the schematic don't make it to the board. To avoid this, always keep board file open when editing schematic, and vice versa! Use "rip up" instead of "delete" on the board. DRC will tell you when you are not in sync, otherwise you won't know. Use it often, and save often.<br />
# Don't click on "Drop" button when adding a component. Hit "cancel." "Drop" "drops" the library (!)<br />
# tOrigin layers must be visible to move/rotate components.<br />
# Overlapping wires sometimes don't logically connect. Add junction (green dot) if a problem. Check by moving component and seeing if wire moves with it. <br />
# "Cut" (scissor icon) is really "copy to paste buffer" and only works on groups! Use "copy" for single items. In V5, use shift-right-click or menu item to copy/move groups. <br />
# Pay attention to messages in the status bar, they are often helpful. For example when trying to select things on top of each other, clicking will cycle through each and the status bar will tell you how to select the one you want.<br />
<br />
===Possible topics for advanced tutorials===<br />
<br />
* How to design/edit custom parts using the library editor<br />
* How to fab a board. Converting EagleCAD designs to Gerber and drill files, checking output files and design rules, uploading to fab houses. <br />
* Panelizing (step-and-repeat copying) designs using http://claymore.engineer.gvsu.edu/~steriana/Python/gerbmerge/ (one way around EagleCad board size limitation)<br />
* Advanced tricks like logo images in the silkscreen layer<br />
<br />
===Checking Gerber file output===<br />
<br />
You will want to check that things look OK. Use a gerber file viewer<br />
like ViewMate (reg req) <br />
http://www.pentalogix.com/Download/download.html#item8<br />
<br />
or GerbView (free, open source, a little buggy)<br />
http://sourceforge.net/projects/gerbv/<br />
<br />
<br />
===PCB Fab Houses===<br />
<br />
Where to get your printed circuit boards fabricated after you've designed them<br />
<br />
Lady Ada has a PCB cost calculator with most sources: http://www.ladyada.net/library/pcb/costcalc.html<br />
<br />
The following is a biased list from [[User:Jtfoote|Jtfoote]] 09:36, 5 May 2009 (PDT)<br />
<br />
* [http://www.goldphoenixpcb.biz/ Gold Phoenix]: cheapest, longer turn-around (sent from China), fine quality, no charge for "panelization," can submit multiple boards for one run. SparkFun uses them; so could we, if we want to combine orders. They don't have web upload; you email your gerbers to some dude, but it worked great for me. <br />
* [www.protoexpress.com Sierra Proto Express]: I found this best combination of price/turn around time for small orders and prototypes, and they're local (Sunnyvale)<br />
* 4pcb.com (same as 33each.com and others) Good quality, slick marketing, more expensive than they seem (not-well-advertised setup charges and minimums). Avoid, but definitely use their free gerber file check site: http://www.freedfm.com/<br />
<br />
One reponse to Skory's list email said:<br />
<br />
<quote><br />
I have had good luck with both Sunstone Circuits (http://www.sunstone.com/) and Advanced Circuits (http://www.4pcb.com/). My order sizes have been 2, 100, and 350 boards.<br />
</quote></div>Elgreengeetohttps://www.noisebridge.net/index.php?title=EagleCAD_workshop&diff=4904EagleCAD workshop2009-05-05T21:18:49Z<p>Elgreengeeto: /* PCB Fab Houses */</p>
<hr />
<div>===EagleCAD===<br />
<br />
EagleCAD is a computer-aided tool for schematic capture and designing printed circuit boards<br />
that runs on Macs, Linux, and Windows. There is a free (as in beer) version available here:<br />
<br />
http://www.cadsoftusa.com/freeware.htm<br />
<br />
The free version is slightly crippled in terms of the size of the board you can design but is perfectly fine for most hobbyist use. <br />
<br />
====Tutorials====<br />
[http://online.sfsu.edu/~larryk/engr301/Waveform%20Generator/How%20to%20Make%20Circuit%20Boards.pdf Larry Klingenberg's Double Sided Board Tutorial]<br />
<br />
More info, tutorials, etc. from the SWARM wiki: http://wiki.orbswarm.com/index.php?title=The_PC_Board_Page<br />
<br />
====List of EacgleCAD "gotchas"====<br />
<br />
I promised I would post my list of "gotchas;" hope this helps avoid some irritation! [[User:Jtfoote|Jtfoote]] 23:38, 27 April 2009 (PDT)<br />
<br />
# IF BOARD AND SCHEMATIC GET OUT OF SYNC, YOU ARE SCREWED. This can happen if updates on the schematic don't make it to the board. To avoid this, always keep board file open when editing schematic, and vice versa! Use "rip up" instead of "delete" on the board. DRC will tell you when you are not in sync, otherwise you won't know. Use it often, and save often.<br />
# Don't click on "Drop" button when adding a component. Hit "cancel." "Drop" "drops" the library (!)<br />
# tOrigin layers must be visible to move/rotate components.<br />
# Overlapping wires sometimes don't logically connect. Add junction (green dot) if a problem. Check by moving component and seeing if wire moves with it. <br />
# "Cut" (scissor icon) is really "copy to paste buffer" and only works on groups! Use "copy" for single items. In V5, use shift-right-click or menu item to copy/move groups. <br />
# Pay attention to messages in the status bar, they are often helpful. For example when trying to select things on top of each other, clicking will cycle through each and the status bar will tell you how to select the one you want.<br />
<br />
===Possible topics for advanced tutorials===<br />
<br />
* How to design/edit custom parts using the library editor<br />
* How to fab a board. Converting EagleCAD designs to Gerber and drill files, checking output files and design rules, uploading to fab houses. <br />
* Panelizing (step-and-repeat copying) designs using http://claymore.engineer.gvsu.edu/~steriana/Python/gerbmerge/ (one way around EagleCad board size limitation)<br />
* Advanced tricks like logo images in the silkscreen layer<br />
<br />
===Checking Gerber file output===<br />
<br />
You will want to check that things look OK. Use a gerber file viewer<br />
like ViewMate (reg req) <br />
http://www.pentalogix.com/Download/download.html#item8<br />
<br />
or GerbView (free, open source, a little buggy)<br />
http://sourceforge.net/projects/gerbv/<br />
<br />
<br />
===PCB Fab Houses===<br />
<br />
Where to get your printed circuit boards fabricated after you've designed them<br />
<br />
Lady Ada has a PCB cost calculator with most sources: http://www.ladyada.net/library/pcb/costcalc.html<br />
<br />
The following is a biased list from [[User:Jtfoote|Jtfoote]] 09:36, 5 May 2009 (PDT)<br />
<br />
* Gold Phoenix: cheapest, longer turn-around (sent from China), fine quality, no charge for "panelization," can submit multiple boards for one run. SparkFun uses them; so could we, if we want to combine orders. They don't have web upload; you email your gerbers to some dude, but it worked great for me. <br />
* Sierra Proto Express: I found this best combination of price/turn around time for small orders and prototypes, and they're local (Sunnyvale)<br />
* 4pcb.com (same as 33each.com and others) Good quality, slick marketing, more expensive than they seem (not-well-advertised setup charges and minimums). Avoid, but definitely use their free gerber file check site: http://www.freedfm.com/<br />
<br />
One reponse to Skory's list email said:<br />
<br />
<quote><br />
I have had good luck with both Sunstone Circuits (http://www.sunstone.com/) and Advanced Circuits (http://www.4pcb.com/). My order sizes have been 2, 100, and 350 boards.<br />
</quote></div>Elgreengeetohttps://www.noisebridge.net/index.php?title=EagleCAD_workshop&diff=4903EagleCAD workshop2009-05-05T21:16:59Z<p>Elgreengeeto: /* PCB Fab Houses */</p>
<hr />
<div>===EagleCAD===<br />
<br />
EagleCAD is a computer-aided tool for schematic capture and designing printed circuit boards<br />
that runs on Macs, Linux, and Windows. There is a free (as in beer) version available here:<br />
<br />
http://www.cadsoftusa.com/freeware.htm<br />
<br />
The free version is slightly crippled in terms of the size of the board you can design but is perfectly fine for most hobbyist use. <br />
<br />
====Tutorials====<br />
[http://online.sfsu.edu/~larryk/engr301/Waveform%20Generator/How%20to%20Make%20Circuit%20Boards.pdf Larry Klingenberg's Double Sided Board Tutorial]<br />
<br />
More info, tutorials, etc. from the SWARM wiki: http://wiki.orbswarm.com/index.php?title=The_PC_Board_Page<br />
<br />
====List of EacgleCAD "gotchas"====<br />
<br />
I promised I would post my list of "gotchas;" hope this helps avoid some irritation! [[User:Jtfoote|Jtfoote]] 23:38, 27 April 2009 (PDT)<br />
<br />
# IF BOARD AND SCHEMATIC GET OUT OF SYNC, YOU ARE SCREWED. This can happen if updates on the schematic don't make it to the board. To avoid this, always keep board file open when editing schematic, and vice versa! Use "rip up" instead of "delete" on the board. DRC will tell you when you are not in sync, otherwise you won't know. Use it often, and save often.<br />
# Don't click on "Drop" button when adding a component. Hit "cancel." "Drop" "drops" the library (!)<br />
# tOrigin layers must be visible to move/rotate components.<br />
# Overlapping wires sometimes don't logically connect. Add junction (green dot) if a problem. Check by moving component and seeing if wire moves with it. <br />
# "Cut" (scissor icon) is really "copy to paste buffer" and only works on groups! Use "copy" for single items. In V5, use shift-right-click or menu item to copy/move groups. <br />
# Pay attention to messages in the status bar, they are often helpful. For example when trying to select things on top of each other, clicking will cycle through each and the status bar will tell you how to select the one you want.<br />
<br />
===Possible topics for advanced tutorials===<br />
<br />
* How to design/edit custom parts using the library editor<br />
* How to fab a board. Converting EagleCAD designs to Gerber and drill files, checking output files and design rules, uploading to fab houses. <br />
* Panelizing (step-and-repeat copying) designs using http://claymore.engineer.gvsu.edu/~steriana/Python/gerbmerge/ (one way around EagleCad board size limitation)<br />
* Advanced tricks like logo images in the silkscreen layer<br />
<br />
===Checking Gerber file output===<br />
<br />
You will want to check that things look OK. Use a gerber file viewer<br />
like ViewMate (reg req) <br />
http://www.pentalogix.com/Download/download.html#item8<br />
<br />
or GerbView (free, open source, a little buggy)<br />
http://sourceforge.net/projects/gerbv/<br />
<br />
<br />
===PCB Fab Houses===<br />
<br />
Where to get your printed circuit boards fabricated after you've designed them<br />
<br />
Lady Ada has a PCB cost calculator with most sources: http://www.ladyada.net/library/pcb/costcalc.html<br />
<br />
The following is a biased list from [[User:Jtfoote|Jtfoote]] 09:36, 5 May 2009 (PDT)<br />
<br />
* Gold Phoenix: cheapest, longer turn-around (sent from China), fine quality, no charge for "panelization," can submit multiple boards for one run. SparkFun uses them; so could we, if we want to combine orders. They don't have web upload; you email your gerbers to some dude, but it worked great for me. <br />
* Sierra Proto Express: I found this best combination of price/turn around time for small orders and prototypes, and they're local (Sunnyvale)<br />
* 4pcb.com (same as 33each.com and others) Good quality, slick marketing, more expensive than they seem (not-well-advertised setup charges and minimums). Avoid, but definitely use their free gerber file check site: http://www.freedfm.com/</div>Elgreengeetohttps://www.noisebridge.net/index.php?title=Compass_Vibro_Anklet_Directions&diff=4893Compass Vibro Anklet Directions2009-05-04T21:01:23Z<p>Elgreengeeto: </p>
<hr />
<div>How to make a vibrating compass anklet<br />
<br />
These steps describe how to make a vibrating compass anklet which lets you tell absolute direction all day long. The project is described in [[Compass Vibro Anklet]] which is mostly a description of Eric and Skory's work.<br />
<br />
Skory took the time to sit down with me at [[Sensebridge]] and explain how they did it, so I wrote this up so that others can see it too.<br />
<br />
I’m going to work on assembling an anklet myself using these steps. When I do, I’ll update the directions with what I find.<br />
<br />
If you want to make a compass belt instead of a compass anklet, it should be easy: use a longer ribbon cable, space the motors out wider, and cut longer strips of fabric. Everything else would be the same.<br />
<br />
Hope this is helpful! Feedback on this document is very welcome.--[[User:Ted|Ted]] 01:29, 4 May 2009 (PDT)<br />
<br />
==Components==<br />
<br />
You’ll need all the following components:<br />
<br />
'''Arduino:''' a controller to run everything. (I’m using the Arduino-clone [www.moderndevice.com Really (RBBB) Bare-Bones Board])<br />
<br />
'''Shift Register:''' regulates power and switches which pager motor is running. (I’m using part number TPIC6B595)<br />
<br />
'''Compass Chip:''' determines compass direction and feeds that information to the Arduino. <br />
(I’m using an HM55B from Parallax)<br />
<br />
'''Battery:''' For power. You’ll need something that will source at least 3.325V and about 700mAh. (I bought a Polymer Li-Ion Battery 3.7V 875mAh from [http://www.all-battery.com/polymerli-ionbattery37v875mah383562.aspx here)<br />
<br />
'''Pager Motors:''' Eight vibrating motors. Whichever one is northmost will vibrate. (I bought ROB-08449 vibration motors but they were crazy overpriced - $7 each, it's better to get them from [www.pagermotors.com pagermotors.com])<br />
<br />
'''Proto-board''' a thin board with a grid of pads into which one can solder the components, which you will need to cut down to size (available at an electronics store).<br />
<br />
'''Ribbon Cable:''' One or possibly two twelve inch lines of Ribbon Cable wire to connect the controller to the pager motors. (available at an electronics store)<br />
<br />
'''Connector/Switch:''' A power switch or connection for the power supply to act as an on/off switch for the device (available at an electronics store)<br />
<br />
'''Connector:''' A 9-pin connector to connect the shift register to the pager motor assembly. (available at an electronics store)<br />
<br />
'''Wiring:''' Wire & solder & electrical tape to connect everything (available at an electronics store)<br />
<br />
'''Elastic:''' The main body of the anklet armature. Two inches wide. About 12 inches of elastic, plus a few three inch pieces to make pockets for the controller and the battery. (get from a fabric store)<br />
<br />
'''Zipper:''' A zipper so that you can close every up when you’re not tinkering. About 12 inches of zipper. (get from a fabric store)<br />
<br />
'''Velcro Strip:''' To close the anklet. About an inch wide, and three or four inches long. (get from a fabric store)<br />
<br />
'''Felt Strip:''' To connect to the ankle on the other side and hold onto the Velco-backed motors. About an inch wide and twelve inches long.<br />
<br />
'''Foam:''' A thin strip of foam. Goes between the felt and the elastic to absorb vibration (making it easier to distinguish which motor is vibrating and to make the device quieter). About an inch wide and twelve inches long.<br />
<br />
'''Velcro Patches:''' Eight little patches of Velcro, about half an inch square each. These will attach the pager motors to the anklet in a way that lets you move them around the anklet so that each motor is in the right place.<br />
<br />
'''Cloth Patches:''' Eight little patches of cloth, about half an inch square each. These will connect to the Velcro patches to make little pockets for each pager motor. The cloth patch will be the part that touches your ankle, so pick something soft.<br />
<br />
'''Casing for controller assembly:''' Casing to hold the final controller assembly. It may be possible to adapt this from a scrounged plastic box of some kind. (make or improvise)<br />
<br />
==Tools== <br />
Computer to program Arduino<br />
<br />
FTDI Cable (or BUB Board from Modern Device) to program Arduino<br />
<br />
Soldering tools<br />
<br />
Breadboard for initial controller build<br />
<br />
Possibly LEDs for initial controller build<br />
<br />
Saw to cut the proto-board to size<br />
<br />
Wire stripper<br />
<br />
Scissors<br />
<br />
Sewing machine<br />
<br />
<br />
==Overview of Compass Vibro Anklet==<br />
The vibrating compass anklet has three basic parts: a '''controller''', a '''pager motor array''', and an '''armature'''.<br />
<br />
The '''controller''' controls the motors, provides power and data and sensory input. The controller consists of an Arduino (a programmable board that uses the ATMega processor + Arduino bootloader, which is designed for exactly this kind of project), a Shift Register (which takes a single byte of data from the Arduino and uses this to trigger a single motor), the compass chip (which connects to the Arduino), and the battery (which connects to the Arduino). Basically, everything in the controller connects to the Arduino, and then the shift register connects to the pager motor array.<br />
<br />
The '''pager motor array''' consists of eight pager motors (little vibrating motors) and the wire to connect them up. The pager motor array receives power and signal from the shift register, which activates one of eight pager motors. The pager motors are little vibrating motors that come out along the length of the ribbon cable. All of the motors get power from the same line, but only one will be grounded at a time, so only one will run at a time.<br />
<br />
The '''armature''' is the housing for the whole thing. It’s an elastic anklet, with a zipper and housing for the controller and the pager motor array. The motors go on the inside of the armature, and will need to have an adjustable location.<br />
<br />
==Assembly Summary==<br />
<br />
There are four basic parts to making the Vibrating Compass Anklet. After each part, test everything to make sure it works. Probably you’ll go through each step several times to get it right, and hopefully you’ll find ways to improve the design and the creation.<br />
<br />
'''Part One: Assemble Controller on Breadboard'''<br />
<br />
'''Part Two: Build Pager Motor Array'''<br />
<br />
'''Part Three: Make Armature'''<br />
<br />
'''Part Four: Assemble Controller on Board'''<br />
<br />
'''Part Five: Put Assembly Into Armature'''<br />
<br />
==Part One: Assemble Controller on Breadboard==<br />
<br />
The controller has five parts: the Arduino, the shift register, the compass chip, the battery, and the pager motor connector. The pager motor connector connects to the shift register. Everything else connects to the Arduino.<br />
<br />
Here’s a really fake diagram of that:<br />
<br />
<br />
compass chip<br />
|<br />
Arduino --- Shift Register --- pager motor connector<br />
|<br />
battery<br />
<br />
To assemble the controller on the breadboard:<br />
<br />
1. Connect the battery to the Arduino. The wires from the battery go into the power and ground for the Arduino. If the battery includes a connect, you may just want to get a matching connector for the other side and attach that to the Arduino. Alternately, if you’re feeling ambitious you could add a power switch here.<br />
<br />
2. Connect the compass chip to the Arduino. You’ll connect three data pins, plus power and ground, to the Arduino. One pin is input/output: bridge together the “in” pin and the “out” pin from the compass and connect them to the same pin on the Arduino. The other two are the clock pin and the enable pin. These all connect to the Arduino’s output pins. Note which pins you use, since you’ll need to update the code with that information.<br />
<br />
3. Connect the shift register to the Arduino. You’ll connect five data pins, plus power and ground. One of the data pins on the shift register is the enable pin. This pin must connect to a pin on the Arduino which is capable of PWM. (PWM lets a digital signal simulate analog, and the enable pin needs analog input if you want to be able to vary the speed of the motors.)<br />
<br />
4. Connect the shift register to the header socket. Solder ribbon wire to the shift register’s output and give it a few inches of wire. On the other side of the ribbon wire, solder a 9-pin header socket.<br />
<br />
5. Install the Arduino IDE on your computer. You can get the IDE here: http://www.arduino.cc/en/Main/Software<br />
<br />
6. Connect your computer to the Arduino with a data cable (it is recommended to unplug the battery when you do so). Make sure you’ve got a data connection. Try running Hello World or a similar program to make sure you’ve got everything working.<br />
<br />
7. Download the code into the Arduino. It's on the wiki on the [[Compass Vibro Anklet Code]] page. You will probably need to modify the Arduino code based on what you connected on the Arduino: if you connect anything differently, change the Arduino code so that it connects to the right place. This shouldn’t be a very difficult change in the code: just change the constants to reflect where you attached each wire.<br />
<br />
8. For testing purposes, you may want to connect the shift register to LEDs and try moving around with the breadboard. Each LED in turn should light up as you turn around. Note that the light will go off if you hold it in one place for a while. This is intentional: when the motors are vibrating against your ankle, they can get very annoying and itchy if they run all the time!<br />
<br />
When you’re done with this, you’ll have a breadboard that includes all the logic to make the device work. You’ll have a powered digital compass. Most likely, you’ll want to test the compass with LEDs instead of motors at this point because they’re easier.<br />
<br />
This is a working sensor! Now you need a display and an armature.<br />
<br />
==Part Two: Build Pager Motor Array==<br />
<br />
The pager motor array is logically pretty simple, but it’s tricky to solder together properly.<br />
<br />
The pager motor array consists of a ribbon cable, eight motors, and a connector with at least nine pins: one for power and eight for ground. Each pager motor will connect to one of the ground lines, and all pager motors connect to the power line. The pager motors are spaced somewhat evenly along the length of the ribbon cable.<br />
<br />
Note that the exact dimensions will depend on the size of the finished product. Your ribbon cable may be shorter or longer than twelve inches. If you’re making this for yourself, measure the circumferences of your own ankle. Plan on making something that big, and add a few inches for connections and extra space.<br />
<br />
1. Connect the ribbon cable to the connector. Strip the ends of the ribbon cable and solder them into the connector.<br />
<br />
2. Peel off a little bit of the bottom ground wire of the ribbon cable. Strip the end of the wire. Solder the line to the ground line of the first pager motor.<br />
<br />
3. Splice off a wire from the power line: strip some of the cable, solder another wire to the exposed metal, and wrap the connection with electrical tape for stability. Connect the spliced wire to the power line of the first pager motor.<br />
<br />
4. Repeat steps 2-3 for each pager motor along the length of the ribbon cable. Peel of a little more from the next ground wire of the ribbon cable and strip the wire to solder to the ground line of the next pager motor. Splice another wire from the power line in the same place and solder the spliced wire to the power line of the next pager motor.<br />
<br />
NOTE: There may be an easier way to solder all this together. Instead of using one cable and splicing power off for each pager motor, use two separate ribbon cables: one for power and one for ground. At each pager motor, peel off one wire from each ribbon cable. Eight pins will connect to the ground, and all of the ribbon cable for power will get connected together at the end, and all connect to a single pin. This is harder to describe, but easier to assemble. If this works well, the instructions will be updated with steps for how to do this instead.<br />
<br />
When you’re done, you should have a ribbon cable that gets thinner and thinner as it moves away from the connector, as wires split off to connect to each of the eight pager motors. Connect it to the controller and try it out! <br />
<br />
To really test it, make a quick armature with some elastic and walk around with it. This is actually a fully functional vibrating compass! It’s just that it would be impossible to wear for long periods, so you need to put the compass into something more complex, and make an armature suitable for wearing long-term.<br />
<br />
==Part Three: Make Armature==<br />
<br />
The armature is cloth part that will house everything. It consists of a folded-over piece of elastic, a zipper, felt and foam to contain the pager array comfortably, a Velcro strap to close the anklet, and elastic pockets for the controller and battery.<br />
<br />
Note that the exact dimensions will depend on the size of the finished product. Your strip of cloth may be shorter or longer than twelve inches. If you’re making this for yourself, measure the circumferences of your own ankle. Plan on making something that big, and add a few inches for connections and extra space.<br />
<br />
1. Cut a twelve-inch length of elastic and fold it in half.<br />
<br />
2. Sew each end of the elastic closed. You should now have something like a long floppy canoe.<br />
<br />
3. Sew the zipper onto the elastic on each side of the fold, at the top. You should have a long tube that you can unzip into a long floppy canoe.<br />
<br />
4. Pick one side of the elastic to be the inner side, which will go against your ankle. Lay a thin layer of foam onto this side, and then a layer of felt. Sew this down so that it all stays in place.<br />
<br />
5. Cut vertical slits into the inner side, through the elastic, the foam and the felt. Sew these open so that they’re stable. They should end up a little like button holes. The vibrating motors are the buttons: they’ll poke out through these button holes to press against your leg.<br />
<br />
6. On the outer side of the elastic, on one end of the anklet, sew two strips of elastic to make pockets. One will hold the controller, the other will hold the battery. It’s better to sew these on like a loop, rather than a wave: loop them back under so that the stitching is on the inside of the battery. This is a little harder to do, but it means that the pressure from the pockets will pull the elastic out instead of bunching it up.<br />
<br />
7. On one end of the anklet, on the outside of the elastic, sew a couple inches of fuzzy velcro. On the other end, sew a couple inches of pointy Velcro out past the edge. Ensure that the dimensions of these allow you to wrap the armature around your ankle and then fasten it on.<br />
<br />
You should now have an anklet that can hold all the wiring on the inside of a zipped-up pocket, which allows pager motors to poke into your ankle to vibrate, which has two elastic pockets for the controller and battery, and which you can wear comfortably with the Velcro strap.<br />
<br />
NOTE: Skory is working on an better design for this, where the foam and felt are inside the belt. With this improvement, the only thing that touches your skin will be the armature, so it should be easier to take all the electronics out and wash all the cloth so it doesn’t get gross and sweaty. If this works well, the instructions will be updated with steps for how to do this instead.<br />
<br />
==Part Four: Assemble Controller on Board==<br />
<br />
This step pretty much involves putting the controller together again in a way that is more compact so you can wear it around.<br />
<br />
The compass chip still needs to be horizontal, even though the rest of it will probably end up vertical. Compass chips needs to be horizontal to work. At least, two-axis compass chips do. A good three-axis chip wouldn’t necessarily need to be horizontal to work, but 3D compass chips are prohibitively expensive.<br />
<br />
1. Solder the shift register onto a minimally sized rectangle of proto-board.<br />
<br />
2. Solder the Arduino board on top so that the shift register is sandwiched in between. If you do this right, most of the data connections will actually fit together perfectly.<br />
<br />
3. Solder the compass chip at the tip of the other two boards so that the compass chip is horizontal while the Arduino is vertical. Connect the compass chip to the Arduino.<br />
<br />
4. Make a connection from the Arduino to the battery (again, this should probably involve your switch). The battery will go in a separate pocket, so use a few inches of wire on each side.<br />
<br />
5. Make a connection from the shift register to the connector for the pager motor array. Again, one pin needs to have power, and the other eight will connect to the eight drains on the shift register. Soldering the little wires in for this step is absolutely horrible, but don't worry too much if you don't solder the pins in the right order, you can change to code later to compensate.<br />
<br />
At this point, you should have a compact little stack of electronics plus a battery. It should still work the same way it did when everything was on the breadboard, but now it will fit in the armature.<br />
<br />
You will need some kind of casing for the stack of electronics. You may be able to modify an existing plastic box for this, or make your own.<br />
<br />
NOTE: Skory and Eric are working very hard on a PCB which will make this step a lot easier and remove a lot of the wiring and difficult soldering and hassle for this. If this works well, the instructions will be updated with steps for how to do this instead, along with how to purchase these PCBs.<br />
<br />
==Part Five: Put Assembly Into Armature==<br />
<br />
Now put it all together.<br />
<br />
1. Glue squares of Velcro and cloth onto the end of each pager motor. Any good fabric glue will do, but be patient if it's slow-setting. (Alternatively, for another dollar or two, you can by square-inch velcro stickers, the adhesive on which seems to be good enough to hold the cloth on the other side of the motor.)<br />
<br />
2. Put the whole pager motor assembly into the pouch, with just the connector sticking out of one end of the zipper.<br />
<br />
3, Put the controller assembly and batteries into the appropriate pockets and connect them up.<br />
<br />
4. Push the pager motors through the button-holes in the armature. Wear the anklet and test it a little to find where each motor should go. Since ankles are so irregularly-shaped, you’ll need to adjust which button-holes get pager motors by trial and error.<br />
<br />
You should now have a compass anklet that you can wear comfortably in daily life!</div>Elgreengeetohttps://www.noisebridge.net/index.php?title=HM55B_Order&diff=4847HM55B Order2009-05-03T19:42:44Z<p>Elgreengeeto: </p>
<hr />
<div>Order of HM55B 2-axis compass chip from Parallax<br />
<br />
<br />
Hitachi HM55B Compass Module 98 29123 5 28.49 142.45 8.25 %<br />
Subtotal Excl. Tax USD 142.45 <br />
Plus Tax USD 11.75 <br />
Shipping & Handling USD 0.55 <br />
Total Incl. Tax USD 154.75 <br />
<br />
$154.75 / 5 = $31<br />
<br />
<br />
{| border="1" cellspacing="0" cellpadding="5" align="center"<br />
|-<br />
! Name of Orderer<br />
! Total Owed<br />
! Payment Received<br />
|-<br />
|-<br />
| Eric<br />
| $31<br />
| orderer<br />
|-<br />
| David<br />
| $31<br />
| paid $31<br />
|-<br />
| Ted<br />
| $31<br />
| paid $31<br />
|-<br />
| Matt<br />
| $31<br />
| paid $31<br />
|-<br />
| Ayer<br />
| $31<br />
| paid $31 (to Skory, Skory will pay Eric)<br />
|}</div>Elgreengeetohttps://www.noisebridge.net/index.php?title=Hack_Notes_CVA_090421&diff=4794Hack Notes CVA 0904212009-04-29T06:35:34Z<p>Elgreengeeto: </p>
<hr />
<div>Working on our Schematics today - making decisions about parts, and discovering that Eagle is hard to use.<br />
<br />
We are trying to use Eagle software as it's common in the community, free for non-commercial use (and only $49 if you sell stuff that has small & simple boards).<br />
<br />
Here is the basic physical form factor we discussed:<br />
#On the back side of the PCB mounts a 3xAAA battery holder<br />
#*We can include a mount-point on the back as well for a JST connector, allowing builders to optionally use a LiPo instead of AAA's. (This way we don't have to inclue LiPo + charger in kit, which would be a further $20-$30 but it's still an easy option.)<br />
#On the front goes most of the components.<br />
#*This allows everything except the motor array to be in one case meaning simpler construction and less wires.<br />
#*One downside is increased weight in one place on the armature, rather than distributed in two.<br />
#The case will have thin grooves down the sides to fit the long edges of the PCB, holding it in place.<br />
#The width of the PCB+components+battery(pack) is sufficient that we can mount an HM55B compass chip at a right angle across the top without needing to add any kind of bulge for it.<br />
#*We can achieve this by having two right angle headers, one on each side of the PCB. By using different size headers, the through-hole pins can meet the board at different heights, but the sockets will be at the same height. The width can be adjusted to match the width of the pins on the Parallax breakout board.<br />
#*Some drawings or pictures of a mock-up would make this easier to understand. Maybe later! <br />
<br />
<br />
568-1708-5-ND = 12 bit shift register, 20-SOIC, $2.17. Same thing 20DIP: 568-3142-5-ND.<br />
<br />
Sparkfun Arduino Pro Mini - 3.3V/8MHz<br />
http://www.sparkfun.com/commerce/product_info.php?products_id=8824<br />
There is a download link for Eagle schematics. Circuit includes the ATMEGA168, oscillator, passives, and serial programmer pin out. Also includes a reset button which we will eliminate. <br />
<br />
The Pro Mini does not have the bootloader flash (ISP) pinout organized, we could copy that from the Ardiuno Pro circuit:<br />
http://www.sparkfun.com/commerce/product_info.php?products_id=8783<br />
<br />
We want an on/off switch. EG1943-ND $0.92 - lower profile. CKN9564-ND, $0.53 - winner for now<br />
<br />
3xAAA battery holder, 2479K-ND. Plus, pin out and part for JST jack (but no LiPo included in kit).<br />
(Amazingly least terrible) [http://www.keyelco.com/images/products/2479.gif schematic here].<br />
<br />
Provide a pin out for talking to other circuits - I2C, SPI. Plus VCC and GND.<br />
<br />
Socket for pager motor array - double layer right angle header. 14 pins total: 7x2. Digikey # S5521-ND.<br />
<br />
Pin out for connections to compass IC. 6 holes in PCB, right angle female headers connect into male headers from HM55B. S4338-ND, plus S5517-ND on battery side - must clip bottom row leads.<br />
<br />
64KB EEPROM I2C 8 SOIC footprint: AT24C64CN-SH-B-ND. Useful for logging data from device during use e.g. motor activity. Same thing 8DIP: AT24C64C-PU-ND.<br />
<br />
Voltage Regulator. Specs: 3.3V output, >250mA. Two choices: TKS71733CT-ND accept from 1.8-14V, 280mA output, $1.52. MCP1824T-3302E/OTCT-ND accepts from 2.1-6V, 300mA, $0.79. Both require 2 external caps (typically 1uf and 2.2 or 4.7uf). These will add a few dimes more in cost.<br />
<br />
What shape do we want the board to have? Match shape of battery holder<br />
<br />
JST connectors: 455-1734-1-ND (top entry), 455-1749-1-ND (side entry), $0.43/0.41 each. Females.<br />
<br />
<br />
Bill Of Materials (BOM): we need to make a list of all parts once we have the circuit down.<br />
<br />
Do we need mounting holes? NO<br />
<br />
They sell GPS chips for $40 now - we could put a footprint down and I bet some hackers would go nuts for that...<br />
<br />
People who want some boards:<br />
Ayer - 1<br />
Eric - 1<br />
Skory - 1</div>Elgreengeetohttps://www.noisebridge.net/index.php?title=Hack_Notes_CVA_090426&diff=4748Hack Notes CVA 0904262009-04-27T06:06:49Z<p>Elgreengeeto: /* Science of Vibration Management */</p>
<hr />
<div>=Long Overdue Hack Notes from Eric=<br />
<br />
==Eric's CVA Working Again==<br />
<br />
I spent all week trying to get my CVA working - I had to fix numerous issues, like the death of my programmer pins, the death of my compass chip, various bad solder joints, and of course the complete rebuilding of my armature and display. <br />
<br />
But it done - I once again have a fully functioning CVA, which even points north!<br />
<br />
==Dual Ribbon Display==<br />
<br />
I tested our idea of using two ribbons for the display, one which carries only power. This worked great - I didn't have to create little extension wires for the motors, and it was therefore much quicker to create. On the downside, I now have two crimps next to each other in the armature and that makes it stand out a little more than I like. In the future I think I would use Skory's design which has the electronics at the end so that crimps are not necessary.<br />
<br />
==Science of Vibration Management==<br />
<br />
Skory and I both wore both of our armatures. One armature has an extra layer of foam, the idea being to absorb some of the vibration, thus making it easier to differentiate between the various motors.<br />
<br />
Eric: I think the foam makes a real difference, if I ever rebuild my armature I am likely to do the extra work. Motor isolation is far superior with the foam present, but without foam the device is still totally usable.<br />
<br />
Skory: Foam helps, but works fine without it. For kits, we may not need to use foam. Foam is cheap, so it's a question of labor costs/value. Current vote is for foam.<br />
<br />
==HM55B Female Jack Idea==<br />
<br />
I rebuild my electronics today to use the HM55B compass chip, because my HMC6352 stopped working. I used our new idea of having a single right angle female header on one side of the board, and a dual row of female headers on the other, and have the compass just jack into them. It worked, I think this is a super great idea for how to get the 90 degree angle that we need without difficulty or a quirky daughter board.<br />
<br />
==Review of protoboard design decisions with Mikolaj==<br />
<br />
Mikolaj suggested that we have a footprint for an SD card on our protoboard design. This is an interesting idea, but I suspect that if we use the through-hole footprint for the ATMEGA and shift register and EEPROM, etc we won't have room. But maybe you can use a micro-SD footprint? I think we should delay this investigation until the 2nd rev of the board, just to save time on this job. We need to finish before I go to China, which is on the 1st of May!<br />
<br />
I also talked with Mikolaj about the features of the board and he is in agreement that the LiPo battery's have to go. In fact he is switching to other batteries for his belt already, because it's so difficult to charge the LiPos. He likes our compass jack, and our power switch idea.<br />
<br />
Anyway, he's on board with getting a couple of boards from us.</div>Elgreengeeto