View Event Logs; Engineer Tests - Pyronix PCX 46 App Programming Reference Manual

Table of Contents

Advertisement

5.2 View Event Logs?

There are two logs available on the system, panel and access control. Each log displays most recent
event first. Use the [] keys 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.
Pressing the a key will return to the main screen for that entry.
NOTE: In any disarmed or armed period, the
any particular event. It is not permitted to delete logs.
5.2.1 The Panel Log?
Includes Arm, Disarm, Trouble, User, Alarm, Engineer Access, Time & Date changes and etc.
5.2.2 The Access/Control Log?
Includes all Access Control and Guard Tour events.

5.3 Engineer Tests?

This function allows the engineer to test zone/inputs, outputs, batteries and the bell.
5.3.1 Walk Test?
This function allows the engineer to test all programmed zones/inputs on each area. The zones/inputs
that haven't been activated will be shown on the display. As each zone/input is triggered, a chime will
sound and that zone/input will disappear from the scrolling list. Once all the zones/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 combined detectors you must first
activate the first detector once and then trigger the second detector; next open the second detector
and trigger the first detector. A walk test can also be done on a single zone/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 zones/inputs are already programmed and saved (i.e.
after exiting the engineers menu).
5.3.2 Soak Test?
The Soak Test is used when zones/inputs need testing without creating problems for the user. For
example testing a perimeter alarm set up when false alarms are likely. If the zone/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 zones/inputs are placed on test without removing previously tested ones, they will
be returned to soak test.
5.3.3 Test Bell & Strobe?
Any outputs programmed as 'any bell' or 'any strobe' (including the wireless bells) will be activated in
this test.
5.3.4 Do Battery Load Test?
The system 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
12.0V, or the battery fuse has failed, a 'BATTERY FAULT 100' warning will be generated. The
may be programmed to perform an automatic battery load test at every power supply at
PCX 46 App
07:00am each day from 'SYSTEM CONFIGURATION?' -> 'Options' -> 'Do Battery Load Test' (See page
20) menu. This will drop the power supply voltage below the battery voltage, whilst monitoring the
system diagnostics. The test will NOT take place if: the End Station bell and strobe PGMs are active,
the system is in Engineer Mode, any battery fault exists, any mains fault exists, or the system option
is not selected. If the test has already started, it will be aborted if any of these conditions apply, other
than entry into Engineer Mode. If the test is aborted, it will NOT take place until the next day.
5.3.5 Test Outputs?
Before you can test any outputs, the output programming must be saved to the NVM by first exiting
the Engineer Menu. The engineer can test all the Programmable Outputs on the End Station (panel),
ROXs, keypads and readers.
5.3.6 Send a Test Call?
If Contact ID or SIA has been programmed, you can send a test call from this option. The system will
send a test call event once the call is activated. Press the t key after the prompt "Are you Sure?"
PCX 46 Programming Reference
PCX 46 App
Page: 22
will only log a maximum of three occurrence of

Advertisement

Table of Contents
loading

Table of Contents