Table of Contents
Advertisement
Service Modes, Error Codes, and Fault Finding
Extra Info
•
Rebooting. When a TV is constantly rebooting due to
internal problems, most of the time no errors will be logged
or blinked. This rebooting can be recognised via a ComPair
interface and Hyperterminal (for Hyperterminal settings,
see paragraph "Stand-by software upgrade). You will see
that the loggings which are generated by the main software
keep continuing. In this case (rebooting) diagnose has to
be done via ComPair.
2
•
Error 1 (I
C bus 1 blocked). Depending on the software
version, there are two possibilities:
- The TV goes into protection and the front LED will blink
error 1. Now you can start up the TV via the SDM short-cut
pins on the SSB. The TV will start up and ignores the error.
Depending on the problem it is even possible that you have
picture.
- With this error, probably only the green LED lights up. The
TV does not go into protection but error 1 will still be logged
in the error buffer. In some cases you can have picture and
sound and then you can check the error buffer. Otherwise
use ComPair for further diagnosis (e.g. read out the NVM
content).
2
•
Error 2 (I
C bus 2 blocked). Depending on the software
version, there are two possibilities:
- The TV will not start or will keep rebooting.
Due to hardware restriction (I
it will be impossible to start up the VIPER when I
is blocked. When this error occurs, the TV will not start (but
probably you will see the green LED) or will keep rebooting
(see "Rebooting" description on how to recognize). Starting
up the TV via the SDM short-cut pins will not work. So it will
not be possible to read out error 2 via internal software
(although it will be logged). Use ComPair for further
diagnose (e.g. read out the NVM content).
- The TV will go to standby.
Due to occasional Pacific problems, it is possible that the
2
Pacific will block the I
C-bus 2. Therefore it has been
decided that the TV has to go to stand-by in all cases of a
2
blocked I
C bus 2. Refer also to error 46 description.
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 blink when the NVM gives no
2
acknowledge on the I
C bus. Note that if the 12 V supply is
missing, the DC/DC supply on the SSB will not work.
Therefore the VIPER will not get supplies and could block
2
I
C bus 3. So, a missing 12 V can also lead to an error 3.
2
•
Error 4 (I
C bus 4 blocked). In this chassis, error 4 is no
longer a protection error.
•
Error 5 (VIPER does not boot). 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 (8V6 error). In case of a TV with SDI display you
will see error 7 blink in case of an audio protection. So
except a problem with the 8V6 itself it is also possible that
there is something wrong with the audio part. See also
paragraph "Hardware Protections" for this.
•
Error 14 (Audio protection). The detection is done on the
audio board itself. Several items are monitored:
overvoltage, overcurrent, DC level on the speakers and the
audio supply voltages. If one of these items fails, the
audioprotection will switch "off" the main supply. All
supplies will drop, the standby processor "thinks" there is a
mains dip, and will reboot. At the beginning of the boot
process, the audio-protection line is monitored: if this line is
"active", the set will go to protection and will blink error 14.
•
Error 27 (PNX2015 HD subsystem part). Diagnosing this
error will not be possibly via the normal errorcodes. In case
this device can not communicate with the Viper via I²C, it
will not be possible to initialise the tunnelbus. Hence the
software will not be able to start up, and will re-boot
constantly. Diagnosing these problems will only be
possible via ComPair. In theory it is possible that the error
2
2
C-bus 2 is the fast I
C-bus),
2
C-bus 2
2
C link between VIPER and
BJ3.1A LA
is logged in the NVM (that's why this error is still mentioned
here).
•
Error 29 (AVIP 1). Same remark as for error 27.
•
Error 31 (AVIP 2). Same remark as for error 27.
•
Error 44 (NVM). This error will probably never occur
because it is masked by error 3 (I
mechanism for error 3 checks on an I
the NVM. If 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 46 (Pacific 3). When this errors occurs the TV will go
to stand-by. The reason for this is, when there is an
occasional boot problem of the Pacific, it will look like the
TV has started up in stand-by mode, and the customer can
switch it "on" again. When there is an actual problem with
or around the Pacific the TV will go to stand-by every time
you try to start up. So this behaviour is an indication of a
Pacific problem. But remind that also a blocked I2C-bus 2
can lead to this behaviour (refer also to error 2 description).
•
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).
Note that it takes 90 seconds before the TV goes to
protection in this case.
•
Error 63 (POWER OK). When this error occurs, it means
that the POWER-OK line did not became "high". This error
is only applicable for TV's with a SDI display, a FHP display
or a Sharp full HD display. Depending on the software
version it is possible that the detection mechanism of this
error does not function and that the TV keeps rebooting.
•
Error 64 (Display error). When this error occurs it means
that there is a problem with the I
the display. Although several display types communicate
2
via I
C, this error will only work for TV's with a FHP display.
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 8 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. 8 short blinks followed by a pause of 3 s,
4. 6 short blinks followed by a pause of 3 s,
5.
EN 33
2
C bus 3). The detection
2
C acknowledge of
2
C communication towards
Advertisement
Table of Contents
