Message Logging; Persistent Log - Crestron 3 Series Reference Manual

Message Logging

3-Series control systems provide messages when the control system performs a
task or when it encounters an issue, such as a hardware or software failure,
hardware incompatibility with software definitions, or a programming error.
NOTE:
that an error has occurred.
Messages created by the control system are written to a persistent log that
stored in the internal flash memory. The persistent log can be saved to external
storage on supported models and can be viewed through the console or through
Crestron Toolbox.

Persistent Log

The persistent log (PLOG) is a log of messages defined by the control system.
The current PLOG can be viewed in the control system console and is available
following a device reboot. The control system stores the contents of the current
PLOG file at "\Sys\Plog\CurrentBoot". The log file is locked and cannot be
opened for transfer.
To print the contents of the current PLOG in the console, issue the ERR
PLOGCURRENT command.
Observe the following about the PLOG:
•
•
The PLOG can also be viewed in Crestron Toolbox using the Error Log function.
For more information, refer to the Crestron Toolbox help file.
Reference Guide – DOC. 7150B
The control system or a controlled device may light a MSG LED to indicate
If a soft reboot is performed, any pending messages are written to the
latest log file and zipped into one file. On reboot, the zipped file at
"\Sys\Plog\CurrentBoot" is moved to "\Sys\Plog\PreviousBoot". During
subsequent reboots, the zipped file from "\Sys\Plog\PreviousBoot" is
moved to "\SYS\Plog\ZippedLogs" for storage.
The control system logs errors as long as there are not over 250 messages
per two-minute period for two consecutive two-minute logging periods:
For each error period, the console displays a PersistentLog: Error
o
state threshold met if error logging is suspended.
When logging is suspended, the log file displays a PersistentLog:
o
Consecutive error states detected; logging is suspended
message, and the user receives a PersistentLog is suspended,
please contact dealer message in the console.
Message logging resumes when there has been less than 10 error
o
messages logged for 10 consecutive two-minute logging periods.
When logging resumes, all messages from the 10 previous logging
periods are logged to the PLOG file. The log in the console also
displays a PersistentLog: Consecutive quite states
detected; logging is resumed message.
3-Series Control Systems • 29