User Guide

13. Other features - Page 197
Pearl 2004 Manual v1 - 27th August 2004
changing the operating software.
Do make sure you have plenty of time to complete these operations. Do
not attempt to upgrade the operating system or make other
fundamental changes just before showtime!
A [Run AVOS2] - AVOS2 is the low-level operating system of the
console. While AVOS2 is running, you can update the main
operating software in the console. See next section for AVOS2
functions.
B [Diagnostic Screen] - Displays a diagnostic screen which enables
you to test the buttons, faders and wheels on the console. Press
the Up arrow or turn the key back to Run mode to get out of
Diagnostic mode.
The top line of the display shows the Master Fader levels.
Below that are the settings of the Playback Swop buttons, Flash
buttons and faders.
Below that are the preset fader flash/swop buttons and the fader
levels themselves.
Whl1 and Whl2 give an incremental count from the wheels.
Timer and DMX show a count of internal timer ticks and DMX
packets sent.
DOM_resets indicates if resets of the DMX Output Module have
occurred; this is normally caused by the TMS micro becoming
loose in its socket. Try pushing it back into the socket.
Key shows key press and release codes for the buttons. X and Y
show graphics tablet pen coordinates.
XTAL=Good shows if the MIDI oscillator is running. On early
motherboards a modification was required.
C [Display Bus Errors] - A Bus error is generated when either the
software or hardware malfunctions. Up to 20 bus errors are
logged. Press ENTER while viewing the Bus errors to clear the list.
The Bus error Type and the Program counter value at the time of
the Bus Error are stored in the log. Should the Bus error have
been caused by a Software fault, then this information can be
used the pinpoint the precise location of the fault.
If a bus error has been logged then the letter 'E' appears on the
main LCD display positioned somewhere to the top left of the
Chase Window.
Most Bus errors are caused by a faulty or incorrectly inserted VDU
card. As a general rule, if a Bus error occurs, check that all the
Chips on the Borris motherboard are properly seated.
The correct procedure to follow after a Bus error has occurred is
to send the bus error log to [e-mail] together
with a brief description of events just before the Bus error and if
possible the show files and the key log (see D [Tests] Æ E [View
Key History]
D [Tests] - Displays another menu allowing you to test various
hardware in the system.
B [Read FIX.SYS] allows a user dimmer curve to be loaded
C [Modify memory] for Avolites tech support use only