Table of Contents
Advertisement
EN 28
5.
EL1.1U
pins on the SSB. Due to hardware restriction (I
2
the fast I
C bus) it will be impossible to start up the VIPER
and therefore it is also impossible to read out the error
codes via ComPair or via the blinking LED method. With
the knowledge that only errors 1, 2, 4, and 63 result in a 3
Hz blinking LED, the range of possible defects is limited.
When you have restarted the TV via the SDM shortcut pins,
and then pressed "CH+" on your remote control, the TV will
go to protection again, and the front LED blink at 3 Hz
again. This could be an indication that the problem is
related to error 2.
2
•
Error 3 (I
C bus 3 blocked). There are only three devices
2
on I
C bus 3: VIPER, Stand-by Processor, and NVM. The
Stand-by Processor is the detection device of this error, so
this error will only occur if the VIPER or the NVM is blocking
the bus. This error will also be logged when the NVM gives
no acknowledge on the I
the 12 V supply is missing (connector 1M46 on the SSB),
the DC/DC supply on the SSB will not work. Therefore the
VIPER will not get supplies and could block I
a missing 12 V can also lead to an error 3.
2
•
Error 4 (I
C bus 4 blocked). Same remark as with error 1.
2
•
Error 5 (I
C bus 5 blocked). This error will point to a
severe hardware problem around the VIPER (supplies not
OK, VIPER completely dead, I
Stand-by Processor broken, etc...).
•
Error 7 (8.6 V error). Except a physical problem with the
8.6 V itself, it is also possible that there is something wrong
with the Audio DC Protection: see paragraph "Hardware
Protections" for this.
•
Error 12 (12 V error). Except a physical problem with the
12 V itself, it is also possible that there is something wrong
with the Audio DC Protection: see paragraph "Hardware
Protections" for this.
•
Error 14 (Audio supply). This error is triggered in case of
too low voltage of the audio supplies and therefore a drop
of the audio supply voltage of below appr. 9 V per supply
rail (or lower than 18 V rail to rail). Also a DC voltage of
higher than 1 V DC on the speakers will lead to protection
and error 14 blinking. For LCD sets this circuit can be found
on schematic SA3, for PDP sets this can be found on
schematic C. It should be noted that for 26-inch models
there is only a supply link between the amplifiers and the
stand-by µC whereas in all other models this link is
implemented by Audio-Prot line pin 7 on 1 M02.
•
Error 29 (AVIP1). This error will probably generate extra
errors. You will probably also see errors 32 (MPIF) and
error 31 (AVIP 2). Error 29 and 31 will always be logged
together due to the fact that both AVIPs are inside the
PNX2015 and are on the same I
looking for the cause around AVIP (part of PNX2015).
•
Error 31 (AVIP2). See info on error 29.
•
Error 34 (Tuner 1). When this error is logged, it is not sure
that there is something wrong with the tuner itself. It is also
possible that there is something wrong with the
communication between channel decoder and tuner. See
schematic B2B.
•
Error 37 (Channel decoder). This error will always log
error 34 (tuner) extra. This is due to the fact that the tuner
2
I
C bus is coming from the channel decoder.
•
Error 44 (NVM). This error will never occur because it is
masked by error 3 (I
for error 3 checks on an I
NVM gives no acknowledge, the stand-by software
assumes that the bus is blocked, the TV goes to protection
and error 3 will be blinking.
•
Error 53. This error will indicate that the VIPER has started
to function (by reading his boot script, if this would have
failed, error 5 would blink) but initialization was never
completed because of hardware peripheral problems
(NAND flash, ...) or software initialization problems.
Possible cause could be that there is no valid software
loaded (try to upgrade to the latest main software version).
Service Modes, Error Codes, and Fault Finding
2
C bus 2 is
2
C bus (see error 44). Note that if
2
C bus 3. So,
2
C link between VIPER and
2
C bus. In this case start
2
C bus 3). The detection mechanism
2
C acknowledge of the NVM. If
5.6
The Blinking LED Procedure
5.6.1
Introduction
The blinking LED procedure can be split up into two situations:
•
Blinking LED procedure in case of a protection detected by
the stand-by processor. In this case the error is
automatically blinked. This will be only one error, namely
the one that is causing the protection. Therefore, you do
not have to do anything special, just read out the blinks. A
long blink indicates the decimal digit, a short blink indicates
the units.
•
Blinking LED procedure in the "on" state. Via this
procedure, you can make the contents of the error buffer
visible via the front LED. This is especially useful for fault
finding, when there is no picture.
When the blinking LED procedure is activated in the "on" state,
the front LED will show (blink) the contents of the error-buffer.
Error-codes > 10 are shown as follows:
1. "n" long blinks (where "n" = 1 - 9) indicating decimal digit,
2. A pause of 1.5 s,
3. "n" short blinks (where "n"= 1 - 9),
4. A pause of approx. 3 s.
5. When all the error-codes are displayed, the sequence
finishes with a LED blink of 3 s,
6. The sequence starts again.
Example: Error 12 9 6 0 0.
After activation of the SDM, the front LED will show:
1. 1 long blink of 750 ms (which is an indication of the decimal
digit) followed by a pause of 1.5 s,
2. 2 short blinks of 250 ms followed by a pause of 3 s,
3. 9 short blinks followed by a pause of 3 s,
4. 6 short blinks followed by a pause of 3 s,
5. 1 long blink of 3 s to finish the sequence,
6. The sequence starts again.
5.6.2
How to Activate
Use one of the following methods:
•
Activate the SDM. The blinking front LED will show the
entire contents of the error buffer (this works in "normal
operation" mode).
•
Transmit the commands "MUTE" - "062500" - "OK"
with a normal RC. The complete error buffer is shown.
Take notice that it takes some seconds before the blinking
LED starts.
•
Transmit the commands "MUTE" - "06250x" - "OK"
with a normal RC (where "x" is a number between 1 and
5). When x= 1 the last detected error is shown, x= 2 the
second last error, etc.... Take notice that it takes some
seconds before the blinking LED starts.
Advertisement
Table of Contents
