RFID entry system
| RFID entry system | |
|---|---|
| |
| Name | ESP RFID door controller |
| Zone | Infrastructure
|
| Owner | i3Detroit |
| Make Model | ESP-RFID relay board |
| Part Number | |
| Date Acquired | |
| Storage Location | Mounted to the wall near the door |
| Authorization Required | No |
| Status | Running |
| Value | |
| IP Address | a side: 10.13.107.15; b side: 10.13.107.167 |
| MAC Address | A side: 58:BF:25:DB:82:7E; b side: 58:BF:25:DC:62:8E |
| Hostname | a-side-main, b-side-office |
| Documentation | code |
| Other References | |
Contents
Intro
This is the door controller that controls access to the building
Rules
Instructions
Maintenance Info
Door log is at /var/log/mqtt-door.log
FAQ
ToDo
- make a script that can automagically pull the spreadsheet, but this is a google permissions issue and I think the best way is to create an account that only has read access to the spreadsheet and use credentials from that and I've been lazy.
- Update CRM to replace slot with pin, and put all the keys back in the CRM.
- Cronjob or something to update the doors, but this will need some more error handling because the doors will often crash if you sync twice. You just have to retry, but it's annoying.
- fix or at least report some bugs in esprfid, such as sometimes using data from the last person to scan instead of the most recent scan, as well as the crashing if you sync too many times.
Wiring Notes
Keypad connection
From the top of the board the order is
- D0
- D1
- WG (N/C)
- BUZ
- LED
- GND
- VIN
- F1 (N/C)
- F2 (N/C)
colour table
| purpose | reader | extension |
|---|---|---|
| 12V | red | brown |
| GND | black | brown/white |
| D0 | green | green |
| D1 | white | green/white |
| LED | blue | blue |
| beep | yellow | orange |
| ??? | grey(not populated on all keypads) | orange/wite |
| N/C | N/C | blue/white |
non-keypad connections
- Button has a button
- Door Stat: not connected
- 12V
- RSW: Not connected, no idea
- RPDW: Connected to magnet coil
