Difference between revisions of "RFID door lock"

From Baltimore Node Wiki
Jump to navigationJump to search
Line 7: Line 7:
 
* Cooperation with Sherwin and the rest of the tenants
 
* Cooperation with Sherwin and the rest of the tenants
 
* Should be extremely reliable. QA / field testing should be fun.
 
* Should be extremely reliable. QA / field testing should be fun.
 +
* Should be extremely simple, require no skills (programming, unix, etc.) to change settings, add or remove access.
 
* Should cheap enough to replace all artists keys or work with the current lock system
 
* Should cheap enough to replace all artists keys or work with the current lock system
 
* Should have an option to buzz people in for visitors
 
* Should have an option to buzz people in for visitors
Line 12: Line 13:
  
 
== Solutions ==
 
== Solutions ==
 +
 +
=== No Networking ===
 +
* Each door has its own microcontroller and reader, stores its own access list ( SD card? )
 +
* Buzz in system connects directly to lock and uses simple two conductor wire and a button.
 +
* This system limits failure to one door at a time, is very modular.
  
 
=== Wireless Networking ===  
 
=== Wireless Networking ===  
Line 27: Line 33:
 
** could store access keys locally incase server melts down
 
** could store access keys locally incase server melts down
  
=== Door Hardware ===
+
=== Third Party / Complete Solutions ===
 +
 
 +
What are the money and time costs of using a pre-packaged solution?
 +
 
 +
== Door Hardware ==
  
 
* Electric door strike
 
* Electric door strike
Line 33: Line 43:
 
* Electromagnetic lock
 
* Electromagnetic lock
 
** requires a battery backup incase power goes out
 
** requires a battery backup incase power goes out
** requires a button to be pressed to exit
+
** requires a button to be pressed to exit (This could be a motion sensor, with the button just as a backup)
 
 
=== Third Party / Complete Solutions ===
 
 
 
What are the money and time costs of using a pre-packaged solution?
 

Revision as of 15:51, 24 November 2010

Here is Makers Local 256's version of what we are thinking of doing.

https://256.makerslocal.org/wiki/index.php/USB_Auth

Required features of Load of Fun lock system

  • Cooperation with Sherwin and the rest of the tenants
  • Should be extremely reliable. QA / field testing should be fun.
  • Should be extremely simple, require no skills (programming, unix, etc.) to change settings, add or remove access.
  • Should cheap enough to replace all artists keys or work with the current lock system
  • Should have an option to buzz people in for visitors
  • Will be internal requiring access to two doors

Solutions

No Networking

  • Each door has its own microcontroller and reader, stores its own access list ( SD card? )
  • Buzz in system connects directly to lock and uses simple two conductor wire and a button.
  • This system limits failure to one door at a time, is very modular.

Wireless Networking

  • Jeenodes
    • Do they have enough range?
    • What would the power situation be like?
    • What are the failure modes?

Wired Networking

  • Ethernet shield and web server
    • One wire between door and router, second wire between router and server, and always on door server. As few "moving" parts as necessary.
    • would require people to be on the loadoffun wireless to buzz people in
    • could store access keys locally incase server melts down

Third Party / Complete Solutions

What are the money and time costs of using a pre-packaged solution?

Door Hardware

  • Electric door strike
    • we have one but from our tests it will not work on the outside door. Great for door to studio
  • Electromagnetic lock
    • requires a battery backup incase power goes out
    • requires a button to be pressed to exit (This could be a motion sensor, with the button just as a backup)