Access Controller Software Guide

By Brian Rhodes, Published Dec 11, 2017, 10:28am EST

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.

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.

Read this IPVM report for free.

This article is part of IPVM's 6,815 reports, 914 tests and is only available to members. To get a one-time preview of our work, enter your work email to access the full article.

Already a member? Login here | Join now
Loading Related Reports