Difference between revisions of "Keypad Door Access"
Jump to navigation
Jump to search
| Line 12: | Line 12: | ||
* Code on RasPi, based on Noisebidge Baron.py ( https://gitorious.org/sudo-room-keypad-baron ) | * Code on RasPi, based on Noisebidge Baron.py ( https://gitorious.org/sudo-room-keypad-baron ) | ||
* Script is run from /root/sudoor/keypad on the RasPi | * Script is run from /root/sudoor/keypad on the RasPi | ||
== Adding/Managing Codes == | |||
* Codes are in /root/sudoor/keypad/codes.txt | * Codes are in /root/sudoor/keypad/codes.txt | ||
At this time you must be root to add new codes. Next step is to add eaiser ways of adding codes, including being able to add onetime codes that expire for events | At this time you must be root to add new codes. Next step is to add eaiser ways of adding codes, including being able to add onetime codes that expire for events | ||
Revision as of 01:36, 30 May 2013
Sudo Room Keypad Access
Hardware
- 4x4 Keypad
- Arduino
- DoorPi (Sudo Room's Rasberry Pi at the Outside Door)
Software
- Arduino Code based on Noisebridge's keypad code modified for a 4x4 keypad ( https://gitorious.org/sudo-keypad-arduino/sudo-keypad-arduino )
- Code on RasPi, based on Noisebidge Baron.py ( https://gitorious.org/sudo-room-keypad-baron )
- Script is run from /root/sudoor/keypad on the RasPi
Adding/Managing Codes
- Codes are in /root/sudoor/keypad/codes.txt
At this time you must be root to add new codes. Next step is to add eaiser ways of adding codes, including being able to add onetime codes that expire for events