HacDC Wiki - User contributions [en]

User:Q

2009-06-19T20:19:38Z

[[Category:Members]]

== Andrew Q Righter ==
=== Security Researcher ===

[[Image:Qlabs-photo1.jpg]]

Experience: 
o Website Development Level: Advanced Note: Really don't enjoy doing this stuff anymore
o Web Application Development Level: Intermediate Note: Don't enjoy doing this stuff anymore
o Graphic Design Level: Advanced Note: Don't enjoy doing this stuff anymore
o Digital Media Level: Intermediate Note: Don't enjoy doing this stuff anymore
o Programmer Level: Intermediate Note: Python and C seem to be the languages I use most
o Network Security Level: Intermediate Note: It's what pays the bills (most of them anyway)
o Electronic Engineering Level: Intermediate Note: EE FTW!
o Machinist Level: Intermediate Note: Trying to get access to a machine shop in D.C.
o Reverse Engineering Level: Beginner Note: Trying to get someone to teach a course on this subject.
o Wireless Hacker Level: Advanced Note: Will teach anyone how to pwnz the APz
o Lockpicker Level: Intermediate Note: Severely out-of-practice but I can still teach
o Electronic Security Level: Intermediate Note: Will be giving my Blackhat training at HacDC before/after
o Gamer Level: Advanced Note: Will teach anyone how to pwnz noobs
o Telco Level: Chicken Noob Note: Trying to get someone to teach me more
o HAM Dork Level: Chicken Noob Note: Trying to get someone to teach me more

OS Choice: 
o Linux (Slackware, Ubuntu)
o Mac (OSX)
o Windows (XP Professional)

Current Interests: 
o Hardware
o Tools
o Machining
o Building labs

Projects: 
o Physical Access Control Thingy
o MAME Cabinet Build
o Robotic Arm Development (Codename: Butterfingers)

Conferences: 
o '''HOPE 2006''' New York City, New York - TOOOL US lockpicking training
o '''Defcon 2007''' Las Vegas, Nevada - Wireless Village (setup | ran wireless hacking contest)
o '''Hack in the Box 2007''' Kuala Lumpur, Malaysia - Spoke about the insecurities of RFID
o '''HackCon 2008''' Oslo, Norway - Spoke on electronic security and DIY ideas for hobbyists
o '''Blackhat 2008''' Las Vegas, Nevada - Will be training students about electronic security exploits
o '''Hack in the Box 2008''' Kuala Lumpur, Malaysia - Will be training students about hacking the RF spectrum (802.11, RFID)

Talk:Physical Access Control Project

2008-07-01T21:20:40Z

'''Discussion: Physical Access Control Project'''

-----

I'm with you on the wiki-tard front, and not sure the "discussion" page is really all that good for discussions, being essentially a whiteboard. Anyone?

Andrew, thanks for cleaning this up and making the project look all professional-like. Feel free to delete any of the old material as you see fit. I wasn't sure what the tone of the project should be initially, and I took it fairly far in the unprofessional direction. I like what you've done with it better.

As for the logic layer in-between the card reader and electronic impeder/strikeplate/whatever, that should be fairly simple, depending on how much fun we decide to have with it. Myself, I'm for keeping it fairly open to allow multiple (amusing?) opening mechanisms in addition to the keycards, but that will necessarily reduce the security of the lock.

Are we building a fortress or just beefing up our current (minimal!) security?

(Elliot)

-----

''So i'm a wiki-tard, is there anyway to make these discussions threaded? Seems like it would make more sense''

''Added by Mark W, Thu, May 22, 2008:'' I think this is what you're looking for: [http://www.smarthome.com/5190s12.html Electric Door Strike]

Elliot demo'ed his knock-code routine and got some useful feedback. Things like ambient noise and a relatively-long timeout period need improvement.

Andrew suggested using a "Sonic Screwdriver" a la Doctor Who. This opens up all sorts of fun/funny code mechanisms. For instance, a keyfob with an ultrasonic speaker might be sweet. Or use LEDs and blink out a code string into a light sensor. And like the RFID scheme, we could have individual keys for individual peoples.

Thoughts: Smart cards can offer some nice crypto, but they'd require the purchase of additional hardware ([http://www.smartcardsupply.com/Content/Hardware/AC-KIT.htm a kit]) and are more expensive than RFID (around $2.50)

Another idea I had, and kinda like, is to have a computer connected to the internet and a SIP provider (as [http://onlineapps.newsvine.com/_news/2008/05/02/1466218-land-of-the-freeware-making-and-receiving-free-phone-calls-via-any-computer-or-internet-enabled-device-with-grandcentral noted] repeatedly, you can get free inbound calls via Google [http://grandcentral.com/ GrandCentral]). When a call is received, it could listen for an access code (prepend a few digits for user id if desired) --[[User:NikolasCo|NikolasCo]] 09:27, 28 May 2008 (UTC)

how easy is it to forge phone number? because otherwise you could just have a database of member cellphones --[[phf]]

pretty easy with asterisk and a voip provider. --[[markw]]

== Well, you guys can use the "add a comment" button (i.e. the little + next to edit) ==

I know you were looking at a couple of options for the electronic door as of
the last dork bot, I found this part in passing on hackaday.com
http://www.smarthome.com/519012.html
I hope to make it down from baltimore soon!
-justin.

/ 
To answer Elliot's question:

I think the purpose is to provide an extensible level of access to our members, improve upon the trivial amount of security we currently have and finally to be creative and have fun designing "peripherals" to add onto our strike plate / logic controller setup we choose.

Justin: Thanks ! That's what I've been looking to pick-up. I'm just waiting for the mechanical portion to show up so I can install that and move onto the electronics.
-[[User:Q|Q]]
 
/

Talk:Physical Access Control Project

2008-07-01T21:19:50Z

'''Discussion: Physical Access Control Project'''

-----

I'm with you on the wiki-tard front, and not sure the "discussion" page is really all that good for discussions, being essentially a whiteboard. Anyone?

Andrew, thanks for cleaning this up and making the project look all professional-like. Feel free to delete any of the old material as you see fit. I wasn't sure what the tone of the project should be initially, and I took it fairly far in the unprofessional direction. I like what you've done with it better.

As for the logic layer in-between the card reader and electronic impeder/strikeplate/whatever, that should be fairly simple, depending on how much fun we decide to have with it. Myself, I'm for keeping it fairly open to allow multiple (amusing?) opening mechanisms in addition to the keycards, but that will necessarily reduce the security of the lock.

Are we building a fortress or just beefing up our current (minimal!) security?

(Elliot)

-----

''So i'm a wiki-tard, is there anyway to make these discussions threaded? Seems like it would make more sense''

''Added by Mark W, Thu, May 22, 2008:'' I think this is what you're looking for: [http://www.smarthome.com/5190s12.html Electric Door Strike]

Elliot demo'ed his knock-code routine and got some useful feedback. Things like ambient noise and a relatively-long timeout period need improvement.

Andrew suggested using a "Sonic Screwdriver" a la Doctor Who. This opens up all sorts of fun/funny code mechanisms. For instance, a keyfob with an ultrasonic speaker might be sweet. Or use LEDs and blink out a code string into a light sensor. And like the RFID scheme, we could have individual keys for individual peoples.

Thoughts: Smart cards can offer some nice crypto, but they'd require the purchase of additional hardware ([http://www.smartcardsupply.com/Content/Hardware/AC-KIT.htm a kit]) and are more expensive than RFID (around $2.50)

Another idea I had, and kinda like, is to have a computer connected to the internet and a SIP provider (as [http://onlineapps.newsvine.com/_news/2008/05/02/1466218-land-of-the-freeware-making-and-receiving-free-phone-calls-via-any-computer-or-internet-enabled-device-with-grandcentral noted] repeatedly, you can get free inbound calls via Google [http://grandcentral.com/ GrandCentral]). When a call is received, it could listen for an access code (prepend a few digits for user id if desired) --[[User:NikolasCo|NikolasCo]] 09:27, 28 May 2008 (UTC)

how easy is it to forge phone number? because otherwise you could just have a database of member cellphones --[[phf]]

pretty easy with asterisk and a voip provider. --[[markw]]

== Well, you guys can use the "add a comment" button (i.e. the little + next to edit) ==

I know you were looking at a couple of options for the electronic door as of
the last dork bot, I found this part in passing on hackaday.com
http://www.smarthome.com/519012.html
I hope to make it down from baltimore soon!
-justin.

To answer Elliot's question:

I think the purpose is to provide an extensible level of access to our members, improve upon the trivial amount of security we currently have and finally to be creative and have fun designing "peripherals" to add onto our strike plate / logic controller setup we choose.

Justin: Thanks ! That's what I've been looking to pick-up. I'm just waiting for the mechanical portion to show up so I can install that and move onto the electronics.
-[[User:Q|Q]]

Category:What I Stole

2008-07-01T21:18:08Z

<h2>Items Borrowed from the HacDC Space</h2>

June 19, 2008 - Tim Ball (timball@tux.org) / Richard Bewley (rbewley@gmail.com) - Not Returned / Outstanding 
- 1x Lineman's handset

June 30, 2008 - Q (andrew@i11industries.com) - 
- 1x Digital Multimeter (Yellow) 
Note: I will be returning this ASAP - I got my Fluke lab style DMM working great

<h2>Items Returned to the HacDC Space</h2>

Talk:Physical Access Control Project

2008-07-01T21:16:19Z

'''Discussion: Physical Access Control Project'''

-----

I'm with you on the wiki-tard front, and not sure the "discussion" page is really all that good for discussions, being essentially a whiteboard. Anyone?

Andrew, thanks for cleaning this up and making the project look all professional-like. Feel free to delete any of the old material as you see fit. I wasn't sure what the tone of the project should be initially, and I took it fairly far in the unprofessional direction. I like what you've done with it better.

As for the logic layer in-between the card reader and electronic impeder/strikeplate/whatever, that should be fairly simple, depending on how much fun we decide to have with it. Myself, I'm for keeping it fairly open to allow multiple (amusing?) opening mechanisms in addition to the keycards, but that will necessarily reduce the security of the lock.

Are we building a fortress or just beefing up our current (minimal!) security?

(Elliot)

-----

''So i'm a wiki-tard, is there anyway to make these discussions threaded? Seems like it would make more sense''

''Added by Mark W, Thu, May 22, 2008:'' I think this is what you're looking for: [http://www.smarthome.com/5190s12.html Electric Door Strike]

Elliot demo'ed his knock-code routine and got some useful feedback. Things like ambient noise and a relatively-long timeout period need improvement.

Andrew suggested using a "Sonic Screwdriver" a la Doctor Who. This opens up all sorts of fun/funny code mechanisms. For instance, a keyfob with an ultrasonic speaker might be sweet. Or use LEDs and blink out a code string into a light sensor. And like the RFID scheme, we could have individual keys for individual peoples.

Thoughts: Smart cards can offer some nice crypto, but they'd require the purchase of additional hardware ([http://www.smartcardsupply.com/Content/Hardware/AC-KIT.htm a kit]) and are more expensive than RFID (around $2.50)

Another idea I had, and kinda like, is to have a computer connected to the internet and a SIP provider (as [http://onlineapps.newsvine.com/_news/2008/05/02/1466218-land-of-the-freeware-making-and-receiving-free-phone-calls-via-any-computer-or-internet-enabled-device-with-grandcentral noted] repeatedly, you can get free inbound calls via Google [http://grandcentral.com/ GrandCentral]). When a call is received, it could listen for an access code (prepend a few digits for user id if desired) --[[User:NikolasCo|NikolasCo]] 09:27, 28 May 2008 (UTC)

how easy is it to forge phone number? because otherwise you could just have a database of member cellphones --[[phf]]

pretty easy with asterisk and a voip provider. --[[markw]]

== Well, you guys can use the "add a comment" button (i.e. the little + next to edit) ==

I know you were looking at a couple of options for the electronic door as of
the last dork bot, I found this part in passing on hackaday.com
http://www.smarthome.com/519012.html
I hope to make it down from baltimore soon!
-justin.

To answer Elliot's question:

I think the purpose is to provide an extensible level of access to our members, improve upon the trivial amount of security we currently have and finally to be creative and have fun designing "peripherals" to add onto our strike plate / logic controller setup we choose.

Justin: Thanks ! That's what I've been looking to pick-up. I'm just waiting for the mechanical portion to show up so I can install that and move onto the electronics.
--[[Q]]

Talk:Physical Access Control Project

2008-07-01T21:15:55Z

'''Discussion: Physical Access Control Project'''

-----

I'm with you on the wiki-tard front, and not sure the "discussion" page is really all that good for discussions, being essentially a whiteboard. Anyone?

Andrew, thanks for cleaning this up and making the project look all professional-like. Feel free to delete any of the old material as you see fit. I wasn't sure what the tone of the project should be initially, and I took it fairly far in the unprofessional direction. I like what you've done with it better.

As for the logic layer in-between the card reader and electronic impeder/strikeplate/whatever, that should be fairly simple, depending on how much fun we decide to have with it. Myself, I'm for keeping it fairly open to allow multiple (amusing?) opening mechanisms in addition to the keycards, but that will necessarily reduce the security of the lock.

Are we building a fortress or just beefing up our current (minimal!) security?

(Elliot)

-----

''So i'm a wiki-tard, is there anyway to make these discussions threaded? Seems like it would make more sense''

''Added by Mark W, Thu, May 22, 2008:'' I think this is what you're looking for: [http://www.smarthome.com/5190s12.html Electric Door Strike]

Elliot demo'ed his knock-code routine and got some useful feedback. Things like ambient noise and a relatively-long timeout period need improvement.

Andrew suggested using a "Sonic Screwdriver" a la Doctor Who. This opens up all sorts of fun/funny code mechanisms. For instance, a keyfob with an ultrasonic speaker might be sweet. Or use LEDs and blink out a code string into a light sensor. And like the RFID scheme, we could have individual keys for individual peoples.

Thoughts: Smart cards can offer some nice crypto, but they'd require the purchase of additional hardware ([http://www.smartcardsupply.com/Content/Hardware/AC-KIT.htm a kit]) and are more expensive than RFID (around $2.50)

Another idea I had, and kinda like, is to have a computer connected to the internet and a SIP provider (as [http://onlineapps.newsvine.com/_news/2008/05/02/1466218-land-of-the-freeware-making-and-receiving-free-phone-calls-via-any-computer-or-internet-enabled-device-with-grandcentral noted] repeatedly, you can get free inbound calls via Google [http://grandcentral.com/ GrandCentral]). When a call is received, it could listen for an access code (prepend a few digits for user id if desired) --[[User:NikolasCo|NikolasCo]] 09:27, 28 May 2008 (UTC)

how easy is it to forge phone number? because otherwise you could just have a database of member cellphones --[[phf]]

pretty easy with asterisk and a voip provider. --[[markw]]

== Well, you guys can use the "add a comment" button (i.e. the little + next to edit) ==

I know you were looking at a couple of options for the electronic door as of
the last dork bot, I found this part in passing on hackaday.com
http://www.smarthome.com/519012.html
I hope to make it down from baltimore soon!
-justin.

To answer Elliot's question:

I think the purpose is to provide an extensible level of access to our members, improve upon the trivial amount of security we currently have and finally to be creative and have fun designing "peripherals" to add onto our strike plate / logic controller setup we choose.

Justin: Thanks ! That's what I've been looking to pick-up. I'm just waiting for the mechanical portion to show up so I can install that and move onto the electronics.

(Andrew 'Q')

Talk:Physical Access Control Project

2008-07-01T21:15:17Z

'''Discussion: Physical Access Control Project'''

-----

I'm with you on the wiki-tard front, and not sure the "discussion" page is really all that good for discussions, being essentially a whiteboard. Anyone?

Andrew, thanks for cleaning this up and making the project look all professional-like. Feel free to delete any of the old material as you see fit. I wasn't sure what the tone of the project should be initially, and I took it fairly far in the unprofessional direction. I like what you've done with it better.

As for the logic layer in-between the card reader and electronic impeder/strikeplate/whatever, that should be fairly simple, depending on how much fun we decide to have with it. Myself, I'm for keeping it fairly open to allow multiple (amusing?) opening mechanisms in addition to the keycards, but that will necessarily reduce the security of the lock.

Are we building a fortress or just beefing up our current (minimal!) security?

(Elliot)

-----

''So i'm a wiki-tard, is there anyway to make these discussions threaded? Seems like it would make more sense''

''Added by Mark W, Thu, May 22, 2008:'' I think this is what you're looking for: [http://www.smarthome.com/5190s12.html Electric Door Strike]

Elliot demo'ed his knock-code routine and got some useful feedback. Things like ambient noise and a relatively-long timeout period need improvement.

Andrew suggested using a "Sonic Screwdriver" a la Doctor Who. This opens up all sorts of fun/funny code mechanisms. For instance, a keyfob with an ultrasonic speaker might be sweet. Or use LEDs and blink out a code string into a light sensor. And like the RFID scheme, we could have individual keys for individual peoples.

Thoughts: Smart cards can offer some nice crypto, but they'd require the purchase of additional hardware ([http://www.smartcardsupply.com/Content/Hardware/AC-KIT.htm a kit]) and are more expensive than RFID (around $2.50)

Another idea I had, and kinda like, is to have a computer connected to the internet and a SIP provider (as [http://onlineapps.newsvine.com/_news/2008/05/02/1466218-land-of-the-freeware-making-and-receiving-free-phone-calls-via-any-computer-or-internet-enabled-device-with-grandcentral noted] repeatedly, you can get free inbound calls via Google [http://grandcentral.com/ GrandCentral]). When a call is received, it could listen for an access code (prepend a few digits for user id if desired) --[[User:NikolasCo|NikolasCo]] 09:27, 28 May 2008 (UTC)

how easy is it to forge phone number? because otherwise you could just have a database of member cellphones --[[phf]]

pretty easy with asterisk and a voip provider. --[[markw]]

== Well, you guys can use the "add a comment" button (i.e. the little + next to edit) ==

I know you were looking at a couple of options for the electronic door as of
the last dork bot, I found this part in passing on hackaday.com
http://www.smarthome.com/519012.html
I hope to make it down from baltimore soon!
-justin.

To answer Elliot's question:

I think the purpose is to provide an extensible level of access to our members, improve upon the trivial amount of security we currently have and finally to be creative and have fun designing "peripherals" to add onto our strike plate / logic controller setup we choose.

Justin: Thanks ! That's what I've been looking to pick-up. I'm just waiting for the mechanical portion to show up so I can install that and move onto the electronics.

User:Q

2008-06-12T15:50:11Z

Q: /* Security Consultant Badass */

[[Category:Members]]

== Andrew Q Righter ==
=== Security Researcher ===

[[Image:Qlabs-photo1.jpg]]

Experience: 
o Website Development Level: Advanced Note: Really don't enjoy doing this stuff anymore
o Web Application Development Level: Intermediate Note: Don't enjoy doing this stuff anymore
o Graphic Design Level: Advanced Note: Don't enjoy doing this stuff anymore
o Digital Media Level: Intermediate Note: Don't enjoy doing this stuff anymore
o Programmer Level: Intermediate Note: Python and C seem to be the languages I use most
o Network Security Level: Intermediate Note: It's what pays the bills (most of them anyway)
o Electronic Engineering Level: Beginner Note: Been building kits forever, learning EE-level
o Machinist Level: Intermediate Note: Trying to get access to a machine shop in D.C.
o Reverse Engineering Level: Chicken Noob Note: Trying to get someone to teach a course on this subject.
o Wireless Hacker Level: Advanced Note: Will teach anyone how to pwnz the APz
o Lockpicker Level: Intermediate Note: Severely out-of-practice but I can still teach
o Electronic Security Level: Intermediate Note: Will be giving my Blackhat training at HacDC before/after
o Gamer Level: Advanced Note: Will teach anyone how to pwnz noobs
o Telco Level: Chicken Noob Note: Trying to get someone to teach me more
o HAM Dork Level: Chicken Noob Note: Trying to get someone to teach me more

OS Choice: 
o Linux (Slackware, Ubuntu)
o Mac (OSX)
o Windows (XP Professional)

Current Interests: 
o Hardware
o Tools
o Machining
o Building labs

Projects: 
o Physical Access Control Thingy
o MAME Cabinet Build
o Robotic Arm Development (Codename: Butterfingers)

Conferences: 
o '''HOPE 2006''' New York City, New York - TOOOL US lockpicking training
o '''Defcon 2007''' Las Vegas, Nevada - Wireless Village (setup | ran wireless hacking contest)
o '''Hack in the Box 2007''' Kuala Lumpur, Malaysia - Spoke about the insecurities of RFID
o '''HackCon 2008''' Oslo, Norway - Spoke on electronic security and DIY ideas for hobbyists
o '''Blackhat 2008''' Las Vegas, Nevada - Will be training students about electronic security exploits
o '''Hack in the Box 2008''' Kuala Lumpur, Malaysia - Will be training students about hacking the RF spectrum (802.11, RFID)

Talk:HacDC Museum

2008-06-12T15:49:37Z

Has anyone been to the Museum of Useful things in Cambridge? Unfortunately it's now closed, but it used to be a combined store and museum, with old and interesting gadgets displayed in cases and above head level around the store. It's the first thing that came to mind when Ben proposed a HacDC museum. The Museum of Useful Things still exists online, but primarily as a store. I couldn't find much on their site about the things in their collection, but there are a few pages ([http://themut.com/exhibits/2/ Example]).

One thing that I liked about the physical store is that they often displayed old and new versions of the same product (with the new version available to buy). For example, this [http://themut.com/zoomprod/product72/ staple-free stapler] was displayed under a model that looked more like one of [http://www.officemuseum.com/stapler_gallery_stapleless.htm these guys].

:Sounds like a really interesting concept. I'd love to aim for a more expansive display of artifacts, space permitting, and if the Museum is wildly successful, perhaps its own space someday in the distant future. The idea of a store is intriguing, as well. Perhaps as HacDC grows, there could be something akin to the [http://www.826valencia.org/ 826 Valencia] model, where a fun storefront (They have a Pirate Store, a superhero store, and a Bigfoot Research Institute) is the gateway to a spectacular hacking/teaching space and proceeds are used to subsidize the programs of HacDC. We're a long way from that, but it's something to consider. [[User:Ben|Ben]] 19:10, 11 June 2008 (UTC)

== Name Controversy ==

There's been some debate about whether to name the collection after our first large benefactor, and whether to identify objects in the collection as having been donated by certain individuals. A suggestion has been made by Derek Cooper to contact the benfactor's family to verify permission to use the name, but to avoid a potentially embarrassing situation, I think it would be wise to see if the group is in favor of naming a part of the collection after the benefactor before asking for permission.

Those '''in favor''' of naming the collection after the benefactor
* [[User:Ben|Ben]] 15:43, 12 June 2008 (UTC)
* [[User:Q|Q]] 11:49, 12 June 2008 (EST)

Those '''opposed''' to naming the collection after the benefactor

AVR Lesson: Setup

2008-06-12T14:40:55Z

The first step is to get set up with all the necessary hardware and software to start making your controllers do your bidding.

== Programmer ==

A programmer needn't be super-fancy. In fact, you can get by with five wires soldered to a parallel port plug if you'd like. [http://www.instructables.com/id/Ghetto-Programming%3a-Getting-started-with-AVR-micro/ This Instructable] steps through making a parallel port programmer. I'll probably make up a cable or two and bring it in to the space if you'd just like to try it out. Note that if you've got a breadboard, you can skip the step of making a programming cradle and just plug the wires into the correct pins on the AVR.

If you're getting a little more serious, spend $22 and get a [http://www.ladyada.net/make/usbtinyisp/ USB-based programmer from ladyada] or make your own [http://www.xs4all.nl/~dicks/avr/usbtiny/ usbtiny SPI programmer] for maybe $10-15ish. If you're making your own, you'll need to flash an AVR with the supplied firmware, but you can do that with a parallel port programmer or just ask one of us to hook you up.

This part may seem daunting -- it's not. Dive in or get someone to help you. The Ladyada kit is a good first/second soldering project.

== Software ==

The standard toolchain consists of a GCC-based C cross-compiler, the AVR-libc libraries, and the software to run your programmer: ''avrdude.'' Feel free to write the C or assembler code using whatever editor you like best.

For Windows, it's all put together nicely with [http://sourceforge.net/projects/winavr WinAVR]. Download and install. If you're using a parallel port programmer, you'll need to also run the included ''giveio.bat'' file to get yourself permissions.

For Linux, it's not that hard either. I'm most familiar with Ubuntu these days. As of 2008/04, "sudo apt-get install avrdude avr-libc binutils-avr gcc-avr" will set you up. Or fetch tarballs and compile it yourself. (I'll incluce versions here in a few.)

For Mac, I don't have a Mac. Is any of this [http://www.ladyada.net/learn/avr/setup-mac.html from Ladyada's site] useful?

'''MAC:''' 
Wanted to note something quick about my MAC experience so far (Q): I haven't really read the link to ada's site about programming AVR for MAC but 'AVRMacPack' is really cool! In OSX it's a simple .pkg file to install and drop into /Applications - then as long as you've installed XCode (that comes with macbook in the 2nd CD 'Developer Tools' section) they have this great little script in there called 'avr-project'. When you run this little badass piece of code it creates a DIR for your project called /FIRMWARE and three things:

An .xcodeproj file - this is a template (with skeleton code) for writing your program in Xcode

Makefile template which ROCKS - all you have to do after is change the DEVICE you're using along with PROGRAMMER and FUSES. (Will LINK my file here for reference email Q if i forget)

main.c file that is just a stupid simple C template to get you started

In addition to the compiler and programming software, it's nice to have an [[AVR Makefile]] that automates the cross-compilation build process. Comment in/out the first few defines to match your environment.

== Chips ==

So you're set to program, but you need a couple chips. [http://www.avrfreaks.net/index.php?module=Freaks%20Devices&func=viewDev This page at AVRFreaks] has some of the specs and all the datasheets in one place, but it's a bit overwhelming.

A shortlist of the coolest chips includes:

'''Tiny13''' -- Smallest and cheapest. 8 pins, 5 of them useful. 1k program memory. Goes everywhere. Cheaper and more versatile than a 555 IC. Some hardware SPI/I2C support, but it's a pain to write for.

'''Tiny45''' -- Another 8-pin, but with a high-speed PWM clock and 4k of program memory. ~$0.75 from Digikey. Can be made to run at 16MHz+ using its internal oscillator, making firmware USB a reality. Some hardware SPI/I2C support like the Tiny13.

'''Tiny2313''' -- 20 pins. It's the cheapest/smallest unit with > 5 usable pins. Hardware USART makes serial communication (e.g. with your computer) reasonably simple, which can be sweet for debugging or datalogging.

'''Mega 48''' -- 28 pins. All of the bells and whistles, with 4k program memory. 6 ADC channels, buncha timers, SPI/I2C/USART communications. They'll do what you want.

'''Mega 88, 168''' and beyond -- You're writing micro-controller code that requires 16k?!?! Time to learn assembler, parallel out your tasks to a couple chips, or step up to something like an ARM platform, IMO.

Maybe we could do a few group purchases to get up to Digikey's price-break minimums. Interested? E-mail Elliot.

And while you're at the AVRFreaks page, download both the long and short datasheets for whichever chips you end up buying. The short one has a nice pinout diagram on page two, while the long one explains everything you'll ever need to know.

== Misc. Extras ==

You're at least going to need some LED's to go blink. Pushbuttons are nice for playing around with inputs. Photocells give your creations sight. Motors and motor drivers give you legs. I'm sure there's more than enough scrounge around the space to get everyone started.

[http://www.instructables.com/id/Ghetto-Development-Environment This Instructable] details my current setup, and is a good start.

[[Category: AVR Tutorial]]

AVR Lesson: Setup

2008-06-12T14:40:06Z

The first step is to get set up with all the necessary hardware and software to start making your controllers do your bidding.

== Programmer ==

A programmer needn't be super-fancy. In fact, you can get by with five wires soldered to a parallel port plug if you'd like. [http://www.instructables.com/id/Ghetto-Programming%3a-Getting-started-with-AVR-micro/ This Instructable] steps through making a parallel port programmer. I'll probably make up a cable or two and bring it in to the space if you'd just like to try it out. Note that if you've got a breadboard, you can skip the step of making a programming cradle and just plug the wires into the correct pins on the AVR.

If you're getting a little more serious, spend $22 and get a [http://www.ladyada.net/make/usbtinyisp/ USB-based programmer from ladyada] or make your own [http://www.xs4all.nl/~dicks/avr/usbtiny/ usbtiny SPI programmer] for maybe $10-15ish. If you're making your own, you'll need to flash an AVR with the supplied firmware, but you can do that with a parallel port programmer or just ask one of us to hook you up.

This part may seem daunting -- it's not. Dive in or get someone to help you. The Ladyada kit is a good first/second soldering project.

== Software ==

The standard toolchain consists of a GCC-based C cross-compiler, the AVR-libc libraries, and the software to run your programmer: ''avrdude.'' Feel free to write the C or assembler code using whatever editor you like best.

For Windows, it's all put together nicely with [http://sourceforge.net/projects/winavr WinAVR]. Download and install. If you're using a parallel port programmer, you'll need to also run the included ''giveio.bat'' file to get yourself permissions.

For Linux, it's not that hard either. I'm most familiar with Ubuntu these days. As of 2008/04, "sudo apt-get install avrdude avr-libc binutils-avr gcc-avr" will set you up. Or fetch tarballs and compile it yourself. (I'll incluce versions here in a few.)

For Mac, I don't have a Mac. Is any of this [http://www.ladyada.net/learn/avr/setup-mac.html from Ladyada's site] useful?

'''MAC:''' 
Wanted to note something quick about my MAC experience so far (Q): I haven't really read the link to ada's site about programming AVR for MAC but 'AVRMacPack' is really cool! In OSX it's a simple .pkg file to install and drop into /Applications - then as long as you've installed XCode (that comes with macbook in the 2nd CD 'Developer Tools' section) they have this great little script in there called 'avr-project'. When you run this little badass piece of code it creates a DIR for your project called /FIRMWARE and three things:

An .xcodeproj file - this is a template (with skeleton code) for writing your program in Xcode

Makefile template which ROCKS - all you have to do after is change the DEVICE you're using along with PROGRAMMER and FUSES. (Will LINK my file here for reference ''email Q if i forget)''

main.c file that is just a stupid simple C template to get you started

In addition to the compiler and programming software, it's nice to have an [[AVR Makefile]] that automates the cross-compilation build process. Comment in/out the first few defines to match your environment.

== Chips ==

So you're set to program, but you need a couple chips. [http://www.avrfreaks.net/index.php?module=Freaks%20Devices&func=viewDev This page at AVRFreaks] has some of the specs and all the datasheets in one place, but it's a bit overwhelming.

A shortlist of the coolest chips includes:

'''Tiny13''' -- Smallest and cheapest. 8 pins, 5 of them useful. 1k program memory. Goes everywhere. Cheaper and more versatile than a 555 IC. Some hardware SPI/I2C support, but it's a pain to write for.

'''Tiny45''' -- Another 8-pin, but with a high-speed PWM clock and 4k of program memory. ~$0.75 from Digikey. Can be made to run at 16MHz+ using its internal oscillator, making firmware USB a reality. Some hardware SPI/I2C support like the Tiny13.

'''Tiny2313''' -- 20 pins. It's the cheapest/smallest unit with > 5 usable pins. Hardware USART makes serial communication (e.g. with your computer) reasonably simple, which can be sweet for debugging or datalogging.

'''Mega 48''' -- 28 pins. All of the bells and whistles, with 4k program memory. 6 ADC channels, buncha timers, SPI/I2C/USART communications. They'll do what you want.

'''Mega 88, 168''' and beyond -- You're writing micro-controller code that requires 16k?!?! Time to learn assembler, parallel out your tasks to a couple chips, or step up to something like an ARM platform, IMO.

Maybe we could do a few group purchases to get up to Digikey's price-break minimums. Interested? E-mail Elliot.

And while you're at the AVRFreaks page, download both the long and short datasheets for whichever chips you end up buying. The short one has a nice pinout diagram on page two, while the long one explains everything you'll ever need to know.

== Misc. Extras ==

You're at least going to need some LED's to go blink. Pushbuttons are nice for playing around with inputs. Photocells give your creations sight. Motors and motor drivers give you legs. I'm sure there's more than enough scrounge around the space to get everyone started.

[http://www.instructables.com/id/Ghetto-Development-Environment This Instructable] details my current setup, and is a good start.

[[Category: AVR Tutorial]]

AVR Lesson: Setup

2008-06-12T14:39:18Z

The first step is to get set up with all the necessary hardware and software to start making your controllers do your bidding.

== Programmer ==

A programmer needn't be super-fancy. In fact, you can get by with five wires soldered to a parallel port plug if you'd like. [http://www.instructables.com/id/Ghetto-Programming%3a-Getting-started-with-AVR-micro/ This Instructable] steps through making a parallel port programmer. I'll probably make up a cable or two and bring it in to the space if you'd just like to try it out. Note that if you've got a breadboard, you can skip the step of making a programming cradle and just plug the wires into the correct pins on the AVR.

If you're getting a little more serious, spend $22 and get a [http://www.ladyada.net/make/usbtinyisp/ USB-based programmer from ladyada] or make your own [http://www.xs4all.nl/~dicks/avr/usbtiny/ usbtiny SPI programmer] for maybe $10-15ish. If you're making your own, you'll need to flash an AVR with the supplied firmware, but you can do that with a parallel port programmer or just ask one of us to hook you up.

This part may seem daunting -- it's not. Dive in or get someone to help you. The Ladyada kit is a good first/second soldering project.

== Software ==

The standard toolchain consists of a GCC-based C cross-compiler, the AVR-libc libraries, and the software to run your programmer: ''avrdude.'' Feel free to write the C or assembler code using whatever editor you like best.

For Windows, it's all put together nicely with [http://sourceforge.net/projects/winavr WinAVR]. Download and install. If you're using a parallel port programmer, you'll need to also run the included ''giveio.bat'' file to get yourself permissions.

For Linux, it's not that hard either. I'm most familiar with Ubuntu these days. As of 2008/04, "sudo apt-get install avrdude avr-libc binutils-avr gcc-avr" will set you up. Or fetch tarballs and compile it yourself. (I'll incluce versions here in a few.)

For Mac, I don't have a Mac. Is any of this [http://www.ladyada.net/learn/avr/setup-mac.html from Ladyada's site] useful?

'''MAC:''' 
Wanted to note something quick about my MAC experience so far (Q): I haven't really read the link to ada's site about programming AVR for MAC but 'AVRMacPack' is really cool! In OSX it's a simple .pkg file to install and drop into /Applications - then as long as you've installed XCode (that comes with macbook in the 2nd CD 'Developer Tools' section) they have this great little script in there called 'avr-project'. When you run this little badass piece of code it creates a DIR for your project called /FIRMWARE and three things:

An .xcodeproj file - this is a template (with skeleton code) for writing your program in Xcode

Makefile template which ROCKS - all you have to do after is change the DEVICE you're using along with PROGRAMMER and FUSES. (Will LINK my file here for reference - email Q if i forget)

main.c file that is just a stupid simple C template to get you started

In addition to the compiler and programming software, it's nice to have an [[AVR Makefile]] that automates the cross-compilation build process. Comment in/out the first few defines to match your environment.

== Chips ==

So you're set to program, but you need a couple chips. [http://www.avrfreaks.net/index.php?module=Freaks%20Devices&func=viewDev This page at AVRFreaks] has some of the specs and all the datasheets in one place, but it's a bit overwhelming.

A shortlist of the coolest chips includes:

'''Tiny13''' -- Smallest and cheapest. 8 pins, 5 of them useful. 1k program memory. Goes everywhere. Cheaper and more versatile than a 555 IC. Some hardware SPI/I2C support, but it's a pain to write for.

'''Tiny45''' -- Another 8-pin, but with a high-speed PWM clock and 4k of program memory. ~$0.75 from Digikey. Can be made to run at 16MHz+ using its internal oscillator, making firmware USB a reality. Some hardware SPI/I2C support like the Tiny13.

'''Tiny2313''' -- 20 pins. It's the cheapest/smallest unit with > 5 usable pins. Hardware USART makes serial communication (e.g. with your computer) reasonably simple, which can be sweet for debugging or datalogging.

'''Mega 48''' -- 28 pins. All of the bells and whistles, with 4k program memory. 6 ADC channels, buncha timers, SPI/I2C/USART communications. They'll do what you want.

'''Mega 88, 168''' and beyond -- You're writing micro-controller code that requires 16k?!?! Time to learn assembler, parallel out your tasks to a couple chips, or step up to something like an ARM platform, IMO.

Maybe we could do a few group purchases to get up to Digikey's price-break minimums. Interested? E-mail Elliot.

And while you're at the AVRFreaks page, download both the long and short datasheets for whichever chips you end up buying. The short one has a nice pinout diagram on page two, while the long one explains everything you'll ever need to know.

== Misc. Extras ==

You're at least going to need some LED's to go blink. Pushbuttons are nice for playing around with inputs. Photocells give your creations sight. Motors and motor drivers give you legs. I'm sure there's more than enough scrounge around the space to get everyone started.

[http://www.instructables.com/id/Ghetto-Development-Environment This Instructable] details my current setup, and is a good start.

[[Category: AVR Tutorial]]

AVR Lesson: Setup

2008-06-12T14:36:22Z

The first step is to get set up with all the necessary hardware and software to start making your controllers do your bidding.

== Programmer ==

A programmer needn't be super-fancy. In fact, you can get by with five wires soldered to a parallel port plug if you'd like. [http://www.instructables.com/id/Ghetto-Programming%3a-Getting-started-with-AVR-micro/ This Instructable] steps through making a parallel port programmer. I'll probably make up a cable or two and bring it in to the space if you'd just like to try it out. Note that if you've got a breadboard, you can skip the step of making a programming cradle and just plug the wires into the correct pins on the AVR.

If you're getting a little more serious, spend $22 and get a [http://www.ladyada.net/make/usbtinyisp/ USB-based programmer from ladyada] or make your own [http://www.xs4all.nl/~dicks/avr/usbtiny/ usbtiny SPI programmer] for maybe $10-15ish. If you're making your own, you'll need to flash an AVR with the supplied firmware, but you can do that with a parallel port programmer or just ask one of us to hook you up.

This part may seem daunting -- it's not. Dive in or get someone to help you. The Ladyada kit is a good first/second soldering project.

== Software ==

The standard toolchain consists of a GCC-based C cross-compiler, the AVR-libc libraries, and the software to run your programmer: ''avrdude.'' Feel free to write the C or assembler code using whatever editor you like best.

For Windows, it's all put together nicely with [http://sourceforge.net/projects/winavr WinAVR]. Download and install. If you're using a parallel port programmer, you'll need to also run the included ''giveio.bat'' file to get yourself permissions.

For Linux, it's not that hard either. I'm most familiar with Ubuntu these days. As of 2008/04, "sudo apt-get install avrdude avr-libc binutils-avr gcc-avr" will set you up. Or fetch tarballs and compile it yourself. (I'll incluce versions here in a few.)

For Mac, I don't have a Mac. Is any of this [http://www.ladyada.net/learn/avr/setup-mac.html from Ladyada's site] useful?

'''MAC:''' 
Wanted to note something quick about my MAC experience so far (Q): I haven't really read the link to ada's site about programming AVR for MAC but 'AVRMacPack' is really cool! In OSX it's a simple .pkg file to install and drop into /Applications - then as long as you've installed XCode (that comes with macbook in the 2nd CD 'Developer Tools' section) they have this great little script in there called 'avr-project'. When you run this little badass piece of code it creates a DIR for your project called /FIRMWARE and three things:

An .xcodeproj file - this is a template (with skeleton code) for writing your program in Xcode

Makefile template which ROCKS - all you have to do after is change the DEVICE you're using along with PROGRAMMER and FUSES. (Will LINK my file here for reference - email Q if i forget)

main.c file that is just a stupid simple C template to get you started

In addition to the compiler and programming software, it's nice to have an [[AVR Makefile]] that automates the cross-compilation build process. Comment in/out the first few defines to match your environment.

== Chips ==

So you're set to program, but you need a couple chips. [http://www.avrfreaks.net/index.php?module=Freaks%20Devices&func=viewDev This page at AVRFreaks] has some of the specs and all the datasheets in one place, but it's a bit overwhelming.

A shortlist of the coolest chips includes:

'''Tiny13''' -- Smallest and cheapest. 8 pins, 5 of them useful. 1k program memory. Goes everywhere. Cheaper and more versatile than a 555 IC. Some hardware SPI/I2C support, but it's a pain to write for.

'''Tiny45''' -- Another 8-pin, but with a high-speed PWM clock and 4k of program memory. ~$0.75 from Digikey. Can be made to run at 16MHz+ using its internal oscillator, making firmware USB a reality. Some hardware SPI/I2C support like the Tiny13.

'''Tiny2313''' -- 20 pins. It's the cheapest/smallest unit with > 5 usable pins. Hardware USART makes serial communication (e.g. with your computer) reasonably simple, which can be sweet for debugging or datalogging.

'''Mega 48''' -- 28 pins. All of the bells and whistles, with 4k program memory. 6 ADC channels, buncha timers, SPI/I2C/USART communications. They'll do what you want.

'''Mega 88, 168''' and beyond -- You're writing micro-controller code that requires 16k?!?! Time to learn assembler, parallel out your tasks to a couple chips, or step up to something like an ARM platform, IMO.

Maybe we could do a few group purchases to get up to Digikey's price-break minimums. Interested? E-mail Elliot.

And while you're at the AVRFreaks page, download both the long and short datasheets for whichever chips you end up buying. The short one has a nice pinout diagram on page two, while the long one explains everything you'll ever need to know.

== Misc. Extras ==

You're at least going to need some LED's to go blink. Pushbuttons are nice for playing around with inputs. Photocells give your creations sight. Motors and motor drivers give you legs. I'm sure there's more than enough scrounge around the space to get everyone started.

[http://www.instructables.com/id/Ghetto-Development-Environment This Instructable] details my current setup, and is a good start.

[[Category: AVR Tutorial]]

AVR Lesson: Setup

2008-06-12T14:34:21Z

The first step is to get set up with all the necessary hardware and software to start making your controllers do your bidding.

== Programmer ==

A programmer needn't be super-fancy. In fact, you can get by with five wires soldered to a parallel port plug if you'd like. [http://www.instructables.com/id/Ghetto-Programming%3a-Getting-started-with-AVR-micro/ This Instructable] steps through making a parallel port programmer. I'll probably make up a cable or two and bring it in to the space if you'd just like to try it out. Note that if you've got a breadboard, you can skip the step of making a programming cradle and just plug the wires into the correct pins on the AVR.

If you're getting a little more serious, spend $22 and get a [http://www.ladyada.net/make/usbtinyisp/ USB-based programmer from ladyada] or make your own [http://www.xs4all.nl/~dicks/avr/usbtiny/ usbtiny SPI programmer] for maybe $10-15ish. If you're making your own, you'll need to flash an AVR with the supplied firmware, but you can do that with a parallel port programmer or just ask one of us to hook you up.

This part may seem daunting -- it's not. Dive in or get someone to help you. The Ladyada kit is a good first/second soldering project.

== Software ==

The standard toolchain consists of a GCC-based C cross-compiler, the AVR-libc libraries, and the software to run your programmer: ''avrdude.'' Feel free to write the C or assembler code using whatever editor you like best.

For Windows, it's all put together nicely with [http://sourceforge.net/projects/winavr WinAVR]. Download and install. If you're using a parallel port programmer, you'll need to also run the included ''giveio.bat'' file to get yourself permissions.

For Linux, it's not that hard either. I'm most familiar with Ubuntu these days. As of 2008/04, "sudo apt-get install avrdude avr-libc binutils-avr gcc-avr" will set you up. Or fetch tarballs and compile it yourself. (I'll incluce versions here in a few.)

For Mac, I don't have a Mac. Is any of this [http://www.ladyada.net/learn/avr/setup-mac.html from Ladyada's site] useful?

'''MAC:''' 
Wanted to note something quick about my MAC experience so far (Q): I haven't really read the link to ada's site about programming AVR for MAC but 'AVRMacPack' is really cool! In OSX it's a simple .pkg file to install and drop into /Applications - then as long as you've installed XCode (that comes with macbook in the 2nd CD 'Developer Tools' section) they have this great little script in there called 'avr-project'. When you run this little badass piece of code it creates a DIR for your project called /FIRMWARE and two files:

Makefile template which ROCKS - all you have to do after is change the DEVICE you're using along with PROGRAMMER and FUSES.

main.c file that is just a stupid simple C template to get you started

In addition to the compiler and programming software, it's nice to have an [[AVR Makefile]] that automates the cross-compilation build process. Comment in/out the first few defines to match your environment.

== Chips ==

So you're set to program, but you need a couple chips. [http://www.avrfreaks.net/index.php?module=Freaks%20Devices&func=viewDev This page at AVRFreaks] has some of the specs and all the datasheets in one place, but it's a bit overwhelming.

A shortlist of the coolest chips includes:

'''Tiny13''' -- Smallest and cheapest. 8 pins, 5 of them useful. 1k program memory. Goes everywhere. Cheaper and more versatile than a 555 IC. Some hardware SPI/I2C support, but it's a pain to write for.

'''Tiny45''' -- Another 8-pin, but with a high-speed PWM clock and 4k of program memory. ~$0.75 from Digikey. Can be made to run at 16MHz+ using its internal oscillator, making firmware USB a reality. Some hardware SPI/I2C support like the Tiny13.

'''Tiny2313''' -- 20 pins. It's the cheapest/smallest unit with > 5 usable pins. Hardware USART makes serial communication (e.g. with your computer) reasonably simple, which can be sweet for debugging or datalogging.

'''Mega 48''' -- 28 pins. All of the bells and whistles, with 4k program memory. 6 ADC channels, buncha timers, SPI/I2C/USART communications. They'll do what you want.

'''Mega 88, 168''' and beyond -- You're writing micro-controller code that requires 16k?!?! Time to learn assembler, parallel out your tasks to a couple chips, or step up to something like an ARM platform, IMO.

Maybe we could do a few group purchases to get up to Digikey's price-break minimums. Interested? E-mail Elliot.

And while you're at the AVRFreaks page, download both the long and short datasheets for whichever chips you end up buying. The short one has a nice pinout diagram on page two, while the long one explains everything you'll ever need to know.

== Misc. Extras ==

You're at least going to need some LED's to go blink. Pushbuttons are nice for playing around with inputs. Photocells give your creations sight. Motors and motor drivers give you legs. I'm sure there's more than enough scrounge around the space to get everyone started.

[http://www.instructables.com/id/Ghetto-Development-Environment This Instructable] details my current setup, and is a good start.

[[Category: AVR Tutorial]]

AVR Lesson: Setup

2008-06-12T14:33:24Z

The first step is to get set up with all the necessary hardware and software to start making your controllers do your bidding.

== Programmer ==

A programmer needn't be super-fancy. In fact, you can get by with five wires soldered to a parallel port plug if you'd like. [http://www.instructables.com/id/Ghetto-Programming%3a-Getting-started-with-AVR-micro/ This Instructable] steps through making a parallel port programmer. I'll probably make up a cable or two and bring it in to the space if you'd just like to try it out. Note that if you've got a breadboard, you can skip the step of making a programming cradle and just plug the wires into the correct pins on the AVR.

If you're getting a little more serious, spend $22 and get a [http://www.ladyada.net/make/usbtinyisp/ USB-based programmer from ladyada] or make your own [http://www.xs4all.nl/~dicks/avr/usbtiny/ usbtiny SPI programmer] for maybe $10-15ish. If you're making your own, you'll need to flash an AVR with the supplied firmware, but you can do that with a parallel port programmer or just ask one of us to hook you up.

This part may seem daunting -- it's not. Dive in or get someone to help you. The Ladyada kit is a good first/second soldering project.

== Software ==

The standard toolchain consists of a GCC-based C cross-compiler, the AVR-libc libraries, and the software to run your programmer: ''avrdude.'' Feel free to write the C or assembler code using whatever editor you like best.

For Windows, it's all put together nicely with [http://sourceforge.net/projects/winavr WinAVR]. Download and install. If you're using a parallel port programmer, you'll need to also run the included ''giveio.bat'' file to get yourself permissions.

For Linux, it's not that hard either. I'm most familiar with Ubuntu these days. As of 2008/04, "sudo apt-get install avrdude avr-libc binutils-avr gcc-avr" will set you up. Or fetch tarballs and compile it yourself. (I'll incluce versions here in a few.)

For Mac, I don't have a Mac. Is any of this [http://www.ladyada.net/learn/avr/setup-mac.html from Ladyada's site] useful?

Wanted to note something quick about my MAC experience so far (Q): I haven't really read the link to ada's site about programming AVR for MAC but 'AVRMacPack' is really cool! In OSX it's a simple .pkg file to install and drop into /Applications - then as long as you've installed XCode (that comes with macbook in the 2nd CD 'Developer Tools' section) they have this great little script in there called 'avr-project'. When you run this little badass piece of code it creates a DIR for your project called /FIRMWARE and two files:

A Makefile template which ROCKS - all you have to do after is change the DEVICE you're using along with PROGRAMMER and FUSES.

A main.c file that is just a stupid simple C template to get you started

In addition to the compiler and programming software, it's nice to have an [[AVR Makefile]] that automates the cross-compilation build process. Comment in/out the first few defines to match your environment.

== Chips ==

So you're set to program, but you need a couple chips. [http://www.avrfreaks.net/index.php?module=Freaks%20Devices&func=viewDev This page at AVRFreaks] has some of the specs and all the datasheets in one place, but it's a bit overwhelming.

A shortlist of the coolest chips includes:

'''Tiny13''' -- Smallest and cheapest. 8 pins, 5 of them useful. 1k program memory. Goes everywhere. Cheaper and more versatile than a 555 IC. Some hardware SPI/I2C support, but it's a pain to write for.

'''Tiny45''' -- Another 8-pin, but with a high-speed PWM clock and 4k of program memory. ~$0.75 from Digikey. Can be made to run at 16MHz+ using its internal oscillator, making firmware USB a reality. Some hardware SPI/I2C support like the Tiny13.

'''Tiny2313''' -- 20 pins. It's the cheapest/smallest unit with > 5 usable pins. Hardware USART makes serial communication (e.g. with your computer) reasonably simple, which can be sweet for debugging or datalogging.

'''Mega 48''' -- 28 pins. All of the bells and whistles, with 4k program memory. 6 ADC channels, buncha timers, SPI/I2C/USART communications. They'll do what you want.

'''Mega 88, 168''' and beyond -- You're writing micro-controller code that requires 16k?!?! Time to learn assembler, parallel out your tasks to a couple chips, or step up to something like an ARM platform, IMO.

Maybe we could do a few group purchases to get up to Digikey's price-break minimums. Interested? E-mail Elliot.

And while you're at the AVRFreaks page, download both the long and short datasheets for whichever chips you end up buying. The short one has a nice pinout diagram on page two, while the long one explains everything you'll ever need to know.

== Misc. Extras ==

You're at least going to need some LED's to go blink. Pushbuttons are nice for playing around with inputs. Photocells give your creations sight. Motors and motor drivers give you legs. I'm sure there's more than enough scrounge around the space to get everyone started.

[http://www.instructables.com/id/Ghetto-Development-Environment This Instructable] details my current setup, and is a good start.

[[Category: AVR Tutorial]]

Category:Heroes

2008-06-11T20:47:11Z

== Artists ==
Leonardo DaVinci

== Authors ==
Neal Stephenson

Carl Sagan

Philip K. Dick

Stanislaw Lem

Cory Doctorow

Terry Goodkind

== Composers ==
Wolfgang Amadeus Mozart

== Philosophers ==
Marshall McLuhan

== Scientists ==
Richard Feynman

Brian Greene

Albert Einstein

Category:Heroes

2008-06-11T20:46:38Z

== Artists ==
Leonardo DaVinci

== Authors ==
Neal Stephenson
Carl Sagan
Philip K. Dick
Stanislaw Lem
Cory Doctorow
Terry Goodkind

== Composers ==
Wolfgang Amadeus Mozart

== Philosophers ==
Marshall McLuhan

== Scientists ==
Richard Feynman
Brian Greene
Albert Einstein

Physical Access Control Project

2008-06-11T17:45:54Z

[[Category:Projects]]
[[Category:Ongoing Projects]]
[[Category:Umbrella Projects]]

'''Project Lead: [http://wiki.hacdc.org/index.php?title=User:Q Q]''' 
'''Current Members: [[Elliot]], [[Nathan]] and [[Ash]]'''

'''Proposed Budget: $500.00'''

'''Status:''' 
o Ordered Medeco M3 cylinder (with tail piece) and 5 keys

'''Abstract''' 
The access control project, which has had many names over the past few weeks of its existence, is a project with two main goals in mind. The security of our space and the convenience of entry for all of our members. The project has been developed into two stages and contains the first stage of a revitalization of the mechanical locking mechanisms currently being used as well as an enhancement to the door frame and its underlying structure and the second stage being the development of a brand new electronic security system with improved access control.

''If you would like to add ideas please do so on the DISCUSSION page, if you are a member of this project feel free to add to this page.''

Stage One:
o Using longer, stronger screws in the door's frame to enhance the structural integrity
o Replacing the crappy core cylinder that is currently in there with a new Medeco M3 series rim/mortise cylinder
o Reinforcing the hinges and making sure they are all strong enough to handle a kick by the feds (joke, please no emails)
o Either buying a new door knob or fixing the internals of the current, it was possible to lock yourself in when we first arrived.

Stage Two:
o Implementing a smart card reader system (contacted)
o Installing the impeding mechanism
o We may need a circuit in the middle of the impeding mechanism and the card reader to do perform some logic
It depends on how the reader we buy is setup, if there are usable pins on the unit we could piggy-back
a connector and setup a small circuit (diode and tiny IC) to supply voltage to the impeding mechanism when
user_card = accepted;
o Writing all the access cards for members
o Developing a PAX system for the backend to log entry data and control users access (helpful for janitor access)
o Use the PAX system to develop alerts that can be broadcast over TCP

'''Wed, May 14, 2008:''' 
Andrew ("Q"), Ash, and Elliot have continued brainstorming. Posted up a link on the blog [http://hacdc.org/2008/05/14/door-unlockerator-project/] to discuss ways to go. Great suggestion (though it might have been a (brilliant) joke?) to make a DDR pad. Elliot's been messing around with the [[Parallax RFID board]], and learning what it can/can't do, but he's terribly terribly new to RF stuff.

'''Wed, June 5, 2008''' 
So last night at open lab I disassembled the current locking mechanics and made sure everything would work when buying a regular mortise cylinder core from Medeco. Everything looks good to go, I think I'm going to use the existing backplate which should be fine as long as we get a tail on our new core. The door knob and internals are still really flaky, but they really aren't even necessary at this point. With the new core, (Medeco 10 series) we will have sufficient security and it will be 100x better than our current locks. -Q

Physical Access Control Project

2008-06-11T17:44:46Z

[[Category:Projects]]
[[Category:Ongoing Projects]]
[[Category:Umbrella Projects]]

'''Project Lead: [http://wiki.hacdc.org/index.php?title=User:Q Q]''' 
'''Current Members: [[Elliot]], [[Nathan]] and [[Ash]]'''

'''Proposed Budget: $500.00'''

'''Abstract''' 
The access control project, which has had many names over the past few weeks of its existence, is a project with two main goals in mind. The security of our space and the convenience of entry for all of our members. The project has been developed into two stages and contains the first stage of a revitalization of the mechanical locking mechanisms currently being used as well as an enhancement to the door frame and its underlying structure and the second stage being the development of a brand new electronic security system with improved access control.

''If you would like to add ideas please do so on the DISCUSSION page, if you are a member of this project feel free to add to this page.''

Stage One:
o Using longer, stronger screws in the door's frame to enhance the structural integrity
o Replacing the crappy core cylinder that is currently in there with a new Medeco M3 series rim/mortise cylinder
o Reinforcing the hinges and making sure they are all strong enough to handle a kick by the feds (joke, please no emails)
o Either buying a new door knob or fixing the internals of the current, it was possible to lock yourself in when we first arrived.

Stage Two:
o Implementing a smart card reader system (contacted)
o Installing the impeding mechanism
o We may need a circuit in the middle of the impeding mechanism and the card reader to do perform some logic
It depends on how the reader we buy is setup, if there are usable pins on the unit we could piggy-back
a connector and setup a small circuit (diode and tiny IC) to supply voltage to the impeding mechanism when
user_card = accepted;
o Writing all the access cards for members
o Developing a PAX system for the backend to log entry data and control users access (helpful for janitor access)
o Use the PAX system to develop alerts that can be broadcast over TCP

'''Wed, May 14, 2008:''' 
Andrew ("Q"), Ash, and Elliot have continued brainstorming. Posted up a link on the blog [http://hacdc.org/2008/05/14/door-unlockerator-project/] to discuss ways to go. Great suggestion (though it might have been a (brilliant) joke?) to make a DDR pad. Elliot's been messing around with the [[Parallax RFID board]], and learning what it can/can't do, but he's terribly terribly new to RF stuff.

'''Wed, June 5, 2008''' 
So last night at open lab I disassembled the current locking mechanics and made sure everything would work when buying a regular mortise cylinder core from Medeco. Everything looks good to go, I think I'm going to use the existing backplate which should be fine as long as we get a tail on our new core. The door knob and internals are still really flaky, but they really aren't even necessary at this point. With the new core, (Medeco 10 series) we will have sufficient security and it will be 100x better than our current locks. -Q

Wishlist

2008-06-08T00:07:41Z

'''Our most urgent need currently is for bins, boxes, and shelving! Please see below.'''

We're always on the lookout for donations. Put what you've got to good use! Donate it to HacDC!

E-mail [mailto:info@hacdc.org info@hacdc.org] if you have questions about specific items that do not appear here, or to arrange specific donation times. Otherwise, please stop by any of our public events with your donations!

== Equipment ==

=== Power Tools ===
* <s>Circular saw</s>
* Soldering Irons
* <s>3/8" VSR Drill (in good working order plzkthx!)</s>
* Shop-Vac accessories
* Dust-collector type equipment for woodworking

=== Hand Tools ===
* Screwdrivers
* Hammers
* Pliers
* Saw, sharp
* Chisels

=== Test Equipment ===
Note: Test equipment that pushes data via USB or Serial to a computer is preferred.

* Spectrum Analyzer
* Oscilloscope
* [[http://www.google.com/products?hl=en&q=pc%20cable%20tester PC cable tester]]
* Cat-5 tester that detects split pairs
* Infrared thermometer
* Thermal camera (hey, we can dream!)
* USB protocol analyzer (as above!)
* EPROM programmer, and oodles of socket adapters and test clips

=== Other ===
* Variable-output power supply
* Electron Microscope
* Wifi Unidapt Kit
* Regular Unidapt kit

=== Furniture ===
* Any wheeled shelving or carts with dimensions smaller than (32"Hx64"WX30"D). This will fit under our tables.
* Any tall shelving, approx 24-36"Wx18"Dx72"H. Taller is fine. Target has wire shelving, 5 tiers, 36x18x72, for $30 but they're out of stock.
* Plastic bins, boxes, trays, the sturdier the better. Clear?
* Dry-erase board (we might build this ourselves)
* Pull-down movie screen (as above)
* Comfortable Chairs (Office or other)

== Parts & Supplies ==
* Audio Cables
* <s>Ethernet Cables</s> (very funny! we're swimming in 'em!)
* Radio Parts
* Power Cables
* Power Converters/Chargers
* Plastic baggies (small zipper, not food-grade)
* Wall-hung cabinet with a zillion tiny clear plastic drawers
* Rubber bands
* Markers
* Dry-erase markers

User:Q

2008-06-05T20:12:38Z

[[Category:Members]]

== Andrew Q Righter ==
=== Security Consultant Badass ===

[[Image:Qlabs-photo1.jpg]]

Experience: 
o Website Development Level: Advanced Note: Really don't enjoy doing this stuff anymore
o Web Application Development Level: Intermediate Note: Don't enjoy doing this stuff anymore
o Graphic Design Level: Advanced Note: Don't enjoy doing this stuff anymore
o Digital Media Level: Intermediate Note: Don't enjoy doing this stuff anymore
o Programmer Level: Intermediate Note: Python and C seem to be the languages I use most
o Network Security Level: Intermediate Note: It's what pays the bills (most of them anyway)
o Electronic Engineering Level: Beginner Note: Been building kits forever, learning EE-level
o Machinist Level: Intermediate Note: Trying to get access to a machine shop in D.C.
o Reverse Engineering Level: Chicken Noob Note: Trying to get someone to teach a course on this subject.
o Wireless Hacker Level: Advanced Note: Will teach anyone how to pwnz the APz
o Lockpicker Level: Intermediate Note: Severely out-of-practice but I can still teach
o Electronic Security Level: Intermediate Note: Will be giving my Blackhat training at HacDC before/after
o Gamer Level: Advanced Note: Will teach anyone how to pwnz noobs
o Telco Level: Chicken Noob Note: Trying to get someone to teach me more
o HAM Dork Level: Chicken Noob Note: Trying to get someone to teach me more

OS Choice: 
o Linux (Slackware, Ubuntu)
o Mac (OSX)
o Windows (XP Professional)

Current Interests: 
o Hardware
o Tools
o Machining
o Building labs

Projects: 
o Physical Access Control Thingy
o MAME Cabinet Build
o Robotic Arm Development (Codename: Butterfingers)

Conferences: 
o '''HOPE 2006''' New York City, New York - TOOOL US lockpicking training
o '''Defcon 2007''' Las Vegas, Nevada - Wireless Village (setup | ran wireless hacking contest)
o '''Hack in the Box 2007''' Kuala Lumpur, Malaysia - Spoke about the insecurities of RFID
o '''HackCon 2008''' Oslo, Norway - Spoke on electronic security and DIY ideas for hobbyists
o '''Blackhat 2008''' Las Vegas, Nevada - Will be training students about electronic security exploits
o '''Hack in the Box 2008''' Kuala Lumpur, Malaysia - Will be training students about hacking the RF spectrum (802.11, RFID)

User:Q

2008-06-05T19:12:41Z

[[Category:Members]]

== Andrew Q Righter ==
=== Security Consultant Badass ===

[[Image:Qlabs-photo1.jpg]]

Experience: 
o Website Development Level: Advanced Note: Really don't enjoy doing this stuff anymore
o Web Application Development Level: Intermediate Note: Don't enjoy doing this stuff anymore
o Graphic Design Level: Advanced Note: Don't enjoy doing this stuff anymore
o Digital Media Level: Intermediate Note: Don't enjoy doing this stuff anymore
o Programmer Level: Intermediate Note: Python and C seem to be the languages I use most
o Network Security Level: Intermediate Note: It's what pays the bills (most of them anyway)
o Electronic Engineering Level: Beginner Note: Been building kits forever, learning EE-level
o Machinist Level: Intermediate Note: Trying to get access to a machine shop in D.C.
o Reverse Engineering Level: Chicken Noob Note: Trying to get someone to teach a course on this subject.
o Wireless Hacker Level: Advanced Note: Will teach anyone how to pwnz the APz
o Lockpicker Level: Intermediate Note: Severely out-of-practice but I can still teach
o Electronic Security Level: Intermediate Note: Will be giving my Blackhat training at HacDC before/after
o Gamer Level: Advanced Note: Will teach anyone how to pwnz noobs
o Telco Level: Chicken Noob Note: Trying to get someone to teach me more
o HAM Dork Level: Chicken Noob Note: Trying to get someone to teach me more

OS Choice: 
o Linux (Slackware, Ubuntu)
o Mac (OSX)
o Windows (XP Professional)

Current Interests: 
o Hardware
o Tools
o Machining
o Building labs

Projects: 
o Physical Access Control Thingy
o MAME Cabinet Build
o Robotic Arm Development (Codename: Butterfingers)

Conferences: 
o '''HOPE 2006''' New York City, New York - TOOOL US lockpicking training
o '''Hack in the Box 2007''' Kuala Lumpur, Malaysia - Spoke about the insecurities of RFID
o '''HackCon 2008''' Oslo, Norway - Spoke on electronic security and DIY ideas for hobbyists
o '''Blackhat 2008''' Las Vegas, Nevada - Will be training students about electronic security exploits
o '''Hack in the Box 2008''' Kuala Lumpur, Malaysia - Will be training students about hacking the RF spectrum (802.11, RFID)

User:Q

2008-06-05T18:53:17Z

[[Category:Members]]

== Andrew Q Righter ==
=== Security Consultant Badass ===

[[Image:Qlabs-photo1.jpg]]

Experience: 
o Website Development Level: Advanced
o Web Application Development Level: Intermediate
o Graphic Design Level: Advanced
o Digital Media Level: Intermediate
o Programmer Level: Intermediate
o Network Security Level: Intermediate
o Electronic Engineering Level: Beginner
o Machinist Level: Intermediate
o Reverse Engineering Level: Chicken Noob
o Wireless Hacker Level: Intermediate
o Lockpicker Level: Intermediate
o Electronic Security Level: Intermediate

OS Choice: 
o Linux (Slackware, Ubuntu)
o Mac (OSX)
o Windows (XP Professional)

Current Interests: 
o Hardware
o Tools
o Machining
o Building labs

Projects: 
o Physical Access Control Thingy
o MAME Cabinet Build
o Robotic Arm Development (Codename: Butterfingers)

Conferences: 
o '''HOPE 2006''' New York City, New York - TOOOL US lockpicking training
o '''Hack in the Box 2007''' Kuala Lumpur, Malaysia - Spoke about the insecurities of RFID
o '''HackCon 2008''' Oslo, Norway - Spoke on electronic security and DIY ideas for hobbyists
o '''Blackhat 2008''' Las Vegas, Nevada - Will be training students about electronic security exploits
o '''Hack in the Box 2008''' Kuala Lumpur, Malaysia - Will be training students about hacking the RF spectrum (802.11, RFID)

User:Q

2008-06-05T18:51:55Z

[[Category:Members]]

== Andrew Q Righter ==
=== Security Consultant Badass | Hacker | Speaker ===

[[Image:Qlabs-photo1.jpg]]

Experience: 
o Website Development Level: Advanced
o Web Application Development Level: Intermediate
o Graphic Design Level: Advanced
o Digital Media Level: Intermediate
o Programmer Level: Intermediate
o Network Security Level: Intermediate
o Electronic Engineering Level: Beginner
o Machinist Level: Intermediate
o Reverse Engineering Level: Chicken Noob
o Wireless Hacker Level: Intermediate
o Lockpicker Level: Intermediate
o Electronic Security Level: Intermediate

OS Choice: 
o Linux (Slackware, Ubuntu)
o Mac (OSX)
o Windows (XP Professional)

Current Interests: 
o Hardware
o Tools
o Machining
o Building labs

Projects: 
o Physical Access Control Thingy
o MAME Cabinet Build
o Robotic Arm Development (Codename: Butterfingers)

Conferences: 
o '''HOPE 2006''' New York City, New York - TOOOL US lockpicking training
o '''Hack in the Box 2007''' Kuala Lumpur, Malaysia - Spoke about the insecurities of RFID
o '''HackCon 2008''' Oslo, Norway - Spoke on electronic security and DIY ideas for hobbyists
o '''Blackhat 2008''' Las Vegas, Nevada - Will be training students about electronic security exploits
o '''Hack in the Box 2008''' Kuala Lumpur, Malaysia - Will be training students about hacking the RF spectrum (802.11, RFID)

User:Q

2008-06-05T18:44:37Z

User:Q

2008-06-05T18:30:41Z

User:Q

2008-06-05T18:30:06Z

[[Category:Members]]

<center>== Andrew Q Righter ==</center>
<center>=== Security Consultant Badass | Hacker | Speaker ===</center>

[[Image:Qlabs-photo1.jpg]]

Experience: 
o Website Development Level: Advanced
o Web Application Development Level: Intermediate
o Graphic Design Level: Advanced
o Digital Media Level: Intermediate
o Programmer Level: Intermediate
o Network Security Level: Intermediate
o Electronic Engineering Level: Chicken Noob
o Machinist Level: Intermediate
o Reverse Engineering Level: Chicken Noob

OS Choice: 
o Linux (Slackware, Ubuntu)
o Mac (OSX)
o Windows (XP Professional)

Current Interests: 
o Hardware
o Tools
o Machining
o Building labs

Projects: 
o Physical Access Control Thingy
o MAME Cabinet Build
o Robotic Arm Development (Codename: Butterfingers)

User:Q

2008-06-05T18:29:00Z

User:Q

2008-06-05T18:27:16Z

User:Q

2008-06-05T18:18:14Z

Q: Protected "User:Q" [edit=sysop:move=sysop]

[[Category:Members]]

== Andrew Q Righter ==
=== Security Consultant Badass ===

[[Image:Qlabs-photo1.jpg]]

Experience: 
o Website Development
Level: Badass
o Web Application Development
Level: Intermediate
o Graphic Design
Level: Advanced
o Digital Media
Level: Intermediate
o Python Programmer
Level: Intermediate
o Network Security
Level: Intermediate

User:Q

2008-06-05T18:17:54Z

User:Q

2008-06-05T18:17:40Z

[[Category:Members]]

== Andrew Q Righter ==
= Security Consultant Badass =

[[Image:Qlabs-photo1.jpg]]

Experience: 
o Website Development
Level: Badass
o Web Application Development
Level: Intermediate
o Graphic Design
Level: Advanced
o Digital Media
Level: Intermediate
o Python Programmer
Level: Intermediate
o Network Security
Level: Intermediate

User:Q

2008-06-05T18:16:50Z

[[Category:Members]]

Name: Andrew Q Righter 
Job: Security Consultant

[[Image:Qlabs-photo1.jpg]]

Experience: 
o Website Development
Level: Badass
o Web Application Development
Level: Intermediate
o Graphic Design
Level: Advanced
o Digital Media
Level: Intermediate
o Python Programmer
Level: Intermediate
o Network Security
Level: Intermediate

User:Q

2008-06-05T18:16:11Z

[[Category:Members]]

[[Image:Qlabs-photo1.jpg]]

Name: Andrew Q Righter
Job: Security Consultant

Experience: 
o Website Development
Level: Badass
o Web Application Development
Level: Intermediate
o Graphic Design
Level: Advanced
o Digital Media
Level: Intermediate
o Python Programmer
Level: Intermediate
o Network Security
Level: Intermediate

User:Q

2008-06-05T18:10:09Z

[[Category:Members]]

[[Image:Qlabs-photo1.jpg]]

'''Welcome'''

I will be adding information soon, just beautified the physical access control page - go look !

File:Qlabs-photo1.jpg

2008-06-05T18:09:43Z

User:Q

2008-06-05T18:08:31Z

[[Category:Members]]

'''Welcome'''

I will be adding information soon, just beautified the physical access control page - go look !

User:Q

2008-06-05T18:08:13Z

[[Category:Members]]

'''Welcome'''

I will be adding information soon, just beautified the physical access control page - go look !

<img src="http://theqlabs.com/img/qlabs-photo1.jpg" alt="meee" />

User:Q

2008-06-05T18:06:23Z

[[Category:Members]]

'''Welcome'''

I will be adding information soon, just beautified the physical access control page - go look !

[[Image:http://theqlabs.com/img/qlabs-photo1.jpg]]

User:Q

2008-06-05T18:04:51Z

[[Category:Members]]

'''Welcome'''

I will be adding information soon, just beautified the physical access control page - go look !

User:Q

2008-06-05T18:04:00Z

<math>pi*5</math>

[[Category:Members]]

Physical Access Control Project

2008-06-05T18:02:44Z

[[Category:Projects]]
[[Category:Ongoing Projects]]
[[Category:Umbrella Projects]]

'''Project Lead: [http://wiki.hacdc.org/index.php?title=User:Q Q]''' 
'''Current Members: [[Elliot]], [[Nathan]] and [[Ash]]'''

'''Abstract''' 
The access control project, which has had many names over the past few weeks of its existence, is a project with two main goals in mind. The security of our space and the convenience of entry for all of our members. The project has been developed into two stages and contains the first stage of a revitalization of the mechanical locking mechanisms currently being used as well as an enhancement to the door frame and its underlying structure and the second stage being the development of a brand new electronic security system with improved access control.

''If you would like to add ideas please do so on the DISCUSSION page, if you are a member of this project feel free to add to this page.''

Stage One:
o Using longer, stronger screws in the door's frame to enhance the structural integrity
o Replacing the crappy core cylinder that is currently in there with a new Medeco 10 series rim/mortise cylinder
o Reinforcing the hinges and making sure they are all strong enough to handle a kick by the feds (joke, please no emails)
o Either buying a new door knob or fixing the internals of the current, it was possible to lock yourself in when we first arrived.

Stage Two:
o Implementing a smart card reader system (contacted)
o Installing the impeding mechanism
o We may need a circuit in the middle of the impeding mechanism and the card reader to do perform some logic
It depends on how the reader we buy is setup, if there are usable pins on the unit we could piggy-back
a connector and setup a small circuit (diode and tiny IC) to supply voltage to the impeding mechanism when
user_card = accepted;
o Writing all the access cards for members
o Developing a PAX system for the backend to log entry data and control users access (helpful for janitor access)
o Use the PAX system to develop alerts that can be broadcast over TCP

'''Wed, May 14, 2008:''' 
Andrew ("Q"), Ash, and Elliot have continued brainstorming. Posted up a link on the blog [http://hacdc.org/2008/05/14/door-unlockerator-project/] to discuss ways to go. Great suggestion (though it might have been a (brilliant) joke?) to make a DDR pad. Elliot's been messing around with the [[Parallax RFID board]], and learning what it can/can't do, but he's terribly terribly new to RF stuff.

'''Wed, May 21, 2008:''' 
Last night, we started looking at the door in question, realized that it only had a handle-lock on it, and realized that we're going to need a wholly new locking mechanism to do anything useful/secure with -- so that's going to be project #1 in terms of serious implementation.

'''Wed, June 5, 2008''' 
So last night at open lab I disassembled the current locking mechanics and made sure everything would work when buying a regular mortise cylinder core from Medeco. Everything looks good to go, I think I'm going to use the existing backplate which should be fine as long as we get a tail on our new core. The door knob and internals are still really flaky, but they really aren't even necessary at this point. With the new core, (Medeco 10 series) we will have sufficient security and it will be 100x better than our current locks. -Q

Physical Access Control Project

2008-06-05T18:01:58Z

[[Category:Projects]]
[[Category:Ongoing Projects]]
[[Category:Umbrella Projects]]

'''Project Lead: [[Users:Q]]''' 
'''Current Members: [[Elliot]], [[Nathan]] and [[Ash]]'''

'''Abstract''' 
The access control project, which has had many names over the past few weeks of its existence, is a project with two main goals in mind. The security of our space and the convenience of entry for all of our members. The project has been developed into two stages and contains the first stage of a revitalization of the mechanical locking mechanisms currently being used as well as an enhancement to the door frame and its underlying structure and the second stage being the development of a brand new electronic security system with improved access control.

''If you would like to add ideas please do so on the DISCUSSION page, if you are a member of this project feel free to add to this page.''

Stage One:
o Using longer, stronger screws in the door's frame to enhance the structural integrity
o Replacing the crappy core cylinder that is currently in there with a new Medeco 10 series rim/mortise cylinder
o Reinforcing the hinges and making sure they are all strong enough to handle a kick by the feds (joke, please no emails)
o Either buying a new door knob or fixing the internals of the current, it was possible to lock yourself in when we first arrived.

Stage Two:
o Implementing a smart card reader system (contacted)
o Installing the impeding mechanism
o We may need a circuit in the middle of the impeding mechanism and the card reader to do perform some logic
It depends on how the reader we buy is setup, if there are usable pins on the unit we could piggy-back
a connector and setup a small circuit (diode and tiny IC) to supply voltage to the impeding mechanism when
user_card = accepted;
o Writing all the access cards for members
o Developing a PAX system for the backend to log entry data and control users access (helpful for janitor access)
o Use the PAX system to develop alerts that can be broadcast over TCP

'''Wed, May 14, 2008:''' 
Andrew ("Q"), Ash, and Elliot have continued brainstorming. Posted up a link on the blog [http://hacdc.org/2008/05/14/door-unlockerator-project/] to discuss ways to go. Great suggestion (though it might have been a (brilliant) joke?) to make a DDR pad. Elliot's been messing around with the [[Parallax RFID board]], and learning what it can/can't do, but he's terribly terribly new to RF stuff.

'''Wed, May 21, 2008:''' 
Last night, we started looking at the door in question, realized that it only had a handle-lock on it, and realized that we're going to need a wholly new locking mechanism to do anything useful/secure with -- so that's going to be project #1 in terms of serious implementation.

'''Wed, June 5, 2008''' 
So last night at open lab I disassembled the current locking mechanics and made sure everything would work when buying a regular mortise cylinder core from Medeco. Everything looks good to go, I think I'm going to use the existing backplate which should be fine as long as we get a tail on our new core. The door knob and internals are still really flaky, but they really aren't even necessary at this point. With the new core, (Medeco 10 series) we will have sufficient security and it will be 100x better than our current locks. -Q

User:Q

2008-06-05T18:01:05Z

Q: New page: Category:Members

[[Category:Members]]

Physical Access Control Project

2008-06-05T17:59:00Z

[[Category:Projects]]
[[Category:Ongoing Projects]]
[[Category:Umbrella Projects]]

'''Project Lead: [[Q]]''' 
'''Current Members: [[Elliot]], [[Nathan]] and [[Ash]]'''

'''Abstract''' 
The access control project, which has had many names over the past few weeks of its existence, is a project with two main goals in mind. The security of our space and the convenience of entry for all of our members. The project has been developed into two stages and contains the first stage of a revitalization of the mechanical locking mechanisms currently being used as well as an enhancement to the door frame and its underlying structure and the second stage being the development of a brand new electronic security system with improved access control.

''If you would like to add ideas please do so on the DISCUSSION page, if you are a member of this project feel free to add to this page.''

Stage One:
o Using longer, stronger screws in the door's frame to enhance the structural integrity
o Replacing the crappy core cylinder that is currently in there with a new Medeco 10 series rim/mortise cylinder
o Reinforcing the hinges and making sure they are all strong enough to handle a kick by the feds (joke, please no emails)
o Either buying a new door knob or fixing the internals of the current, it was possible to lock yourself in when we first arrived.

Stage Two:
o Implementing a smart card reader system (contacted)
o Installing the impeding mechanism
o We may need a circuit in the middle of the impeding mechanism and the card reader to do perform some logic
It depends on how the reader we buy is setup, if there are usable pins on the unit we could piggy-back
a connector and setup a small circuit (diode and tiny IC) to supply voltage to the impeding mechanism when
user_card = accepted;
o Writing all the access cards for members
o Developing a PAX system for the backend to log entry data and control users access (helpful for janitor access)
o Use the PAX system to develop alerts that can be broadcast over TCP

'''Wed, May 14, 2008:''' 
Andrew ("Q"), Ash, and Elliot have continued brainstorming. Posted up a link on the blog [http://hacdc.org/2008/05/14/door-unlockerator-project/] to discuss ways to go. Great suggestion (though it might have been a (brilliant) joke?) to make a DDR pad. Elliot's been messing around with the [[Parallax RFID board]], and learning what it can/can't do, but he's terribly terribly new to RF stuff.

'''Wed, May 21, 2008:''' 
Last night, we started looking at the door in question, realized that it only had a handle-lock on it, and realized that we're going to need a wholly new locking mechanism to do anything useful/secure with -- so that's going to be project #1 in terms of serious implementation.

'''Wed, June 5, 2008''' 
So last night at open lab I disassembled the current locking mechanics and made sure everything would work when buying a regular mortise cylinder core from Medeco. Everything looks good to go, I think I'm going to use the existing backplate which should be fine as long as we get a tail on our new core. The door knob and internals are still really flaky, but they really aren't even necessary at this point. With the new core, (Medeco 10 series) we will have sufficient security and it will be 100x better than our current locks. -Q

Physical Access Control Project

2008-06-05T17:58:29Z

[[Category:Projects]]
[[Category:Ongoing Projects]]
[[Category:Umbrella Projects]]

'''Project Lead:[[Q]]''' 
'''Current Members: Elliot, Nathan and Ash'''

'''Abstract''' 
The access control project, which has had many names over the past few weeks of its existence, is a project with two main goals in mind. The security of our space and the convenience of entry for all of our members. The project has been developed into two stages and contains the first stage of a revitalization of the mechanical locking mechanisms currently being used as well as an enhancement to the door frame and its underlying structure and the second stage being the development of a brand new electronic security system with improved access control.

''If you would like to add ideas please do so on the DISCUSSION page, if you are a member of this project feel free to add to this page.''

Stage One:
o Using longer, stronger screws in the door's frame to enhance the structural integrity
o Replacing the crappy core cylinder that is currently in there with a new Medeco 10 series rim/mortise cylinder
o Reinforcing the hinges and making sure they are all strong enough to handle a kick by the feds (joke, please no emails)
o Either buying a new door knob or fixing the internals of the current, it was possible to lock yourself in when we first arrived.

Stage Two:
o Implementing a smart card reader system (contacted)
o Installing the impeding mechanism
o We may need a circuit in the middle of the impeding mechanism and the card reader to do perform some logic
It depends on how the reader we buy is setup, if there are usable pins on the unit we could piggy-back
a connector and setup a small circuit (diode and tiny IC) to supply voltage to the impeding mechanism when
user_card = accepted;
o Writing all the access cards for members
o Developing a PAX system for the backend to log entry data and control users access (helpful for janitor access)
o Use the PAX system to develop alerts that can be broadcast over TCP

'''Wed, May 14, 2008:''' 
Andrew ("Q"), Ash, and Elliot have continued brainstorming. Posted up a link on the blog [http://hacdc.org/2008/05/14/door-unlockerator-project/] to discuss ways to go. Great suggestion (though it might have been a (brilliant) joke?) to make a DDR pad. Elliot's been messing around with the [[Parallax RFID board]], and learning what it can/can't do, but he's terribly terribly new to RF stuff.

'''Wed, May 21, 2008:''' 
Last night, we started looking at the door in question, realized that it only had a handle-lock on it, and realized that we're going to need a wholly new locking mechanism to do anything useful/secure with -- so that's going to be project #1 in terms of serious implementation.

'''Wed, June 5, 2008''' 
So last night at open lab I disassembled the current locking mechanics and made sure everything would work when buying a regular mortise cylinder core from Medeco. Everything looks good to go, I think I'm going to use the existing backplate which should be fine as long as we get a tail on our new core. The door knob and internals are still really flaky, but they really aren't even necessary at this point. With the new core, (Medeco 10 series) we will have sufficient security and it will be 100x better than our current locks. -Q

Physical Access Control Project

2008-06-05T17:56:37Z

[[Category:Projects]]
[[Category:Ongoing Projects]]
[[Category:Umbrella Projects]]

'''Project Lead:[[Q]] - mail me:[[mailto:andrew@i11industries.com]]''' 
'''Current Members: Elliot, Nathan and Ash'''

'''Abstract''' 
The access control project, which has had many names over the past few weeks of its existence, is a project with two main goals in mind. The security of our space and the convenience of entry for all of our members. The project has been developed into two stages and contains the first stage of a revitalization of the mechanical locking mechanisms currently being used as well as an enhancement to the door frame and its underlying structure and the second stage being the development of a brand new electronic security system with improved access control.

''If you would like to add ideas please do so on the DISCUSSION page, if you are a member of this project feel free to add to this page.''

Stage One:
o Using longer, stronger screws in the door's frame to enhance the structural integrity
o Replacing the crappy core cylinder that is currently in there with a new Medeco 10 series rim/mortise cylinder
o Reinforcing the hinges and making sure they are all strong enough to handle a kick by the feds (joke, please no emails)
o Either buying a new door knob or fixing the internals of the current, it was possible to lock yourself in when we first arrived.

Stage Two:
o Implementing a smart card reader system (contacted)
o Installing the impeding mechanism
o We may need a circuit in the middle of the impeding mechanism and the card reader to do perform some logic
It depends on how the reader we buy is setup, if there are usable pins on the unit we could piggy-back
a connector and setup a small circuit (diode and tiny IC) to supply voltage to the impeding mechanism when
user_card = accepted;
o Writing all the access cards for members
o Developing a PAX system for the backend to log entry data and control users access (helpful for janitor access)
o Use the PAX system to develop alerts that can be broadcast over TCP

'''Wed, May 14, 2008:''' 
Andrew ("Q"), Ash, and Elliot have continued brainstorming. Posted up a link on the blog [http://hacdc.org/2008/05/14/door-unlockerator-project/] to discuss ways to go. Great suggestion (though it might have been a (brilliant) joke?) to make a DDR pad. Elliot's been messing around with the [[Parallax RFID board]], and learning what it can/can't do, but he's terribly terribly new to RF stuff.

'''Wed, May 21, 2008:''' 
Last night, we started looking at the door in question, realized that it only had a handle-lock on it, and realized that we're going to need a wholly new locking mechanism to do anything useful/secure with -- so that's going to be project #1 in terms of serious implementation.

'''Wed, June 5, 2008''' 
So last night at open lab I disassembled the current locking mechanics and made sure everything would work when buying a regular mortise cylinder core from Medeco. Everything looks good to go, I think I'm going to use the existing backplate which should be fine as long as we get a tail on our new core. The door knob and internals are still really flaky, but they really aren't even necessary at this point. With the new core, (Medeco 10 series) we will have sufficient security and it will be 100x better than our current locks. -Q

Physical Access Control Project

2008-06-05T17:54:56Z

[[Category:Projects]]
[[Category:Ongoing Projects]]
[[Category:Umbrella Projects]]

'''Project Lead: [[mailto:andrew@i11industries.com][[Q]]''' 
'''Current Members: Elliot, Nathan and Ash'''

'''Abstract''' 
The access control project, which has had many names over the past few weeks of its existence, is a project with two main goals in mind. The security of our space and the convenience of entry for all of our members. The project has been developed into two stages and contains the first stage of a revitalization of the mechanical locking mechanisms currently being used as well as an enhancement to the door frame and its underlying structure and the second stage being the development of a brand new electronic security system with improved access control.

''If you would like to add ideas please do so on the DISCUSSION page, if you are a member of this project feel free to add to this page.''

Stage One:
o Using longer, stronger screws in the door's frame to enhance the structural integrity
o Replacing the crappy core cylinder that is currently in there with a new Medeco 10 series rim/mortise cylinder
o Reinforcing the hinges and making sure they are all strong enough to handle a kick by the feds (joke, please no emails)
o Either buying a new door knob or fixing the internals of the current, it was possible to lock yourself in when we first arrived.

Stage Two:
o Implementing a smart card reader system (contacted)
o Installing the impeding mechanism
o We may need a circuit in the middle of the impeding mechanism and the card reader to do perform some logic
It depends on how the reader we buy is setup, if there are usable pins on the unit we could piggy-back
a connector and setup a small circuit (diode and tiny IC) to supply voltage to the impeding mechanism when
user_card = accepted;
o Writing all the access cards for members
o Developing a PAX system for the backend to log entry data and control users access (helpful for janitor access)
o Use the PAX system to develop alerts that can be broadcast over TCP

'''Wed, May 14, 2008:''' 
Andrew ("Q"), Ash, and Elliot have continued brainstorming. Posted up a link on the blog [http://hacdc.org/2008/05/14/door-unlockerator-project/] to discuss ways to go. Great suggestion (though it might have been a (brilliant) joke?) to make a DDR pad. Elliot's been messing around with the [[Parallax RFID board]], and learning what it can/can't do, but he's terribly terribly new to RF stuff.

'''Wed, May 21, 2008:''' 
Last night, we started looking at the door in question, realized that it only had a handle-lock on it, and realized that we're going to need a wholly new locking mechanism to do anything useful/secure with -- so that's going to be project #1 in terms of serious implementation.

'''Wed, June 5, 2008''' 
So last night at open lab I disassembled the current locking mechanics and made sure everything would work when buying a regular mortise cylinder core from Medeco. Everything looks good to go, I think I'm going to use the existing backplate which should be fine as long as we get a tail on our new core. The door knob and internals are still really flaky, but they really aren't even necessary at this point. With the new core, (Medeco 10 series) we will have sufficient security and it will be 100x better than our current locks. -Q

Physical Access Control Project

2008-06-05T17:52:35Z

[[Category:Projects]]
[[Category:Ongoing Projects]]
[[Category:Umbrella Projects]]

'''Project Lead: [[mailto:andrew@i11industries.com|Andrew (Q)]]''' 
'''Current Members: Elliot, Nathan and Ash'''

'''Abstract''' 
The access control project, which has had many names over the past few weeks of its existence, is a project with two main goals in mind. The security of our space and the convenience of entry for all of our members. The project has been developed into two stages and contains the first stage of a revitalization of the mechanical locking mechanisms currently being used as well as an enhancement to the door frame and its underlying structure and the second stage being the development of a brand new electronic security system with improved access control.

''If you would like to add ideas please do so on the DISCUSSION page, if you are a member of this project feel free to add to this page.''

Stage One:
o Using longer, stronger screws in the door's frame to enhance the structural integrity
o Replacing the crappy core cylinder that is currently in there with a new Medeco 10 series rim/mortise cylinder
o Reinforcing the hinges and making sure they are all strong enough to handle a kick by the feds (joke, please no emails)
o Either buying a new door knob or fixing the internals of the current, it was possible to lock yourself in when we first arrived.

Stage Two:
o Implementing a smart card reader system (contacted)
o Installing the impeding mechanism
o We may need a circuit in the middle of the impeding mechanism and the card reader to do perform some logic
It depends on how the reader we buy is setup, if there are usable pins on the unit we could piggy-back
a connector and setup a small circuit (diode and tiny IC) to supply voltage to the impeding mechanism when
user_card = accepted;
o Writing all the access cards for members
o Developing a PAX system for the backend to log entry data and control users access (helpful for janitor access)
o Use the PAX system to develop alerts that can be broadcast over TCP

'''Wed, May 14, 2008:''' 
Andrew ("Q"), Ash, and Elliot have continued brainstorming. Posted up a link on the blog [http://hacdc.org/2008/05/14/door-unlockerator-project/] to discuss ways to go. Great suggestion (though it might have been a (brilliant) joke?) to make a DDR pad. Elliot's been messing around with the [[Parallax RFID board]], and learning what it can/can't do, but he's terribly terribly new to RF stuff.

'''Wed, May 21, 2008:''' 
Last night, we started looking at the door in question, realized that it only had a handle-lock on it, and realized that we're going to need a wholly new locking mechanism to do anything useful/secure with -- so that's going to be project #1 in terms of serious implementation.

'''Wed, June 5, 2008''' 
So last night at open lab I disassembled the current locking mechanics and made sure everything would work when buying a regular mortise cylinder core from Medeco. Everything looks good to go, I think I'm going to use the existing backplate which should be fine as long as we get a tail on our new core. The door knob and internals are still really flaky, but they really aren't even necessary at this point. With the new core, (Medeco 10 series) we will have sufficient security and it will be 100x better than our current locks. -Q

Physical Access Control Project

2008-06-05T17:51:33Z

[[Category:Projects]]
[[Category:Ongoing Projects]]
[[Category:Umbrella Projects]]

'''Abstract''' 
The access control project, which has had many names over the past few weeks of its existence, is a project with two main goals in mind. The security of our space and the convenience of entry for all of our members. The project has been developed into two stages and contains the first stage of a revitalization of the mechanical locking mechanisms currently being used as well as an enhancement to the door frame and its underlying structure and the second stage being the development of a brand new electronic security system with improved access control.

''If you would like to add ideas please do so on the DISCUSSION page, if you are a member of this project feel free to add to this page.''

Stage One:
o Using longer, stronger screws in the door's frame to enhance the structural integrity
o Replacing the crappy core cylinder that is currently in there with a new Medeco 10 series rim/mortise cylinder
o Reinforcing the hinges and making sure they are all strong enough to handle a kick by the feds (joke, please no emails)
o Either buying a new door knob or fixing the internals of the current, it was possible to lock yourself in when we first arrived.

Stage Two:
o Implementing a smart card reader system (contacted)
o Installing the impeding mechanism
o We may need a circuit in the middle of the impeding mechanism and the card reader to do perform some logic
It depends on how the reader we buy is setup, if there are usable pins on the unit we could piggy-back
a connector and setup a small circuit (diode and tiny IC) to supply voltage to the impeding mechanism when
user_card = accepted;
o Writing all the access cards for members
o Developing a PAX system for the backend to log entry data and control users access (helpful for janitor access)
o Use the PAX system to develop alerts that can be broadcast over TCP

'''Wed, May 14, 2008:''' 
Andrew ("Q"), Ash, and Elliot have continued brainstorming. Posted up a link on the blog [http://hacdc.org/2008/05/14/door-unlockerator-project/] to discuss ways to go. Great suggestion (though it might have been a (brilliant) joke?) to make a DDR pad. Elliot's been messing around with the [[Parallax RFID board]], and learning what it can/can't do, but he's terribly terribly new to RF stuff.

'''Wed, May 21, 2008:''' 
Last night, we started looking at the door in question, realized that it only had a handle-lock on it, and realized that we're going to need a wholly new locking mechanism to do anything useful/secure with -- so that's going to be project #1 in terms of serious implementation.

'''Wed, June 5, 2008''' 
So last night at open lab I disassembled the current locking mechanics and made sure everything would work when buying a regular mortise cylinder core from Medeco. Everything looks good to go, I think I'm going to use the existing backplate which should be fine as long as we get a tail on our new core. The door knob and internals are still really flaky, but they really aren't even necessary at this point. With the new core, (Medeco 10 series) we will have sufficient security and it will be 100x better than our current locks. -Q

'''Project Lead: [[mailto:andrew@i11industries.com]]'''
'''Current Members: Elliot, Nathan and Ash'''