When activating an input or a detector, the corresponding alarm event is not generated on the software screen.
- The controller does not communicate
→ Make sure that the controller communication LED are blinking or try to pass a card or to press on the Reset button of the controller in order to see the corresponding event in the log event screen.
- The detector is not cabled correctly to the controller input connector
→ Check the detector cabling. If changing the detector status, the corresponding input LED on the controller should change.
- The corresponding input belongs to an Input group (Alarm zone)
→ Check that its input group is armed and not deactivated. Open the "Controller>Input>Alarm status" screen to determinate what is the input group and make sure that the 'Latest action' field is "None". Then, open the "Event handling program" screen and click on the "View group of inputs" option in order to make sure that the corresponding input group has a Weekly Program which is in the green period at this moment. If this option does not appear, open the INI file and set the following options:
AlarmZones = 1
ControllerInputGroup = 1
Then save and restart GuardPointPro server.
- The corresponding input is not armed on the software
→ Check in the software that the alarm is armed and not deactivated. Open the "Controller>Input" screen and check in the 'General' tab that the corresponding input has a Weekly Program which is in the green period at this moment. Click on the 'Alarm status' tab and make sure that the 'Latest action' field is "None".
- The problem persists
→ If the problem persists, try to initialize the controller, when the installation is not hard-working.
→ Check in the Report Wizard if recent changes have been done in the database on this alarm and if communication problems have occurred recently on this controller.
→ Check if there are errors on the AME file at that time. If so, please send us these errors.