Access Controller Software Guide

By: Brian Rhodes, Published on Dec 11, 2017

Properly configuring access controllers software is key to a professional access system.

These devices have fundamental settings that must be configured appropriately, including:

  • Unlock times / extended unlock times
  • Door Hold Open Alarms
  • Request to Exit Inputs
  • Card Formats
  • Reader / interface type
  • Input / output devices
  • Tamper switches

Inside this guide, we review all of those elements including examples of configuration with Axis, HID, Hikvision and Mercury controllers, a hands-on-video, and an explanation of the importance of each element.

******** ***************** ******************* ** *** ** a ************ ****** ******.

***** ******* **** *********** settings **** **** ** configured *************, *********:

  • ****** ***** / ******** unlock *****
  • **** **** **** ******
  • ******* ** **** ******
  • **** *******
  • ****** / ********* ****
  • ***** / ****** *******
  • ****** ********

****** **** *****, ** review *** ** ***** elements ********* ******** ** configuration **** ****, ***, Hikvision *** ******* ***********, a *****-**-*****, *** ** explanation ** *** ********** of **** *******.

[***************]

Configuration ******* *******

*** ***** ******** **** must ** ********** ** every ******* *******:

****** *****

***** **** ******* ***** and ******** *** *********, and ***** **** *** need ** *********** *** variation, *** **** ******* used ** ****** *********** is *** **** * lock ** *******/********* ** unlocked. ******* ** ***** time ** ******** * credential *** **** **** to ** ****-******* ** opening, **** ******* ** central ** ****** **** the ******* ** **** unsecured **** ****** ** allow *** **** ** pass ******* ****** ******** relocked.

******** ****** ****

**** ********* ** ***** unlock **** ** ********* given ** ******** ********** holders ***** ** ******* needs (**** ***********) ** job **************** (**** ******** people). ***** ******* **** 'extended ******' ***** **** a ****** ****** ** keep ***** **** ****** they *** **-****** ** 'held ****' ****** *****.

**** **** **** ******

******* **** ***** *** not ******, ****** ******* generate '**** **** ****' alarms ** ****** ********* when ***** ****** **** for *** ****. ** not **********, *** ****** will *** ********** ****** operators ** ***** ** troubleshoot *********** ***** **********.

********* **** *******

** *******, *********** **** specific ******* ** ********** to ******** ********* *********** from ******** *******. ***** controllers ****** ****** ************** ** ****, ******* *** ***** proprietary ***** *** ** available ** ****** ** specific ****** *******.

******* ** **** ********

**** ***** ** ***** (ie: ********) *** **** openings ****************** ** *********** **** ***** ***** to ******** **** ***** without ***** ***********. ******* these ******* **** **** to ********* *** **** temporarily, *** ******* **** to ****** ***** ********** are ********* ** *** controller *** *** *** lock ********. *** ********** allows ** *** ****** to ******* ** ******, but *** ********** **** restores *** **** *** opening ** * ****** state ***** * ***** period *** *******.

****** ********

** ********, * ******* of ******** *** ****** detection ****** **** ** configured ****, ***, *** who ******** ************* **** they ******. ** *******, controllers *** ****** *** taking ****** ******* ******** or ******** *** ******* emails, ***, ** **** VMS ****** **** ******* is ********** ****** *********.

Configuration ****** ********

******* *** **** ******* of **** *********** **** by ****** *******, *** method ** *********** **** and **** *** *********** used ** ******** ******** is ********* *******. *** sections ***** **** **** common ********** ********:

  • *** **** ***
  • **** *****
  • ******* ******** (**-****)
  • ********* **** *****

***** ***** *** *** party ****** ******** ** our**** ****** ********** ***** (Axis, ***, ******, ***********, *** ***** ******* independent ** **** *****, configure ******* *********** *********. In **** *****, *** underlying ********** ******** *** always ** **** ** configure ***** ********, ******** some ***-***** ** ********** units *** *** ********* them ******** ** ********.

HID **** ***

*****, ***** **** ***'* ******** *** ******* under *** '**** **********' tab:

**** **** '******' *** 'Extended ******' ***** *** be ******** * ****** between * ****** ** to ** *******, *** a ***** *********** ** each ******* ** ****** beside **** *******. ** this **********, *** ******** connected ****** ****** *** keypad ** **** ********** in **** ******.

Axis *****

*** ***-**** **** ********** (**** ****** ****) ***** ***** ******** under *** '******** *************' screen:

**** *** **** ***** lock *** ******** ****** times *** ******, *** called '****** ****' *** 'Long ****** ****' ************. In ********, **** **** open (**** *** **** time) *** ******** (***-***** time) ****** *** **** listed ** **** ******. Note *** ******** ** inputs **** '**** *******' or**** ******** *********** **** ** ********** here.

Hikvision ****** ***********

********* (***:********* ****** ******* ******), *** ** ********* for ******** ********** ******** in ***** ****-**** ********:

***** *** ***** ******** varies, *** ******** **** control *** *** **** as ***** *********. *** example, '**** **** ******** by **** *** ******** Person' ** *** **** as '******** ****** ****', and '**** **** ******* Alarm' ** '**** **** Open *****'.

Mercury ******** ***********

*** ******* ********, *** settings *********** ***** ********* are ******* ** *** partner ********** ******** ********* rather **** ** *** hardware ********** ** ***** itself:

*** *********** *** ***** number ** ******** ****** on *** ****** *** parent ******** *** ********** the ******** **********, *** in ******* ******* ********, all ******* **** ******** like **** '****** ****', extended ****** ********, *** common *****/****** ********** **** locks *** **** ******** switches.

Practical ******* ************

** *** **** *****, these ******** *** **** a *********** ****** ** how **** *** ****** system ********.

Unlock *****

**** ******* ******* ******** a ***** ** *****, typically ******* ** ************. The ******* ******* ****** widely ******* ******* ***** and **** ********** *****. Common ******-********** ******** *** the ******* ****** ***** include:

*****:*** '********' ******** ***** where *** ****** ** mounted *********** ******** ** or ** *** **** frame, *** ****** **** generally ** *** ******* 5 *** ** *******. This ****** ****** **** for ******* ** **** a ****, ****, *** pull **** * **** before ** *******, *** is ***** ****** ** secure *** **** ****** the **** *** ******* that **** ********** ****** **.

******* *****:*** ***** ** ***** needed ** ****** **** a **** *** ***** a ******* ******* **** depending ** *** **** of ******** *** ***** of ****. *******, *********** that ******** ********* *** be ** ** **** feet, *** ********** *** need ** ***** ***** contacts *** ** ******* or ****.

********:**** ***** *** ********* in ******, ** ******** to ***** *** **** in ********, * ********** (or ****** ** ***********) must ** ********** ** lock *** ****** ***** on *** ****** ** other *****. *** **** detail **********, *** *** ****. ******* * *** trapped **** ***** ****** be ****** ***** *** previous ******* ** ******, the "****** ****" ***** 5 ******* ** ****.

Extended ****** ****

******** ** ******** *****:**** * ********** ******* uses ********, * **********, or *** * *** that ******** ******* ******* an ******* ******* ***** in * ***** ******, an "******** ******" **** is ***** ******** ** that ****, ** **** the **** ******** ****** than ******* *** ***********. For *******, * ******** person *** *** ** able ** ******** *** packages ******* * **** in * - ** seconds, *** * ****** of ** ** ** seconds *** ** **** enough ** **** ******* without ************ ********* *** opening.

Door **** **** ******

**** ***** ****** **** risks ***, *** ** alarms ***** ***** *********** durations, *** ****** ******* system *** ******* ** ignored ** * ********. For **** ********, **** Hold **** ****** ****** not ** ********** *** less **** ** *******, and *** **** **** 3 *******.

*******, *** ***** ******** assigned ***** ***** ** be ********** ** ******** use.

Hardware ************* *******

** ******** ** ******** configuration, **** ********** ****** on ******** ********* ****. The ***** ******* *******:

  • ****** ** ************** *******:******* ** ****** **** is *** *********** ** credentials ****** ** **** a ****. *** *******, even ***** ****** ******* offer ** ****** ** card, ***, ** **** card & *** *********** to **** * ****. The ******** ** *** many ******* ** *** may ** ******* ** controller ******* ** ******* credential ***** *** *** require ******** ************* *** production ***. *** * deeper ****, *** ************** ************** ********.
  • *****/****** *******:*** '***********' ***** ** I/O ******* *** ****** may ** *******, *** the ******* ** *** relay ******** ******* *** controller **** * *** part ** *** **** are *********. *** **********, see *********/******* *****.** * ***** ** devices **** ********* ******** and ********* *** ** be ******** ** *** controller, *** *** **** to ** *******, **********, or ********* ** '**********' circuits ***** **** *** switched.
  • ******* ****** ********:** **** *****, *********** a ***** ** ********* tamper ******* ** ****** for ******* ** ***** as ** ******. **** controllers ******* * ****** contact ** ****** *******, but ******* ** ** for *** ** ***** optional. ******** **************, ***** contact **************, ** ******** jumper ******** *** ****** steps ******** ** *** these ****** ********.

Controller *** ****** ****** *******

** *** ***** *****, we **** * ***** overview ** *** ***** common ************* **** **** on ******* - ******** connection ** ********** **** readers. **** *********** *** low ******* ******* ********** to ********** ******* ********** that *** ********** *** the ******** ********* *****.

** **** *****, *** settings ******** ***** *** not ** ******** ** recognized *** ************* ***** the ******** ********** *** wired ** *** **********. This ***** ***** *** wiring ** ********* ************ via ****** ***** ****-**** or **** ******* ***** coding:

[****: **** ******** *** originally ********* ** **** and ************* ******* ** 2017]

Comments (12)

Would be useful to add a section with multiple doors considerations

....read in / out,

....anti passback

and the plethora of functionalities that can be obtained with multiple card readers

You may find this article helpful: The Passback Problem

We will queue up an post on 'advanced access configurations' that address read in/out situations. Good idea!

PIR request to exits not programmed correctly resulting in nuisance forced door alarms and request to exits unlocking doors unnecessarily (e.g., when mag lock is not being used) are very common problems we encounter regularly at client sites.

Some codes state that an RTE has to be wired directly in line with the lock circuit, negating the use of the terminals for it on an access controller in those instances.

How would you negate a forced open in that case?  

 

Wire the door through the RTE as well?

I have never seen that as a requirement for a door unless it had a maglock.

Very helpful

It would be great if this article could be amended to include an iStar panel

Looks pretty straight forward

Brian

Please be informed that alot of referable links are not working. Ex : I/O connections, see our note & Multifactor Authentication tutorial.

If you can rectify it, it will be helpful.

Thanks for this. All links have been checked/fixed/updated.

Login to read this IPVM report.
Why do I need to log in?
IPVM conducts unique testing and research funded by member's payments enabling us to offer the most independent, accurate and in-depth information.

Related Reports

Door Operators Access Control Tutorial on Apr 17, 2019
Doors equipped with door operators, specialty devices that automate opening and closing, tend to be quite complex. The mechanisms needed to...
Designing Access Control Guide on Jan 30, 2019
Designing an access control solution requires decisions on 8 fundamental questions. This in-depth guide helps you understand the options and...
ZK Teco Atlas Access Control Tested on Aug 20, 2019
Who needs access specialists? China-based ZKTeco claims its newest access panel 'makes it very easy for anyone to learn and install access control...
Access Control Mustering Guide on Sep 30, 2019
In emergencies, determining where employees are located can be critical for knowing whether they are in danger. Access systems can be used for...
Access Control Door Controllers Guide on Oct 22, 2019
Door controllers are at the center of physical access control systems connecting software, readers, and locks. Despite being buried inside...
Securing Access Control Installations Tutorial on Oct 17, 2019
The physical security of access control components is critical to ensuring that a facility is truly secure. Otherwise, the entire system can be...
Tailgating: Access Control Tutorial on Oct 31, 2019
Nearly all access control systems are vulnerable to an easy exploit called 'tailgating'. Indeed, a friendly gesture in holding doors for others...
Hotel Access Control Explained on Dec 23, 2019
Hotel access control does not work like typical commercial access control because doors in hotels are not typically directly connected to a central...
Low-Tech Access Control: Master Keying Explained on Jan 09, 2020
Mechanical keys are one of the most fundamental forms of access control. 'Master Keying' can allow individually different credential keys to...
Wyze Smart Door Lock Test on Jan 14, 2020
Wyze's inexpensive cameras have grabbed the attention of many in the consumer market, but can the company's new smart lock get similar...

Most Recent Industry Reports

Hanwha Wisenet X Plus PTRZ Tested on Feb 14, 2020
Hanwha has released their PTRZ camera, the Wisenet X Plus XNV-6081Z, claiming the "modular design allows for easy installation". We bought and...
PRC Warns Against China Video Surveillance Hacks, Hikvision Targeted on Feb 14, 2020
Hackers are targeting China video surveillance manufacturers and systems, according to the PRC's main cyber threat monitoring body. The hackers...
IPVM Conference 2020 on Feb 13, 2020
IPVM is excited to announce our 2020 conference. This is the first and only industry event that will be 100% sponsor-free. Like IPVM online, the...
Bosch Dropping Dahua on Feb 13, 2020
Bosch has confirmed to IPVM that it is in the process of dropping Dahua, over the next year, as both IP camera contract manufacturer and recorder...
BluB0X Alleges Lenel, S2, Software House Are Dinosaurs on Feb 13, 2020
BluB0X is running an ad campaign labeling Lenel, S2, Software House, Honeywell, AMAG and more as dinosaurs: In a follow-up email to IPVM,...
London Live Police Face Recognition Visited on Feb 13, 2020
London police have officially begun using live facial recognition in select areas of the UK capital, sparking significant controversy. IPVM...
Converged vs Dedicated Networks For Surveillance Tutorial on Feb 12, 2020
Use the existing network or deploy a new one? This is a critical choice in designing video surveillance systems. Though 'convergence' was a big...
Monitoreal "Completely Autonomous" Home AI Tested on Feb 12, 2020
Monitoreal claims to allow users to "see the things you want (people, vehicles, animals) and ignore the things you don’t”, using AI to distinguish...
Cisco Video Surveillance Is Dead, Long Live Cisco Meraki Video Surveillance on Feb 11, 2020
A dozen years ago much of the industry thought that Cisco was destined to dominate video surveillance. They stumbled repeatedly, failing. Now it is...
BICSI For IP Video Surveillance Guide on Feb 11, 2020
Spend enough time around networks and eventually someone will mention BICSI, the oft-referenced but only vaguely known standards body prevalent in...