Article ID: GV4-19-12-04-Ch
Release Date: 12/04/2019
Applied to
GV-AS Controllers
Causes of GV-AS Controller Failing to Manage / Grant Access
Note that once GV-AS Controllers are successfully configured by GV-ASManager, they can operate and manage access with the access database stored within the devices regardless of its connection status with GV-ASManager and network stability.
If a GV-AS Controller is unable to operate properly, for managing / granting access, it may due be due to one or more of the causes listed below:
- Controller / Reader Losing Power Supply
If the power supply of a controller is lost, it can no longer operate and manage the access of its connected readers.
If the power supply of a reader is lost, it can no longer operate and manage access for the door it is associated with.
- Controller / Reader Hardware or Physical Malfunction
When a hardware malfunction occurs on the controller / reader, such as a memory defect and/or wear and tear of its cables, connectors or ports, it can no longer perform the function associated with that malfunction.
- Controller Database Not in Sync with GV-ASManager
When the access database stored within the controller is not synchronized with that of the GV-ASManager, it is unable to manage the access of any new personnel, cards and vehicles added on the GV-ASManager but only able to operate based on its own database.
If and when any GV-AS Controller is unable to manage access as configured by GV-ASManager, users should check for the possible causes as listed for troubleshooting.