Page 13 of 14
fields of the header and the
“enhanced text” are displayed on the user interface as shown below.
CAP to EAS message conversion information, including the constructed
CAP “enhanced text”
Message Failure
If the alert message fails the CAP conformity test, the unit will not attempt to
verify IPAWS conformity and this fact will be recorded in the log file. If it
passes the CAP verification but fails to create an EAS header, this will be
displayed in the EAS alert information area of the user interface as well as
noted in the log file.
Logging
In addition to the email and print summary logging capabilities described above in the setup section, the
CAP-DEC 1
maintains comprehensive local logs of its alert message activity. Logs are stored on the unit’s
main storage device in the
CAPEAS
directory. These logs may be accessed locally on the unit via
connected keyboard, display and mouse interfaces or over your local network from a PC connected to your
LAN (as network setups may vary, contact your station IT personnel to set up network file sharing access).
Navigate to
C:\CAPEAS
to access these files.
Summary Log
The main C:\
CAPEAS
directory contains the monthly log files which contain details about each message
received. These details include the CAP-DEC 1 unit ID (useful if you are maintaining logs for multiple
units), alert source, whether the alert passed CAP 1.2 and IPAWS Profile constraints, the unique alert
identifier, whether the alert is within the unit’s listening area, whether the alert is current or expired and
additional message details. The log also contains the path to a local copy of the original XML formatted
CAP message and any attached audio. If the message meets all constraints and is successfully converted
into an EAS message, the resulting EAS header string is also included in the log file entry.
Original Message Files
Within the main
CAPEAS
directory is a sub-directory named
log
. The
log
directory holds all of the original
XML formatted CAP messages that the unit receives regardless of the success or failure of converting
them to an EAS message. If the message includes an attached EAS audio file, it is also stored in this
directory. Each entry in the summary log file contains the path to its associated XML alert file and attached
audio file (if present) in this directory.