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.
- Navigate to Controller Records | Controllers.
- Select the controller and view the Status section.
Controller Health Statuses
The controller will report one of the following health statuses:
- Online - OK
- Online - Health issues
- Offline - Last seen <date time>
- Offline - Not paired
If the controller is offline, check its pairing status (see Controller Pairing Troubleshooting).
Common Health Status Messages
If the controller reports any health issues they will be displayed below the controller status. This includes any problems that the controller has with its current configuration or its associated (child) resources. Common health status messages include:
- Modules that require a restart
- Modules that are offline
- Areas that require rearming due to input changes
- Areas where the tamper area (24 hour monitoring) is disarmed
- Inputs that have been assigned to an area, but not assigned a type
- Items that can't fit in the internal database
Essentially, anything that has been configured but is not operating according to that configuration is shown in this list.
Modules that Require a Restart
Typical Health Status Message
Reader Expander Warehouse Reader requires a module restart
Cause
Modules need to be restarted whenever a programming change is made that requires the hardware to physically function in a different manner. The restart allows the module to load the new programming configuration.
Solution
Navigate to the module record and perform a module update.
- Navigate to the appropriate expander menu and select the module that is listed in the health status message.
- Click the button beside the expander record. This opens the module update command window for that module.
- Click Update Module. The module will restart, temporarily dropping offline. When it connects again it will use the new configuration.
It is recommended that you use this method to update modules one at a time instead of the controller's Update Modules command, which restarts every module connected to the controller (regardless of whether the programming has changed).
Modules that are Offline
Typical Health Status Message
Reader Expander Warehouse Reader is offline
Cause
This can occur when the module has been added, but the address has not been correctly set.
Note that if you have recently cycled power to the controller it can take up to 250 seconds for the module to come back online.
Solution
- If you have cycled power to the controller, ensure you have allowed enough time for the module to come online.
- Navigate to the appropriate expander menu.
- Check that the Physical Address allocated in the Configuration section matches that allocated under Controller Records | Controllers | Module Addressing.
- If the problem continues, check that the module is wired correctly.
- Check the LED indicators of the module. If the fault light is on and the status light is flashing red, the number of sequential flashes will indicate an error code.
See the error code section in the relevant hardware installation manual for module error descriptions.
Areas with the Tamper Area Disarmed
Typical Health Status Message
Area Warehouse has its Tamper Area disarmed
Cause
Every area created in Protege X is actually made up of two areas:
- The main area that monitors devices (such as PIRs) only when it is armed.
- The 24 hour (or tamper) area that monitors 24/7 for a tamper or short condition on devices (such as PIRs), and for trouble inputs and panic alarms.
The 24 hour area should be armed at all times, and a health status message will be reported if it is not.
The 24 hour tamper area is armed automatically when the main area is armed.
Solution
- Navigate to Areas and click the arrow beside the area record to open the manual commands window.
- Click Arm 24 Hour Area to enable it.
Areas Requiring Rearming due to Input Changes
Typical Health Status Message
Area Warehouse requires rearming due to Input Warehouse PIR changes
Cause
The 24 hour portion of an area must be rearmed when programming changes result in the input functioning in a different manner. This is to prevent inadvertent changes to a live system that could result in an undetected security breach.
Solution
- Navigate to Areas and click the button beside the area record to open the manual commands window.
- Click Disarm 24 Hour to disarm 24 hour monitoring, then Arm 24 Hour Area to enable it.
Inputs Assigned an Area but no Input Type
Typical Health Status Message
Input Warehouse PIR has an Area but no Input Type assigned
Cause
An input has been assigned to an area but the system has not been instructed on what to do if the input is activated.
Solution
- Navigate to Controller Records | Inputs and select the input listed in the message.
- In the Areas and Input Types section, set the Input Type to the required type for the input for that area.
- Save your changes.
Items that Can't Fit in the Database
Typical Health Status Message
Input Warehouse PIR will not fit into the internal database
Cause
Each module has only a set number of inputs and outputs. For instance, the controller has 8 inputs and 3 outputs, whereas a reader expander has 8 inputs and 8 outputs. If you add a record where the address is higher than the maximum allowed for that expander (such as adding an input to a controller with a module input of 9 or higher), it cannot be added to the system.
Solution
- Navigate to Controller Records | Inputs and select the input listed in the message.
- Ensure that the Module Input setting is valid for the connected expander module.
- Save your changes.