Restructured
This commit is contained in:
Executable
+69
@@ -0,0 +1,69 @@
|
||||
### 2024 Policy Proposals
|
||||
|
||||
<em>[Our annual board-member elections are occurring on Tuesday, Mar
|
||||
12](https://www.meetup.com/hac-dc/events/vhhpbtygcfbqb/)!</em>
|
||||
**Update** <em>[New date for annual board-member elections is Tuesday
|
||||
Mar 26](https://www.meetup.com/hac-dc/events/299761507/)</em> - - -
|
||||
|
||||
## Noisebridge Inspirations
|
||||
|
||||
Suggested by Callie Composed by Gabriel
|
||||
|
||||
Noisebridge has a lot of good material on their wiki about community
|
||||
standards. We have an [Anti-Harassment
|
||||
Policy](Anti-Harassment_Policy "wikilink"), but we could have a lot more
|
||||
clarity around expected conduct at the space. Here are some policies I'd
|
||||
like to highlight for consideration at HacDC,
|
||||
|
||||
- ([Conflict
|
||||
Resolution](https://www.noisebridge.net/wiki/Conflict_Resolution))
|
||||
|
||||
1. Start by being
|
||||
[Excellent](https://www.noisebridge.net/wiki/Excellence) to each
|
||||
other
|
||||
2. Try to resolve potential conflicts that arise using [Restorative
|
||||
Communication](https://www.noisebridge.net/wiki/Restorative_Communication)
|
||||
3. [Ask To
|
||||
Disengage](https://www.noisebridge.net/wiki/Ask_To_Disengage) to
|
||||
separate people in an argument that is escalating.
|
||||
4. [Ask to leave](https://www.noisebridge.net/wiki/AskToLeave) if
|
||||
someone refuses to disengage or is doing something that makes people
|
||||
feel unsafe.
|
||||
5. [Ask for Mediation](https://www.noisebridge.net/wiki/Mediation) if
|
||||
you don't seem to be able to resolve issues with someone in the
|
||||
space directly.
|
||||
|
||||
- ([No_sleeping_at_Noisebridge](https://www.noisebridge.net/wiki/No_sleeping_at_Noisebridge))
|
||||
You can hack at HacDC as late as you want, but you can not sleep here.
|
||||
|
||||
## Open Hac Nights
|
||||
|
||||
We have a popular open hac night on Mondays. The official hours are from
|
||||
7-9. I think we need to make it clear that hosts of this meeting are
|
||||
free to ask visitors to leave at 9 if no other members are going to be
|
||||
present. IF there are members who want to continue to host guests past 9
|
||||
then it is their responsibility to supervise and clean up after those
|
||||
guests.
|
||||
|
||||
## Permission Required on Recordings
|
||||
|
||||
Proposed/composed by: Callie
|
||||
|
||||
No one shall record media, or share media recorded, in our space, such
|
||||
as includes images of someone else, or original ideas, sayings, or
|
||||
products of labor made by someone else, unless such are agreed upon:
|
||||
|
||||
- scope of use or publication
|
||||
- branding or labeling conditions, including the original producer's
|
||||
name
|
||||
- a simple erasure procedure
|
||||
|
||||
\- - -
|
||||
|
||||
## Non Aggression
|
||||
|
||||
Proposed by: Sven Composed by: Callie
|
||||
|
||||
In case anyone using our space engages in, or displays aggression in
|
||||
body motions, language, or mannerisms, such one shall be compelled from
|
||||
our space, so as remaining members can reclaim secure premises.
|
||||
Executable
+17
@@ -0,0 +1,17 @@
|
||||
## Artificial Intelligence
|
||||
|
||||
### Status: No Longer Taught
|
||||
|
||||
WHERE: HacDC 1525 Newton ST NW Washington D.C. 20010
|
||||
|
||||
WHEN: The first, third and fourth Tuesday of the month starting at
|
||||
7:00pm. WHO: Brad Barr
|
||||
|
||||
HacDC will be hosting a study group for [Stanford's AI
|
||||
class](http://ai-class.org). We'll be helping each other understand the
|
||||
material, talk about the classes lectures, and discussing possible
|
||||
project ideas. The listserv for the AI class can be found
|
||||
[here](http://hacdc.org/cgi-bin/mailman/listinfo/ai-class). More
|
||||
information will appear here when we get it.
|
||||
|
||||
[Category:Classes](Category:Classes "wikilink")
|
||||
Executable
+50
@@ -0,0 +1,50 @@
|
||||
- OSI layer 2 (data link layer) protocol. Technically, it occupies
|
||||
layers 1-3.
|
||||
- Same layer as BATMAN-Advanced.
|
||||
- Used for packet radio by hams.
|
||||
- Can transport network layer protocols, including IP.
|
||||
- Not designed to support switching, though routers can probably be set
|
||||
up to handle it.
|
||||
- Support in the Linux kernel.
|
||||
- v2.6.x: ax25.ko
|
||||
- Commonly used with three different communication specs:
|
||||
- Bell 103 tones @ 300bps
|
||||
- Bell 202 tones @ 1200bps
|
||||
- G3RUH DFSK @ 9600bps
|
||||
- These speeds are hard limits.
|
||||
- KISS encapsulates frames such that they can be send to a TNC for
|
||||
transmission. Derived from SLIP.
|
||||
- KISS is a serial protocol. Thus, multiple serial channels are required
|
||||
for multiple transceivers.
|
||||
- Other protocols fulfill the same function.
|
||||
- Either half or full duplex modes.
|
||||
- Three components
|
||||
- Kernel module
|
||||
- Configuration utilities
|
||||
- Utility software
|
||||
- Each AX.25 network device ("port") must be configured with a unique
|
||||
callsign/SSID. Hostnames are probably not a good idea.
|
||||
- We would be using [soundmodem](Notes_on_Soundmodem "wikilink") on top
|
||||
of AX.25.
|
||||
|
||||
Configuring AX.25 network interface:
|
||||
|
||||
` ifconfig sm0 hw ax25 `<callsign>` up`
|
||||
|
||||
` Create an entry in /etc/ax25/axports for the network interface:`
|
||||
` sm0 `<callsign>` `<speed in bps>` `<maximum packet length>` <AX.25 window parameter (K)> `<description of interface>
|
||||
|
||||
Once this is done, you can treat it like any other network interface:
|
||||
|
||||
` ifconfig sm0 192.168.1.1 netmask 255.255.255.0`
|
||||
` route add -net 192.168.1.0 netmask 255.255.255.0 sm0`
|
||||
` route add default sm0`
|
||||
|
||||
[Using /usr/bin/call to test an AX.25
|
||||
connection.](http://tldp.org/HOWTO/AX25-HOWTO/x1449.html)
|
||||
|
||||
[Wikipedia: AX.25](https://secure.wikimedia.org/wikipedia/en/wiki/AX.25)
|
||||
[About AX.25](http://www.tapr.org/pub_ax25.html) [Linux AX.25
|
||||
Howto](http://tldp.org/HOWTO/AX25-HOWTO/)
|
||||
|
||||
[Category:Byzantium](Category:Byzantium "wikilink")
|
||||
Executable
+55
@@ -0,0 +1,55 @@
|
||||
This is a proposal to create a holiday-themed program for kids, aimed at
|
||||
raising money for and awareness of [the Loaves & Fishes
|
||||
program](http://www.loavesandfishesdc.org/). Saturday night (weekend in
|
||||
December) would be the best time.
|
||||
|
||||
## Proposal Vitals
|
||||
|
||||
**Status**: In Progress, Discussion
|
||||
|
||||
- Project Lead: [Q](User:Q "wikilink")'''
|
||||
- Proposed Budget: \$500.00'''
|
||||
- Goals:
|
||||
- To have a high profile charity event to stimulate HacDC's presence
|
||||
in the community
|
||||
- To boost our 501(c)(3) application
|
||||
- To build relationships within the church
|
||||
|
||||
## Detailed Proposal
|
||||
|
||||
The idea is basically to have the Church transformed into a technology
|
||||
playground for kids of the area, in a very Christmas type fashion. The
|
||||
main things we could have is someone (Nick? hehe) dressed up as Santa
|
||||
sitting on the stage talking with kids, we could have plenty of food for
|
||||
both kids and maybe the homeless (like [the F&L
|
||||
program](http://www.loavesandfishesdc.org/) already does)... The
|
||||
stage/meeting area in the Church could be the kids area and then we
|
||||
could have a separate area for just [the F&L
|
||||
program](http://www.loavesandfishesdc.org/) portion... So with foods and
|
||||
Santa comes the best part and the main reason we would want to be
|
||||
involved...
|
||||
|
||||
We can have little workshops setup throughout the church with little
|
||||
Christmas-type kits where we can teach the kids about technology and
|
||||
creating/MAKEing/building and certainly the reality of developing
|
||||
whatever you dream.
|
||||
|
||||
Ideally, I was thinking the workshops would include things like: NYCR's
|
||||
lazz0r and 3D printing (with some of us helping them design Christmas
|
||||
type objects to build, we need a project to collaborate with them
|
||||
anyway), One of MAKE:DC's awesome little kit builds designed with a
|
||||
Christmas theme for kids (Mark, want to design?), Maybe Elliot can do a
|
||||
micro controller class where they make some type of LED Christmas tree
|
||||
...
|
||||
|
||||
The reality of it is that we would need a whole lot of support and
|
||||
participation from our members and friends of HacDC. This doesn't have
|
||||
to be something amazingly EPIC at first, but if we stay around awhile
|
||||
(even if we do move) we could do this anually. Not only would this help
|
||||
our 501c3 but it's also a great thing to do for our community and for
|
||||
the holidays in general.
|
||||
|
||||
Richard has lots of turkeys and may be able to bring in his old chamber
|
||||
group together for it
|
||||
|
||||
[Category:Proposed Projects](Category:Proposed_Projects "wikilink")
|
||||
Executable
+7
@@ -0,0 +1,7 @@
|
||||
The HacDC Advisory Council is an informal group of people who offer
|
||||
advice to HacDC. The council presently offers advice via a closed,
|
||||
invite-only e-mail list.
|
||||
|
||||
Members on the Advisory Council are typically those who can offer great
|
||||
amounts of support to HacDC, through publicity and financial means, but
|
||||
for time and distance reasons, cannot regularly participate in HacDC.
|
||||
Executable
+118
@@ -0,0 +1,118 @@
|
||||
This is the OpenSCAD code to create a wafer air flow sensor (and
|
||||
backflow preventer) to hold a microswitch to stop the laser from firing
|
||||
if the exhaust flow stops. Dimensions have been set to match the exhaust
|
||||
nozzle. The current version of the header doesn't quite match, even
|
||||
though the nozzle was reverse engineered from it.
|
||||
|
||||
This was printed on 5/1 and it has some issues.
|
||||
|
||||
1. The arms which hold the switch body interfere with the flap plate.
|
||||
2. The flap plate axis of rotation could be lowered to improve the
|
||||
balance.
|
||||
3. The thickness of the wafer can be increased to reduce the warpage of
|
||||
the piece.
|
||||
|
||||
Model was redesigned on 5/5:
|
||||
|
||||
1. Switch holder moved to side from top center
|
||||
2. Flap axis of rotation lowered
|
||||
3. Up arrow added
|
||||
4. Thickness increased from 3 to 5 mm
|
||||
5. Wire holes relocated 180??
|
||||
|
||||
You can find the stl file here
|
||||
|
||||
|
||||
<nowiki>
|
||||
/*
|
||||
exhaust airflow detector
|
||||
safety interlock for cheap Chinese laser at Hac DC
|
||||
This switch is a lug style wafer for insertion between the exhaust collector and the exhaust nozzle on the back of the laser chassis.
|
||||
When the exhaust fan is running and air is flowing the switch will operate to allow the laser to fire. This switch is upstream of
|
||||
the exhaust fan so air will leak into the exhaust stream, not exhaust leaking out into room air.
|
||||
James Sullivan
|
||||
5-5-17, v2
|
||||
OpenSCAD version 2015.03-1
|
||||
|
||||
--dimensions from mating exhaust nozzle--
|
||||
nid=60; //nozzle inner diameter
|
||||
nod=80; //nozzle outer diameter
|
||||
mod=100; //maximum outer diameter
|
||||
sh=30; //step height
|
||||
sw=5; //step width
|
||||
oah=50; //over-all height
|
||||
tlw=3; //top ledge width
|
||||
bcd=46.8*2; //bolt circle diameter
|
||||
bhd=3.6; //bolt hole diameter
|
||||
fw=12; //foot width
|
||||
fh=15; //foot height
|
||||
fod=108; //foot outside dimension, from outside edge to outside edge
|
||||
fid=(nid+nod)/2;//foot inside dimension, from inside edge to inside edge
|
||||
*/
|
||||
fid=60; //flange inner diameter, same as nid
|
||||
fod=80; //flange outer diameter, same as nod
|
||||
bhd=3.6; //bolt hole diameter
|
||||
bcd=93.6;//bolt circle diameter
|
||||
thick=5; //thickness of flange - originally 3, but warped when removing from printer bed
|
||||
flap=3; //thickness of flap - originally 3, but warped when removing from printer bed
|
||||
hph=bhd*2; //hinge pin height above center line, i.e. butterfly offset. Reduce to make switch more sensitive. Increse to make switch more stable. - originally 10
|
||||
sfw=fid-thick*2; //switch flap width - originally sqrt(fid*fid-4*hph*hph)
|
||||
shd=2; //switch hole diameter
|
||||
shp=10; //switch hole pitch, i.e. center to center spacing of mounting holes on microswitch
|
||||
srh=12; //switch roller height, i.e. height above switch hole centerline where switching action occurs
|
||||
sbw=6; //switch body width
|
||||
nfw=5; //nut face width
|
||||
nt=1; //nut thickness
|
||||
$fn=80;
|
||||
|
||||
difference(){ //wafer body
|
||||
union(){
|
||||
cylinder(d=fod,h=thick);
|
||||
for(ang=[0,90]){
|
||||
rotate([0,0,ang]) hull(){ //lugs
|
||||
translate([bcd/2,0,0]) cylinder(d=3*bhd, h=thick);
|
||||
translate([-bcd/2,0,0]) cylinder(d=3*bhd, h=thick);
|
||||
}
|
||||
}
|
||||
translate([sfw/2+thick/2,0,thick]) rotate([-90,0,0]) cylinder(d1=shd*1.6,d2=0,h=shd*2);//up direction arrow head
|
||||
translate([sfw/2+thick/2,0,thick]) rotate([90,0,0]) cylinder(d=shd*0.8,h=shd*2); //up direction arrow shaft
|
||||
}
|
||||
translate([0,0,-thick/2]) intersection(){ //bore
|
||||
cylinder(d=fid, h=2*thick); //circular top and bottom
|
||||
cube([sfw,fod,thick*4],true); //vertical left and right
|
||||
}
|
||||
for (angle=[0:90:270]){ //bolt holes in lugs
|
||||
rotate([0,0,angle]) translate([bcd/2,0,-thick/2]) cylinder(d=bhd,h=thick*2);
|
||||
}
|
||||
for (angle=[235:5:245]){ //wire holes through flange
|
||||
translate([0,0,thick-flap/2]) rotate([0,90,angle]) cylinder(d=1,h=bcd/2);
|
||||
}
|
||||
translate([0,hph,flap/2]) rotate([0,90,0]) cylinder(d=1,h=bcd+4*bhd,center=true); //hinge pin axle hole
|
||||
} //end of wafer body
|
||||
translate([-thick/2-sfw/2,0,flap/2+srh]){ //switch holder
|
||||
difference(){
|
||||
union(){
|
||||
cube([thick,shp+3*shd,3*shd],center=true);//mount flange
|
||||
color("blue") translate([0,0,-srh/2-flap/4+thick/2-3*shd/4]) cube([thick,shp+3*shd,srh+flap/2-thick-3*shd/2],center=true); //support for mount flange
|
||||
translate([-thick/2,0,-shd*2]) cylinder(d2=shd*1.6,d1=0,h=shd*2.0);//flow direction arrow head
|
||||
translate([-thick/2,0,-shd/2]) cylinder(d=shd*0.8,h=shd*2.0); //flow direction arrow shaft
|
||||
}
|
||||
for (dy=[-shp/2,shp/2]) {
|
||||
translate([0,dy,0]) rotate([0,90,0]) cylinder(d=shd,h=2*thick,center=true); //bolt holes
|
||||
for (angle=[0:120:240]){
|
||||
translate([-thick/2,dy,0]) rotate([angle,0,0]) cube([nt*2,nfw,nfw/sqrt(3)],center=true); //nut sockets
|
||||
}
|
||||
}
|
||||
}
|
||||
}
|
||||
|
||||
translate([0,fid/2+bcd/2+bhd*2,0]) difference(){ //flap disk
|
||||
intersection(){ //bore
|
||||
cylinder(d=fid-0.5, h=flap); //circular top and bottom
|
||||
cube([sfw-0.5,fod,flap*2],true); //vertical left and right
|
||||
}
|
||||
translate([0,hph,flap/2]) rotate([0,90,0]) cylinder(d=1,h=bcd+4*bhd,center=true); //hinge pin axis
|
||||
}
|
||||
</nowiki>
|
||||
|
||||
[Category: CheapChineseLaser](Category:_CheapChineseLaser "wikilink")
|
||||
Executable
+217
@@ -0,0 +1,217 @@
|
||||
# Functions
|
||||
|
||||
albert is an infrastructural VM host and nothing else.
|
||||
|
||||
# Access
|
||||
|
||||
Admin access only. Email support@hacdc.org if you need to report an
|
||||
issue.
|
||||
|
||||
# Admin Notes
|
||||
|
||||
## Case
|
||||
|
||||
- 3U 19 inch rackmount
|
||||
|
||||
### PSU
|
||||
|
||||
- ATX PSU with both 4 and 8 pin cpu power connectors
|
||||
- Wattage:
|
||||
|
||||
### Slots
|
||||
|
||||
- 7 stock 3.5 inch hot swap slots
|
||||
- 1 front, floppy slot
|
||||
- 1 front, 5.25 inch slot
|
||||
- 2 internal front 3.5 inch slots
|
||||
- 2 3.5 inch slots on spreader bar
|
||||
|
||||
### Addon Cards
|
||||
|
||||
- RAID/SATA controller
|
||||
- ports
|
||||
- model
|
||||
- GPU see [Server_Albert#GPU](Server_Albert#GPU "wikilink")
|
||||
|
||||
## Mother Board
|
||||
|
||||
### RAM
|
||||
|
||||
- 4GB DDR2 ECC
|
||||
|
||||
### CPU
|
||||
|
||||
- dual socket dual core Xeon
|
||||
- has VM extensions
|
||||
- no hyper-threading
|
||||
- /proc/cpuinfo
|
||||
|
||||
` processor : 0`
|
||||
` vendor_id : GenuineIntel`
|
||||
` cpu family : 6`
|
||||
` model : 15`
|
||||
` model name : Intel(R) Xeon(R) CPU 5140 @ 2.33GHz`
|
||||
` stepping : 6`
|
||||
` microcode : 0x44`
|
||||
` cpu MHz : 2333.448`
|
||||
` cache size : 4096 KB`
|
||||
` fpu : yes`
|
||||
` fpu_exception : yes`
|
||||
` cpuid level : 10`
|
||||
` wp : yes`
|
||||
` flags : fpu de tsc msr pae cx8 apic sep cmov pat clflush acpi mmx fxsr sse sse2 ss ht syscall nx lm constant_tsc rep_good nopl pni est ssse3 cx16 hypervisor lahf_lm dtherm`
|
||||
` bogomips : 4666.89`
|
||||
` clflush size : 64`
|
||||
` cache_alignment : 64`
|
||||
` address sizes : 36 bits physical, 48 bits virtual`
|
||||
` power management:`
|
||||
` `
|
||||
` processor : 1`
|
||||
` vendor_id : GenuineIntel`
|
||||
` cpu family : 6`
|
||||
` model : 15`
|
||||
` model name : Intel(R) Xeon(R) CPU 5140 @ 2.33GHz`
|
||||
` stepping : 6`
|
||||
` microcode : 0x44`
|
||||
` cpu MHz : 2333.448`
|
||||
` cache size : 4096 KB`
|
||||
` fpu : yes`
|
||||
` fpu_exception : yes`
|
||||
` cpuid level : 10`
|
||||
` wp : yes`
|
||||
` flags : fpu de tsc msr pae cx8 apic sep cmov pat clflush acpi mmx fxsr sse sse2 ss ht syscall nx lm constant_tsc rep_good nopl pni est ssse3 cx16 hypervisor lahf_lm dtherm`
|
||||
` bogomips : 4666.89`
|
||||
` clflush size : 64`
|
||||
` cache_alignment : 64`
|
||||
` address sizes : 36 bits physical, 48 bits virtual`
|
||||
` power management:`
|
||||
` `
|
||||
` processor : 2`
|
||||
` vendor_id : GenuineIntel`
|
||||
` cpu family : 6`
|
||||
` model : 15`
|
||||
` model name : Intel(R) Xeon(R) CPU 5140 @ 2.33GHz`
|
||||
` stepping : 6`
|
||||
` microcode : 0x44`
|
||||
` cpu MHz : 2333.448`
|
||||
` cache size : 4096 KB`
|
||||
` fpu : yes`
|
||||
` fpu_exception : yes`
|
||||
` cpuid level : 10`
|
||||
` wp : yes`
|
||||
` flags : fpu de tsc msr pae cx8 apic sep cmov pat clflush acpi mmx fxsr sse sse2 ss ht syscall nx lm constant_tsc rep_good nopl pni est ssse3 cx16 hypervisor lahf_lm dtherm`
|
||||
` bogomips : 4666.89`
|
||||
` clflush size : 64`
|
||||
` cache_alignment : 64`
|
||||
` address sizes : 36 bits physical, 48 bits virtual`
|
||||
` power management:`
|
||||
` `
|
||||
` processor : 3`
|
||||
` vendor_id : GenuineIntel`
|
||||
` cpu family : 6`
|
||||
` model : 15`
|
||||
` model name : Intel(R) Xeon(R) CPU 5140 @ 2.33GHz`
|
||||
` stepping : 6`
|
||||
` microcode : 0x44`
|
||||
` cpu MHz : 2333.448`
|
||||
` cache size : 4096 KB`
|
||||
` fpu : yes`
|
||||
` fpu_exception : yes`
|
||||
` cpuid level : 10`
|
||||
` wp : yes`
|
||||
` flags : fpu de tsc msr pae cx8 apic sep cmov pat clflush acpi mmx fxsr sse sse2 ss ht syscall nx lm constant_tsc rep_good nopl pni est ssse3 cx16 hypervisor lahf_lm dtherm`
|
||||
` bogomips : 4666.89`
|
||||
` clflush size : 64`
|
||||
` cache_alignment : 64`
|
||||
` address sizes : 36 bits physical, 48 bits virtual`
|
||||
` power management:`
|
||||
|
||||
### GPU
|
||||
|
||||
- NVIDIA Corporation NV43 \[GeForce 6600\] (rev a2)
|
||||
|
||||
### BIOS/UEFI
|
||||
|
||||
- Make - ?
|
||||
- Version - ?
|
||||
|
||||
#### Menu
|
||||
|
||||
- ?Setup
|
||||
- ?View Post
|
||||
- ?Boot Select
|
||||
|
||||
## OS
|
||||
|
||||
- Debian
|
||||
- Version - stable
|
||||
- Arch - amd64
|
||||
|
||||
# OS Config
|
||||
|
||||
## DomU
|
||||
|
||||
- Shell server - tortoise
|
||||
- File server - hoard
|
||||
- Squid Proxy - cthulhu
|
||||
|
||||
## Storage
|
||||
|
||||
- Partitions \#FIXME
|
||||
- All drives have stripe for /boot
|
||||
- 1TB drives
|
||||
- 500GB drives
|
||||
- 250GB drives
|
||||
- Soft RAID \# FIXME
|
||||
- the /boot stripe is RAID1
|
||||
- 250GB drives
|
||||
- 500GB drives
|
||||
- 1TB drives
|
||||
|
||||
### LVM
|
||||
|
||||
- Volume Groups
|
||||
- albert
|
||||
- home
|
||||
- /home
|
||||
- root
|
||||
- /
|
||||
- swap
|
||||
- Contiguous LV.
|
||||
- nas
|
||||
- Attached to hoad.
|
||||
- Shell users' /home/users/\*
|
||||
- Generic storage.
|
||||
- proxy
|
||||
- Attached to cthulhu.
|
||||
- Contains the cache from the proxies.
|
||||
- cthulhu-disk - 4GB
|
||||
- cthulhu-swap - 1GB
|
||||
- hoard-disk - 4GB
|
||||
- hoard-swap - 128MB
|
||||
- tortoise-disk - 4GB
|
||||
- tortoise-home - 50GB (will be reduced)
|
||||
- tortoise-swap - 128MB
|
||||
- tortoise-tmp - 10GB
|
||||
- tortoise-var - 30GB
|
||||
- template.debian-testing-minimal - 4GB
|
||||
- to be removed
|
||||
- template-swap
|
||||
- vms
|
||||
|
||||
## Software
|
||||
|
||||
#### Xen HVM
|
||||
|
||||
- domain configs /etc/xen/conf
|
||||
- configs tracked with git
|
||||
- use /etc/xen/conf/.commit to commit changes as nonroot user
|
||||
|
||||
## VMs
|
||||
|
||||
- [cthulhu](cthulhu "wikilink") - proxy server
|
||||
- [tortoise](tortoise "wikilink") - shell server
|
||||
- [hoard](hoard "wikilink") - file server
|
||||
|
||||
[Category:Infrastructure](Category:Infrastructure "wikilink")
|
||||
[Category:Servers](Category:Servers "wikilink")
|
||||
Executable
+4
@@ -0,0 +1,4 @@
|
||||
Andaman Honeymoons Ltd brings an opportunity to spend honeymoon at the
|
||||
romantic and serene archipelago situated in the Bay of Bengal. They have
|
||||
different types of [Andaman honeymoon
|
||||
package](http://andamanhoneymoons.com/)s available at different budgets.
|
||||
Executable
+100
@@ -0,0 +1,100 @@
|
||||
"Central Services" is the internal reference for all members who serve
|
||||
in some leadership or official function at HacDC...
|
||||
|
||||
## Disorganization Chart
|
||||
|
||||
| The Will of the Membership (Directly Elected Positions) |
|
||||
|---------------------------------------------------------|
|
||||
| The [Board of Directors](Board_of_Directors "wikilink") |
|
||||
| [The Ministers](The_Ministers "wikilink") |
|
||||
| [Coordinator in Chief](Coordinator_in_Chief "wikilink") |
|
||||
| |
|
||||
|
||||
<table>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th><p>Central Services (i.e. HacDC Organizational
|
||||
Administration)</p></th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td><p><a href="Coordinator_in_Chief" title="wikilink">Coordinator in
|
||||
Chief</a></p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td><p>Appointed by the <a href="Coordinator_in_Chief"
|
||||
title="wikilink">Coordinator in Chief</a>:</p>
|
||||
<ul>
|
||||
<li>Shadow Coordinator in Chief</li>
|
||||
<li>Sergeant-at-Arms (Physical Security)</li>
|
||||
<li>(Member who handles Public Relations)</li>
|
||||
</ul></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td><p><em>Note: These are presently all proposed positions and are, if
|
||||
the draft policy below is adopted, subject to discretion of the relevant
|
||||
minister as well as full-member review. (Review means the membership can
|
||||
change it if they don't like it, but they don't have to approve it in
|
||||
advance)</em></p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
## The [Board of Directors](Board_of_Directors "wikilink") (Set by Bylaws)
|
||||
|
||||
The [Board of Directors](Board_of_Directors "wikilink"), per our
|
||||
[Bylaws](Bylaws "wikilink") consists of [the
|
||||
Ministers](the_Ministers "wikilink") and two At-Large Directors. The
|
||||
[Board of Directors](Board_of_Directors "wikilink") at HacDC is largely
|
||||
ceremonial. Members generally directly decide on all issues before
|
||||
HacDC. Only certain minutiae and other actions required by law are
|
||||
carried out by the [Board of Directors](Board_of_Directors "wikilink").
|
||||
|
||||
Despite direct membership control wherever possible, the [Board of
|
||||
Directors](Board_of_Directors "wikilink") remains primarily responsible
|
||||
for the affairs of HacDC under District of Columbia Corporate Law.
|
||||
|
||||
### [The Ministers](The_Ministers "wikilink")
|
||||
|
||||
Most corporate law refers to "officers". [The
|
||||
Ministers](The_Ministers "wikilink") are our Corporate Officers and
|
||||
serve in the following roles:
|
||||
|
||||
- [Coordinator in Chief](Coordinator_in_Chief "wikilink") = President
|
||||
and Chairman of the [Board of
|
||||
Directors](Board_of_Directors "wikilink")
|
||||
- [Minister of Information](Minister_of_Information "wikilink") =
|
||||
Executive Vice President and Vice Chairman of the [Board of
|
||||
Directors](Board_of_Directors "wikilink") (and Chief Information
|
||||
Officer)
|
||||
- [Keeper of the MIBS](Keeper_of_the_MIBS "wikilink") = Secretary
|
||||
- [Minister of Finance](Minister_of_Finance "wikilink") = Treasurer
|
||||
|
||||
### At Large Directors
|
||||
|
||||
The At Large Directors are the membership's direct representation on the
|
||||
[Board of Directors](Board_of_Directors "wikilink"). At Large Directors
|
||||
should be regular members who are not involved with the day-to-day
|
||||
running of HacDC. They are there to offer advice and perspective to [the
|
||||
Ministers](the_Ministers "wikilink") and act as a form of internal
|
||||
control.
|
||||
|
||||
## Current [Board of Directors](Board_of_Directors "wikilink")
|
||||
|
||||
Prior board of directors.
|
||||
|
||||
| Title | Name |
|
||||
|---------------------------------------------------|----------------------------------------|
|
||||
| [President](President "wikilink") | [Bradford Barr](User:Bbarr "wikilink") |
|
||||
| [Vice President](Vice_President "wikilink") | [Ben Mendis](User:Sitwon "wikilink") |
|
||||
| [Secretary](Secretary "wikilink") | [Eric Miller](User:Eric "wikilink") |
|
||||
| [Treasurer](Treasurer "wikilink") | [Tim Slagle](User:Tslagle "wikilink") |
|
||||
| [At Large Director](At_Large_Director "wikilink") | Martin Rothfield |
|
||||
| [At Large Director](At_Large_Director "wikilink") | [Nick Stoler](User:NickS "wikilink") |
|
||||
| | |
|
||||
|
||||
[Category:BOD](Category:BOD "wikilink")
|
||||
Executable
+141
@@ -0,0 +1,141 @@
|
||||
This is the "instruction manual" for the Area science event list
|
||||
(wiki.hacdc.org/index.php/Area_science_event_list). This is an
|
||||
incomplete list of science events (talks and science fairs; generally
|
||||
excluding book, article, or movie discussions, workshops, and events
|
||||
focused on finance rather than science) in the Washington area and at
|
||||
the STScI and BUGSS in Baltimore. Only free events are listed but
|
||||
registration, a free ticket, or other advance arrangements may be
|
||||
required (noted when known). Normal times and locations for events are
|
||||
given below but note that there may be exceptions. In-person events
|
||||
where the speaker is virtual are included. Warning: All events are
|
||||
subject to change with no warning. Send additions, corrections,
|
||||
comments, etc. to: gippgig@gmail.com CI=Carnegie Institute -
|
||||
carnegiescience.edu/public-events - Capital Science Evenings - 6:30PM
|
||||
MLK Library (901 G St. NW Washington, D.C. 20001) (registration) NLS -
|
||||
6:30PM Broad Branch Road Campus (5251 Broad Branch Rd. NW Washington,
|
||||
D.C. 20015) (registration recommended) DASER=DC Art Science Evening
|
||||
Rendezvous - www.cpnas.org/events/upcoming-events.html - 6PM
|
||||
(registration and photo ID required) DCSC=D.C. Science Cafe -
|
||||
dcswa.org/dc-science-cafe/ - 6:30PM Busboys and Poets (1025 5th St. NW
|
||||
(5th & K St.) Washington, D.C. 20001 (202)789-BBAP HacDC - www.hacdc.org
|
||||
(202)556-4225 - 7:30PM St. Stephen & the Incarnation Episcopal Church
|
||||
2nd floor (1525 Newton St. NW Washington, D.C. 20010) LDPL=The Labs at
|
||||
DC Public Library - www.dclibrary.org/labsatdcpl LFV=Little Falls
|
||||
Village -
|
||||
www.littlefallsvillage.org/content.aspx?page_id=4001&club_id=560791
|
||||
(301) 320-3267 - 1:30PM Little Falls Library MCPL=Montgomery County
|
||||
Public Libraries - www.montgomerycountymd.gov/library/ NAS=National
|
||||
Academy of Sciences - www.nationalacademies.org/events NCAS=National
|
||||
Capital Area Skeptics - www.ncas.org (240)670-NCAS - 1:30PM
|
||||
PSW=Philosophical Society of Washington - www.philsoc.org/ - 8PM John
|
||||
Wesley Powell Auditorium (left of Cosmos Club 2170 Florida Ave. NW
|
||||
Washington, D.C. 20008) RSC=Rockville Science Center -
|
||||
www.rockvillesciencecenter.org, (240)FUN-8111 (RSC=Rockville Science
|
||||
Cafe - 3rd Tue. 7PM ST=Science Tuesdays \*YASC=Young Adult Science Cafe
|
||||
Rockville Science Day - April noon Montgomery College (51 Mannakee St.
|
||||
Rockville, Md. 20850)) TBC=The Bowen Center for the Study of the
|
||||
Family - thebowencenter.org - 4400 MacArthur Boulevard, NW Suite 103,
|
||||
Washington, DC 20007-2521 Biology BUGSS=Baltimore Under Ground Science
|
||||
Space - www.bugssonline.org/ - (410)732-0947 (101 N. Haven St. Suite 105
|
||||
Baltimore, Md. 21224) CASSS - www.casss.org/meetings-and-events
|
||||
(biotech) HHMI=Howard Hughes Medical Institute -
|
||||
www.janelia.org/you-janelia/dialogues-discovery - Janelia Research
|
||||
Campus (19700 Helix Dr. Ashburn, Va. 20147 (571)209-4000) (ticket
|
||||
required) IBBR=Institute for Bioscience & Biotechnology Research
|
||||
(UMd.) - www.ibbr.umd.edu/events/upcoming-events SCBI=Smithsonian
|
||||
Conservation Biology Institute (National Zoo) -
|
||||
nationalzoo.si.edu/conservation/scbi-rock-creek-park-seminars
|
||||
UMdBpS=Univ. of Md. Biophysics Seminars -
|
||||
marylandbiophysics.umd.edu/seminars/ (301)405-9307 - Mon. 4PM IPST 1116
|
||||
UMdBS=Univ. of Md. biology seminars (also see IBBR) -
|
||||
www.bisi.umd.edu/events-3/ (301)405-6905 (ANSC=Animal & Avian Science
|
||||
Seminar BBS=BISI-BEES Seminar BCBMS=BISI-CBBG and BISI-MOCB Seminar
|
||||
BCS=BISI-CBBG Seminar BEES=Behaviour, Ecology, Evolution and Systematics
|
||||
CBBG=Computational Biology, Bioinformatics, and Genomics CBCB=Center for
|
||||
Bioinformatics and Computational Biology CBG=Computational Biology and
|
||||
Genomics CBMG=Cell Biology and Molecular Genetics CSC=Cognitive Science
|
||||
Colloquium EC=Entomology Colloquium EG=Evo-Gen Seminar ENTM=Entomology
|
||||
Seminar MOCB=Molecular and Cellular Biology PSL=Plant Science Lecture
|
||||
RIP=Research in Progress VM=VetMed Seminar) Chemistry UMdCS=Univ. of Md.
|
||||
chemistry seminar - www.chem.umd.edu/whats-new/calendar (301)405-1788
|
||||
(SS=Student Seminar) CSW=Chemical Society of Washington -
|
||||
capitalchemist.org/category/csw-events/ Engineering UMdEgS=University of
|
||||
Md. engineering seminar (FDR=Fluid Dynamics Reviews -
|
||||
enme.umd.edu/events/fluid-dynamics-seminar-series MES=Mechanical
|
||||
Engineering - enme.umd.edu/events/seminars MNC=Maryland NanoCenter -
|
||||
www.nanocenter.umd.edu/events CBmE=Chemical and Biomolecular
|
||||
Engineering - chbe.umd.edu/seminar-series Be=Bioengineering -
|
||||
bioe.umd.edu/events/seminars) WBMSDG=Washington-Baltimore Mass
|
||||
Spectrometry Discussion Group - wbmsdg.org/ Environment-Geology
|
||||
GLMSMC=Gem, Lapidary, and Mineral Society of Montgomery County, MD.,
|
||||
Inc. - www.glmsmc.com/ - 7:30PM 2nd Monday Rockville Senior Center (1150
|
||||
Carnation Dr. Rockville, Md.) GSW=The Geological Society of Washington -
|
||||
www.gswweb.org UMdES=Univ. of Md. environment seminar -
|
||||
aosc.umd.edu/seminars (301)405-5391 (ACBBT=Atmospheric Chemistry Brown
|
||||
Bag Talk - Friday CSS 3400, DS=AOSC Departmental Seminar - Thursday
|
||||
3:30PM CSS 2400, ESSIC=Earth System Science Interdisciplinary Center
|
||||
Seminar - Monday noon M-Square 4102, SS=AOSC Student Seminar - Tuesday
|
||||
3:30PM CSS 3400) UMdGcS=Univ. of Md. Geochemistry Seminars -
|
||||
www.geol.umd.edu/department/geochemseminar.php - Wed. 11AM CHEM 0215
|
||||
UMdGS=Univ. of Md. Geology Seminars -
|
||||
www.geol.umd.edu/department/seminar.php (301)405-4082 geology@umd.edu -
|
||||
Fri. 3PM PLS 1140 GMUES=George Mason University environment seminar -
|
||||
science.gmu.edu/academics/departments-units/atmospheric-oceanic-earth-sciences/aoes-seminars
|
||||
PtSW=Paleontological Society of Washington -
|
||||
nmnh.typepad.com/paleontological_society/ - 3rd Wed. 7PM National Museum
|
||||
of Natural History room E-304 Math DCAPS=DC-Area Anonymity, Privacy, and
|
||||
Security Seminar - dcaps.info/ MAA=Mathematical Society of America -
|
||||
www.maa.org/meetings/calendar-events - Carriage House (1781 Church St.
|
||||
NW Washington, D.C. 20036 (202)319-8476) (registration) UMdCSS= Univ. of
|
||||
Md. computer science - www.cs.umd.edu/events & talks.cs.umd.edu/
|
||||
(301)405-2662 (CAT=Capital Area Theory Seminar CLIP=Computational
|
||||
Linguistics and Information Processing HCIL=Human-Computer Interaction
|
||||
Lab QuICS=Joint Center for Quantum Information and Computer Science
|
||||
Seminar) UMdMS=Univ. of Md. Math Seminars -
|
||||
www-math.umd.edu/research/seminars (301)405-4190 (ANT=Algebra-Number
|
||||
Theory D=Dynamics GT=Geometry-Topology LGRT=Lie Groups and
|
||||
Representation Theory NA=Numerical Analysis) Misc. TOOOL-DC=The Open
|
||||
Organization of Lockpickers - toool.us/meetings.html - 1st Wed. The
|
||||
Board Room (1737 Conn. Ave. NW Washington, D.C.) Physics APS=American
|
||||
Physical Society - www.aps.org/units/maspg/meetings/ - 3rd Wed. 1PM
|
||||
American Center for Physics (1 Physics Ellipse College Park, Md. 20740
|
||||
(301)209-3000) UMdPS=Univ. of Md. physics seminars -
|
||||
umdphysics.umd.edu/events (301)405-3401 (AD=Applied Dynamics Seminar
|
||||
CNAM=Center for Nanophysics and Advanced Materials CMTC=Condensed Matter
|
||||
Theory Center DSTL=Distinguished Scholar-Teacher Lecture
|
||||
GP=Gravitational Physics Seminar HEP=High Energy Physics ISP=Informal
|
||||
Statistical Physics JQCS=JQI-QuICS-CMTC Seminar JQI=Joint Quantum
|
||||
Institute LPS=Laboratory for Physical Sciences MSES=MSE Seminar
|
||||
NP=Nuclear Physics Seminar NT=Nuclear Theory Seminar
|
||||
PACP=Phys/ANE/ChemPhys Joint Seminar PP=Plasma Physics Seminar QuICS-see
|
||||
UMdCSS SP=Space Physics Seminar) Space UMdObs=Univ. of Md. Observatory
|
||||
open houses - www.astro.umd.edu/openhouse/ - (301)405-6555 - 5th & 20th
|
||||
8PM (Nov.-April) or 9PM (May-Oct.) (Metzerott Rd.) NCA=National Capital
|
||||
Astronomers - capitalastronomers.org/ - 2nd Sat. 7:30PM UMd. Observatory
|
||||
(Metzerott Rd.) NoVAC=Northern Virginia Astronomy Club - www.novac.com -
|
||||
2nd Sun. 7PM GMU Exploratory Hall Room 3301 GMUObs=George Mason Univ.
|
||||
Observatory - physics.gmu.edu/~hgeller/observing.html - Research Hall
|
||||
TPS=The Planetary Society - Jack.Kiraly@planetary.org
|
||||
ISUSC=International Space University Space Cafe - www.isuspacecafe.org
|
||||
ASG=Astronomical Society of Greenbelt -
|
||||
www.greenbeltastro.org/events.shtml - last Thur. 7:30PM HAL=Howard
|
||||
Astronomical League - www.howardastro.org/meetings.php - 3rd Thur. 7PM
|
||||
Robinson Nature Center downstairs (6692 Cedar La. Columbia, Md. 21044
|
||||
(410)313-0400) NASM=National Air & Space Museum -
|
||||
airandspace.si.edu/visit/events (202)633-1000 (WNIA?=What's New in
|
||||
Aerospace?) Goddard Space Flight Center Scientific Colloquium -
|
||||
scicolloq.gsfc.nasa.gov/ (restricted access; not included in list)
|
||||
STScI=Space Telescope Science Institute -
|
||||
hubblesite.org/about_us/public_talks/ - 1st Tue. 8PM (3700 San Martin
|
||||
Dr. Baltimore, Md. 21218 (410)338-4700 UMdSS=UMd. space seminar -
|
||||
www.astro.umd.edu/ & space.umd.edu/seminars/ (301)405-3001 (AC=Astronomy
|
||||
Colloquia - Wed. 4:05PM CSS 2400 BANG=Better Astronomy for a New
|
||||
Generation - Thur. 4PM PSC 1136 CTC=CTC Theory Lunch - Mon. 11AM PSC
|
||||
1136 LCS=LMA/CARMA Seminar - 3PM PSC 2136 PAL=Planetary Astronomy
|
||||
Late-afternoon Seminar - Mon. 2PM SCRP=Space and Cosmic Ray Physics
|
||||
Seminar - Mon. 4:30PM CSS 2400) Weather AMS=American Meteorological
|
||||
Society - www.ametsoc.org/chapters/washingtondc/Events.html
|
||||
NOAA=National Oceanic and Atmospheric Administration -
|
||||
www.nodc.noaa.gov/seminars/ - (1305 East-West Hwy. Silver Spring, Md.
|
||||
20910 & 5830 University Research Ct. College Park, Md. 20740) (possible
|
||||
nuisance security; may require advance notice)
|
||||
Executable
+5
@@ -0,0 +1,5 @@
|
||||
May 17 8PM PSW - Resurrecting the Unrecoverable Reading the Herculaneum
|
||||
Papyri using X-ray CT and AI 31 8PM PSW - Fukushima Health Effects June
|
||||
8 7:30PM NCA - Science Fair Winners 14 8PM PSW - Returning Humans to the
|
||||
Moon How the United States Can Actually Get There Instead of Watching
|
||||
China Do It 26 3PM NAS - The State of the Science Address (registration)
|
||||
Executable
+12
@@ -0,0 +1,12 @@
|
||||
Automatic [Pad Submitter](http://software.seosniper.net) with Online
|
||||
Free Software Submission Service for your [software
|
||||
promotion](http://software.seosniper.net) from seosniper [Pad
|
||||
Submission](http://software.seosniper.net). Free User can Submit to 25
|
||||
Software Download Sites. From Pro Member You can Submit to 150 Software
|
||||
Download sites, and RegNow/ShartIT/Plimus Software Submission, and your
|
||||
pad submission will submit 100 Articles/100 Wikis/200 Directories/100
|
||||
SocialBookmarks/500 BlogComments Submission also.From Ulimate Member You
|
||||
can Submit to 300 Software Download sites, and RegNow/ShartIT/Plimus
|
||||
Software Submission, and your pad submission will submit 500
|
||||
Articles/500 Wikis/500 Directories/500 SocialBookmarks/3000 BlogComments
|
||||
Submission also.
|
||||
Executable
+72
@@ -0,0 +1,72 @@
|
||||
## Compile and install BATMAN-Advanced
|
||||
|
||||
Download batman-adv and batctl. Standard "make && sudo make install".
|
||||
|
||||
If no interface "wlan0" exists, check for a different wireless interface
|
||||
using 'ifconfig -a'
|
||||
|
||||
## Setup ad-Hoc network
|
||||
|
||||
1. Disable NetworkManager
|
||||
1. Right-click on NetworkManager applet, un-check "Enable
|
||||
networking".
|
||||
2. Fedora:
|
||||
# /etc/init.d/NetworkManager stop
|
||||
3. Ubuntu:
|
||||
# stop network-manager
|
||||
|
||||
2. Disable the firewall
|
||||
1. # iptables -F
|
||||
|
||||
3. # ifconfig wlan0 down
|
||||
|
||||
4. # iwconfig wlan0 mode ad-hoc essid hacdc-batman channel 8
|
||||
|
||||
5. # ifconfig wlan0 up
|
||||
|
||||
## Setup BATMAN-Advanced
|
||||
|
||||
In the unpacked 'batman-adv' directory:
|
||||
|
||||
1. # insmod batman-adv.ko
|
||||
|
||||
In the batctl directory:
|
||||
|
||||
1. # ./batctl if add wlan0
|
||||
|
||||
2. # ifconfig wlan0 mtu 1527
|
||||
|
||||
3. # cat /sys/class/net/wlan0/batman_adv/iface_status
|
||||
|
||||
Should read "active".
|
||||
|
||||
4. # ifconfig wlan0 0.0.0.0
|
||||
|
||||
5. # ifconfig bat0 up
|
||||
|
||||
6. give bat0 an IP address
|
||||
1. ifconfig w.x.y.z netmask a.b.c.d up
|
||||
2. dhcp
|
||||
3. dhcp6
|
||||
4. dhclient
|
||||
5. Avahi/zeroconf
|
||||
6. IPv6
|
||||
|
||||
## Testing BATMAN-Advanced
|
||||
|
||||
Display local table of known peers (by MAC address of node):
|
||||
|
||||
1. batctl o
|
||||
|
||||
Ping by batX MAC address of nodes:
|
||||
|
||||
1. batctl p uu:vv:ww:xx:yy:zz
|
||||
|
||||
Monitor traffic of batX interface:
|
||||
|
||||
1. tcpdump -i bat0 -s 0 -v -X -n
|
||||
|
||||
Test connectivity between nodes:
|
||||
|
||||
1. ping6 -p DEADBEEF -I bat0 (IPv4 address of host)
|
||||
2. ping6 -p DEADBEEF -I bat0 (IPv6 address of host)
|
||||
Executable
+150
@@ -0,0 +1,150 @@
|
||||
**BATMAN is depreciated in favor of BATMAN-Adv or Babel**
|
||||
|
||||
- Decentralization of routing knowledge.
|
||||
- No node has all of the routing data possible.
|
||||
- Propagation of routing information is not done with broadcast.
|
||||
- Nodes have only information about routes packets were received from.
|
||||
|
||||
<!-- -->
|
||||
|
||||
- Stable.
|
||||
- Slow convergance times.
|
||||
|
||||
<!-- -->
|
||||
|
||||
- Other BATMAN nodes are detected and noted.
|
||||
- New nodes are noted. Neighbors are informed.
|
||||
|
||||
<!-- -->
|
||||
|
||||
- Every node broadcasts its existence periodically. \< 200 seconds.
|
||||
- These periodic updates overwrite contradictory information.
|
||||
- Neighbors relay this information until every node has heard about it.
|
||||
- Nodes which are currently considered the best next hop are considered
|
||||
neighbors.
|
||||
- A particular node counts the number of messages sent in reply for
|
||||
every node and determines the route length that way.
|
||||
- Each node only knows about routes to its neighbors. It lets neighbors
|
||||
worry about additional hops.
|
||||
- Good routes, by definition, propagate farther than dodgy ones.
|
||||
- Timeless FSM: events are used to react to changing network conditions,
|
||||
not timers.
|
||||
|
||||
<!-- -->
|
||||
|
||||
- Aims for easy, small, and fast.
|
||||
- Supports multiple network devices of probably any kind. All are used
|
||||
to retransmit packets.
|
||||
- Nodes can inform other nodes that they're gateways to the Net.
|
||||
- Nodes can announce that they are gateways from the mesh to an attached
|
||||
LAN providing services.
|
||||
|
||||
<http://www.open-mesh.org/>
|
||||
<http://www.open-mesh.org/wiki/batman-adv-quick-start-guide>
|
||||
<http://lwn.net/Articles/426947/>
|
||||
|
||||
- Branches: major variants of not only the codebase but the protocol
|
||||
itself.
|
||||
- batmand operates at layer 3.
|
||||
- batman-adv users the version III algorithm, but operates at layer 2.
|
||||
- Implemented as a kernel module for speed.
|
||||
- batctl is the control utility.
|
||||
|
||||
<!-- -->
|
||||
|
||||
- v0.3 makes use of the kernel's policy routing capabilities.
|
||||
|
||||
<!-- -->
|
||||
|
||||
- Four routing tables.
|
||||
- View routing tables:
|
||||
- batmand -i \| grep rt_table
|
||||
- rt_table_networks: entries for announced networks.
|
||||
- rt_table_hosts: all reachable BATMAN nodes.
|
||||
- rt_table_unreach:
|
||||
- rt_table_tunnel: default route if the client uses routing_class
|
||||
and a gateway is involved.
|
||||
|
||||
<!-- -->
|
||||
|
||||
- Need to use the ip command (iproute2 package).
|
||||
- Makes use of advanced IP routing tools.
|
||||
- batmand -i \| grep rt_prio
|
||||
- ip rule
|
||||
- Allows you to separate client nodes from network routers.
|
||||
- BATMAN related routing tables are easy to flush because they're
|
||||
separate.
|
||||
- The normal routing table can be messed with without disturbing
|
||||
batmand's operation.
|
||||
|
||||
<!-- -->
|
||||
|
||||
- batmand can announce that a node is a gateway to the Net by announcing
|
||||
how much downlink bandwidth it has available:
|
||||
- batmand -g <kbits> <network interface>
|
||||
- batmand -g 1500kbit eth0
|
||||
- Opens new tunnel interface gateX, automagically sets route.
|
||||
- Gateway interface must NAT traffic!
|
||||
- batmand v0.3.2 and newer will automatically call iptables to configure
|
||||
NAT.
|
||||
- Stop announcing a gateway:
|
||||
- batmand -c -g 0
|
||||
- Announce a perferred gateway:
|
||||
- batmand -c -p 1.2.3.4
|
||||
|
||||
<!-- -->
|
||||
|
||||
- batmand must be configured to watch for announced gateways.
|
||||
- batmand -r 1 <interface>
|
||||
- Considers link quality and gateway class before using for downlink.
|
||||
- Kept open as long as possible for statefulness.
|
||||
|
||||
<!-- -->
|
||||
|
||||
- - batmand -r 2 <interface>
|
||||
- Considers link quality toward gateway.
|
||||
|
||||
<!-- -->
|
||||
|
||||
- - batmand -r 3 <interface>
|
||||
- Considers link quality, but will drop tunnel for one with a better
|
||||
link it it sees one.
|
||||
|
||||
<!-- -->
|
||||
|
||||
- - batmand -r \[3-256\] <interface>
|
||||
- Considers link quality, but will switch to another as soon as a new
|
||||
one has an X better transmission quality metric.
|
||||
|
||||
To reduce load if there are many clients, the batgat.ko module can do
|
||||
all of this from kernelspace. batmand automatically looks for a loaded
|
||||
batgat.ko module, and will use it if one is found. batgat.ko has been in
|
||||
the kernel since v2.6.33. Can separately compile and install later
|
||||
versions of the module if upgrading the kernel isnt' an option. v2.6.33
|
||||
-\> batman-adv v0.2.0 ... v2.6.36 -\> batman-adv v2010.1.0 v2.6.37 -\>
|
||||
batman-adv v2010.2.0 v2.6.38 -\> batman-adv v2011.0.0 Because it's at
|
||||
layer 2, it doesn't use UDP for transport: raw 802.11 frames. Implements
|
||||
a virtual network switch. Thus, doesn't care about anything higher than
|
||||
it on the stack. You can not use IP if you want. Non-mesh clients are
|
||||
easier to handle. Client roaming is easier. Easier to optimize traffic
|
||||
flow.
|
||||
|
||||
Static hosts not running batmand must be explicitly announced - called
|
||||
HNA. These announcements tell every batmand node that a network segment
|
||||
/foo/ has non-clients available. The non-BATMAN network must have routes
|
||||
back, possibly NAT. Example: web servers on 192.168.1.0/24:
|
||||
|
||||
` batmand -c -a 192.168.1.0/24`
|
||||
` batmand -c -a 192.168.1.0/24 -a 192.168.30.0/24`
|
||||
|
||||
Revoking an announcement:
|
||||
|
||||
` batmand -c -A 192.168.1.0/24`
|
||||
` batmand -c -A 192.168.1.0/24 -A 192.168.30.0/24`
|
||||
|
||||
No inherent security. Designed for community, not for privacy. Do
|
||||
encryption higher in the stack. SSL, TLS, IPsec... use good Tor
|
||||
security.
|
||||
|
||||
Can be found in the Debian repository. Available for many embedded Linux
|
||||
platforms. Comes with OpenWRT.
|
||||
Executable
+188
@@ -0,0 +1,188 @@
|
||||
Available in most Linux distributions (including Arch, Debian, OpenWRT).
|
||||
|
||||
# Features
|
||||
|
||||
Distance vector routing protocol:
|
||||
|
||||
- Direction in which a packet should be forwarded.
|
||||
- Interface to which a protocol should be sent
|
||||
- Direction == address of next hop and exit interface
|
||||
- Distance from destination
|
||||
- Cost of reaching destination is computed using various metrics
|
||||
|
||||
<!-- -->
|
||||
|
||||
- Designed for both wireless (in ad-hoc mode) and wired network routing.
|
||||
- Designed with mobile nodes in mind.
|
||||
- Can route both IPv4 and IPv6 simultaneously and transparently. Doesn't
|
||||
care which layer 3 protocols are running on top of it.
|
||||
- Converges rapidly.
|
||||
- Triggered updates.
|
||||
- Explicit requests for routing information rather than continual
|
||||
broadcasting.
|
||||
|
||||
<!-- -->
|
||||
|
||||
- Uses link quality metrics.
|
||||
- Metric: packet loss, interference (optional) and RTT (optional).
|
||||
- History sensitive to avoid route flapping.
|
||||
|
||||
<!-- -->
|
||||
|
||||
- Does not optimize route tables immediately, more concerned with
|
||||
stability than slim tables. Premature optimization is the root of all
|
||||
coders' anguish, and all that.
|
||||
- This is used to cure route starvation.
|
||||
- Used to choose feasibility of a particular route.
|
||||
- Every route carries a sequence number that never decreases and is
|
||||
propagated unchanged through the network.
|
||||
- Only the route's source can ever increment that number.
|
||||
- If the sequence number is more recent that the feasibility distance
|
||||
maintained by the receiving node, or if it's equally recent but the
|
||||
metric is smaller, then that particular route will be selected.
|
||||
- Routes become feasible again after the sequence number is incremented.
|
||||
- Ideal for embedded systems due to the properties inherent of DVRPs.
|
||||
|
||||
<!-- -->
|
||||
|
||||
- Most routing loops are avoided, remaining routing loops are transient,
|
||||
disappear in time proportional to the diameter of the loops.
|
||||
- Routers take note of loops and ensure that they do not recur.
|
||||
|
||||
<!-- -->
|
||||
|
||||
- Highly mobile nodes may elect to use shorter time constants, to
|
||||
reflect their changing environment more accurately.
|
||||
|
||||
<!-- -->
|
||||
|
||||
- Nodes periodically broadcast HELLO packets. Nodes also respond to
|
||||
HELLO broadcasts from neighboring nodes with I HEARD YOU packets.
|
||||
These are used to calculate link costs.
|
||||
- Periodically, every node B broadcasts a routing update D(B).
|
||||
|
||||
Every neighboring node A checks to see if B is its next hop. If so,
|
||||
|
||||
` NH(A) = B`
|
||||
` D(A) = C(A, B) + D(B)`
|
||||
|
||||
otherwise,
|
||||
|
||||
` if (C(A, B) + D(B)) < D(A)`
|
||||
` the received route is a better one`
|
||||
` NH(A) = B`
|
||||
` D(A) = C(A, B) + D(B)`
|
||||
|
||||
For any node A:
|
||||
|
||||
` estimated distance to node S = D(A)`
|
||||
` next hop router to node S = NH(A)`
|
||||
|
||||
Initially, D(S) == 0, D(A) == infinity, NH(A) == UNDEFINED
|
||||
|
||||
If a route has to be retracted for any rason, babeld flags that route as
|
||||
UNREACHABLE for a few minutes. Even if the route comes back it won't be
|
||||
used until that timer is up. This is usually the worst case propagation
|
||||
time for the route to a particular node C.
|
||||
|
||||
Every Babel router gets a unique ID, a string of 8 octets.
|
||||
|
||||
- Transmitted over UDP.
|
||||
- Sent with a unicast source address to a multicast address (usually).
|
||||
- Known neighbors get both multicast and unicast (directed to a
|
||||
particular node).
|
||||
|
||||
# Usage
|
||||
|
||||
How to use babeld: Put the NIC into ad-hoc mode:
|
||||
|
||||
` iwconfig wlan0 mode ad-hoc channel X essid "mesh"`
|
||||
` ifconfig wlan0 up`
|
||||
|
||||
All nodes need to have unique IP addresses. IPv4 at least, IPv6 if you
|
||||
have it.
|
||||
|
||||
` ifconfig wlan0 192.168.13.37/32`
|
||||
`` ifconfig wlan0 `generate-ipv6-address -r`/128 ``
|
||||
|
||||
Start babeld:
|
||||
|
||||
` babeld wlan0`
|
||||
|
||||
If there are multiple network interfaces:
|
||||
|
||||
` babeld wlan0 eth1 eth2 ppp0 ...`
|
||||
|
||||
If a specific network gateway router exists, set it:
|
||||
|
||||
` route add default gw 1.2.3.4 dev eth1`
|
||||
|
||||
These are often set on a per-node basis. For example, babeld is running
|
||||
on a laptop with both wireless and wired interfaces.
|
||||
|
||||
Then redistribute routes through the mesh:
|
||||
|
||||
` babeld -C 'redistribute metric 128' eth1`
|
||||
|
||||
It is possible to redistribute the routes associated only with a
|
||||
particular network interface:
|
||||
|
||||
` babeld -C 'redistribute if eth2 metric 128' eth1`
|
||||
|
||||
Other babeld options:
|
||||
|
||||
` -h `<sec>`: interval in seconds between HELLO broadcasts over wireless.`
|
||||
` Default: 4 sec.`
|
||||
` -H `<sec>`: as -h, only for wired interfaces.`
|
||||
|
||||
babeld is not designed for security. An attacker that is link-local can
|
||||
inject packets, just like ARP. Local firewalls, if applicable, should be
|
||||
configured to allow Babel packets. Default: 6697/UDP
|
||||
|
||||
# Accessories
|
||||
|
||||
## AHCPD
|
||||
|
||||
AHCP can also be used to configure routing when using babeld:
|
||||
|
||||
` `[`http://www.pps.jussieu.fr/~jch/software/ahcp/`](http://www.pps.jussieu.fr/~jch/software/ahcp/)
|
||||
|
||||
Arch Linux package downloaded, compiled, and ready to install.
|
||||
|
||||
Automagically configures IPv6 and IPv4/IPv6 networks when babeld is
|
||||
used. Implements router discovery. Replaces DHCP. Configures IPv?
|
||||
addresses, DNS, NTP. Does not configure default routes, that's babeld's
|
||||
job.
|
||||
|
||||
Setting up an authoritative AHCP server:
|
||||
|
||||
` Configure /etc/ahcpd.conf appropriately.`
|
||||
` ahcpd -c /etc/ahcpd.conf -D wlan0`
|
||||
|
||||
Does not need to run as root, only needs to be able to write a pidfile
|
||||
and the lease database. If the server can sync its clock using NTP, it
|
||||
will. If it can't it will only give short leases and be careful with
|
||||
releasing them. Multiple servers can run on the same mesh so long as
|
||||
they work different IPv4 netblocks.
|
||||
|
||||
Other options:
|
||||
|
||||
` -t `<sec>` - time in second that leases are offered for.`
|
||||
` -L /path/to/log - Specify a logfile. By default, /var/log/ahcpd.log`
|
||||
|
||||
kill -USR1 to print server status to logfile. kill -USR2 checks for
|
||||
interface status changes, then reopens logfile.
|
||||
|
||||
Running an AHCP client:
|
||||
|
||||
` ahcpd wlan0`
|
||||
|
||||
Designed for mesh networks. Doesn't set default gateway, netmask, or
|
||||
on-link prefixes for IPv6.
|
||||
|
||||
## WebGUI
|
||||
|
||||
haxwithaxe doesn't know how this works yet but it looks really cool.
|
||||
[babelweb](http://babelweb.wifi.pps.univ-paris-diderot.fr:8080)
|
||||
|
||||
git clone git://git.wifi.pps.univ-paris-diderot.fr/babelweb.git
|
||||
Executable
+34
@@ -0,0 +1,34 @@
|
||||
## Compile and install Babel
|
||||
|
||||
Download babeld and ahcpd. Standard "make && sudo make install".
|
||||
|
||||
On OS X: rt lib is not available in OS X, the ahcpd README is missing
|
||||
this info
|
||||
|
||||
make LDLIBS=''
|
||||
make install
|
||||
|
||||
## Setup ad-Hoc network
|
||||
|
||||
1. Disable NetworkManager
|
||||
1. Right click on NetworkManager applet, un-check "Enable
|
||||
networking".
|
||||
2. Fedora:
|
||||
# /etc/init.d/NetworkManager stop
|
||||
3. Ubuntu:
|
||||
# stop network-manager
|
||||
|
||||
2. Disable the firewall
|
||||
1. # iptables -F
|
||||
|
||||
3. # ifconfig wlan0 down
|
||||
|
||||
4. # iwconfig wlan0 mode ad-hoc essid hacdc-babel channel 9
|
||||
|
||||
5. # ifconfig wlan0 up
|
||||
|
||||
## Setup Babel
|
||||
|
||||
1. # babeld -D wlan0
|
||||
|
||||
2. # ahcpd -D wlan0
|
||||
Executable
+34
@@ -0,0 +1,34 @@
|
||||
The basement contains various shelves and our more dangerous/high
|
||||
powered/shop type equipment.
|
||||
|
||||
## Location
|
||||
|
||||
The basement is at St. Stephen and the Incarnation Episcopal Church. It
|
||||
is locked and access is somewhat restricted.
|
||||
|
||||
## Organization
|
||||
|
||||
It's not really organized according to any principle currently.
|
||||
|
||||
## Equipment
|
||||
|
||||
Optical Table Robot
|
||||
|
||||
CNC Lathe
|
||||
|
||||
Tons of stuff...
|
||||
|
||||
## Storage
|
||||
|
||||
See organization.
|
||||
|
||||
## Secure Rack
|
||||
|
||||
We have a rack and servers in the basement.
|
||||
|
||||
## Outgoing
|
||||
|
||||
The outgoing area is in the basement.
|
||||
|
||||
[Category:In_the_Space](Category:In_the_Space "wikilink")
|
||||
[Category:Basement](Category:Basement "wikilink")
|
||||
Executable
+34
@@ -0,0 +1,34 @@
|
||||
# Design
|
||||
|
||||
Initial design by mirage335 for HacDC Basement. Intended for placement a
|
||||
few feet away from wall in either or both rooms as necessary, accessible
|
||||
from both sides, providing a sort of warehouse.
|
||||
|
||||
# Specifications
|
||||
|
||||
- 8' high, 16' long, 4' deep, 16" elevations
|
||||
- 64 square feet per shelf
|
||||
- 6 shelves total
|
||||
- 384 usable square feet, including floor, excluding top shelf
|
||||
|
||||
# Render
|
||||
|
||||
<img src="BasementShelves-Render.png" title="BasementShelves-Render.png"
|
||||
width="800" alt="BasementShelves-Render.png" />
|
||||
<img src="BasementShelves-Results-Stress.png"
|
||||
title="BasementShelves-Results-Stress.png" width="800"
|
||||
alt="BasementShelves-Results-Stress.png" />
|
||||
|
||||
# OpenSource
|
||||
|
||||
Please see [github](https://github.com/HacDC/BasementShelves) for CAD
|
||||
model, BOM, and simulation results.
|
||||
|
||||
# Credits
|
||||
|
||||
Special thanks to Zack for initiative, financing, material sourcing,
|
||||
timely design advice, the right tools, rigging, and most of the heavy
|
||||
lifting. Also thanks to Martin, Ben Mendis (aka. sitwon), haxwithaxe,
|
||||
and others for feedback.
|
||||
|
||||
[Category:BasementShelves](Category:BasementShelves "wikilink")
|
||||
Executable
+78
@@ -0,0 +1,78 @@
|
||||
|
||||
|
||||
## LED Lighting
|
||||
|
||||
Feb 2014: LED strips have been added to the underside of each shelf by
|
||||
[Gatohaus](User:Gatohaus "wikilink")
|
||||
([talk](User_talk:Gatohaus "wikilink")). These are SMD 5050 strips, 5m
|
||||
long, 300 LEDs each that draw 1.2A per meter at 12v. Note they have been
|
||||
trimmed nearly a foot each to fit. Total maximum wattage for the 10
|
||||
strips currently in place is 10 x 72w = 720w. Output is around 800-900
|
||||
lumens per meter. (~40k lumens) A good balance between light and heat
|
||||
(longevity) seems to be in the 3 to 4A per strip range.
|
||||
|
||||
The location of the strips was chosen: to be somewhat protected, to
|
||||
light the shelf adequately, to avoid as much glare as possible, and to
|
||||
provide significant spillage into the surrounding area.
|
||||
|
||||
Feb 2014: **Expect a few of the strips to fall down.** Some are still
|
||||
partially attached by their adhesive tape which won't really fail until
|
||||
they're warm for a while. When they do fail, reattach them with a hot
|
||||
glue gun. That seems (fingers crossed) to be permanent.
|
||||
|
||||
### <u>Lessons Learned</u>
|
||||
|
||||
#### Strip Choice
|
||||
|
||||
SMD 3528's were also tested (the strip remains in use on the shelves).
|
||||
The 5050's were the same price (~\$12) at about the same efficiency but
|
||||
allow for a higher maximum brightness (and greater power draw of
|
||||
course).
|
||||
|
||||
#### Adhering the strips
|
||||
|
||||
The tape adhesive that comes on the strips works very poorly on OSB
|
||||
(shelving material used). They'll hold while the lights are off, but
|
||||
once they warm up the adhesive begins to fail. I tried 3M's "77" spray..
|
||||
an embarrassing failure. It too loses adhesion when warmed.
|
||||
|
||||
Trying mechanical attachments, typically a nail or staple with a plastic
|
||||
brace, the type used to hold cables in place, proved troublesome. The
|
||||
OSB is hard enough that significant force is required with a hammer to
|
||||
drive the nails in. Over a span of 50m of LEDs it seems likely that
|
||||
misses would occur probably smashing some of the LED components.
|
||||
|
||||
In the end a simple hot glue gun seems to have worked.
|
||||
|
||||
#### Wiring & Power
|
||||
|
||||
In hindsight it would have been better to mount the strips with more of
|
||||
the connecting leads sticking out at the end. The leads can easily be
|
||||
replaced if needed, they're just surface mounted.
|
||||
|
||||
<s>I used a PC's ATX power supply which has 2 x 12v at 15A.</s> (I
|
||||
managed to damage this ps somehow.) I don't know how efficient it is but
|
||||
after spending several hours hunting for options in our collection of
|
||||
stuff, this seemed the best choice. Perhaps it can be replaced at some
|
||||
point. I'm giving one of the 15A sources to the lower 3 shelves, and the
|
||||
other to the top two shelves. This means the upper ones will be
|
||||
brighter, but the spill over will help illuminate the surrounding area.
|
||||
|
||||
Temporarily (which tends to become permanent) there is another ATX ps
|
||||
plus a couple of in-line wall warts in place of the ATX mentioned above.
|
||||
This ATX has 12v at 21A and the two wall warts have 5A and 2.5A at 12v.
|
||||
Not quite the distribution I'd like, but it works.
|
||||
|
||||
**Well... almost works...** After being on for half an hour or so the
|
||||
21A ATX takes a nap. Exhaust air feels cool, but it's probably too much
|
||||
of a load. So I added *another* computer power supply (~5A) to help out.
|
||||
Seems to be stable. Need help either repairing the original ATX supply
|
||||
or finding something else.
|
||||
|
||||
### <u>Things to Improve</u>
|
||||
|
||||
In general I'm not exactly proud of the wiring. It's solid and safe, but
|
||||
not quite pretty. If someone wishes to redo this work, please do!
|
||||
|
||||
[Category:BasementShelves](Category:BasementShelves "wikilink")
|
||||
Executable
+24
@@ -0,0 +1,24 @@
|
||||
## Introduction
|
||||
|
||||
Big Blue Button is an open source communication framework that allows
|
||||
for video-conferencing and more. It would allow this hackerspace to host
|
||||
video conferences for other hackerspaces/makerspaces and organizations
|
||||
which would further enhance our ability to communicate and share
|
||||
resources.
|
||||
|
||||
[Watch this video for a full
|
||||
introduction](https://www.youtube.com/watch?v=6Saztv2WlKI)
|
||||
|
||||
## Infrastructure
|
||||
|
||||
We will be using a high-cpu Digital Ocean droplet 8GB Ram/50GB SSD/4
|
||||
CPUs. This was presented as a viable option by a very helpful Fred Dixon
|
||||
from Blindside Networks.
|
||||
|
||||
We will use chill.hakely.org as our domain name until another
|
||||
more-appropriate domain name is decided upon.
|
||||
|
||||
## Software Installation
|
||||
|
||||
[Check Server
|
||||
Specs](http://docs.bigbluebutton.org/install/install.html#check-server-specs)
|
||||
Executable
+29
@@ -0,0 +1,29 @@
|
||||
__notoc__ This is a 6 week series intended for all skill/knowledge
|
||||
levels. Each class will have a hands on portion so bring your bike in,
|
||||
stands will be provided. If you can't, don't worry, each class will have
|
||||
relevant demo bikes and components on hand. Tools will be limited so
|
||||
bring in your own if you have them.
|
||||
|
||||
## Lesson Overviews
|
||||
|
||||
- [Week 1, Introduction and Flat
|
||||
Repair](Bike_Maintenance_Class:_Week_1,_Introduction_and_Flat_Repair "wikilink")
|
||||
- [Week 2, Basic Fit, Component Materials, and Brake
|
||||
System](Bike_Maintenance_Class:_Week_2,_Basic_Fit,_Component_Materials,_and_Brake_System "wikilink")
|
||||
- [Week 3, Drivetrain and
|
||||
Shifting](Bike_Maintenance_Class:_Week_3 "wikilink")
|
||||
|
||||
## Online Resources
|
||||
|
||||
[Sheldon Brown](http://www.sheldonbrown.com/) - More than you'll ever
|
||||
want to know about bikes. [Park Tool Repair
|
||||
Help](http://www.parktool.com/blog/repair-help) - World class tool
|
||||
company with great, straight forward how-to's.
|
||||
[WABA](http://www.waba.org/) - Washington Area Bicycle Association.
|
||||
Awesome people, awesome resource.
|
||||
|
||||
## Offline Resources
|
||||
|
||||
Your local bike shop! Go support them!
|
||||
|
||||
[Category:Bike_Maintenance_Class](Category:Bike_Maintenance_Class "wikilink")
|
||||
@@ -0,0 +1,79 @@
|
||||
[Bike Maintenance Class:](Bike_Maintenance_Class "wikilink") Week 1,
|
||||
Introduction and Flat Repair
|
||||
|
||||
## Component Identification and Basic Terminology
|
||||
|
||||
### What's What on a Bike
|
||||
|
||||
|
||||
|
||||
|
||||
### Drive Side and Non-drive Side
|
||||
|
||||
The right side of the bike is referred to as the drive side while the
|
||||
left side is the non-drive side.
|
||||
|
||||
### How to talk about gearing
|
||||
|
||||
Gears closer to the frame are referred to as *inner* gears while the
|
||||
ones furthest from the frame are the *outer* gears. High and low in
|
||||
relation to the gears describes the relative mechanical advantage of the
|
||||
gearing. An easy mnemonic for this is **H**igher gears are **h**arder
|
||||
while lower gears are easier. The inner gears on a bike are always going
|
||||
to be the lower gears and the outer gears are the higher gears.
|
||||
|
||||
### Right-hand vs Left-hand Threading
|
||||
|
||||
Almost every threaded component on a bike is going to be right-hand
|
||||
threaded, which means that turning it clockwise will tighten it and
|
||||
turning it counter-clockwise will loosen it. Pedals and bottom bracket
|
||||
cups are examples where you would run into left-hand threaded
|
||||
components. To identify the *handedness* of a component hold it in front
|
||||
of you as in the picture below. The direction that the threads slant up
|
||||
too corresponds to the components handedness.
|
||||
|
||||
<figure>
|
||||
<img src="LineDrawingofLeftandRightHandedSquareThreads.png"
|
||||
title="LineDrawingofLeftandRightHandedSquareThreads.png" width="200" />
|
||||
<figcaption>LineDrawingofLeftandRightHandedSquareThreads.png</figcaption>
|
||||
</figure>
|
||||
|
||||
Left-handed Right-handed
|
||||
|
||||
### Valves: Schrader and Presta
|
||||
|
||||
The two types of valves you will see on 99% of bikes in America are
|
||||
schrader and presta. Schrader valves are the same type of valve that you
|
||||
see on cars and most other pneumatic tires. Presta valves are
|
||||
<img src="valvetypes.jpg" title="valvetypes.jpg" width="150"
|
||||
alt="valvetypes.jpg" />
|
||||
|
||||
## Basic Upkeep
|
||||
|
||||
### Inflating Tires
|
||||
|
||||
<figure>
|
||||
<img src="valvedeflate.gif" title="Image:valvedeflate.gif" />
|
||||
<figcaption>Image:valvedeflate.gif</figcaption>
|
||||
</figure>
|
||||
|
||||
### Cleaning and lubing the chain
|
||||
|
||||
## Flat Repair
|
||||
|
||||
- Understanding brake and wheel quick release mechanisims
|
||||
- How to remove a tire with tirelevers
|
||||
- Identifying puncture source (don't forget to keep everything lined
|
||||
up!)
|
||||
- Patching
|
||||
|
||||
## Hands On
|
||||
|
||||
Repairing flat tires on demo wheels.
|
||||
|
||||
## **Resources**
|
||||
|
||||
More than you really need to know about flats: [Sheldon Brown Tells
|
||||
All](http://www.sheldonbrown.com/flats.html)
|
||||
|
||||
[Category:Bike_Maintenance_Class](Category:Bike_Maintenance_Class "wikilink")
|
||||
Executable
+124
@@ -0,0 +1,124 @@
|
||||
[Bike Maintenance Class:](Bike_Maintenance_Class "wikilink") Week 2,
|
||||
Basic Fit, Component Materials, and Brake System
|
||||
|
||||
## Judging Bike Fit: Stand Over Height
|
||||
|
||||
Finding a bike that fits correctly is important, but its also is mostly
|
||||
about personal preference. So what should you look at?
|
||||
The most basic component of bike fit is stand over height. On the bike
|
||||
its the distance from the top of the top tube to the ground. On the
|
||||
rider this measurement should be at least an inch or two less than the
|
||||
distance from your crotch to the ground. If you don't have that
|
||||
clearance you could really hurt yourself when dismounting. Stand over
|
||||
height differs between bikes that are the same size based on how the
|
||||
manufacture measures size and the bikes geometry. 
|
||||
|
||||
This will tell you if a bike fits you most of the time. While there are
|
||||
other components to bike fit, most of them are adjustments, which we
|
||||
will cover later in this class.
|
||||
|
||||
## Frame Materials
|
||||
|
||||
Bikes frames are made out of three types of material:
|
||||
|
||||
- **Steel** - If your using your bike on a daily basis and have to lock
|
||||
it up outside sometimes(but never overnight!) steel is what you want.
|
||||
It can take more abuse than aluminium or carbon and sometimes even be
|
||||
realigned after a particularly hard impact that would total other
|
||||
frames. Avoid frames made of high carbon or high-tensile steel (some
|
||||
times called hi-ten). Instead look for frames made of an alloy such as
|
||||
chromoly (chromium-molybdenum) as they are lighter, stronger, and
|
||||
resist rust better. If the frame doesn't have a sticker stating what
|
||||
its made of, there's a good chance is straight gauge, high-tensile
|
||||
steel.
|
||||
- **Aluminium** - Stiffer and lighter than steel, aluminium is ideal for
|
||||
road bikes where you want to be putting down maximum power, or in a
|
||||
bike with suspension where you aren't relying on the frame to absorb
|
||||
shock. The thin tubing in nicer aluminium bikes is prone to dents and
|
||||
dings so be careful when leaning it up against poles and street sights
|
||||
to lock it up. Also, if your frame ever gets bent, that it, game over,
|
||||
time for a new frame.
|
||||
- **Carbon** - Carbon fiber frame are made by laminating sheets of
|
||||
carbon fiber together with epoxy in a vacuum mold. This gives
|
||||
designers a great deal of flexibility in design that can result in
|
||||
extremely light bikes that are stiff in some area and good at
|
||||
absorbing vibration in others. The down side is that carbon fiber is
|
||||
brittle and comparatively more expensive. If your riding a carbon
|
||||
bike, you shouldn't be locking it up anywhere outside.
|
||||
|
||||
**Butted vs Straight Gauge**: Double and triple butted tubing is thinner
|
||||
in the center of the tube than at the ends, taking pounds of the weight
|
||||
off a frame and providing a more comfortable ride.
|
||||
|
||||
## Saddle and Cockpit Set-Up
|
||||
|
||||
### Saddle Height and Position
|
||||
|
||||
- **Level**
|
||||
|
||||
Your saddle should always be about level or tipped slightly towards the
|
||||
front of the bike. Level is measured from the highest point on the rear
|
||||
of the saddle to the hightest point on the front of the saddle (the
|
||||
nose). You can change this slightly but if the saddle is tilted to far
|
||||
forward, your going to put extra pressure on your wrists, to far back
|
||||
and the saddle's nose is going to start putting pressure on bits you
|
||||
wish it wouldn't.
|
||||
|
||||
- **Height**
|
||||
|
||||
When in the saddle, with the peddles at 11 and 5 o'clock, place the
|
||||
heels of you feet on the peddles (you might want to get a friend to hold
|
||||
the bike steady for you). Adjust your saddle so that the extended leg
|
||||
bends slightly at the knee. The idea is the more leg extension you can
|
||||
get, the more efficient the stroke, but you *never* want your leg to
|
||||
extent fully as this is very bad for you knees. 
|
||||
|
||||
- **Setback**
|
||||
|
||||
When in the saddle, with the peddles at 3 and 9 o'clock, the front of
|
||||
your leading knee should be plumb with the peddles spindle.
|
||||
|
||||
### Handlebar/Stem Position
|
||||
|
||||
Seeing as you can have anything from drop bars to 5" risers on a bike,
|
||||
this is mostly personal preference. Just make sure you knees aren't
|
||||
going to hit the bars when your taking a sharp corner. A more upright
|
||||
position gives you better visibility while a lower position will make
|
||||
you more aerodynamic.
|
||||
|
||||
### Cockpit Set-up
|
||||
|
||||
All of this is personal preference, but here's a starting point.
|
||||
|
||||
- **Flat Handlebars**
|
||||
- **Drop Handlebars**
|
||||
|
||||
## Breaks
|
||||
|
||||
### System Overview/Styles
|
||||
|
||||
#### Pull Ratio
|
||||
|
||||
#### Mountain vs Road Cables
|
||||
|
||||
#### Calliper, Cantilever, and Linear Pull
|
||||
|
||||
##### Quick Release
|
||||
|
||||
===Replacing Cable and Housing
|
||||
|
||||
#### What's the Difference Between Break Housing and Shift Housing
|
||||
|
||||
#### Measuring and Cutting Housing
|
||||
|
||||
#### Installing Brake Cable
|
||||
|
||||
### Replacing Brake Pads
|
||||
|
||||
#### Styles of Pads
|
||||
|
||||
## Overview, adjusting, and installing pads
|
||||
|
||||
[Category:Bike_Maintenance_Class](Category:Bike_Maintenance_Class "wikilink")
|
||||
Executable
+8
@@ -0,0 +1,8 @@
|
||||
This page has been deprecated due to the creation of an appropriate
|
||||
Category page and should be deleted.
|
||||
|
||||
--[Shawn Nock (OpenPGP: 0x65118FA5)](User:Nock "wikilink") 13:04, 5
|
||||
November 2012 (PST)
|
||||
|
||||
[Category:Candidates for
|
||||
deletion](Category:Candidates_for_deletion "wikilink")
|
||||
Executable
+52
@@ -0,0 +1,52 @@
|
||||
## System
|
||||
|
||||
- Use beacons mounted on stationary objects within a room to allow user
|
||||
supplied devices to triangulate their rough position inside the room
|
||||
- The users may share their location via various means.
|
||||
- XMPP
|
||||
- complex
|
||||
- relies on external infrastructure eventually
|
||||
- robust against network topology traversals (NAT/Firewall)
|
||||
- Multicast
|
||||
- simple
|
||||
- not robust when traversing NATs
|
||||
- Useful for a conference hall or the like, where an area is large
|
||||
enough to prevent finding ones way or friends easily.
|
||||
|
||||
testing guest captcha
|
||||
|
||||
## Hardware
|
||||
|
||||
### SOCs
|
||||
|
||||
- [Nordic](http://www.mouser.com/ProductDetail/Nordic-Semiconductor/nRF51822-QFAB-R7/?qs=sGAEpiMZZMvQqVCO1QUke9rOCiF3q8UDR59ukwBL9d8%3d)
|
||||
- [TI](http://www.mouser.com/ProductDetail/Texas-Instruments/CC2540F128RHAR/?qs=sGAEpiMZZMuReUCzg6bfTFMX9eNsg5flb%2fyNLpDtSPE%3d)
|
||||
|
||||
### Front End/BT modules
|
||||
|
||||
- just as expensive as SOCs
|
||||
|
||||
## Software
|
||||
|
||||
### Phone App
|
||||
|
||||
#### Android
|
||||
|
||||
#### iThing
|
||||
|
||||
### Firmware
|
||||
|
||||
- bit-bang BTLE library
|
||||
[code](https://dmitry.gr/index.php?r=05.Projects&proj=11.%20Bluetooth%20LE%20fakery)
|
||||
for reference
|
||||
|
||||
#### Beacon
|
||||
|
||||
- Similar use cases
|
||||
- Beacon tagging - tags beacon to allow device to find the tagged item
|
||||
- [iBeacon](http://en.wikipedia.org/wiki/IBeacon) - proprietary
|
||||
implementation
|
||||
- Use [Proximity
|
||||
Sensing](http://en.wikipedia.org/wiki/Bluetooth_low_energy#Proximity_sensing)
|
||||
Profile (PXP/FMP) to let user devices know where and roughly how far
|
||||
they are from the beacons.
|
||||
Executable
+152
@@ -0,0 +1,152 @@
|
||||
------------------------------------------------------------------------
|
||||
|
||||
baghaii:
|
||||
|
||||
I am not sure if you are limited to public transportation or not.
|
||||
<http://en.wikipedia.org/wiki/MIT_Museum>
|
||||
|
||||
<http://www.larzanderson.org/Topics/Topic.cfm?TopicName=Home&CFID=536300&CFTOKEN=51791476>
|
||||
<http://www.hammondcastle.org/common/index.php?com=HAMM&div=AA&nav=AA&page=A91>
|
||||
<http://en.wikipedia.org/wiki/Marconi_Wireless_Station_Site>
|
||||
|
||||
The BU Photonics Center has some interesting sculptures that involve
|
||||
light. There is a really cool sculpture on the 7th floor. There is the
|
||||
thing by the elevator. I forget what it is supposed to do. Understand
|
||||
commands? I don't remember what it did or if it ever quite worked.
|
||||
|
||||
Not relevant but I have always wanted to go.
|
||||
<http://www.museumofbadart.org/>
|
||||
|
||||
------------------------------------------------------------------------
|
||||
|
||||
rmadams:
|
||||
|
||||
Wow! Too cool! I loved _loved_ living in Boston/Cambridge. There are
|
||||
lots of great geek things to do and see in Boston. Here are a few of my
|
||||
favorites:
|
||||
|
||||
1\. See the amazing hacks in the "Nightwork" exhibit at the MIT Museum-
|
||||
geeks at MIT have been performing amazing hacks for _decades_.
|
||||
Besides, the MIT museum is just plain cool. See it at:
|
||||
<http://web.mit.edu/museum/> It is cool, and kind of offbeat, and a lot
|
||||
of fun.
|
||||
|
||||
2\. You can also check out the MIT campus, which is right nearby- it is
|
||||
a lot of fun to walk around there, and see the Media Lab, the AI Lab,
|
||||
etc. etc. Plus, if your timing is good, you can check out such sights as
|
||||
the famous "Infinite Corridor," etc. in the buildings. You might even
|
||||
run into folks like Marvin Minsky hanging around. If you read Levy's
|
||||
"Hackers"
|
||||
(http://www.amazon.com/Hackers-Computer-Revolution-Steven-Levy/dp/0141000511)
|
||||
before you go, you will get some of the history and local color.
|
||||
|
||||
3\. While you are there in Cambridge, have lunch/dinner at the amazing
|
||||
"Miracle of Science" bar/grill. All of their tables are laboratory
|
||||
soapstone, and the menus is chalked up on a chalkboard in "periodic
|
||||
table" form. Very amusing. They don't serve their drinks in laboratory
|
||||
glassware, but the food good and the place is fun. You can overhear some
|
||||
very interesting tech/science conversations there.
|
||||
(http://www.miracleofscience.us/)
|
||||
|
||||
4\. After lunch/dinner, grab drinks (and maybe catch some music/dancing)
|
||||
at the Enormous Room, one T stop up in Central Square:
|
||||
<http://www.enormous.tv/ENORMOUS_2004/main1.html>
|
||||
|
||||
5\. Across the River (almost) you can visit the Boston Museum of
|
||||
Science, which has a lot of really fun stuff, but don't miss the
|
||||
electricity show, using some of the original "atom smashers" giant Van
|
||||
de Graaff generators. Very, very cool. And loud. Also check out the
|
||||
scale model of the solar system. To get to Pluto, you need to take the T
|
||||
(Green Line) all the way out to the end of the line in Riverside...
|
||||
(http://www.mos.org/)
|
||||
|
||||
6\. Check out Willoughby and Baltic at their new digs in Union Square:
|
||||
<http://willoughbybaltic.ning.com/>. They might have some fun
|
||||
hacker-type stuff going on while you are there. Totally cool tech/arts
|
||||
collective.
|
||||
|
||||
Sheesh. I could go on forever. Hope this gives you a start- contact me
|
||||
if you want more of the same!
|
||||
|
||||
Everyone's suggestions are great! I completely forgot about the atrium
|
||||
at the Broad (pronounced to rhyme with "road" in case you have to ask
|
||||
around to find it.) I spend so much time that there that I forgot about
|
||||
the displays in the atrium. It is really neat. If you are down that
|
||||
road, you can walk through the atrium at Draper Labs, where a bunch of
|
||||
the hardware they designed for the lunar landings is displayed. It is
|
||||
actually very cool. <http://www.draper.com/Apollo/apollo_at_draper.html>
|
||||
|
||||
If you take the Red Line "T" the rest of the way up to Harvard Square,
|
||||
you can check out my personal favorite comic book store, "Million Year
|
||||
Picnic" (http://themillionyearpicnic.com/) My brother ran into Ben
|
||||
Affleck there- apparently it is his favorite comic book store, too. As
|
||||
for bookstores, check out the Harvard Coop, right around the corner
|
||||
there- they have a pretty remarkable selection of stuff academic and
|
||||
otherwise.
|
||||
|
||||
Okay- I promised that I would not go on and on- I am making myself
|
||||
homesick!
|
||||
|
||||
------------------------------------------------------------------------
|
||||
|
||||
mml:
|
||||
|
||||
These are slightly adjacent to the topic directly at hand (already well
|
||||
covered)
|
||||
|
||||
If you are in to bookstores. (I was so excited when I found out about
|
||||
Reiter's here in DC). - MIT Press book store is cool - Schoenhof's, the
|
||||
most amazing foreign language store anywhere, with tons of useful stuff
|
||||
for learners. <http://www.schoenhofs.com/>
|
||||
|
||||
I enjoyed The Computer Museum, but it's gone now. I hear the Museum of
|
||||
Science is good, though.
|
||||
|
||||
Um, if bikes appeal at all, Broadway Bicycle School is cool and has a
|
||||
nice DIY angle. <http://www.broadwaybicycleschool.com/>
|
||||
|
||||
------------------------------------------------------------------------
|
||||
|
||||
curiouslee:
|
||||
|
||||
Adding to all the great suggestions (I'm at the Media Lab this coming
|
||||
Tue-Thu)...
|
||||
|
||||
Not far from MIT Press are:
|
||||
|
||||
- The DNAtrium\*
|
||||
|
||||
<http://www.broadinstitute.org/outreach/dnatrium/dnatrium> This is a
|
||||
lobby museum on genome mapping with huge curved interactive video walls.
|
||||
|
||||
- Stata Center\*
|
||||
|
||||
<http://en.wikipedia.org/wiki/Stata_Center> Amazing Frank Gehry building
|
||||
if you're into crazy architecture. There's an elevated central
|
||||
courtyard. During day hours, you should be able to get inside.
|
||||
|
||||
- The Media Lab\*
|
||||
|
||||
<http://en.wikipedia.org/wiki/MIT_Media_Lab> Access to the lab spaces is
|
||||
controlled, but you can walk the upper atrium where there is the List
|
||||
Visual Arts Center <http://listart.mit.edu/> and the lower atrium where
|
||||
you can press your nose up against the Lifelong Kindergarten Lab or even
|
||||
step inside if you are nice to one of the lab staff that might be
|
||||
inside. The Media Lab is also nearing completion of a new expansion out
|
||||
back <http://www.media.mit.edu/about/building>
|
||||
|
||||
I'd offer up a peek into the offices of One Laptop per Child (and
|
||||
Nicholas Negroponte's office), but I know they are swamped this weekend
|
||||
with visiting students.
|
||||
|
||||
------------------------------------------------------------------------
|
||||
|
||||
dcmk1mr2:
|
||||
|
||||
While in Harvard Sq, check out the sign in one of the corner windows for
|
||||
the law firm DEWEY, CHEETHAM & HOWE. They're the lawyers for NPR's Car
|
||||
Talk.
|
||||
|
||||
------------------------------------------------------------------------
|
||||
|
||||
[Category:Hacker Travel](Category:Hacker_Travel "wikilink")
|
||||
Executable
+14
@@ -0,0 +1,14 @@
|
||||
We approved the purchase of business cards for the HacDC board and TimS
|
||||
bought some LivingSocial/Groupon discounts for VistaPrint to print them.
|
||||
Here are the Inkscape design files:  and
|
||||
.
|
||||
|
||||
The coupons actually do help on the price but not as much as one might
|
||||
think because larger percentage discounts are available without them.
|
||||
Net cost was about \$17 for 250 glossy two-sided color cards or 500
|
||||
matte cards.
|
||||
|
||||
The QR code was generated by <http://zxing.appspot.com/generator> which
|
||||
I found gave a smaller payload than <http://www.qrstuff.com/>.
|
||||
|
||||
[Category:Marketing](Category:Marketing "wikilink")
|
||||
Executable
+107
@@ -0,0 +1,107 @@
|
||||
\<!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN"
|
||||
"http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd"\> \<svg width="168mm"
|
||||
height="184mm" viewBox="-84 -92.0 168 184"\> \<symbol id="Fan"
|
||||
stroke-width="2.5" stroke="gray" fill="gray" \> \<path d="M 25 23 v -2 a
|
||||
2 2 0 0 1 -2 -1.8 l -1 -5 a 3 4 0 1 1 6 0 l -1 5 a 2 2 0 0 1 -2 1.8 v 2
|
||||
a 2 2 0 1 0 0 4 2 2 0 1 0 0 -4 z"/\> \<path d="M 25 23 v -2 a 2 2 0 0 1
|
||||
-2 -1.8 l -1 -5 a 3 4 0 1 1 6 0 l -1 5 a 2 2 0 0 1 -2 1.8 v 2 a 2 2 0 1
|
||||
0 0 4 2 2 0 1 0 0 -4 z" transform="rotate(120,25,25)"/\> \<path d="M 25
|
||||
23 v -2 a 2 2 0 0 1 -2 -1.8 l -1 -5 a 3 4 0 1 1 6 0 l -1 5 a 2 2 0 0 1
|
||||
-2 1.8 v 2 a 2 2 0 1 0 0 4 2 2 0 1 0 0 -4 z"
|
||||
transform="rotate(-120,25,25)"/\> \</symbol\> \<symbol id="Pump"
|
||||
stroke="gray" fill="none" \> \<rect x="60" y="22" rx="9" ry="9"
|
||||
width="34" height="100" stroke-width="8"/\> \<rect x="69" y="32" rx="3"
|
||||
ry="3" width="16" height="35" stroke-width="0" fill="gray"/\> \<rect
|
||||
x="58" y="0" rx="4" ry="4" width="38" height="12" fill="gray"
|
||||
stroke-width="2"/\> \<line x1="77" y1="0" x2="77" y2="34"
|
||||
stroke-width="8"/\> \<path d="M 5 43 q 11.5 10 23 0 t 23 0 v 15 q -11.5
|
||||
-10 -23 0 t -23 0 z" fill="gray"/\> \<path d="M 5 68 q 11.5 10 23 0 t 23
|
||||
0 v 15 q -11.5 -10 -23 0 t -23 0 z" fill="gray"/\> \<path d="M 5 93 q
|
||||
11.5 10 23 0 t 23 0 v 15 q -11.5 -10 -23 0 t -23 0 z" fill="gray"/\>
|
||||
\<path d="M 101 43 q 11.5 10 23 0 t 23 0 v 15 q -11.5 -10 -23 0 t -23 0
|
||||
z" fill="gray"/\> \<path d="M 101 68 q 11.5 10 23 0 t 23 0 v 15 q -11.5
|
||||
-10 -23 0 t -23 0 z" fill="gray"/\> \<path d="M 101 93 q 11.5 10 23 0 t
|
||||
23 0 v 15 q -11.5 -10 -23 0 t -23 0 z" fill="gray"/\> \</symbol\>
|
||||
\<symbol id="Temp"\> \<circle cx="65" cy="15" r="2.5" stroke-width="2"
|
||||
stroke="gray" fill="white"/\> \<circle cx="50" cy="40" r="12"
|
||||
fill="gray"/\> \<rect x="42" y="0" width="16" height="45" fill="gray"
|
||||
rx="10" ry="10"/\> \<circle cx="50" cy="40" r="9" fill="white"/\> \<rect
|
||||
x="45" y="3" width="10" height="42" fill="white" rx="7" ry="7"/\>
|
||||
\<circle cx="50" cy="40" r="5" fill="gray"/\> \<rect x="48" y="6"
|
||||
width="4" height="39" fill="gray" rx="4" ry="4"/\> \<circle cx="50"
|
||||
cy="25" r="2" fill="gray"/\> \<line x1="50" y1="40" x2="50" y2="25"
|
||||
stroke-width="5"/\> \<path d="M 5 60 q 15 10 30 0 t 30 0 30 0 v 10 q -15
|
||||
10 -30 0 t -30 0 -30 0 z" fill="gray"/\> \<path d="M 5 80 q 15 10 30 0 t
|
||||
30 0 30 0 v 10 q -15 10 -30 0 t -30 0 -30 0 z" fill="gray"/\>
|
||||
\</symbol\> \<symbol id="Level"\> \<rect x="0" y="0" width="100"
|
||||
height="100" fill="gray" rx="15" ry="15"/\> \<rect x="8" y="8"
|
||||
width="84" height="84" fill="white" rx="10" ry="10"/\> \<rect x="-1"
|
||||
y="-1" width="102" height="21" fill="white" /\> \<line x1="50" y1="10"
|
||||
x2="50" y2="60" stroke-width="10" stroke="gray"/\> \<line x1="30"
|
||||
y1="40" x2="53" y2="63" stroke-width="10" stroke="gray"/\> \<line
|
||||
x1="70" y1="40" x2="47" y2="63" stroke-width="10" stroke="gray"/\>
|
||||
\<path d="M 12 75 q 9.5 10 19 0 t 19 0 19 0 19 0 v 10 q -9.5 -10 -19 0 t
|
||||
-19 0 -19 0 -19 0 z" fill="gray"/\> \</symbol\> \<symbol id="Laser"\>
|
||||
\<rect x="0" y="0" width="60" height="90" fill="gray"/\> \<rect x="5"
|
||||
y="5" width="50" height="80" fill="white"/\> \<g transform="scale(0.9,1)
|
||||
skewY(10)"\> \<line x1="10" y1="40" x2="82" y2="40" stroke-width="5"
|
||||
stroke="gray"/\> \<circle cx="88" cy="40" r="4" fill="gray"/\> \<g
|
||||
transform="translate(88,40)"\> \<line x1="0" y1="-8" x2="0" y2="-16"
|
||||
stroke="gray" stroke-width="5" transform="rotate(-45)"/\> \<line x1="0"
|
||||
y1="-8" x2="0" y2="-16" stroke="gray" stroke-width="5"
|
||||
transform="rotate(0)"/\> \<line x1="0" y1="-8" x2="0" y2="-16"
|
||||
stroke="gray" stroke-width="5" transform="rotate(45)"/\> \<line x1="0"
|
||||
y1="-8" x2="0" y2="-16" stroke="gray" stroke-width="5"
|
||||
transform="rotate(90)"/\> \<line x1="0" y1="-8" x2="0" y2="-16"
|
||||
stroke="gray" stroke-width="5" transform="rotate(135)"/\> \<line x1="0"
|
||||
y1="-8" x2="0" y2="-16" stroke="gray" stroke-width="5"
|
||||
transform="rotate(180)"/\> \<line x1="0" y1="-8" x2="0" y2="-16"
|
||||
stroke="gray" stroke-width="5" transform="rotate(225)"/\> \</g\> \</g\>
|
||||
\<g transform="scale(0.8,1) skewY(20)"\> \<rect x="0" y="0" width="60"
|
||||
height="90" fill="gray"/\> \<rect x="5" y="5" width="50" height="80"
|
||||
fill="white"/\> \<circle cx="48" cy="48" r="4" fill="gray"/\> \</g\>
|
||||
\</symbol\> \<symbol id="Control"\> \<rect x="0" y="0" width="60"
|
||||
height="90" fill="gray"/\> \<rect x="5" y="5" width="50" height="80"
|
||||
fill="white"/\> \<g transform="translate(90,10) rotate(45)"\> \<path
|
||||
d="M 0 0 l -10 22 10 10 -10 25 10 10 0 20 10 -22 -10 -10 10 -25 -10 -10
|
||||
0 -20 z" stroke="gray" fill="gray"/\> \</g\> \<g transform="scale(0.8,1)
|
||||
skewY(20)"\> \<rect x="0" y="0" width="60" height="90" fill="gray"/\>
|
||||
\<rect x="5" y="5" width="50" height="80" fill="white"/\> \<circle
|
||||
cx="48" cy="48" r="4" fill="gray"/\> \</g\> \</symbol\> \<g\>
|
||||
\<title\>Layer 1\</title\> \<rect x="-84" y="-92.0" width="168"
|
||||
height="184" fill="black"/\> \<rect x="57.0" y="-92.0" width="18"
|
||||
height="184" rx="9.0" ry="9.0" fill="gray"/\> \<rect x="-76.0" y="-92.0"
|
||||
width="18" height="184" rx="9.0" ry="9.0" fill="gray"/\> \<circle
|
||||
cx="66" cy="83" r="3" fill="black"/\> \<circle cx="66" cy="-83" r="3"
|
||||
fill="black"/\> \<circle cx="-67" cy="83" r="3" fill="black"/\> \<circle
|
||||
cx="-67" cy="-83" r="3" fill="black"/\> \<rect x="-84" y="-72"
|
||||
width="168" height="144" rx="18" ry="18" fill="white"/\> \<circle
|
||||
cx="-55.05" cy="-43.05" r="19.95" fill="black"/\> \<rect x="-65.8"
|
||||
y="26.5" width="21.5" height="27.5" fill="black"/\> \<rect x="-73.35"
|
||||
y="-10.1" width="36.6" height="23.6" fill="black"/\> \<rect
|
||||
x="-28.749999999999993" y="-63.0" width="10" height="11.5"
|
||||
fill="black"/\> \<rect x="-9.699999999999996" y="-63.0" width="10"
|
||||
height="11.5" fill="black"/\> \<rect x="9.350000000000001" y="-63.0"
|
||||
width="10" height="11.5" fill="black"/\> \<rect x="28.400000000000006"
|
||||
y="-63.0" width="10" height="11.5" fill="black"/\> \<rect x="47.45"
|
||||
y="-63.0" width="10" height="11.5" fill="black"/\> \<rect x="66.5"
|
||||
y="-63.0" width="10" height="11.5" fill="black"/\> \<rect
|
||||
x="-28.749999999999993" y="-34.599999999999994" width="10" height="11.5"
|
||||
fill="black"/\> \<rect x="-9.699999999999996" y="-34.599999999999994"
|
||||
width="10" height="11.5" fill="black"/\> \<rect x="9.350000000000001"
|
||||
y="-34.599999999999994" width="10" height="11.5" fill="black"/\> \<rect
|
||||
x="28.400000000000006" y="-34.599999999999994" width="10" height="11.5"
|
||||
fill="black"/\> \<rect x="47.45" y="-34.599999999999994" width="10"
|
||||
height="11.5" fill="black"/\> \<rect x="66.5" y="-34.599999999999994"
|
||||
width="10" height="11.5" fill="black"/\> \<circle cx="-10" cy="44" r="6"
|
||||
fill="black"/\> \<circle cx="-10" cy="4" r="5" fill="black"/\> \<circle
|
||||
cx="24" cy="80" r="6" fill="black"/\> \<circle cx="56" cy="80" r="6"
|
||||
fill="black"/\> \</g\> \<use transform="translate(-35,-53)
|
||||
scale(0.4,0.4)" xlink:href="#Fan"/\> \<use
|
||||
transform="translate(-13.5,-50) scale(0.10,0.10)" xlink:href="#Pump"/\>
|
||||
\<use transform="translate(7,-50) scale(0.13,0.13)"
|
||||
xlink:href="#Temp"/\> \<use transform="translate(25.8,-51)
|
||||
scale(0.13,0.13)" xlink:href="#Level"/\> \<use
|
||||
transform="translate(45.8,-51) scale(0.13,0.13)" xlink:href="#Laser"/\>
|
||||
\<use transform="translate(65.0,-51) scale(0.13,0.13)"
|
||||
xlink:href="#Control"/\> \</svg\>
|
||||
Executable
+133
@@ -0,0 +1,133 @@
|
||||
<nowiki>
|
||||
<svg width="174mm" height="184mm" viewBox="-87 -92.0 174 184">
|
||||
|
||||
<symbol id="Fan" fill="gray" >
|
||||
<circle r="7" cx="50" cy="50"/>
|
||||
<g id="blade">
|
||||
<rect x="48" y="32" width="4" height="16"/>
|
||||
<circle r="6" cx="50" cy="35"/>
|
||||
<circle r="9" cx="50" cy="9"/>
|
||||
<path d="M50 9 h9 l-3 26 h-12 l -3 -26z"/>
|
||||
</g>
|
||||
<use xlink:href="#blade" transform="rotate(72,50,50)"/>
|
||||
<use xlink:href="#blade" transform="rotate(144,50,50)"/>
|
||||
<use xlink:href="#blade" transform="rotate(216,50,50)"/>
|
||||
<use xlink:href="#blade" transform="rotate(288,50,50)"/>
|
||||
</symbol>
|
||||
|
||||
<symbol id="Pump">
|
||||
<g fill="gray">
|
||||
<path d="M50 4 h7 a 2 2 0 0 1 2 2 v 2 a 2 2 0 0 1 -2 2 h -5 v 20 h 6 a 6 6 0 0 1 6 6 v 56 a 6 6 0 0 1 -6 6 h -16 a 6 6 0 0 1 -6 -6 v -56 a 6 6 0 0 1 6 -6 h 6 m 0 4 h -5 a 3 3 0 0 0 -3 3 v 54 a 3 3 0 0 0 3 3 h 14 a 3 3 0 0 0 3 -3 v -54 a 3 3 0 0 0 -3 -3 h -5 v 6 h 2 a 3 3 0 0 1 3 3 v 16 a 3 3 0 0 1 -3 3 h -8 a 3 3 0 0 1 -3 -3 v -16 a 3 3 0 0 1 3 -3 h 2 v -6 m 0 -4 v -20 h -5 a 2 2 0 0 1 -2 -2 v -2 a 2 2 0 0 1 2 -2 h 7 z"/>
|
||||
<path d="M3 56 q7.5 6 15 0 t15 0 v8 q-7.5 -6 -15 0 t-15 0 z"/>
|
||||
<path d="M3 70 q7.5 6 15 0 t15 0 v8 q-7.5 -6 -15 0 t-15 0 z"/>
|
||||
<path d="M3 84 q7.5 6 15 0 t15 0 v8 q-7.5 -6 -15 0 t-15 0 z"/>
|
||||
<path d="M67 56 q7.5 6 15 0 t15 0 v8 q-7.5 -6 -15 0 t-15 0 z"/>
|
||||
<path d="M67 70 q7.5 6 15 0 t15 0 v8 q-7.5 -6 -15 0 t-15 0 z"/>
|
||||
<path d="M67 84 q7.5 6 15 0 t15 0 v8 q-7.5 -6 -15 0 t-15 0 z"/>
|
||||
</g>
|
||||
</symbol>
|
||||
|
||||
<symbol id="Temp">
|
||||
<circle cx="65" cy="15" r="2.5" stroke-width="2" stroke="gray" fill="white"/>
|
||||
<circle cx="50" cy="40" r="12" fill="gray"/>
|
||||
<rect x="42" y="0" width="16" height="45" fill="gray" rx="10" r="10"/>
|
||||
<circle cx="50" cy="40" r="9" fill="white"/>
|
||||
<rect x="45" y="3" width="10" height="42" fill="white" rx="7" r="7"/>
|
||||
<circle cx="50" cy="40" r="5" fill="gray"/>
|
||||
<rect x="48" y="6" width="4" height="39" fill="gray" rx="4" r="4"/>
|
||||
<circle cx="50" cy="25" r="2" fill="gray"/>
|
||||
<line x1="50" y1="40" x2="50" y2="25" stroke-width="5"/>
|
||||
<path d="M 5 60 q 15 10 30 0 t 30 0 30 0 v 10 q -15 10 -30 0 t -30 0 -30 0 z" fill="gray"/>
|
||||
<path d="M 5 80 q 15 10 30 0 t 30 0 30 0 v 10 q -15 10 -30 0 t -30 0 -30 0 z" fill="gray"/>
|
||||
</symbol>
|
||||
<symbol id="Level" fill="gray">
|
||||
<path d="M 0 20 v 65 a 15 15 0 0 0 15 15 h 70 a 15 15 0 0 0 15 -15 v -65 h -8 v 62 a 10 10 0 0 1 -10 10 h -64 a 10 10 0 0 1 -10 -10 v -62 z"/>
|
||||
<path d="M 12 75 q 9.5 10 19 0 t 19 0 19 0 19 0 v 10 q -9.5 -10 -19 0 t -19 0 -19 0 -19 0 z"/>
|
||||
<path d="M45 10 h 10 v 39 l 12 -12 7 7 -24 24 -24 -24 7 -7 12 12 z"/>
|
||||
</symbol>
|
||||
<symbol id="Laser">
|
||||
<rect x="0" y="0" width="60" height="90" fill="gray"/>
|
||||
<rect x="5" y="5" width="50" height="80" fill="white"/>
|
||||
<g transform="scale(0.9,1) skewY(10)">
|
||||
<line x1="10" y1="40" x2="82" y2="40" stroke-width="5" stroke="gray"/>
|
||||
<circle cx="88" cy="40" r="4" fill="gray"/>
|
||||
<g transform="translate(88,40)">
|
||||
<line x1="0" y1="-8" x2="0" y2="-16" stroke="gray" stroke-width="5" transform="rotate(-45)"/>
|
||||
<line x1="0" y1="-8" x2="0" y2="-16" stroke="gray" stroke-width="5" transform="rotate(0)"/>
|
||||
<line x1="0" y1="-8" x2="0" y2="-16" stroke="gray" stroke-width="5" transform="rotate(45)"/>
|
||||
<line x1="0" y1="-8" x2="0" y2="-16" stroke="gray" stroke-width="5" transform="rotate(90)"/>
|
||||
<line x1="0" y1="-8" x2="0" y2="-16" stroke="gray" stroke-width="5" transform="rotate(135)"/>
|
||||
<line x1="0" y1="-8" x2="0" y2="-16" stroke="gray" stroke-width="5" transform="rotate(180)"/>
|
||||
<line x1="0" y1="-8" x2="0" y2="-16" stroke="gray" stroke-width="5" transform="rotate(225)"/>
|
||||
</g>
|
||||
</g>
|
||||
<g transform="scale(0.8,1) skewY(20)">
|
||||
<rect x="0" y="0" width="60" height="90" fill="gray"/>
|
||||
<rect x="5" y="5" width="50" height="80" fill="white"/>
|
||||
<circle cx="48" cy="48" r="4" fill="gray"/>
|
||||
</g>
|
||||
</symbol>
|
||||
<symbol id="Control">
|
||||
<rect x="0" y="0" width="60" height="90" fill="gray"/>
|
||||
<rect x="5" y="5" width="50" height="80" fill="white"/>
|
||||
<g transform="translate(90,10) rotate(45)">
|
||||
<path d="M 0 0 l -10 22 10 10 -10 25 10 10 0 20 10 -22 -10 -10 10 -25 -10 -10 0 -20 z" stroke="gray" fill="gray"/>
|
||||
</g>
|
||||
<g transform="scale(0.8,1) skewY(20)">
|
||||
<rect x="0" y="0" width="60" height="90" fill="gray"/>
|
||||
<rect x="5" y="5" width="50" height="80" fill="white"/>
|
||||
<circle cx="48" cy="48" r="4" fill="gray"/>
|
||||
</g>
|
||||
</symbol>
|
||||
<g>
|
||||
<title>Control Panel</title>"
|
||||
#background
|
||||
<rect x="-87" y="-92.0" width="174" height="184" fill="black"/>
|
||||
#mounting tabs
|
||||
<rect x="57.0" y="-92.0" width="18" height="184" rx="9.0" ry="9.0" fill="gray"/>"
|
||||
<rect x="-75.0" y="-92.0" width="18" height="184" rx="9.0" ry="9.0" fill="gray"/>"
|
||||
#mounting holes for studs in control cabinet
|
||||
<circle cx="66" cy="83" r="3" fill="black"/>
|
||||
<circle cx="66" cy="-83" r="3" fill="black"/>
|
||||
<circle cx="-66" cy="83" r="3" fill="black"/>
|
||||
<circle cx="-66" cy="-83" r="3" fill="black"/>
|
||||
#panal flange with rounded corners
|
||||
<rect x="-87" y="-75" width="174" height="149" rx="22" ry="22" fill="gray"/>"
|
||||
#panal face with rounded corners
|
||||
<rect x="-84" y="-72" width="168" height="143" rx="19" ry="19" fill="white"/>"
|
||||
<circle cx="-55.05" cy="-43.05" r="19.95" fill="black"/>
|
||||
<circle cx="-38.05" cy="-25.499999999999996" r="1.5" fill="black"/>
|
||||
<circle cx="-72.05" cy="-25.499999999999996" r="1.5" fill="black"/>
|
||||
<rect x="-65.8" y="24.5" width="21.5" height="27.5" fill="black"/>
|
||||
<rect x="-73.35" y="-11.1" width="36.6" height="23.6" fill="black"/>
|
||||
<rect x="-28.75" y="-63.0" width="10" height="11.5" fill="black"/>
|
||||
<rect x="-9.7" y="-63.0" width="10" height="11.5" fill="black"/>
|
||||
<rect x="9.35" y="-63.0" width="10" height="11.5" fill="black"/>
|
||||
<rect x="28.4" y="-63.0" width="10" height="11.5" fill="black"/>
|
||||
<rect x="47.45" y="-63.0" width="10" height="11.5" fill="black"/>
|
||||
<rect x="66.5" y="-63.0" width="10" height="11.5" fill="black"/>
|
||||
<rect x="-28.75" y="-34.6" width="10" height="11.5" fill="black"/>
|
||||
<rect x="-9.7" y="-34.6" width="10" height="11.5" fill="black"/>
|
||||
<rect x="9.35" y="-34.6" width="10" height="11.5" fill="black"/>
|
||||
<rect x="28.4" y="-34.6" width="10" height="11.5" fill="black"/>
|
||||
<rect x="47.45" y="-34.6" width="10" height="11.5" fill="black"/>
|
||||
<rect x="66.5" y="-34.6" width="10" height="11.5" fill="black"/>
|
||||
</g>
|
||||
<g fill="black">
|
||||
<circle cx="-10" cy="4" r="5"/> # power level potentiometer
|
||||
<circle cx="-10" cy="44" r="6"/> # power auto-hand switch
|
||||
<circle cx="24" cy="44" r="6"/> # safety override switch
|
||||
<circle cx="56" cy="44" r="6"/> # manual fire switch
|
||||
</g>
|
||||
<g transform="scale(0.13,0.13)">
|
||||
<use transform="translate(-230.0,-380)" xlink:href="#Fan"/>
|
||||
<use transform="translate(-83.46,-380)" xlink:href="#Pump"/>
|
||||
<use transform="translate(63.08,-380)" xlink:href="#Temp"/>
|
||||
<use transform="translate(209.62,-380)" xlink:href="#Level"/>
|
||||
<use transform="translate(356.15,-380)" xlink:href="#Laser"/>
|
||||
<use transform="translate(502.69,-380)" xlink:href="#Control"/>
|
||||
</g>
|
||||
</svg>
|
||||
</nowiki>
|
||||
|
||||
[Category: CheapChineseLaser](Category:_CheapChineseLaser "wikilink")
|
||||
Executable
+43
@@ -0,0 +1,43 @@
|
||||
[CadSoft](http://www.cadsoftusa.com/) makes EAGLE, a popular piece of
|
||||
software for designing electrical circuits and laying out PCBs. It runs
|
||||
on Windows, Mac OS X, and Linux. There's a [free (as in beer)
|
||||
version](http://www.cadsoftusa.com/freeware.htm) available for
|
||||
non-profit use.
|
||||
|
||||
### Learning
|
||||
|
||||
#### Sparkfun Tutorial Series
|
||||
|
||||
- [Getting started with
|
||||
eagle](http://sparkfun.com/commerce/tutorial_info.php?tutorials_id=108)
|
||||
- [The basics of laying out a PCB with
|
||||
eagle](http://sparkfun.com/commerce/tutorial_info.php?tutorials_id=109)
|
||||
- [How to create a custom footprint & part in
|
||||
eagle](http://sparkfun.com/commerce/tutorial_info.php?tutorials_id=110)
|
||||
|
||||
#### Instructables
|
||||
|
||||
- [Draw Electronic Schematics with CadSoft
|
||||
EAGLE](http://www.instructables.com/id/Draw-Electronic-Schematics-with-CadSoft-EAGLE/)
|
||||
- [Turn your EAGLE schematic into a
|
||||
PCB](http://www.instructables.com/id/Turn-your-EAGLE-schematic-into-a-PCB/)
|
||||
- [Make hobbyist PCBs with professional CAD tools by modifying "Design
|
||||
Rules"](http://www.instructables.com/id/Make-hobbyist-PCBs-with-professional-CAD-tools-by-/)
|
||||
- [How to make a custom library part in Eagle CAD
|
||||
tool](http://www.instructables.com/id/How-to-make-a-custom-library-part-in-Eagle-CAD-too/)
|
||||
|
||||
### Parts Libraries
|
||||
|
||||
- [Sparkfun Eagle
|
||||
Library](http://www.opencircuits.com/SFE_Footprint_Library_Eagle)
|
||||
- [CadSoft's user-contributed
|
||||
libraries](http://www.cadsoftusa.com/cgi-bin/download.pl?page=/home/cadsoft/html_public/download.htm.en&dir=eagle/userfiles/libraries)
|
||||
- [Adafruit Eagle
|
||||
Library](http://github.com/adafruit/Adafruit-Eagle-Library/blob/master/adafruit.lbr)
|
||||
|
||||
### User Language Programs (ULPs)
|
||||
|
||||
- [epscdraw_411.ulp](ftp://ftp.cadsoft.de/eagle/userfiles/ulp/epscdraw_411.ulp)
|
||||
outputs color EPS (encapsulated PostScript). Handy for printing
|
||||
|
||||
[Category:Useful_Info](Category:Useful_Info "wikilink")
|
||||
Executable
+85
@@ -0,0 +1,85 @@
|
||||
- By default, access is denied.
|
||||
- Traffic destined for anywhere but to a select few services (i.e., TCP
|
||||
or UDP ports) is blocked by the local firewall.
|
||||
- NTP
|
||||
- IMAP(S)
|
||||
- POP(S)
|
||||
- OpenVPN
|
||||
- IPsec
|
||||
- HTTP(S) traffic caught by firewall, redirected to the mesh node's
|
||||
client IP and port.
|
||||
- **iptables -t nat -A PREROUTING -i wlan0 -p tcp --dport 80 -j
|
||||
REDIRECT --to-port 31337**
|
||||
- **iptables -t nat -A PREROUTING -i wlan0 -p tcp --dport 443 -j
|
||||
REDIRECT --to-port 31338**
|
||||
- We'd have to add an extra bit in there **--destination 10.x.x.1**
|
||||
- A web server listening on the redirect ports (31337/TCP and 31338/TCP)
|
||||
uses URI rewriting to point everything to a special URI:
|
||||
|
||||
` <VirtualHost *:31337>`
|
||||
` RewriteEngine On`
|
||||
` RewriteRule .* `[`https://byzantium.mesh/`](https://byzantium.mesh/)` [R,L]`
|
||||
` `</VirtualHost>
|
||||
` `
|
||||
` <VirtualHost *:31338>`
|
||||
` RewriteEngine On`
|
||||
` RewriteRule .* `[`https://byzantium.mesh/`](https://byzantium.mesh/)` [R,L]`
|
||||
` `</VirtualHost>
|
||||
|
||||
- The web server listening on ports 31337/TCP and 31338/TCP serves a
|
||||
page to the client. The client reads the text ("This is a wireless
|
||||
mesh, stuff about OPSEC, click here to pass through to the directory
|
||||
of services.") and clicks a button.
|
||||
- It'd be nice if the page also optionally displayed a message "There
|
||||
is a gateway to the public Net, so you can browse outside of this
|
||||
mesh." if a gateway route existed and had been propagated.
|
||||
- When the button is clicked the firewall is updated to permit that MAC
|
||||
address to send traffic.
|
||||
- **[ipset](http://ipset.netfilter.org/) -A capo_sessions_ipset
|
||||
CLIENT_IP,CLIENT_MAC**
|
||||
- Yes, MAC spoofing to bypass this is trivial. This isn't to prevent
|
||||
people from getting online if they don't have a valid room number,
|
||||
it's to force them to see a message from the admin and then kick
|
||||
them over to a directory of services curated by the node's software.
|
||||
- Set a timeout on the client IP? 10 minutes? 60 minutes? 5 minutes
|
||||
(same as DHCP lease time)?
|
||||
- **ipset -D capo_sessinos_ipset CLIENT_IP**
|
||||
- Captive::Portal includes a script (capo-ctl.pl) which already does
|
||||
this. In fact, you're supposed to run it from cron every ten minutes
|
||||
or so to clean out idle sessions.
|
||||
- Captive::Portal requires iptables (have it), ipset (need to compile
|
||||
and install it), and a rule in */etc/sudoers* so it can run without
|
||||
privileges but still carry out privileged tasks.
|
||||
- fping is used to test idle sessions (have it).
|
||||
- A CGI script that implements a captive portal is included in
|
||||
Captive::Portal, it's called capo.cgi and runs under Apache.
|
||||
- Basics of coding with this module:
|
||||
|
||||
` my $capo = Captive::Portal->new(cfg_file=>$cfg_file);`
|
||||
` while (my $eq = CGI::Fast->new){`
|
||||
` $capo->run($q);`
|
||||
` }`
|
||||
|
||||
- capo-ctl.pl is included with the module and manipulates the currently
|
||||
running IPtables rules (as well as backing store of Captive::Portal)
|
||||
with the ipset utility
|
||||
- Everything Captive::Portal relies on the same configuration file (by
|
||||
default, config.pl).
|
||||
- mock-server.pl is a script that pulls the HTML from a URI (say, a web
|
||||
server listening on wlan0) and spits it to stdout for testing.
|
||||
- Used for testing your setup without needing a client.
|
||||
- test-server.pl implements a very simple HTTP server so you can test
|
||||
your capi.cgi script without having to configure Apache.
|
||||
|
||||
<!-- -->
|
||||
|
||||
- We might have to modify capo.cgi to use the DBI Perl module to access
|
||||
the SQLite databases that hold the directories of services users can
|
||||
reach.
|
||||
- We may have either modify or subclass the Captive::Portal class and
|
||||
add support for extracting and using the IP address of the client
|
||||
interface (wlan0:1) rather than just the physical interface (wlan0).
|
||||
It's been a long time since I've done OO under Perl but it's certainly
|
||||
possible.
|
||||
- config.pl should be configured for no authentication (i.e., just a
|
||||
click-through).
|
||||
Executable
+48
@@ -0,0 +1,48 @@
|
||||
## Build-A-CTF
|
||||
|
||||
Join us to create unique hacking CTF competitions meeting **every Sunday
|
||||
at the HacDC Space**. Sign up for events at
|
||||
[Meetup.com](https://www.meetup.com/hac-dc/events/291602998/).
|
||||
|
||||
As per Wikipedia, "A Capture the Flag (CTF) in computer security is an
|
||||
exercise in which "flags" are secretly hidden in purposefully-vulnerable
|
||||
programs or websites. It can either be for competitive or educational
|
||||
purposes. Competitors steal flags either from other competitors
|
||||
(attack/defense-style CTFs) or from the organizers (jeopardy-style
|
||||
challenges)."
|
||||
|
||||
### Goals
|
||||
|
||||
Our first CTF aims to achieve the following goals:
|
||||
|
||||
1. Be a *learning experience*, for both the organizers and participants
|
||||
2. Be *beginner-friendly*, open and accessible to first-time
|
||||
participants
|
||||
3. Be *fun, engaging, and encouraging* to newcomers to explore the
|
||||
wider world of cybersecurity
|
||||
|
||||
## Design
|
||||
|
||||
Based on the above goals, we have decided to design our first
|
||||
competition in the style of \[
|
||||
<https://en.wikipedia.org/wiki/King_of_the_hill_(game)> King of the
|
||||
Hill\] (KotH). A participant wins the event upon maintaining the sole
|
||||
login session on the target machine for 30 **uninterrupted** minutes.
|
||||
Participants may use any exploit to establish a session on the target
|
||||
machine, but are only allowed to patch the exploit that they used to
|
||||
enter upon establishing a session. It is in the interest of the present
|
||||
King to monitor the machine for sessions established by other teams, and
|
||||
to continue to research exploits in the event that they are dethroned by
|
||||
an opposing team.
|
||||
|
||||
### Architecture
|
||||
|
||||
The environment will be developed in [GNS3](https://gns3.com/), a
|
||||
virtualization software that enables the CTF organizers to construct a
|
||||
purely software-based network, all within a single VM! VMs inside a VM,
|
||||
a.k.a. VM-ception.
|
||||
|
||||
<figure>
|
||||
<img src="Example_GNS3.png" title="Example_GNS3.png" />
|
||||
<figcaption>Example_GNS3.png</figcaption>
|
||||
</figure>
|
||||
Executable
+45
@@ -0,0 +1,45 @@
|
||||
# Overview
|
||||
|
||||
In order to begin [biomaterials](:Category:Biomaterials "wikilink")
|
||||
testing, GrindDC needs a realistic implant test platform. The
|
||||
implantable cardiac pacemaker was chosen as the first project because it
|
||||
is:
|
||||
|
||||
- easily implemented
|
||||
- cheap to produce
|
||||
- small
|
||||
- can easily utilize inductive power
|
||||
|
||||
# Status
|
||||
|
||||
Implant is early in the design phase.
|
||||
|
||||
# Goals
|
||||
|
||||
## Inductive Power
|
||||
|
||||
Inductive power is a core feature that will be implemented in all future
|
||||
designs for primary power or recharging of implanted power supply.
|
||||
|
||||
The pacemaker test platform should implement:
|
||||
|
||||
- inductive power recharge (with battery)
|
||||
- inductive power only operation (without battery)
|
||||
- easily replaced inductors
|
||||
|
||||
## Small Size / Inexpensive
|
||||
|
||||
To accomplish the [biomaterials](:Category:Biomaterials "wikilink")
|
||||
testing goals the pacemaker reference implant will need to be small in
|
||||
area to facilitate cheap production of the printed circuit boards.
|
||||
Additionally, the required parts should be minimized in number and cost.
|
||||
|
||||
## Functional
|
||||
|
||||
Using a simulated cardiac cell model, the pacer should regulate the
|
||||
circuit when Artrial-Ventricular block is simulated. The chosen cardiac
|
||||
model is described in *Synchronization with low power consumption of
|
||||
hardware models of cardiac cells* (Maeda, Yagi, Makino;
|
||||
2005[1](http://dx.doi.org/10.1016/j.biosystems.2004.09.005)).
|
||||
|
||||
[Category:Implants](Category:Implants "wikilink")
|
||||
Executable
+47
@@ -0,0 +1,47 @@
|
||||
<figure>
|
||||
<img src="Pic081908_3.jpg" title="Pic081908_3.jpg" />
|
||||
<figcaption>Pic081908_3.jpg</figcaption>
|
||||
</figure>
|
||||
|
||||
Our cash register is a Sharp XE-A203 ([quickstart
|
||||
guide](:media:Cas_qguide_XEA203.pdf "wikilink"), [full
|
||||
manual](:media:Cas_man_XEA203.pdf "wikilink")).
|
||||
|
||||
## How to Use the Cash Register
|
||||
|
||||
Before beginning, make sure that the key is set to the *Reg* position.
|
||||
If you want a receipt, turn the key to the *OP X/2* position and hit the
|
||||
<span style="color:salmon">**RCPT/PO**</span> key.
|
||||
|
||||
1. Hit the <span style="color:salmon">**ESC**</span> key in the lower
|
||||
left-hand corner.
|
||||
2. If you're a HacDC member, hit the **1** key in the Amount/Clerk
|
||||
Keys. Otherwise—i.e., if you're a guest—hit the **2** key in the
|
||||
Amount/Clerk Keys.
|
||||
3. Hit the **CL** key in the Amount/Clerk Keys.
|
||||
4. Enter the amount of your purchase on the Amount/Clerk Keys. DO NOT
|
||||
USE THE DECIMAL KEY. For example, to enter 50 cents, press the **5**
|
||||
key then the **0** key on the Amount/Clerk Keys.
|
||||
5. Under Department Keys, hit the appropriate department key, according
|
||||
to the table below. If you have multiple items to ring up, repeat
|
||||
steps 4 and 5.
|
||||
6. Press the <span style="color:lightseagreen">**CA/AT/NS**</span> key
|
||||
in the bottom right-hand corner.
|
||||
7. Put in your money and close the drawer!
|
||||
|
||||
## Departments
|
||||
|
||||
| Department code | Description |
|
||||
|-----------------|----------------------|
|
||||
| **R** | Refreshments |
|
||||
| **2** | Donations |
|
||||
| **3** | Member Dues |
|
||||
| **4** | Bulk Parts |
|
||||
| **5** | Tools |
|
||||
| **6** | Equipment |
|
||||
| **7** | Clothing |
|
||||
| **8** | Salvage Buy |
|
||||
| **9** | Stickers and patches |
|
||||
| **10** | Other |
|
||||
|
||||
Cash register department codes
|
||||
Executable
+22
@@ -0,0 +1,22 @@
|
||||
This is a list of wiki entries I (Bobby) have created (including old
|
||||
ones): <http://wiki.hacdc.org/index.php/Area_science_event_info> -
|
||||
"instruction manual" for Area science event list
|
||||
<http://wiki.hacdc.org/index.php/Area_science_event_list>
|
||||
<http://wiki.hacdc.org/index.php/Documentation-ATmega_microcontroller> -
|
||||
attempt to write instructions for the ATmega328P microcontroller
|
||||
<http://wiki.hacdc.org/index.php/Documentation-CAD>
|
||||
<http://wiki.hacdc.org/index.php/Documentation-Computer_network>
|
||||
<http://wiki.hacdc.org/index.php/Documentation-HacDC_equipment> -
|
||||
telephone, printer, etc.
|
||||
<http://wiki.hacdc.org/index.php/Documentation-Laser_cutter-K40>
|
||||
<http://wiki.hacdc.org/index.php/Documentation-Tabletop_computers>
|
||||
<http://wiki.hacdc.org/index.php/Documentation-3D_printer_computer>
|
||||
<http://wiki.hacdc.org/index.php/Documentation-3D_printer-Mini>
|
||||
<http://wiki.hacdc.org/index.php/Documentation-3D_printer-Rostock>
|
||||
<http://wiki.hacdc.org/index.php/Documentation-3D_printer-Ultimaker>
|
||||
<http://wiki.hacdc.org/index.php/Hacdc_log> - what happened at HacDC
|
||||
<http://wiki.hacdc.org/index.php/Inventory-space-by-Bobby>
|
||||
<http://wiki.hacdc.org/index.php/Objects> - ImplicitCAD (.escad) files
|
||||
for objects
|
||||
<http://wiki.hacdc.org/index.php/TV_shows_that_may_be_of_interest>
|
||||
<http://wiki.hacdc.org/index.php/TV_shows_that_may_be_of_interest_-_weekly>
|
||||
Executable
+532
@@ -0,0 +1,532 @@
|
||||
**WARNING: Working on the laser cutter poses hazards far beyond anything
|
||||
many people have encountered.**
|
||||
|
||||
- The laser beam can blind instantly. It is invisible. It can reflect
|
||||
unexpectedly. Operating the laser with the cover open (normally
|
||||
blocked) is a really bad idea.
|
||||
- The laser runs off of high power high voltage. Unlike household
|
||||
current this can kill you even if you just come close to it. Think
|
||||
lightning-in-a-box. Always turn the power switch off and unplug the
|
||||
plug at the back of the laser cutter (so you know it's the right one)
|
||||
before working on it. In addition, high voltage power supplies can
|
||||
hold a charge after they've been turned off so you can still get
|
||||
zapped for a while after everything's been shut off. If at all in
|
||||
doubt get expert advice.
|
||||
- Freak accidents happen.
|
||||
- On the other hand, just using the laser cutter poses far less risk.
|
||||
Take standard precautions.
|
||||
|
||||
[Cheap Chinese Laser](Cheap_Chinese_Laser "wikilink")
|
||||
|
||||
This is the page dealing with the [Cheap Chinese
|
||||
Laser](Cheap_Chinese_Laser "wikilink") at [HacDC](https://www.hacdc.org)
|
||||
in the upstairs room at St. Stephen and the Incarnate church in
|
||||
Washington, DC. This page replaces [PA
|
||||
LaserCutter](PA_LaserCutter "wikilink") page from some years ago. It had
|
||||
high ideals, but poor execution.
|
||||
|
||||
## Introduction
|
||||
|
||||
HacDC has a K40, 40W, CO2, water cooled, laser for CNC cutting of
|
||||
various materials, aka a cheap Chinese laser. It allegedly used to work
|
||||
just fine, but someone decided that wasn't good enough so she ordered
|
||||
and half-ass installed some new parts that only half-ass work. After our
|
||||
intrepid hero, [James](user:James "wikilink"), fully-assed the
|
||||
installation of the new parts, the laser still only half-ass worked.
|
||||
[Tom](user:Tom "wikilink") was railroaded into helping with the
|
||||
software, but even so the dynamic duo couldn't get the damn thing to
|
||||
work. Then one day at work, boredom struck in a meeting and James had
|
||||
the idea to create this wiki page to guide others through the confusion
|
||||
and misinformation that plagues most equipment at HacDC and often
|
||||
results in subpar operation. I beseech you, dear reader, to continue
|
||||
your edification on our topic at hand and become your own evil
|
||||
arch-villain with laser powers. (Sharks sold separately.)
|
||||
|
||||
## Components
|
||||
|
||||
### Chassis
|
||||
|
||||
The chassis is the laser itself, the blue metal box with 3 flip up lids.
|
||||
|
||||
- The main lid users deal with is for the **cutting chamber** on the
|
||||
left front of the machine. It includes an orange plastic window. The
|
||||
cutting chamber contains the transverse and longitudinal axes, aka X
|
||||
and Y. X goes left to right, and Y goes back to front. The material to
|
||||
be cut goes in this chamber.
|
||||
- The second flip up lid is for the **controls and power supplies
|
||||
chamber**. This lid contains the front panel controls and indicators.
|
||||
There are two control boards, the [Smoothie
|
||||
board](http://smoothieware.org/smoothieboard-v1) and the K40 ACR
|
||||
plug-and-play board which connects the Smoothie board to the machine
|
||||
hardware. There are two power supplies as well, the control power
|
||||
supply which is right below the control boards and the high-voltage
|
||||
(and I mean real high voltage, like around 15kV, not those namby-pamby
|
||||
B.S. 120VAC "high voltage" warning labels) laser tube power supply
|
||||
which creates enough voltage to excite the electrons in the CO2
|
||||
molecules to a higher energy level so they emit coherent light when
|
||||
they drop down to a lower energy level. For more about this exciting
|
||||
process, read a science book.
|
||||
- The third lid covers the **laser tube chamber** at the back of the
|
||||
chassis. You don't really need to mess with these last two lids unless
|
||||
you are modifying the equipment or troubleshooting a failure. The
|
||||
first 2 lids have interlock switches so the laser will not fire if any
|
||||
one is open (unless you turn the SAFETIES switch off, in which case,
|
||||
it's your own darn fault for burning out your eye; as we say in
|
||||
Charlotte, "you did it to yourself") but the laser tube cover does not
|
||||
yet (it should; the high voltage is probably the most dangerous thing
|
||||
in the space).
|
||||
|
||||
### Exhaust
|
||||
|
||||
The exhaust system sucks smoke from the laser chassis cutting chamber
|
||||
and sends it outside through a window. It was cobbled together using a
|
||||
fan and housing salvaged from a prior laser cutter and is mostly held
|
||||
together with zipties and metal duct tape. Seriously. I'm not kidding.
|
||||
Actual zipties and duct tape. (I'd like to give a shout-out to Home
|
||||
Depot for selling me the roll of metal tape for only one cent.) If any
|
||||
part of the whole laser system is going to crap out, this would be a
|
||||
good part to bet on. It also uses 4" diameter (that's 105mm for those of
|
||||
you on the metric system) flexible metal clothes dryer exhaust duct to
|
||||
carry the exhaust gasses. There are custom-made, 3d-printed transiton
|
||||
pieces at the back of the laser chassis which replace the original
|
||||
feeble exhaust system. Read about them on the [K40 Exhaust
|
||||
Assembly](K40_Exhaust_Assembly "wikilink") page.
|
||||
|
||||
### Cooling
|
||||
|
||||
The cooling system presently consists of a 5 gallon pail in the roller
|
||||
cabinet with a submersible pump. The water should be replaced with
|
||||
distilled. (The pump power cord got a new plug. It stays plugged in much
|
||||
better than the original cheap Chinese plug.) If the water doesn't flow,
|
||||
the laser will burnout. Sadness. The cooling system presently only works
|
||||
based on the heat capacity of the water in the bucket. Once the water
|
||||
heats up, you just need to wait for it to cool back down all by itself.
|
||||
You can read about other people with more sophisticated refrigerated
|
||||
cooling systems, but this was quick and easy, like a virgin on prom
|
||||
night. Julia has mentioned she's got some thermoelectric coolers in
|
||||
hiding for this project. We'll cross that bridge when we get everything
|
||||
else running first. The cooling system will have 3 interlocks: low water
|
||||
level, low flow, and high temperature.
|
||||
|
||||
### Computer
|
||||
|
||||
This is CNC equipment. The first C is for Computer. (No, not for cookie,
|
||||
but we often have cookies anyway.) You need a computer with a USB port.
|
||||
You need computer software. I hope we can have a computer dedicated to
|
||||
the laser, but let's be real, that's not likely to happen. I hope Tom
|
||||
will fill out this section.
|
||||
|
||||
### Software
|
||||
|
||||
Hey, kids! [Ubuntourist](user:Ubuntourist "wikilink") here. In the
|
||||
software department, we are using a
|
||||
[LaserWeb](https://github.com/LaserWeb/LaserWeb4/wiki) AppImage
|
||||
(currently version 4.0 as of 2018.09). However, additional tools
|
||||
include:
|
||||
|
||||
- [VisiCut](http://visicut.org/) - a user-friendy, platform-independent
|
||||
tool for preparing, saving and sending jobs to Lasercutters
|
||||
- [GCodeTools](http://www.cnc-club.ru/forum/viewtopic.php?t=35) -
|
||||
Inkscape plugin / extension
|
||||
- [Usage
|
||||
"Manual"](http://www.cnc-club.ru/forum/viewtopic.php?p=101#p101)
|
||||
- [Tutorial: Area
|
||||
processing](http://www.cnc-club.ru/forum/viewtopic.php?p=341#p341)
|
||||
- [Tutorial: Make some gears using Gcode tools and Gear
|
||||
extension](http://www.cnc-club.ru/forum/viewtopic.php?p=194#p194)
|
||||
|
||||
### Cabinet
|
||||
|
||||
The cabinet is what the chassis sits on. The cabinet has wheels. It's
|
||||
made of particle board and painted white. The left door has upper and
|
||||
lower latches inside which hold it shut, so don't yank on it. The
|
||||
cabinet houses the cooling system, the 12V accessory power supply, the
|
||||
power strip which all the line voltage equipment plugs into: exhaust
|
||||
fan, cooling pump, laser chassis, 12V power supply (marginal one
|
||||
installed currently to power the cutting chamber accessory lights).
|
||||
|
||||
## Safety Interlocks
|
||||
|
||||
**Only some of these safeties (cutting chamber cover, control cover, &
|
||||
water level) are installed presently.** Don't go futzing around with
|
||||
stuff unless you know exactly what you are doing. And tell James or Tom.
|
||||
For troubleshooting purposes, there is a safety override switch on the
|
||||
control panel (SAFETIES; middle of three).
|
||||
|
||||
### Ventilation
|
||||
|
||||
1. Exhaust - If the exhaust fan isn't moving air, we don't want the
|
||||
laser to fire and make lots of smoke which would then fill the room
|
||||
2. Lens - Eventually we plan to install an air shroud nozzle around the
|
||||
laser lens to keep smoke from coating the lens and reducing cutting
|
||||
power.
|
||||
|
||||
### Coolant
|
||||
|
||||
1. Level - Installed
|
||||
2. Flow
|
||||
3. Temp
|
||||
|
||||
### Doors
|
||||
|
||||
1. Cutting Chamber - Installed
|
||||
2. Control Chamber - Installed
|
||||
3. Laser Chamber - Probably not going to install this switch because
|
||||
the door is in back and control panel space is at a premium
|
||||
4. Cabinet - Probably not going to install this switch because there's
|
||||
not much harm in the cabinet and control panel space is at a premium
|
||||
|
||||
## Workflow
|
||||
|
||||
### Prestart
|
||||
|
||||
1. Come up with design
|
||||
2. Create SVG using software like [Inkscape](https://inkscape.org/)
|
||||
3. Upload SVG to computer
|
||||
|
||||
### Startup
|
||||
|
||||
1. Roll cabinet out from under shelf
|
||||
2. Get extension cord out of cabinet and plug laser into extension cord
|
||||
and extension cord into live receptacle
|
||||
3. Turn on laser master power switch (power strip inside the wooden
|
||||
cabinet)
|
||||
4. Close cabinet door
|
||||
5. Load material to be cut in cutting chamber
|
||||
6. Shut lid on cutting chamber
|
||||
7. Turn on laser cutter power switch
|
||||
|
||||
### Operations
|
||||
|
||||
1. Ensure all safety interlocks are operable by checking indicator
|
||||
lights
|
||||
1. You can skip this step for now since the lights don't work
|
||||
2. Do software stuff
|
||||
1. Connect to LaserWeb server at [192.168.26.122 Port
|
||||
8000](http://192.168.26.122:8000/) from HacDC network
|
||||
2. Clear LaserWeb 4 upgrade warning popup
|
||||
3. Click on Settings on left edge of page
|
||||
4. Click on BACKUP at top of setting pane
|
||||
5. Click on Restore from file
|
||||
6. Upload
|
||||
|
||||
file
|
||||
7. Click Save
|
||||
8. Observe messages "Saved Settings" and "Please refresh page for
|
||||
settings to take effect"
|
||||
9. Refresh webpage
|
||||
10. Clear LaserWeb 4 upgrade warning popup, again
|
||||
11. Load SVG file of cutting paths by dragging and dropping into the
|
||||
web browser window
|
||||
12. Click Generate G-Code (on CAM menu)
|
||||
13. Click Connect at the top of the webpage
|
||||
14. If a popup appears, choose Option 1
|
||||
15. Click Jog on left edge of the window
|
||||
16. Click home and observe the gantry move to the home position in
|
||||
the far left corner of the cutting chamber
|
||||
3. Run program without laser powered on to observe tool path and ensure
|
||||
material to be cut is properly arranged in the cutting chamber
|
||||
1. Click check outline and observe the laser move
|
||||
1. Check that material is fully under the travel area
|
||||
2. Check that your design is the size you expect it to be (25.4
|
||||
for mm)
|
||||
3. If the size is not right, go to the Settings page and adjust
|
||||
the DPI setting on the Size menu
|
||||
4. Run program with laser powered on to cut material
|
||||
1. Click run gcode
|
||||
2. Watch for things catching fire
|
||||
|
||||
### Shutdown
|
||||
|
||||
1. Turn off laser chassis and master power switches
|
||||
2. Unplug laser and extension cord
|
||||
3. Coil up and store extension cord
|
||||
4. Shut cabinet door
|
||||
5. Roll cabinet back under the shelf
|
||||
6. Continue with your evil plans for world domination
|
||||
|
||||
## Custom Wiring
|
||||
|
||||
Julia had some LED strips she wanted installed. We succeeded. They
|
||||
illuminate when the main power is turned on.
|
||||
|
||||
|
||||
They are white LEDs but the orange laser viewing window colors them.
|
||||
|
||||
<figure>
|
||||
<img src="Laser-leds2.jpg" title="File:Laser-leds2.jpg" />
|
||||
<figcaption><a
|
||||
href="File:Laser-leds2.jpg">File:Laser-leds2.jpg</a></figcaption>
|
||||
</figure>
|
||||
|
||||
Sully really likes relays and discrete, analogue circuits, so he jimmied
|
||||
up a bunch of stuff to make it less likely for you to poke your eye out
|
||||
or burn out the laser.
|
||||
|
||||
The laser power supply from the factory takes input from 3 front panel
|
||||
controls: off-on laser switch, momentary-on laser switch, power control
|
||||
potentiometer knob. The off-on switch was a cheap latching push button
|
||||
which was connected to the leftmost two terminals of the 6 terminal plug
|
||||
with black wires. It was replaced with an off-on, metal, toggle switch
|
||||
on 3-23-17. The middle two terminals of the block connect to the
|
||||
momentary on push button switch on the front panel which causes the
|
||||
laser to fire (when the left two terminals are shorted together by the
|
||||
toggle switch). The right 3 terminals (which overlap with the right
|
||||
center terminal going to the push button switch) connect to the front
|
||||
panel potentiometer which controls the laser current. Do not turn the
|
||||
knob to full clockwise, because increasing the laser firing current past
|
||||
a certain point doesn't provide any benefit and just reduces the tube
|
||||
lifespan. The plan is to parallelize the push button firing switch with
|
||||
a solid-state relay controlled directly by the Smoothie board and
|
||||
bypassing the K40 ACR board (which was supposed to make the Smoothie
|
||||
board plug-and-play, but as mentioned earlier did a halfassed job). The
|
||||
potentiometer will be connected to a 3PDT switch for computerized or
|
||||
manual power level control. A PWM to DC circuit will do the automatic
|
||||
control and the original pot will remain for the manual control.
|
||||
|
||||
The safety interlocks are basically a whole bunch of microswitches in
|
||||
series so if any one of them gets tripped the left two pins of the power
|
||||
supply 6 pin connector won't be shorted together and the laser won't
|
||||
fire. There's also a plan to have lights illuminate to show which
|
||||
safeties are operating properly or tripped. Plus indicator lights are
|
||||
cool. And for the remaining manual firing switches we plan on getting
|
||||
those flip-up red covers like in those military movies where they're
|
||||
firing nuclear missiles and stuff like that. These would aid in
|
||||
troubleshooting, and look really cool, even if they are kinda spendy.
|
||||
Man, this is really turning into a wall of text. Someone should do
|
||||
something about this sometime. Anyway, schematic drawings would go here,
|
||||
or links to them would go here.
|
||||
|
||||
**Terminal Block Connections**
|
||||
|
||||
1. Cutting chamber door safety switch - common
|
||||
2. Cutting chamber door safety switch - n.o.
|
||||
3. Cutting chamber door safety switch - n.c.
|
||||
4. Control chamber door safety switch - common
|
||||
5. Control chamber door safety switch - n.o.
|
||||
6. Control chamber door safety switch - n.c.
|
||||
7. Cooling water level float safety switch - common
|
||||
8. Cooling water level float safety switch - n.o.
|
||||
9. Cooling water level float safety switch - n.c.
|
||||
10.
|
||||
11.
|
||||
12.
|
||||
13.
|
||||
14.
|
||||
15. 12VDC / Cutting Chamber LED positive
|
||||
16. Hour meter / 12VDC / Cutting Chamber LED ground
|
||||
17. Hour meter positive
|
||||
18. Laser fire switch positive - shorts to ground (below) to fire laser
|
||||
19. Laser power supply power level control potentiometer GND
|
||||
20. Auto power control voltage divided between +V and GND - connects to
|
||||
auto-hand control panel switch and to PWM-DC converter circuit
|
||||
output
|
||||
21. Laser power supply power level control potentiometer +V
|
||||
|
||||
| Connectors at front of bottom power supply (4, 6, & 4 connections) |
|
||||
|--------------------------------------------------------------------|
|
||||
| Position |
|
||||
| Left |
|
||||
| |
|
||||
| |
|
||||
| |
|
||||
| Center |
|
||||
| |
|
||||
| |
|
||||
| |
|
||||
| |
|
||||
| |
|
||||
| Right |
|
||||
| |
|
||||
| |
|
||||
| |
|
||||
| Connectors at front of middle power supply are labeled |
|
||||
| |
|
||||
| |
|
||||
| |
|
||||
| |
|
||||
| |
|
||||
| |
|
||||
| |
|
||||
| |
|
||||
|
||||
## Custom Parts
|
||||
|
||||
Images of custom parts like the exhaust nozzles and eventually a new
|
||||
control panel and source files for 3d printed or laser cut parts can go
|
||||
here.
|
||||
|
||||
[CCL front panel](CCL_front_panel "wikilink")
|
||||
|
||||
[Air flow switch holder](Air_flow_switch_holder "wikilink")
|
||||
|
||||
[Exhaust nozzle](Exhaust_nozzle "wikilink")
|
||||
|
||||
[Terminal block holder](Terminal_block_holder "wikilink")
|
||||
|
||||
This image is colored for 3d printing using it as a height map:
|
||||
black=0mm, gray=1mm, white=2mm. 174mm wide, 184mm tall. The SVG file was
|
||||
created by a Ruby program to modularize the positions and sizes of
|
||||
cutouts for switches, knobs, lamps, etc.
|
||||
|
||||
<figure>
|
||||
<img src="Control-panel.png" title="file:Control-panel.png" />
|
||||
<figcaption><a
|
||||
href="file:Control-panel.png">file:Control-panel.png</a></figcaption>
|
||||
</figure>
|
||||
|
||||
## Bill of Materials, a.k.a. Donation Wishlist, and Hardware Store Shopping List
|
||||
|
||||
1. Laser goggles
|
||||
2. USB A-B cord, i.e. printer cable, which doesn't suck
|
||||
3. Solid state relays -- we used
|
||||
[1](http://www.clare.com/home/pdfs.nsf/www/LBA110.pdf/$file/LBA110.pdf)
|
||||
this one. --This should move to custom parts and off the wishlist
|
||||
(JS 4-20).
|
||||
4. Stuff to cut
|
||||
1. 1/8" Baltic birch plywood
|
||||
2. Plastic sheets, e.g. acrylic
|
||||
3. Masonite?
|
||||
5. Cabinet reinforcements
|
||||
1. dimensional lumber, e.g. 2x4, 2x2, 1x3
|
||||
2. unidirectional casters
|
||||
6. Cooling system stuff
|
||||
1. Distilled water
|
||||
2. Float switch
|
||||
3. Thermocouple or thermistor/RTD temperature sensor probe
|
||||
4. Radiator and fans
|
||||
5. Solid state heat pump
|
||||
6. Working water fountain chiller (for future use on the 100W
|
||||
downstairs)
|
||||
7. PLC/Microcontroller with A/D inputs for temperature probe
|
||||
conditioning and temp display (advanced task)
|
||||
7. Green connectors for smoothieboard and laser power supply
|
||||
[2](https://www.amazon.com/uxcell-Terminals-Pitch-Mount-Terminal/dp/B00E6Q4FE6/ref=sr_1_9?ie=UTF8&qid=1493691567&sr=8-9&keywords=pluggable+terminal+block+connector)
|
||||
|
||||
## To-Do Tasks
|
||||
|
||||
1. Airflow switch housing
|
||||
1. manufacture
|
||||
2. install
|
||||
2. Coolant interlocks
|
||||
1. Flow sensor
|
||||
1. design
|
||||
2. manufacture
|
||||
3. install
|
||||
2. Temp sensor
|
||||
1. design
|
||||
2. manufacture
|
||||
3. install
|
||||
3. Door switches
|
||||
1. Cabinet door
|
||||
2. Laser tube chamber door
|
||||
4. Chassis wiring
|
||||
1. Wire up the safety switches as they are installed
|
||||
2. Draw a wiring diagram of custom components
|
||||
5. CNC firing control - This svg file can be used to test run the
|
||||
laser: [Laser circle test](Laser_circle_test "wikilink")
|
||||
1. find firing signal on Smoothie board
|
||||
2. in the config you specify this with laser_module_ttl_pin
|
||||
3. determine relay requirements
|
||||
4. purchase and receive relay
|
||||
5. install firing relay
|
||||
6. software
|
||||
1. determine best software to use
|
||||
2. develop workflows for various programs and operating systems
|
||||
3. update this page to explain the above
|
||||
4. We're gonna use Laserweb I think so setup a RasPi or something
|
||||
as a Laserweb server.
|
||||
5. backup the raspi so when the sdcard fails we don't have to
|
||||
rebuild it.
|
||||
|
||||
## Completed Tasks
|
||||
|
||||
If you do work on the laser, please record it here.
|
||||
|
||||
| Task | Fixer | Date | Notes |
|
||||
|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------|------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|
||||
| Create Wiki page | [James](user:James "wikilink") | 3/24/2017 | Ongoing updates needed |
|
||||
| Install operational exhaust system | James | 2/2017 | Still needs interlocks |
|
||||
| Install cooling system | James | 2/2017 | Air cooling or refrigeration could be added |
|
||||
| Connect control power supply to switched mains | James | 3/2017 | Done |
|
||||
| Get x and y axis movements working | [Tom](user:Tom "wikilink") | 3/2017 | Firing still needs to be fixed |
|
||||
| Replaced cooling pump power cord plug | James | 3/26/2017 | |
|
||||
| Installed door closure bolts on left cabinet door | James | 3/26/2017 | |
|
||||
| Installed cutting chamber illumination LEDs and 12VDC power supply | James | 3/26/2017 | |
|
||||
| Control + interlock circuits design/brainstorm session | James + Tom | 3/27/2017 | See webpages below for Smoothieboard help |
|
||||
| Mocked up and tested control circuit for PWM from smoothieboard | James + Tom | 3/27/2017 | <http://smoothieware.org/laser-cutter-guide> |
|
||||
| Scoped out various pins on the smoothieboard to find PWM out | James + Tom | 3/27/2017 | <http://smoothieware.org/smoothieboard-v1> |
|
||||
| Removed control panel | James | 3/30/17 | Don't mess with nothing until a new one gets installed! |
|
||||
| Tried to 3d print a new control panel | James | 4/2/17 | Lulzbot Taz either didn't extrude or made bird poop. :( It's too bad we don't have a working laser cutter. |
|
||||
| Adjusted program size parameters based on failed print and added ammeter mounting screw holes to control panel design | James | 4/11/17 | Still need to upload new SVG here and print it |
|
||||
| Ordered self adhesive cable tie mounting squares and SSR for PWM-\> DC | Tom | 4/11/17 | Delivery expected Thursday |
|
||||
| Design 3d-printed mounting bracket/clip to hold switches for door interlocks | James + Tom | 4/15/17 | Impromptu Saturday night productivity session. |
|
||||
| Design, breadboard and test PWM circuit with solid state relay and newly determined time constant | James + Tom | 4/15/17 | Impromptu Saturday night productivity session. |
|
||||
| Uploaded exhaust nozzle and exhaust flow switch scad files | James | 4/20/17 | Flow switch needs printing and Tom's nacelle needs dimension tweeking. |
|
||||
| Tried printing control panel on the Ultimaker<sup>2</sup> | James | 4/25/17 | Print failed twice, but third time looked good before I left. |
|
||||
| Installed control panel 3d printed on Tuesday | James | 4/27/17 | Controls and indicators are installed but not operational, yet. It looks sweet! Could be thicker, maybe 4mm. Dimensions could use tweeking too: toggle switches moved down, corner radii reduced,... |
|
||||
| Uploaded source code and stl for water level float switch and for terminal block holders. Installed v5 of door switch holder and soldered wires to switches. | James | 5/1/17 | Still need to print float switch parts and terminal block holders. New parts fit well. A very productive day overall. |
|
||||
| Installed terminal block with manually modified v1 terminal block holder parts. Wired up cutting chamber and control chamber door safety switches. Connected laser power supply wiring to new control panel switches. | James | 5/4/17 | Need to adjust terminal block holder dimensions and reprint. |
|
||||
| Uploaded v2 source code and stl for terminal block holder. | James | 5/5/17 | Need to print float switch parts and terminal block holders. |
|
||||
| Printed and installed new terminal block holders (v2). Printed new air flow switch and water level float switch head and base. Remodeled exhaust header. | James | 5/6/17 | Holders fit great. Base, not so much. |
|
||||
| Reprinted water level float switch base. Investigated PWM output from Smoothieboard. | James + Tom | 5/7/17 | Pin 4.2 and GND work for PWM signal. PWM to DC breadboard isn't working. Laser power supply 5V circuit for safety switches doesn't have enough current to illuminate the trouble lamps on front panel. |
|
||||
| Install float switch. | James | 5/11/17 | Not seeming to function as of 5/14 - remains conductive even when open? |
|
||||
| Successful CNC laser firing on circle laser test. | James + Tom | 5/14/17 | Some kind of beam splitting or 2-layer reflection is going on. PWM out can be set using laser_module_pwm_pin in smoothieboard config. |
|
||||
| Setup the auto-man power level control switch. General stuff. | James + Tom | 5/28/17 | We've got some stray AC current in the case. |
|
||||
| Installed RasPI as webhost. Replaced USB cable. | James + Tom | 6/4/17 | [Laserweb server](http://192.168.26.122:8000/), from HacDC network |
|
||||
| Test cut Pepe the frog on opaque acrylic with painters tape mask. | James + [Andrew](user:Andrew "wikilink") | 6/5/17 | Auto fire signal still isn't working. |
|
||||
| Added circuitry to breadboard to automate the firing signal. | James | 6/6/17 | Will test on Thursday. |
|
||||
| Test fire was successful. Operations section updated. | James | 6/8/17 | Fully automatic operations achieved! |
|
||||
| Unsuccessful work to connect hour meter. | James | 6/11/17 | Don't use laser for now. I'm waiting on some parts to make a soldered accessory board. |
|
||||
| Strip boards arrived and I fabbed a circuit card to control the power, fire the laser, and drive the hour meter. It still needs to be connected and tested. | James | 6/17/17 | Don't use laser for now. Accessory board needs testing. |
|
||||
| After several rounds of testing, the problem with the board is still undetermined. SSRs might be fried. Tom is researching bulk buy. Thanks, Tom. | James | 6/22/17 | Laser only works with manual fire and power control. |
|
||||
| Work on firing up the laser directly from smoothieboard pinouts PWM and TTL. TTL (1.30) to Laser LO and PWM (2.4) to 5v control. Problem: PWM out looks like it is 3.3v logic. Problem: TTL needs to drive the hourmeter. | Tom + Forrest | 8/1/2017 | Configured TTL in config and changed PWM period to 20 from 200. DANGER: LASER FIRES AT ALL TIMES WHEN CONNECTED TO PWM. |
|
||||
| Fix issue with leaky voltage or improper configuration why does the laser fire too much | Oni | 08/10/2017 | Attached manual fire ground. Removed and put-back small laser fire wire and ground to the smoothieboard. This appeared to fix laser autofire issue. Not 100% sure about that. Removed 2nd and 3rd mirror to find them damaged. Took photos and sought advice on their state. Put mirrors back in place but alignment is needed. Best to wait for new mirrors in the meantime. |
|
||||
| Alignment and knackered mirrors | Oni | 08/28/2017 | Removed mirror 2 and 3, replacing with new mirrors. Mirror 1 should probably be checked at some point as well. Adjusted the alignment on mirrors 1 and 2. Reduced the torque on the adjustment screws to 'finger-tight'. Alignment on 3rd mirror is dead centre across the entire bed. This should improve cutting power across the entire range. Might be worth ordering another set of spare mirrors and a lens for future repairs. Laser appears to fire correctly, respecting interlocks and fire control. |
|
||||
|
||||
Sept. 1, 2018 - Independent examination revealed multiple issues: 1.
|
||||
Closed loop in wiring - resolved (A loop can act like a transformer and
|
||||
couple noise into the wiring.) Removed. 2. AUTO/MAN switch did not
|
||||
affect control of laser firing, only laser current - partially resolved
|
||||
(This may explain unexpected firing of laser.) Rewired so FIRE switch
|
||||
has no effect in AUTO mode and controller cannot fire laser while in MAN
|
||||
mode. However, setting switch on MAN does not stop the controller; it
|
||||
can continue moving the mirrors and could resume firing the laser the
|
||||
instant the switch is returned to AUTO. Therefore, always HALT AUTOMATIC
|
||||
OPERATION BEFORE USING MANUAL CONTROL. 3. A loose connection around the
|
||||
Laser Current meter could result in deadly high voltage appearing in the
|
||||
control circuitry - resolved Added shunt diode to clamp voltage to \<1V.
|
||||
4. Interlock switches not connected - resolved Connected (cutting
|
||||
chamber door, electronics cover, water level). Terminal block positions
|
||||
10 & 11 are allocated for additional switches. 5. Missing interlock
|
||||
switches - not resolved (laser tube cover, water flow, & water
|
||||
temperature) New wiring is color coded (but old wiring is not): Black -
|
||||
ground connection Green - safety switches White - control & temporary
|
||||
Some of the wiring is rather sloppy and should probably be redone once
|
||||
all the bugs are out of it. A loose wire to the power socket & the
|
||||
exhaust duct (may have just come loose) were also reconnected. The laser
|
||||
cutter should now be ready for testing by an expert. Oops, left out 6.
|
||||
No manual control for laser position - unresolved Sept. 3 Tom showed up
|
||||
to test the laser cutter. It fired under manual control but the safeties
|
||||
did not stop it from firing. Tried other firing pin (C3) - same result.
|
||||
Completely disconnected wire to enable pin (C2) & then also tried
|
||||
disconnecting the diode I added - laser still fired, suggesting faulty
|
||||
power supply. Laser did not move in y direction when commanded by
|
||||
computer but moved in both x & y when commanded to move in x direction.
|
||||
Tom moved a connector on the ACR board - problem solved. Mirrors now
|
||||
move correctly under computer control but computer could not fire laser.
|
||||
Left with enable disconnected. Time to examine power supply schematic.
|
||||
|
||||
## Additional Reading
|
||||
|
||||
1. [Laser blog](http://howell.seattle.wa.us/essays/lasercutter.shtml)
|
||||
2. [Reddit K40 wiki](https://www.reddit.com/r/lasercutting/wiki/k40)
|
||||
3. [Light Object laser
|
||||
retailer](http://www.lightobject.com/Default.aspx)
|
||||
|
||||
[Category:Equipment](Category:Equipment "wikilink")
|
||||
[Category:LaserCutter](Category:LaserCutter "wikilink")
|
||||
[Category:Projects](Category:Projects "wikilink") [Category:Ongoing
|
||||
Projects](Category:Ongoing_Projects "wikilink") [Category:Project
|
||||
Awesome](Category:Project_Awesome "wikilink")
|
||||
[Category:CheapChineseLaser](Category:CheapChineseLaser "wikilink")
|
||||
Executable
+9
@@ -0,0 +1,9 @@
|
||||
The circuit breaker for the space is located on the last landing before
|
||||
you go up to the top floor. There are two circuit breaker boxes, we use
|
||||
the one on the right.
|
||||
|
||||
Known circuits:
|
||||
|
||||
`#32 - HacDC hallway, ham radio`
|
||||
|
||||
[Category:Circuit Breaker](Category:Circuit_Breaker "wikilink")
|
||||
Executable
+40
@@ -0,0 +1,40 @@
|
||||
HacDC will create a series of curriculum for classes that can be taught
|
||||
on a regular basis. It'd be neat if we could create kits to teach
|
||||
classes from and maybe even Kickstarter them if they get an appropriate
|
||||
level of polish.
|
||||
|
||||
## Past Classes
|
||||
|
||||
Here are the wiki resources for our previous classes at HacDC:
|
||||
|
||||
- [AVR Microcontroller Class
|
||||
2011](AVR_Microcontroller_Class_2011 "wikilink")
|
||||
- [Bike Maintenance Class](Bike_Maintenance_Class "wikilink")
|
||||
- [ElectronicsClass](ElectronicsClass "wikilink")
|
||||
- [FPGA Workshop](FPGA_Workshop "wikilink")
|
||||
- [Robotics Class 2011](Robotics_Class_2011 "wikilink")
|
||||
- [Noisemaker Workshop](Noisemaker_Workshop "wikilink")
|
||||
- [Microcontroller Course](Microcontroller_Course "wikilink")
|
||||
- [Linux Class](Linux_Class "wikilink")
|
||||
- [Introduction to Python](Introduction_to_Python "wikilink")
|
||||
- [TECS](TECS "wikilink")
|
||||
- [NARG](NARG "wikilink")
|
||||
- [Intro to Programming](Intro_to_Programming "wikilink")
|
||||
- [IntrotoVisualsforProgrammers](IntrotoVisualsforProgrammers "wikilink")
|
||||
|
||||
## Class Roster
|
||||
|
||||
Please fill in what classes you're interested in, want to teach or have
|
||||
resources for.
|
||||
|
||||
| Class | Teacher | Links |
|
||||
|----------------------------|------------------------|--------------------------------------------------------------------------------------------|
|
||||
| Electronics | Justin Myers, Ash | [First stab at a syllabus, parts list and cost breakdown](Intro_to_Electronics "wikilink") |
|
||||
| RF Theory | Lee Ciereszko | |
|
||||
| Linux (New Users) | Brad Barr, Paul Fields | |
|
||||
| Linux (SysAdmin) | James Dasinger | |
|
||||
| HTML/CSS | Alli R | |
|
||||
| Microcontrollers (Arduino) | Brad Barr | |
|
||||
| Programming (Python) | Brad Barr, Bryce | |
|
||||
|
||||
[Category:Classes](Category:Classes "wikilink")
|
||||
Executable
+86
@@ -0,0 +1,86 @@
|
||||
This page serves as a specification and feature request page for the
|
||||
classroom laptops.
|
||||
|
||||
The classroom laptops are running a Linux distribution, currently Debian
|
||||
(probably better to be running testing than stable), with MATE desktop
|
||||
environment. Tom maintains a canonical image.
|
||||
|
||||
They are used primarily for modeling, rendering, and slicing 3d printed
|
||||
parts, but can and should be functional for all purposes in the
|
||||
classroom.
|
||||
|
||||
Currently implemented on a bunch (6) of Dell D430s, maybe some D420s.
|
||||
|
||||
## Hardware
|
||||
|
||||
I (Tom) donated 6 old Dell Core Duo D430/420 laptops for this use.
|
||||
They're super cheap and I had a pile of them. I think they're actually
|
||||
kind of ideal for this purpose, all things considered. They're not nice
|
||||
enough that anybody would want to re-purpose them to any other job, and
|
||||
since most of them don't have batteries nobody walks off with them.
|
||||
After almost a year they seem to be doing the job and getting lots of
|
||||
use.
|
||||
|
||||
## Software (locally installed or remote access)
|
||||
|
||||
### 3d design
|
||||
|
||||
- Cura
|
||||
- Meshlab
|
||||
- Implicitcad (runs on Jobs or gygax)
|
||||
|
||||
### Browsers
|
||||
|
||||
- Firefox
|
||||
- Chromium
|
||||
- Midori or something similarly lightweight.
|
||||
|
||||
### Microcontroller
|
||||
|
||||
- INO
|
||||
- Arduino
|
||||
|
||||
### Coding
|
||||
|
||||
- Python 3
|
||||
- Rust
|
||||
|
||||
### Productivity
|
||||
|
||||
- Something for email
|
||||
- Printing should be enabled
|
||||
|
||||
### Sys utils
|
||||
|
||||
- tmux ssh vi/vim emacs etc.
|
||||
- Terminator
|
||||
- guake
|
||||
- most
|
||||
- avahi-utils
|
||||
|
||||
### Other HacDC activities
|
||||
|
||||
Documentation, links, and how-tos on the desktop...
|
||||
|
||||
## TODO
|
||||
|
||||
- Update image and re-image all laptops.
|
||||
- Enable all laptops for incoming and outgoing email...?
|
||||
- Fix the HW clock issue possibly by setup NTP so that SSL errors don't
|
||||
happen.
|
||||
- Work out a way to do efficient X-forwarding over our WiFi to job
|
||||
server for heavier applications.
|
||||
- Configure laptops in some way to be more like a thin client so there
|
||||
is no/less need to 'update' the image or re-image regularly. In the
|
||||
dumbest case we could have them be simple VNC kiosks to a VM running
|
||||
on jobs...?
|
||||
- Test above last two for practicality.
|
||||
|
||||
## Feature requests
|
||||
|
||||
- Most recent Arduino suite. \[INO\]
|
||||
- More scripts and or instructions for usability -- 2d printing, 3d
|
||||
printing, using jobs.
|
||||
- Maybe put ~/\* or ~/Desktop on a network share.
|
||||
|
||||
[Category:HacDC Computers](Category:HacDC_Computers "wikilink")
|
||||
Executable
+43
@@ -0,0 +1,43 @@
|
||||
# Goals
|
||||
|
||||
World peace. Also:
|
||||
|
||||
- A laser cutting device.
|
||||
- A 3D Printer.
|
||||
- A pick and place and solder paste and laser soldering machine.
|
||||
- PCB fab through resist application, laser resist removal, and etchant
|
||||
application.
|
||||
- Air flow controls
|
||||
- forcing air down (cooling a 3d print)
|
||||
- pulling air across and out (laser cutting)
|
||||
|
||||
# Tools
|
||||
|
||||
In order of priority.
|
||||
|
||||
- Laser(s?). For cutting.
|
||||
- A single plastic extruder, for 3d printing.
|
||||
- A part lifting nozzle, for pick and place functionality. --
|
||||
<http://www.robotdigg.com/product/517/Nozzle+w/+Adapter+to+5mm+Hollow+Shaft+Stepper>
|
||||
- Epson ink jet head, for Liquid Deposition (PCB resist)
|
||||
- Unknown, for etchant deposition.
|
||||
|
||||
# Parts
|
||||
|
||||
- 40w computer controlled power
|
||||
supply.[1](http://www.made-in-china.com/showroom/eileen916/product-detailqMfJZAkdrvYy/China-40W-Laser-Power-Supply.html)
|
||||
|
||||
# Constraints
|
||||
|
||||
## Julia
|
||||
|
||||
Three separate rackmount components:
|
||||
|
||||
- laser delivery platform
|
||||
- Motion control platform
|
||||
- Part delivery platform
|
||||
|
||||
<!-- -->
|
||||
|
||||
- Rackmountable footprint. ~17 inches wide, ~24 inches deep.
|
||||
<http://www.server-racks.com/eia-310.html>
|
||||
Executable
+143
@@ -0,0 +1,143 @@
|
||||
The Classroom TV is hooked up to various PCs.
|
||||
|
||||
Once we repair'd it by exhaustively testing each LED on the device and
|
||||
replacing the broken one.
|
||||
|
||||
## The TV
|
||||
|
||||
The current TV is a 60-inch **Sharp Aquos LC-60LE920UN**.
|
||||
|
||||
Manual is available at
|
||||
<http://files.sharpusa.com/Downloads/ForHome/HomeEntertainment/LCDTVs/Manuals/tel_man_LC52_60LE920UN.pdf>
|
||||
|
||||
<https://www.youtube.com/watch?v=rhSiDx5P9s4>
|
||||
|
||||
It should be labeled appropriately for ease of use. There is a remote
|
||||
control. If the screen won't come on and the little LED logo at the
|
||||
bottom middle blinks instead of coming on solid, reset according to
|
||||
instructions on the device.
|
||||
|
||||
Sometimes when there's a problem, it displays a constant small blue box
|
||||
which reads **\[K\] 60LE810UN** which the careful reader will note looks
|
||||
remarkably like a model number...
|
||||
|
||||
### Resetting the TV
|
||||
|
||||
<http://www.fixya.com/support/t17617780-60_sharp_aquos_power_indicator_flashing>
|
||||
|
||||
POWER LIGHT FLASHES ONE SHORT AND ONE LONG FLASH.
|
||||
|
||||
What is the problem? THE PROBLEM IS THAT ONE OF THE LED's STRIPS IS BAD!
|
||||
|
||||
SHARP AQUOS LC60LE810UN RESET INSTRUCTIONS
|
||||
|
||||
` 1. Plug in TV to electric current First then wait until LED start flashing.`
|
||||
` 2. Press Volume DOWN [ - ] HOLD BUTTON.`
|
||||
` 3. Press Channel UP [ ^ ] HOLD BUTTON.`
|
||||
` 4. Press Power [ (') ] HOLD ALL three buttons until LED stops flashing and then release.`
|
||||
|
||||
This will reset the TV in order to fix the problem.
|
||||
|
||||
THE FIX IS TO REPLACE ONE OF THE LED's. You need to open the back of the
|
||||
TV and you will also need to remove the front cover and panel to get to
|
||||
the LEDs. The TV will need to be placed facedown and on the backside.
|
||||
This is a 2 person job to turn the TV on its sides. Be careful with the
|
||||
white computer connectors (wide white strip) at the base of the TV where
|
||||
the TV stand sits. You will need to disconnect this in order to get to
|
||||
the LED's.
|
||||
|
||||
Once you have the LED's exposed, you will need to unplug one by one by
|
||||
placing the new strip next to it until the unit turns on. You will have
|
||||
to use the RESET procedure above if the Power lite flashes. The Power
|
||||
lite MUST BE ON SOLID - no blinking in order to test the strips. The
|
||||
LED's will flash, but still one of them will be burned. Even if you
|
||||
stare and all the strip light-up, you will still need to check
|
||||
one-by-one!
|
||||
|
||||
Once the TV lights up, your face will also light up with joy! Put
|
||||
everything back together and you are set. If you need the complete
|
||||
instructions which come from Sharp as to how to disassemble the unit,
|
||||
please send me an e-mail to LGTR61@YAHOO.ES. Please note I don't check
|
||||
this address daily, so a few days wait may take for you to receive the
|
||||
instructions.
|
||||
|
||||
Where can you buy the LED's - try searching Yahoo.com or Google.com for
|
||||
resellers.
|
||||
|
||||
SHARP AQUOS LC60LE810UN LCD STRIP INFORMATION
|
||||
|
||||
` LONG STRIP (49 LED's)`
|
||||
` FRONT SIDE BACK SIDE RL 94v-0`
|
||||
` E329419`
|
||||
` 1029`
|
||||
` LFa`
|
||||
` Sn-Ag-Cu`
|
||||
` Ps-1`
|
||||
` K4458TP`
|
||||
` 4458ZZ`
|
||||
` 0921FM`
|
||||
` 104863`
|
||||
` ee03A`
|
||||
|
||||
` SHORT STRIP (30 LED's)`
|
||||
` FRONT SIDE BACK SIDE`
|
||||
` RL 94v-0`
|
||||
` E329419`
|
||||
` 1025 LFa`
|
||||
` Sn-Ag-Cu`
|
||||
` Ps-1`
|
||||
` K4459TP`
|
||||
` 4459ZZ`
|
||||
` 0714FM`
|
||||
` 302213`
|
||||
` Mm05A `
|
||||
|
||||
Posted on Dec 11, 2013
|
||||
|
||||
SOURCE:
|
||||
|
||||
No POWER
|
||||
|
||||
How many times does the POWER led flash per second? (Dont worry about
|
||||
the OPC).
|
||||
|
||||
` * 1x (steady constant blink) = Lamps or inverters`
|
||||
` * 2x = Power Supply`
|
||||
` * 3x = Main Unit`
|
||||
|
||||
If i am reading it correctly, looks like the POWER led is flashing 2x,
|
||||
which means it is a power supply failure. Either way, your TV needs to
|
||||
have a board replaced, there isn't anything you can do to fix it
|
||||
yourself. Try locating your local sharp authorized service center to
|
||||
repair your TV (1-800-237-4277)
|
||||
|
||||
Posted on Mar 16, 2008
|
||||
|
||||
## The PCs
|
||||
|
||||
### Windows VR box
|
||||
|
||||
(it's grody and uses proprietary poison).
|
||||
|
||||
### Classroom TV
|
||||
|
||||
(highly superior build -- uses Debian Linux, a free software
|
||||
distribution, although we have compromised to allow non-free software
|
||||
and firmware).
|
||||
|
||||
2018-02-27 21:29 <thossou> something's up with the GPU on the classroom tv what for it won't work
|
||||
2018-02-27 21:30 <thossou> but the fans turn
|
||||
2018-02-27 21:30 <thossou> http://dlcdnet.asus.com/pub/ASUS/mb/LGA1366/Sabertooth_X58/e5995_sabertooth_X58.pdf#p55
|
||||
|
||||
## Instructions for use
|
||||
|
||||
### How to remotely control the classroom-tv PC
|
||||
|
||||
(copy from the desktop of classroom PC)
|
||||
|
||||
### How to use VR
|
||||
|
||||
### How to run a videoconference with another space using BBB
|
||||
|
||||
[Category:Room Displays](Category:Room_Displays "wikilink")
|
||||
[Category:HacDC Computers](Category:HacDC_Computers "wikilink")
|
||||
Executable
+74
@@ -0,0 +1,74 @@
|
||||
(The following diagram is available as an 8.5" x 11" page in DjVu
|
||||
format. Click it to go to the downloadable image page and click that to
|
||||
get a full-size image)
|
||||
|
||||
### Network diagram
|
||||
|
||||
 *Diagram of classroom
|
||||
network devices and cables,
|
||||
traced and documented by Bobby circa 2019.03.18*
|
||||
|
||||
------------------------------------------------------------------------
|
||||
|
||||
The following text is almost verbatim from Bobby's e-mail message. I
|
||||
have attempted basic formatting but it could use more reformatting work
|
||||
(probably as a wiki table) to make it readable.
|
||||
|
||||
On floor below clock:
|
||||
|
||||
Netgear ProSAFE 16-Port Gigabit Click Switch
|
||||
1 - gray - TP-Link Router 2
|
||||
2 - gray - Printer (paper) computer
|
||||
14 - white - open (by laser cutter)
|
||||
16 - orange - renderadmin computer
|
||||
others - no connection
|
||||
|
||||
On bottom shelf over sink:
|
||||
|
||||
LinkSys VOIP Voice
|
||||
Phone - phone cable - Uniden EX18560 phone
|
||||
Internet - blue - LinkSys switch 6
|
||||
|
||||
C7 TP-Link AC1750 Wireless Dual-Band Gigabit Router
|
||||
Internet - blue - D-Link switch
|
||||
Ethernet 1 - gray - open
|
||||
2 - yellow - TP-Link switch 7
|
||||
|
||||
On middle shelf over sink:
|
||||
|
||||
D-Link Wireless AC750 Dual-Band Router DIR-817LW
|
||||
LAN 4 - blue - TP-Link switch 8
|
||||
Internet - gray - LinkSys switch 5
|
||||
|
||||
TP-Link TL-SG1008D Gigabit Switch
|
||||
(Numbering from left to right)
|
||||
1 - yellow - wall socket
|
||||
2 - gray - Netgear switch 1
|
||||
3 - blue - 3D printer computer
|
||||
4 - no connection
|
||||
5 - black - Linksys switch 1
|
||||
6 - no connection
|
||||
7 - yellow - TP-Link router Ethernet 2
|
||||
8 - blue - D-Link router LAN 4
|
||||
|
||||
Linksys Gigabit 8-Port Workgroup Switch
|
||||
(Numbering from right to left)
|
||||
1 - black - TP-Link switch 5
|
||||
2 - no connection
|
||||
3 - gray - open (below HARC)
|
||||
4 - black - open (below HARC)
|
||||
5 - gray - D-Link router Internet
|
||||
6 - blue - Linksys VOIP Voice Internet
|
||||
7 - blue - open (below HARC)
|
||||
8 - no connection
|
||||
|
||||
On table below TV screen:
|
||||
|
||||
D-Link igreen DGS-1005D switch
|
||||
1 - blue - TP-Link router Internet
|
||||
2 - gray - open
|
||||
3 - no connection
|
||||
4 - no connection
|
||||
5 - yellow - TV computer
|
||||
|
||||
If I read this right 3 of the 4 switches are unnecessary!
|
||||
Executable
+54
@@ -0,0 +1,54 @@
|
||||
The discussion list for this project is neighborhoodwireless@hacdc.org.
|
||||
Proposal
|
||||
|
||||
The Columbia Heights Wireless Project aims to provide wireless access to
|
||||
the Internet to HacDC's neighbors in Columbia Heights. This project, in
|
||||
three phases, will help test different technologies and methods for
|
||||
providing this access as well as building local neighborhood IT
|
||||
infrastructure. Phase One: Rewire St. Stephen's Church
|
||||
|
||||
St. Stephen's Church is used by many community organizations, each of
|
||||
which are responsible for obtaining their own Internet and Telephone
|
||||
service.
|
||||
|
||||
There are potential costs savings for the church and its tenants to
|
||||
upgrade the IT infrastructure of the facility, allowing the church and
|
||||
tenants to share common Internet access and Telephone service.
|
||||
|
||||
After assessing the needs of the church, its tenants and occasional
|
||||
guests from out of town, HacDC will draft a plan to re-wire the
|
||||
telecommunications and networking infrastructure of the church.
|
||||
|
||||
` * Replace the IT wiring infrastructure of the church.`
|
||||
` o Run house cable to church office and basement and other key areas of the church, reducing need for cabling on the outside of the building and/or expansive cable runs within the building`
|
||||
` o Install wired outlets in offices and other places they may be necessary`
|
||||
` o Run wire to ares where wireless access points may be deployed`
|
||||
` * Provide building wide Internet access`
|
||||
` o Replace multiple DSL lines with one solid, very high speed internet connection`
|
||||
` o Install building router to handle and segregate internet connection`
|
||||
` o Provide church and its tenants with private subnet`
|
||||
` o Provide wired network access to tenants who require it`
|
||||
` o Provide infrastructure for building-wide wireless network`
|
||||
` * Build church wireless network`
|
||||
` o Provide private wireless networks to tenants who require it`
|
||||
` o Provide public wireless network for church and tenant guests, etc.`
|
||||
|
||||
As of June 20, 2009 this phase is almost entirely complete. Phase Two:
|
||||
Provide Wireless to the Housing Project Surrounding the Church
|
||||
|
||||
Once the hurdles of providing wireless to a given area (the church) are
|
||||
handled, the goal is to extending the public church network to the
|
||||
housing project which surrounds the church. The goals of this project
|
||||
are relatively less complex:
|
||||
|
||||
` * Provide public wireless accessible in all rooms of the development around the church`
|
||||
` * Work with community members on best methods for building and supporting a public wireless network`
|
||||
` * Deploy specialized equipment on the roof of the church and possibly on the development property`
|
||||
` * Work out technical challenges present in extending the public network beyond church immediate line-of-sight`
|
||||
|
||||
Phase Three: Provide Wireless to Neighborhood Buildings
|
||||
|
||||
` * Provide public wireless available throughout Columbia Heights`
|
||||
` * Attract public and government support to make such a public wireless network viable and sustainable`
|
||||
|
||||
[Category:Previous Projects](Category:Previous_Projects "wikilink")
|
||||
Executable
+147
@@ -0,0 +1,147 @@
|
||||
The discussion list for this project is
|
||||
[neighborhoodwireless@hacdc.org](http://hacdc.org/mailman/listinfo/neighborhoodwireless_hacdc.org).
|
||||
|
||||
# Proposal
|
||||
|
||||
This project, in its current form, will be announced at the June 17
|
||||
member meeting
|
||||
|
||||
The Columbia Heights Wireless Project aims to provide wireless access to
|
||||
the Internet to HacDC's neighbors in Columbia Heights. This project, in
|
||||
three phases, will help test different technologies and methods for
|
||||
providing this access as well as building local neighborhood IT
|
||||
infrastructure.
|
||||
|
||||
## Phase One: Rewire St. Stephen's Church
|
||||
|
||||
St. Stephen's Church is used by many community organizations, each of
|
||||
which are responsible for obtaining their own Internet and Telephone
|
||||
service.
|
||||
|
||||
There are potential costs savings for the church and its tenants to
|
||||
upgrade the IT infrastructure of the facility, allowing the church and
|
||||
tenants to share common Internet access and Telephone service.
|
||||
|
||||
After assessing the needs of the church, its tenants and occasional
|
||||
guests from out of town, HacDC will draft a plan to re-wire the
|
||||
telecommunications and networking infrastructure of the church. Prior to
|
||||
consultation with the tenants (this consultation meeting is scheduled
|
||||
for June 13) this phase has the following goals:
|
||||
|
||||
- Replace the IT wiring infrastructure of the church.
|
||||
- Remove all "dead cables" from the exterior and interior of the
|
||||
church
|
||||
- Run house cable to church office and basement and other key areas of
|
||||
the church, reducing need for cabling on the outside of the building
|
||||
and/or expansive cable runs within the building
|
||||
- Replace the demarc with more modern equipment (should be done by
|
||||
Verizon)
|
||||
- Install wired outlets in offices and other places they may be
|
||||
necessary
|
||||
- Run wire to ares where wireless access points may be deployed
|
||||
- Provide building wide Internet access
|
||||
- Replace multiple DSL lines with one solid, very high speed internet
|
||||
connection
|
||||
- Install building router to handle and segregate internet connection
|
||||
- Provide church and its tenants with private subnet
|
||||
- Provide wired network access to tenants who require it
|
||||
- Provide infrastructure for building-wide wireless network
|
||||
- Build church wireless network
|
||||
- Provide private wireless networks to tenants who require it
|
||||
- Provide public wireless network for church and tenant guests, etc.
|
||||
- Integrate church security system into building wide network
|
||||
- Replace existing church security and entry system (see also
|
||||
[Physical_Access_Control_Project](Physical_Access_Control_Project "wikilink"))
|
||||
- Provide method for tenants to view persons outside the building and
|
||||
allow building access
|
||||
|
||||
## Phase Two: Provide Wireless to the Housing Project Surrounding the Church
|
||||
|
||||
Once the hurdles of providing wireless to a given area (the church) are
|
||||
handled, the goal is to extending the public church network to the
|
||||
housing project which surrounds the church. The goals of this project
|
||||
are relatively less complex:
|
||||
|
||||
- Provide public wireless accessible in all rooms of the development
|
||||
around the church
|
||||
- Work with community members on best methods for building and
|
||||
supporting a public wireless network
|
||||
- Deploy specialized equipment on the roof of the church and possibly on
|
||||
the development property
|
||||
- Work out technical challenges present in extending the public network
|
||||
beyond church immediate line-of-sight
|
||||
|
||||
## Phase Three: Provide Wireless to Neighborhood Buildings
|
||||
|
||||
- Provide public wireless available throughout Columbia Heights
|
||||
- Attract public and government support to make such a public wireless
|
||||
network viable and sustainable
|
||||
|
||||
------------------------------------------------------------------------
|
||||
|
||||
# Implementation
|
||||
|
||||
A meeting was held with the church coordinator and a few tenants on
|
||||
Friday, June 13th, to assess the needs and scope of the project. As
|
||||
outlined above, it looks quite viable, with a few considerations:
|
||||
|
||||
All the tenants we met with are currently using some form of DSL or
|
||||
dialup access. They'd all be happy with a plain vanilla shared
|
||||
connection, using whatever sort of upstream we find appropriate. One
|
||||
tenant (CISPES) uses VoIP phones, and at least one other (Brainfood)
|
||||
uses Skype heavily, so QoS factors (latency, jitter) are important.
|
||||
|
||||
Telephone needs were also discussed. Most tenants have POTS lines into
|
||||
their spaces, with a few using cellular phones exclusively, and one
|
||||
using VoIP, as mentioned above. There's at least one FAX line. The POTS
|
||||
customers weren't averse to going VoIP at some point in the future, as
|
||||
long as they can keep their existing numbers.
|
||||
|
||||
As for security, it'd be nice to distribute front-door video to each
|
||||
space and provide tenants with an intercom and a way to buzz guests into
|
||||
the building. This would let the church go down to a nighttime guard
|
||||
only, saving the cost of the daytime guard.
|
||||
|
||||
In my (Nate B) professional judgment, the voice and video projects
|
||||
should be considered separately from the data project, except where it
|
||||
would be wise to combine cabling installation. Running a PBX is a wholly
|
||||
separate set of administration skills and maintenance considerations.
|
||||
Likewise, assembling a video distribution network and interfacing with
|
||||
the door lock system is a separate job, only related because it also
|
||||
involves running wire in the building.
|
||||
|
||||
Since inexpensive baluns are available to transmit video over a single
|
||||
pair of UTP, a single additional run of Cat-5 to each space should be
|
||||
adequate to support the access project. Since wire is cheap compared to
|
||||
labor (even volunteer labor, trust me!), I don't think there's any such
|
||||
thing as pulling "too many" drops into each space. Leave the unused ones
|
||||
coiled and tagged in the ceiling if need be, but run extra cable now.
|
||||
|
||||
The next steps for the first phase, then, are as follows:
|
||||
|
||||
- Formally present this project at the next HacDC meeting and get member
|
||||
approval and buy-in.
|
||||
- Obtain, or draw, floor plans of the building. Scope out good cable
|
||||
routes, be they inside walls, above drop ceilings, or held in surface
|
||||
wiring raceways.
|
||||
- Perform a site-survey to ascertain the RF propagation characteristics
|
||||
of the church building. Plaster lath walls are notorious for eating
|
||||
wifi signals.
|
||||
- Determine whether it's appropriate to do everything as a home-run to a
|
||||
single closet, or to have "vertical" house-cables that appear on each
|
||||
floor. (I like home runs. --Nate B.)
|
||||
- Pick a location for a wiring closet. In addition to patch panels, it
|
||||
should be able to hold (and provide cooling for) a moderate amount of
|
||||
infrastructure gear: A DSL modem, a router, an Ethernet switch or two,
|
||||
a midspan PoE injector, a video distribution amplifier, a small PBX,
|
||||
and whatever lock control system gets built. A bit of room for growth
|
||||
would be good, to allow for scope creep.
|
||||
- Solicit donations of wire, jacks, accesspoints, and the above
|
||||
infrastructure gear.
|
||||
- Evaluate potential upstream connections. Nick mentioned that
|
||||
point-to-point microwave access may be available in our location.
|
||||
Consider multi-homing the network, if financially practical.
|
||||
- Contact community members who'd be interested in helping the project
|
||||
and learning to maintain and administer the network.
|
||||
|
||||
[Category:Proposed Projects](Category:Proposed_Projects "wikilink")
|
||||
Executable
+4
@@ -0,0 +1,4 @@
|
||||
[CommonStupidMan.Com](http://commonstupidman.com) is overseen by
|
||||
Shahnawaz Sadique. He expounds on specialty site business, programming,
|
||||
topics, wp modules audit. He is know subsidiary advertiser and item
|
||||
launcher.
|
||||
Executable
+109
@@ -0,0 +1,109 @@
|
||||
Our general communications policy is simple:
|
||||
|
||||
1. Pick a system that works to facilitate communication
|
||||
2. Use it
|
||||
3. Don't change it unless it's failing.
|
||||
|
||||
## E-Mail
|
||||
|
||||
E-mail is the most common method of communication within HacDC and
|
||||
between HacDC and the outside world.
|
||||
|
||||
### Public E-mail Lists
|
||||
|
||||
Our public lists, which anyone can sign up for, are:
|
||||
|
||||
- [announce@hacdc.org](http://hacdc.org/mailman/listinfo/announce_hacdc.org)
|
||||
: A moderated, weekly update list designed to keep the general public
|
||||
informed about what's happening, what's been discussed and what's
|
||||
coming up at HacDC.
|
||||
- [blabber@hacdc.org](http://hacdc.org/mailman/listinfo/blabber_hacdc.org)
|
||||
: Our completely unmoderated and public open discussion forum covering
|
||||
a wide range of topics and questions.
|
||||
|
||||
### Public POC E-mail
|
||||
|
||||
All inquiries from the outside world, via e-mail, should go to
|
||||
[bod@hacdc.org](bod@hacdc.org "wikilink").
|
||||
|
||||
[bod@hacdc.org](bod@hacdc.org "wikilink") may be used within the web
|
||||
page, wiki, on documents, flyers, etc. as a way for those outside HacDC
|
||||
to contact the organization.
|
||||
|
||||
### Internal/Member E-mail Addresses/Aliases
|
||||
|
||||
Each member is entitled to an @hacdc.org e-mail account. HacDC shall
|
||||
offer hosting for @hacdc.org e-mail accounts or offer the option of
|
||||
forwarding to the member's chosen e-mail address. Member e-mail shall
|
||||
not be archived, except as chosen by the member in a hosted e-mail
|
||||
account.
|
||||
|
||||
### Internal E-mail Lists/Accounts
|
||||
|
||||
| E-mail address | Purpose | List Members | Archived by |
|
||||
|----------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------|------------------------------------------|
|
||||
| advisors@hacdc.org | A discussion forum for the HacDC [Advisory Council](Advisory_Council "wikilink"), where HacDC solicits advice and council. | [Advisory Council](Advisory_Council "wikilink"), [Members](:Category:Members "wikilink") | Mailman |
|
||||
| bod@hacdc.org | Contact list for the Board of Directors | [The Board of Directors](:Category:BOD "wikilink") | Mailman |
|
||||
| finance@hacdc.org | E-mail account for all things relating to HacDC Finances | [The Minister of Finance](The_Minister_of_Finance "wikilink") | Archived E-Mail (7 year retention cycle) |
|
||||
| members@hacdc.org | Open, unmoderated discussion for HacDC Voting and Non-Voting (i.e. Honorary) Members | [The Members](:Category:Members "wikilink"), [Honorary Members](:Category:Honorary_Members "wikilink") | Mailman |
|
||||
| members-announce@hacdc.org | Moderated, essential traffic for members. Primary distribution method for weekly members update, meeting minutes and agendas and emergencies. | [The Members](:Category:Members "wikilink"), [Honorary Members](:Category:Honorary_Members "wikilink") | Mailman |
|
||||
| ministers@hacdc.org | Primary contact address for the administrators of HacDC, designed for use by members to address specific concerns and by ministers to keep each other updated on minor administrative action. | [The Ministers](The_Ministers "wikilink"), [Shadow Ministers](Shadow_Ministers "wikilink") | Mailman |
|
||||
| news@hacdc.org | Primary contact list for the PR team of HacDC, designed to help members and associates get events publicised via HacDC's public e-mail lists, blog, twitter, etc. | [news@hacdc.org](news@hacdc.org "wikilink") | Mailman |
|
||||
|
||||
### Project Contact E-Mail Addresses
|
||||
|
||||
Each ongoing project must have an e-mail address associated with it. The
|
||||
e-mail address may be an alias for the project coordinator, a discussion
|
||||
list for the project as a whole or an alias to bod@ so [The
|
||||
Ministers](The_Ministers "wikilink") may be able to send project
|
||||
inquiries to the correct relevant parties. In any case, the status of
|
||||
each project contact e-mail must be documented here:
|
||||
|
||||
| E-mail address | Aliases | General Purpose | Delivery Mechanism | Archived? |
|
||||
|-------------------------------------------------------------------------------------------------|---------|----------------------------------------------------------------------------------------------------|-----------------------|-----------|
|
||||
| [multi-touch-int-display@](http://hacdc.org/mailman/listinfo/multi-touch-int-display_hacdc.org) | (None) | Discussion list for the [HacDC Multi-touch device](HacDC_Multi-touch_device "wikilink") Project. | Mailman via hacdc.org | Yes |
|
||||
| [museum@](http://hacdc.org/mailman/listinfo/museum_hacdc.org) | (None) | Discussion list for the [HacDC Museum](HacDC_Museum "wikilink") Project. | Mailman via hacdc.org | Yes |
|
||||
| [neighborhoodwireless@](http://hacdc.org/mailman/listinfo/neighborhoodwireless_hacdc.org) | (None) | Discussion list for the [Columbia Heights Wireless](Columbia_Heights_Wireless "wikilink") Project. | Mailman via hacdc.org | Yes |
|
||||
| [smartclothing@](http://hacdc.org/mailman/listinfo/smartclothing_hacdc.org) | (None) | Discussion list for the [Smart Clothing](Smart_Clothing "wikilink") Project. | Mailman via hacdc.org | Yes |
|
||||
| [micromondays@](http://hacdc.org/mailman/listinfo/micromondays_hacdc.org) | (None) | Discussion list for the [Microcontroller Course](Microcontroller_Course "wikilink") | Mailman via hacdc.org | Yes |
|
||||
| [reddoor@](http://hacdc.org/mailman/listinfo/reddoor_hacdc.org) | (None) | Discussion list for the [Door Entry Project](Door_Entry_Project "wikilink") | Mailman via hacdc.org | Yes |
|
||||
|
||||
## Web Presence
|
||||
|
||||
### Homepage/Blog: hacdc.org
|
||||
|
||||
Our main website is run on [Drupal](Wikipedia:Drupal "wikilink") and
|
||||
functions primarily as a blog.
|
||||
|
||||
### Wiki
|
||||
|
||||
Our wiki is run on [MediaWiki](Wikipedia:MediaWiki "wikilink"). You're
|
||||
most likely reading it now.
|
||||
|
||||
### Twitter
|
||||
|
||||
Our twitter is [hacdc](http://twitter.com/hacdc).
|
||||
|
||||
### Livejournal
|
||||
|
||||
Our Livejournal is [hacdc](http://hacdc.livejournal.com/).
|
||||
|
||||
### Meetup
|
||||
|
||||
Our meetup is [hacdc](http://www.meetup.com/hac-dc/).
|
||||
|
||||
## Phone
|
||||
|
||||
Our Phone number is (202) 556-4225 (556-HACK).
|
||||
|
||||
## CHAT
|
||||
|
||||
Visit [chat.hacdc.org](http://chat.hacdc.org) or point your IRC client
|
||||
to \#hacdc at [freenode.org](irc://irc.freenode.org/hacdc). This is the
|
||||
primary chat medium for HacDC.
|
||||
|
||||
Projects whose communities rely on IRC are encouraged to start their own
|
||||
IRC channels or actively participate in existing channels - we have
|
||||
control of the entire \#hacdc-\* namespace, if sub-channels are needed.
|
||||
|
||||
[Category:HacDC_Systems](Category:HacDC_Systems "wikilink")
|
||||
Executable
+13
@@ -0,0 +1,13 @@
|
||||
| What | When | Where | Who's going | What we're doing there (e.g., [Hackersmart](Hackersmart "wikilink")) |
|
||||
|-------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|-----------------------------------------------------------------------------|------------------------------------------------------------------------|----------------------------------------------------------------------|
|
||||
| [Notacon](http://www.notacon.org/) | April 15-18, 2010 | Cleveland, OH | | |
|
||||
| [Robotfest](http://robotfest.com/) / [Mid-Atlantic Mini Maker Faire](http://baltimorenode.org/2010/01/mid-atlantic-mini-maker-faire-robot-fest-2k10/) | April 24, 2010 | [National Electronics Museum](http://www.hem-usa.org/), Linthicum, Maryland | | |
|
||||
| [Maker Faire North Carolina](http://makerfairenc.com/) | April 25, 2010 | Durham, NC | | |
|
||||
| [Penguicon 7.0](http://www.penguicon.org/) | April 30 - May 2, 2010 | Troy, MI | | |
|
||||
| [The Next HOPE](http://www.thenexthope.org/) | July 16-18, 2010 | New York, NY | [User:Katie](User:Katie "wikilink"), [Nocko](User:Nock "wikilink") ... | [under discussion](TheNextHOPE "wikilink") |
|
||||
| [Defcon](http://www.defcon.org/) | July 29 - August 1, 2010 | Las Vegas, NV | | |
|
||||
| [Maker Faire New York City](http://www.makerfaire.com/) | September 26-26, 2010 | Queens, NY | | |
|
||||
|
||||
Upcoming Conferences of Interest
|
||||
|
||||
[Category:Conferences](Category:Conferences "wikilink")
|
||||
Executable
+223
@@ -0,0 +1,223 @@
|
||||
"They who can give up essential liberty to obtain a little temporary
|
||||
safety deserve neither liberty nor safety." -Benjamin Franklin,
|
||||
Franklin's Contributions to the Conference on February 17 (III) Fri, Feb
|
||||
17, 1775 (http://www.ushistory.org/franklin/quotable/singlehtml.htm)
|
||||
|
||||
# Anonymity/Privacy?
|
||||
|
||||
Q: What is anonymity? A: In the context of security anonymity refers to
|
||||
the inability of unauthorized parties to link communications to your
|
||||
"real" identiy in whatever for that may take. This can also work on a
|
||||
sliding scale such as "Can my
|
||||
<crazy stalker/local law enforcement/federal law enforcement> find me?".
|
||||
The answer of yes for the "crazy stalker" will be significantly easier
|
||||
to achieve than the yes for "federal law enforcement". Q: What is
|
||||
privacy? A: Privacy is the ability to expose your information or
|
||||
behavior to only those parties you wish to share it with. This does not
|
||||
inherently include the ability to obscure your identity.
|
||||
|
||||
Anonymity and privacy are complementary to each other in many cases but
|
||||
are not mutually inclusive.
|
||||
|
||||
# SSL
|
||||
|
||||
Why SSL is broken: <http://notary.icsi.berkeley.edu/trust-tree/> The red
|
||||
circles on that map are the "root CAs", the Certificate Authorities that
|
||||
have their certificate trusted in most browsers. The size of the circle
|
||||
is based on the amount of certificates the CA is thought to have issued.
|
||||
These are all the entities that if one gets hacked, they can issue a
|
||||
wildcard certificate and your browser would show the certificate as
|
||||
valid.
|
||||
|
||||
# GPG
|
||||
|
||||
This page shows how the web of trust works:
|
||||
<http://www.gnupg.org/gph/en/manual.html#WOT-EXAMPLES>
|
||||
|
||||
# TOR
|
||||
|
||||
What is TOR and why does it matter?
|
||||
<http://thenextweb.com/insider/2013/10/08/what-is-tor-and-why-does-it-matter/>
|
||||
|
||||
What is TOR? A beginner's guide to the privacy tool -
|
||||
<http://www.theguardian.com/technology/2013/nov/05/tor-beginners-guide-nsa-browser>
|
||||
|
||||
What is TOR from the EFF (https://www.eff.org/torchallenge/what-is-tor):
|
||||
Tor is a service that helps you to protect your anonymity while using
|
||||
the Internet. Tor is comprised of two parts: software you can download
|
||||
that allows you to use the Internet anonymously, and the volunteer
|
||||
network of computers that makes it possible for that software to work.
|
||||
|
||||
When you use the Tor software, your IP address remains hidden and it
|
||||
appears that your connection is coming from the IP address of a Tor exit
|
||||
relay, which can be anywhere in the world. There are many reasons you
|
||||
might use Tor, including keeping websites from tracking you and your
|
||||
family members, using websites or services which are blocked in your
|
||||
country (for example, getting around the Great Firewall of China), and
|
||||
maintaining anonymity when communicating about socially sensitive
|
||||
information, such as health issues or whistleblowing. Learn more about
|
||||
who uses Tor.
|
||||
|
||||
# Hard Drive Encryption
|
||||
|
||||
## Truecrypt (Windows drive encryption)
|
||||
|
||||
How to encrypted your system drive (Windows boot drive) on Windows using
|
||||
Truecrypt:
|
||||
<http://www.maximumpc.com/article/howtos/how_to_encrypt_your_entire_hard_drive_the_easy_way_using_truecrypt>
|
||||
|
||||
# Suggested Software:
|
||||
|
||||
Software usable under multiple operating systems is normally listed
|
||||
under each operating system.
|
||||
|
||||
Note about Truecrypt-No complete audit has been done yet, people are
|
||||
currently collecting funds for a full audit -
|
||||
<http://istruecryptauditedyet.com/>
|
||||
|
||||
## GPG Key IDs:
|
||||
|
||||
These are GPG Key IDs which can be obtained from keyservers.
|
||||
|
||||
| Group: | Key: |
|
||||
|--------------------------------------------|----------|
|
||||
| TAILS (The Amnesiac Incognito Live System) | BE2CD9C1 |
|
||||
| Tor Browser Bundle (TOR Project) | 63FEE659 |
|
||||
| GPG4Win | EC70B1B8 |
|
||||
| Truecrypt | F0D6B1E0 |
|
||||
| GPGTools | 00D026C4 |
|
||||
| Enigmail | 9369CDF3 |
|
||||
|
||||
## OS independent (Normally bootable iso images):
|
||||
|
||||
| Program: | Desc: | URL: | Why? |
|
||||
|--------------------------------------------|-----------------------------------|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|
||||
| TAILS (The Amnesiac Incognito Live System) | Secure workstation LiveCD | <https://tails.boum.org/> | A Linux Live edition for accessing TOR outside of your normal operating system (Note, for security reasons make sure your normal hard drive isn't accessible while booted into this, running encrypting with any whole drive encryption software should work). |
|
||||
| DBAN | Secure storage media destruction. | <http://dban.org/> | |
|
||||
|
||||
If you require help burning ISO images, please join the HacDC Blabber
|
||||
mailing list
|
||||
(https://groups.google.com/a/hacdc.org/group/Blabber/subscribe) and ask
|
||||
how (make sure to include which operating system you are running when
|
||||
asking for help).
|
||||
|
||||
## Linux and other Unix variants:
|
||||
|
||||
| Program: | Desc: | URL: |
|
||||
|--------------------|----------------------------------------------------|-------------------------------------------------------------|
|
||||
| Truecrypt | Hard Drive Encryption, File encryption | <http://truecrypt.org/> |
|
||||
| Tor Browser Bundle | Anonymous web surfing (includes Tor & web browser) | <https://www.torproject.org/download/download-easy.html.en> |
|
||||
| Thunderbird | Email Encryption | <https://www.mozilla.org/en-US/thunderbird/all.html> |
|
||||
|
||||
## Windows:
|
||||
|
||||
| Program: | Desc: | URL: |
|
||||
|--------------------|----------------------------------------------------|-------------------------------------------------------------|
|
||||
| Truecrypt | Hard Drive Encryption, File encryption | <http://truecrypt.org/> |
|
||||
| Tor Browser Bundle | Anonymous web surfing (includes Tor & web browser) | <https://www.torproject.org/download/download-easy.html.en> |
|
||||
| Thunderbird | Email Encryption | <https://www.mozilla.org/en-US/thunderbird/all.html> |
|
||||
| GPG4Win | GPG front-end for Windows | <http://www.gpg4win.org/download.html> |
|
||||
| eraser | Secure Delete | <http://eraser.heidi.ie/> |
|
||||
|
||||
## Mac OS:
|
||||
|
||||
| Program: | Desc: | URL: |
|
||||
|--------------------|----------------------------------------------------|-------------------------------------------------------------|
|
||||
| Truecrypt | Hard Drive Encryption, File encryption | <http://truecrypt.org/> |
|
||||
| Tor Browser Bundle | Anonymous web surfing (includes Tor & web browser) | <https://www.torproject.org/download/download-easy.html.en> |
|
||||
| Thunderbird | Email Encryption | <https://www.mozilla.org/en-US/thunderbird/all.html> |
|
||||
| GPGtools | Integrates GnuPG with MacOSX. | <http://gpgtools.org/> |
|
||||
|
||||
## Android:
|
||||
|
||||
| Program: | Desc: |
|
||||
|--------------|----------------------------------------------------------------------|
|
||||
| Orbot | TOR for Android |
|
||||
| Orweb | TOR web browser for Android (Orbot required) |
|
||||
| APG | GPG Program |
|
||||
| K-9 Mail | Email program for Android that can directly interact with APG |
|
||||
| Adblock Plus | Detects and blocks advertisements (images, JavaScript, Java applets) |
|
||||
|
||||
## iOS:
|
||||
|
||||
| | | |
|
||||
|----------|----------------------------------------------------|-----------------------------|
|
||||
| Ghostery | Blocks web analytics agents (web bugs, JavaScript) | <https://www.ghostery.com/> |
|
||||
|
||||
## Web Browser Plugins:
|
||||
|
||||
### Safari:
|
||||
|
||||
| Ghostery | Blocks web analytics agents (web bugs, JavaScript) | <https://www.ghostery.com/> |
|
||||
|----------|----------------------------------------------------|-----------------------------|
|
||||
| Lastpass | Password manager | <https://lastpass.com> |
|
||||
|
||||
### Firefox:
|
||||
|
||||
| Noscript | Disable JavaScript, Java, Flash, Silverlight, XSS, Clickjacking, etc | <http://noscript.net/> |
|
||||
|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------|
|
||||
| Lastpass | Password manager | <https://lastpass.com> |
|
||||
| HTTPS Everywhere | Enable SSL wherever possible | <https://www.eff.org/https-everywhere> |
|
||||
| Web of Trust | Website reputation checker | <https://www.mywot.com/> |
|
||||
| Mailvelope | GPG Add-on for Firefox and Chrome. Needs vetting and only the chrome addon is available prebuilt from them but the ff adon is easy to build and can be built ahead of time if needed. | <http://www.mailvelope.com/> |
|
||||
| Calomel SSL Validation | Analyzes SSL configuration of sites you visit and gives you an analysis with reasoning behind the rating. | <https://addons.mozilla.org/en-US/firefox/addon/calomel-ssl-validation/> |
|
||||
| ShareMeNot | Blocks sharing buttons and applets unless you specifically click on them to enable them. | <http://sharemenot.cs.washington.edu/> |
|
||||
| HTTPS Finder | Automatically detect SSL capabilities. Generates rules for HTTPS Everywhere. | <https://github.com/kevinjacobs/HTTPS-Finder> |
|
||||
| Ghostery | Blocks web analytics agents (web bugs, JavaScript) | <https://www.ghostery.com/> |
|
||||
| Adblock Plus | Detects and blocks advertisements (images, JavaScript, Java applets) | <https://adblockplus.org/> |
|
||||
|
||||
### Chrome:
|
||||
|
||||
| Lastpass | Password manager | <https://lastpass.com> |
|
||||
|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------|
|
||||
| HTTPS Everywhere | Enable SSL wherever possible | <https://www.eff.org/https-everywhere> |
|
||||
| Web of Trust | Website reputation checker | <https://www.mywot.com/> |
|
||||
| Mailvelope | GPG Add-on for Firefox and Chrome. Needs vetting and only the chrome addon is available prebuilt from them but the ff adon is easy to build and can be built ahead of time if needed. | <http://www.mailvelope.com/> |
|
||||
| ShareMeNot | Blocks sharing buttons and applets unless you specifically click on them to enable them. | <http://sharemenot.cs.washington.edu/> |
|
||||
| Ghostery | Blocks web analytics agents (web bugs, JavaScript) | <https://www.ghostery.com/> |
|
||||
| Adblock Plus | Detects and blocks advertisements (images, JavaScript, Java applets) | <https://adblockplus.org/> |
|
||||
|
||||
### Opera:
|
||||
|
||||
| Lastpass | Password manager | <https://lastpass.com> |
|
||||
|--------------|----------------------------------------------------------------------|-----------------------------|
|
||||
| Ghostery | Blocks web analytics agents (web bugs, JavaScript) | <https://www.ghostery.com/> |
|
||||
| Adblock Plus | Detects and blocks advertisements (images, JavaScript, Java applets) | <https://adblockplus.org/> |
|
||||
|
||||
### Internet Explorer:
|
||||
|
||||
| Lastpass | Password manager | <https://lastpass.com> |
|
||||
|----------|----------------------------------------------------|-----------------------------|
|
||||
| Ghostery | Blocks web analytics agents (web bugs, JavaScript) | <https://www.ghostery.com/> |
|
||||
|
||||
## Non web browser plugins:
|
||||
|
||||
### Thunderbird:
|
||||
|
||||
| Enigmail | GPG Add-on for Thunderbird | <http://www.enigmail.net/download/index.php> |
|
||||
|----------|----------------------------|----------------------------------------------|
|
||||
|
||||
# Links:
|
||||
|
||||
## Internet:
|
||||
|
||||
| Site: | URL: | Notes: |
|
||||
|--------------------------------------------|-----------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|
||||
| Mailvelope | <http://www.mailvelope.com/> | In-browser PGP encryption for webmail |
|
||||
| Encrypt Everything | <https://www.encrypteverything.ca/index.php?title=Main_Page> | Good resource on encryption for the web. Good resource for beginner to intermediate skill level. |
|
||||
| Surveilance Self-Defense | <https://ssd.eff.org/> | EFF's guide to protecting yourself from digital surveilance. Extremely in-depth and detailed. For the advanced (or very paranoid). Not light reading. |
|
||||
| Qualys Browsercheck | <https://browsercheck.qualys.com/> | Automated scanning of browser, plugins, and Windows updates for vulnerable, out-of-date configuration |
|
||||
| SSL Labs | <https://www.ssllabs.com/> | Tool for checking any site's SSL setup for bad practices and vulnerabilities |
|
||||
| Calomel SSL Validation | <https://calomel.org/firefox_ssl_validation.html> | Firefox add-on for analyzing and verifying SSL configurations of sites you visit. |
|
||||
| DEATH NOTE: L, ANONYMITY & ELUDING ENTROPY | <http://www.gwern.net/Death%20Note%20Anonymity> | A.k.a., why "metadata" matters and how much the NSA can really know about you from your phone records. |
|
||||
| Using Metadata to Find Paul Revere | <http://kieranhealy.org/blog/archives/2013/06/09/using-metadata-to-find-paul-revere/> | Illustration of how to use seemingly useless data points to pin charges on someone. Told from the perspective of a British intelligence officer looking for trators in collonial America. |
|
||||
| crypto-log | <http://www.uni-mannheim.de/studorg/gahg/PGP/cryptolog1.html> | Updated 1996 |
|
||||
| Intro level guide to Internet Security | <http://qz.com/120946/the-complete-guide-to-not-being-that-idiot-who-got-the-company-hacked/> | A guide for non-technical denizens of the Internet on how not to be low-hanging fruit for hackers. |
|
||||
| How the Heartbleed Bug Works | <https://xkcd.com/1354/> | Nice illustration of how Heartbleed worked to give layfolk an idea of how some of these exploits happen and how client/server systems negotiate a connection. |
|
||||
|
||||
## TOR:
|
||||
|
||||
| Site: | URL: | Notes: |
|
||||
|-------------|--------------------------------------------------------|--------------------------------------|
|
||||
| tormail.org | <http://jhiwjjlqpyawmpjx.onion/> (http://tormail.org/) | Email service only available via tor |
|
||||
| Mailtor | <http://mailtoralnhyol5v.onion/> (http://mailtor.net/) | Email service only available via tor |
|
||||
Executable
+34
@@ -0,0 +1,34 @@
|
||||
This is an internal working wiki page to assist in cryptoparty
|
||||
organization.
|
||||
|
||||
Morning Session, suggested topics:
|
||||
|
||||
Order, Time, Presenter(s), Title
|
||||
|
||||
1, 10:30 am, Enrique/etc, Welcome to HacDC
|
||||
|
||||
2, 10:35 am, Enrique, Why do computers suck at security? SQL injections
|
||||
and buffer overflows.
|
||||
|
||||
3, 11:00 am, Enrique, Scams: Phishing and Spearphishing
|
||||
|
||||
4, 11:15 am, Enrique/Ankeet, Password Security, Hashing, Two-Factor
|
||||
Security
|
||||
|
||||
5, 11:30 am, Xavier, Introduction to Encryption
|
||||
|
||||
6, 11:45 am, Xavier, Digital Signatures & Certificates
|
||||
|
||||
7, 12:15 pm, Ankeet?, PGP, Signal, Tor
|
||||
|
||||
Afternoon Session:
|
||||
|
||||
Order, Time, Presenter(s), Title
|
||||
|
||||
8, 1:00pm, somebody, Tor 9, 1:30pm, Micah Sherr, Georgetown University,
|
||||
"Hidden Voice Commands," 10, 2:00 pm, Lindsay Beck, Open Tech Fund,
|
||||
"Resources for your Digital Security Projects??? 10, 2:20 pm, Ross
|
||||
Schulman, Open Tech Institute, "Security Law in 2017" 11, 2:40 pm+ Open
|
||||
Discussion, Q&A, Self-organized workshops, etc
|
||||
|
||||
Wrap-up at 3:30pm (HacDC Annual Meeting is at 4pm.)
|
||||
Executable
+47
@@ -0,0 +1,47 @@
|
||||
## Functions
|
||||
|
||||
- Transparent caching proxy for package management traffic (apt, yum,
|
||||
etc)
|
||||
- Mirroring and timeshifting of distribution repositories to offset
|
||||
bandwidth usage.
|
||||
|
||||
# Access
|
||||
|
||||
This machine is just for caching package management traffic and
|
||||
rehosting it. There are no user accounts available on this machine.
|
||||
|
||||
## Caching Proxies
|
||||
|
||||
- apt - via apt-cacher-ng - <http://cthulhu:9999>
|
||||
- web
|
||||
|
||||
# Admin Notes
|
||||
|
||||
## Xen Config
|
||||
|
||||
- CPU: 2
|
||||
- RAM: 2048MB
|
||||
- Disk:
|
||||
- / - albert/cthulhu-disk
|
||||
- swap - albert/cthulhu-swap
|
||||
- cache - albert/proxy
|
||||
|
||||
# Software
|
||||
|
||||
## Squid
|
||||
|
||||
- **Not configured**
|
||||
- Caches:
|
||||
- Packages for:
|
||||
- Debian/Ubuntu/Mint
|
||||
- does not cache Packages\* files - prevents stale package lists
|
||||
- Installer and live ISOs for:
|
||||
- Debian/Ubuntu/Mint
|
||||
- Fedora/Centos
|
||||
- Slackware/Slax/Porteus
|
||||
- Gentoo/Funtoo
|
||||
- Will coordinate with mirage
|
||||
|
||||
[Category:Infrastructure](Category:Infrastructure "wikilink")
|
||||
[Category:Servers](Category:Servers "wikilink")
|
||||
[Category:VMs](Category:VMs "wikilink")
|
||||
Executable
+35
@@ -0,0 +1,35 @@
|
||||
# Alternate Slicer Instruction (Experimental)
|
||||
|
||||
**Don't do this until we verify**
|
||||
|
||||
1. Open the Kisslicer link on the desktop
|
||||
2. Load your stl
|
||||
3. Slice
|
||||
4. Save (should save with a .bfb ext)
|
||||
5. Open CodeX32 link on the desktop
|
||||
1. Printer: CubePro
|
||||
2. Function: EnCode
|
||||
3. Input File: your.brb
|
||||
4. Output File: youre.cube (cubepro file should work with cube ext)
|
||||
|
||||
## References
|
||||
|
||||
You can use a regular slicer and convert it to .cube code See this
|
||||
[Thread](https://groups.google.com/forum/#!topic/kisslicer-refugee-camp/ZMuIrtn5Mfo)
|
||||
|
||||
Here's a [Thread](http://www.kisslicertalk.com/viewtopic.php?f=20&t=353)
|
||||
specific to the cube 2
|
||||
|
||||
Another
|
||||
[Thread](http://cube3d.createaforum.com/general-discussion/alternative-slicer-to-the-cubes-standard-software/).
|
||||
This seems to be the latest.
|
||||
|
||||
## Troubleshooting Notes
|
||||
|
||||
- Decoding a .cube file generated by cubes software and re-encoding with
|
||||
cubepro setting and then renaming file .cube seems to work. Using
|
||||
cubex setting does not work.
|
||||
- Setting Filament parameter to -1 does not cause an error
|
||||
- Setting Time to 0 does not cause an error
|
||||
|
||||
[Category:Cube](Category:Cube "wikilink")
|
||||
Executable
+62
@@ -0,0 +1,62 @@
|
||||
**When you use the Cube, please add notes here. Newest at top.**
|
||||
|
||||
- Operational at Makersmiths. Seems to print a RasPi case fine.
|
||||
[Mirage335](User:Mirage335 "wikilink")
|
||||
([talk](User_talk:Mirage335 "wikilink")) 11:27, 8 April 2016 (PDT)
|
||||
|
||||
<!-- -->
|
||||
|
||||
- Printed Reprap Wilson Z Brace. Failed becuase cartridge ran out of
|
||||
filament. Refilled filament making sure not to wind it too tightly
|
||||
(Did by hand). Also made sure to release tension on wound filament
|
||||
very few winds by counter rotation cartridge.
|
||||
--[Nostromo](User:Nostromo "wikilink")
|
||||
([talk](User_talk:Nostromo "wikilink")) 16:45, 16 April 2015 (PDT)
|
||||
|
||||
<!-- -->
|
||||
|
||||
- James reports: Attempted to print LCD Knob for Reprap Wilson but
|
||||
printer refused to start printing with a "Cartridge Empty" error
|
||||
message. Need to procure another cartridge and being doing cartridge
|
||||
swap procedure to bypass this check.
|
||||
--[Nostromo](User:Nostromo "wikilink")
|
||||
([talk](User_talk:Nostromo "wikilink")) 09:52, 13 March 2015 (PDT)
|
||||
|
||||
<!-- -->
|
||||
|
||||
- James reports: Printed Y bearing holders from Prusa Mendel upgrade.
|
||||
New mirrored build surface is working well with Elmers glue stick
|
||||
(Easier to release parts). Several failed attempts at printing
|
||||
filament bypass for cube because of poor STL file orientation.
|
||||
--[Nostromo](User:Nostromo "wikilink")
|
||||
([talk](User_talk:Nostromo "wikilink")) 09:34, 1 March 2015 (PST)
|
||||
|
||||
<!-- -->
|
||||
|
||||
- James reports: Printer is operating well. There is slight warping of
|
||||
larger 4 inch parts on the corners but prints complete successfully.
|
||||
The part I was printing failed in a strange way (printed part was
|
||||
missing a geometric section). This might be due to forgetting to run
|
||||
heal in the software. Also when transferring the .cube file to the
|
||||
printer just use the USB key as it is far more reliable than the wifi.
|
||||
--[Nostromo](User:Nostromo "wikilink")
|
||||
([talk](User_talk:Nostromo "wikilink")) 13:49, 11 February 2015 (PST)
|
||||
|
||||
<!-- -->
|
||||
|
||||
- James reports: Performed Bed Leveling procedure (Ugh!!). Printing
|
||||
Wilson Piecemeal Y Idler. The print looks a little smooshed on the
|
||||
bottom. Consider recalibrating Z a little higher.
|
||||
--[Nostromo](User:Nostromo "wikilink")
|
||||
([talk](User_talk:Nostromo "wikilink")) 17:36, 5 February 2015 (PST)
|
||||
|
||||
<!-- -->
|
||||
|
||||
- James reports: Printed 2nd part on this printer. Reset Z axis to 1.60z
|
||||
so that it wouldn't smoosh the part as much. seemes to have worked but
|
||||
has a little bit of warping of the edges of the 5" part I was
|
||||
printing. Removing the part is requiring long times in a water bath to
|
||||
permeate the glue underneath --[Nostromo](User:Nostromo "wikilink")
|
||||
([talk](User_talk:Nostromo "wikilink")) 16:01, 8 February 2015 (PST)
|
||||
|
||||
[Category:Cube](Category:Cube "wikilink")
|
||||
Executable
+79
@@ -0,0 +1,79 @@
|
||||
## Overview
|
||||
|
||||
Welcome to the Culture Jamming page. Here we will explore and document
|
||||
the history and practice of culture jamming. Feel free to add to this
|
||||
wiki if you have gems to share.
|
||||
|
||||
From [Wikipedia](http://en.wikipedia.org/wiki/Culture_jamming): Coined
|
||||
by the collage band Negativland on its release JamCon '84, the phrase
|
||||
"culture jamming" comes from the idea of radio jamming: that public
|
||||
frequencies can be pirated and subverted for independent communication,
|
||||
or to disrupt dominant frequencies\[12\].
|
||||
|
||||
\[12\] [Disrupt Dominant
|
||||
Frequencies](http://disruptdominantfrequencies.net/)
|
||||
|
||||
## Museums, collections, directories
|
||||
|
||||
[The Alternative Museum](http://www.alternativemuseum.org/) (Doesn't
|
||||
appear to have been updated since 2003)
|
||||
|
||||
## DIY projects related to CJ
|
||||
|
||||
[MAKE electronics
|
||||
projects](http://blog.makezine.com/archive/2009/12/culture_jamming_open_source_hardwar.html)
|
||||
|
||||
## DC Area Culture Jamming
|
||||
|
||||
[Capitol Climage Action](http://www.capitolclimateaction.org/)
|
||||
(apparently the webmaster has moved to SF?)
|
||||
|
||||
## Examples
|
||||
|
||||
- Barbie Liberation Organization
|
||||
- [Youtube Video](http://www.youtube.com/watch?v=OVT4T7OR3iQ)
|
||||
|
||||
## Articles and papers
|
||||
|
||||
- [Elliot Feldman, Aug 22 2007,
|
||||
AP](http://www.associatedcontent.com/article/350004/what_is_culture_jamming.html)
|
||||
- [Mark Dery, Dec 23 1990, NY
|
||||
Times](http://www.nytimes.com/1990/12/23/arts/the-merry-pranksters-and-the-art-of-the-hoax.html)
|
||||
|
||||
## Movers and shakers
|
||||
|
||||
[Mark Dery popularized the term "culture jamming" in his
|
||||
writing](http://en.wikipedia.org/wiki/Mark_Dery)
|
||||
|
||||
[Gareth Branwyn](http://en.wikipedia.org/wiki/Gareth_branwyn) has
|
||||
written about and practiced culture jamming writ large, influenced in
|
||||
part by the theories and practice of the
|
||||
[Dadaists](http://en.wikipedia.org/wiki/Dada), the
|
||||
[Surrealists](http://en.wikipedia.org/wiki/Surrealism), the
|
||||
[Futurists](http://en.wikipedia.org/wiki/Futurism), the 60s
|
||||
counter-culture, [The Situationist
|
||||
International](http://en.wikipedia.org/wiki/Situationist_International),
|
||||
[Fluxus](http://en.wikipedia.org/wiki/Fluxus), [William
|
||||
Blake](http://en.wikipedia.org/wiki/William_blake), and other
|
||||
proto-culture-jammers and thinkers. During the 80s and 90s he practiced
|
||||
[mail art](http://en.wikipedia.org/wiki/Mail_art), published
|
||||
[zines](http://www.streettech.com/bcp/BCPgraf/CyberCulture/goinggaga.html),
|
||||
wrote early DIY-culture texts such as [The Happy Mutant
|
||||
Handbook](http://www.amazon.com/Happy-Mutant-Handbook-Carla-Sinclair/dp/1573225029/ref=sr_1_1?ie=UTF8&s=books&qid=1268709584&sr=8-1),
|
||||
the seminal HyperCard stack, [Beyond
|
||||
Cyberpunk!](http://www.streettech.com/bcp/), held countless discussions
|
||||
on the topic on [The Well](http://en.wikipedia.org/wiki/The_WELL), and
|
||||
articles for culture hacking champions, [Mondo
|
||||
2000](http://en.wikipedia.org/wiki/Mondo_2000) and
|
||||
[Wired](http://en.wikipedia.org/wiki/Wired_%28magazine%29) where he
|
||||
created and edited the longest running column for that publication,
|
||||
[Jargon
|
||||
Watch](http://www.amazon.com/Jargon-Watch-Dictionary-Jitterati-Hardwired/dp/1888869062/ref=sr_1_1?ie=UTF8&s=books&qid=1268710455&sr=8-1),
|
||||
about the accelerating influence that information technology was
|
||||
exerting on the evolution of the English language. In 1997, he wrote
|
||||
[Jamming the
|
||||
Media](http://www.amazon.com/Jamming-Media-Gareth-Branwyn/dp/0811817954/ref=sr_1_2?ie=UTF8&s=books&qid=1268708624&sr=8-2),
|
||||
a citizen's guide to reclaiming the tools of communication. He is
|
||||
currently Editor in Chief of the [MAKE Blog](http://blog.makezine.com/).
|
||||
|
||||
[Category:HacDC_Culture](Category:HacDC_Culture "wikilink")
|
||||
@@ -0,0 +1,3 @@
|
||||
1. REDIRECT [HacDC Spaceblimp 6/Projects/Curriculum Development and key
|
||||
Project
|
||||
Documents](HacDC_Spaceblimp_6/Projects/Curriculum_Development_and_key_Project_Documents "wikilink")
|
||||
Executable
+234
@@ -0,0 +1,234 @@
|
||||
## Project Description
|
||||
|
||||
- Organizers: Enrique C., Nancy C. Wolfson, Bobby B.
|
||||
- Contact: crispr@hacdc.org
|
||||
|
||||
CRISPR-Cas9 is a groundbreaking new (2012 vintage) gene editing
|
||||
technique. While gene editing is not a new concept, previous methods
|
||||
were far more expensive, slow and restricted in capabilities than
|
||||
CRISPR. Further, whereas previous methods only successfully edited a few
|
||||
percent of the exposed cells, CRISPR's efficiency approaches 100%. This
|
||||
is particularly important for gene editing in living multi-cellular
|
||||
organisms. The new technique is dramatically accelerating the pace of
|
||||
genetic engineering since its invention in 2012.
|
||||
|
||||
CRISPR is an acronym that describes a genetic curiosity observed several
|
||||
decades ago: Clusters of Regularly Interspaced Short Palindromic
|
||||
Repeats. A few years go it was recognized that these odd DNA sequences
|
||||
in bacteria are deactivated virus DNA and make up a kind of Virus
|
||||
Definition Database. Finally, it was discovered that a protein exists
|
||||
which goes around scanning bacteria DNA searching for matches to virus
|
||||
DNA sequences and, when a match is found, cuts the gene in the bacteria
|
||||
DNA very precisely and efficiently. This protein was termed Cas9. In
|
||||
effect, bacteria and other organisms already have an excellent built-in
|
||||
gene-editing mechanism, and scientists have since learned to hijack that
|
||||
mechanism using engineered RNA sequences that direct the Cas9 protein to
|
||||
cut DNA in any desired location in the genome.
|
||||
|
||||
The Cas9 mechanism only cuts the DNA in one location, leaving DNA repair
|
||||
mechanisms to fix the double-strand cut. Repair mechanisms for such a
|
||||
serious double-strand break are so imperfect as to incapacitate the gene
|
||||
with errors most of the time. Thus the Cas9 protein deactivates genes
|
||||
rather than removing them. However, by programming two custom RNA target
|
||||
strands, two Cas9 proteins can be used in tandem to excise part of a
|
||||
genome altogether. To add a new gene, there must be enough of that gene
|
||||
floating around during the CRISPR process that it becomes incorporated
|
||||
into the genome via the repair mechanisms.
|
||||
|
||||
These are the best videos we've found so far: Genome Editing with
|
||||
CRISPR-Cas9 by McGovern Institute for Brain Research
|
||||
<https://www.youtube.com/watch?v=2pp17E4E-O8>
|
||||
|
||||
What is CRISPR? by Bozeman Science
|
||||
<https://www.youtube.com/watch?v=MnYppmstxIs>
|
||||
|
||||
Read more here: <https://en.wikipedia.org/wiki/CRISPR>
|
||||
|
||||
Read more here: <https://en.wikipedia.org/wiki/CRISPR>
|
||||
|
||||
In the ODIN kit experiment, bacteria (E. coli HME63 strain) are modified
|
||||
to add resistance to the antibiotic streptomycin. The kit provides the
|
||||
vulnerable bacteria, the resistance gene, and growth media with and
|
||||
without antibiotic. The original unmodified bacteria can only grow on
|
||||
the plain agar media whereas bacteria with a successfully edited genome
|
||||
will also grow on the streptomycin-laced agar. This is similar to Wenyan
|
||||
Jiang, David Bikard, David Cox, Feng Zhang and Luciano Marraffini,
|
||||
RNA-guided editing of bacterial genomes using CRISPR-Cas systems, Nature
|
||||
Biotechnology 31(3), pp.233 (2013).
|
||||
<http://zlab.mit.edu/assets/reprints/Jiang_W_Nat_Biotechnol_2013.pdf>
|
||||
|
||||
## Financial Support / Sponsors
|
||||
|
||||
HacDC - 8/2016 - purchased Bacterial DIY CRISPR kit. Enrique C -
|
||||
11/2016- purchased Bacterial DIY CRISPR Kit. Nancy W - purchased
|
||||
Bacterial DIY CRISPR kit. Enrique C - 5/2017 - purchased Bacterial DIY
|
||||
CRISPR Kit Refill. Nancy W - 2017 - purchased Bacterial DIY CRISPR kit
|
||||
refill. Nancy W - 2017 - purchased temperature-controlled water bath.
|
||||
Nancy W - 2017 - loaned 1600X Optical Microscope with USB camera.
|
||||
Enrique C - 2017 - purchased supplies and gram staining kit. The ODIN -
|
||||
01/2018- provided free sample of next-gen CRISPR kit.
|
||||
|
||||
## Activities and Goals
|
||||
|
||||
DC CRISPR Initiative is our effort to learn about, perform, and teach
|
||||
CRISPR genetic editing at HacDC. To begin the project, we???ve ordered a
|
||||
Do-It-Yourself CRISPR Kit, which includes (supposedly) all the tools and
|
||||
ingredients needed to perform a CRISPR procedure a few times. We???ll
|
||||
hold a few events at HacDC to go through the procedure and document our
|
||||
experience. Eventually we???ll create a guide that older high school
|
||||
kids can follow. This project also explores interest in molecular
|
||||
biology and genetics at HacDC. We're just starting! Keep an eye out for
|
||||
CRISPR events in our MeetUp page, on the mailing list, and our Blabber
|
||||
discussion forum.
|
||||
|
||||
## Project Team Members
|
||||
|
||||
Enrique C. - Project Manager and Point of Contact Nancy W. - Project
|
||||
Development Lead Bobby B. - Molecular Biology Advisor Sophia M. -
|
||||
Scientific Advisor
|
||||
|
||||
## Worklog
|
||||
|
||||
July 30, 2016 We received the CRISPR kit purchased with Project
|
||||
EXPANSION funds (thanks!).
|
||||
|
||||
August 2, 2016 Nancy and Enrique inventoried the ODIN kit and designated
|
||||
the small classroom fridge as the "NO FOOD" Project CRISPR fridge.
|
||||
|
||||
August 5, 2016 Nancy and Enrique prepared four Petri dishes (two plain
|
||||
agar, two streptomycin-agar). The agar and
|
||||
antibiotic(streptomycin)-laced agar are gel-like substances similar to
|
||||
gelatin. They come as powders which must be mixed with water and heated
|
||||
to dissolve. The recipe is proportioned for seven Petri dishes but we
|
||||
scaled down to one of each, scaling the agar powders and water by
|
||||
one-seventh. Even so we were able to coat two dishes with each growth
|
||||
medium. We didn't have distilled or deionized water and used bottled
|
||||
purified drinking water in a pinch. The mixture (agar gel only, no
|
||||
bacteria!) was heated in the microwave 7 seconds at a time. It took 4-5
|
||||
cycles until the powders were fully dissolved and the liquid
|
||||
transparent, then another 5 minutes until they were cool enough to
|
||||
handle and pour into the plastic Petri dishes. The dishes cooled at room
|
||||
temperature for an hour to remove some condensation (the covered hot
|
||||
liquid creates condensation on the lid), then placed in the fridge. Two
|
||||
are agar (no antibiotic) and two are streptomycin/Kan agar (antibiotic
|
||||
laced).
|
||||
|
||||
August 10, 2016 Ken, Bobby, Nancy, and Enrique. We streaked some of the
|
||||
original E. coli HME63 bacteria onto two plain agar plates. Plate 1 was
|
||||
left out tonight (the bacteria need to grow). Plate 2 was immediately
|
||||
refrigerated and will be taken out to grow just before the actual
|
||||
experiment.
|
||||
|
||||
August, 2016 Nancy, Ken and Enrique. We performed the CRISPR experiment,
|
||||
but realized we don't have a constant-temperature water bath. We used an
|
||||
IR thermometer and the microwave to prepare and maintain a water bath of
|
||||
approximately 42C. The incubation period post-CRISPR is also quite long,
|
||||
up to 4 hours at room temperature, which makes this experiment
|
||||
problematic as an after-work evening activity. It'd work better on a
|
||||
weekend day or holiday since we have day jobs.
|
||||
|
||||
September, 2016 Nancy, Enrique. The first CRISPR-modified bacteria on
|
||||
the Strep-Kan plate was left at room temperature over the weekend (48
|
||||
hours). However, no bacteria colonies could be easily seen in the plate.
|
||||
The plate was left at room temperature several more days with no change.
|
||||
It looks like our first attempt did not wildly succeed.
|
||||
|
||||
September, 2016 Enrique. I prepared a new set of Agar (3) and Strep-Kan
|
||||
Agar (3) plates for troubleshooting experiments and a second try at
|
||||
CRISPR. We should test the full CRISPR protocol again, both on Agar and
|
||||
Strep-Kan plates, but also test the survival of bacteria at several
|
||||
other steps: Transformation Mix only and Transformation Mix + tracrRNA +
|
||||
crRNA.
|
||||
|
||||
September, 2016 Enrique and Nancy. We developed a troubleshooting
|
||||
protocol under the suspicion that maybe none of the bacteria are
|
||||
surviving (we did not make a plain Agar control plate last time). We
|
||||
also tested the 'sterile' innoculation loops vs. a bag of zip-ties we
|
||||
found laying around. Nancy brought an alcohol thermometer that's
|
||||
probably more accurate in water than the IR thermometer. The resulting
|
||||
plates were incubated for 24-48 hours. It was difficult to re-suspend
|
||||
the bacteria in solution after harvesting from the first plate. A vortex
|
||||
generator (basically a strong vibrator) would be helpful.
|
||||
|
||||
September, 2016 Enrique and Nancy. Hm... there are some specs on the
|
||||
CRISPR plate this time, just 2-3 colonies though. All the other (Agar)
|
||||
plates had tons of bacteria, so clearly the low efficiency is at the
|
||||
CRISPR step with the Template DNA. Also we brought in more Bleach for
|
||||
disposal of old samples, and bleach wipes.
|
||||
|
||||
September, 2016 Enrique. I located a much better (real) biological
|
||||
microscope with up to 1000x magnification in the basement. Man our
|
||||
inventory sucks; I had no idea we had this thing. Images are much
|
||||
better, although I'm not certain we're looking at individual bacteria. I
|
||||
also purchased a hotplate so we can actually control temperature baths
|
||||
in the future.
|
||||
|
||||
January, 2017 See notebook.
|
||||
|
||||
February, 2017. The third trial of the CRISPR process gave us a positive
|
||||
control sample, which makes the result inconclusive. While the Agar
|
||||
media grew more, both the CRISPR and original LD 21 bacteria grew
|
||||
somewhat on the Strep-Kan media. We perfomed a second control
|
||||
experiment, plating 100uL of the LD21 bacteria and the
|
||||
Transformation-Mix HME 63 strain with 400uL of DI water each, onto
|
||||
Strep-Kan media.
|
||||
|
||||
June, 2017 Purchased Bacterial CRISPR refill kit using HacDC Project
|
||||
CRISPR funds.
|
||||
|
||||
July 2017 - Bobby, Nancy, Enrique, Sophia and Richard. Met to plan
|
||||
workshop. Bobby gave us his Introduction to Molecular Biology talk - it
|
||||
was about 90 minutes but could probably be shortened to 60 if needed.
|
||||
Prepared fresh Agar and Strep-Kan plates. Sophia showed us a new
|
||||
(correct) streaking technique. We plated some bacteria but they overgrew
|
||||
(storage place on top of the fridge is too warm in the summer), making
|
||||
it impossible to isolated a colony. Sophia took a second batch home and
|
||||
it was better with some isolated colonies.
|
||||
|
||||
August 23, 2017 - Sophia, Nancy and Enrique. Trial 4 of the full CRISPR
|
||||
process. Enrique took the resulting plates home to monitor growth at
|
||||
room temperature. No growth observed on the CRISPR sample. Control
|
||||
sample grew quickly.
|
||||
|
||||
December 11, 2017 - Nancy and Enrique. Contacted kit supplier to obtain
|
||||
fresh ingredients.
|
||||
|
||||
January 09, 2017 - Enrique. Prepared fresh Agar and Strep-Kan Agar
|
||||
plates. Checked for contamination growth 48 hours (none).
|
||||
|
||||
January 12, 2017 - Nancy, Enrique and guests Tobi and Tom. Trial 4.5 of
|
||||
the CRISPR process. Used bacteria straight from the supply rather than a
|
||||
colony (not available). The result after 48 hours was much growth on the
|
||||
Agar plate and zero growth on the Strep-Kan plate. (no modification)
|
||||
|
||||
## Sample Inventory
|
||||
|
||||
**CRISPR Trial 8/24/2017** LB-Agar Plate at 1 and 20 Hours:
|
||||
|
||||
|
||||
|
||||
StrepKan Plate at 1, 20, 28 and 57 Hours:
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
**CRISPR Trial 1/12/2018**Clean Agar plate after 48 hours incubation. No
|
||||
contamination growth observed.
|
||||
[Media:CRISPR-180112-Agar_blank_48h.jpeg](Media:CRISPR-180112-Agar_blank_48h.jpeg "wikilink")
|
||||
Clean Strep-Kan plate after 48 hours incubation. No contamination growth
|
||||
observed.
|
||||
[Media:CRISPR-180112-StrepKan_blank_48h.jpeg](Media:CRISPR-180112-StrepKan_blank_48h.jpeg "wikilink")
|
||||
Agar plate with the post-protocol bacteria incubated 48 hours (control
|
||||
sample): much growth (overgrown).
|
||||
[Media:CRISPR-180112-Agar_Bact_48h.jpeg](Media:CRISPR-180112-Agar_Bact_48h.jpeg "wikilink")
|
||||
Strep-Kan plate with the post-protocol bacteria incubation 48 hours
|
||||
(CRISPR result): no growth.
|
||||
[Media:CRISPR-180112-StrepKan_CrisprBact_48h.jpeg](Media:CRISPR-180112-StrepKan_CrisprBact_48h.jpeg "wikilink")
|
||||
|
||||
## News References
|
||||
|
||||
- Video: bacteria evolving antibiotic resistance in 11 days.
|
||||
<https://www.youtube.com/watch?v=yybsSqcB7mE>
|
||||
- Video: CRISPR Patent Controversy:
|
||||
<https://www.youtube.com/watch?v=IboHEQumDGc>
|
||||
Executable
+343
@@ -0,0 +1,343 @@
|
||||
## 2017.11.21 "Inaugural" Meeting
|
||||
|
||||
In attendance:
|
||||
|
||||
- Ken Kenworthy, KnowledgeRealm, (instigator)
|
||||
- Marvin Gay, Coomunity Outreach Coordinator, [Safer, Stronger
|
||||
DC](https://www.facebook.com/SaferStrongerDC) Community Partnerships,
|
||||
out of the [Office of the Deputy Mayor for Health and Human
|
||||
Services](https://dmhhs.dc.gov/)
|
||||
- Michael Dodson, Program Assistant, [Safer, Stronger
|
||||
DC](https://www.facebook.com/SaferStrongerDC) Community Partnerships,
|
||||
out of the [Office of the Deputy Mayor for Health and Human
|
||||
Services](https://dmhhs.dc.gov/)
|
||||
- Dorothy Jones-Davis, Executive Director, [Nation of
|
||||
Makers](http://nationofmakers.org/)
|
||||
- Enrique Cobas (ex-exchequer, [HacDC](http://hacdc.org/))
|
||||
- Julia Longtin (once and future queen / madame president,
|
||||
[HacDC](http://hacdc.org/))
|
||||
- Kevin Cole ([Ubuntourist](User:Ubuntourist "wikilink")) (fugitive
|
||||
at-large, [HacDC](http://hacdc.org/))
|
||||
- Betty Amos (designer, educator, animator [Betty Amos
|
||||
Designs](http://bettyamosdesigns.com/))
|
||||
- Nicolas Sabharwal (lewlking)
|
||||
|
||||
## DC government initiative
|
||||
|
||||
From June 2017, the ["Innovation Space and Marketplace Report:
|
||||
Developing a Makerspace in the
|
||||
District"](https://dmped.dc.gov/page/innovation-space-and-marketplace-report-developing-makerspace-district)
|
||||
from the Office of the Deputy Mayor for Planning and Economic
|
||||
Development
|
||||
|
||||
???There's a 77-page PDF at the bottom of the page. Lots of good
|
||||
information here on needs and possibilities.
|
||||
|
||||
## Neighborhood Artisan Centers (NACs)
|
||||
|
||||
- [concept
|
||||
paper](https://docs.google.com/document/d/1UxZ_VBHbBEJ9fVJN7rdwqIjmKjv-HTKhiVUrSnDJta4/edit)
|
||||
by Ken
|
||||
|
||||
### Background/Reference
|
||||
|
||||
- **Makers: The New Industrial Revolution**
|
||||
- Wikipedia:
|
||||
\[<https://en.wikipedia.org/wiki/Makers:_The_New_Industrial_Revolution>:
|
||||
Makers: The New Industrial Revolution\] by Chris Anderson
|
||||
- Video: [Makers: The New Industrial
|
||||
Revolution](https://vimeo.com/60496236) by Chris Anderson. (Highly
|
||||
recommended.)
|
||||
- Book: [Makers: The New Industrial
|
||||
Revolution](https://www.amazon.com/Makers-Industrial-Revolution-Chris-Anderson/dp/0307720969)
|
||||
by Chris Anderson. (Highly recommended.)
|
||||
- [The Skills
|
||||
Revolution](http://www.manpowergroup.co.uk/the-word-on-work/skills-revolution/)
|
||||
by The ManpowerGroup.
|
||||
|
||||
<!-- -->
|
||||
|
||||
- **Good Sources To Keep Pace with Technology**
|
||||
- [The Singularity Hub](https://singularityhub.com/), "Singularity Hub
|
||||
chronicles technological progress ..."
|
||||
- [3DPrint.com](https://3dprint.com/) "3DPrint.com is a news
|
||||
organization dedicated to bringing you up to date on all the latest
|
||||
news from the 3D printing industry."
|
||||
- [Road to VR](https://www.roadtovr.com/) "Founded in 2011, Road to VR
|
||||
is the world???s leading independent news publication dedicated to
|
||||
the consumer virtual reality industry."
|
||||
- [Science X](https://sciencex.com/) "a network of high-quality
|
||||
websites that provides the most complete and comprehensive daily
|
||||
coverage of science, technology, and medical news."
|
||||
|
||||
<!-- -->
|
||||
|
||||
- **Examples of Project Based/Self Organized Learning, Virtual and
|
||||
On-site Mentors**
|
||||
- Video: [Anacostia HS Aquaponics
|
||||
Project](https://youtu.be/UgGpn_6Ryss), Teens and young adults
|
||||
participating in Aquaponics project at Anacostia High School
|
||||
- Video: [Web Conferencing with Virtual
|
||||
Mentors](https://youtu.be/gEV2-b_w7hg) Older teens at Anacostia HS
|
||||
interacted via web conferencing with Dr. Subhrankar Mukherjee
|
||||
(Subra), India chapter Club of Rome, from Mumbai, and David Li,
|
||||
founder of first Makerspace in China, from Shanghai
|
||||
- Video: [Videoconferencing with Virtual
|
||||
Mentor](https://youtu.be/jxKilY6Wvmo) Older teens at Anacostia HS
|
||||
interacted via web conferencing with Tyrese Gould, daughter of Mark
|
||||
Gould, Chief of the Nanticoke Lenni-Lenape Tribal Nation in New
|
||||
Jersey
|
||||
- **Potential Funding Sources and Grants**
|
||||
- [Funding
|
||||
Alert](http://links.govdelivery.com:80/track?type=click&enid=ZWFzPTEmbXNpZD0mYXVpZD0mbWFpbGluZ2lkPTIwMTcwOTExLjc3OTUzODYxJm1lc3NhZ2VpZD1NREItUFJELUJVTC0yMDE3MDkxMS43Nzk1Mzg2MSZkYXRhYmFzZWlkPTEwMDEmc2VyaWFsPTE3MTA4OTEyJmVtYWlsaWQ9bWFydmluLmdheTJAZGMuZ292JnVzZXJpZD1tYXJ2aW4uZ2F5MkBkYy5nb3YmdGFyZ2V0aWQ9JmZsPSZtdmlkPSZleHRyYT0mJiY=&&&103&&&https://opgs.dc.gov/publications?type=732)
|
||||
Mayor???s Office of Partnerships and Grant Services
|
||||
- [NSF Smart and Connected Communities (S&CC)
|
||||
Solicitation](https://www.nsf.gov/pubs/2018/nsf18520/nsf18520.htm)
|
||||
- [NSF Campus Cyberinfrastructure
|
||||
(CC\*)](https://www.nsf.gov/pubs/2018/nsf18508/nsf18508.htm)
|
||||
|
||||
------------------------------------------------------------------------
|
||||
|
||||
**Add your notes and thoughts below**
|
||||
|
||||
Try to make an effort to keep the page sane and readable by using
|
||||
[Mediawiki's formatting](https://www.mediawiki.org/wiki/Help:Formatting)
|
||||
correctly.
|
||||
|
||||
## DC/MD/VA spaces
|
||||
|
||||
Following up with some of the other local maker/hacker/bio/food spaces
|
||||
in the area (*Dorothy*):
|
||||
|
||||
- **Washington, DC**
|
||||
- [FabLab DC](http://www.fablabdc.org/) (FabLab)
|
||||
- [Hac DC](http://www.hacdc.org/) (Hackerspace)
|
||||
- [Local Motors](http://localmotors.com/national-harbor/) (Commercial
|
||||
Makerspace)
|
||||
- [Mess Hall](http://messhalldc.com/) (Food Makerspace)
|
||||
- [Taste Lab](http://tastelab.co/) (Food Makerspace)
|
||||
- [Union Kitchen](http://unionkitchendc.com/) (Food Makerspace)
|
||||
- [MLK Library "Fab Lab"](https://www.dclibrary.org/labs/fablab)
|
||||
(Makerspace)
|
||||
- [Maker Hub at Georgetown
|
||||
University](https://www.library.georgetown.edu/makerhub) (University
|
||||
Makerspace)
|
||||
- [Catholic University
|
||||
FabLab](https://architecture.catholic.edu/student-experience/technology/fabrication-labs/index.html)
|
||||
(University Makerspace; FabLab)
|
||||
- [District Makers
|
||||
Collective](http://www.districtmakerscollective.org/) (a
|
||||
work-in-progress from the refugees of the now-shuttered Tech Shop in
|
||||
Crystal City)
|
||||
|
||||
<!-- -->
|
||||
|
||||
- **Northern Virginia**
|
||||
- [NoVA Labs](http://nova-labs.org/) (Reston, VA; Community
|
||||
Makerspace)
|
||||
- [Building Momentum](http://buildingmomentum.us/) (Alexandria, VA;
|
||||
Community problem-solving space)
|
||||
- [Makersmiths](https://makersmiths.org/) (Leesburg, VA; Community
|
||||
makerspace)
|
||||
|
||||
<!-- -->
|
||||
|
||||
- **Maryland**
|
||||
- [Baltimore Underground Science Space
|
||||
(BUGGS)](http://www.bugssonline.org/) (Baltimore, MD; Biospace)
|
||||
- [Catylator](http://catylator.com/) (Silver Spring, MD; Makerspace)
|
||||
- [Digital Harbor Foundation](http://www.digitalharbor.org/)
|
||||
(Baltimore, MD; Youth Makerspace (Rec To Tech)
|
||||
- [The Foundery](http://foundery.com/) (Baltimore, MD; Focus on
|
||||
economic empowerment - working with City of Baltimore)
|
||||
- [Greenbelt MakerSpace](http://make125.org/) (Greenbelt, MD -
|
||||
Community Makerspace; co-op model)
|
||||
- [KiD Museum](http://kid-museum.org/) (Bethesda, MD; Children's
|
||||
makerspace)
|
||||
- [Open Works](http://www.openworksbmore.com/) (Baltimore, MD; Focus
|
||||
on entrepreneurship)
|
||||
- [Pyramid Atlantic Art
|
||||
Center](http://www.pyramidatlanticartcenter.org/) (Hyattsville, MD;
|
||||
Art makerspace)
|
||||
- [Station North Tool
|
||||
Library](http://www.stationnorthtoollibrary.org/) (Baltimore, MD)
|
||||
- [Unallocated Space](https://www.unallocatedspace.org/) (Severn, MD)
|
||||
- [John and Stella Graves Makerspace at the University of
|
||||
Maryland](https://www.lib.umd.edu/tlc/makerspace) (College Park, MD;
|
||||
University Makerspace)
|
||||
- [Rhizome DC](http://www.rhizomedc.org/) (Takoma Park, MD)
|
||||
|
||||
## Miscellaneous links
|
||||
|
||||
Some of the places, people and events mentioned yesterday, in no
|
||||
particular order (**[Ubuntourist](User:Ubuntourist "wikilink")**)
|
||||
|
||||
- **HacDC Space Blimp videos** - very cool!
|
||||
- [Space Blimp VI launch, flight and
|
||||
re-entry](https://www.youtube.com/watch?v=JhjD4Q3JfMM)
|
||||
- [Space Blimp III video with
|
||||
narration](https://www.youtube.com/watch?v=Mh8xYoCoLSU)
|
||||
|
||||
<!-- -->
|
||||
|
||||
- **Other HacDC activities**
|
||||
- Make for the Planet Hackathon, Earth Optimism Summit, Smithsonian
|
||||
Institute and Conservation X Labs
|
||||
- [Huffington Post
|
||||
article](https://www.huffingtonpost.com/entry/make-for-the-planet-challenge-transforming-conservation_us_59137564e4b04e66b8c3ad94)
|
||||
- [Tweet +
|
||||
Photo](https://twitter.com/conservationx/status/855850944063524865)
|
||||
|
||||
<!-- -->
|
||||
|
||||
- **Free Geek** - community-built refurbished computers, E-cycling,
|
||||
education centers
|
||||
- [Free Geek provides jobs and free classes to the
|
||||
community](https://opensource.com/life/13/1/free-geek) - an article
|
||||
by [Ubuntourist](User:Ubuntourist "wikilink")
|
||||
- [Free Geek Arkansas](http://www.freegeekarkansas.org/) - Formerly
|
||||
instigated and run by Julia
|
||||
- [Governance nitty-gritty for Free Geek,
|
||||
Portland](http://wiki.freegeek.org/index.php)
|
||||
|
||||
<!-- -->
|
||||
|
||||
- **Fab Lab**
|
||||
- Wikipedia: [Neil
|
||||
Gershenfeld](https://en.wikipedia.org/wiki/Neil_Gershenfeld),
|
||||
Director, MIT Center for Bits and Atoms; Creator of the Fab Lab
|
||||
"blueprint"
|
||||
- Book: [Fab: The Coming Revolution on Your Desktop-From Personal
|
||||
Computers to Personal
|
||||
Fabrication](https://books.google.com/books?id=rHdkDiUMpaUC) by Neil
|
||||
Gershenfeld. (Highly recommended.)
|
||||
|
||||
<!-- -->
|
||||
|
||||
- **Potential partners locally**
|
||||
- [John Capozzi](https://www.linkedin.com/in/john-capozzi-3154561/),
|
||||
Program Manager at The Office of the Chief Technology Officer,
|
||||
Government of the District of Columbia. He was part of the Broadband
|
||||
Bridge Coalition, and other progressive tech efforts.
|
||||
- [Mike Lee](https://www.linkedin.com/in/curiouslee/), Senior Advisor,
|
||||
Digital Strategy at AARP Digital Strategy & Membership; Founder, One
|
||||
Laptop Per Child (OLPC) Learning Club DC
|
||||
- [Leshell Hatley](http://www.leshellhatley.com/), Founder and
|
||||
Director, [Uplift, Inc.](http://upliftdc.org/) in SE DC. A fantastic
|
||||
program. ([LinkedIn
|
||||
profile](https://www.linkedin.com/in/leshellhatley/))
|
||||
- Phil Shapiro, tweeter/ promoter / dreamer / writer
|
||||
[Makezine](https://makezine.com/author/pshapiro/),
|
||||
[OpenSource.com](https://opensource.com/users/pshapiro),
|
||||
[Twitter](https://twitter.com/philshapiro),
|
||||
[LinkedIn](https://www.linkedin.com/in/phshapiro/) (He can be very
|
||||
good at "getting the word out")
|
||||
- [Greg Bloom](https://www.linkedin.com/in/gregbloom/) - serial
|
||||
digital justice crusader / organizer (no longer in the area but
|
||||
still "connected" to DC)
|
||||
- [Gerald Cooper](https://twitter.com/itwizkids) - Founder, [IT
|
||||
Computer Wizkids](https://www.itcomputerwizkids.com/)
|
||||
- [Damon Jones](https://www.linkedin.com/in/steamteacher/), Founder /
|
||||
Director, [STEAM America](http://www.steam-america.org/)
|
||||
- [Alex Dehgan](https://www.linkedin.com/in/alex-dehgan-aa81335/), CEO
|
||||
and co-Founder, [Conservation X Labs](http://conservationxlabs.com/)
|
||||
& Chanler Innovator, Duke University. He invited HacDC to
|
||||
participate in the Smithsonian Institute's Earth Optimism Summit
|
||||
**Make for the Planet** hackathon.
|
||||
- (If you talk to any of the above, drop my name.)
|
||||
- [Code for DC Brigade](https://codefordc.org/) of Code for America
|
||||
- The [Open Technology Institute
|
||||
(OTI)](https://www.newamerica.org/oti/), a division of the [New
|
||||
America Foundation](https://www.newamerica.org/), a progressive
|
||||
think tank in DC. New America Foundation has some fantastic lectures
|
||||
and panels on science, technology, and policy. OTI folks helped the
|
||||
DC Broadband Bridge group set up a neighborhood mesh network, that
|
||||
the DC government *was* hoping to model when Bryan Sivak ran OCTO.
|
||||
(Alas, the community got cut out of those conversations after Bryan
|
||||
left.)
|
||||
- [Digital Stewardship progam](http://digitalstewards.org/about) from
|
||||
the Open Technology Institute
|
||||
- [Cities of Learning, DC](https://www.lrng.org/dc) part of [Cities of
|
||||
LRNG](https://www.lrng.org/cities) (pronounced "learning"),
|
||||
mentioned by Ken
|
||||
- \[???http://www.sustainabledc.org/ Sustainable DC 2.0\] - several
|
||||
education, energy, and urban agriculture goals
|
||||
- [Youth Entrepreneur Institute
|
||||
(YEI)](http://www.youthentrepreneurinstitute.org/about-us/) -
|
||||
Tacharna Crump, Executive Director
|
||||
- [Workshop DC](http://www.workshopdc.org/?page_id=7) - also Tacharna
|
||||
Crump
|
||||
- **Non-HacDC Past Events** (a bit biased: I only know about them cuz I
|
||||
volunteered for and/or hosted them)
|
||||
- [DISCovering TECHnology Fair I (Disco Tech
|
||||
I)](https://web.archive.org/web/20160914185155/http://www.breadforthecity.org/2011/10/discovering-technology-fair-saturday/) -
|
||||
Bread for the City, November 5, 2011
|
||||
[Photos](https://www.flickr.com/photos/33621330@N07/albums/72157627954349203)
|
||||
[Washington Post
|
||||
article](https://www.washingtonpost.com/business/capitalbusiness/training-to-bridge-the-digital-divide/2011/11/10/gIQAx2YMIN_story.html)
|
||||
- [DISCovering TECHnology II (Disco Tech
|
||||
II)](https://www.facebook.com/events/692870980840136/) - Thurgood
|
||||
Marshall Academy, Anacostia, February 25, 2012
|
||||
- Photos: [Software Freedom Day at Takoma Park Folk
|
||||
Festival](https://www.flickr.com/groups/ubuntu-us-dc/) - Several
|
||||
years (plus some additional gatherings of the Ubuntu DC Local
|
||||
Community, a.k.a. the DC "LoCo")
|
||||
- Photos: [Scratch Day 2013, OLPC Learning Club
|
||||
DC](https://www.flickr.com/photos/curiouslee/sets/72157633511463081) -
|
||||
Mike's a photo junkie and tech junkie. LOTS of good photos. See the
|
||||
rest of his streams.
|
||||
- [OLPC Learning Club
|
||||
(audio)](https://archive.org/details/MikeLeeOLPCLearningClubAugustMeetingatNortelNetworks)
|
||||
and [OLPC Learning Club
|
||||
(slides)](https://www.slideshare.net/fotogeek/1ccmedia-lab-aug-2008-presentation) -
|
||||
Nortel Networks, August 2008
|
||||
|
||||
<!-- -->
|
||||
|
||||
- **Further afield** (but in cyberspace, distance is irrelevant)
|
||||
- [Detroit Digital Justice Coalition's Disco Tech
|
||||
Fair](http://detroitdjc.org/documentation-from-the-last-discotech-get-ready-for-the-next-april-15/) -
|
||||
The model for the DC Disco Techs, promoted at the [Allied Media
|
||||
Conference](https://www.alliedmedia.org/). HIGHLY RECOMMENDED: The
|
||||
[Disco Tech 'Zine](http://detroitdjc.org/discotech-zine-out-now/)
|
||||
featuring articles from both Detroit and DC folks on how to run a
|
||||
Disco Tech (Detroit, MI)
|
||||
- [Qeyno Group / Academy](https://www.qeyno.com/), co-founded and
|
||||
headmastered by [Kalimah Atreyu
|
||||
Priforce](https://www.linkedin.com/in/priforce/) (Oackland, CA)
|
||||
- [**ELiTE** Education (**E**merging **L**eaders **i**n **T**echnology
|
||||
and **E**ngineering)](http://www.elite-education.org/) - Executive
|
||||
Director, [Chelsey
|
||||
Roebuck](https://www.linkedin.com/in/chelseyroebuck) (New York City,
|
||||
NY)
|
||||
- [OPEN International](http://openinternational.org/about-open/),
|
||||
Founder: [Khady
|
||||
Lusby](https://www.linkedin.com/in/khady-lusby-9921ab21/) (Nioro,
|
||||
Mali but Khady lives in Arlington)
|
||||
- [Barre Open Source Institute
|
||||
(BOSI)](http://45.33.3.156:8080/bosivt.org), Founder, director and
|
||||
ringmaster: [Paul
|
||||
Flint](https://www.linkedin.com/in/paul-flint-98ab5b/) (Barre, VT)
|
||||
- [NextFab](https://nextfab.com/) (N. Philadelphia, PA, S.
|
||||
Philadelphia, PA and Wilmington, DE)
|
||||
- [Idea Foundry](https://ideafoundry.com/) (Columbus, OH)
|
||||
|
||||
## 2017.12.13 Virtual Reality Demo Meeting
|
||||
|
||||
In attendance:
|
||||
|
||||
- Ken Kenworthy, KnowledgeRealm, (instigator)
|
||||
- Marvin Gay, Coomunity Outreach Coordinator, [Safer, Stronger
|
||||
DC](https://www.facebook.com/SaferStrongerDC) Community Partnerships,
|
||||
[Office of the Deputy Mayor for Health and Human
|
||||
Services](https://dmhhs.dc.gov/)
|
||||
- Cameron Shields, [Safer, Stronger
|
||||
DC](https://www.facebook.com/SaferStrongerDC) Community Partnerships,
|
||||
[Office of the Deputy Mayor for Health and Human
|
||||
Services](https://dmhhs.dc.gov/)
|
||||
- Dorothy Jones-Davis, Executive Director, [Nation of
|
||||
Makers](http://nationofmakers.org/)
|
||||
- Julia Longtin (once and future queen / madame president,
|
||||
[HacDC](http://hacdc.org/))
|
||||
- Kevin Cole ([Ubuntourist](User:Ubuntourist "wikilink")) (fugitive
|
||||
at-large, [HacDC](http://hacdc.org/))
|
||||
Executable
+29
@@ -0,0 +1,29 @@
|
||||
## Listings
|
||||
|
||||
- [DCist](http://dcist.com)
|
||||
- [Washington City Paper](http://www.washingtoncitypaper.com)
|
||||
- [Washington Post](http://www.washingtonpost.com)
|
||||
- [Baltimore City Paper](http://www.baltimorecitypaper.com)
|
||||
- [Ticket Master](http://www.ticketmaster.com)
|
||||
- [Beer Advocate](http://www.beeradvocate.com)
|
||||
- [batches of tickets to events around DC for a discounted
|
||||
price.](http://www.goldstar.com/events/browse/20201)
|
||||
- [For art and local culture stuff](http://pinklineproject.com/)
|
||||
|
||||
## Museums, Clubs, Orgs
|
||||
|
||||
- [Smithsonian National Air and Space Museum](http://www.nasm.si.edu/)
|
||||
Amazing overview of mans efforts of lifting himself off the ground.
|
||||
Downtown DC near many tourist sites.
|
||||
- [National Building Museum](http://www.nbm.org/) Exhibits and
|
||||
collections on cityscapes, urban planning, building design and
|
||||
construction. Relates how we live relates to technology. Hosts many
|
||||
hands on activities throughout the year
|
||||
- [National Cryptologic
|
||||
Museum.](http://www.nsa.gov/about/cryptologic_heritage/museum/)
|
||||
- [Washington Woodworkers
|
||||
Guild](http://www.washingtonwoodworkersguild.org/)
|
||||
- [Chesapeake Area Metalworking Society](http://www.cams-club.org/)
|
||||
- [DC Maxecuter](http://dcmaxecuter.org/) Flying model aircraft club
|
||||
|
||||
[Category:Hacker Travel](Category:Hacker_Travel "wikilink")
|
||||
Executable
+85
@@ -0,0 +1,85 @@
|
||||
## Overview
|
||||
|
||||
Here are notes for myself and others interested in building DIY ECG
|
||||
equipment. There are many ways to skin this particular err.. project,
|
||||
from crude to incredibly complex. Here are lists of parts, websites,
|
||||
theory, etc.
|
||||
|
||||
Page maintained by [User:Obscurite](User:Obscurite "wikilink") who is
|
||||
working on his own ECG equipment. Enjoy.
|
||||
|
||||
## PARTS for higher-precision version(s)
|
||||
|
||||
- Instrumentation Amplifiers (not sure why these are priced so
|
||||
differently)
|
||||
- Both have CMMR of 110+ for gain of 1000, so they should both work
|
||||
equally well. AD624AD is referenced in the sciam article, but it
|
||||
also mentions the AD620A which is 1/3 the cost at about \$7.
|
||||
- Cheaper version:
|
||||
[AD620A](http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=AD620ANZ-ND)
|
||||
- Expensive version:
|
||||
[AD624AD](http://parts.digikey.com/1/parts/453660-ic-amp-inst-25mhz-prec-ln-16cdip-ad624ad.html)
|
||||
- Better op amp - OP97 (need to review data sheet)
|
||||
|
||||
## PARTS for basic version(s)
|
||||
|
||||
- LM358 (dual opamp) or LM324 (quad opamp), or LF353 (which is pin
|
||||
compatible)
|
||||
- Diodes
|
||||
- 0.1uF capacitor(s)
|
||||
- Variety of 1/4 watt resistors (10k, 100k, etc)
|
||||
- shielded wires for electrodes (phone or coax cables)
|
||||
- electrodes (soldered pennies, medical electrodes, etc)
|
||||
- diodes (1N4001)
|
||||
|
||||
## Microcontrollers and FPGAs
|
||||
|
||||
- Atmel atmega168/328 has onboard ADC
|
||||
- Xilinx Spartan3E dev board has built in ADC
|
||||
|
||||
## References
|
||||
|
||||
These sites, papers, and articles provide info on ECG making, A/D
|
||||
conversion, signal processing, projects, and general theory:
|
||||
|
||||
General info:
|
||||
|
||||
- [OpenECG Project](http://www.open-ecg-project.org/tiki-index.php)
|
||||
- [Scientific American, Shawn
|
||||
Carlson](http://www.scientificamerican.com/article.cfm?id=home-is-where-the-ecg-is)
|
||||
- [AVR ADC tutorial (a little
|
||||
old)](http://extremeelectronics.co.in/avr-tutorials/using-the-analog-to-digital-converter/)
|
||||
- [wikipedia ECG
|
||||
article](http://en.wikipedia.org/wiki/Electrocardiography)
|
||||
- [EKG Report from ITP (describes the Ramsey kit circuit,
|
||||
etc)](http://itp.nyu.edu/physcomp/sensors/Reports/EKG)
|
||||
|
||||
DIY Projects (some with tutorials):
|
||||
|
||||
- [DIY ECG, Scott
|
||||
Harden](http://www.swharden.com/blog/2009-08-14-diy-ecg-machine-on-the-cheap/)
|
||||
- [DIY ECG Improvements (based on Jason Nguyen's 6 opamp design), also
|
||||
from Scott
|
||||
Harden](http://www.swharden.com/blog/2009-01-20-diy-ecg-improvements/)
|
||||
- [DIY ECG, Jason
|
||||
Nguyen](http://www.eng.utah.edu/~jnguyen/ecg/ecg_index.html)
|
||||
- [ECG Measurement System, Chia-Hung Chen, Shi-Gun Pan, Peter
|
||||
Kinget](http://www.cisl.columbia.edu/kinget_group/student_projects/ECG%20Report/E6001%20ECG%20final%20report.htm)
|
||||
- [DIY ECG howto (AD620A and OP97 used in schematic) by Refik
|
||||
Hadzialic](http://www.radiolocman.com/shem/schematics.html?di=47010)
|
||||
- [Refik Hadzialic's AVR ADC code for his
|
||||
ECG](http://www.rlocman.ru/i/File/2008/04/15/egg.txt)
|
||||
- [Holter ECG based on AVR by Dragisa
|
||||
Jankovic](http://www.gilefx.com/avrecg.htm)
|
||||
- [also an ARM based Holter ECG by Dragisa
|
||||
Jankovic](http://www.gilefx.com/armecg.htm)
|
||||
- [Homemade EKG by Jake Haglund](http://www.diyhappy.com/homemade-ekg)
|
||||
- [Dual-purpose EEG/EKG by artist/composer Adam
|
||||
Overton](http://plus1plus1plus.org/Resources/EEG-EKG)
|
||||
|
||||
Kits:
|
||||
|
||||
- [Ramsey ECG
|
||||
kit](http://www.ramseyelectronics.com/cgi-bin/commerce.exe?preadd=action&key=ECG1C)
|
||||
|
||||
[Category:DIY_ECG](Category:DIY_ECG "wikilink")
|
||||
Executable
+41
@@ -0,0 +1,41 @@
|
||||
## Description
|
||||
|
||||
The process taken to make a Hackerspace Passport of similar quality to a
|
||||
US passport.
|
||||
|
||||
## Status
|
||||
|
||||
Received parts (paper and cover material)
|
||||
|
||||
## Plan
|
||||
|
||||
Use paper and cover material similar to US passport to make Hackerspace
|
||||
Passports
|
||||
|
||||
1. order fancy paper and vinyl cover material (done)
|
||||
- ordered 100% cotton paper and [vinyl report
|
||||
covers](http://www.factory-express.com/Supplies/BindingSupplies/BindingCovers/bindingcovers.html)
|
||||
2. make wood/plastic block stamps to print the generic info and layouts
|
||||
- planning to use the CNC to route the SVGs to wood blocks or PCB
|
||||
blanks
|
||||
3. make/order inks for printing
|
||||
- depends on the printing blocks
|
||||
4. print a test run on regular printer paper
|
||||
- the cotton paper is cheaper than gold but more expensive than
|
||||
plain printer paper by a lot
|
||||
5. print a Hackerspace Passport
|
||||
- pages only here
|
||||
6. figure out that whole embossing thing
|
||||
- pressing down the vinyl til it satays that way i get but the
|
||||
application of the metal leaf in conjunction is outside my realm
|
||||
of experience
|
||||
7. emboss cover art
|
||||
- insert magic here
|
||||
8. bind a Hackerspace Passport
|
||||
- my US passport is bound with some fancy string. i think i'll use
|
||||
telcom twisted pairs for mine :P
|
||||
9. enjoy perplexed look on TSA officers face when they search my bag at
|
||||
<insert major transit point here>
|
||||
- "WTF?" is such a satisfying expression to see :P
|
||||
|
||||
[Category:Previous Projects](Category:Previous_Projects "wikilink")
|
||||
Executable
+27
@@ -0,0 +1,27 @@
|
||||
## Problem
|
||||
|
||||
DSONano v2 with DFU loader v3.26 does not work with the firmware used by
|
||||
the other v2 models. The drivers for the LCD display changed so flashing
|
||||
the "normal" thirdparty firmware causes an all white screen to persist
|
||||
on the screen. In some cases it flickers as well.
|
||||
|
||||
## Sollution
|
||||
|
||||
1. use the patched firmware provided
|
||||
[here](http://www.seeedstudio.com/forum/viewtopic.php?f=22&t=4823&sid=3e537c759d444eb3ae50c74adf5fc1eb&start=40)
|
||||
and mirrored
|
||||
[here](Media:BenF_P2-3.64APP_3.53LIB_LCD_patched_v2.hex "wikilink")
|
||||
|
||||
### flashing
|
||||
|
||||
1. plug the dsonano in via usb
|
||||
2. press the down arrow and power on the device
|
||||
3. mount the block device (/dev/sdX, no number)
|
||||
4. copy the .hex file to the mount point
|
||||
5. wait for it to dissappear
|
||||
6. unmount the mount point
|
||||
7. mount the new block device
|
||||
8. check to see that the extension on the file now reads .RDY (limited
|
||||
file name length truncates the rest of the name sometimes)
|
||||
9. powercycle to check if it worked
|
||||
10. repeat until it works
|
||||
+42
@@ -0,0 +1,42 @@
|
||||
This is a proposal to create an ongoing event aimed at procuring more
|
||||
quality hardware for HacDC.
|
||||
|
||||
## Proposal Vitals
|
||||
|
||||
**Status**: In Progress, Discussion
|
||||
|
||||
- Project Lead: ?
|
||||
- Proposed Budget: \$0
|
||||
- Goals:
|
||||
- To obtain more quality hardware for HacDC
|
||||
- To teach the public/corporations about proper Data Destruction
|
||||
techniques
|
||||
- To build relationships with potential donors, future sources of
|
||||
hardware
|
||||
- To develop & demo creative ways of recycling computers
|
||||
|
||||
## Detailed Proposal
|
||||
|
||||
A lot of local companies and non-profits have old computers sitting
|
||||
around. They know they need to destroy the data before the dispose of
|
||||
the machines, but they can't afford a professional disposal service.
|
||||
|
||||
I thought it would be fun to have a public event where we would teach
|
||||
people how to dismantle and destroy their hard-drives. We could pitch it
|
||||
as a security event, capitalizing on the Hacker name in a positive way.
|
||||
We could publicize the event by sending invitations to local companies,
|
||||
perhaps through the chamber of commerce. I'd like to also invite local
|
||||
non-profits but I don't know if there's an easy way to reach them.
|
||||
|
||||
My thought was that we could harvest the magnets and use them to build a
|
||||
windmill generator. The only problem is that I've been too tired to
|
||||
follow through. My current consulting arrangment ends on the first of
|
||||
January. If I don't get another job or contract immediately I may have
|
||||
time to work on this.
|
||||
|
||||
## Links
|
||||
|
||||
[1](http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.20.1489)
|
||||
[2](http://ccrma-www.stanford.edu/~verplank/ThePlank.pdf)
|
||||
|
||||
[Category:Proposed Projects](Category:Proposed_Projects "wikilink")
|
||||
Executable
+87
@@ -0,0 +1,87 @@
|
||||
## References
|
||||
|
||||
Some links to get us started:
|
||||
|
||||
[Bit](wikipedia:Bit "wikilink")
|
||||
|
||||
[Byte](wikipedia:Byte "wikilink")
|
||||
|
||||
[Pointer](wikipedia:http:Pointer_(computing) "wikilink")
|
||||
|
||||
[6502](wikipedia:MOS_Technology_6502 "wikilink")
|
||||
|
||||
[6502 instruction
|
||||
set](http://e-tradition.net/bytes/6502/6502_instruction_set.html)
|
||||
|
||||
[Atari 8-bit documentation online](http://www.atariarchives.org/)
|
||||
|
||||
[Atari 8-bit memory
|
||||
map](http://www.atariarchives.org/mapping/memorymap.php)
|
||||
|
||||
[Atari 800 emulator](http://atari800.sourceforge.net/)
|
||||
|
||||
[Altirra - an Atari 800 emulator for
|
||||
Windows](http://www.virtualdub.org/altirra.html)
|
||||
|
||||
[A ton of Atari 8-bit
|
||||
documentation](http://thepiratebay.org/torrent/5576778)
|
||||
|
||||
[Atari 8-bit
|
||||
ROMS](http://sourceforge.net/projects/atari800/files/ROM/Original%20XL%20ROM/xf25.zip/download)
|
||||
|
||||
[Space
|
||||
Invaders](http://www.atarimania.com/game-atari-400-800-xl-xe-space-invaders_4831.html)
|
||||
|
||||
git repository for work so far is at
|
||||
<git://git.cluephone.com/atari8/spaceinvaders/>
|
||||
|
||||
[gitweb view of
|
||||
above](http://git.cluephone.com/git/gitweb.cgi?p=atari8/spaceinvaders)
|
||||
|
||||
## Getting Started
|
||||
|
||||
prerequisites
|
||||
|
||||
- knowledge
|
||||
- tools
|
||||
- emulator
|
||||
- cc65
|
||||
- roms
|
||||
- documentation of the atari 800
|
||||
|
||||
Toolchain
|
||||
|
||||
` get and install cc65, etc.`
|
||||
|
||||
` * description of the various tools included in the package`
|
||||
|
||||
Set up your info file:
|
||||
|
||||
` jason started with the example info file from the cc65 website`
|
||||
` `[`http://www.cc65.org/doc/da65-4.html#ss4.7`](http://www.cc65.org/doc/da65-4.html#ss4.7)
|
||||
|
||||
` ** notes about setting up your info file`
|
||||
` tell the DA what is code, what is a bytetable, what is a list of addresses`
|
||||
` tell the DA about the labels you are aware of`
|
||||
|
||||
` iterative process of creating this info file as you learn more about the program`
|
||||
|
||||
` eventually naming functions, etc.`
|
||||
|
||||
disassemble your ROM
|
||||
|
||||
`da65 --start-addr 0xa000 Space\ Invaders.rom --comments 3`
|
||||
|
||||
re-assemble your ROM
|
||||
|
||||
` first time, this should be from the base output from the disassembly`
|
||||
` subsequent assemblies will include changes that you made to the ASM in your quest for information`
|
||||
|
||||
ITERATE
|
||||
|
||||
[6502 cross-compiler and tools](http://www.cc65.org)
|
||||
|
||||
[Atarimania 8-bit
|
||||
games](http://www.atarimania.com/pgemainsoft.awp?type=G&system=8)
|
||||
|
||||
[Category:Classes](Category:Classes "wikilink")
|
||||
+23
@@ -0,0 +1,23 @@
|
||||
Problem 4, Part D was omitted from the solutions. It is presented here.
|
||||
|
||||
D\) What is t_pd of the fastest equivalent circuit (i.e. one that
|
||||
implements the same function) built using only the three components
|
||||
listed above?
|
||||
|
||||
Lets start by reducing the logic equation....I'm going to use three
|
||||
intermediary signals, alpha, beta and gamma, and pull identity numbers
|
||||
from the slides
|
||||
|
||||
alpha=!(A+B) beta=!(alpha+A) gamma=!(alpha+!B) OUT=!(beta+gama)
|
||||
|
||||
OUT=!(!(alpha+A) + !(alpha+!B)) substitution OUT=!(!(!(A+B)+A) +
|
||||
!(!(A+B)+!B)) substitution OUT=!(!(!A\*!B+A) + !(!A\*!B+!B)) demorgans
|
||||
OUT=!!(!A\*!B+A) \* !!(!A\*!B+!B) demorgans OUT= (!A\*!B+A) \*
|
||||
(!A\*!B+!B) identity 4 elementary OUT= (!A\*!B+A) \* (!B) identity 10
|
||||
absorption OUT= (!A\*!B+A\*!B) identity 8 distributivity OUT= !B (!A +
|
||||
A) identity 8 distributivity OUT= !B 5 elementary
|
||||
|
||||
Since this can be implemented with a single inverter, the smallest
|
||||
propagation delays is 1ns.
|
||||
|
||||
[Category:FPGAWorkshop](Category:FPGAWorkshop "wikilink")
|
||||
Executable
+19
@@ -0,0 +1,19 @@
|
||||
## Proposal
|
||||
|
||||
Very nebulous idea at the moment, but the idea would be to build a
|
||||
distributed lightning detection system, with the intended goal of having
|
||||
precision high enough to go find the aftereffects of strikes (like
|
||||
[geocaching](http://en.wikipedia.org/wiki/Geocaching)). After thinking
|
||||
of this, I found some dutch folks have done [much what I had in
|
||||
mind](http://members.home.nl/fkooiman/lightning/), so the problem is
|
||||
kind of a solved one. Still, it would be neat thing to make, and it
|
||||
doesn't appear to have a stateside equivalent yet (its sort of a public
|
||||
service project). [Here](http://www.blitzortung.org/) is live data
|
||||
coming from the central European system.
|
||||
|
||||
I've heard the government runs these, but I haven't found any place the
|
||||
data is accessible online. If that's the case (and it's fairly high res)
|
||||
my enthusiasm for this idea is dimmed a lot.
|
||||
--[Bjorn](User:Bjorn "wikilink") 14:49, 28 May 2008 (UTC)
|
||||
|
||||
[Category:Proposed_Projects](Category:Proposed_Projects "wikilink")
|
||||
Executable
+33
@@ -0,0 +1,33 @@
|
||||
Tabletop computer terms - move over means to use the touch pad to move
|
||||
the arrow on the display to the described position click on means to
|
||||
move the arrow to the described position & then press either click
|
||||
button type means to type what is described type: means to type the
|
||||
characters that follow the space after : enter means to type what is
|
||||
described (if anything) & then press the Enter key (at right) enter:
|
||||
means to type the characters that follow the space after : & then press
|
||||
Enter insCADImp How to use ImplicitCAD on one of the tabletop
|
||||
computers - Dec. 26, 2019 version I.1 Turn on the computer & log in (see
|
||||
Documentation-Tabletop_computers for detailed instructions) I.2 Click on
|
||||
Applications (top left) I.3 Move over System Tools I.4 Click on MATE
|
||||
Terminal in window that just appeared I.5 To connect (ssh) thru the
|
||||
HacDC network & perform the following on the renderadmin computer
|
||||
instead of the tabletop computer type: ssh renderadmin@jobs.hacdc.org
|
||||
I.6 At renderadmin@jobs.hacdc.org's password: enter standard password
|
||||
I.7 Enter cd directorybeingused/ (i.e., ImplicitCAD/radioshack_box/) I.8
|
||||
Enter emacs -nw file.escad (i.e., testcube.escad - editor (one of many
|
||||
that can be used) for creating or modifying file (in this case object
|
||||
description)) I.9 Create or modify object description I.10 Type Ctrl X
|
||||
Ctrl S (saves file) Ctrl X Ctrl C (exits from editor) I.11 Enter make
|
||||
file.stl (i.e., testcube.stl - convert from object description (.escad)
|
||||
to surface description (.stl)) I.12 Wait - complex objects can take a
|
||||
very long time I.13 If there is an error then repeat I.8-I.12 as many
|
||||
times as necessary I.14 To disconnect from the renderadmin computer
|
||||
enter: exit I.15 Enter scp
|
||||
renderadmin@jobs.hacdc.org:/home/renderadmin/directorybeingused/file.stl
|
||||
./ (i.e.,
|
||||
renderadmin@jobs.hacdc.org:/home/renderadmin/ImplicitCAD/radioshack_box/testcube.stl
|
||||
./ - copy source, item, to; copy file back to tabletop computer) I.16 At
|
||||
Password: enter standard password I.17 Enter meshlab file.stl (i.e.,
|
||||
meshlab testcube.stl - display object) I.18 At Post-Open Processing:
|
||||
click on OK I.19 After examining object type Ctrl Q (exits from meshlab)
|
||||
I.20 Repeat I.5-I.19 as many times as needed
|
||||
Executable
+59
@@ -0,0 +1,59 @@
|
||||
HacDC computer network - Jan. 2, 2020 Tabletop computer terms - move
|
||||
over means to use the touch pad to move the arrow on the screen to the
|
||||
described position click on means to move the arrow to the described
|
||||
position & then press either click button type means to type what is
|
||||
described type: means to type the characters that follow the space after
|
||||
: enter means to type what is described (if anything) & then press the
|
||||
Enter key (at right) enter: means to type the characters that follow the
|
||||
space after : & then press Enter It is possible to connect to devices on
|
||||
the network using the internet or using the local network. To connect
|
||||
using the internet: 1. Enter ssh systemname@machinename.hacdc.org (i.e.,
|
||||
ssh renderadmin@jobs.hascdc.org) 2. At Password: enter standard password
|
||||
To connect using the HacDC network: 1. Enter ssh
|
||||
systemname@machinename.local (i.e., ssh renderadmin@jobs.local) 2. If
|
||||
the system asks Are you sure you want to continue connecting (yes/no)?
|
||||
enter: yes 3. At Password: enter standard password To check if it is
|
||||
possible to communicate with a device: 1. Open a MATE terminal (if not
|
||||
already present; see Documentation-Tabletop_computers) 2. Enter ping
|
||||
machinename.hacdc.org or ping machinename.local (i.e., ping jobs.local)
|
||||
3. If it responds \## bytes from \###... it is communicating 4. To stop
|
||||
pinging type Ctrl C To determine the path to the address the computer is
|
||||
connected to: 1. Enter mtr address (i.e., mtr jobs.hacdc.org) 2. When
|
||||
finished click on Quit If the network will not connect: 1. Try using the
|
||||
other connection method (.local if .hacdc.org doesn't work or vice
|
||||
versa) 2. Check if it is possible to communicate by using ping (see
|
||||
above) 3. If it is not communicating stop here & get help 4. Enter mtr
|
||||
address (i.e., mtr jobs.hacdc.org) 5. Look at the column labeled Loss;
|
||||
if any of the values are close to 100% that could be the problem 6.
|
||||
Click on Quit 7. If there was a problem with the path restart the
|
||||
computer & hope it uses a different path this time Components of the
|
||||
network: Renderadmin computer (large computer at left under table below
|
||||
clock) - for converting .escad files to .stl files for 3D printing
|
||||
etc. - machine name=jobs, system name=renderadmin 3D printer computer
|
||||
(Dell Optiplex 760 to left of Rostock) - controls Rostock, Mini, & Taz
|
||||
3D printers - machine name=pronterhost, system name=hacdc Classroom TV
|
||||
computer (large Sharkoon below big screen) - controls screen - machine
|
||||
name=classroom-tv, system name=hacdc Laser cutter computer (small
|
||||
computer in cabinet below laser cutter) - controls laser cutter Here is
|
||||
the current HacDC network wiring: On floor below clock - Netgear ProSAFE
|
||||
16-Port Gigabit Click Switch 1 - gray - TP-Link Router 2 2 - gray -
|
||||
Printer (paper) computer 14 - white - open (by laser cutter) 16 -
|
||||
orange - renderadmin computer others - no connection On bottom shelf
|
||||
over sink - LinkSys VOIP Voice Phone - phone cable - Uniden EX18560
|
||||
phone Internet - blue - LinkSys switch 6 C7 TP-Link AC1750 Wireless
|
||||
Dual-Band Gigabit Router Internet - blue - D-Link switch Ethernet 1 -
|
||||
gray - open 2 - yellow - TP-Link switch 7 Middle shelf - D-Link Wireless
|
||||
AC750 Dual-Band Router DIR-817LW LAN 4 - blue - TP-Link switch 8
|
||||
Internet - gray - LinkSys switch 5 TP-Link TL-SG1008D Gigabit Switch 1 -
|
||||
yellow - wall socket 2 - gray - Netgear switch 1 3 - blue - 3D printer
|
||||
computer 4 - no connection 5 - black - Linksys switch 1 6 - no
|
||||
connection 7 - yellow - TP-Link router Ethernet 2 8 - blue - D-Link
|
||||
router LAN 4 Linksys Gigabit 8-Port Workgroup Switch (note that the
|
||||
connections on this switch are numbered from right to left while the
|
||||
TP-Link switch is left-to-right) 1 - black - TP-Link switch 5 2 - no
|
||||
connection 3 - gray - open (below HARC) 4 - black - open (below HARC)
|
||||
5 - gray - D-Link router Internet 6 - blue - Linksys VOIP Voice Internet
|
||||
7 - blue - open (below HARC) 8 - no connection On table below TV
|
||||
screen - D-Link igreen DGS-1005D switch 1 - blue - TP-Link router
|
||||
Internet 2 - gray - open 3-4 - no connection 5 - yellow - TV computer If
|
||||
I read this right 3 of the 4 switches are unnecessary!
|
||||
Executable
+18
@@ -0,0 +1,18 @@
|
||||
Cordless telephone To change the cordless phone ring: 1. Hold down cid
|
||||
(menu) button (top right) until phone beeps a 2nd time and text is
|
||||
displayed (the arrowhead at the left should be at the top pointing to
|
||||
Ringer; the up/down button moves the arrowhead). 2. Press select channel
|
||||
button (bottom) to select desired ring (don't use Type A since it's the
|
||||
same as the door intercom; Type C is recommended). 3. Press END button.
|
||||
Brother printer To adjust the paper tray (note that paper feeds from the
|
||||
front of the tray): 1. Slide the blue button in the back side of the
|
||||
tray out (away from the tray) 2. Squeeze the vertical blue tab near the
|
||||
center of the back side & move the back side in or out 3. Slide the blue
|
||||
button in (towards the tray) If the back side is pulled all the way out
|
||||
14" (legal size) paper should fit. If the paper seems to be too long to
|
||||
fit in the tray pull the back side out no more than is needed for the
|
||||
paper to fit. If the tray will not go in all the way but goes in if the
|
||||
paper is removed try pulling the back side out & make sure the paper
|
||||
fits correctly (does not stick up). If the paper does not feed but there
|
||||
is no sign of jamming try pushing the back side in until the paper is
|
||||
snug (but does not stick up).
|
||||
Executable
+93
@@ -0,0 +1,93 @@
|
||||
Using the tabletop computers Terms - move over means to use the touch
|
||||
pad to move the arrow on the screen to the described position click on
|
||||
means to move the arrow to the described position & then press either
|
||||
click button type means to type what is described type: means to type
|
||||
the characters that follow the space after : enter means to type what is
|
||||
described (if anything) & then press the Enter key (at right) enter:
|
||||
means to type the characters that follow the space after : & then press
|
||||
Enter To use a tabletop computer (should be stored on the Tabletop
|
||||
Computer cart to the right of the laser cutter; make sure there is a USB
|
||||
drive glued into the back) - Dec. 26, 2019: C.1 Plug the round connector
|
||||
of a tabletop computer power supply (19-20V; they should be on the cart
|
||||
next to the computers) into the hole at the left of the back of the
|
||||
computer. C.2 Plug the power supply into an outlet that has power. C.3
|
||||
Slide the silver latch at the front of the computer to the right & open
|
||||
the computer. C.4 Push the power button in the right end of the hinge (3
|
||||
green lights should briefly come on at the center back of the computer,
|
||||
then the left one should come back on & stay on) C.4 If the display
|
||||
states Strike the F1 key to continue then press F1 (at left of back) C.5
|
||||
At Login: (it takes a long time to appear) enter: hacdc C.6 At Password:
|
||||
enter standard password To use the computer for general use (Linux) -
|
||||
Dec. 12, 2019: G.1 Click on Applications (top left of display) G.2 Move
|
||||
over System Tools (at bottom of new list) G.3 Click on MATE Terminal
|
||||
(middle of 2nd list; new window should appear) To use the computer to
|
||||
access the internet - Dec. 12, 2019: I.1 Click on Applications (top left
|
||||
of display) I.2 Move over Internet (middle of new list) I.3 Move over
|
||||
directly to the right to Chromium Web Browser in the 2nd list I.4 Click
|
||||
on the desired web browser To shut off the computer - Dec. 12, 2019: S.1
|
||||
Click on System (top left of display) S.2 Click on Shut Down on new list
|
||||
S.3 To speed things up click on Shut Down at bottom right of new window
|
||||
If the computer isn't responding at all hold down the power button in
|
||||
the right end of the hinge until it shuts off To update the software -
|
||||
Feb. 23, 2020: U.1 In a MATE terminal (see To use the computer for
|
||||
general use (Linux) above) enter: sudo apt update U.2 If the terminal
|
||||
displays \[sudo\] password for hacdc: then enter standard password U.3
|
||||
Optional - to see what updates exist enter: sudo apt list --upgradable
|
||||
\| most U.4 Optional - to see how much space is available on the USB
|
||||
drive enter: df -h U.5 enter: sudo apt full-upgrade U.6 When the
|
||||
terminal states how much additional disk space will be used and asks Do
|
||||
you want to continue? \[Y/n\] enter: y U.7 If at any point the terminal
|
||||
states that a file has been modified and asks what you would like to do
|
||||
about it (keep your currently-installed version is preselected) note the
|
||||
file name and enter U.8 If the terminal states that xdm must be stooped
|
||||
before the upgrade & If you want to interrupt the upgrade now and
|
||||
continue later, please answer No to the question below. \<Ok\> (\<Ok\>
|
||||
should be preselected) enter U.9 If the terminal asks Do you want to
|
||||
upgrade glibc now? \<Yes\> \<No\> (Yes should be preselected) enter U.10
|
||||
If the terminal states Display manager must be restarted manually...
|
||||
(\<Ok\> should be preselected) enter U.11 If the terminal states The
|
||||
grub boot loader was previously installed to a disk that is no longer
|
||||
present, ... & asks for GRUB install devices: enter space (selects
|
||||
first) down arrow space (selects second too) tab U.12 If the terminal
|
||||
asks for any other input (an option should be preselected as the
|
||||
default) enter U.13 When the update is finished enter: sudo shutdown -r
|
||||
now U.14 If the graphical display (not just a text display like the
|
||||
terminal) reappears (it takes a while) after logging in skip steps
|
||||
U.15-U.18 U.15 enter: sudo apt-get purge xserver-xorg-video-intel U.16
|
||||
sudo shutdown -r now U.17 sudo apt-get install xserver-xorg-video-intel
|
||||
U.18 sudo shutdown -r now U.19 In a MATE terminal enter: emacs -nw
|
||||
update.txt U.20 Enter or change the date of the update U.21 Enter or
|
||||
change the list of files that weren't updated because they had been
|
||||
modified (see step U.7) U.22 Type Ctrl x Ctrl s Ctrl x Ctrl c To install
|
||||
minicom - Dec. 23, 2019: M.1 If a MATE Terminal is already displayed
|
||||
then skip steps M.2-M.4 M.2 Click on Applications at top left M.3 Move
|
||||
over System Tools M.4 Click on MATE Terminal M.5 Enter: sudo apt install
|
||||
minicom M.6 If the screen displays \[sudo\] password for hacdc: then
|
||||
enter standard password M.7 If the display asks Do you want to continue?
|
||||
\[Y/n\]: then enter: y M.8 When hacdc@XXXXXXX:~\$ (where XXXXXXX is the
|
||||
computer name) appears (it takes a while) enter: sudo minicom -s M.9
|
||||
Press down arrow twice to move highlighted line down to: Serial port
|
||||
setup M.10 Enter M.11 If A - Serial Device : is /dev/ttyACM0 then skip
|
||||
M.12-M.14 M.12 At Change which setting? type: a M.13 Use the Backspace
|
||||
key to change /dev/modem to /dev/ttyACM0 M.14 Enter M.15 Enter M.16
|
||||
Press down arrow twice to move highlighted line down to Screen and
|
||||
keyboard M.17 Enter M.18 At Change which setting? (Esc to exit) if Q -
|
||||
Local echo : is no then type: q M.19 If T - Add carriage return : is no
|
||||
then type: t M.20 Enter M.21 Press down arrow to move highlighted line
|
||||
down to Save setup as dfl M.22 Enter (Configuration saved should appear
|
||||
briefly) M.23 Press down arrow 3 times to move highlighted line to Exit
|
||||
from Minicom M.24 Enter M.25 Enter: sudo usermod -G dialout hacdc M.26
|
||||
Click on System at top towards left M.27 Click on Log Out hacdc... M.28
|
||||
To speed things up click on Log Out at lower right of new window M.29 At
|
||||
Login: enter hacdc M.30 At Password: enter standard password M.31 Repeat
|
||||
steps M.2-M.4 M.32 emacs -nw installed.txt M.33 Add minicom (in
|
||||
alphabetical order if a list already exists) M.34 Type Ctrl x Ctrl s
|
||||
Ctrl x Ctrl c (always hold down the Ctrl key while pressing the
|
||||
following letter) M.35 Enter minicom To rename the computer - Jan. 13,
|
||||
2020: N.1 Enter: sudo -i N.2 If the display shows \[sudo\] password for
|
||||
hacdc: then enter standard password N.3 cd /etc/ N.4 Enter: nano
|
||||
hostname N.5 Change the name to the new name N.6 Type Ctrl x N.7 At Save
|
||||
modified buffer? type: y N.8 At File Name to Write: hostname enter N.9
|
||||
Enter: nano hosts N.10 Change the name on the 2nd line to the new name
|
||||
N.11 Type Ctrl x N.12 At Save modified buffer? type: y N.13 At File Name
|
||||
to Write: hosts enter N.14 Enter: reboot
|
||||
Executable
+43
@@ -0,0 +1,43 @@
|
||||
This page collects information about how to use
|
||||
[hacdc.org](http://hacdc.org/)'s copy of Drupal. To use the website to
|
||||
create content, you need to sign up for an account on the drupal page,
|
||||
activate your account (follow instructions in the email), and then bug
|
||||
Will Gibb to make sure your account is setup as a member.
|
||||
|
||||
# Creating a blog post
|
||||
|
||||
The site's blog content is driven by content nodes. To add something to
|
||||
it, [create a new story "node"](http://hacdc.org/node/add/story) and
|
||||
fill it out the page appropriately. Give your story a title and content.
|
||||
You can add content in HTML, Wordpress or drupal wiki markup langauge.
|
||||
You have the option of splitting your post into two parts, with the
|
||||
"Split summary at cursor" option, if you have a longer post than you
|
||||
feel is appropriate for the main site.
|
||||
|
||||
Your post will automatically be sent to the HacDC twitter feed. You can
|
||||
disable this (why would you?) or change the title. You can use !url,
|
||||
!url-alias, !tinyurl, !title and !user as replacement text.
|
||||
|
||||
You can also attach images to your post and use them inline. You can
|
||||
also post images to the wiki. To do that, you can use the <img> HTML
|
||||
tag, and set your input to "Full HTML". You can read more about how to
|
||||
use the img tag here \[syntax\]
|
||||
<http://www.w3schools.com/tags/tag_img.asp> and here \[examples\]
|
||||
<http://www.htmlkit.com/minit/pages/imgtag1.html> Poke around the drupal
|
||||
site and see how other authors have used the img tag in their posts, to
|
||||
do positioning. Katie has some pretty good examples.
|
||||
|
||||
# Adding an Event
|
||||
|
||||
Drupal's [calendar](http://hacdc.org/date-browser) is driven by content
|
||||
nodes. To add something to it, [create a new event
|
||||
"node"](http://hacdc.org/node/add/event) and fill it out. That node is
|
||||
what the calendar will link to. If you select "Promoted to front page"
|
||||
(under "Publishing options") it will also be published to the front
|
||||
page, as a blog post like thing. **Note:** Please include an end time as
|
||||
well as a start time, even if it's just approximate. Otherwise chaos
|
||||
will ensue as different pieces of software assume different things.
|
||||
|
||||
Once you have created an event, it may take an hour or more for it to
|
||||
appear in the web side's sidebar and in the Google Calendar version of
|
||||
our calendar.
|
||||
Executable
+56
@@ -0,0 +1,56 @@
|
||||
Note that, as a point of distinction from the [Physical Access Control
|
||||
Project](Physical_Access_Control_Project "wikilink"), this project's
|
||||
scope includes the whole [church](http://www.saintstephensdc.org/), its
|
||||
staff and tenants.
|
||||
|
||||
There was a meeting in the space at 1pm on Saturday, 6 December 2008 to
|
||||
start prototyping the Asterisk back-end.
|
||||
|
||||
Discussion is taking place on [the red door mailing
|
||||
list](http://hacdc.org/mailman/listinfo/reddoor_hacdc.org).
|
||||
|
||||
# Current plans
|
||||
|
||||
As per a discussion Nate had with Brian on Tuesday, December 16th, here
|
||||
are the current plans:
|
||||
|
||||
Requirement: the person doing the unlocking must see the guest before
|
||||
opening the door. So, unlocking by phone is not permissible. Either get
|
||||
video on screen, or just walk downstairs and see 'em through the window.
|
||||
|
||||
Outside: All that's needed is a camera, a keypad, and a place Brian can
|
||||
stick a printed directory page. Two-way audio (speakerphone at the
|
||||
outside panel) would be nice too but isn't a strict requirement. The
|
||||
video will be served to the internet over St. Stephen's internet
|
||||
connection.
|
||||
|
||||
When a guest dials a suite number: (which will be a 1 or 2 digit number,
|
||||
probably followed by the star or pound key) The system should place a
|
||||
call over the PSTN to ring whoever's associated with that space. The
|
||||
suite-number-to-phone-number lookup table will be maintained by Brian.
|
||||
|
||||
When the phone is answered: It'd be nice to have two-way audio to the
|
||||
panel, so the answerer can talk to the guest and ascertain who they are.
|
||||
BUT UNLOCKING CANNOT BE DONE BY PHONE. See "requirement", above.
|
||||
|
||||
To unlock the door: The answerer (or anyone else) can just walk
|
||||
downstairs and open the door, OR pull up video over the web, and after
|
||||
having visually confirmed the guest's identity, the answerer can enter
|
||||
their PIN on the website and unlock the door that way. So the webserver
|
||||
will need a copy of the PIN database, or will need to forward all
|
||||
attempts to some other device to try them.
|
||||
|
||||
Any authorized user can just enter their PIN at the keypad and let
|
||||
themself in, of course. (Yeah, I know that's not a word. Bite me,
|
||||
English language!)
|
||||
|
||||
Caveat: The answerer could just tell their PIN to the guest over the
|
||||
phone, couldn't they? To prevent this, and enforce the face-view
|
||||
requirement, perhaps the keypad could refuse to accept PINs for a while
|
||||
after dialing a suite number.
|
||||
|
||||
Ideally: Video from the panel camera will be split, so it can be
|
||||
digitized by the web video server AND by the surveillance recorder in
|
||||
Brian's office, which is NOT connected to the internet.
|
||||
|
||||
[Category:Previous Projects](Category:Previous_Projects "wikilink")
|
||||
Executable
+60
@@ -0,0 +1,60 @@
|
||||
//Front Door Switch Holder
|
||||
//Mark 5
|
||||
//James Sullivan
|
||||
//4/28/17
|
||||
//OpenSCAD version 2015.03-1
|
||||
//HacDC, cheap Chinese laser, K40, 40 watt
|
||||
//This part holds 2 microswitches to shut down the laser power supply if the cutting chamber door or the control equipment chamber door is opened
|
||||
thick=5; //thickness of part
|
||||
metal=1; //metal thickness
|
||||
slot=16; //width of slot in mount, width of flange on machine, full width outside to outside!
|
||||
//height=16; //z distance of mount, extrusion height, installed length
|
||||
pin=1.25; //switch hold radius
|
||||
pitch = 10 ; //switch hole center-center distance
|
||||
ph = 9; //pin height, centerline of screw holes above flange top
|
||||
height = pitch + 6 * pin; //z distance of mount, extrusion height, installed length
|
||||
wr=4; //wrench size for nuts width across flats
|
||||
nh=1; //nut height, depth of nut sockets
|
||||
lfw=15; // left flange width, distance from left face of machine flange to right face of left mounting post
|
||||
nhl = slot + lfw + 2 * nh; //nut hole length
|
||||
tw=slot+lfw+2*thick; //total width
|
||||
$fn=40;
|
||||
difference(){
|
||||
union(){
|
||||
translate([-lfw,0,0]) cube([tw,thick,height]); //top horizontal
|
||||
translate([thick+metal,-thick-metal,0]) cube([slot+thick-metal,thick,height]); //lower horizontal
|
||||
translate([-lfw,0,0]) cube([thick,ph+3*pin,height]); //far left vertical
|
||||
translate([0,-metal-thick*1.5,0]) cube([thick,metal+thick*2.5,height]); //left vertical
|
||||
translate([thick+metal,-1.5*thick-metal,0]) cube([thick,thick*1.5,height]); //center vertical
|
||||
translate([slot+thick,-metal-thick,0]) cube([thick,metal+thick+ph+3*pin,height]); //right vertical
|
||||
translate([0,0,height/2]) cube([thick*2,thick*2,height],center=true); //fillet material
|
||||
}
|
||||
translate([-1.5*thick-lfw,ph,(height-pitch)/2]) rotate([0,90,0]) cylinder(r=pin,h=tw+2*thick); //bolt hole
|
||||
translate([-1.5*thick-lfw,ph,(height+pitch)/2]) rotate([0,90,0]) cylinder(r=pin,h=tw+2*thick); //bolt hole
|
||||
translate([nhl/2-lfw+thick-nh,ph,(height-pitch)/2]) union(){ //nut sockets
|
||||
cube([nhl,wr/sqrt(3),wr],center=true);
|
||||
rotate([120,0,0]) cube([nhl,wr/sqrt(3),wr],center=true);
|
||||
rotate([240,0,0]) cube([nhl,wr/sqrt(3),wr],center=true);
|
||||
}
|
||||
translate([nhl/2-lfw+thick-nh,ph,(height+pitch)/2]) union(){ //nut sockets
|
||||
cube([nhl,wr/sqrt(3),wr],center=true);
|
||||
rotate([120,0,0]) cube([nhl,wr/sqrt(3),wr],center=true);
|
||||
rotate([240,0,0]) cube([nhl,wr/sqrt(3),wr],center=true);
|
||||
}
|
||||
translate([-thick,-thick,-height/2]) cylinder(r=thick,h=height*2); //corner fillet
|
||||
translate([thick/2-lfw,thick/2,-height/2]) rotate([0,0,180]) difference(){ //left round
|
||||
cube([thick,thick,height*2]);
|
||||
cylinder(d=thick,h=height*2);
|
||||
}
|
||||
translate([slot+thick*3/2,-thick/2-metal,-height/2]) rotate([0,0,-90]) difference(){ //right round
|
||||
cube([thick,thick,height*2]);
|
||||
cylinder(d=thick,h=height*2);
|
||||
}
|
||||
}
|
||||
|
||||
<figure>
|
||||
<embed src="Fdsh-v5.stl" title="File:Fdsh-v5.stl" />
|
||||
<figcaption><a href="File:Fdsh-v5.stl">File:Fdsh-v5.stl</a></figcaption>
|
||||
</figure>
|
||||
|
||||
[Category:CheapChineseLaser](Category:CheapChineseLaser "wikilink")
|
||||
Executable
+105
@@ -0,0 +1,105 @@
|
||||
[Byzantium Project](http://byzantium.virtadpt.net/byzantium.pubkey)
|
||||
public PGP key.
|
||||
|
||||
<table>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th><p>Version</p></th>
|
||||
<th><p>Codename</p></th>
|
||||
<th><p>Released</p></th>
|
||||
<th><p>Fitness*</p></th>
|
||||
<th><p>Torrent</p></th>
|
||||
<th><p>Direct DL</p></th>
|
||||
<th><p>PGPSign</p></th>
|
||||
<th><p>Comments</p></th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td><p>0.1a</p></td>
|
||||
<td><p>Scarab</p></td>
|
||||
<td><p>2012/01/11</p></td>
|
||||
<td><p>0</p></td>
|
||||
<td><ul>
|
||||
<li><a
|
||||
href="http://linuxtracker.org/download.php?id=fcc7607270ba48897ff865ed5361013554a659eb&f=Byzantium%20Linux%20v0.1a.torrent">Linux
|
||||
Tracker</a></li>
|
||||
<li><a href="https://thepiratebay.se/torrent/7074687">The Pirate
|
||||
Bay</a></li>
|
||||
</ul></td>
|
||||
<td><ul>
|
||||
<li><a href="http://linuxfreedom.com/byzantium">Linux Freedom</a></li>
|
||||
<li><a
|
||||
href="http://byzantium.virtadpt.net/v0.1a/">byzantium.virtadpt.net</a></li>
|
||||
<li><a
|
||||
href="https://s3.amazonaws.com/byzantium/byzantium-curent.iso">haxwithaxe's
|
||||
S3</a></li>
|
||||
</ul></td>
|
||||
<td><ul>
|
||||
<li><a
|
||||
href="https://s3.amazonaws.com/byzantium/byzantium-current.iso.asc">haxwithaxe's
|
||||
S3</a></li>
|
||||
<li><a
|
||||
href="http://byzantium.virtadpt.net/v0.1a/byzantium-v0.1a.iso.asc">byzantium.virtadpt.net</a></li>
|
||||
</ul></td>
|
||||
<td><ul>
|
||||
<li>current version.</li>
|
||||
</ul>
|
||||
<p>*EXTREME ALPHA</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td></td>
|
||||
<td></td>
|
||||
<td></td>
|
||||
<td></td>
|
||||
<td></td>
|
||||
<td></td>
|
||||
<td></td>
|
||||
<td></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
\`\*Fitness is a score from 0 to 5 indicating the fitness of a release
|
||||
for use as an **Emergency** networking aid. Do not let this put you off
|
||||
downloading it to try it out or help us by finding and reporting bug and
|
||||
feature requests. In order to make it to a level 5 fitness we need as
|
||||
many people to use it as possible so we are more likely to find bugs
|
||||
before they end up causing trouble for people who expect our livedistro
|
||||
to work in an emergency.
|
||||
|
||||
- 0 = completely unfit (likely to do more harm than good in any
|
||||
emergency)
|
||||
- 1 = still mostly unfit (unless you are an active developer on the
|
||||
project you won't likely benefit from this in an emergency)
|
||||
- 2 = works well enough to provide basic connectivity with minimal
|
||||
configuration. (yeh! we're a little bit fit now! which is not to say
|
||||
we're fit enough to run a marathon, so don't expect to be able to do
|
||||
much without a regular internet connection or some sysadmin skills)
|
||||
- 3 = in addition to qualifying for level 2 fitness this has basic
|
||||
intermesh services like a built in chat server, microblog server and
|
||||
similar user oriented services ready to run with minimal
|
||||
configuration. (still needs a service to tell other mesh users and end
|
||||
users about the services on the mesh, aka our DNSless service
|
||||
distribution).
|
||||
- 4 = fully featured and works well enough to be used in friendly
|
||||
network conditions (you aren't in jeopardy of getting
|
||||
arrested/attacked for using it for things that are considered legal
|
||||
where you are using it)
|
||||
- 5 = fully featured and setup with best effort secure defaults and
|
||||
possibly other security features (this by no means should suggest that
|
||||
it is safe to use in an environment where there is a government or
|
||||
government like entity is actively trying to suppress network
|
||||
connectivity by means other than denial standard network connectivity)
|
||||
- 6 = if we find the magic sauce that can make it super hard to find
|
||||
users if you aren't a user and reasonably impossible to detect or
|
||||
decrypt traffic not sent to you, then you will see this magic number
|
||||
as the fitness score. Until then it is the metaphorical unicorn. It
|
||||
doesn't exist.
|
||||
|
||||
You may have noticed that the fitness list doesn't ever say it's safe to
|
||||
use in a hostile network. That's because it won't likely ever be safe to
|
||||
use in a hostile network. The best we can do is to set reasonably secure
|
||||
defaults and policies and try to educate users on internet hygiene so
|
||||
they don't let people rub malware in their face if they go someplace we
|
||||
can't protect them.
|
||||
Executable
+45
@@ -0,0 +1,45 @@
|
||||
<table>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th><p>Version</p></th>
|
||||
<th><p>Codename</p></th>
|
||||
<th><p>Released</p></th>
|
||||
<th><p>Torrent</p></th>
|
||||
<th><p>Direct DL</p></th>
|
||||
<th><p>PGPSign</p></th>
|
||||
<th><p>Comments</p></th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td><p>0.1a</p></td>
|
||||
<td><p>Scarab</p></td>
|
||||
<td><p>2012/01/11</p></td>
|
||||
<td><ul>
|
||||
<li><a
|
||||
href="http://wiki.hacdc.org/images/e/e6/Byzantium_Linux_v0.1a.torrent">local
|
||||
copy</a></li>
|
||||
<li><a
|
||||
href="http://linuxtracker.org/download.php?id=fcc7607270ba48897ff865ed5361013554a659eb&f=Byzantium%20Linux%20v0.1a.torrent">Linux
|
||||
Tracker</a></li>
|
||||
</ul></td>
|
||||
<td><p><a
|
||||
href="https://s3.amazonaws.com/byzantium/byzantium-curent.iso">S3</a></p></td>
|
||||
<td><p><a
|
||||
href="https://s3.amazonaws.com/byzantium/byzantium-current.iso.asc">S3</a></p></td>
|
||||
<td><ul>
|
||||
<li>current version.</li>
|
||||
</ul>
|
||||
<p>*EXTREME ALPHA</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td></td>
|
||||
<td></td>
|
||||
<td></td>
|
||||
<td></td>
|
||||
<td></td>
|
||||
<td></td>
|
||||
<td></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
Executable
+5
@@ -0,0 +1,5 @@
|
||||
## Desired Features
|
||||
|
||||
- RSS feeds
|
||||
- recent changes
|
||||
- [categories](http://www.mediawiki.org/wiki/Help:Categories)
|
||||
Executable
+42
@@ -0,0 +1,42 @@
|
||||
Here be the UNofficial duties of the Secretary.. well, in the eyes of
|
||||
the current (Jan '14) secretary..
|
||||
|
||||
The only guidance I (David Mc.) was given upon taking this position was
|
||||
to take notes at the meetings. Having been in this position for a while,
|
||||
I'm certain that was an inadequate description. So here's a list of
|
||||
things I think the Secretary should be responsible for..
|
||||
|
||||
- Primary, but not sole, 'handler' for incoming emails on info@hacdc.org
|
||||
|
||||
:\* Mostly this means either deleting things or forwarding them on to
|
||||
the Blabber list.. sometimes it means longer conversations, particularly
|
||||
with other groups around the world trying to start a hacker-space.
|
||||
|
||||
:\* Always be positive and promote openness, learning, and growth.
|
||||
|
||||
- Governance of the wiki
|
||||
|
||||
:\* Not necessarily watching the wiki software, but definitely taking
|
||||
lead on the wiki's flow and standards
|
||||
|
||||
- NEW: no one ever mentioned this, but I think it's a good idea for the
|
||||
Sec to keep the calendar updated with happenings not only from within
|
||||
HacDC, but from the general community
|
||||
|
||||
:\* ..actually I'm just starting this now (Jan '14), it never occurred
|
||||
to me before, but I think it'll help people engage.
|
||||
|
||||
- Yes, keep the minutes of the meetings.. b/c no one else will, and it
|
||||
sounds like we should.
|
||||
- While I have never had to say anything.. keep an eye on what
|
||||
conversations are in Members vs Blabber. Roughly, I default to
|
||||
Blabber, unless it's something that only members could act upon.
|
||||
- Never forget that the Board's primary mission is to keep out of the
|
||||
way.
|
||||
- Just in case ya' missed it, Board members are expected to participate
|
||||
in the monthly meetings. I'd say missing one out of the year is ok.
|
||||
- There's a bit of confusion regarding new members.. The Sec. is
|
||||
supposed to get their email and ID, but the Treasurer is the one that
|
||||
needs this info. This really hasn't been worked out.
|
||||
- Keep an eye on who is in the various groups, specifically Members and
|
||||
BOD. Remove those that have left.
|
||||
Executable
+15
@@ -0,0 +1,15 @@
|
||||
This is a guide. While it is part of the [:Category:Communications
|
||||
Policy](:Category:Communications_Policy "wikilink"), this is meant to
|
||||
act as more of a guideline for how we communicate. Everyone can improve
|
||||
their communication skills, which are vital not only to our work within
|
||||
HacDC, but in our careers and relationships as well.
|
||||
|
||||
## Within The Group
|
||||
|
||||
Show respect!
|
||||
|
||||
## With the Outside World
|
||||
|
||||
Show respect!
|
||||
|
||||
[Category:HacDC_Culture](Category:HacDC_Culture "wikilink")
|
||||
Executable
+35
@@ -0,0 +1,35 @@
|
||||
# Household Emergency Prep
|
||||
|
||||
## Indoors
|
||||
|
||||
- make ice blocks in freezer with cleaned used drink containers leaving
|
||||
room for the ice to expand when filling
|
||||
- DO NOT BURN STUFF INSIDE THE HOUSE unless you have a fireplace or the
|
||||
like that has ventilation.
|
||||
|
||||
### Cold Weather
|
||||
|
||||
- use rocks/bricks/concrete to transfer heat from a outdoors fire inside
|
||||
the house using cotton or wool clothe to wrap them after removing them
|
||||
from the fire so you don't burn yourself of stuff inside the house.
|
||||
|
||||
### Warm Weather
|
||||
|
||||
- water mist near doorways or around porches cools the air nearby.
|
||||
|
||||
### Hygiene
|
||||
|
||||
- traditional siphon flush toilets can be flushed by pouring water into
|
||||
the bowl until it flushes. using waste water and/or urine can help to
|
||||
prevent wasting potable water.
|
||||
|
||||
## Outdoors
|
||||
|
||||
- store dry wood in recycle bins and trashcans and secure the lids
|
||||
|
||||
### High Wind
|
||||
|
||||
- store or tie down items such as lawn furniture, tables, umbrellas,
|
||||
flowerpots, construction material, etc.
|
||||
|
||||
# After The Event
|
||||
Executable
+69
@@ -0,0 +1,69 @@
|
||||
**HacDC Event Survey**
|
||||
|
||||
|
||||
How did you find out about the Event?
|
||||
|
||||
- HacDC Web Site
|
||||
- HacDC Wiki
|
||||
- RSS Feed Site (if possible, provide URL or Name of Feed)
|
||||
________________
|
||||
- Word of mouth
|
||||
|
||||
<!-- -->
|
||||
|
||||
|
||||
What is your technical expertise in relation to the Event's content?
|
||||
|
||||
- I wrote the book or I am in the process of writing a book.
|
||||
- I am a technical expert and work with the content on a day to day
|
||||
basis
|
||||
- I have studied the content but only work with the content once every
|
||||
few months
|
||||
- I have heard of the content and browsed websites, but I do not work
|
||||
with the content.
|
||||
- I have no technical experience with the content.
|
||||
|
||||
Grade the Event A = Excellent, B = Good, C = Average, D = Lacking, F =
|
||||
Fail Circle the grade.
|
||||
|
||||
|
||||
Presentation of the content
|
||||
|
||||
- A
|
||||
- B (What can we improve:
|
||||
_______________________________________________
|
||||
)
|
||||
- C (What can we improve:
|
||||
_______________________________________________
|
||||
)
|
||||
- D (What can we improve:
|
||||
_______________________________________________
|
||||
)
|
||||
- F (What can we improve:
|
||||
_______________________________________________
|
||||
)
|
||||
|
||||
<!-- -->
|
||||
|
||||
|
||||
Quality and accuracy of information presented
|
||||
|
||||
- A
|
||||
- B (What can we improve:
|
||||
_______________________________________________
|
||||
)
|
||||
- C (What can we improve:
|
||||
_______________________________________________
|
||||
)
|
||||
- D (What can we improve:
|
||||
_______________________________________________
|
||||
)
|
||||
- F (What can we improve:
|
||||
_______________________________________________
|
||||
)
|
||||
|
||||
Additional Comments:
|
||||
____________________________________________________
|
||||
|
||||
[Category:Events](Category:Events "wikilink")
|
||||
[Category:Marketing](Category:Marketing "wikilink")
|
||||
Executable
+254
@@ -0,0 +1,254 @@
|
||||
**Not yet official HacDC policy until approved at a monthly meeting.**
|
||||
|
||||
# Donation Rules
|
||||
|
||||
Donations must be labeled with the names of donor(s) and member(s)
|
||||
accepting them. Donors and accepting members have authority to, and are
|
||||
expected to manage the donation consistent with the following:
|
||||
|
||||
- Refuse or dispose of any materials not meeting the "Relevant to HacDC
|
||||
Criteria".
|
||||
- Properly store and/or deploy the new resources.
|
||||
- Refuse or dispose of any new materials that cannot be stored properly
|
||||
on shelves, installed in equipment, or otherwise kept out of the way.
|
||||
HacDC work areas are not for storage.
|
||||
- Low-value items (eg. keyboards, low-end computers, etc) must be
|
||||
clearly labeled "free for all, take home, will be summarily disposed
|
||||
of in one week," to that effect.
|
||||
- Leased items at HacDC must be clearly labeled with lender's name by
|
||||
permanent pen, tape, etc.
|
||||
|
||||
New donations not handled in a manner consistent with the above should
|
||||
be **disposed of immediately**.
|
||||
|
||||
# Disposal Rules
|
||||
|
||||
- Expiration on the going-out pile is a point of no return. Retrieval
|
||||
from a dumpster and return to HacDC is explicitly forbidden.
|
||||
- The going-out pile is a process to members to throw-away or take
|
||||
resources permanently, not to borrow resources.
|
||||
- A majority vote at an official meeting is required to allow return of
|
||||
a disposed resource to HacDC.
|
||||
|
||||
Materials violating these rules should be **disposed of immediately**.
|
||||
|
||||
# Space Use Rules
|
||||
|
||||
## Everywhere
|
||||
|
||||
- Floor and work surfaces must be kept clean.
|
||||
|
||||
## Upstairs
|
||||
|
||||
- Front room will not be used for storage.
|
||||
- Storage in back room limited to shelves and lockers.
|
||||
- Arrangement of back room will reasonably permit secondary use as class
|
||||
room or meeting space.
|
||||
|
||||
## Unshared Member Storage
|
||||
|
||||
Limited to 3 cubic feet (3' \* 1'), must be clearly labeled with contact
|
||||
information, and must fit on a shelf.
|
||||
|
||||
## Basement
|
||||
|
||||
- Front room will reasonably permit usage of at least 3 wood/metal
|
||||
machining workstations and optical table.
|
||||
- Front room storage is limited to overhead shelves.
|
||||
- Back room arrangement must permit temporary storage for at least 3
|
||||
front-room workstations.
|
||||
|
||||
## Unshared Member Storage
|
||||
|
||||
Limited to 27 cubic feet (3' \* 3' \* 3'), must be clearly labeled with
|
||||
contact information, and must fit on a shelf.
|
||||
|
||||
HacDC BoD may change the rules or authorize corrective actions,
|
||||
including "Emergency Disposal".
|
||||
|
||||
# Relevant to HacDC Criteria
|
||||
|
||||
HacDC's goals include education, research, and engineering.
|
||||
|
||||
- Actively in use, or likely to be deployed in six months.
|
||||
- Worthwhile components likely to be salvaged in six months.
|
||||
- Rare, valuable, and useful, likely to be sorely missed. Repurchasing
|
||||
multiple items worth \>\$250 is a costly mistake.
|
||||
|
||||
<!-- -->
|
||||
|
||||
- Not already present in excessive quantities, see "Rotation".
|
||||
|
||||
<!-- -->
|
||||
|
||||
- Available to other HacDC members (not private). HacDC is for
|
||||
collaboration, individual member storage should be limited.
|
||||
- Labeled as loaned to HacDC. Lenders should always have a reasonable
|
||||
chance to repossess their items.
|
||||
|
||||
**The following consultants may be able to offer insights on specific
|
||||
items:**
|
||||
|
||||
Note: salvage experts can quickly identify advanced hardware and
|
||||
identify valuable components likely to be inside.
|
||||
|
||||
- mirage335 (Hardware and Salvage Expert)
|
||||
- Dan Barlow (Hardware and Salvage Expert)
|
||||
- Julia Longtin aka. juri (Hardware and Salvage Expert)
|
||||
|
||||
<!-- -->
|
||||
|
||||
- Lee Ciereszko (Radio Communications and CCTV Equipment Expert)
|
||||
|
||||
# Going out Pile
|
||||
|
||||
Designated going out pile is in the basement. Anything put on the right
|
||||
side of that pile has a lifetime of **two weeks**, at which time it may
|
||||
be disposed of. Anything on the left side has already expired, awaiting
|
||||
disposal, and may not return to HacDC without a majority vote at an
|
||||
official meeting.
|
||||
|
||||
When possible, it is preferred that:
|
||||
|
||||
- Going out pile photographed at the beginning of the week (Monday).
|
||||
- Photo and/or contents list published to a HacDC mailing list within a
|
||||
day (Tuesday).
|
||||
- Expired items moved to the expired side of the pile next week
|
||||
(Monday).
|
||||
|
||||
Items meeting the "Relevant to HacDC Criteria" should not be added to
|
||||
this pile except in dire need.
|
||||
|
||||
**Members are welcome to bid on unexpired items, return unexpired items
|
||||
to service or storage at HacDC, or take expired items.**
|
||||
|
||||
# Emergency Disposal
|
||||
|
||||
When at least half the HacDC floor space and work areas are unusable due
|
||||
to improper resource storage, the going-out pile expiration period may
|
||||
be reduced to **three days**, with no requirement to photo or publish
|
||||
the contents list.
|
||||
|
||||
Such emergencies must be declared by HacDC BoD on the HacDC members
|
||||
mailing list, with an expiration time, three days prior to a disposal.
|
||||
Emergency disposal procedures may not be in effect more than 60 days per
|
||||
year.
|
||||
|
||||
# Rotation
|
||||
|
||||
Not all valuable or useful items at HacDC are in mint condition. When
|
||||
better condition items of the same type become available, and agreed
|
||||
upon limits have been exceeded, **poorer condition items should be be
|
||||
sent to the going out pile immediately.**
|
||||
|
||||
Limits apply to non-in-use equipment (eg. not dedicated to CNC mill, not
|
||||
on the test cart, etc), and are set in the following table:
|
||||
|
||||
| Item | Limit | Comments |
|
||||
|:------------------------|-------|-------------------------------------------------------------------------------------------------------------------------------|
|
||||
| Laptops | 5 | ThinkPads, more CPUs/cores/threads, and identical models (for classes) preferred. |
|
||||
| Desktops | 3 | More CPUs/cores/threads and RAM preferred. |
|
||||
| WYSE Terminals | 50 | More RAM preferred. |
|
||||
| LCD Monitors | 5 | Higher resolution preferred, especially \>1080p. |
|
||||
| Keyboards/Mice | 3 | Ridiculously cheap, not worth keeping. |
|
||||
| CRT Monitors, TVs, etc. | 1 | Must fit on shelves. Longer (higher-voltage) is better. Useful mainly for elementary particle physics experiments. |
|
||||
| Full Size Oscilloscopes | 3 | Higher speed, measurement functions, ease of use, special purpose uses (ie. scope clock), and working order determines value. |
|
||||
| | | |
|
||||
|
||||
**Members are welcome to revise this table as necessary.**
|
||||
|
||||
# Disposal Methods
|
||||
|
||||
Unwanted donations, expired items on the going out pile, or items
|
||||
declared unwanted at an official meeting should be disposed of ASAP as
|
||||
follows:
|
||||
|
||||
## Salvage
|
||||
|
||||
Small, usable parts may be salvaged from bulky equipment for active
|
||||
HacDC projects, education, or crafts. The parts may be permitted to
|
||||
return to HacDC service or storage, unless declared otherwise by
|
||||
majority vote at an official meeting.
|
||||
|
||||
## Regifting
|
||||
|
||||
Another non-profit organization may be able to keep the undesired items
|
||||
out of the waste stream.
|
||||
|
||||
## Sale
|
||||
|
||||
Ham fests (amateur radio conventions) are an excellent opportunity to
|
||||
obtain cash for junk. Proceeds should go to HacDC.
|
||||
|
||||
## Take Home by Member
|
||||
|
||||
Members may take an undesired item home, so long as the purpose is not
|
||||
to sell the item{s) for personal gain.
|
||||
|
||||
## Dump
|
||||
|
||||
Anything efficient that does not inconvenience our host or other
|
||||
authorities is acceptable, including without limitation:
|
||||
|
||||
- Throw it in an empty dumpster we are authorized to use, within reason.
|
||||
- Take it to the dump.
|
||||
- E-waste and hazardous materials should be properly recycled or
|
||||
processed.
|
||||
|
||||
## Local Electronics Recycling Resources
|
||||
|
||||
The [DC Department of Public Works](http://www.dpw.dc.gov) offers a
|
||||
free, weekly electronics recycling drop-off service at the Benning Road
|
||||
Trash Transfer Station, [3200 Benning Road
|
||||
NE](http://maps.google.com/maps?f=q&hl=en&geocode=&q=3200+Benning+Road+NE,+Washington,+DC&sll=37.0625,-95.677068&sspn=29.992289,59.0625&ie=UTF8&ll=38.900385,-76.962662&spn=0.028723,0.090981&z=14&iwloc=addr),
|
||||
each Saturday from 8 am to 3 pm.
|
||||
|
||||
[From Tom
|
||||
Lee](http://www.hacdc.org/pipermail/blabber/2009-August/001563.html):
|
||||
|
||||
> The DC government will take electronic waste without an additional
|
||||
> fee, but you need to drop it off at the Ft. Totten Waste Transfer
|
||||
> Station, which is almost impossible to find, particularly since the
|
||||
> directions on their website refer to the use of a road that is
|
||||
> currently closed. [Here's a quick Google
|
||||
> Map](http://maps.google.com/maps/ms?ie=UTF&msa=0&msid=117070561667971774162.000470c9871f982a1fc2c)
|
||||
> that conveys three key things:
|
||||
>
|
||||
> 1. McCormick Road cannot be used -- at least, not the last time I
|
||||
> went there
|
||||
> 2. you should not cross Puerto Rico Ave from Taylor, but rather get
|
||||
> onto Brookland Ave going north immediately before it (I believe
|
||||
> you can use either ramp off of Taylor to do this, but am not sure)
|
||||
> 3. The employees at the station can be a little vague on where
|
||||
> electronics recycling occurs. Go to the end of the path on the map
|
||||
> (although I should emphasize that its final location, not the
|
||||
> specific way it gets there, is the important thing -- I can't
|
||||
> recall the exact geometry of the station, and would encourage you
|
||||
> not to drive your car into anything that looks like a giant
|
||||
> crushing machine, despite what my map may say)
|
||||
>
|
||||
> \[<http://dpw.dc.gov/dpw/cwp/view,A,1202,Q,517961,dpwNav>,\|34219\|.asp
|
||||
> Hours are listed here.\]
|
||||
|
||||
# Conflict Resolution
|
||||
|
||||
By majority vote, HacDC members may declare items unwanted at an
|
||||
official meeting. These items should then be disposed of immediately,
|
||||
and are not permitted to return without a similar vote taking place.
|
||||
|
||||
By majority vote, HacDC Board of Directors is authorized to identify
|
||||
cases of improper disposal, warn specific members that the disposal was
|
||||
improper, and if necessary, prohibit specific members involved from
|
||||
undertaking further disposal. Further, improper disposal by those
|
||||
members after this prohibition may be deemed as occurring without the
|
||||
permission of HacDC members. That may have legal implications.
|
||||
|
||||
Nothing in this policy establishes disciplinary measures to be
|
||||
automatically taken upon mistakes or abuse, nor is it to conflict with
|
||||
purchases, salvage, scrap disposal, or normal use of HacDC tools,
|
||||
materials, supplies, beverages, etc. However, it does set guidelines
|
||||
agreed upon by HacDC members, with the expectation that other members
|
||||
will make a good faith effort to abide them. The expectation is also set
|
||||
that members will make reasonable efforts to discourage theft by guests.
|
||||
|
||||
[Category:EverydayPolicy](Category:EverydayPolicy "wikilink")
|
||||
Executable
+21
@@ -0,0 +1,21 @@
|
||||
This is the exhaust nozzle to transition from the header on the back
|
||||
panel of the chassis to the 4 inch flexible metal exhaust duct which
|
||||
goes to the exhaust fan.
|
||||
|
||||
//James Sullivan //exhaust nozzle for laser cutter to connect to 4"
|
||||
exhaust hose //dimensions in millimeters //parametric version //4-20-17
|
||||
//OpenSCAD version 2015.03-1 \$fn=80; nid=60; //nozzle inner diameter
|
||||
nod=80; //nozzle outer diameter mod=100; //maximum outer diameter sh=30;
|
||||
//step height sw=5; //step width oah=50; //over-all height tlw=3; //top
|
||||
ledge width bcd=46.8\*2; //bolt circle diameter bhd=3.6; //bolt hole
|
||||
diameter fw=12; //foot width fh=15; //foot height fod=108; //foot
|
||||
outside dimension, from outside edge to outside edge
|
||||
fid=(nid+nod)/2;//foot inside dimension, from inside edge to inside edge
|
||||
difference(){ //nozzle rotate_extrude (angle=360,convexity=4)
|
||||
{polygon(points=\[\[nid/2,0\],\[nod/2,0\],\[mod/2,sh\],\[mod/2-sw,sh\],\[mod/2-sw,oah\],\[mod/2-sw-tlw,oah\|nid/2,0\],\[nod/2,0\],\[mod/2,sh\],\[mod/2-sw,sh\],\[mod/2-sw,oah\],\[mod/2-sw-tlw,oah\]\]);};
|
||||
//nozzle itself for (angle=\[0:90:270\]){ //screw access cuts
|
||||
rotate(\[0,0,angle\]) translate(\[bcd/2,0,-5\]) rotate(\[0,6,0\])
|
||||
cylinder(d=bhd\*3.5,h=oah+10); } } module foot(){ difference(){
|
||||
translate(\[fid/2,-fw/2,0\]) cube(\[(fod-fid)/2,fw,fh\]); //foot
|
||||
translate(\[bcd/2,0,-5\]) cylinder(d=bhd,h=25); //bolt hole } } for
|
||||
(angle=\[0:90:270\]){ rotate(\[0,0,angle\]) foot(); }
|
||||
Executable
+85
@@ -0,0 +1,85 @@
|
||||
David Whiteis has loaned the **CRS/Fisher F3 Robotic arm** to Dr. Nuno
|
||||
Martin's group at the University of Maryland.
|
||||
|
||||
HacDC members interested in working with the robot should get in touch
|
||||
with David.
|
||||
|
||||
<figure>
|
||||
<img src="f3-robot-drawing-edited.jpg"
|
||||
title="f3-robot-drawing-edited.jpg" width="200" />
|
||||
<figcaption>f3-robot-drawing-edited.jpg</figcaption>
|
||||
</figure>
|
||||
|
||||
**We are currently gathering ideas about what we might do with the
|
||||
robot. Here is part of what we have come up with so far, shown in groups
|
||||
and including sample videos where possible.**
|
||||
|
||||
We may use this wiki page to document what we have learned about the
|
||||
robot, what projects are proposed, planned or implemented, and more
|
||||
videos of the machine in action.
|
||||
|
||||
## Moving and stacking stuff:
|
||||
|
||||
Grabbing dominoes from a stack, setting them up to tumble over in a row:
|
||||
<http://www.youtube.com/watch?v=-UzOfwHeV5k>
|
||||
|
||||
## Videoing stuff:
|
||||
|
||||
Holding a video camera in the gripper, and filming while in motion:
|
||||
<http://www.youtube.com/watch?v=2GDsFChduiI> That second video gives a
|
||||
limited overview of the robot's ability as an advanced 3D video camera
|
||||
dolly. We know a lot more about what is possible now. You could make
|
||||
some amazing videos with that setup. Here are some of the lessons
|
||||
learned:
|
||||
|
||||
`- Videoing miniatures such as model train layouts is fun and gives great results.`
|
||||
`- Get in close, and don't pan too much. `
|
||||
`- Keep a single object as the center of focus, and change the camera location while keeping that focus.`
|
||||
`- Track moving objects making complex movements, like a model train following a track.`
|
||||
|
||||
The O scale train in the above video was good, but tracking a smaller
|
||||
train (HO or N scale) would be much better, since then the robot could
|
||||
track the train through multiple left and right turns, much like a
|
||||
real-world helicopter filming a train for a Hollywood movie.
|
||||
|
||||
David plans to reach out to model train enthusiasts to see if there is
|
||||
interest in collaborating on a movie that really shows off the
|
||||
technology.
|
||||
|
||||
David sent an email on 3-8-13 to 'marylandfilmmakersclub@gmail.com' to
|
||||
see if the film school students at
|
||||
<http://www.marylandfilmmakersclub.com/home.html> are interested in
|
||||
collaborating on a project.
|
||||
|
||||
You could do great stop-motion animation with the setup. Your camera
|
||||
could move slightly every time your parts/clay are moved, making for a
|
||||
much more dynamic and flowing movie than when the camera stays in a
|
||||
static position.
|
||||
|
||||
If you programmed the arm to move the camera through the air in a big,
|
||||
elaborate flowing path, and then had someone who was a hotshot at flying
|
||||
miniature RC helicopters fly a pattern that kept it in front of the
|
||||
lens, that would make an amazing video.
|
||||
|
||||
## 3D printing, or subtractive CNC machining:
|
||||
|
||||
We have talked about mounting a plastic extruder, Dremel router, or
|
||||
cutting laser on the tool post, but we have not done any of this yet.
|
||||
Will it be you that drives this project?
|
||||
|
||||
## More on Maker Tech Tuesdays:
|
||||
|
||||
For several months the F3 robot was at Chas Colburn's place, before it
|
||||
was loaned to the University of Maryland.
|
||||
|
||||
Maker Tech Tuesdays is a hackerspace provided by Chas Colburn at his
|
||||
place of business, 3DMetalParts, just south of the University of
|
||||
Maryland. The space is free to visit and is open every Tuesday.
|
||||
|
||||
Chas & Maker Tech Tuesday's Facebook page:
|
||||
<http://www.facebook.com/video/video.php?v=10150900147128842>
|
||||
|
||||
More info on Chas is here, search for 'Colburn':
|
||||
<http://wiki.hacdc.org/index.php/Suppliers>
|
||||
|
||||
[Category:Previous_Projects](Category:Previous_Projects "wikilink")
|
||||
Executable
+61
@@ -0,0 +1,61 @@
|
||||
### Direct Installation (Ubuntu version)
|
||||
|
||||
--- Gtkwave ---
|
||||
|
||||
gtkwave is good in the Universe repository. If you've already got that
|
||||
linked in your /etc/apt/sources.list file, then installation is as
|
||||
simple as:
|
||||
|
||||
` sudo apt-get install gtkwave`
|
||||
|
||||
--- Compiling icarus verilog ---
|
||||
|
||||
Icarus verilog, on the other hand, is buggy in the Jaunty repository. So
|
||||
you'll want to compile it by hand.
|
||||
|
||||
- Fetch the .tar.gz file:
|
||||
|
||||
` wget `[`ftp://ftp.icarus.com/pub/eda/verilog/snapshots/verilog-20090923.tar.gz`](ftp://ftp.icarus.com/pub/eda/verilog/snapshots/verilog-20090923.tar.gz)
|
||||
` tar xvzf verilog-20090923.tar.gz`
|
||||
` cd verilog-20090923`
|
||||
|
||||
- Make sure you have the necessary compile tools:
|
||||
|
||||
` sudo apt-get install build-essential flex bison g++`
|
||||
|
||||
- Compile and install:
|
||||
|
||||
` ./configure `
|
||||
` make`
|
||||
` sudo make install `
|
||||
|
||||
- Go get a cup of tea after you type "make", because compiling takes a
|
||||
while. But when you get back, you should be good to go. Copy William's
|
||||
makefile into your code directory and get to work. Now you have your
|
||||
usual development tools at your fingertips. (Emacs and Gedit have
|
||||
sweet colorization modes for verilog.)
|
||||
|
||||
### Direct Installation (Mac OSX Version)
|
||||
|
||||
Spartan instructions follow...
|
||||
|
||||
- Install XCode tools from developer.apple.com
|
||||
- Install macports from macports.org. I don't know how macports plays
|
||||
with fink, so be wary if your using fink.
|
||||
- Install Icarus verilog with macports
|
||||
|
||||
<!-- -->
|
||||
|
||||
sudo port install iverilog
|
||||
|
||||
- Install GTKWave with macports. This will actually take a while on a
|
||||
fresh install of macports, so go and watch a tv show.
|
||||
|
||||
<!-- -->
|
||||
|
||||
sudo port install gtkwave
|
||||
|
||||
- You can now launch iverilog, vvp and gtkwave from the command line,
|
||||
and use the makefile provided with the workshop.
|
||||
|
||||
[Category:FPGAWorkshop](Category:FPGAWorkshop "wikilink")
|
||||
Executable
+83
@@ -0,0 +1,83 @@
|
||||
# Assumptions
|
||||
|
||||
- There is at least one mesh node.
|
||||
- Meshes are not built through collusion, i.e., each person setting up a
|
||||
node does not do so knowing that others are as well.
|
||||
- Mesh nodes are able to broadcast the existence of services they run
|
||||
("I run a microblog!")
|
||||
- Services can be activated on a node (implying that their presence will
|
||||
be announced) or deactivated (implying that their presence will not be
|
||||
announced)
|
||||
- Mesh nodes continually listen for announcements of services from
|
||||
neighboring mesh nodeds
|
||||
- Mesh nodes maintain directories of services running on neighboring
|
||||
mesh nodes
|
||||
- ...except when a service is designed to automatically federate with
|
||||
others of a like type (i.e., announcements of content from one will
|
||||
automatically be incorporated into cached announcements on the node)
|
||||
- Clients neither broadcast nor listen for service announcements
|
||||
- Smartphones
|
||||
- MP3 players
|
||||
- Computers not running Byzantium
|
||||
|
||||
# Existing protocols
|
||||
|
||||
- Avahi/ZeroConf/mDNS
|
||||
- Included in Porteus Linux
|
||||
- Host can publish running services
|
||||
- Host can be informed of services running on other hosts
|
||||
- User does not have to specifically configure any of this
|
||||
- Host admins may have to configure this
|
||||
- Bindings for multiple languages are available
|
||||
- Protocol in a nutshell:
|
||||
- Ad-hoc DHS over IP multicast (224.0.0.251, port 5353/UDP)
|
||||
- Each node has a resource record for each service
|
||||
- SRV
|
||||
- TXT
|
||||
- PTR
|
||||
- Types documented in /usr/share/avahi/service-types on
|
||||
Windbringer. File is part of Avahi on all systems.
|
||||
- HAS NOTHING TO DO WITH dnsmasq!
|
||||
- Resolution is done by the host running an Avahi implementation -
|
||||
broadcast a resolution request to the multicast domain and listen
|
||||
for a response
|
||||
- Node needs to have its hostname set (machinename.local)
|
||||
- Ignores point-to-point links by default. Add
|
||||
"allow-point-to-point=yes" in avahi-daemon.conf
|
||||
- Do mesh interfaces have the POINTTOPOINT flag?
|
||||
- wide-area functionality seems relevant to a mesh.
|
||||
- deny-interfaces=eth0 in avahi-daemon.conf may be necessary to
|
||||
prevent mDNS traffic from going over gateways.
|
||||
- avahi-daemon implements service announcement and listening, and
|
||||
interfaces with Avahi-enabled client apps.
|
||||
- avahi-dnsconfd connects to avahi-daemon and keeps track of unicast
|
||||
DNSes detected.
|
||||
- Read manage for avahi-daemon.conf!
|
||||
- Will need an /etc/avahi/services/foo.service XML file for each
|
||||
service offered by a node.
|
||||
- Manpage avahi.service(5) documents all required XML tags.
|
||||
- Each mesh node will have a list of all mesh nodes it's heard from in
|
||||
recent memory. This can be used to build the directory of
|
||||
neighboring services.
|
||||
|
||||
<!-- -->
|
||||
|
||||
- XMPP service discovery
|
||||
- Message oriented, based on XML
|
||||
- Jabber's protocol.
|
||||
- [XEP-0030](http://xmpp.org/extensions/xep-0030.html)
|
||||
- Used for discovering other XMPP entities/services implemented by
|
||||
XMPP servers.
|
||||
- Could be used for discovering and federating apps running on other
|
||||
nodes (i.e., distributed microblog).
|
||||
|
||||
# Notes
|
||||
|
||||
- KDE comes with something called Personal File Server, which allows
|
||||
arbitrary directories to be made available over HTTP(S?). It's
|
||||
Avahi-enabled. KDE is packagedwith Porteus. There's our file dump.
|
||||
- avahi-bookmarks allows the user to access HTTP resources with a web
|
||||
browser.
|
||||
- nss-mdns should be enabled in /etc/nssswitch.conf.
|
||||
|
||||
[Category:Byzantium](Category:Byzantium "wikilink")
|
||||
Executable
+658
@@ -0,0 +1,658 @@
|
||||
Trying to piece together whatever limits would apply to various projects
|
||||
involving small aircraft-like platforms.
|
||||
|
||||
Since the powers that be have made actually finding the rules that would
|
||||
apply to, well, any specific case really, very difficult.. don't take
|
||||
what's listed here as accurate, current, or complete.
|
||||
|
||||
## Jargon
|
||||
|
||||
Moored vs tethered
|
||||
tethered seems to be when you have a single line holding a balloon in
|
||||
place to temporarily hold it prior to release
|
||||
|
||||
moored seems more of an end result, holding the baloon in horizontal
|
||||
position in addition to vertical
|
||||
|
||||
Shielded
|
||||
Operating a moored balloon near, but lower than, a structure.
|
||||
|
||||
NOTAM
|
||||
Notice to Airmen, notices from FAA about changes, hazards along flight
|
||||
paths.
|
||||
|
||||
Oddly, I have not found anywhere that says these are legally binding,
|
||||
they do not seem to be actual regulations, just friendly reminders of
|
||||
regulations or restrictions.
|
||||
|
||||
TFR
|
||||
Temporary Flight Restriction, FAA enforced restrictions.. "temporary" is
|
||||
sometimes a misnomer
|
||||
|
||||
ADIZ
|
||||
Air Defense Identification Zone, most of North America, planes need to
|
||||
be in radio contact, etc.
|
||||
|
||||
SFRA
|
||||
Special Flight Rules Area, an area with a whole new bag of regulations,
|
||||
DC for one.
|
||||
|
||||
## Federal Regulations
|
||||
|
||||
Within the "Code of Federal Regulations" parts relating to airspace fall
|
||||
under "Title 14", FAA regulations.
|
||||
|
||||
- <http://www.ecfr.gov/cgi-bin/retrieveECFR?gp=1&SID=ddd67bb738ed6d267afd420fd9dfd893&ty=HTML&h=L&n=14y2.0.1.3.15&r=PART>
|
||||
|
||||
..this link probably won't work, but you can perform a search there
|
||||
|
||||
### Summary of Part 101 bits that apply to kites and moored balloons
|
||||
|
||||
- These rules apply to:
|
||||
|
||||
moored balloons with either a diameter \> 6 feet, or gas capacity of
|
||||
\> 115 cubic feet
|
||||
|
||||
kites \> 5 pounds
|
||||
- Operation:
|
||||
|
||||
can't create a hazard to people or property
|
||||
|
||||
cannot allow objects to drop from platfrom IF it creates a hazard
|
||||
- Operation airspace (in non-restricted area)
|
||||
|
||||
500 feet below cloud base
|
||||
|
||||
\< 500 feet AGL
|
||||
|
||||
if visibility \< 3 miles
|
||||
|
||||
must be \> 5 miles from any airport
|
||||
|
||||
|
||||
..except if below top of any structure within 250 feet (known as
|
||||
"sheilded" operation)
|
||||
|
||||
IF operating "unshielded", must notify nearest ATC if \> 150 feet AGL
|
||||
- (In all areas) Moored balloon must have automatic rapid deflation
|
||||
device
|
||||
- Time of operation
|
||||
|
||||
if at night, it's gotta be lit up, including the mooring lines
|
||||
|
||||
if in day, mooring lines need pennants every 50 feet starting at 150
|
||||
feet AGL
|
||||
|
||||
#### Meaning...
|
||||
|
||||
Keep it under 6 feet in diameter and \< 115 cubic feet and under 5
|
||||
pounds.
|
||||
|
||||
|
||||
( Near sea level He at STP gives roughly 1 oz / ft3, so 115 ft3 -\> 7
|
||||
pounds )
|
||||
|
||||
"Part 101" covers balloons, kites, and amateur rockets.
|
||||
|
||||
e-CFR Data is current as of August 7, 2013
|
||||
return arrow Return to Search Results
|
||||
|
||||
Browse Previous | Browse Next
|
||||
|
||||
Title 14: Aeronautics and Space
|
||||
PART 101???MOORED BALLOONS, KITES, AMATEUR ROCKETS AND UNMANNED FREE BALLOONS
|
||||
Contents
|
||||
|
||||
Subpart A???General
|
||||
?? 101.1 Applicability.
|
||||
?? 101.3 Waivers.
|
||||
?? 101.5 Operations in prohibited or restricted areas.
|
||||
?? 101.7 Hazardous operations.
|
||||
|
||||
Subpart B???Moored Balloons and Kites
|
||||
?? 101.11 Applicability.
|
||||
?? 101.13 Operating limitations.
|
||||
?? 101.15 Notice requirements.
|
||||
?? 101.17 Lighting and marking requirements.
|
||||
?? 101.19 Rapid deflation device.
|
||||
|
||||
Subpart C??? Amateur Rockets
|
||||
?? 101.21 Applicability.
|
||||
?? 101.22 Definitions.
|
||||
?? 101.23 General operating limitations.
|
||||
?? 101.25 Operating limitations for Class 2-High Power Rockets and Class 3-Advanced High Power Rockets.
|
||||
?? 101.27 ATC notification for all launches.
|
||||
?? 101.29 Information requirements.
|
||||
|
||||
Subpart D???Unmanned Free Balloons
|
||||
?? 101.31 Applicability.
|
||||
?? 101.33 Operating limitations.
|
||||
?? 101.35 Equipment and marking requirements.
|
||||
?? 101.37 Notice requirements.
|
||||
?? 101.39 Balloon position reports.
|
||||
|
||||
Authority: 49 U.S.C. 106(g), 40103, 40113-40114, 45302, 44502, 44514, 44701-44702, 44721, 46308.
|
||||
|
||||
return arrow Back to Top
|
||||
Subpart A???General
|
||||
|
||||
return arrow Back to Top
|
||||
?? 101.1 Applicability.
|
||||
|
||||
(a) This part prescribes rules governing the operation in the United States, of the following:
|
||||
|
||||
(1) Except as provided for in ?? 101.7, any balloon that is moored to the surface of the earth or an object thereon and that has a diameter of more than 6 feet or a gas capacity of more than 115 cubic feet.
|
||||
|
||||
(2) Except as provided for in ?? 101.7, any kite that weighs more than 5 pounds and is intended to be flown at the end of a rope or cable.
|
||||
|
||||
(3) Any amateur rocket except aerial firework displays.
|
||||
|
||||
(4) Except as provided for in ?? 101.7, any unmanned free balloon that???
|
||||
|
||||
(i) Carries a payload package that weighs more than four pounds and has a weight/size ratio of more than three ounces per square inch on any surface of the package, determined by dividing the total weight in ounces of the payload package by the area in square inches of its smallest surface;
|
||||
|
||||
(ii) Carries a payload package that weighs more than six pounds;
|
||||
|
||||
(iii) Carries a payload, of two or more packages, that weighs more than 12 pounds; or
|
||||
|
||||
(iv) Uses a rope or other device for suspension of the payload that requires an impact force of more than 50 pounds to separate the suspended payload from the balloon.
|
||||
|
||||
(b) For the purposes of this part, a gyroglider attached to a vehicle on the surface of the earth is considered to be a kite.
|
||||
|
||||
[Doc. No. 1580, 28 FR 6721, June 29, 1963, as amended by Amdt. 101-1, 29 FR 46, Jan. 3, 1964; Amdt. 101-3, 35 FR 8213, May 26, 1970; Amdt. 101-8, 73 FR 73781, Dec. 4, 2008; 74 FR 38092, July 31, 2009]
|
||||
|
||||
return arrow Back to Top
|
||||
?? 101.3 Waivers.
|
||||
|
||||
No person may conduct operations that require a deviation from this part except under a certificate of waiver issued by the Administrator.
|
||||
|
||||
[Doc. No. 1580, 28 FR 6721, June 29, 1963]
|
||||
|
||||
return arrow Back to Top
|
||||
?? 101.5 Operations in prohibited or restricted areas.
|
||||
|
||||
No person may operate a moored balloon, kite, amateur rocket, or unmanned free balloon in a prohibited or restricted area unless he has permission from the using or controlling agency, as appropriate.
|
||||
|
||||
[Doc. No. 1457, 29 FR 46, Jan. 3, 1964, as amended at 74 FR 38092, July 31, 2009]
|
||||
|
||||
return arrow Back to Top
|
||||
?? 101.7 Hazardous operations.
|
||||
|
||||
(a) No person may operate any moored balloon, kite, amateur rocket, or unmanned free balloon in a manner that creates a hazard to other persons, or their property.
|
||||
|
||||
(b) No person operating any moored balloon, kite, amateur rocket, or unmanned free balloon may allow an object to be dropped therefrom, if such action creates a hazard to other persons or their property.
|
||||
|
||||
(Sec. 6(c), Department of Transportation Act (49 U.S.C. 1655(c)))
|
||||
|
||||
[Doc. No. 12800, 39 FR 22252, June 21, 1974, as amended at 74 FR 38092, July 31, 2009]
|
||||
|
||||
return arrow Back to Top
|
||||
Subpart B???Moored Balloons and Kites
|
||||
|
||||
Source: Docket No. 1580, 28 FR 6722, June 29, 1963, unless otherwise noted.
|
||||
|
||||
return arrow Back to Top
|
||||
?? 101.11 Applicability.
|
||||
|
||||
This subpart applies to the operation of moored balloons and kites. However, a person operating a moored balloon or kite within a restricted area must comply only with ?? 101.19 and with additional limitations imposed by the using or controlling agency, as appropriate.
|
||||
|
||||
return arrow Back to Top
|
||||
?? 101.13 Operating limitations.
|
||||
|
||||
(a) Except as provided in paragraph (b) of this section, no person may operate a moored balloon or kite???
|
||||
|
||||
(1) Less than 500 feet from the base of any cloud;
|
||||
|
||||
(2) More than 500 feet above the surface of the earth;
|
||||
|
||||
(3) From an area where the ground visibility is less than three miles; or
|
||||
|
||||
(4) Within five miles of the boundary of any airport.
|
||||
|
||||
(b) Paragraph (a) of this section does not apply to the operation of a balloon or kite below the top of any structure and within 250 feet of it, if that shielded operation does not obscure any lighting on the structure.
|
||||
|
||||
return arrow Back to Top
|
||||
?? 101.15 Notice requirements.
|
||||
|
||||
No person may operate an unshielded moored balloon or kite more than 150 feet above the surface of the earth unless, at least 24 hours before beginning the operation, he gives the following information to the FAA ATC facility that is nearest to the place of intended operation:
|
||||
|
||||
(a) The names and addresses of the owners and operators.
|
||||
|
||||
(b) The size of the balloon or the size and weight of the kite.
|
||||
|
||||
(c) The location of the operation.
|
||||
|
||||
(d) The height above the surface of the earth at which the balloon or kite is to be operated.
|
||||
|
||||
(e) The date, time, and duration of the operation.
|
||||
|
||||
return arrow Back to Top
|
||||
?? 101.17 Lighting and marking requirements.
|
||||
|
||||
(a) No person may operate a moored balloon or kite, between sunset and sunrise unless the balloon or kite, and its mooring lines, are lighted so as to give a visual warning equal to that required for obstructions to air navigation in the FAA publication ???Obstruction Marking and Lighting???.
|
||||
|
||||
(b) No person may operate a moored balloon or kite between sunrise and sunset unless its mooring lines have colored pennants or streamers attached at not more than 50 foot intervals beginning at 150 feet above the surface of the earth and visible for at least one mile.
|
||||
|
||||
(Sec. 6(c), Department of Transportation Act (49 U.S.C. 1655(c)))
|
||||
|
||||
[Doc. No. 1580, 28 FR 6722, June 29, 1963, as amended by Amdt. 101-4, 39 FR 22252, June 21, 1974]
|
||||
|
||||
return arrow Back to Top
|
||||
?? 101.19 Rapid deflation device.
|
||||
|
||||
No person may operate a moored balloon unless it has a device that will automatically and rapidly deflate the balloon if it escapes from its moorings. If the device does not function properly, the operator shall immediately notify the nearest ATC facility of the location and time of the escape and the estimated flight path of the balloon.
|
||||
|
||||
return arrow Back to Top
|
||||
Subpart C??? Amateur Rockets
|
||||
|
||||
return arrow Back to Top
|
||||
?? 101.21 Applicability.
|
||||
|
||||
(a) This subpart applies to operating unmanned rockets. However, a person operating an unmanned rocket within a restricted area must comply with ?? 101.25(b)(7)(ii) and with any additional limitations imposed by the using or controlling agency.
|
||||
|
||||
(b) A person operating an unmanned rocket other than an amateur rocket as defined in ?? 1.1 of this chapter must comply with 14 CFR Chapter III.
|
||||
|
||||
[Doc. No. FAA-2007-27390, 73 FR 73781, Dec. 4, 2008]
|
||||
|
||||
return arrow Back to Top
|
||||
?? 101.22 Definitions.
|
||||
|
||||
The following definitions apply to this subpart:
|
||||
|
||||
(a) Class 1???Model Rocket means an amateur rocket that:
|
||||
|
||||
(1) Uses no more than 125 grams (4.4 ounces) of propellant;
|
||||
|
||||
(2) Uses a slow-burning propellant;
|
||||
|
||||
(3) Is made of paper, wood, or breakable plastic;
|
||||
|
||||
(4) Contains no substantial metal parts; and
|
||||
|
||||
(5) Weighs no more than 1,500 grams (53 ounces), including the propellant.
|
||||
|
||||
(b) Class 2???High-Power Rocket means an amateur rocket other than a model rocket that is propelled by a motor or motors having a combined total impulse of 40,960 Newton-seconds (9,208 pound-seconds) or less.
|
||||
|
||||
(c) Class 3???Advanced High-Power Rocket means an amateur rocket other than a model rocket or high-power rocket.
|
||||
|
||||
[Doc. No. FAA-2007-27390, 73 FR 73781, Dec. 4, 2008]
|
||||
|
||||
return arrow Back to Top
|
||||
?? 101.23 General operating limitations.
|
||||
|
||||
(a) You must operate an amateur rocket in such a manner that it:
|
||||
|
||||
(1) Is launched on a suborbital trajectory;
|
||||
|
||||
(2) When launched, must not cross into the territory of a foreign country unless an agreement is in place between the United States and the country of concern;
|
||||
|
||||
(3) Is unmanned; and
|
||||
|
||||
(4) Does not create a hazard to persons, property, or other aircraft.
|
||||
|
||||
(b) The FAA may specify additional operating limitations necessary to ensure that air traffic is not adversely affected, and public safety is not jeopardized.
|
||||
|
||||
[Doc. No. FAA-2007-27390, 73 FR 73781, Dec. 4, 2008]
|
||||
|
||||
return arrow Back to Top
|
||||
?? 101.25 Operating limitations for Class 2-High Power Rockets and Class 3-Advanced High Power Rockets.
|
||||
|
||||
When operating Class 2-High Power Rockets or Class 3-Advanced High Power Rockets, you must comply with the General Operating Limitations of ?? 101.23. In addition, you must not operate Class 2-High Power Rockets or Class 3-Advanced High Power Rockets???
|
||||
|
||||
(a) At any altitude where clouds or obscuring phenomena of more than five-tenths coverage prevails;
|
||||
|
||||
(b) At any altitude where the horizontal visibility is less than five miles;
|
||||
|
||||
(c) Into any cloud;
|
||||
|
||||
(d) Between sunset and sunrise without prior authorization from the FAA;
|
||||
|
||||
(e) Within 9.26 kilometers (5 nautical miles) of any airport boundary without prior authorization from the FAA;
|
||||
|
||||
(f) In controlled airspace without prior authorization from the FAA;
|
||||
|
||||
(g) Unless you observe the greater of the following separation distances from any person or property that is not associated with the operations:
|
||||
|
||||
(1) Not less than one-quarter the maximum expected altitude;
|
||||
|
||||
(2) 457 meters (1,500 ft.);
|
||||
|
||||
(h) Unless a person at least eighteen years old is present, is charged with ensuring the safety of the operation, and has final approval authority for initiating high-power rocket flight; and
|
||||
|
||||
(i) Unless reasonable precautions are provided to report and control a fire caused by rocket activities.
|
||||
|
||||
[74 FR 38092, July 31, 2009, as amended by Amdt. 101-8, 74 FR 47435, Sept. 16, 2009]
|
||||
|
||||
return arrow Back to Top
|
||||
?? 101.27 ATC notification for all launches.
|
||||
|
||||
No person may operate an unmanned rocket other than a Class 1???Model Rocket unless that person gives the following information to the FAA ATC facility nearest to the place of intended operation no less than 24 hours before and no more than three days before beginning the operation:
|
||||
|
||||
(a) The name and address of the operator; except when there are multiple participants at a single event, the name and address of the person so designated as the event launch coordinator, whose duties include coordination of the required launch data estimates and coordinating the launch event;
|
||||
|
||||
(b) Date and time the activity will begin;
|
||||
|
||||
(c) Radius of the affected area on the ground in nautical miles;
|
||||
|
||||
(d) Location of the center of the affected area in latitude and longitude coordinates;
|
||||
|
||||
(e) Highest affected altitude;
|
||||
|
||||
(f) Duration of the activity;
|
||||
|
||||
(g) Any other pertinent information requested by the ATC facility.
|
||||
|
||||
[Doc. No. FAA-2007-27390, 73 FR 73781, Dec. 4, 2008, as amended at Doc. No. FAA-2007-27390, 74 FR 31843, July 6, 2009]
|
||||
|
||||
return arrow Back to Top
|
||||
?? 101.29 Information requirements.
|
||||
|
||||
(a) Class 2???High-Power Rockets . When a Class 2???High-Power Rocket requires a certificate of waiver or authorization, the person planning the operation must provide the information below on each type of rocket to the FAA at least 45 days before the proposed operation. The FAA may request additional information if necessary to ensure the proposed operations can be safely conducted. The information shall include for each type of Class 2 rocket expected to be flown:
|
||||
|
||||
(1) Estimated number of rockets,
|
||||
|
||||
(2) Type of propulsion (liquid or solid), fuel(s) and oxidizer(s),
|
||||
|
||||
(3) Description of the launcher(s) planned to be used, including any airborne platform(s),
|
||||
|
||||
(4) Description of recovery system,
|
||||
|
||||
(5) Highest altitude, above ground level, expected to be reached,
|
||||
|
||||
(6) Launch site latitude, longitude, and elevation, and
|
||||
|
||||
(7) Any additional safety procedures that will be followed.
|
||||
|
||||
(b) Class 3???Advanced High-Power Rockets . When a Class 3???Advanced High-Power Rocket requires a certificate of waiver or authorization the person planning the operation must provide the information below for each type of rocket to the FAA at least 45 days before the proposed operation. The FAA may request additional information if necessary to ensure the proposed operations can be safely conducted. The information shall include for each type of Class 3 rocket expected to be flown:
|
||||
|
||||
(1) The information requirements of paragraph (a) of this section,
|
||||
|
||||
(2) Maximum possible range,
|
||||
|
||||
(3) The dynamic stability characteristics for the entire flight profile,
|
||||
|
||||
(4) A description of all major rocket systems, including structural, pneumatic, propellant, propulsion, ignition, electrical, avionics, recovery, wind-weighting, flight control, and tracking,
|
||||
|
||||
(5) A description of other support equipment necessary for a safe operation,
|
||||
|
||||
(6) The planned flight profile and sequence of events,
|
||||
|
||||
(7) All nominal impact areas, including those for any spent motors and other discarded hardware, within three standard deviations of the mean impact point,
|
||||
|
||||
(8) Launch commit criteria,
|
||||
|
||||
(9) Countdown procedures, and
|
||||
|
||||
(10) Mishap procedures.
|
||||
|
||||
[Doc. No. FAA-2007-27390, 73 FR 73781, Dec. 4, 2008, as amended at Doc. No. FAA-2007-27390, 74 FR 31843, July 6, 2009]
|
||||
|
||||
return arrow Back to Top
|
||||
Subpart D???Unmanned Free Balloons
|
||||
|
||||
Source: Docket No. 1457, 29 FR 47, Jan. 3, 1964, unless otherwise noted.
|
||||
|
||||
return arrow Back to Top
|
||||
?? 101.31 Applicability.
|
||||
|
||||
This subpart applies to the operation of unmanned free balloons. However, a person operating an unmanned free balloon within a restricted area must comply only with ?? 101.33 (d) and (e) and with any additional limitations that are imposed by the using or controlling agency, as appropriate.
|
||||
|
||||
return arrow Back to Top
|
||||
?? 101.33 Operating limitations.
|
||||
|
||||
No person may operate an unmanned free balloon???
|
||||
|
||||
(a) Unless otherwise authorized by ATC, below 2,000 feet above the surface within the lateral boundaries of the surface areas of Class B, Class C, Class D, or Class E airspace designated for an airport;
|
||||
|
||||
(b) At any altitude where there are clouds or obscuring phenomena of more than five-tenths coverage;
|
||||
|
||||
(c) At any altitude below 60,000 feet standard pressure altitude where the horizontal visibility is less than five miles;
|
||||
|
||||
(d) During the first 1,000 feet of ascent, over a congested area of a city, town, or settlement or an open-air assembly of persons not associated with the operation; or
|
||||
|
||||
(e) In such a manner that impact of the balloon, or part thereof including its payload, with the surface creates a hazard to persons or property not associated with the operation.
|
||||
|
||||
[Doc. No. 1457, 29 FR 47, Jan. 3, 1964, as amended by Amdt. 101-5, 56 FR 65662, Dec. 17, 1991]
|
||||
|
||||
return arrow Back to Top
|
||||
?? 101.35 Equipment and marking requirements.
|
||||
|
||||
(a) No person may operate an unmanned free balloon unless???
|
||||
|
||||
(1) It is equipped with at least two payload cut-down systems or devices that operate independently of each other;
|
||||
|
||||
(2) At least two methods, systems, devices, or combinations thereof, that function independently of each other, are employed for terminating the flight of the balloon envelope; and
|
||||
|
||||
(3) The balloon envelope is equipped with a radar reflective device(s) or material that will present an echo to surface radar operating in the 200 MHz to 2700 MHz frequency range.
|
||||
|
||||
The operator shall activate the appropriate devices required by paragraphs (a) (1) and (2) of this section when weather conditions are less than those prescribed for operation under this subpart, or if a malfunction or any other reason makes the further operation hazardous to other air traffic or to persons and property on the surface.
|
||||
|
||||
(b) No person may operate an unmanned free balloon below 60,000 feet standard pressure altitude between sunset and sunrise (as corrected to the altitude of operation) unless the balloon and its attachments and payload, whether or not they become separated during the operation, are equipped with lights that are visible for at least 5 miles and have a flash frequency of at least 40, and not more than 100, cycles per minute.
|
||||
|
||||
(c) No person may operate an unmanned free balloon that is equipped with a trailing antenna that requires an impact force of more than 50 pounds to break it at any point, unless the antenna has colored pennants or streamers that are attached at not more than 50 foot intervals and that are visible for at least one mile.
|
||||
|
||||
(d) No person may operate between sunrise and sunset an unmanned free balloon that is equipped with a suspension device (other than a highly conspicuously colored open parachute) more than 50 feet along, unless the suspension device is colored in alternate bands of high conspicuity colors or has colored pennants or streamers attached which are visible for at least one mile.
|
||||
|
||||
(Sec. 6(c), Department of Transportation Act (49 U.S.C. 1655(c)))
|
||||
|
||||
[Doc. No. 1457, 29 FR 47, Jan. 3, 1964, as amended by Amdt. 101-2, 32 FR 5254, Mar. 29, 1967; Amdt. 101-4, 39 FR 22252, June 21, 1974]
|
||||
|
||||
return arrow Back to Top
|
||||
?? 101.37 Notice requirements.
|
||||
|
||||
(a) Prelaunch notice: Except as provided in paragraph (b) of this section, no person may operate an unmanned free balloon unless, within 6 to 24 hours before beginning the operation, he gives the following information to the FAA ATC facility that is nearest to the place of intended operation:
|
||||
|
||||
(1) The balloon identification.
|
||||
|
||||
(2) The estimated date and time of launching, amended as necessary to remain within plus or minus 30 minutes.
|
||||
|
||||
(3) The location of the launching site.
|
||||
|
||||
(4) The cruising altitude.
|
||||
|
||||
(5) The forecast trajectory and estimated time to cruising altitude or 60,000 feet standard pressure altitude, whichever is lower.
|
||||
|
||||
(6) The length and diameter of the balloon, length of the suspension device, weight of the payload, and length of the trailing antenna.
|
||||
|
||||
(7) The duration of flight.
|
||||
|
||||
(8) The forecast time and location of impact with the surface of the earth.
|
||||
|
||||
(b) For solar or cosmic disturbance investigations involving a critical time element, the information in paragraph (a) of this section shall be given within 30 minutes to 24 hours before beginning the operation.
|
||||
|
||||
(c) Cancellation notice: If the operation is canceled, the person who intended to conduct the operation shall immediately notify the nearest FAA ATC facility.
|
||||
|
||||
(d) Launch notice: Each person operating an unmanned free balloon shall notify the nearest FAA or military ATC facility of the launch time immediately after the balloon is launched.
|
||||
|
||||
return arrow Back to Top
|
||||
?? 101.39 Balloon position reports.
|
||||
|
||||
(a) Each person operating an unmanned free balloon shall:
|
||||
|
||||
(1) Unless ATC requires otherwise, monitor the course of the balloon and record its position at least every two hours; and
|
||||
|
||||
(2) Forward any balloon position reports requested by ATC.
|
||||
|
||||
(b) One hour before beginning descent, each person operating an unmanned free balloon shall forward to the nearest FAA ATC facility the following information regarding the balloon:
|
||||
|
||||
(1) The current geographical position.
|
||||
|
||||
(2) The altitude.
|
||||
|
||||
(3) The forecast time of penetration of 60,000 feet standard pressure altitude (if applicable).
|
||||
|
||||
(4) The forecast trajectory for the balance of the flight.
|
||||
|
||||
(5) The forecast time and location of impact with the surface of the earth.
|
||||
|
||||
(c) If a balloon position report is not recorded for any two-hour period of flight, the person operating an unmanned free balloon shall immediately notify the nearest FAA ATC facility. The notice shall include the last recorded position and any revision of the forecast trajectory. The nearest FAA ATC facility shall be notified immediately when tracking of the balloon is re-established.
|
||||
|
||||
(d) Each person operating an unmanned free balloon shall notify the nearest FAA ATC facility when the operation is ended.
|
||||
|
||||
## DC Regulations
|
||||
|
||||
Under Title 14, part 93, "Special Air Traffic Rules"
|
||||
|
||||
- <http://www.ecfr.gov/cgi-bin/text-idx?c=ecfr&rgn=div5&view=text&node=14:2.0.1.3.11&idno=14#14:2.0.1.3.11.19>
|
||||
|
||||
This doesn't seem to apply to kites and tethered balloons at all. RC
|
||||
aircraft and 'drones' aren't mentioned either but the jist seems to be
|
||||
that if it's large enough to deliver a significantly harmful payload,
|
||||
consider it restricted.
|
||||
|
||||
Otherwise it defines the restricted space and talks a lot about radio
|
||||
communication requirements.
|
||||
|
||||
e-CFR Data is current as of August 7, 2013
|
||||
Title 14: Aeronautics and Space
|
||||
PART 93???SPECIAL AIR TRAFFIC RULES
|
||||
|
||||
Subpart V???Washington, DC Metropolitan Area Special Flight Rules Area
|
||||
|
||||
Source: Doc. No. FAA-2004-17005, 73 FR 76213, Dec. 16, 2008, unless otherwise noted.
|
||||
|
||||
return arrow Back to Top
|
||||
?? 93.331 Purpose and applicability of this subpart.
|
||||
|
||||
This subpart prescribes special air traffic rules for aircraft operating in the Washington, DC Metropolitan Area. Because identification and control of aircraft is required for reasons of national security, the areas described in this subpart constitute national defense airspace. The purpose of establishing this area is to facilitate the tracking of, and communication with, aircraft to deter persons who would use an aircraft as a weapon, or as a means of delivering weapons, to conduct an attack on persons, property, or buildings in the area. This subpart applies to pilots conducting any type of flight operations in the airspace designated as the Washington, DC Metropolitan Area Special Flight Rules Area (DC SFRA) (as defined in ?? 93.335), which includes the airspace designated as the Washington, DC Metropolitan Area Flight Restricted Zone (DC FRZ) (as defined in ?? 93.335).
|
||||
|
||||
return arrow Back to Top
|
||||
?? 93.333 Failure to comply with this subpart.
|
||||
|
||||
(a) Any violation . The FAA may take civil enforcement action against a pilot for violations, whether inadvertent or intentional, including imposition of civil penalties and suspension or revocation of airmen's certificates.
|
||||
|
||||
(b) Knowing or willful violations . The DC FRZ and DC SFRA were established for reasons of national security under the provisions of 49 U.S.C. 40103(b)(3). Areas established by the FAA under that authority constitute ???national defense airspace??? as that term is used in 49 U.S.C. 46307. In addition to being subject to the provisions of paragraph (a) of this section, persons who knowingly or willfully violate national defense airspace established pursuant to 49 U.S.C. 40103(b)(3) may be subject to criminal prosecution.
|
||||
|
||||
return arrow Back to Top
|
||||
?? 93.335 Definitions.
|
||||
|
||||
For purposes of this subpart???
|
||||
|
||||
DC FRZ flight plan is a flight plan filed for the sole purpose of complying with the requirements for VFR operations into, out of, and through the DC FRZ. This flight plan is separate and distinct from a standard VFR flight plan, and does not include search and rescue services.
|
||||
|
||||
DC SFRA flight plan is a flight plan filed for the sole purpose of complying with the requirements for VFR operations into, out of, and through the DC SFRA. This flight plan is separate and distinct from a standard VFR flight plan, and does not include search and rescue services.
|
||||
|
||||
Fringe airports are the following airports located near the outer boundary of the Washington, DC Metropolitan Area Special Flight Rules Area: Barnes (MD47), Flying M Farms (MD77), Mountain Road (MD43), Robinson (MD14), and Skyview (51VA).
|
||||
|
||||
Washington, DC Metropolitan Area Flight Restricted Zone (DC FRZ) is an area bounded by a line beginning at the Washington VOR/DME (DCA) 311?? radial at 15 nautical miles (NM) (Lat. 38??59???31??? N., Long. 077??18???30??? W.); then clockwise along the DCA 15 nautical mile arc to the DCA 002?? radial at 15 NM (Lat. 39??06???28??? N., Long 077??04???32??? W.); then southeast via a line drawn to the DCA 049?? radial at 14 NM (Lat. 39??02???18??? N., Long. 076??50???38??? W.); thence south via a line drawn to the DCA 064?? radial at 13 NM (Lat. 38??59???01??? N., Long. 076??48???32??? W.); thence clockwise along the 13 NM arc to the DCA 276?? radial at 13 NM (Lat.38??50???53??? N., Long 077??18???48??? W.); thence north to the point of beginning, excluding the airspace within a one nautical mile radius of the Freeway Airport, W00, Mitchellville, MD from the surface up to but not including flight level (FL) 180. The DC FRZ is within and part of the Washington, DC Metropolitan Area SFRA.
|
||||
|
||||
Washington, DC Metropolitan Area Special Flight Rules Area (DC SFRA) is an area of airspace over the surface of the earth where the ready identification, location, and control of aircraft is required in the interests of national security. Specifically, the DC SFRA is that airspace, from the surface to, but not including, FL 180, within a 30-mile radius of Lat. 38??51???34??? N., Long. 077??02???11??? W., or the DCA VOR/DME. The DC SFRA includes the DC FRZ.
|
||||
|
||||
[Doc. No. FAA-2004-17005, 73 FR 76213, Dec. 16, 2008; Amdt. 93-91, 73 FR 79314, Dec. 29, 2008]
|
||||
|
||||
return arrow Back to Top
|
||||
?? 93.337 Requirements for operating in the DC SFRA.
|
||||
|
||||
A pilot conducting any type of flight operation in the DC SFRA must comply with the restrictions listed in this subpart and all special instructions issued by the FAA in the interest of national security. Those special instructions may be issued in any manner the FAA considers appropriate, including a NOTAM. Additionally, a pilot must comply with all of the applicable requirements of this chapter.
|
||||
|
||||
return arrow Back to Top
|
||||
?? 93.339 Requirements for operating in the DC SFRA, including the DC FRZ.
|
||||
|
||||
(a) Except as provided in paragraphs (b) and (c) of this section and in ?? 93.345, or unless authorized by Air Traffic Control, no pilot may operate an aircraft, including an ultralight vehicle or any civil aircraft or public aircraft, in the DC SFRA, including the DC FRZ, unless???
|
||||
|
||||
(1) The aircraft is equipped with an operable two-way radio capable of communicating with Air Traffic Control on appropriate radio frequencies;
|
||||
|
||||
(2) Before operating an aircraft in the DC SFRA, including the DC FRZ, the pilot establishes two-way radio communications with the appropriate Air Traffic Control facility and maintains such communications while operating the aircraft in the DC SFRA, including the DC FRZ;
|
||||
|
||||
(3) The aircraft is equipped with an operating automatic altitude reporting transponder;
|
||||
|
||||
(4) Before operating an aircraft in the DC SFRA, including the DC FRZ, the pilot obtains and transmits a discrete transponder code from Air Traffic Control, and the aircraft's transponder continues to transmit the assigned code while operating within the DC SFRA;
|
||||
|
||||
(5) For VFR operations, the pilot must file and activate a DC FRZ or DC SFRA flight plan by obtaining a discrete transponder code. The flight plan is closed upon landing at an airport within the DC SFRA or when the aircraft exits the DC SFRA;
|
||||
|
||||
(6) Before operating the aircraft into, out of, or through the Washington, DC Tri-Area Class B Airspace Area, the pilot receives a specific Air Traffic Control clearance to operate in the Class B airspace area; and
|
||||
|
||||
(7) Before operating the aircraft into, out of, or through Class D airspace area that is within the DC SFRA, the pilot complies with ?? 91.129 of this chapter.
|
||||
|
||||
(b) Paragraph (a)(5) of this section does not apply to operators of Department of Defense aircraft, law enforcement operations, or lifeguard or air ambulance operations under an FAA/TSA airspace authorization, if the flight crew is in contact with Air Traffic Control and is transmitting an Air Traffic Control-assigned discrete transponder code.
|
||||
|
||||
(c) When operating an aircraft in the VFR traffic pattern at an airport within the DC SFRA (but not within the DC FRZ) that does not have an airport traffic control tower, a pilot must???
|
||||
|
||||
(1) File a DC SFRA flight plan for traffic pattern work;
|
||||
|
||||
(2) Communicate traffic pattern position via the published Common Traffic Advisory Frequency (CTAF);
|
||||
|
||||
(3) Monitor VHF frequency 121.5 or UHF frequency 243.0, if the aircraft is suitably equipped;
|
||||
|
||||
(4) Obtain and transmit the Air Traffic Control-assigned discrete transponder code; and
|
||||
|
||||
(5) When exiting the VFR traffic pattern, comply with paragraphs (a)(1) through (a)(7) of this section.
|
||||
|
||||
(d) When operating an aircraft in the VFR traffic pattern at an airport within the DC SFRA (but not within the DC FRZ) that has an operating airport traffic control tower, a pilot must???
|
||||
|
||||
(1) Before departure or before entering the traffic pattern, request to remain in the traffic pattern;
|
||||
|
||||
(2) Remain in two-way radio communications with the tower. If the aircraft is suitably equipped, the pilot must also monitor VHF frequency 121.5 or UHF frequency 243.0;
|
||||
|
||||
(3) Continuously operate the aircraft transponder on code 1234 unless Air Traffic Control assigns a different code; and
|
||||
|
||||
(4) Before exiting the traffic pattern, comply with paragraphs (a)(1) through (a)(7) of this section.
|
||||
|
||||
(e) Pilots must transmit the assigned transponder code. No pilot may use transponder code 1200 while in the DC SFRA.
|
||||
|
||||
return arrow Back to Top
|
||||
?? 93.341 Aircraft operations in the DC FRZ.
|
||||
|
||||
(a) Except as provided in paragraph (b) of this section, no pilot may conduct any flight operation under part 91, 101, 103, 105, 125, 133, 135, or 137 of this chapter in the DC FRZ, unless the specific flight is operating under an FAA/TSA authorization.
|
||||
|
||||
(b) Department of Defense (DOD) operations, law enforcement operations, and lifeguard or air ambulance operations under an FAA/TSA airspace authorization are excepted from the prohibition in paragraph (a) of this section if the pilot is in contact with Air Traffic Control and operates the aircraft transponder on an Air Traffic Control-assigned beacon code.
|
||||
|
||||
(c) The following aircraft operations are permitted in the DC FRZ:
|
||||
|
||||
(1) Aircraft operations under the DCA Access Standard Security Program (DASSP) (49 CFR part 1562) with a Transportation Security Administration (TSA) flight authorization.
|
||||
|
||||
(2) Law enforcement and other U.S. Federal aircraft operations with prior FAA approval.
|
||||
|
||||
(3) Foreign-operated military and state aircraft operations with a State Department-authorized diplomatic clearance, with State Department notification to the FAA and TSA.
|
||||
|
||||
(4) Federal, State, Federal DOD contract, local government agency aircraft operations and part 121, 129 or 135 air carrier flights with TSA-approved full aircraft operator standard security programs/procedures, if operating with DOD permission and notification to the FAA and the National Capital Regional Coordination Center (NCRCC). These flights may land and depart Andrews Air Force Base, MD, with prior permission, if required.
|
||||
|
||||
(5) Aircraft operations maintaining radio contact with Air Traffic Control and continuously transmitting an Air Traffic Control-assigned discrete transponder code. The pilot must monitor VHF frequency 121.5 or UHF frequency 243.0.
|
||||
|
||||
(d) Before departing from an airport within the DC FRZ, or before entering the DC FRZ, all aircraft, except DOD, law enforcement, and lifeguard or air ambulance aircraft operating under an FAA/TSA airspace authorization must file and activate an IFR or a DC FRZ or a DC SFRA flight plan and transmit a discrete transponder code assigned by an Air Traffic Control facility. Aircraft must transmit the discrete transponder code at all times while in the DC FRZ or DC SFRA.
|
||||
|
||||
return arrow Back to Top
|
||||
?? 93.343 Requirements for aircraft operations to or from College Park Airport, Potomac Airfield, or Washington Executive/Hyde Field Airport.
|
||||
|
||||
(a) A pilot may not operate an aircraft to or from College Park Airport, MD, Potomac Airfield, MD, or Washington Executive/Hyde Field Airport, MD unless???
|
||||
|
||||
(1) The aircraft and its crew and passengers comply with security rules issued by the TSA in 49 CFR part 1562, subpart A;
|
||||
|
||||
(2) Before departing, the pilot files an IFR or DC FRZ or DC SFRA flight plan with the Washington Hub Flight Service Station (FSS) for each departure and arrival from/to College Park, Potomac Airfield, and Washington Executive/Hyde Field airports, whether or not the aircraft makes an intermediate stop;
|
||||
|
||||
(3) When filing a flight plan with the Washington Hub FSS, the pilot identifies himself or herself by providing the assigned pilot identification code. The Washington Hub FSS will accept the flight plan only after verifying the code; and
|
||||
|
||||
(4) The pilot complies with the applicable IFR or VFR egress procedures in paragraph (b), (c) or (d) of this section.
|
||||
|
||||
(b) If using IFR procedures, a pilot must???
|
||||
|
||||
(1) Obtain an Air Traffic Control clearance from the Potomac TRACON; and
|
||||
|
||||
(2) Comply with Air Traffic Control departure instructions from Washington Executive/Hyde Field, Potomac Airport, or College Park Airport. The pilot must then proceed on the Air Traffic Control-assigned course and remain clear of the DC FRZ.
|
||||
|
||||
(c) If using VFR egress procedures, a pilot must???
|
||||
|
||||
(1) Depart as instructed by Air Traffic Control and expect a heading directly out of the DC FRZ until the pilot establishes two-way radio communication with Potomac Approach; and
|
||||
|
||||
(2) Operate as assigned by Air Traffic Control until clear of the DC FRZ, the DC SFRA, and the Class B or Class D airspace area.
|
||||
|
||||
(d) If using VFR ingress procedures, the aircraft must remain outside the DC SFRA until the pilot establishes communications with Air Traffic Control and receives authorization for the aircraft to enter the DC SFRA.
|
||||
|
||||
(e) VFR arrivals:
|
||||
|
||||
(1) If landing at College Park Airport a pilot may receive routing via the vicinity of Freeway Airport; or
|
||||
|
||||
(2) If landing at Washington Executive/Hyde Field or Potomac Airport, the pilot may receive routing via the vicinity of Maryland Airport or the Nottingham VORTAC.
|
||||
|
||||
return arrow Back to Top
|
||||
?? 93.345 VFR outbound procedures for fringe airports.
|
||||
|
||||
(a) A pilot may depart from a fringe airport as defined in ?? 93.335 without filing a flight plan or communicating with Air Traffic Control, unless requested, provided:
|
||||
|
||||
(1) The aircraft's transponder transmits code 1205;
|
||||
|
||||
(2) The pilot exits the DC SFRA by the most direct route before proceeding on course; and
|
||||
|
||||
(3) The pilot monitors VHF frequency 121.5 or UHF frequency 243.0.
|
||||
|
||||
(b) No pilot may operate an aircraft arriving at a fringe airport or transit the DC SFRA unless that pilot complies with the DC SFRA operating procedures in this subpart.
|
||||
Executable
+9
@@ -0,0 +1,9 @@
|
||||
HacDC Flyers
|
||||
|
||||
[:<File:flyer-1.pdf>](:File:flyer-1.pdf "wikilink") - full letter-size
|
||||
flyer with verb cloud and qr code
|
||||
|
||||
[:<File:flyer-2.pdf>](:File:flyer-2.pdf "wikilink") - half letter-size
|
||||
flyer with hacdc logo
|
||||
|
||||
[Category:Marketing](Category:Marketing "wikilink")
|
||||
Executable
+685
@@ -0,0 +1,685 @@
|
||||
Below is the proposed draft of the HacDC IRS [Form
|
||||
1023](http://ftp.irs.gov/charities/article/0,,id=130101,00.html). This
|
||||
is the form we need to fill out to become a 501(c)(3) status.
|
||||
|
||||
This wiki article will document proposed answers to the form, following
|
||||
on a Part and Line Item basis. You can follow along using [the complete
|
||||
1023 form](http://www.irs.gov/pub/irs-pdf/f1023.pdf), or check out the
|
||||
[1023 form instructions](http://www.irs.gov/pub/irs-pdf/i1023.pdf).
|
||||
|
||||
## Issues of note
|
||||
|
||||
- We should complete our Bylaws amendments before submitting this
|
||||
application. (See Part II, Line 5)
|
||||
- We should make sure all our DC filings are complete and correct (i.e.
|
||||
registered agent, registered office) before submitting.
|
||||
- We should prepare an Annual Report, as per our bylaws, describing the
|
||||
activities of HacDC and giving our financial picture from our Tax Year
|
||||
ended December 31, 2008. (See [Part
|
||||
IV](Form_1023_Draft#Part_IV:_Narrative_Description_of_Your_Activities "wikilink"))
|
||||
- Even though we have no paid staff or contractors, it may be a good
|
||||
idea to adopt compensation policies as described (See [Part
|
||||
V](Form_1023_Draft#Part_V_:_Compensation_and_Other_Financial_Arrangements_With_Your_Officers.2C_Directors.2C_Trustees.2C_Employees.2C_and_Independent_Contractors "wikilink"))
|
||||
- We should determine whether or not we will retain rights to
|
||||
intellectual property or other discoveries. (See Part VIII, Question
|
||||
10)
|
||||
- We should determine whether or not HacDC will make grants or
|
||||
distributions. (See Part VIII, Question 13)
|
||||
|
||||
## Sections to note
|
||||
|
||||
The "difficult" sections will be noted here. These are the ones that
|
||||
require real thought as opposed to simple plugging away of information
|
||||
|
||||
- [Part
|
||||
IV](Form_1023_Draft#Part_IV:_Narrative_Description_of_Your_Activities "wikilink")
|
||||
|
||||
## Part I : Identification of Applicant
|
||||
|
||||
1. Full name of organization (exactly as it appears in your organizing
|
||||
document): **HacDC**
|
||||
2. c/o Name (if applicable): (Not Applicable)
|
||||
3. Mailing address: **1525 Newton St NW, Washington DC 20010** *Note,
|
||||
there is no room or suite for HacDC*
|
||||
4. Employer Identification Number (EIN): **(tc should have this
|
||||
number)**
|
||||
5. Month the annual accounting period ends: **12** *We follow a
|
||||
calendar accounting year*
|
||||
6. Primary contact: *Contact information for Elliot or Tim, whoever
|
||||
wants to be the primary.*
|
||||
7. Are you represented...: **No** *This line is if attorneys or CPAs
|
||||
are filling the application and we want the IRS to communicate with
|
||||
them directly.*
|
||||
8. Was a person who is not one of your officers...: **No** *Presumably,
|
||||
nobody is getting paid to help us fill out this application*
|
||||
9. Organization???s website, e-mail: **<http://hacdc.org>
|
||||
info@hacdc.org**
|
||||
10. Certain organizations are not required to file: **No** *We will be
|
||||
required to fill out an 990*
|
||||
11. Date incorporated if a corporation...: **03/25/08** *Wow, we missed
|
||||
our anniversary party. This was the date we were officially
|
||||
incorporated in the District of Columbia. You can see our
|
||||
registration information
|
||||
[here](http://mblr.dc.gov/corp/lookup/status.asp?id=53073)*
|
||||
12. Were you formed under the laws of a foreign country?: **No**
|
||||
|
||||
## Part II : Organizational Structure
|
||||
|
||||
We are a Not for Profit corporation organized in the District of
|
||||
Columbia, organized specifically to become a 501(c)(3).
|
||||
|
||||
1. Are you a corporation?: **Yes** *Tim should have our original
|
||||
articles of incorporation*
|
||||
2. Are you a limited liability company: **No**
|
||||
3. Are you an unincorporated association?: **No**
|
||||
4. Are you a trust?: **No**
|
||||
5. Have you adopted bylaws?: **Yes** *Note: We should complete all
|
||||
proposed bylaws amendments before submitting this application.*
|
||||
|
||||
## Part III : Required Provisions in Your Organizing Document
|
||||
|
||||
We have all the required language in our [Articles of
|
||||
Incorporation](Articles_of_Incorporation "wikilink")
|
||||
|
||||
1. Section 501(c)(3) requires that your organizing document state your
|
||||
exempt purpose(s)...: **Yes [Third
|
||||
Article](Articles_of_Incorporation#4Third_Article "wikilink")**
|
||||
2. Section 501(c)(3) requires that upon dissolution of your
|
||||
organization, your remaining assets...: **Yes [Sixth
|
||||
Article](Articles_of_Incorporation##Sixth_Article_:_Management.2C_Affairs_and_Activities_and_Provision_for_Dissolution "wikilink")**
|
||||
|
||||
## Part IV: Narrative Description of Your Activities
|
||||
|
||||
This is the part of the application that will require the most
|
||||
discussion among our members. We may choose to attach our Annual Report,
|
||||
which we should prepare before submitting the application. In addition
|
||||
to a narrative of projects we're working on and the general nature of
|
||||
the space, what we're doing and what we plan to do, the Annual Report
|
||||
should be professional looking and serve as an attractive promotional
|
||||
device for HacDC. [Here's a good
|
||||
example](http://www.carnegie.org/pdf/CCNY-AR08-18.pdf) of an Annual
|
||||
Report from the Carnegie Foundation
|
||||
|
||||
### Instructions from the application
|
||||
|
||||
Using an attachment, describe your **past, present, and planned
|
||||
activities in a narrative**. If you believe that you have already
|
||||
provided some of this information in response to other parts of this
|
||||
application, you may summarize that information here and refer to the
|
||||
specific parts of the application for supporting details. You may also
|
||||
attach representative copies of newsletters, brochures, or similar
|
||||
documents for supporting details to this narrative. **Remember that if
|
||||
this application is approved, it will be open for public inspection.**
|
||||
Therefore, your narrative description of activities should be thorough
|
||||
and accurate. Refer to the instructions for information that must be
|
||||
included in your description.
|
||||
|
||||
### Instructions from the form instructions
|
||||
|
||||
For each past, present, or planned activity, include information that
|
||||
answers the following questions:
|
||||
|
||||
- What is the activity?
|
||||
- Who conducts the activity?
|
||||
- When is the activity conducted?
|
||||
- Where is the activity conducted?
|
||||
- How does the activity further your exempt purposes?
|
||||
- What percentage of your total time is dedicated to the activity?
|
||||
- How is the activity funded?
|
||||
- List any alternate names under which you operate
|
||||
|
||||
If you have a website, you may attach a paper copy of to support your
|
||||
narrative description of activities
|
||||
|
||||
### Sample Activity: Microcontroller Mondays
|
||||
|
||||
Note: This is by no means complete, this is just to give an example of a
|
||||
good description of the activity. The same information may be presented
|
||||
in a less structured/more narrative form, as long as the questions are
|
||||
answered.
|
||||
|
||||
- Microcontroller Mondays is a weekly gathering of those interested in
|
||||
the pursuit of microcontroller-driven devices, their designa nd
|
||||
theory. The event is open to the public, designed for all skill levels
|
||||
and serves as one of the organization's primary "entry points" for
|
||||
involvement.
|
||||
- The activity is conducted by volunteer members of HacDC
|
||||
- The activity is conducted most Monday nights
|
||||
- The activity is conducted at HacDC's laboratory space
|
||||
- The activity furthers the following exempt purposes
|
||||
- Charitable: The activity is free and open to the public. HacDC's
|
||||
equipment, meeting space and some consumables are made available to
|
||||
all participants. Other non-profit organizations and those pursuing
|
||||
charitable activities use the weekly meetup to learn more about
|
||||
microcontrollers and other electronic technology as well as network
|
||||
with those who have expertise and are willing to apply that
|
||||
expertise to relevant charitable work.
|
||||
- Educational: The activity's primary aim is information exchange and
|
||||
mentorship on the science of microcontroller design and theory.
|
||||
Experts and those well-versed in the technology share information
|
||||
with each other and mentor those with little to no experience with
|
||||
the technology. Often, a potential hobbyist will bring a project
|
||||
they cannot complete to the event to seek advice and mentorship in
|
||||
completing the project and learning techniques and theory to
|
||||
complete more advanced projects or design new ones.
|
||||
- Scientific: The activity's secondary aim is to engage with
|
||||
microcontroller and related technology, discover new applications of
|
||||
the technology and test the limits and potentials of existing
|
||||
technology and theory in the field.
|
||||
- Approximately 15% of our total volunteer and member hours are
|
||||
dedicated to this activity
|
||||
- The meeting space and utilities for the space are funded by members,
|
||||
the equipment is primarily donated or paid through membership dues and
|
||||
donations. Those participating in mentorship and research activities
|
||||
do so as volunteers.
|
||||
|
||||
## Part V : Compensation and Other Financial Arrangements With Your Officers, Directors, Trustees, Employees, and Independent Contractors
|
||||
|
||||
HacDC has no paid staff, officers, volunteers, etc. As such, this clause
|
||||
should present no issue to us, though we may want to adopt policies
|
||||
stating under what circumstances someone would be compensated (i.e. a
|
||||
teacher of a class, speaker, etc.)
|
||||
|
||||
This clause was expanded in the most recent revision of the application
|
||||
to ferret out organizations formed primarily for the enrichment of the
|
||||
participants. It's common for hobbyists in the field to form their own
|
||||
non-profit to fund their presumably exempt activities as a primary
|
||||
career.
|
||||
|
||||
**However, the officers will have to attach a list "showing their name,
|
||||
qualifications, average hours worked, and duties."**
|
||||
|
||||
Note: The officer titles are most likely going to change pending a
|
||||
Bylaws revision.
|
||||
|
||||
|
||||
1a.
|
||||
|
||||
Elliot Williams / Coordinator in Chief / 1525 Newton St NW, Washington
|
||||
DC, 20010 / -\$0-
|
||||
|
||||
(Other officers, etc.)
|
||||
|
||||
<!-- -->
|
||||
|
||||
|
||||
1b. **None**
|
||||
|
||||
1c. **None**
|
||||
|
||||
<!-- -->
|
||||
|
||||
|
||||
2a. Are any of your officers, directors, or trustees related to each
|
||||
other through family or business relationships? If ???Yes,??? identify
|
||||
the individuals and explain the relationship. **No**
|
||||
|
||||
2b. Do you have a business relationship with any of your officers,
|
||||
directors, or trustees other than through their position as an officer,
|
||||
director, or trustee? If ???Yes,??? identify the individuals and
|
||||
describe the business relationship with each of your officers,
|
||||
directors, or trustees. **No**
|
||||
|
||||
2c. Are any of your officers, directors, or trustees related to your
|
||||
highest compensated employees or highest compensated independent
|
||||
contractors listed on lines 1b or 1c through family or business
|
||||
relationships? If ???Yes,??? identify the individuals and explain the
|
||||
relationship. **No**
|
||||
|
||||
3a. For each of your officers, directors, trustees, highest compensated
|
||||
employees, and highest compensated independent contractors listed on
|
||||
lines 1a, 1b, or 1c, attach a list showing their name, qualifications,
|
||||
average hours worked, and duties. **Attached list of qualifications,
|
||||
etc.** *This is where the officers will have to list their duties,
|
||||
qualifications, etc.*
|
||||
|
||||
3b. Do any of your officers, directors, trustees, highest compensated
|
||||
employees, and highest compensated independent contractors listed on
|
||||
lines 1a, 1b, or 1c receive compensation from any other organizations,
|
||||
whether tax exempt or taxable, that are related to you through common
|
||||
control? **No** *This assumes that none of the officers work or have
|
||||
business or other outside interests with the same entities.*
|
||||
|
||||
4\. In establishing the compensation for your officers, directors,
|
||||
trustees, highest compensated employees, and highest compensated
|
||||
independent contractors listed on lines 1a, 1b, and 1c, the following
|
||||
practices are recommended, although they are not required to obtain
|
||||
exemption. Answer ???Yes??? to all the practices you use. *If HacDC
|
||||
decides to not compensate officers, directors, etc. or does not envision
|
||||
hiring employees in the forseeable future, we should answer that we
|
||||
don't need such policies as no compensation will be set or granted. If
|
||||
we believe we will hire employees or compensate officers, etc. we should
|
||||
consult with an attorney to draft these policies.*
|
||||
|
||||
## Part VI: Your Members and Other Individuals and Organizations That Receive Benefits From You
|
||||
|
||||
This is a very sticky part of the application. What HacDC does and how
|
||||
it relates to other organizations will need to be documented in
|
||||
narrative form in this part of the application.
|
||||
|
||||
What we've done and what we plan to do should be noted in this section
|
||||
and what avenues we choose to open or close for ourselves will need to
|
||||
be decided before we can fill this out. We should distinguish between
|
||||
ongoing activities (past/present) and what we plan to do ("planned
|
||||
activities"). We should structure our responses in terms of "programs",
|
||||
even though in practice, we don't make specific programmatic
|
||||
distinctions as such.
|
||||
|
||||
The IRS basically wants to make sure that the exempt services and
|
||||
related "benefits" we provide here are not for any particular group of
|
||||
individuals or are otherwise self-serving. HacDC is basically in the
|
||||
clear on this, but it is important to clearly document this as such.
|
||||
|
||||
|
||||
1a. In carrying out your exempt purposes, do you provide goods,
|
||||
services, or funds to individuals? **Yes. Our core program is providing
|
||||
a space for the creative exploration of technology. Members and other
|
||||
individuals use the space and incidental services provided. Our
|
||||
educational program, through more formalized classes, provide
|
||||
individuals with introductory knowledge in electronics, open source
|
||||
software and other technical pursuits. We also plan on providing
|
||||
services to the community, such as public wireless internet access.
|
||||
Informally, we serve as a hub for donated equipment which individuals
|
||||
may avail themselves of for their own benefit. However, we do not as a
|
||||
rule provide individualized goods or services to individuals. While we
|
||||
anticipate funding specific projects or pursuits, we do not provide
|
||||
funds to individuals.**
|
||||
|
||||
<!-- -->
|
||||
|
||||
|
||||
1b. In carrying out your exempt purposes, do you provide goods,
|
||||
services, or funds to organizations? **Yes. We currently provide a forum
|
||||
for other organizations to have meetings or host workshops. We are also
|
||||
working with our landlord to provide internet access to other
|
||||
organizations that rent space in our building.**
|
||||
|
||||
<!-- -->
|
||||
|
||||
|
||||
2\. Do any of your programs limit the provision of goods, services, or
|
||||
funds to a specific individual or group of specific individuals? **No**
|
||||
*Note, we should draft some kind of non-discrimination policy along
|
||||
these lines.*
|
||||
|
||||
<!-- -->
|
||||
|
||||
|
||||
3\. Do any individuals who receive goods, services, or funds through
|
||||
your programs have a family or business relationship with any officer,
|
||||
director, trustee, or with any of your highest compensated employees or
|
||||
highest compensated independent contractors listed in Part V, lines 1a,
|
||||
1b, and 1c? **No**
|
||||
|
||||
## Part VII: Your History
|
||||
|
||||
These are relatively simple and straightforward.
|
||||
|
||||
|
||||
1\. Are you a successor to another organization? **No** *HacDC did not
|
||||
take on another organization's assets or mission, it was formed entirely
|
||||
independently.*
|
||||
|
||||
<!-- -->
|
||||
|
||||
|
||||
2\. Are you submitting this application more than 27 months after the
|
||||
end of the month in which you were legally formed? **NO** *As long as we
|
||||
complete this application by May of 2010, we're OK.*
|
||||
|
||||
## Part VIII: Your Specific Activities
|
||||
|
||||
These are relatively straightforward questions that shouldn't pose too
|
||||
much difficulty. In answering specifically, we should attempt to keep
|
||||
our options open while bearing in mind that HacDC should not contact
|
||||
with outside organizations to accomplish any fund raising or other
|
||||
program goals, nor should it serve other groups as such.
|
||||
|
||||
One potential issue is raised regarding intellectual property in
|
||||
Question 10.
|
||||
|
||||
|
||||
1\. Do you support or oppose candidates in political campaigns in any
|
||||
way? **No** *501(c)(3)s are not allowed to specifically advocate or
|
||||
influence legislators or pending legislation, while they may, in a
|
||||
general way, provide information about political issues. Short of
|
||||
retaining counsel to guide such activities, it's best if HacDC itself
|
||||
remains politically neutral as an organization.*
|
||||
|
||||
<!-- -->
|
||||
|
||||
|
||||
2a. Do you attempt to influence legislation? **No**
|
||||
|
||||
2b. (N/A)
|
||||
|
||||
<!-- -->
|
||||
|
||||
|
||||
3a. Do you or will you operate bingo or gaming activities? **No** *We'd
|
||||
have to get really desperate to resort to Bingo, but it is a legitimate
|
||||
question for churches, native american groups, etc.*
|
||||
|
||||
3b./3c. (N/A)
|
||||
|
||||
<!-- -->
|
||||
|
||||
|
||||
4a. Do you or will you undertake fundraising? **Yes. Email
|
||||
solicitations, Personal Solicitations, Foundation Grant Solicitations,
|
||||
Accept Donations on Your Website, Receive Donations from Another
|
||||
Organization???s Website, Government Grant Solicitations**
|
||||
|
||||
Attach a description of each fundraising program:
|
||||
|
||||
**\* General Fundraising: We have pursued general fundraising to support
|
||||
the efforts of HacDC. Such fundraising has taken place through our
|
||||
website, at events in our space, external events we participate in and
|
||||
through various channels by our members' individual initiative.**
|
||||
|
||||
**\* Equipment Donations: Most of HacDC's equipment is donated and we
|
||||
plan on pursuing other equipment donations**
|
||||
|
||||
**\* Specific Fundraising: Members have expressed interested and plan on
|
||||
targeting fundraising efforts towards the acquisition of larger pieces
|
||||
of equipment or capital intensive projects.**
|
||||
|
||||
<!-- -->
|
||||
|
||||
|
||||
4b. Do you or will you have written or oral contracts with any
|
||||
individuals or organizations to raise funds for you? **No**
|
||||
|
||||
4c. Do you or will you engage in fundraising activities for other
|
||||
organizations? **No**
|
||||
|
||||
4d. List all states and local jurisdictions in which you conduct
|
||||
fundraising.
|
||||
|
||||
**\* Washington, District of Columbia: Fundraising for HacDC conducted
|
||||
by HacDC**
|
||||
|
||||
**\* Maryland: Fundraising for HacDC conducted by HacDC**
|
||||
|
||||
**\* Virginia: Fundraising for HacDC conducted by HacDC**
|
||||
|
||||
**\* Ohio: Fundraising for HacDC conducted by HacDC**
|
||||
|
||||
**\* Globally, Via the Internet: Fundraising for HacDC conducted by
|
||||
HacDC**
|
||||
|
||||
<!-- -->
|
||||
|
||||
|
||||
4e. Do you or will you maintain separate accounts for any contributor
|
||||
under which the contributor has the right to advise on the use or
|
||||
distribution of funds? **No** ''HacDC should not maintain what are
|
||||
called "Donor Advised Funds". While people may donate to a specific
|
||||
cause, i.e. a "Laser Cutter Fund" or other restricted fund, the IRS is
|
||||
asking about funds where donors have the right to specify where funds go
|
||||
after the donation is made.
|
||||
|
||||
<!-- -->
|
||||
|
||||
|
||||
5\. Are you affiliated with a governmental unit? **No** *HacDC was not
|
||||
created or controlled by a government agency.*
|
||||
|
||||
<!-- -->
|
||||
|
||||
|
||||
6\. Do you or will you engage in economic development? **No** *This is
|
||||
specifically asking if HacDC will take part in activities like a
|
||||
Business Improvement District, entities which are somewhat complicated
|
||||
and well outside the scope of what HacDC does.*
|
||||
|
||||
<!-- -->
|
||||
|
||||
|
||||
7a. Do or will persons other than your employees or volunteers develop
|
||||
your facilities? **No** *This is asking about the development of real
|
||||
property. HacDC does not own real property, nor does it have any
|
||||
concrete plans to do so at this time.*
|
||||
|
||||
7b. Do or will persons other than your employees or volunteers manage
|
||||
your activities or facilities? **No**
|
||||
|
||||
7c. *We should not have any relationships which need to be documented in
|
||||
this section*
|
||||
|
||||
<!-- -->
|
||||
|
||||
|
||||
8\. Do you or will you enter into joint ventures, including partnerships
|
||||
or limited liability companies treated as partnerships, in which you
|
||||
share profits and losses with partners other than section 501(c)(3)
|
||||
organizations? **No** *While obtaining something like the laser cutter
|
||||
might be advisable under this scenario, it's advisable to avoid such
|
||||
relationships. If this status changes, we merely need to inform the IRS
|
||||
as such as part of our regular 990 filing process.*
|
||||
|
||||
<!-- -->
|
||||
|
||||
|
||||
9a. Are you applying for exemption as a childcare organization under
|
||||
section 501(k)? **No** *We're not in any way qualified to nor would we
|
||||
gain much by applying under this section*
|
||||
|
||||
<!-- -->
|
||||
|
||||
|
||||
10\. Do you or will you publish, own, or have rights in music,
|
||||
literature, tapes, artworks, choreography, scientific discoveries, or
|
||||
other intellectual property? **No** *HacDC should not be in the business
|
||||
of owning intellectual property or managing property rights, especially
|
||||
as the space we operate in is one of open source style collaboration. We
|
||||
should also eschew this so our members and others are free to pursue
|
||||
their own discoveries within our space and determine, on an individual
|
||||
basis, how those discoveries are licensed.*
|
||||
|
||||
<!-- -->
|
||||
|
||||
|
||||
11\. Do you or will you accept contributions of: real property;
|
||||
conservation easements; closely held securities; intellectual property
|
||||
such as patents, trademarks, and copyrights; works of music or art;
|
||||
licenses; royalties; automobiles, boats, planes, or other vehicles; or
|
||||
collectibles of any type? **Yes**. *We should explain here that we would
|
||||
accept certain pieces of equipment or real property that have a specific
|
||||
application to our exempt purposes, i.e. a building for our activities,
|
||||
a vehicle for equipment moving, etc. The IRS is trying to determine
|
||||
whether or not we'll be engaging in vehicle donation programs or the
|
||||
like where such items are donated, then turned around and sold for cash
|
||||
by the organization.*
|
||||
|
||||
<!-- -->
|
||||
|
||||
|
||||
12\. Do you or will you operate in a foreign country or countries?
|
||||
**No** *As an organization, HacDC itself should not operate in foreign
|
||||
countries, though it may support other relief efforts.*
|
||||
|
||||
<!-- -->
|
||||
|
||||
|
||||
13a. Do you or will you make grants, loans, or other distributions to
|
||||
organization(s)? **No** *This is a potentially sticky issue. It's
|
||||
probably best for HacDC to stay out of the grant making business, at
|
||||
least for now, until HacDC can properly craft a role or mission for
|
||||
doing so. For now, it's best that HacDC projects remain in house.*
|
||||
|
||||
<!-- -->
|
||||
|
||||
|
||||
14a. Do you or will you make grants, loans, or other distributions to
|
||||
foreign organizations? **No** *Post 9/11, this is an incredibly thorny
|
||||
issue which HacDC should avoid at all costs.*
|
||||
|
||||
<!-- -->
|
||||
|
||||
|
||||
15\. Do you have a close connection with any organizations? **No**.
|
||||
''HacDC's officers and members are not, as a whole, closely connected to
|
||||
another organization. The closest connection we might have is to our
|
||||
landlord, St. Stephen's, but they do not exercise control over HacDC as
|
||||
an organization nor does HacDC exercise control over it."
|
||||
|
||||
<!-- -->
|
||||
|
||||
|
||||
16\. Are you applying for exemption as a cooperative hospital service
|
||||
organization under section. **No**
|
||||
|
||||
<!-- -->
|
||||
|
||||
|
||||
17\. Are you applying for exemption as a cooperative service
|
||||
organization of operating educational organizations under section
|
||||
501(f)? **No**
|
||||
|
||||
<!-- -->
|
||||
|
||||
|
||||
18\. Are you applying for exemption as a charitable risk pool under
|
||||
section 501(n)? **No**
|
||||
|
||||
<!-- -->
|
||||
|
||||
|
||||
19\. Do you or will you operate a school? **No** *While we offer
|
||||
classes, we do not have formal instruction, a regular faculty, or a
|
||||
regularly enrolled body of pupils.*
|
||||
|
||||
<!-- -->
|
||||
|
||||
|
||||
20\. Is your main function to provide hospital or medical care? If
|
||||
???Yes,??? complete Schedule C. **No**
|
||||
|
||||
<!-- -->
|
||||
|
||||
|
||||
21\. Do you or will you provide low-income housing or housing for the
|
||||
elderly or handicapped? **No**
|
||||
|
||||
<!-- -->
|
||||
|
||||
|
||||
22\. Do you or will you provide scholarships, fellowships, educational
|
||||
loans, or other educational grants to individuals, including grants for
|
||||
travel, study, or other similar purposes? **No**
|
||||
|
||||
## Part IX : Financial Data
|
||||
|
||||
This information is fairly straightforward. Using the UCOA, the
|
||||
applicable statements for the financial year ended December 31, 2008 and
|
||||
the tax year to this point should be easily prepared when the
|
||||
application is ready.
|
||||
|
||||
The balance sheet is for the tax year ended December 31. This will have
|
||||
substantially changed as of the time of filing, and the statement at the
|
||||
time of filing.
|
||||
|
||||
## Part X: Public Charity Status
|
||||
|
||||
HacDC is a Public Charity by virtue of the fact that it receives "broad
|
||||
public support" from many different sources in the public. A Private
|
||||
Foundation is one that is primarily funded by a few individuals, trusts,
|
||||
corporations, etc. The questions below are designed to clarify HacDC's
|
||||
status as a Public Charity.
|
||||
|
||||
|
||||
1\. Are you a private foundation? **No**
|
||||
|
||||
<!-- -->
|
||||
|
||||
|
||||
...
|
||||
|
||||
<!-- -->
|
||||
|
||||
|
||||
5\. If you answered ???No??? to line 1a, indicate the type of public
|
||||
charity status you are requesting by checking one of the choices below.
|
||||
You may check only one box. **Box 5h most closely applies to HacDC**
|
||||
|
||||
<!-- -->
|
||||
|
||||
|
||||
**5h. 509(a)(2)???an organization that normally receives not more than
|
||||
one-third of its financial support from gross investment income and
|
||||
receives more than one-third of its financial support from
|
||||
contributions, membership fees, and gross receipts from activities
|
||||
related to its exempt functions (subject to certain exceptions).**
|
||||
|
||||
<!-- -->
|
||||
|
||||
|
||||
*HacDC qualifies more under 509(a)(2) rather than 509(a)(1), as more
|
||||
than 1/3rd of its income comes from "(i) gifts, grants, contributions,
|
||||
or membership fees, and (ii) gross receipts from ... sales of
|
||||
merchandise, performance of services, or furnishing of facilities, in an
|
||||
activity which is not an unrelated trade or business ..." and does not
|
||||
receive more than 1/3rd of is income from investments or unrelated
|
||||
business income.*
|
||||
|
||||
<!-- -->
|
||||
|
||||
|
||||
6\. If you checked box g, h, or i in question 5 above, you must request
|
||||
either an advance or a definitive ruling by selecting one of the boxes
|
||||
below. Refer to the instructions to determine which type of ruling you
|
||||
are eligible to receive. **Box under 6b should be checked**
|
||||
|
||||
<!-- -->
|
||||
|
||||
|
||||
Request for Definitive Ruling: Check this box if you have completed one
|
||||
tax year of at least 8 full months and you are requesting a definitive
|
||||
ruling. To confirm your public support status, answer line 6b(i) if you
|
||||
checked box g in line 5 above. *Answer line 6b(ii) if you checked box h
|
||||
in line 5 above*. If you checked box i in line 5 above, answer both
|
||||
lines 6b(i) and (ii).
|
||||
|
||||
<!-- -->
|
||||
|
||||
|
||||
6.b(ii)
|
||||
|
||||
<!-- -->
|
||||
|
||||
|
||||
For each year amounts are included on lines 1, 2, and 9 of Part IX-A.
|
||||
Statement of Revenues and Expenses, attach a list showing the name of
|
||||
and amount received from each disqualified person. **None** *Aside from
|
||||
the officers, HacDC has no disqualified persons as long as no person has
|
||||
contributed more than \$5,000. A legal argument can be made the officers
|
||||
are not technically disqualified persons.*
|
||||
|
||||
<!-- -->
|
||||
|
||||
|
||||
For each year amounts are included on line 9 of Part IX-A. Statement of
|
||||
Revenues and Expenses, attach a list showing the name of and amount
|
||||
received from each payer, other than a disqualified person, whose
|
||||
payments were more than the larger of (1) 1% of line 10, Part IX-A.
|
||||
Statement of Revenues and Expenses, or (2) \$5,000. If the answer is
|
||||
???None,??? check this box. **None** *I don't believe there is anyone
|
||||
who contributed more than \$5,000 to HacDC in aggregate*
|
||||
|
||||
<!-- -->
|
||||
|
||||
|
||||
7\. Did you receive any unusual grants during any of the years shown on
|
||||
Part IX-A. Statement of Revenues and Expenses? If ???Yes,??? attach a
|
||||
list including the name of the contributor, the date and amount of the
|
||||
grant, a brief description of the grant, and explain why it is unusual.
|
||||
**No.** *This would be if HacDC received a windfall grant that would
|
||||
wreck the 1/3rd formula.*
|
||||
|
||||
## Part XI: User Fee Information
|
||||
|
||||
Unfortunately, HacDC does not qualify for the reduced user fee. The
|
||||
application will cost \$750.
|
||||
|
||||
[Category:HacDC_Docs](Category:HacDC_Docs "wikilink")
|
||||
Executable
+4
@@ -0,0 +1,4 @@
|
||||
- [MakeDC](http://www.makedc.org)
|
||||
- [Dorkbot DC](http://dorkbot.org/dorkbotdc/)
|
||||
|
||||
[Category:Community](Category:Community "wikilink")
|
||||
Executable
+4
@@ -0,0 +1,4 @@
|
||||
ChanServ AlonzoTG awwaiid blueglass fl1pfl0p\[m\] foxlet\[m\] godane
|
||||
Hunterkll_ juri__ lawlking naomi-test\[m\] natewalck ozzloy_ qeed
|
||||
red_beard rektide rojisan rojisan_roaming RossSchulman\[m\] schneider
|
||||
seele TheAssassin TheCowboy thossou ZipCPU
|
||||
Executable
+4
@@ -0,0 +1,4 @@
|
||||
[Fuller Enterprises](http://www.everydayitemsforless.com) sells a
|
||||
deviation of products online, including gifts, gadgets, collectibles,
|
||||
and novelties over their website everydayitemsforless.com at the of the
|
||||
first water prices.
|
||||
Executable
+44
@@ -0,0 +1,44 @@
|
||||
# Assumptions
|
||||
|
||||
- Each service assumes at the outset that it's the only one in
|
||||
existence.
|
||||
- Each service periodicially probes for the existence of other services.
|
||||
- If two services of the same type find one another, they'll link up and
|
||||
synchronize.
|
||||
- If three services of the same type exist, but A knows about B and B
|
||||
knows about A and C, B and C will synch, and then A and B will synch
|
||||
the content of B and C.
|
||||
|
||||
# Problems
|
||||
|
||||
- Service foo wants to search for services of the same type on other
|
||||
nodes that may or may not exist.
|
||||
- Service foo wants to use another piece of software running on the same
|
||||
node to search for other instances.
|
||||
- The datastore backing service foo isn't capable of synchronizing on
|
||||
its own with others of its type.
|
||||
- The datastore backing service foo cannot grow without bound.
|
||||
- Service foo isn't designed to have a web front end, but needs one.
|
||||
- Service foo needs a plug-in that exposes the service over HTTP.
|
||||
- Each instance of service foo needs a unique identifier.
|
||||
|
||||
# Nonspecific solutions
|
||||
|
||||
- Designate a service on the node that maintains a catalogue of other
|
||||
services running on the node and make them available on the local
|
||||
network.
|
||||
- Designate a service on the node that listens for announcements of
|
||||
other services on neighboring nodes.
|
||||
- Designate a service on the node that watches for new instances of the
|
||||
same service to appear.
|
||||
- The monitoring daemon checks to see if the service announcement has
|
||||
already been picked up.
|
||||
- The monitoring daemon contacts the service's administrative
|
||||
interface and executes the necessary commands to inform it of a new
|
||||
instance to contact.
|
||||
- Service foo contacts the new instance and initiates synchronization.
|
||||
|
||||
I guess I'm talking about ejabberd and avahi here. Maybe with some glue
|
||||
code and the odd exposed administrative interface.
|
||||
|
||||
[Category:Byzantium](Category:Byzantium "wikilink")
|
||||
+451
@@ -0,0 +1,451 @@
|
||||
The following code is capable of converging on a solution to Brad's
|
||||
parabola problem, which can be found on the [NARG](NARG "wikilink") page
|
||||
|
||||
master_stack = {}
|
||||
function_table = {}
|
||||
type_array = {}
|
||||
type_stack = {}
|
||||
|
||||
stack_size = 32
|
||||
|
||||
num_types = 0
|
||||
|
||||
num_x_samples = 5
|
||||
constant = {0,1,2,3,4}
|
||||
expected_result = {0, 4.75, 12.75, 23.98, 38.45, 56.15}
|
||||
function sleep(n)
|
||||
os.execute("sleep " .. tonumber(n))
|
||||
end
|
||||
|
||||
function deepcopy(object)
|
||||
local lookup_table = {}
|
||||
local function _copy(object)
|
||||
if type(object) ~= "table" then
|
||||
return object
|
||||
elseif lookup_table[object] then
|
||||
return lookup_table[object]
|
||||
end
|
||||
local new_table = {}
|
||||
lookup_table[object] = new_table
|
||||
for index, value in pairs(object) do
|
||||
new_table[_copy(index)] = _copy(value)
|
||||
end
|
||||
return setmetatable(new_table, getmetatable(object))
|
||||
end
|
||||
return _copy(object)
|
||||
end
|
||||
|
||||
|
||||
function print_table(theTable, indent)
|
||||
|
||||
local iString = ""
|
||||
for index = 1, indent do
|
||||
iString = iString .. "-"
|
||||
end
|
||||
|
||||
-- walk all the topmost values in the table
|
||||
for k,v in pairs(theTable) do
|
||||
print(iString ,k ,v)
|
||||
if type(v) == "table" then
|
||||
print_table(v, indent + 1)
|
||||
end
|
||||
end
|
||||
|
||||
end
|
||||
|
||||
function print_program(theProgram)
|
||||
print("Program Stack Bottom")
|
||||
for counter = 1, table.getn(theProgram) do
|
||||
if (theProgram[counter].name == "real") then
|
||||
print(theProgram[counter].value)
|
||||
else
|
||||
print(theProgram[counter].name)
|
||||
end
|
||||
end
|
||||
print("Program Stack Top")
|
||||
end
|
||||
|
||||
-- add the type to the type table
|
||||
function insert_function(functionName, functionCall, functionType, nArguments)
|
||||
-- ensure we haven't already inserted this function
|
||||
if function_table[functionName] ~= nil then
|
||||
print("function already defined: " .. functionName)
|
||||
return false
|
||||
end
|
||||
|
||||
-- add this function to the function_table
|
||||
tempFunction = {}
|
||||
tempFunction.fName = functionCall
|
||||
tempFunction.fType = functionType
|
||||
tempFunction.nArgs = nArguments
|
||||
|
||||
function_table[functionName] = tempFunction
|
||||
return true
|
||||
end
|
||||
|
||||
function insert_type(typeName, fPointer, weight)
|
||||
-- walk the list of types and make sure this one hasn't already been defined
|
||||
for index = 1, table.getn(type_array) do
|
||||
if (type_array[index].name == typeName) then
|
||||
print("type already defined: " .. typeName)
|
||||
return false
|
||||
end
|
||||
end
|
||||
|
||||
num_types = num_types + 1
|
||||
type_array[num_types] = {}
|
||||
type_array[num_types].name = typeName
|
||||
type_array[num_types].fPointer = fPointer
|
||||
type_array[num_types].weight = weight
|
||||
|
||||
if fPointer == nil then
|
||||
-- establish the stack for this type
|
||||
type_stack[typeName] = {}
|
||||
end
|
||||
|
||||
return true
|
||||
end
|
||||
|
||||
function local_add(arguments)
|
||||
-- print("adding " .. arguments[1] .. " and " .. arguments[2])
|
||||
return arguments[1] + arguments[2]
|
||||
end
|
||||
|
||||
function local_subtract(arguments)
|
||||
-- print("subtracting " .. arguments[1] .. " and " .. arguments[2])
|
||||
return arguments[1] + arguments[2]
|
||||
end
|
||||
|
||||
function local_multiply(arguments)
|
||||
-- print("multiplying " .. arguments[1] .. " and " .. arguments[2])
|
||||
return arguments[1] * arguments[2]
|
||||
end
|
||||
|
||||
function local_divide(arguments)
|
||||
-- print("dividing " .. arguments[1] .. " and " .. arguments[2])
|
||||
-- dragon
|
||||
if (arguments[2] == 0) then
|
||||
arguments[2] = 0.00001
|
||||
end
|
||||
return arguments[1] / arguments[2]
|
||||
end
|
||||
|
||||
function some_constant()
|
||||
-- print("pushing constant onto stack:" .. constant[currentConstant])
|
||||
return constant[currentConstant]
|
||||
end
|
||||
|
||||
function establish_types()
|
||||
-- add each of our types to the type_table
|
||||
insert_type("real", nil, 10)
|
||||
insert_type("+", local_add, 1)
|
||||
insert_type("*", local_multiply, 1)
|
||||
--insert_type("-", local_subtract, 1)
|
||||
--insert_type("/", local_divide, 1)
|
||||
insert_type("X", some_constant, 5)
|
||||
end
|
||||
|
||||
function establish_functions()
|
||||
insert_function("+", local_add, "real", 2)
|
||||
insert_function("-", local_subtract, "real", 2)
|
||||
insert_function("*", local_multiply, "real", 2)
|
||||
insert_function("/", local_divide, "real", 2)
|
||||
insert_function("X", some_constant, "real", 0)
|
||||
end
|
||||
|
||||
function generate_program(programSize )
|
||||
return_stack = {}
|
||||
|
||||
for counter = 1, programSize do
|
||||
currentNode = {}
|
||||
ranVal = math.random(1,table.getn(type_array))
|
||||
currentNode.name = type_array[ranVal].name
|
||||
-- beware hardcoded stuffs
|
||||
if currentNode.name == "real" then
|
||||
currentNode.value = math.random()
|
||||
end
|
||||
|
||||
table.insert(return_stack, currentNode)
|
||||
end
|
||||
|
||||
return return_stack
|
||||
end
|
||||
|
||||
function process_master()
|
||||
while table.getn(master_stack) ~= 0 do
|
||||
-- print("frame begin-------------------------------")
|
||||
-- print("current table:")
|
||||
-- print_table(type_stack["real"], 0)
|
||||
|
||||
currentNode = table.remove(master_stack)
|
||||
-- print("curret node name: " .. currentNode.name )
|
||||
|
||||
-- treat functions and values differently
|
||||
if currentNode.name == "real" then
|
||||
-- print("current node value: " .. currentNode.value)
|
||||
-- add this value to the 'real' stack
|
||||
table.insert(type_stack["real"], currentNode.value)
|
||||
else
|
||||
-- grab the num of params needed for this function
|
||||
nRequired = function_table[currentNode.name].nArgs
|
||||
theType = function_table[currentNode.name].fType
|
||||
|
||||
-- make sure there are enough objects on the param stack to call this function
|
||||
-- print("name = " .. currentNode.name)
|
||||
-- print(function_table[currentNode.name].fType)
|
||||
-- print(type_stack["real"])
|
||||
if (table.getn(type_stack[function_table[currentNode.name].fType]) < nRequired) then
|
||||
-- not enough params available, NOOP
|
||||
-- print("not enough params, NOOP")
|
||||
else
|
||||
theArguments = {}
|
||||
-- build an array for passing the params to the function
|
||||
for counter = 1, nRequired do
|
||||
theArguments[counter] = table.remove(type_stack[theType])
|
||||
end
|
||||
|
||||
-- call the function
|
||||
returnVal = function_table[currentNode.name].fName(theArguments)
|
||||
|
||||
-- push the return val to the appropriate stack
|
||||
table.insert(type_stack[function_table[currentNode.name].fType], returnVal)
|
||||
|
||||
end
|
||||
end
|
||||
-- print("frame end---------------------------------")
|
||||
end
|
||||
|
||||
end
|
||||
|
||||
function grab_result()
|
||||
-- print the top of the "real" stack
|
||||
if (table.getn(type_stack["real"]) == 0) then
|
||||
return 9999999
|
||||
end
|
||||
return table.remove(type_stack["real"])
|
||||
|
||||
end
|
||||
|
||||
--generate_master()
|
||||
|
||||
--process_master()
|
||||
|
||||
--print_result()
|
||||
|
||||
|
||||
function create_population()
|
||||
-- loop through each member in the population
|
||||
for count = 1, population_size do
|
||||
current_member = {}
|
||||
current_member._error = 99999
|
||||
|
||||
-- generate the member's program data
|
||||
current_member.program = generate_program(initial_member_size)
|
||||
|
||||
-- add this member to the population
|
||||
table.insert(population, current_member)
|
||||
end
|
||||
end
|
||||
|
||||
function get_best_candidate()
|
||||
local best_error = 99999
|
||||
local best_index = 0
|
||||
|
||||
for tIndex = 1, table.getn(candidates) do
|
||||
if candidates[tIndex]._error < best_error then
|
||||
best_index = tIndex
|
||||
best_error = candidates[tIndex]._error
|
||||
end
|
||||
end
|
||||
|
||||
--print("candidate size: " .. table.getn(candidates) .. "\nbest error from candidates: " .. best_error)
|
||||
|
||||
-- remove and return the *best* candidate
|
||||
return table.remove(candidates, best_index)
|
||||
end
|
||||
|
||||
function mutate_child(origin, n_mutations)
|
||||
dest_node = deepcopy(origin)
|
||||
|
||||
for counter = 1, n_mutations do
|
||||
-- random point inside this child
|
||||
index_mutate = math.random(1, table.getn(dest_node.program))
|
||||
|
||||
ranVal = math.random(1,table.getn(type_array))
|
||||
dest_node.program[index_mutate].name = type_array[ranVal].name
|
||||
-- beware hardcoded stuffs
|
||||
if dest_node.program[index_mutate].name == "real" then
|
||||
dest_node.program[index_mutate].value = math.random()
|
||||
end
|
||||
end
|
||||
|
||||
return dest_node
|
||||
end
|
||||
|
||||
function crossover_parents(mommy, daddy)
|
||||
index_m = math.random(1, table.getn(mommy))
|
||||
--index_d = math.random(1, table.getn(daddy))
|
||||
|
||||
the_child = {}
|
||||
|
||||
-- add the first index_m elements of mommy to the_child
|
||||
for xxx = 1, index_m do
|
||||
table.insert(the_child, mommy[xxx])
|
||||
end
|
||||
|
||||
-- add the elements index_d to #daddy of daddy to the_child
|
||||
for xxx = index_m+1, table.getn(daddy) do
|
||||
table.insert(the_child, daddy[xxx])
|
||||
end
|
||||
|
||||
return the_child
|
||||
end
|
||||
|
||||
-- initialize the population (1 program for each member in the population)
|
||||
establish_functions()
|
||||
establish_types()
|
||||
population = {}
|
||||
population_size = 10000
|
||||
initial_member_size = 24
|
||||
create_population()
|
||||
|
||||
error_history = {}
|
||||
error_threshhold = 0.016
|
||||
|
||||
|
||||
max_num_iterations = 10000
|
||||
current_iteration = 1
|
||||
|
||||
-- while we haven't reached our error threshhold
|
||||
while current_iteration <= max_num_iterations do
|
||||
|
||||
print("iteration #" .. current_iteration)
|
||||
|
||||
--print_table(population, 2)
|
||||
|
||||
-- get the error for each of the members of our population
|
||||
for pcount = 1, population_size do
|
||||
|
||||
--print_table(population[pcount], 1)
|
||||
|
||||
-- initialize the error for this program
|
||||
population[pcount]._error = 0
|
||||
--print("pcount = " .. pcount)
|
||||
|
||||
if (current_iteration == 2) then
|
||||
--print_table(population[pcount], 1)
|
||||
end
|
||||
|
||||
|
||||
-- for each value of X
|
||||
for icount = 1, num_x_samples do
|
||||
-- establish the index to the current X/Y pair
|
||||
currentConstant = icount
|
||||
|
||||
-- print("population size: " .. table.getn(population))
|
||||
-- print("master_stack size: " .. table.getn(population[pcount].program))
|
||||
|
||||
-- make a copy of this guy's program
|
||||
master_stack = deepcopy(population[pcount].program)
|
||||
|
||||
-- initialize the stacks for each data type
|
||||
type_stack["real"] = {}
|
||||
|
||||
-- evaluate the program
|
||||
process_master()
|
||||
|
||||
-- print("master_stack size: " .. table.getn(population[pcount].program))
|
||||
|
||||
-- print("!!! - " .. table.getn(type_stack["real"]))
|
||||
|
||||
the_result = grab_result()
|
||||
|
||||
--print("the result = " .. the_result)
|
||||
|
||||
-- add the current error to the total error for this program
|
||||
population[pcount]._error = population[pcount]._error + math.abs(the_result - expected_result[currentConstant])
|
||||
end
|
||||
end
|
||||
|
||||
-- scan the population and find the lowest error
|
||||
total_error = 0
|
||||
best_error = 99999
|
||||
best_index = 0
|
||||
for pcount = 1, population_size do
|
||||
total_error = total_error + population[pcount]._error
|
||||
if (population[pcount]._error < best_error) then
|
||||
best_index = pcount
|
||||
best_error = population[pcount]._error
|
||||
end
|
||||
end
|
||||
|
||||
average_error = total_error / population_size
|
||||
|
||||
print("lowest error : " .. best_error)
|
||||
print("average error: " .. average_error)
|
||||
|
||||
table.insert(error_history, best_error)
|
||||
|
||||
-- if the error is under our threshhold, break out and report success
|
||||
if (best_error < error_threshhold) then
|
||||
break
|
||||
end
|
||||
|
||||
|
||||
--=======================================================================
|
||||
-- evolution FTW
|
||||
--=======================================================================
|
||||
|
||||
children = {}
|
||||
child = {}
|
||||
candidates = deepcopy(population)
|
||||
|
||||
-- find the top 10% of the population, keep them
|
||||
tnum = math.ceil(table.getn(population) / 100)
|
||||
for cpop = 1, tnum do
|
||||
table.insert(children, get_best_candidate())
|
||||
end
|
||||
|
||||
|
||||
--sleep(10)
|
||||
-- the next 25% should be mutations of the top 10%
|
||||
xnum = tnum + math.floor(tnum * 10)
|
||||
candidates = deepcopy(children) -- reset candidates
|
||||
-- print("we have " .. table.getn(candidates) .. " candidates to chose from")
|
||||
for cpop = (tnum+1), xnum do
|
||||
child = mutate_child(candidates[math.random(1, table.getn(candidates))], 5)
|
||||
table.insert(children, deepcopy(child))
|
||||
-- print("size of children: " .. table.getn(children))
|
||||
end
|
||||
|
||||
-- the remainder should be crossovers of the full population
|
||||
for pcount = (xnum+1), population_size do
|
||||
|
||||
-- take 7 random values from the population
|
||||
candidates = {}
|
||||
child = {}
|
||||
for ccount = 1, 7 do
|
||||
table.insert(candidates, deepcopy(population[math.random(1, table.getn(population))]))
|
||||
end
|
||||
|
||||
-- print_table(candidates, 1)
|
||||
|
||||
mom = get_best_candidate()
|
||||
dad = get_best_candidate()
|
||||
child.program = crossover_parents(mom.program, dad.program)
|
||||
|
||||
-- write the child data to the list of children
|
||||
table.insert(children, child)
|
||||
end
|
||||
|
||||
-- move the new population to their proper home
|
||||
population = deepcopy(children)
|
||||
|
||||
current_iteration = current_iteration + 1
|
||||
end
|
||||
|
||||
print("all done!")
|
||||
--print_table(population[best_index].program, 1)
|
||||
print_program(population[best_index].program)
|
||||
|
||||
[Category:NARG](Category:NARG "wikilink")
|
||||
+5
@@ -0,0 +1,5 @@
|
||||
Leading Suppliers of Anti-Cancer, Hepatitis-C, HIV-Medicines from India.
|
||||
[Get price or buy online Daclastavir](http://www.hcvmedicine.com/),
|
||||
Sorafenib, Veenat, Lapatinib, Abiraterone, Votrient, Velpatasvir,
|
||||
Crizalk, Hepcinat, Ledifos.Largest Suppliers in India and throughout the
|
||||
world.
|
||||
Executable
+24
@@ -0,0 +1,24 @@
|
||||
## Git Config
|
||||
|
||||
### Git Alias
|
||||
|
||||
To use add to ~/.gitconfig under "\[alias\]"
|
||||
|
||||
- list all untracked files that aren't in .gitignore
|
||||
|
||||
<!-- -->
|
||||
|
||||
ls-untracked = "!git ls-files --other --exclude-standard"
|
||||
|
||||
- shorthand for "pull --rebase"
|
||||
|
||||
<!-- -->
|
||||
|
||||
up = "!git pull --rebase"
|
||||
|
||||
- list all untracked files not in .gitignore and wait for for user to
|
||||
press enter, then "pull --rebase" and push changes
|
||||
|
||||
<!-- -->
|
||||
|
||||
sync = "!sh -c 'git_sync(){ git ls-untracked ; echo press enter to continue; read junk ;git up $* ;git push $* ; } ;git_sync $@'"
|
||||
Executable
+6
@@ -0,0 +1,6 @@
|
||||
It's not Fantasy Sports and it's not betting. It is a fun, social and
|
||||
intelligent diversion to play while you are viewing your most loved
|
||||
group alone or with companions. It's not about spreadsheets or
|
||||
multiplying down; it's extraordinary for tenderfoots and specialists
|
||||
alike. Watch the Video here:
|
||||
[<https://www.youtube.com/watch?v=lcBNHZiOaRs>](https://www.youtube.com/watch?v=lcBNHZiOaRs/)
|
||||
Executable
+18
@@ -0,0 +1,18 @@
|
||||
VLADIMIR PUTIN, Donald Trump, ANATOLIY GOLOD: GOOD CYCLES CAN IMPROVE
|
||||
THE WORLD. READ **[GOOD SENSATION](http://www.super-dobro.com/)**!
|
||||
Vladimir Putin (President, RUSSIAN FEDERATION), Donald Trump (President,
|
||||
USA), Anatoliy Golod (General Director, GUIDES). RUSSIAN FEDERATION
|
||||
creates worldwide support. For making good relations, good situations in
|
||||
the world General Universal Information Defense Excellent Service was
|
||||
created in Russia (GUIDES, General director, creator: Anatoliy Golod,
|
||||
has diploma with honors, Ph.D.). It accumulates informational resources
|
||||
from the all world security services who want to make good situations in
|
||||
the world. That's why it also names in mass media: the Central
|
||||
Intelligence Universe Agency (CIUA , "See I You Are": "I can see, You
|
||||
can see"; it is necessary to see each other, good communicate with each
|
||||
other to make good situations and good relations in society). The good
|
||||
prestige can have good informational, social and economic activities for
|
||||
good results in society, that's why the Russian well oriented
|
||||
organizations, security services and well oriented good organizations,
|
||||
security services in all countries who want to make good situations in
|
||||
the world can take the good prestige.
|
||||
+201
@@ -0,0 +1,201 @@
|
||||
# WELCOME
|
||||
|
||||
Hello, and welcome to The Great Global Hackerspace Challenge, brought to
|
||||
you by the very excited folks over at element14!
|
||||
|
||||
You are one of thirty hackerspaces from across the globe who have been
|
||||
chosen to participate in this amazing event, which seeks to stretch your
|
||||
hackerspace-minded ingenuity to its very limit to create an electronics
|
||||
build that will make a real, and very positive difference in an
|
||||
educational establishment. And for you to have a whole lot of fun along
|
||||
the way!
|
||||
|
||||
Exactly what that build is, and what solution it provides is entirely
|
||||
down to you. The only stipulation is that your build must make use of a
|
||||
microcontroller and a portable power source. We encourage you to reach
|
||||
out to an educational institute in your area so that you can test your
|
||||
invention as it evolves, make sure you are answering a genuine
|
||||
educational need, and hopefully establish a home for your product once
|
||||
the challenge is over.
|
||||
|
||||
Within this pack, you'll find detailed information on the equipment
|
||||
element14 will provide you with to get your creative thoughts flowing,
|
||||
and your talented hands building, as well as the low down on how to
|
||||
share your Hackerspace's ongoing progress with the world.
|
||||
|
||||
We'd also ask you make sure to read our Great Global Hackerspace
|
||||
Challenge Pact section, on which we are asking for a virtual handshake
|
||||
from you. It's our way of establishing mutual ground rules and
|
||||
understanding before the storm of genius activity begins.
|
||||
|
||||
We thank you once again for being a part of this incredible challenge,
|
||||
wish you the very best of luck, and look forward with great anticipation
|
||||
to seeing your work as it develops. This is a challenge in which
|
||||
brilliant minds collaborate so that everybody wins. Onwards!
|
||||
|
||||
## CHALLENGE GUIDELINES
|
||||
|
||||
Outlined below is a step-by-step guide with all the information you will
|
||||
need to help make your hackerspace challenge as successful as possible.
|
||||
There's a great deal to do in a very short space of time, and so we have
|
||||
created a calendar of key delivery dates which you'll find at the end of
|
||||
this pack to help you stay on track.
|
||||
|
||||
If you have any questions along the way that aren't answered here,
|
||||
please email hackerspace@element14.com and we'll be sure to get back to
|
||||
you.
|
||||
|
||||
## YOUR TOOL KIT
|
||||
|
||||
element14 is providing you with a budget of \$900 US to complete your
|
||||
build. You will be contacted directly to establish exactly how you would
|
||||
prefer to receive this money. Your microcontroller and portable power
|
||||
source should be procured using this money, and any additional
|
||||
electronic components you might need can be purchased from the element14
|
||||
store. Simply go to the element14 website (www.element14.com), click on
|
||||
the 'store' tab and then select your items using your \$900 stipend.
|
||||
Your components will then be sent directly to you.
|
||||
|
||||
We ask that you try not add to this budget, as one of the judging
|
||||
criteria is based on the total cost of the final build, but you are
|
||||
fully permitted to use any components or items that you might already
|
||||
have at your hackerspace within your build. We challenge you to be as
|
||||
creative as you like!
|
||||
|
||||
## DOCUMENTING YOUR BUILD
|
||||
|
||||
Core to this challenge is to produce an electronics build that will
|
||||
ultimately help education, but you can also start to help people learn
|
||||
about hackerspaces and electronics building along the way by regularly
|
||||
sharing information on your design. This is also how the judging panel
|
||||
will be able to track your progress and pick the three semi-finalists,
|
||||
and a minimum of one weekly update is a mandatory element of the
|
||||
challenge.
|
||||
|
||||
Please feel free to share all your exciting moments as they happen, but
|
||||
as a guideline, content that would be useful for you to provide would
|
||||
be:
|
||||
|
||||
- Week 1
|
||||
- Introduce your team (video would be a great way to do this), explain
|
||||
your hackerspace's philosophy, and provide a top level summary of
|
||||
your first week
|
||||
- Week 2
|
||||
- Provide a basic outline of the materials you will be using in your
|
||||
build and any key challenges you anticipate
|
||||
- Week 3
|
||||
- Provide an update on the status of your build and quick summary of
|
||||
obstacles encountered and how they are being addressed
|
||||
- Week 4
|
||||
- Is everything going to plan? Perhaps provide footage of a visit to
|
||||
an educational institution you're working with
|
||||
- Week 5
|
||||
- In your penultimate week provide a review of the challenge to date.
|
||||
Is the pressure on? What have you learned?
|
||||
- Week 6
|
||||
- This is the time to really showcase your build, why it works and
|
||||
what features make it stand out
|
||||
|
||||
## HOW TO SHARE
|
||||
|
||||
You will be required to contribute to your profile page within the
|
||||
element14 community. This is where you can upload your videos and photos
|
||||
and keep everyone informed via a written blog. You will be able to
|
||||
personalize the page so that your hackerspace's own unique character
|
||||
shines through. To do this, go to element14.com, click on ???Join Now???
|
||||
if you are not already registered, using your Hackerspace name, and we
|
||||
will create your page for you.
|
||||
|
||||
## BUILD CRITERIA
|
||||
|
||||
Our esteemed panel of judges will include luminaries from the worlds of
|
||||
technology and science, education and hackerspacing.
|
||||
|
||||
Following the completion of the build period, they will be judging each
|
||||
one on the criteria below in order to select three semi-finalists to
|
||||
attend the California Maker Faire for the grand finale on May 22.
|
||||
|
||||
Semi-finalists will be notified personally by Mitch on May 6.
|
||||
|
||||
Criteria:
|
||||
|
||||
- How reproducible is the final project
|
||||
- How easily can the parts be sourced in locations around the world
|
||||
- How low cost is the final output
|
||||
- How well are the plans documented
|
||||
- How relevant is the project to helping education today
|
||||
- How inventive and creative is the design and build of the project
|
||||
|
||||
## THE MAKER FAIRE GRAND FINALE
|
||||
|
||||
The Great Global Hackerspace Challenge will culminate in a live
|
||||
demonstration of each of the three semi-finalists in front of the panel
|
||||
of judges at the San Mateo Maker Faire. One team member from the final
|
||||
three hackerspaces will be flown out to California to attend the Faire
|
||||
and present their build. Air fare, hotel accommodation and daily food
|
||||
costs will all be covered by element14 - we'll provide more detail on
|
||||
this if you are selected.
|
||||
|
||||
In the spirit of collaboration over competition, and to thank you for
|
||||
taking part, element14 will be sending you a set of soldering equipment,
|
||||
including a soldering station, for your hackerspace once you have
|
||||
completed the challenge.
|
||||
|
||||
Each of the semi-finalist hackerspaces will receive the following
|
||||
prizes:
|
||||
|
||||
- Fluke 233 DMM (worth US\$300)
|
||||
- Fluke 381 Clamp Meter (worth US\$500)
|
||||
- Tektronix PWS4205 Power Supply (worth US\$865)
|
||||
- Agilent HH DMM (specific model TBD)
|
||||
|
||||
Finally, the build chosen to have that extra sprinkling of hackerspace
|
||||
magic will receive a suitably rocking prize: a Tektronix MSO2024
|
||||
oscilloscope (worth around US\$5,600). Start clearing a space in the
|
||||
corner of your hackerspace now!
|
||||
|
||||
## THE GREAT GLOBAL HACKERSPACE CHALLENGE PACT
|
||||
|
||||
You won't find any legal language here. We promise. The purpose of this
|
||||
section is to let you know that if, for any reason you are unable to
|
||||
finish your project you should let the organizers know as soon as
|
||||
possible. Particularly if you encounter circumstances beyond your
|
||||
control. We need to be able to manage expectations so we can accommodate
|
||||
the logistics of the event; judging, the Maker Faire event and the
|
||||
management of the content on the community.
|
||||
|
||||
This isn't a contract. You won't be signing your life away. We trust
|
||||
you. We simply want to have the best competition possible.
|
||||
|
||||
To quote the 1989 MGM classic 'Bill & Ted's Excellent Adventure' we want
|
||||
everyone involved in this event to 'Be excellent to each other'. And
|
||||
that works full circle. We are investing funds into your builds and you
|
||||
are investing your valuable time and energy into our challenge. In the
|
||||
spirit of transparency and collaboration we want everyone to succeed and
|
||||
get as much as they can from this project however we reserve the right
|
||||
to withhold product and stipend if groups do not deliver on the
|
||||
requirements of the challenge. We will be in close communication
|
||||
throughout this project and, we can all work together to avoid any
|
||||
adverse situations.
|
||||
|
||||
## CHALLENGE KEY DATES CALENDAR
|
||||
|
||||
- Week of 3/21 : Official Challenge Briefing / Q+A
|
||||
- 3/25: Deadline to create your profile and submit your first blog
|
||||
update
|
||||
- 4/1: Deadline for Hackerspace Challenge Blog Post 2
|
||||
- 4/15: Deadline for Hackerspace Challenge Blog Post 3
|
||||
- 4/30: End of build time
|
||||
- 05/01- 05/05: Judging period
|
||||
- 05/06: 3 semi-finalists will be announced
|
||||
- Week Of 5/16: One team member from each of the three semi-finalist
|
||||
hackerspaces will travel to San Francisco Bay Area
|
||||
- 5/21/22: Maker Faire
|
||||
- 5/22: Maker Faire Great Global Hackerspace Challenge Grand Finale
|
||||
- 5/23: Team members travel home
|
||||
|
||||
## Links
|
||||
|
||||
[<http://www.element-14.com/community/groups/the-great-global-hackerspace-challenge>](http://www.element-14.com/community/groups/the-great-global-hackerspace-challenge)
|
||||
|
||||
[Category:Previous_Projects](Category:Previous_Projects "wikilink")
|
||||
Executable
+14
@@ -0,0 +1,14 @@
|
||||
Group Photo from September, 2010
|
||||
|
||||
With Flash
|
||||
|
||||
<http://wiki.hacdc.org/images/9/95/Group_photo_2010_flash.jpg>
|
||||
|
||||
Without Flash
|
||||
|
||||
<http://wiki.hacdc.org/images/0/05/Group_photo_2010.jpg>
|
||||
|
||||
Originals (read: Print quality) are available on flickr here
|
||||
<http://bit.ly/cXoJUK>
|
||||
|
||||
[Category:Marketing](Category:Marketing "wikilink")
|
||||
Executable
+21
@@ -0,0 +1,21 @@
|
||||
This tutorial follows a series from 'sprites mods'
|
||||
[1](https://spritesmods.com/?art=hddhack&page=1) to attempt to reverse
|
||||
engineer a hard drive controller board
|
||||
|
||||
# JTAG Hookup Process
|
||||
|
||||
The first step is to hook up wires to the JTAG pins of the hard drive
|
||||
controller board in question.
|
||||
|
||||
Fortuitously, the HDD board I have appears to have the same pinout as
|
||||
the one on Sprites Mods for the JTAG pins. This involved a fair bit of
|
||||
fine tip soldering to small pads and attempting to follow traces on a
|
||||
dense PCB. Pictures below
|
||||
|
||||
*INSERT PICTURE HERE*
|
||||
|
||||
Once the pins were soldered (GND, TDI, TMS, CLK IN, and TDO), the ARM
|
||||
JTAG programmer had to get hooked up to the soldered wires.
|
||||
|
||||
The pinout of the JTAG programmer is oriented such that the power input
|
||||
on the bottom.
|
||||
Executable
+39
@@ -0,0 +1,39 @@
|
||||
# NamingConvention
|
||||
|
||||
## Physical
|
||||
|
||||
### Hostnames
|
||||
|
||||
HacDC-shared-m335-1
|
||||
|
||||
- HacDC - Identifies machine as HacDC or HacDC member property on the
|
||||
local network.
|
||||
- shared - One of private, restricted, shared. Private = one member only
|
||||
(eg. RasPi). Restricted = limited access (eg. HacDC web server).
|
||||
Shared = shared resources (ie. remote shells).
|
||||
- m335 - Abbreviated member name or screen name. Full contact details
|
||||
should be written on the physical machine.
|
||||
- 1 - Unique identifier.
|
||||
|
||||
### FQDNs
|
||||
|
||||
HacDC-shared-m335-1.hacdc.org
|
||||
|
||||
## Virtual
|
||||
|
||||
### Hostnames
|
||||
|
||||
mirage335-1
|
||||
|
||||
- mirage335 - Local username.
|
||||
- 1 - Unique machine identifier.
|
||||
|
||||
### FQDNs
|
||||
|
||||
m335-1.HacDC-shared-m335-1.hacdc.org
|
||||
|
||||
# Timezone
|
||||
|
||||
EST/EDT aka US Eastern, America/NewYork, or "Eastern"
|
||||
|
||||
[Category:ServerStandards](Category:ServerStandards "wikilink")
|
||||
Executable
+233
@@ -0,0 +1,233 @@
|
||||
OBSOLETE Xen on Debian Stable gave some mysterious disk-controller
|
||||
errors, thoroughly confirmed not to be hardware problems, at least
|
||||
insofar as lack of HVM support is not a hardware problem. OpenVZ has
|
||||
been chosen instead.
|
||||
|
||||
Simple project server, emphasis on availability and uptime.
|
||||
|
||||
Most likely, this server will continue operating for several years, even
|
||||
as newer and better servers supplant it.
|
||||
|
||||
# Login
|
||||
|
||||
On any unix terminal emulator, enter the command:
|
||||
|
||||
``
|
||||
`ssh <userName>@HacDC-shared-m335-1.hacdc.organd`
|
||||
|
||||
On other platforms, try applications like
|
||||
[PuTTY](http://www.chiark.greenend.org.uk/~sgtatham/putty/) with similar
|
||||
settings.
|
||||
|
||||
# CommandReference
|
||||
|
||||
Routinely important commands unique to this server documented as
|
||||
follows.
|
||||
|
||||
## Root (Admin)
|
||||
|
||||
### ReInstall
|
||||
|
||||
- apt-get install xen-linux-system xen-tools git sudo
|
||||
- dpkg-divert --divert /etc/grub.d/08_linux_xen --rename
|
||||
/etc/grub.d/20_linux_xen
|
||||
- Installation of [hostedXen](https://github.com/mirage335/hostedXen) .
|
||||
- Uncomment lines referring to "-nat" and comment other
|
||||
vif-script/network-script lines in /etc/xen/xend-config.sxp .
|
||||
- Uncomment "dir = /home/xen" in /etc/xen-tools/xen-tools.conf .
|
||||
|
||||
### hostedXen
|
||||
|
||||
- ./hxNewUser <userName> \# Creates user account with default Xen VM and
|
||||
permissions.
|
||||
- ./hxDelUser <userName> \# Deletes user account, associated VMs, and
|
||||
associated Xen permissions.
|
||||
- ./hxNewVM <userName> <VM_Number> <dist> \# Creates VM accessible to
|
||||
non-root user <userName> .
|
||||
|
||||
### Autostart
|
||||
|
||||
Through normal reboots, host will suspend/resume any guest VMs. If that
|
||||
is insufficient, the correct way to enable autostarting is through the
|
||||
xm command, [documented as method 2
|
||||
here](https://www.novell.com/support/kb/doc.php?id=3466408).
|
||||
|
||||
### iptables
|
||||
|
||||
#### Investigation
|
||||
|
||||
- iptables -t nat -L -n -v \#Lists port forwarding rules.
|
||||
- iptables -t nat -F \#Deletes port forwarding rules.
|
||||
- iptables -D PREROUTING 1 \#Deletes port forwarding rule.
|
||||
|
||||
#### Forwarding
|
||||
|
||||
##### Enable
|
||||
|
||||
``
|
||||
`/sbin/iptables -P FORWARD ACCEPT`
|
||||
`/sbin/iptables --table nat -A POSTROUTING -o eth0 -j MASQUERADE`
|
||||
|
||||
##### Specific
|
||||
|
||||
``
|
||||
`/sbin/iptables -t nat -A PREROUTING -p tcp -i eth0 --dport 20283 -j DNAT --to 10.174.10.5:22`
|
||||
|
||||
##### Persistent
|
||||
|
||||
Package iptables-persistent has been installed. Upon installation,
|
||||
existing iptables rules were saved. Edit /etc/iptables/rules.v4 .
|
||||
|
||||
## Users
|
||||
|
||||
### List
|
||||
|
||||
List Xen VMs created for you.
|
||||
|
||||
``
|
||||
`cat ~/xenList`
|
||||
|
||||
### Startup
|
||||
|
||||
Start Xen VM, and launch console.
|
||||
|
||||
``
|
||||
`sudo /usr/sbin/xm create -c /etc/xen/<name>.cfg #Escape with Ctrl+] .`
|
||||
|
||||
Just start Xen VM. Useful if planning to interact through other means
|
||||
(ie. network).
|
||||
|
||||
``
|
||||
`sudo /usr/sbin/xm create /etc/xen/<name>.cfg`
|
||||
|
||||
### Shutdown
|
||||
|
||||
Yes, really, hard shutdown is termed "destroy". Don't worry, not
|
||||
synonymous with "delete".
|
||||
|
||||
``
|
||||
`sudo /usr/sbin/xm destroy <name>`
|
||||
|
||||
### Console
|
||||
|
||||
Opens the console of running VM <name> .
|
||||
|
||||
``
|
||||
`sudo /usr/sbin/xm console <name> #Escape with Ctrl+] .`
|
||||
|
||||
# Characteristics
|
||||
|
||||
- CPU - E2200 Dual-Core 2.2GHz
|
||||
- RAM - 1GB
|
||||
- HDD - 500GB
|
||||
- Hostname - HacDC-shared-m335-1
|
||||
- FQDN - HacDC-shared-m335-1.hacdc.org
|
||||
|
||||
# Redundancy (RAID)
|
||||
|
||||
None yet, keep backups. Nonetheless, hard disk is kept cool, so the
|
||||
server should have a long life ahead of it.
|
||||
|
||||
# Policies
|
||||
|
||||
## Permissions
|
||||
|
||||
### Root
|
||||
|
||||
HacDC members with a demonstrable need or willingness to manage non-root
|
||||
users may be given root access. Imperative that root users do not
|
||||
jeopardize uptime.
|
||||
|
||||
### Shell
|
||||
|
||||
All HacDC members are welcome to non-root shell accounts, directly
|
||||
provided by the server, and used to manage Xen VMs.
|
||||
|
||||
### Xen
|
||||
|
||||
All HacDC members are welcome to Xen Virtual Machines. Resources,
|
||||
including CPU, disk space, and external network ports, will be allocated
|
||||
on an as-needed first-come-first-serve basis.
|
||||
|
||||
Root users, please use the provided hostedXen scripts. Following the
|
||||
naming conventions set therein helps account for which resources belong
|
||||
to whom.
|
||||
|
||||
## Notifications
|
||||
|
||||
Internal server email will notify users, if feasible, on the following
|
||||
schedules, subject to change.
|
||||
|
||||
- Three days before planned downtime exceeding one hour.
|
||||
- One week before planned permanent downtime (obsolescence).
|
||||
|
||||
## Removal
|
||||
|
||||
- Three months before removal of ex-member accounts. Exceptions on a
|
||||
case-by-case basis.
|
||||
|
||||
## DataLoss
|
||||
|
||||
- Users should regularly backup critical data offiste.
|
||||
- Onsite data storage is not guaranteed to be reliable.
|
||||
- All server data may be deleted after obsolescence.
|
||||
- Removed accounts may be deleted immediately and permanently upon
|
||||
deactivation.
|
||||
|
||||
## Privacy
|
||||
|
||||
Machine is physically accessible to all keyholding HacDC members.
|
||||
Although HacDC members are generally responsible, privacy should not be
|
||||
expected.
|
||||
|
||||
## AcceptableUse
|
||||
|
||||
### Sharing
|
||||
|
||||
Sharing of account resources is permitted, however, additional resources
|
||||
will be allocated according to individual member needs for specific
|
||||
purposes. As a reminder, compromised accounts will be immediately
|
||||
removed as discovered.
|
||||
|
||||
### Bandwidth
|
||||
|
||||
Hard bandwidth limits have not been set to ease administration of local
|
||||
file servers. However, please configure applications to limit maximum
|
||||
bandwidth use where possible, particularly for web servers.
|
||||
|
||||
# ChiefAdmin
|
||||
|
||||
mirage335
|
||||
|
||||
# Credits
|
||||
|
||||
Hunterkll - Donated core hardware.
|
||||
|
||||
# Special Services
|
||||
|
||||
# Funtoo
|
||||
|
||||
Funtoo (enhanced Gentoo) build server is available, with binary packages
|
||||
and weekly full-os tarballs for new installations.
|
||||
|
||||
# Softload
|
||||
|
||||
<https://github.com/mirage335/hostedXen>
|
||||
|
||||
# Reference
|
||||
|
||||
- <https://wiki.debian.org/Xen#Domain_0_.28Host.29_Installation>
|
||||
- <http://dev.e-taxonomy.eu/trac/wiki/Xen_installation>
|
||||
- <http://wiki.xenproject.org/wiki/Nested_Virtualization_in_Xen#How_to_use_nested>
|
||||
- <http://wiki.xen.org/wiki/Host_Configuration/Networking#Routing>
|
||||
- <http://blog.manula.org/2012/04/manually-configuring-nat-networking-in.html>
|
||||
- <http://www.fclose.com/816/port-forwarding-using-iptables/>
|
||||
- <https://wiki.debian.org/iptables>
|
||||
- <http://blog.manula.org/2011/02/xen-bridged-networking-mode.html>
|
||||
- <http://xen.1045712.n5.nabble.com/console-access-to-non-root-xen-3-0-td2560667.html>
|
||||
- <http://xen-tools.org/pipermail/xen-tools-discuss/2009-September/000674.html>
|
||||
- <https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/5/html/Virtualization/sect-Virtualization-Tips_and_tricks-Limit_network_bandwidth_for_a_Xen_guest.html>
|
||||
- <http://serverfault.com/questions/52027/how-can-i-limit-per-user-bandwidth>
|
||||
- <http://www.howtoforge.com/nat-gateway-iptables-port-forwarding-dns-and-dhcp-setup-ubuntu-8.10-server>
|
||||
- <https://major.io/2007/02/09/delete-single-iptables-rules/>
|
||||
- <https://www.novell.com/support/kb/doc.php?id=3466408>
|
||||
Some files were not shown because too many files have changed in this diff Show More
Reference in New Issue
Block a user