Error Codes - Philips FTL2.4E Service Manual

Stepwise start- up explanation
This is realised via ComPair and is very helpful when a
protection is activated (see also chapter "Protections"). The
following diagram shows the start-up procedure of the set.
Every step of the stepwise start-up (also called trapped start-
up) in the diagram corresponds with the number of times the
led blinks.
Mains cord IN
OTC gets supply voltage
OTC resets, Initialise IO pins
Read NVM identification
start time extraction
start P50 recording
start EPG loading Stand-by
Standby bit = off
Ambient light ON
Trapped Startup 1
Put Stand-by line LOW
CPU GO becomes HIGH
Set STBYEN,VCCON,PFCON = 1
Only FHP (opt 2, 8)
Keep sound amplifiers muted with
sound enable = high
+5V and +8V is switched on
+8V and +5V get their nominal level,
detected by the OTC
activate protection algorithms for +8V and +5V and
I²C (start I²C protection the moment the component
is initialised).
Trapped Startup 2
Read rest of NVM information
Initialize HIP: IF, source selection, 2fh input, video
processing
Switch on the syncoutput: set_syncout_tristate= off
Initialize tuner
Initialize 3D Combfilter
or Initialize Columbus
Initialize PICNIC + screen info
Initialize rest of PIP/DW module
Start TXT acquisition
and time extraction
Reset Audio = low
and Initialize MSP
Initialize EBILD
Screen type
Start up LCD Initialize PDP FHP
opt 3,4,5,6
opt 2,8
Figure 5-4 Stepwise start-up part 1
Start up LCD Start
Stand-by bit set ?
yes
Trapped Startup 3 Semi stand by
Figure 5-5 Stepwise start-up part 2
Note: When the set is in stepwise mode and, due to stepping-
up, a protection is activated, the set will really go into protection
(blinking LED). The set will not leave the stepwise-mode
however. If state X is the state where the set went to protection,
stepwise start-up will return to state X-1. At state (X-1)
diagnostic measurements can be performed. Also, in the short
time the set is in state X but not yet in protection, you can also
do some measurements.
Service Modes, Error Codes, and Fault Finding
OUT
Reset Audio=high
enable watchdog
Tact switch
OFF
Stand-by bit = OFF
400msec>t>200msec
Initialize PDP SDI
E_14620_048.eps
opt 0,1,7
no
LCD ON
Ebild Power ON
Output Blanking OFF
LAMP ON
ON Trapped Startup 4
E_14620_049.eps
5.4.2 LVDS Tool
Introduction
This service tool (also called "ComPair Assistant 1") may help
you to identify, in case the TV does not show any picture,
whether the Small Signal Board (SSB) or the display of a Flat
TV is defective.
Furthermore it is possible to program EPLDs with this tool
(Byteblaster). Read the user manual for an explanation of this
feature.
Since 2004, the LVDS output connectors in our Flat TV models
are standardised (with some exceptions). With the two
delivered LVDS interface cables (31p and 20p) you can cover
most chassis (in special cases, an extra cable will be offered).
When operating, the tool will show a small (scaled) picture on
a VGA monitor. Due to a limited memory capacity, it is not
possible to increase the size when processing high-resolution
LVDS signals (>= 1280x768). Generally this tool is intended to
determine if the SSB is working or not. Thus to determine if
LVDS, RGB, and sync signals are okay.
How to Connect
Connections are explained in the user manual, which is
delivered with the tool.
Note: To use the LVDS tool, you must have ComPair release
2004-1 (or later) on your PC (engine version >= 2.2.05).
For every TV type number and screen size, one must choose
the proper settings via ComPair. The ComPair file will be
updated regularly with new introduced chassis information.
How to Order
• LVDS tool (incl. two LVDS cables: 31p and 20p):
3122 785 90671.
• Service Manual LVDS tool:
3122 785 00810.
5.5

Error Codes

5.5.1 Introduction
The error code buffer contains all detected errors since the last
170504
time the buffer was erased. The buffer is written from left to
right, new errors are logged at the left side, and all other errors
shift one position to the right.
When an error has occurred, the error is added to the list of
errors, provided the list is not full or the error is a protection
error.
When an error occurs and the error buffer is full, then the new
error is not added, and the error buffer stays intact (history is
maintained), except when the error is a protection error.
To prevent that an occasional error stays in the list forever, the
error is removed from the list after 50+ operation hours.
When multiple errors occur (errors occurred within a short time
span), there is a high probability that there is some relation
between them.
5.5.2 How to read the Error Buffer
170504
Use one of the following methods:
• On screen via the SAM (only if you have a picture).
Examples:
– 0 0 0 0 0: No errors detected
– 6 0 0 0 0: Error code 6 is the last and only detected
error
– 9 6 0 0 0: Error code 6 was first detected and error code
9 is the last detected error
• Via the blinking LED procedure (when you have no
picture). See next paragraph.
• Via ComPair.
FTL2.4E AA 5. EN 17