The controller is the central processing unit responsible for the control of security, access control and building automation in the Protege X system. The controller communicates with system modules, stores configuration and transaction information, processes system communication, and reports alarms and system activity to a monitoring station or remote computer.
For more information about adding, pairing and deleting controllers, see the Setting Up Controllers section.
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.
- Panel Name: The name used to identify the controller to IP reporting services.
General
-
Serial Number: The serial number of the controller. This can be obtained from the controller's built-in web interface or the label on the side of the controller.
-
Pair & Sync: After entering the controller's Serial Number, click this button to pair the controller with Protege X and synchronize all programming.
For pairing requirements and instructions, see Pairing the Controller.
-
Unpair: Use this button to unpair the controller from Protege X. The programming in Protege X is not affected except that the controller's Serial Number is removed. Enter the same serial number again or a new serial number to pair a different controller to this record.
-
Re-Pair: Use this button to temporarily disconnect the controller from Protege X, then attempt to reconnect it. This does not affect any of the programming downloaded to the controller so it will continue to operate normally. This can be used to troubleshoot connectivity issues, as advised by ICT Technical Support.
-
Re-Sync: If the programming has become out-of-sync between Protege X and the controller, you can use this button to completely wipe the controller's programming and synchronize it again. This is useful when a new controller is imported after existing controllers have been paired, or if programming has been changed outside of Protege X.
Be aware that resynchronizing can take a long time and the controller will not be functional until it is complete. For more information, see Resynchronizing the Controller.
Controller Health Status
The controller health status function provides details of the overall status of the system and can be useful in identifying any problem areas that need to be addressed. The controller sends status updates as they occur, allowing Protege X to maintain an updated display of the status of the controller and other system resources.
The available controller health statuses are as follows:
- Online - OK
- Online - Health issues
- Offline - Last seen <date time>
- Offline - Not paired
If the controller reports any health issues they will be displayed in the window below the controller status. This includes any problems that the controller has with its current configuration or its associated (child) resources. For a list of common health status messages, their causes, and actions to take, see Viewing Controller Health Status.
Module Addressing
The module addressing function is used to view the hardware that is connected to the system network, and to set the addresses of the connected modules. This section displays the details of all modules that are currently connected, as well as those that have registered previously but are currently offline.
For more information and instructions for addressing modules, see Module Addressing.
Controller Resources
The following resources are programmed as child records of a controller.
- Inputs
- Outputs
- Input Expanders
- Output Expanders
- Analog Expanders
- Reader Expanders
- Keypads
- Trouble Inputs
- Smart Readers
- Automations
- Programmable Functions
Once programmed they cannot be assigned to a different controller, unless the controller is unpaired and physically replaced with another controller (see Unpairing a Controller).
These records are only downloaded to the parent controller they are assigned to. For more information, see Protege X Record Hierarchy.
Inputs
This section allows you to create and maintain the inputs assigned to the controller, including viewing input status and performing manual commands.
Outputs
This section allows you to create and maintain the outputs assigned to the controller, including viewing output status and performing manual commands.
Input Expanders
This section allows you to create and maintain the input expanders assigned to the controller, including performing module updates.
Output Expanders
This section allows you to create and maintain the output expanders assigned to the controller, including performing module updates.
Analog Expanders
This section allows you to create and maintain the analog expanders assigned to the controller, including performing module updates.
Reader Expanders
This section allows you to create and maintain the reader expanders assigned to the controller, including performing module updates.
Keypads
This section allows you to create and maintain the keypads assigned to the controller, including performing module updates.
Trouble Inputs
This section allows you to create and maintain the trouble inputs assigned to the controller, including viewing trouble input status.
Smart Readers
This section allows you to create and maintain the smart readers assigned to the controller.
Automations
This section allows you to create and maintain the automations assigned to the controller.
Programmable Functions
This section allows you to create and maintain the programmable functions assigned to the controller, including viewing function status and performing manual commands.
Options
-
Test Report Time Is Periodic: This option is currently not supported.
For example, a Test Report Time of 6:00 AM will cause the Service Report Test trouble input to be opened every 6 hours if this option is enabled, or every day at 6AM if disabled.
- Generate Input Restore On Test Report Input: When this option is enabled the controller will generate a restore event for the Service Report Test trouble input closing after the regular test report. This occurs one minute after the Service Report Test trouble input has been activated.
-
Enable UL Operation Mode: When this option is enabled the Protege X system runs in UL compliance mode.
This setting has the following effects:
-
Adds a 10 second grace period following a failed poll before a module is reported as offline.
Each module sends a poll message to the controller every 250 seconds. The module will be reported as offline if no poll has been received for the duration of this poll time plus the 10 second grace period.
- Suppresses reporting of all alarms and/or reportable events to a monitoring station within the first two minutes of the controller powering up. The system will continue to send poll messages as usual.
- Reports 'Input Tamper' events as 'Input Open' events when the area that the input is assigned to is armed. If the area is disarmed an 'Input Tamper' message will be sent.
- Limits the Dial attempts for reporting services to a maximum of 8.
This setting must be used in conjunction with the other configuration requirements specified in the controller installation manual.
-
Misc Options
-
Do Not Wait For Dial Tone When Modem Dials Out: When this option is enabled, modem dialing occurs even when no dial tone is detected.
This setting is only supported by controller models with onboard modem dialers.
-
Enable VOIP Integration: When this option is enabled the controller will allow the Protege Vandal Resistant Touchscreen Entry Station to retrieve user records for directory integration. For more information, see the Protege Vandal Resistant Touchscreen Entry Station Installation Manual.
Controllers on HTTPS currently do not support this feature. This is a known issue.
-
Purge Old Events: When this option is enabled the controller periodically deletes from the event log all events older than the number of days specified in the Days To Keep Events setting below (14 days by default). This is required by local legislation in some countries.
This only deletes events stored on the controller. It does not delete any events from Protege X.
- Days To Keep Events: When the Purge Old Events option above is enabled the controller periodically deletes all events older than the number of days specified here.
Time
The controller's time settings are central to Protege X system functionality and must be properly configured to ensure correct operation of system functions, schedules, automated controls, events and reporting.
- Time Zone: The current time zone that the controller is stationed in. Each time zone is described via its offset from GMT and relevant regions.
- Daylight Savings: The daylight savings configuration to apply to the controller. Daylight savings settings can be configured in the Programming | Daylight Savings page.
For more information, see Programming Daylight Savings.
The controller reads a time update from the Protege X service (if connected) every 24 hours. Whenever the controller is restarted it reads the time and begins the 24 hour cycle again.
Configuration
-
Test Report Time: This field sets the time of day that the controller will test the reporting service by opening the predefined Service Report Test trouble input.
When the Test Report Time Is Periodic option is enabled in the Options section the value programmed here will be used as a period between tests.
-
Module UDP Port: Some modules, such as the Protege Module Network Repeater, can communicate with the controller over an ethernet connection using the UDP protocol. This field defines the UDP port that will be used for these communications. The default port is 9450. If this port is changed at the controller it must also be updated at all relevant modules.
After changing this port you must restart the controller for the setting to take effect.
Module UDP/TCP communications are disabled by default. You can re-enable communications by entering the following commands in the Commands field: EnableModuleUDP = true and EnableModuleTCP = true.
- Default Keypad Language: The default language displayed on the keypad for users who have no language selected.
-
Touch Screen UDP Port:
Touchscreen communications are disabled by default. You can re-enable communications by entering the following command in the Commands field: EnableTLCDCommsUDP = true.
- 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.
Hardware Defaults
-
System Area To Apply: Defines the system area that trouble input records will be automatically assigned to when they are added to the controller or its associated expanders.
- Create Expander Defaults: When enabled, downstream hardware records (inputs, outputs, trouble inputs) will be auto-generated for any expanders created under this controller.
If set to No Area Selected or None, new trouble inputs will not be auto-assigned to any system area, but can be manually assigned.
Custom Reader Format
This section allows you to define a custom reader format (Wiegand or Magnetic) which is available for use by reader expanders connected to the controller.
To use this format, set the Reader Format (Controller Records | Reader Expanders | Reader 1/2) to Custom Format.
See Credential Types for alternative options for configuring custom credentials.
Custom Reader Configuration
- Custom Reader Type: Defines the reader type. The data can be output as Wiegand (D0 and D1) or Magnetic (Clock and Data).
- Bit Length: The total number of bits that are sent by the card reader for each credential.
- Site Code Start: The index where the site/facility code data starts in the transmitted credential data. The count starts at zero.
- Site Code End: The index where the site/facility code data ends in the transmitted credential data. The count starts at zero.
- Card Number Start: The index where the card number data starts in the transmitted credential data. The count starts at zero.
- Card Number End: The index where the card number data ends in the transmitted credential data. The count starts at zero.
-
Data Format: This field describes how to handle the site/facility code and card number received from the reader.
If the size of the site/facility code is smaller than 16 bits and the size of the card number is smaller than 16 bits, set the data format to 16 Bit Data. Otherwise use 32 Bit Data.
Parity 1-4 Options
There can be up to 4 blocks of parity calculated over the received data.
All parity options that are not in use must be set to 255.
- Parity Type 1-4: The method of calculating the parity for the block. This is either even or odd parity.
- Parity Location 1-4: The position of the parity bit in the received data. The count starts at zero.
- Parity Start 1-4: The index where the parity block starts in the received data. The count starts at zero.
- Parity End 1-4: The index where the parity block ends in the received data. The count starts at zero.
Bit Options
All bit options that are not in use must be set to 255.
- Set Bit 1-4: The index of a set bit (a logical '1') in the received data. The count starts at zero.
- Clear Bit 1-4: The index of a clear bit (a logical '0') in the received data. The count starts at zero.
Module Updates
Clicking the button beside a controller record (only visible when hovering) opens the module update command window for that controller.
Programming changes which alter the way hardware will operate require a module update to download the hardware configuration. A module update command causes the module to restart.
- Update Modules: Performs a module update on the controller and all connected modules.
Warning: Sending this command will cause the controller and every connected module to temporarily go offline as they restart. This option should not be used in an active system.
To update only a specific module (such as a keypad or reader expander) navigate to the required module and click on the button beside the module record, then click Update Module.