Review Logs; Engineer Tests - Pyronix Enforcer 32-WE Programming Reference Manual

5.11 Review Logs?

There are two logs available on the system; panel and access control. Each log displays the most
recent event first. Use [ and ] to move forwards and backwards through the log. To view
additional details, press the c key. If no other information is available, the display will move to the
next log entry. Press a to return to the main screen for that log entry.
NOTE: In any disarmed or armed period, the Enforcer 32-WE will only log a maximum of three
occurrences of any particular event.
NOTE: It is not permitted under EN50131-1 to delete any logs. The only circumstance in which the
logs can be cleared, is part of the "Factory Default" operation - see page 33.
5.11.1 The Panel Log?
Includes Arm, Disarm, Trouble, User, Alarm, Engineer Access, Time & Date changes and etc.
5.11.2 The Access/Control Log?
Includes all Access Control and Guard Tour events.
5.11.3 System Fault Codes
For explanation of all faults that are displayed on the LCD display, please see page: 38.

5.12 Engineer Tests?

The Engineer Tests function allows the engineer to test inputs, outputs (PGMs), batteries and the bell.
5.12.1 Walk Test?
This function allows the engineer to test all programmed inputs on each area. The inputs that
haven't been activated will be shown on the display. As each input is triggered, a chime will sound
and that input will disappear from the list. Once all the inputs have been walk tested, 'Walk Test
Completed' will be displayed. When walk-testing a double-knock detector, it must be triggered
twice within the pre-set period. When testing combined detectors the first detector must be
activated and then the second detector; next open the second detector and trigger the first
detector.
A walk test can also be done on a single input if needed. This can be selected by pressing the x
key after the areas are displayed.
NOTE: The walk test feature can only be used if inputs are already programmed and saved (i.e.
exiting the engineers menu).
5.12.2 Soak Test?
The Soak Test is used when inputs need testing without creating problems for the user. For
example testing a perimeter alarm set up when false alarms are likely. If the input in soak test is
activated whilst the area(s) in which it is located is armed, it will indicate the activation (at disarm)
and enter the details in the system log.
NOTE: If additional inputs are placed on test without removing previously tested ones, they will be
returned to soak test.
Test Inputs
The input numbers in test are added through this option. They will be shown on the display in a
scrolling list.
Soak Days Left
To start the test for an input or group of inputs the number of days the soak test is required for is
programmed in this option. The option also shows how many days are left after the required
number of days has been programmed already (99 = 'endless'). For example, if today the engineer
sets this option to 10 and checks it after 5 days then he will be shown 05 days left.
NOTE: If a number is not entered, the soak test will not start.
Initial Soak
This option will have to be programmed in the beginning of the test to be the same as the Soak
Days Left. In the future when the engineer checks the status of the soak test this option will be
used as a reference to know how long the test was set to in the first place. For example, if the test
was set to 10 days then this option will show 10 days.
5.12.3 Bell Test?
Any outputs programmed as 'any bell' or 'any strobe' (including the wireless bells) will be activated
in this test.
Page: 23