Door Controller
(→Door/gate considerations) |
|||
| Line 11: | Line 11: | ||
== Door/gate considerations == | == Door/gate considerations == | ||
| − | Any door, gate or other unit that can be electronically controlled can be used. For example, mag-lock, door strike, solenoid bolt, electric gates, roller shutters etc. | + | Any door, gate or other unit that can be electronically controlled with a simple switch can be used. For example, mag-lock, door strike, solenoid bolt, electric gates, roller shutters etc. |
For fire safety purposes, if this is a fire exit or fire route, this must be able to be exited through during a fire. It is recommend that a mechanical means of exit is provided from the inside, e.g. escape latch with handle – although a pushbutton RQE (Request to Exit) switch can also be used, which will provide traceability of staff movements. This would typically be deployed in conjunction with a break glass override for fire purposes. | For fire safety purposes, if this is a fire exit or fire route, this must be able to be exited through during a fire. It is recommend that a mechanical means of exit is provided from the inside, e.g. escape latch with handle – although a pushbutton RQE (Request to Exit) switch can also be used, which will provide traceability of staff movements. This would typically be deployed in conjunction with a break glass override for fire purposes. | ||
Revision as of 13:16, 16 December 2014
Contents |
What is an esctl Door Controller?
The Door Controller (or Access Controller) module is a small, low power unit that allows automated control over access to a door, gate, turnstile or indeed any other electronically unlockable or controllable item.
It interfaces seamlessly with a central esctl controller (either a dedicated unit, or software running on an existing server) and incorporates a standalone emergency mode for situations where the central controller becomes unavailable. Communication with the central controller is via a standard wired TCP/IP network.
Any standard card or fob system can be used, alongside or instead of electronic keypads.
Deployment Details
Door/gate considerations
Any door, gate or other unit that can be electronically controlled with a simple switch can be used. For example, mag-lock, door strike, solenoid bolt, electric gates, roller shutters etc.
For fire safety purposes, if this is a fire exit or fire route, this must be able to be exited through during a fire. It is recommend that a mechanical means of exit is provided from the inside, e.g. escape latch with handle – although a pushbutton RQE (Request to Exit) switch can also be used, which will provide traceability of staff movements. This would typically be deployed in conjunction with a break glass override for fire purposes.
Reader / Keypad / Keyfob considerations
Any card or fob system can be used with esctl, as long as the readers output in industry-standard Wiegand (26 or 32 bit) format. This covers most types of tags including Mifare, HID Prox, EM4102, Paxton, etc. – in many cases it is possible to re-use existing readers and cards/fobs. Newer technologies such as Mifare are recommended over older technologies such as EM4102, due to the proliferation of devices now on the market to duplicate EM4102 tags, although this is of course similar to physical keys that can also be duplicated.
Network considerations
It is strongly recommended that the wired Ethernet network is physically separated and segregated from end user access. The controllers use embedded low-power micros and no encryption of data is performed.
Whilst it is possible to deploy a central controller on one subnet (perhaps in a central secure server room, or even remotely), and the system will function correctly in this model, this is not recommended due to the additional points of failure introduced by such a configuration. If the end user has relevant expertise (for example perhaps a technology company with a resilient network and guaranteed uptime) then this configuration is possible, on the understanding that any network outages will lead to the inability to access secure doors for the duration.
Hosted / Managed Options
As an optional service, your esctl installation can benefit from the following services
- Secure offsite backup
- Remote support capability
In future releases we will also support Cloud Management, whereby your installation can be administered from a secure cloud console.
Reference details
Revision History
Useful Software
Serial to Ethernet setup software
- USR TCP-232 configuration software can be downloaded from [here]
USB console drivers
To connect via USB to the console of the door controller, a file download may be required if you are running on a Windows computer (for Mac and Linux, no additional drivers are required). The driver is already in Windows, however the .INF file is required to tell Windows which driver to load.
Windows USB driver installation
The following instructions are taken from the [Arduino] site:
- Plug in your board and wait for Windows to begin it's driver installation process. After a few moments, the process will fail, despite its best efforts
- Click on the Start Menu, and open up the Control Panel.
- While in the Control Panel, navigate to System and Security. Next, click on System. Once the System window is up, open the Device Manager.
- Look under Ports (COM & LPT). You should see an open port named "Arduino UNO (COMxx)". If there is no COM & LPT section, look under "Other Devices" for "Unknown Device".
- Right click on the "Arduino UNO (COmxx)" port and choose the "Update Driver Software" option.
- Next, choose the "Browse my computer for Driver software" option.
- Finally, navigate to and select the driver file named arduino.inf (download from here: Media:Arduino.inf,
