Skip to main content
Electronic Theatre Controls Inc

Paradigm Log Files

Paradigm Log Files are often requested by ETC Technical Services to help troubleshoot issues within a Paradigm system. See the links below for instructions on saving logs:
How to Save Logs from a Paradigm Architectural Control Processor (P-ACP)
How to Save Logs from a Paradigm Central Control Server (P-CCS)

Paradigm Log Files are typically saved to a filename of the format Paradigm_log#.tar.gz.  The number matches the processor number of the P-ACP generating the log archive. Paradigm Server logs are often saved as the filename log.tar.gz.

Logs are great at helping sleuth through problems, but they aren't always a silver bullet to every answer. When sending in logs it is best to send logs from the affected Processor, and in a multi-Processor system send in logs from a non-affected Processor as well. In a Server system also include logs from the P-CCS. Always send in the configuration (PCF for non-Server systems, and SPCF for Server systems) along with the logs, as that often helps fill in blanks that can't be gleaned from looking at logs on their own.

Below is a typical, but non-comprehensive, list of the main things we track and do not track in logs.

Info we track:
  • Paradigm version numbers
  • Preset activation or deactivation, and which space(s) it occurs
  • Preset record / snapshot
  • Timed event execution
  • Macro on or off
  • Step labels with log
  • Override enable / disable
  • Stations binding and unbinding (both LON and Ethernet)
  • Heritage station button presses, and resulting actions (if it's something the logs track)
  • Occupancy sensor occupancy / vacancy action
  • Incoming UDP / RS-232 / PSAP strings
  • DMX / sACN acquisition and loss
  • When a Processor or Server reboots / application restarts (but not always able to track why)
  • When P-ACP or P-CCS in multi-processor systems reboot or are experiencing network connectivity issues
  • DRd rack communication issues
  • DRd dimming configuration after a reboot or change to the config
  • ACP power supply or contact I/O fluctuation
  • UTC Offset in a system
  • Discovering LightDesigner sessions and their session name / IP address
  • Entering / Exiting LightDesigner Live Edit and from which IP address
  • P-ACP facepanel interactions (button up and button down, but we don't know specifically what they're doing)
  • USB mount/unmount messages
Info we do not track:
  • Paradigm configs are not saved with the logs
  • Individual Channel level changes or their current status
  • Touchscreen button presses (neither Ethernet or LON)
  • Occupancy sensor state
  • Responsive Controls "button presses" (P-OCC, P-LS, P-DOC)
  • Inspire Station button presses
  • Fader movements on any station
  • Outgoing PSAP triggers
  • Demand Response actions
  • Raise / Lower actions
  • Station Lockout / Visibility current levels or changes of these levels


  • Was this article helpful?