Skip to main content
Electronic Theatre Controls Inc

What Eos Family Logs Cannot Tell Us


Log files can be a helpful diagnostic tool, but not everything in the console can be captured via the log.  The list of what can be seen is long and intricate, and so rather than give pages to read on possibilities, we have chosen to make it clear what we cannot achieve through log reading.

Explanation of What We Cannot See

Hardware Issues

  • “Console doesn’t boot fully” | “Odd beeps on startup” | “Odd BIOS Messages”
    • Logging happens once the shell comes up
    • The symptoms themselves are the best and most useful information
    • Nothing is logged before the Windows Embedded OS is launched
  • Reasons for USB disconnects
    • As far as Eos knows, the USB device just went away.
  • Touchscreens
    • Most of the touchscreen handling is done with a driver, not via the Eos software itself
    • Short of the presence of the touchscreen over USB, there is very little information logged
  • Devices that never connect or come online at all
    • Monitors
    • USB devices (touchscreens, keyboards, mice)


  • Level playback
    • Output from the console, networked or local, is not captured from the logs.  We can see if someone tells a channel to go to a level manually, but not the current output at a specific time.
  • Submaster and other Fader moves are not logged.
  • Rate Wheel and Level Wheel moves minimally logged.


  • Was this article helpful?