Table of Contents
Advertisement
displayed via the blinking LED procedure when SDM is
switched "on".
•
Error 46 (RF4CE). When there is no I
towards the RF4CE driver during start-up, LAYER 2
error = 46 will be logged and displayed via the blinking LED
procedure when SDM is switched "on".
•
Error 53. This error will indicate that the Fusion device has
read his bootscript (when this would have failed, error 15
would blink) but initialization was never completed because
of hardware problems (NAND flash, DDR...) 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 can take a few minutes
before the TV starts blinking LAYER 1 error = 2 or in SDM
(maintain grounding continuously), LAYER 2 error = 53.
•
Error 61 (NT72314). When there is no I
from the Novatek device (Quad full HD Bolt-on board)
towards the MIPS during start-up, LAYER 2 error = 61 will
be logged.Here, the Novatek device operates as frame rate
convertor.
•
Error 62 (NT68361). When there is no I
from the Novatek device (Quad full HD Bolt-on board)
towards the MIPS during start-up, LAYER 2 error = 62 will
be logged.Here, the Novatek device supports the 4K HDMI
to LVDS conversion.
•
Error 63 (NT72314 not alive).Error generated via I
the device itself, although acknowledge passed and
confirmed.
•
Error 64 (NT68361 not alive).Error generated via I
the device itself, although acknowledge passed and
confirmed.
5.6
The Blinking LED Procedure
5.6.1
Introduction
The blinking LED procedure can be split up into two situations:
•
Blinking LED procedure LAYER 1 error. In this case the
error is automatically blinked when the TV is put in CSM.
This will be only one digit error, namely the one that is
referring to the defective board (see table
overview") which causes the failure of the TV. This
approach will especially be used for home repair and call
centres. The aim here is to have service diagnosis from a
distance.
•
Blinking LED procedure LAYER 2 error. Via this
procedure, the contents of the error buffer can be made
visible via the front LED. In this case the error contains
2 digits (see table
"5-2 Error code
displayed when SDM (hardware pins) is activated. This is
especially useful for fault finding and gives more details
regarding the root cause of the defective board.
Important remark:
For an empty error buffer, the LED should not blink at all in
CSM or SDM. No spacer will be displayed.
When one of the blinking LED procedures is activated, the front
LED will show (blink) the contents of the error buffer. Error
codes greater then 10 are shown as follows:
1. "n" long blinks (where "n" = 1 to 9) indicating decimal digit
2. A pause of 1.5 s
3. "n" short blinks (where "n"= 1 to 9)
4. A pause of approximately 3 s,
5. When all the error codes are displayed, the sequence
finishes with a LED blink of 3 s (spacer).
6. The sequence starts again.
Example: Error 12 8 6 0 0.
After activation of the SDM, the front LED will show:
1. One long blink of 750 ms (which is an indication of the
decimal digit) followed by a pause of 1.5 s
2. Two short blinks of 250 ms followed by a pause of 3 s
3. Eight short blinks followed by a pause of 3 s
4. Six short blinks followed by a pause of 3 s
Service Modes, Error Codes, and Fault Finding
2
C communication
2
C acknowledge
2
C acknowledge
2
C by
2
C by
"5-2 Error code
overview") and will be
5. One long blink of 3 s to finish the sequence (spacer).
6. The sequence starts again.
5.6.2
How to Activate
Use one of the following methods:
•
Activate the CSM. The blinking front LED will show the
layer 1 error(s), this works in "normal operation" mode or
automatically when the error/protection is monitored by the
standby processor.
In case no picture is shown and there is no LED blinking,
read the logging to detect whether "error devices" are
mentioned. (see section
Tips,
5.8.6
Logging").
•
Activate the SDM. The blinking front LED will show the
entire content of the LAYER 2 error buffer, this works in
"normal operation" mode or when SDM (via hardware pins)
is activated when the tv set is in protection.
5.7
Protections
5.7.1
Software Protections
Most of the protections and errors use either the standby
microprocessor or the MIPS controller as detection device.
Since in these cases, checking of observers, polling of ADCs,
and filtering of input values are all heavily software based,
these protections are referred to as software protections.
There are several types of software related protections, solving
a variety of fault conditions:
•
Related to supplies: presence of the +5V, +3V3, +2V5,
+1V2 and +1V1 needs to be measured, no protection
triggered here.
•
Protections related to breakdown of the safety check
mechanism. E.g. since the protection detections are done
by means of software, failing of the software will have to
initiate a protection mode since safety cannot be
guaranteed any more.
Remark on the Supply Errors
The detection of a supply dip or supply loss during the normal
playing of the set does not lead to a protection, but to a cold
reboot of the set. If the supply is still missing after the reboot,
the TV will go to protection.
Protections during Start-up
During TV start-up, some voltages and IC observers are
actively monitored to be able to optimize the start-up speed,
and to assure good operation of all components. If these
monitors do not respond in a defined way, this indicates a
malfunction of the system and leads to a protection. As the
observers are only used during start-up, they are described in
the start-up flow in detail (see section
5.8
Fault Finding and Repair Tips
Read also section
Info".
5.8.1
Ambilight
Due to the aging process on the LED's fitted on the Ambilight
module, there can be a difference in the colour and/or light
output of the spare ambilight modules in comparison with the
originals ones contained in the TV set. Via SAM => alignments
=> ambilight, the spare module can be fine-tuned.
Other possibility: the original values can also be recovered via
SAM, Upload to USB => alignments. Now the original settings
are on the USB stick and can be reloaded into another SSB
(NVM).
back to
div. table
QFU1.2E LA
5.
"5.8 Fault Finding and Repair
"5.3
Start-up").
"5.5 Error
Codes,
5.5.4 Error
EN 31
Buffer,
Extra
2014-Jan-10
Hide quick links:
Advertisement
Table of Contents
