History Log; Table 48: History Log Display Descriptions; Table 49: History Log Communication Status Values - Bosch DS7200V2-EXP Installation Manual

DS7200V2-EXP | Installation Guide | 4. Reference Materials
4.7

History Log

The history log can store up to 254 events. When the log reaches its threshold, the control panel
sends a Log Threshold {85} report. When the Log reaches capacity, the system sends a Log Overflow
{84} report to the ARC. See "Log Supervision Configuration" in the DS7200V2 Expert Programming
Guide (P/N: 4998153891).
RPS can accept a download from the control panel's log, thus clearing the log file. If the log is not
cleared it begins writing over previous events.
The first line of the log shows the event description (see Control Panel Events and Reporting Formats
on page 108). The second line of the log display alternates between the time and date of the event
and the area, zone (device), user and communication information for the event. The control panel
displays time in 24-hour format and the date as programmed in the Date Format and Enable PIN
Trouble parameter. See "Date Format and Enable PIN Trouble" in the DS7200V2 Expert Programming
Guide (P/N: 4998153891).
To view the log, press [#][8][5]. The keypad might prompt you to enter a valid PIN. Press [*] to
advance to the next event. Press [#] to exit the log and return to the normal display. The history log
uses the following characters to communicate certain information:
Table 48: History Log Display Descriptions
Display
A Area Number
Zn Zone Number
Dv Device Number
Ln Phone Line Number
Mn Minutes till Auto Arm Sked
Cd User Code Number
Op Output Number
Ks Keyswitch Number
U User Number
## Communication status for Routing Destinations
1 & 2
The following table defines the communication status values that may appear in the history log:
Table 49: History Log Communication Status Values
Value
A Aborted
D Deleted from pending buffer by control panel
reboot
F Failed
L Local
P Pending
S Sent
Bosch Security Systems, Inc. | 04/12 | F01U253045-02
Description
Description Probable Cause
An alarm event was programmed with an event
abort window and the control panel was silenced
before the abort timer had expired. The keypad
sounds a quick three-beep tone if an event report is
aborted when the control panel is silenced.
The control panel was rebooted before the events
could be sent.
The event could not be sent to the specified
destination. The problem might be at the receiver
end, or with the control panel programming.
The event is not programmed to report to any
remote destination.
The event is waiting to be sent to the ARC.
The event was successfully sent.
EN | 127