The output control relays provided on each KT‐100, KT‐200, KT‐300, KT‐400 and KTES can be used to activate alarms or other devices such as lighting control, ventilation, and air conditioning. These relays can be activated according to schedules, events reported by the system. They can also be activated to indicate the status of an alarm system or a combination of different logic conditions.
Defining Relays
1 From the Devices definition tab, select the Relay icon. 2 Select the Site and the Controller from the displayed drop‐down lists, then select the relay for which you want to define settings. 3 Specify the Operating mode for the relay:• Normal: the relay is normally de‐energized (deactivated) until it is energized (activated) by an operator, an event or any other system schedule.
• Reverse: the relay is normally energized (activated or resting) until it is de‐energized (deactivated) by an operator, an event or any other system function.
4 Specify the Automatic activation schedule: when this schedule is valid, the relay will be triggered (activated or deactivated) according to the specified activation mode.
5 Specify the Disable relay action: when this schedule is valid, the relay will be deactivated (or activated) according to the predefined operating mode.
6 Set the Temporary activation timer to indicate the delay during which the relay will be temporarily triggered following a temporary activation.
NOTE: When the timer is set to zero, the default activation delay is set to five seconds. Maximum time allowed: 9:06:07 (9 hours, 6 minutes and 7 seconds). When you are using the KT‐400, the maximum time allowed is 18:12:15 (18 hours, 12 minutes and 15 seconds).
7 Select a Graphic and Video view associated with the relay, if applicable.
Input Configuration
Door controllers can monitor the state of input points such as: door contacts, interlocks, alarm points, motion detectors, temperature sensors, any REX and other devices with dry contacts. KT‐100 monitors
the state of 4 input points, KT‐200 monitors the state of 16 input points, and KT‐300 monitors the state of 8 on‐board input points, with a maximum capacity of 16.
• For KT‐200 only. Inputs are normally closed or normally open dry contacts connected in series with one resistor. If the dry contact is connected in series with the green resistor, the input number will be odd. If the dry contact is connected in series with the red resistor, the input number will be even.
• Inputs 1 (door contact) and 2 (request to exit device) are ideally reserved for Door 1 of the controller whereas Input 9 (door contact) and 10 (request to exit device) are ideally reserved for Door 2 of the same controller. The input that is used for the door contact or REX contact SHOULD NOT have a “monitoring” schedule defined in the “Input Definition” menu. • For KT‐100 Controllers. Input 1 is reserved for door contact while input 2 is reserved for a request to exit device. • For KT‐300 Controllers. Input 1 should be reserved for contact on door 1 while input 2 should be used for request to exit device for door 1 of the controller. Input 3 should be reserved for contact on door 2 while input 4 should be used for request to exit device for door 2 of the controller. • For KT‐400 Controllers. Input 1 should be reserved for contact on door 1 while input 2 should be used for request to exit device for door 1 (REX Door #1) of the controller. Input 5 should be reserved for contact on door 2 while input 6 should be used for request to exit device for door 2 of the controller. Input 9 should be reserved for contact on door 3 while input 10 should be used for request to exit device for door 3 of the controller. Input 13 should be reserved for contact on door 4 while input 6 should be used for request to exit device for door 4 of the controller.
Defining Input
You may define inputs from the Input button of the Devices toolbar. You can also define inputs using the Express Setup when defining a controller (see "Express Setup Program" on page 568). 1 From the Devices toolbar, select the Input icon. 2 Select a specific site (from the Site drop‐down list), a controller (from the Controller drop‐down list). 3 From the Input drop‐down list, select the input you want to define.4 Assign a Monitoring schedule to the selected input: this is the schedule during which the system will supervise the condition of the input. When the schedule is valid, a change in input condition generates either an “Input in alarm” or “Input restore” event. NOTE: The input that is used for the door contact, REX contact or interlock contact SHOULD NOT have a monitoring schedule. 5 Specify the Normal condition for the input: it may be Closed or Opened. NOTE: When using single or double EOL resistors, set input Normal Condition to Closed. 6 Specify the Notify abnormal condition for the input: it may be Alarm or Activate.
NOTE: When configuring event parameters with Input in alarm or Input activated as the selected event, only the inputs corresponding to these criteria are displayed. See "Event Parameters Definition" on page 423 for more information.
7 By default, EntraPass will not select the Suspend status update when not monitored. This is to keep data traffic at a minimum. However, this option can be enabled if necessary.
8 Specify the Input response time. This delay corresponds to a period within which an input must remain in the same state before a transition is recognized. This delay is expressed in minutes (mm:ss:cc). Values range from 10 secs to 10 min:55 secs:35 cc for both the alarm response and alarm restore times. • Alarm response time (mm:ss:cc): The delay before the system generates the input and alarm event.
Default is 50 cc.
• Restore response time (mm:ss:cc): The delay before the system generates the input restore events Default is 50 cc.
NOTE: Specifying the input response time allows bouncing time when the contact changes state, and helps to generate only one event for each transition if this time is longer than the bouncing time. For example, a 01:00:00 delay requires that a condition remains stable for at least one minute before it is reported.
9 Specify the Telephone Entry System options (applies to KTES only).
NOTE: To access the modem call type feature, the site connection type must be set to Modem. For more information, see "Sites Configuration" on page 32. The modem call type feature is supported by Multi‐site Gateways only. • Pager call type: You can select Do not call (the relay activation for that event will not be sent to the pager), Call immediately (the relay activation for that event will be sent immediately to the pager) or Call when scheduled (the relay activation for that event will be sent to the pager according to the pager call schedule). See "If you are assigning or defining schedules, make sure that you are selecting the proper category for this schedule. For example, if you are assigning or defining a system schedule (for workstation, operators, event parameters, video triggers) this schedule will be available for selecting components of this category. If you are selecting a schedule for physical components such as controllers, doors, inputs, their schedules will be grouped by gateway if you are using a Global Gateway and by site if you are using a Multi‐site Gateway by site if you are using a Multi‐site Gateway. If you have defined two sites in your system, there will be two separate groups of schedules for each site. You can define up to 99 schedules for each site." on page 186. Default value is Do not call.
• Under modem call type, assign the call type option that best suits event reporting. Default value is Do not call
• Input pager ID: Enter the pager code corresponding to the selected input. Possible values are 201, 202, 203 and 204.
NOTE: To specify pager call types for each events, the Pager reporting function must be enabled. See "Defining the Pager Options" on page 58
10 For KT‐400 and KTES only, check Override default EOL (56K), and then, in the drop‐down menu, select the appropriate item. Default is unchecked.