Difference between revisions of "RFID door lock"

From Baltimore Node Wiki
Jump to navigationJump to search
Line 37: Line 37:
 
** would require people to be on the loadoffun wireless to buzz people in
 
** would require people to be on the loadoffun wireless to buzz people in
 
** could store access keys locally incase server melts down
 
** could store access keys locally incase server melts down
 +
* No ethernet alternative: signal boards via simple copper wire from central web server.
 +
** '''plus:''' no ethernet shield cost.
 +
** node server (running dyn-dns or similar) authenticates users and then sends command over serial to a usb-attached arduino/similar peripheral. peripheral sets signal lines high for corresponding node devices. Node devices open door locks.
 +
** node server could run fancy program (auth via tropo sms, email, web app), also just as feasible with wireless networking
  
 
=== Third Party / Complete Solutions ===
 
=== Third Party / Complete Solutions ===

Revision as of 16:52, 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?
      • Read that Jeenodes at 100m line of site or 30m indoors. Lower baud-rates improve range.
    • What would the power situation be like?
      • Power off of wall-wart, possibly with battery recharge for power-outage.
    • What are the failure modes?
      • internet out - local activation via keypad/usb key/retina scan
      • power out (internet also out) - battery backup kicks in for a few hours, use local activation
      • it seems like you'd want to always leave the door openable by key for the best failure protection.

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
  • No ethernet alternative: signal boards via simple copper wire from central web server.
    • plus: no ethernet shield cost.
    • node server (running dyn-dns or similar) authenticates users and then sends command over serial to a usb-attached arduino/similar peripheral. peripheral sets signal lines high for corresponding node devices. Node devices open door locks.
    • node server could run fancy program (auth via tropo sms, email, web app), also just as feasible with wireless networking

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)