Specifications

Level One: Protege GX Installer Study Guide | August 2013 209
The health status is generated by the Controller as follows:
1. The Download Server sends configuration data to the Controller
2. The Controller checks the new configuration
3. Any problems are reported back to the Data Server via the Event Server
This can all take time, so it is important to note that a health status problem will not necessarily show up
immediately after it has been programmed.
The health status will also show up issues related to compatibility. For example, if you are using a PCB
Controller and attempt to use a feature that is unique to the DIN Controller (such as adding a single door to an
access level, or programing too many items such as adding more than 5000 Users), the Controller reports this
back as a health status issue.
The total health status items are shown on the status bar. This doesn't update immediately, as it looks across
every Controller on the system, and is only checked periodically.
It is designed as a diagnostic tool and as a last minute check of the system health before leaving site.
Once our Controller is online, our health status should indicate 6 issues:
 The first message tells us the Controller has been restarted.
This shouldn't happen with a battery backed PSU which is why
it's reported as a health status item.
 The second message is telling us that both of our Reader
expanders are offline. The number in brackets is the database
ID of the item, not the physical address of the hardware. This
applies across the system, including the event log.
 The health status is also advising that both reader expanders require a module update. To do this, we will
first need to get them online.
 Finally, the health status is advising us that the encryption between the Controller and the Server is currently
disabled.
We can clear the first message, as it is only an advisory notice
 Highlight the message and press Clear