Trouble inputs are used to monitor the status and condition of the system. Like physical inputs, trouble inputs have a binary on-off state; however, they represent system troubles such as power failures, communications faults, tampers and other issues.
Trouble inputs can be programmed into areas with specific input types so that they are monitored by the system and reported to the monitoring station. Unlike regular inputs, trouble inputs generate 24hr / tamper alarms when they are opened, instead of regular alarms. Typically they are programmed into a dedicated 'system area' that always has its 24hr portion enabled, using the preconfigured Trouble Silent and Trouble Bell input types.
Each module type has its own specific trouble inputs, which are added automatically when that module record is added to the system. The Module Input of each trouble input corresponds to a particular system trouble for that module, such as power supply failure or module tamper. Doors also have dedicated trouble inputs for door left open, door duress and door forced conditions.
See the Trouble Inputs section of the relevant installation manual for a full list for each module.
Name
-
Name: The name of the record in English.
English is the default system language for all records and is assumed to be the primary language.
-
Name (Second Language): The name of the record as it appears within the Protege X user interface when the operator's Portal Settings display language is set to a language other than English.
When the operator's display language is set to any language other than English, all 'Second Language' values become the primary value, and the English versions are displayed as the 'Second Language' value.
-
Keypad Display Name: The name that will be downloaded to the controller. This will be displayed on the keypad and in reports by IP monitoring services. The keypad can only display the first 16 characters of the display name, so it should concisely describe the physical location and function of the resource.
General
Address
- Module Type: The type of device that the trouble input is associated with (e.g. controller, reader expander, door).
- Module Address: The Physical Address of the module or name of the door that the trouble input is associated with.
-
Module Input: The index of the trouble input on the associated module. This determines what system trouble the trouble input monitors and the event code that is sent to the monitoring station when this trouble input generates an alarm.
-
For example, trouble input 3 on an analog expander opens when there is a 'Battery Low / Missing' condition, and sends an event code of 302.
See the Trouble Inputs section of the relevant installation manual for a full list for each module.
-
Configuration
-
Trouble Group: The trouble groups and associated Trouble Group Options determine how trouble conditions will be displayed on the keypad.
There is typically no need to edit the trouble groups as they are automatically set for each trouble input.
The available trouble groups are as follows:
- 0 - None: This trouble input will not be displayed on the keypad. This is used for trouble inputs that technicians on site do not need to be aware of (e.g. 'Installer Logged In').
- 1 - General: This trouble group consists of troubles relevant to the general operation of the system. This includes conditions such as AC failure, reporting issues and input faults.
- 2 - System: This trouble group is used for module related troubles (e.g. module tamper).
- 3 - Access: This trouble group is used for troubles related to access control and door operation (e.g. forced door, too many access attempts).
These fields do not affect the event codes used for reporting.
-
Trouble group settings allow this trouble input to be displayed on the keypad in the Installer View menu, which is useful for technicians checking the system for issues.
-
A custom message based on the selected trouble group option will be displayed in the Trouble View menu, and if enabled on the keypad also in the Offline Trouble View menu.
-
Users can view the current system troubles by logging in to a keypad and pressing [MENU] [5] [2] (Trouble View menu) or [MENU] [4] [1] [2] (Installer View menu).
-
If enabled on the keypad (Controller Records | Keypads | Options 2), the Offline Trouble View menu can be accessed by pressing [MENU] [2], without logging in to the keypad.
-
Trouble Group Options: The trouble group option determines the message that will be displayed on keypads when this trouble input is open.
-
Each selection has one or more variants, determined by the Trouble Group selected above. If the trouble group is set to 1 - General the first entry in the selected trouble group option will be used, trouble group 2 uses the second entry, and so on.
There is typically no need to edit the trouble group options as they are automatically set for each trouble input.
-
-
Reporting ID: The trouble input's Reporting ID is the zone number which will represent that trouble input to the monitoring station.
- The next available ID will be automatically assigned when each trouble input is created. Alternatively, you can manually assign an ID to each trouble input, allowing a high amount of flexibility in trouble input reporting. For example, if two trouble inputs have the same Reporting ID they will both report as the same input.
- If a trouble input has been assigned a number higher than the maximum that can be reported to a particular service the highest possible number will be reported.
- Inputs and trouble inputs share the same range of zone numbers, but trouble inputs typically use higher indexes.
Commands
- This field is used to send programming commands to the device. It should only be used when specifically advised by ICT documentation or technical support.
Areas and Input Types
Like inputs, trouble inputs can be assigned to up to four areas, with a separate input type programmed in each. The input type defines how the trouble input will function in that area. In general, trouble inputs should be used in system areas to generate 24hr alarms (using the preconfigured Trouble Silent and Trouble Bell input types), but they can also be used for output control and automation.
Assigned Areas
-
Area 1-4: The area that monitors this input. Each trouble input can be programmed into up to four different areas. Typically trouble inputs are assigned to a 'system area' which is used to monitor system troubles.
-
Input Type 1-4: The input type defines how the trouble input will operate in that particular area. For example, the Trouble Silent input type will allow the trouble input to generate 24hr / tamper alarms without activating the area's bell output, while the Trouble Bell input type will cause the bell output to be activated. For more information, see Input Types.
Options
General Options
-
Log to Event Buffer: When this option is enabled (by default) the trouble input will generate an event whenever it is opened or closed.
-
Disable this option to prevent trouble input events from being generated, reducing their impact on event storage. Reports will still be sent to the monitoring station.
-
-
Bypassing Not Allowed: It is possible to bypass trouble inputs from the keypad, but the bypass can only be removed by power cycling the controller. Therefore, it is recommended that you disable bypassing for trouble inputs.
-
Latch Bypassing Not Allowed: It is possible to bypass trouble inputs from the keypad, but the bypass can only be removed by power cycling the controller. Therefore, it is recommended that you disable bypassing for trouble inputs.
Advanced Options
-
No Bypass If Any Area Armed: It is possible to bypass trouble inputs from the keypad, but the bypass can only be removed by power cycling the controller. Therefore, it is recommended that you disable bypassing for trouble inputs.