Engineer Tests - Pyronix Enforcer 32-WE Programming And Installation Manual

4.18.2 Access Log
The Access log records all events for Access Control events.
With each log, use the key to move from one event to the previous event. The key will
move from one event to the next event that occurred.
To view additional details, press the  key. If no other information is available, the display will
move to the next log entry. Pressing the key will return to the main screen for that entry.
NOTE: For all Fault Codes please refer to Appendix F, on page 55.
Review Logs Programming
1. Press or to scroll to 'REVIEW LOGS'. Press .
2. 'Panel log' will be displayed. Press  to display the panel log.
3. The time, date and event will be displayed. Use [ or ] to scroll
through the event log. If more information is required, for
example, if 'Alarm on Input' is displayed, press to show more
information (e.g. the input that activated). Press to exit the
Panel log.
4. 'Access log' will be displayed. Press  to display the access log
and repeat the operations mentioned above. Press to exit to
the Engineer menu.

4.19 Engineer Tests

The Test function allows the engineer to test inputs, outputs, batteries and the siren.
4.19.1 Sounds To Play
This function previews all of the different tones the Enforcer 32-WE system makes. They have a
choice of: Chime, Chime Follow, Exit, Exit Fault, Entry, Tech Fault, Tamper, Alarm, PA, and Fire.
4.19.2 Walk Test
The walk test feature is used to test all the inputs programmed on the Enforcer 32-WE. It is
recommended that after programming any inputs, the Engineer menu is exited to save all data,
after this point a walk test should be performed. The inputs that haven't been activated will be
shown on the display. 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
preset period. When testing dual-trip detectors, the first detector must be triggered and then the
second detector; next, open the second detector and trigger the first detector.
4.19.3 Soak Control
Any input may be placed on 'soak test' which monitors the detector without giving an alarm
activation. If the chosen input triggers whilst the system is set, it will indicate the activation and
enter the details in the event log. The number of days the input is in soak control before the
input becomes active can be programmed.
4.19.4 Test Siren
Any outputs programmed as '0014 Siren Any' and '0016 Strobe Any' will be tested.
4.19.5 Do Battery Load Test
The Enforcer 32-WE performs a check of the battery operation every 10 seconds, by dipping the
power supply voltage momentarily, and measuring the system voltage. If the battery voltage
measured is below 8.9V, or the battery fuse has failed, a 'BATTERY FAULT' warning will be
generated. The Enforcer 32-WE is programmed to perform an automatic battery load test at
every power supply at 7.00am each day. This will drop the power supply voltage below the
battery voltage, whilst monitoring the system diagnostics. The test will NOT take place if:
 The siren and strobe Output are live
 The Enforcer 32-WE is in Engineer Mode
 Any battery faults exists
 Any mains fault exists
 The site option 'Do Battery Load Test' is not selected (see 'Site Options', page: 21).
If the test has already started, it will be aborted if any of these conditions apply, other than entry
Enforcer Programming Manual
Page: 24
REVIEW LOGS?
Panel log?
28/04 12:47:49
Engineer Access
Access log?