Editing RFID door lock (section)

== 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.
**** electronic strikes work by unlocking the part that keeps the door in the frame. The bolt going from the door is always unlockable by key.

=== 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?