538
edits
Door control system: Difference between revisions
From London Hackspace Wiki
→Hardware
| Line 71: | Line 71: | ||
== Hardware == | == Hardware == | ||
Card readers are based around a pn532 chipset reader, configured to HSU (High Speed UART) mode. This should allow us to read the UID field from block zero of almost all 13.56MHz RFID cards,rings,bands,fobs. HOWEVER, some reader modules are better than others: | |||
Elechouse V3 modules (genuine, red boards). Need a good +5V Vcc supply to be able to energise bank cards., use a DC/DC boost converter on long cable runs. | |||
Deek-Robot modules (blue boards), beware the pinouts are incorrecly labelled on the silkscreen on one side of the board. These boards appear to no longer be manufactured. | |||
Fake Elechouse V3 modules. Don't read very well at all except for very simple fobs with limited power draw. These can be identified by not having the word 'Elechouse' in italics, or having a full stop after the "NFC MODULE V3" label. | |||
Also on the reader modules, there's normally a pushbutton (for menu access on acnodes, or for doorbell action on the door readers), and an RGB LED. | |||
=== Front doorbot === | === Front doorbot === | ||
| Line 78: | Line 86: | ||
The Hackspace card reader is a small blue enclosure on the right hand glass. The reader loop is at the top of the enclosure near the logo. | The Hackspace card reader is a small blue enclosure on the right hand glass. The reader loop is at the top of the enclosure near the logo. | ||
Front doorbot is in a shared enclosure with the Ground floor doorbot, and has a battery backup. In the event of power failure, it will still try to open doors with cached credentials, though some functions will depend on working networking and working acserver. | Front doorbot is in a shared enclosure with the Ground floor (aka Workshops) doorbot, and has a battery backup. In the event of power failure, it will still try to open doors with cached credentials, though some functions will depend on working networking and working acserver. | ||
The front doorbot sends out notifications using MQTT, to the topic base /door/gf-front-external. Any network device can listen in to these messages and set up their own bot/reporting infrastructure, etc. | The front doorbot sends out notifications using MQTT, to the topic base /door/gf-front-external. Any network device can listen in to these messages and set up their own bot/reporting infrastructure, etc. | ||
| Line 102: | Line 110: | ||
=== Back cage gate doorbot === | === Back cage gate doorbot === | ||
Maglock on cage gate. Exit button in shrouded case. ACNode/Doorbot board. Doorbell button fitted in IP55 reader enclosure. | Maglock on cage gate. Exit button in shrouded case. ACNode/Doorbot board. Doorbell button fitted in IP55 reader enclosure. Reader needs replacement with a more reliable module. Fitted with SD card for cacheing credentials. | ||
=== Maglock vs Solenoid latch vs Solenoid deadbolt === | |||
Though we currently mostly use maglocks (because we had them in stock), we are aware of some issues with them, and intend to replace some of them with solenoid deadbolts. The Cisa solenoid latch on the back door requires very gentle adjustments, and is not really suited to a double-leaf door installation. | |||
==Software== | ==Software== | ||
