G Troubleshooting; Introduction; Locating Problems; Audio Faults - Solid State Logic AWS DELTA 916 Owner's Manual

Troubleshooting
G T
ROUBLESHOOTING
I
NTRODUCTION
The following pages are not intended to teach you how to repair any fault on your AWS console, they are merely designed
to guide you through the basic principles of locating and, where possible, working around faults until a replacement part
can be obtained. The AWS console has been designed with a very modular approach to hardware which ensures that
maintenance is quick and simple. The vast majority of components that make up the console are 'plug in' cassettes that
simply require the removal of three screws to enable their replacement.
L P
OCATING ROBLEMS
You should always check external equipment first (unless the fault is obviously within the console – such as loss of signal
when the EQ is switched in). The AWS spends the majority of its life in a stationary position, whereas microphones, their
cables and effects devices etc. are constantly on the move, and hence are much more likely to incur damage.
Once you have established that the problem lies within the console, you need to determine whether the problem is due
to an operational error, or hardware failure. The most common, and easiest to solve, problems are operational errors,
and you should eliminate these first. Refer to the relevant section in this manual, and ensure that you have followed the
correct procedure.
If you have confirmed that the problem is due neither to external equipment nor operational error, then you may have a
hardware fault. Check the troubleshooting tables (on Pages 20-21) for guidance. If your particular problem is not
highlighted then you will have to diagnose the fault yourself, using the guidelines given below. Ensure that you read the
paragraphs on Replacing Modules (Page A-15) before attempting any maintenance.
In most cases, a fault can be located in minutes, with little technical knowledge. The key to correctly diagnosing a hardware
fault is understanding the console's signal flow. Block diagrams detailing analogue signal flow, digital control bus structure
and power wiring, can be found at the end of this section.
Hardware faults can be defined as one of three types: Audio, Control, or Power. Power faults, with the exception of a
poorly seated connector or blown fuse, are probably best left to your distributor. If you wish to know more about the
AWS power supply, you can download information from our website. Fault finding Audio and Control problems, however,
is well within the capability of all users.
A F
UDIO AULTS
Audio faults will most likely manifest themselves as partial, or total, signal loss, or distortion of the audio signal. Referring
to the Channel and Centre section block diagrams, you can see that there are many possible signal paths through the
console. Logical routing, and monitoring of signals at different points, will enable you to easily locate the faulty module.
To give an example of an audio fault, examine the following problem. By working through this example you will see the
basic principles of fault finding at work. You have Channel 24 routed to Track Busses 1 and 2 pre-fader. When monitoring
the Track Busses you notice that the audio can only be heard on the left monitor output.
Your first step is to refer to the AWS Centre Section block schematic. From this you will see that the channel's output
passes through five different modules before reaching the monitors. We can halve the problem by checking the signal path
halfway through the chain. The monitor meters are fed from the output of the 629951 module. Do the meters show the
same level on left and right? If the meters show the same level then the problem is post the 629951 card on either the
629952, 629953 or 629954 card. If the meters show different levels, then the problem is either on the channel's output,
the 629919X1 card or the 629951 card.
For the sake of this example we will assume that the level shown on the meters was different. Using the same principle
we will try to eliminate modules from the signal path. Again referring to the AWS block schematics you can see that the
Track Bus metering is taken post the 629919X1 card's output, but pre the 629951 module's input. Do the Track Bus
meters show the same signal level? If they do, then the problem is on the 629951 card; if not then the problem lies with
the channel strip or the 629919 module.
AWS elta Owner's Manual
Appendices Page A-13