ETC Product Logging Capabilities

Last updated
Save as PDF

Introduction

Many ETC products include the ability to log information about their functionality and what has transpired over time. Each family of products log vastly different information and not all issues can be diagnosed or determined from logs. Additionally each family of products retain logs for varying amounts of time before being cleared or overwritten. Some products retain logs onboard itself for manual retrieval later, while others are only capable of syslogging data off to another device retain no logs on themselves. The information below outlines the basics of what each product is capable of. If a product is not listed then it has no logging capability. Regardless of what an individual product is capable of, if a system issue is encountered it's best if logs are retrieved as soon as possible to reduce the possibility of important data being lost.

Onboard Logging

The devices below have onboard logging, and are not capable of syslogging data to another device. Logs must be retrieved from the device itself.

Eos Family / ETCnomad Consoles

Eos family consoles (and ETCnomad) contain a variable amount of log data that depends on how much the console is used and the functions utilized in each session. At the extremes some consoles may have as little as one hour of data, while others have logs dating to when it was built at the factory or its last re-image. Most consoles will land somewhere in between. A USB drive and physical access to the console is needed to retrieve logs.

Cobalt / Congo Family Consoles

Cobalt and Congo family consoles contain a variable amount of log data that depends on how much the console is used and the functions utilized in each session. The amount of log data varies based on use but the console, but may contain data to when it was built at the factory or its last re-image. A USB drive and physical access to the console is needed to retrieve logs.

ColorSource Console / EchoTouch

ColorSource (CS) Console and EchoTouch logs are limited to the current session since the last time the hardware was powered on. Logs on the CS console will persist through hibernation, but as soon as power is disconnected all previous logs are erased. EchoTouch has no concept of hibernation, so if power is lost to the unit then all previous logs are erased. In the case of a significant untoward event (such as a crash) the hardware attempts to store the logs to permanent storage for evaluation after the event. That set of 'crash' logs do persist, but are overwritten if another untoward event occurs at a later date or time. A USB drive and physical access to the CS console/EchoTouch is needed to retrieve logs.

Related ColorSource / EchoTouch links:

Retrieving ColorSource Console logs (the process is also valid for EchoTouch)

Conductor

Conductor is unique in that it not only stores its own log information, but also is usually the device which other products send syslog data to. Therefore it's a potential repository for many products in an ETC system, including those which have no onboard log storage. Conductor stores a maximum of 30 days, or 150GB-worth of log data, whichever it hits first. Even the very largest and busiest systems will find it difficult to fill the repository before 30 days. The newest logs will automatically overwrite the oldest log when the repository is full. Network access from a PC or Mac is needed to retrieve logs.

Onboard & Syslog-capable Logging

The devices below have onboard logging, but can also be configured to syslog data to another device. Logs must be retrieved from the device itself.

Paradigm Server (P-CCS) and Processor (P-ACP)

The Paradigm Central Control Server (P-CCS) and individual Paradigm Architectural Control Processors (P-ACP) each store their own unique log data, but can also syslog some of the most important information out. Each stores a maximum of 7 days of logs onboard, but busy systems may end up with less due to the storage limitations of the product. The newest logs will automatically overwrite the oldest logs when the repository is full. Either physical access to the product(s) or network access from a PC or Mac is required to retrieve logs. A USB drive or SD card is needed for P-ACP, and a USB drive is needed for P-CCS when retrieving logs at the physical device.

Paradigm Touchscreen (P-TS18 / P-TSI / VTS)

The large-format Paradigm touchscreens including Paradigm Touchscreen 18" (P-TS18), Paradigm Touchscreen Interface (P-TSI) and Virtual Touchscreen (VTS) contain onboard logs about their sessions, typically about when they connect and disconnect. They can be configured to syslog to an external device. The onboard logs are limited to ten session's-worth of log data. A session begins when the VTS application is launched, and ends when the application is closed. The newest session automatically overwrites the oldest session's log. A USB drive and physical access to the touchscreen is required to retrieve logs.

Mosaic

Individual Mosaic controllers each store their own logs, but can also syslog data out. The onboard logs are limited to the current session since the last time the hardware was powered on; all previous log data is erased on a power cycle. Controllers also have a maximum quantity of logs it can store, making it unlikely log data will reach back to the last boot if it's been powered on for a long duration. Setting up a Controller to syslog helps retain log data for longer durations of time in busier systems.

Mosaic controllers have a definable log verbosity level that apply to new log messages from the point at which the verbosity is changed. Changing the verbosity level will not retroactively change existing log data. Network access from a PC or Mac is required to retrieve logs.

Syslog-capable Only

The list of devices below retain no logs onboard itself, but can syslog data to another device. The only quantity limitation is based on the syslog repository, which usually is Conductor. The type of data each device syslogs varies greatly. Most devices will need some amount of configuration before they'll begin syslogging data out.

Echo Architectural Control Processor (E-ACP)
Echo BACnet Interface (EBI)
Echo Expansion Bridge (EEB)
Echo Integration Interface (EII)
Echo Power Control Processor (E-PCP) used in ERP, ERP-FT, Sensor IQ, and EchoDIN products
Power Control Processor Mk2 (PCP Mk2) used in ERP, ERP-FT, Sensor IQ, and EchoDIN products
Response 0-10v Gateway
Response Mk2 DMX Gateway
Response MIDI / SMPTE / Serial / Analog I/O Gateways
Sensor3 (CEM3)

See How to set up the Syslog IP address on ETC products for instructions on configuring the products above. NOTE: some products require ETC Authorized Service Providers to make changes to product configurations in order to syslog.