12 en Event ProfileAccess Control Interface Module
4 | Event Profile |
This programming category is used to determine if events are created for:
–Access Ganted and Access Denied.
–Door Requests.
–Door state changes due to manual (command center) or automatic scheduled or armed state changes (skeds/hold open on disarm, normal on armed) operation.
Door #
Default:1
Selections1-8
Enter the door you are about to program.
NOTICE!
RTE events require Access Granted to be programmed [YES].
D# Access Granted?
Default:No
Selections: | Yes or No |
|
|
This program item determines if ACCESS GRANTED and DOOR REQUEST events are sent to the panel for processing memory, printing, and remote reporting.
A successful access event can be initiated by a:
–Valid user ID.
–Valid door state changed at the command cener.
–Automatically scheduled or armed state changes that hold a door open.
–Request to enter/exit [RTE/REX].
Yes Access events from this door controller will be sent to the panel for processing. No Access events from this door controller will not be sent to the panel for processing.
D# No Entry?
Default:No
Selections: | Yes or No |
|
|
This program item determines if No Entry events are sent to the panel for processing memory, printing, and remote reporting.
A No Entry event may be caused by:
–Invalid or unknown user ID, interlock or secured door, or incorrect authority level.
–Request to enter/exit [RTE/REX] for door in interlock or secured door.
Yes Access denied events from this door controller will be sent to the panel for processing. No Access denied events from this door controller will not be sent to the panel for processing.
F.01U.201.526 02 2011.10 | Program Entry Guide | Bosch Security Systems, Inc. |