Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
rfid_door_system [2016/02/29 21:04] 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' | + | Quelab now has an electronic sign-in system for members. There' |
===== 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. | ||
- | |||
---- | ---- | ||
- | Technical | + | ===== Maintenance ===== |
+ | |||
+ | ==== Member Maintenance ==== | ||
+ | |||
+ | For Geoff, or whoever registers new members: | ||
+ | |||
+ | * The system automatically records every RFID key it reads. | ||
+ | * When new members sign up, give them keys, then edit the database to assign their names to the keys and mark the keys as authorized for entry. | ||
+ | * When members fail to pay their monthly fees, mark their keys as unauthorized. When members lose their keys, mark the keys as unauthorized, | ||
+ | |||
+ | ==== Registering a New Key ==== | ||
+ | |||
+ | * Hold the key in front of the reader. You'll get a red light. | ||
+ | * On the sign-in laptop, press ctrl-alt-F7. | ||
+ | * Log in with username doorctrl. There' | ||
+ | * Select the RFID_tags table, and select the row with the tag number that matches what's printed on the key. | ||
+ | * Enter the member' | ||
+ | * change the authorized field from 0 to 1 | ||
+ | * Select the Events_24hrs table, then Press the WRITE CHANGES button near the top. | ||
+ | * Move the mouse to the terminal window at the bottom, press the keyboard up arrow to select the xscreensaver lock command from the command history, and press enter to lock the console for doorctrl. | ||
+ | * Press ctr-alt-F5 to switch back to the display of sign-ins during the past 24 hours (it runs under username quelab, and remains unlocked even when you lock doorctrl). | ||
+ | * Have the member try the key, and make sure he gets a green light and his name appears on the display. | ||
+ | |||
+ | <WRAP round important> | ||
+ | |||
+ | * after making any edits, you MUST press WRITE CHANGES in the database editor. | ||
+ | * All RFID keys are disabled while you're editing the database until you write the changes. | ||
+ | * If you get a flashing yellow light but no red or green light when you try a key, check whether the WRITE CHANGES button is enabled, which means you have unwritten changes. | ||
+ | |||
+ | </ | ||
+ | |||
+ | If you need to register multiple keys, you can hold them all in front of the reader one at a time, then authorize them all and enter all the usernames, then write all the changes at once, to save time. You can also log in to the laptop on the network with username doorctrl and edit Quelab_entrance_public.db using whatever editor you want. Do that also if you want to automate revocation of authorization for lack of payment. | ||
+ | |||
+ | ===== Technical | ||
+ | |||
+ | The obsolete Thinkpad T43 by the door was buried under junk and had a thick layer of dust on it when I found it in the shop last week. It now serves several useful functions: | ||
+ | |||
+ | * A display to replace the paper sign-in sheets, so everybody | ||
+ | * A battery back-up for the RFID entry system | ||
+ | * The access control database | ||
+ | * A database editing terminal | ||
+ | * 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 / | ||
+ | |||
+ | 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 // | ||
+ | |||
+ | Source code for the Arduino firmware, the host computer' | ||
+ | ==== System Schematic ==== | ||
+ | {{: |