What Eos Family Logs Cannot Tell Us
Issue
Log files can be a helpful diagnostic tool, but not everything that happens in the console can be captured via logging. The list of what may be included in log files 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 / E.C.U. has started and is visible
- The symptoms themselves are the best and most useful information
- Nothing is logged before the Windows Embedded OS is launched on consoles
- Console powers off or reboots unexpectedly
- There is no way to distinguish between the internal power supply restarting itself and someone toggling the power switch on the back of the console
- Pressing the facepanel power button to restart or power off the console is logged when Eos software is running
- 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
- The presence of the touchscreen connected via USB is logged, but very little other information is logged
- Devices that never connect or come online at all
- Monitors
- USB devices (touchscreens, keyboards, mice)
Software
- 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 or the source of an output (Cue, Sub)
- Main Playback, Submaster, and other Fader moves are minimally logged in v3.x software. They are not logged in v1.x or v2.x software
- Rate Wheel and Level Wheel moves are minimally logged.