Info To Add
From ESCTL
(Difference between revisions)
(→Firmware) |
|||
| (6 intermediate revisions by one user not shown) | |||
| Line 14: | Line 14: | ||
* Implement second relay output | * Implement second relay output | ||
* Unlock (latch) | * Unlock (latch) | ||
| − | * Configurable fail open on loss of controller contact | + | * Configurable fail open or accept any card (optionally on 2nd presentation) on loss of controller contact |
==== Hardware ==== | ==== Hardware ==== | ||
| Line 28: | Line 28: | ||
* Second Wiegand reader [2 pins] | * Second Wiegand reader [2 pins] | ||
| − | + | ===== PCB ===== | |
| − | * Lock connector | + | * Lock connector, with reverse protection diode |
* Door contact connector | * Door contact connector | ||
| + | * Voltage divider for sensing | ||
==== Software ==== | ==== Software ==== | ||
* Write script to do schema extension on Debian | * Write script to do schema extension on Debian | ||
| − | * Extend schema to add 'description' field to escToken | + | * [Done?] Extend schema to add 'description' field to escToken |
| − | * Ability to send commands to door controller via API / remotely e.g. update ID, name, list of local emergency tokens | + | * [DONE] Ability to send commands to door controller via API / remotely e.g. update ID, name, list of local emergency tokens |
| + | * Allow use of escuid in reader configuration, as well as escgid. (Would check for match in escuid if present, then proceed to check escgid as current behaviour) | ||
* Implement second relay output (controllable via LDAP) | * Implement second relay output (controllable via LDAP) | ||
* Unlock automatically between X and Y times/days | * Unlock automatically between X and Y times/days | ||
* Web interface for user / token admin | * Web interface for user / token admin | ||
* Remote unlocking with mobile phone 'key' (app? NFC?) | * Remote unlocking with mobile phone 'key' (app? NFC?) | ||
| + | * Separation of duties (create users vs add access) | ||
| + | * Delegation of privileges (only certain users can grant access to certain doors, etc.) | ||
| + | |||
| + | === Other Info === | ||
| + | * Times in 'escTimeFrom' and 'escTimeTo' are always in local time zone | ||
| + | * Times in 'escDateFrom' and 'escDateTo' may be in GMT (e.g. if created in Active Directory Users and Computers) | ||
Latest revision as of 23:47, 21 March 2017
Contents |
[edit] Future Suggestions
[edit] wiki
- Take screenshots of Apache Directory Studio / schema
- Add colour code / pinout for cat5 cable used between box, lock & reader
[edit] Firmware
- Wiegand output options
- Little-endian / Big-endian / Reversed order
- Convert to Decimal
- Auto read MAC address into Arduino memory
- Store IP address, netmask, router in Arduino memory; set Ethernet each time Arduino boards up
- Store board serial # in Arduino memory
- Implement second relay output
- Unlock (latch)
- Configurable fail open or accept any card (optionally on 2nd presentation) on loss of controller contact
[edit] Hardware
- Implement second relay output
- Two-door controller, that can control two readers and/or two doors (can have reader either side of door, and/or control two doors)
- Self-measurement and reporting of supply voltage
- Door Contact
[edit] Additional Arduino Pins to be used
- Second Relay
- Network card programming
- Door reed switch
- Second Wiegand reader [2 pins]
[edit] PCB
- Lock connector, with reverse protection diode
- Door contact connector
- Voltage divider for sensing
[edit] Software
- Write script to do schema extension on Debian
- [Done?] Extend schema to add 'description' field to escToken
- [DONE] Ability to send commands to door controller via API / remotely e.g. update ID, name, list of local emergency tokens
- Allow use of escuid in reader configuration, as well as escgid. (Would check for match in escuid if present, then proceed to check escgid as current behaviour)
- Implement second relay output (controllable via LDAP)
- Unlock automatically between X and Y times/days
- Web interface for user / token admin
- Remote unlocking with mobile phone 'key' (app? NFC?)
- Separation of duties (create users vs add access)
- Delegation of privileges (only certain users can grant access to certain doors, etc.)
[edit] Other Info
- Times in 'escTimeFrom' and 'escTimeTo' are always in local time zone
- Times in 'escDateFrom' and 'escDateTo' may be in GMT (e.g. if created in Active Directory Users and Computers)
