Issue
Using anti-passback and the transactions are delayed by 5 (or more) seconds after the actual card is presented to the reader. During this period (while LED is green) no additional transactions are been recorded to AMT Transaction window. As a result of this the anti-passback is not working for the concurrent swipes.
The interval time between 2 swipes in the controller is configured to 2 seconds. We have tried changing it to zero, but we are not seeing more than transaction within this period come through to AMT.
Product Line
TAC INET
Environment
I/NET Seven 2.xx – with Anti-passback
Cause
When using anti-passback this is usually caused when you have defined the Door Sense setting in the Door Editor and it is either physically not wired or not working. By default this setting is set to Normally Open.
If you have this setting set to normally open or normally closed - the strike will remain energized until the system detects that the door has opened through the sense switch or the strike duration has elapsed, whichever occurs first, the default strike duration setting is 5 seconds.
This means any badges that occur during this time are ignored; (only when anti-passback is enabled). Changing the Intercard interval will not make any difference in this situation.
Resolution
If the door status is not been monitored, you must set the door sense to none. If you are monitoring the door sense then make sure that the door sense activates on each card presentation so that the system recognizes the individual as entering the ‘zone’, therefore allowing the next card to be read.
Note: Implementing anti-passback also requires that you define access control zones. When you use Anti-passback in the true sense it is strongly recommended to use the door sense switch, this is to ensure the individual has actually entered that zone. In situations where this is not possible you can tell the system to ignore the door status by setting the door sense to none, it will then assume that the individual has entered the zone and provide the transaction thereof once the strike duration has expired. In this case the door strike must be configured to suit the environment. Anti-passback requires that a door controller have both an entry reader and an exit reader. An elevator door controller will support only an entry reader, and therefore, will not support anti-passback.
Refer to TCON 300 Chapter 9 – Access Control Anti-passback section for further information.
I/NET Anti-Passback (APB) rules may also be of assistance in setting up Anti-passback.
