Reset Of Led Signaling - Technoalarm TP4-20 User Manual

WARNING
Even though alarm memory signaling has no effect on functioning of the control panel and can
therefore remain lit, it is recommended to reset it for reasons of confusion once the reason of alarm
has been identified.
Led signaling can be reset by the holder of the master code only.
- ACCESS -
Master
Viewing
Events
WARNING
The active alarms are not stopped upon reset of alarm memory signaling.
Led signaling for tamper alarm cannot be reset by the user. Consult the installer.
Viewing
Events
30/12 14:18:36
Access user
30/12 14:18:36
Master code
30/12 14:18:36
Keypad 1
ATENCION
Los eventos no se pueden cancelar de la memoria de eventos.
TP4-20 - User Manual

4.8 RESET OF LED SIGNALING

Once the alarm has been stopped, the alarm leds become lit indicating that the alarm
has been recognized and the alarm calls programmed have been executed, and that
the alarm has been stored in the event buffer. Alarm memory signaling persists when
the control panel is put into stand-by.
On the other hand, blinking leds indicate the presence of active alarms, or active
alarm call cycles or persisting alarms, e.g. low battery or power failure.
Enter the master code (default code 12345), e.g.:
+ 12345
On the display appears ACCESS Master.
To accede to the event buffer press:
+ MEM
On the display is viewed Viewing Events.
To reset led signaling press:
+ CL-EX
All the leds previously lit are switched off. The alarms remain however stored in the
event buffer of the control panel.
4.9 CONSULTATION OF THE EVENT BUFFER
The event buffer of the control panel contains the register of all the arming/disarming
and bypass processes, alarms and modifications of programming etc.
To consult the event buffer press:
+ MEM
Commands available
+ yw
to select the events
+ CL-EX
to quit
On the display are viewed all the information available for the event selected:
The first line always shows the date and time the event has occurred
The second line views in sequence up to 4 parameters, e.g. for access with user
code (master or standard user):
1. Name of the event
2. Code used
3. Device used
For those events causing a telephone call the information available on the telephone
calls are viewed, too:
The first line always views the date and time the event has occurred
The second line views the issue of the telephone call cycles:
Tel. call Event with telephone call
Issue call X Issue of the telephone call cycle of the channel indicated
(X = channel A...H)
1 - [issue] Issue of the call on the first number associated to the channel
2 - [issue] Issue of the call on the second number associated to the
channel (see table below)
Control by Console
4-13