Difference between revisions of "RFID door lock"

From Baltimore Node Wiki
Jump to navigationJump to search
Line 3: Line 3:
 
https://256.makerslocal.org/wiki/index.php/USB_Auth
 
https://256.makerslocal.org/wiki/index.php/USB_Auth
  
== Important features of Load of Fun lock system ==
+
== Required features of Load of Fun lock system ==
  
 
* Cooperation with Sherwin and the rest of the tenants
 
* Cooperation with Sherwin and the rest of the tenants

Revision as of 15:23, 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 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

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

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

Third Party / Complete Solutions

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