Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
rfid_door_system [2016/05/10 15:55]
John Benedetto 		rfid_door_system [2016/05/23 03:42] (current)
Adric Menning [System Schematic]
Line 3: Line 3:
 ===== Overview ===== ===== Overview =====
  
-Quelab now has an electronic sign-in system for members. There's a hom^H^H^H Quelab-made system with an RFID reader in the window to the left of the front door, and we'll be giving everybody RFID keys. +Quelab now has an electronic sign-in system for members. There's a hom^H^H^H Quelab-made system with an RFID reader in the window to the left of the front door, and we'll be giving everybody RFID keys.
  
 ===== Signing In ===== ===== Signing In =====
Line 14: Line 14:
  
 Besides logging electronic sign-ins, the system also logs when the door is locked and unlocked (using the door code, the knob inside, or the RFID system) and opened and closed. It also has a network connection, so we can get daily reports of sign-ins for accurate accounting of Quelab member traffic, set it to make noises or email the facilities manager if the door is left open or remains unlocked after 10pm, etc. Besides logging electronic sign-ins, the system also logs when the door is locked and unlocked (using the door code, the knob inside, or the RFID system) and opened and closed. It also has a network connection, so we can get daily reports of sign-ins for accurate accounting of Quelab member traffic, set it to make noises or email the facilities manager if the door is left open or remains unlocked after 10pm, etc.
- 
  
 ---- ----
Line 61: Line 60:
     * The network interface     * The network interface
  
-It's configured to allow public read-only access to the database. Log in to the laptop((hostname is Quelabdoor)), and read the Sqlite3 database file /home/doorctrl/rfid_iface_arduino/Quelab_entrance_public.db using sqlitebrowser or whatever else. Editing requires logging in with username doorctrl and a password that I'm giving to Geoff.  ((This password will need to be added to the SYSTEMS password spreadsheet on the Google Drive))+It's configured to allow public read-only access to the database. Log in to the laptop((hostname is Quelabdoor)) , and read the Sqlite3 database file /home/doorctrl/rfid_iface_arduino/Quelab_entrance_public.db using sqlitebrowser or whatever else. Editing requires logging in with username doorctrl and a password that I'm giving to Geoff.  ((This password will need to be added to the SYSTEMS password spreadsheet on the Google Drive))
  
-In addition to the ID that's printed on the key and transmitted to the RFID reader, each key also has a code that's transmitted to the reader but //not//  printed on the key. Our system stores the code in Quelab_entrance_secret.db, which is readable only under username doorctrl, and verifies the code when reading a tag. This means if you try to clone a key just from the printed ID, you won't have the right code, and the system will detect that the key is counterfeit. The table Counterfeits_read records what its name says, and presumably we'll want the system to email the facilities manager if anything ever appears in it.+In addition to the ID that's printed on the key and transmitted to the RFID reader, each key also has a code that's transmitted to the reader but //not//   printed on the key. Our system stores the code in Quelab_entrance_secret.db, which is readable only under username doorctrl, and verifies the code when reading a tag. This means if you try to clone a key just from the printed ID, you won't have the right code, and the system will detect that the key is counterfeit. The table Counterfeits_read records what its name says, and presumably we'll want the system to email the facilities manager if anything ever appears in it.
  
 Source code for the Arduino firmware, the host computer's control program, and the display program are in /home/doorctrl/rfid_iface_arduino/ and are publicly readable. I'll draw a schematic for the hardware, maybe later today. I jerry-rigged a temporary contact switch last night for detecting when the door is open, but Anders is going to replace it with something less embarrassing. However, the scotch tape on the circuit board is intended to be permanent because scotch tape is awesome. Every Arduino I've ever built into anything, including my keyboard, is still held in place with scotch tape. Scotch tape is in fact far better than Arduinos, though that isn't saying much. Source code for the Arduino firmware, the host computer's control program, and the display program are in /home/doorctrl/rfid_iface_arduino/ and are publicly readable. I'll draw a schematic for the hardware, maybe later today. I jerry-rigged a temporary contact switch last night for detecting when the door is open, but Anders is going to replace it with something less embarrassing. However, the scotch tape on the circuit board is intended to be permanent because scotch tape is awesome. Every Arduino I've ever built into anything, including my keyboard, is still held in place with scotch tape. Scotch tape is in fact far better than Arduinos, though that isn't saying much.
  
 ==== System Schematic ==== ==== System Schematic ====
- +{{:quelab_rfid_entry_system_schematic.jpg?200|}}
-FIXME - might look prettier if duplicated in Inkscape, or some other open source editor +
- +
-{{:officers:quelab_rfid_entry_system_schematic.jpg}} +
- +