System information

Crestron 3-Series Control Systems Reference Guide
Reference Guide – DOC. 7150A 3-Series Control Systems • 21
3-Series Control System Error Messages
Introduction
This section provides a brief description of 3-Series error messages that may be
encountered. Error messages may be the result of hardware or software failure,
hardware incompatibility with software definitions, or a programming error.
Error messages created by the control system are written to an error log that is stored
in the control system’s RAM. The error log can be saved on removable media on
processors that support it. Use Crestron Toolbox to display the error log.
NOTE: To save the error log in non-volatile memory, use the PERSISTENTLOG
console command to have the error log write to the removable media. For more
information, refer to “
Running Programs from External Storage” on page 19
Error Levels
The following table lists and defines the four levels of error messages that may appear.
Error Message Levels
TYPE DEFINITION
Notice An event has occurred that is noteworthy, but does not affect program
operation.
Warning An event has occurred that could affect program operation, but the
program can still run normally.
Error An event has occurred that indicates that the program is not operating
as expected.
Fatal An event has occurred that prevents the program from running.
Error Format
Each error message has the following format: Level: Message
Some messages have a suffix with additional information in parenthesis:
{Error Level} :{Application}[App#] # [Date/Time] # Message
Only the first two items (level and message) within the error format are of any
immediate value to the programmer.
• Level – defined in the preceding table
• Message – varied
• Error# – unique identifier for Crestron use
• Extended Error# – unique identifier for Crestron use
• Reserved# – not yet defined; for future use
NOTE: It is important to report the exact error message to a Crestron customer
service representative. Also, be as specific as possible regarding the events that lead
to the error (e.g., pressing a certain sequence of buttons, etc). Finally, provide the
compiled archive file.