The Blinking Led Procedure - Philips 42PF9731D Service Manual

EN 34 5. BJ2.4U/BJ2.5U LA
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 recognized 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). When this error occurs, the
TV will go to protection and the front LED will blink error 1.
Now you can partially restart the TV via the SDM shortcut
pins on the SSB. Depending on the software version it is
possible that this error will not work correct: in some
software versions error 34 was blinking in stead of error 1.
2
• Error 2 (I C bus 2 blocked). When this error occurs, the
TV will go to protection and the front LED will blink error 2.
Now you can partially restart the TV via the SDM shortcut
pins on the SSB. Due to hardware restriction (I
2
the fast I C bus) it will be impossible to start up the VIPER.
When this error occurs, the TV will probably keep
rebooting. Further diagnose has to be done via ComPair.
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
acknowledge on the I
12 V supply is missing, the DC/DC supply on the SSB will
not work. Therefore the VIPER will not get supplies and
2
could block I C bus 3. So, a missing 12 V can also lead to
an error 3.
2
• Error 4 (I C bus 4 blocked). When this error occurs, the
TV will go to protection and the front LED will blink error 4.
Now you can start up the TV via the SDM short-cut pins on
the SSB. The TV will start up and ignore the error.
Depending on the problem it is even possible that you have
picture.
• 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 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 protection). The detection is done on the
audio board itself. Several items are monitored:
overvoltage, overcurrent, audio supply voltages and the
DC level on the speakers. If one of these items fails, the
audio protection 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 error codes. In case
this device can not communicate with the Viper via I²C, it
will not be possible to initialize 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
is logged in the NVM (that's why this error is still mentioned
here).
• Error 16. See remark for error 32.
• Error 17. See remark for error 32.
• Error 18(MPIF1). See also remark for error 32.
• Error 29 (AVIP 1). Same remark as for error 27.
• Error 31 (AVIP 2). Same remark as for error 27.
• Error 32 (MPIF1). Together with error 32, it is possible you
will see error 16,17 and 18 along. These errors are no
longer valid.
• 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
Service Modes, Error Codes, and Fault Finding
2
C bus 2 is
2
C bus (see error 44). Note that if the
2
C link between VIPER and
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 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 behavior is an indication of a
Pacific problem.
• 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.
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.
2
C bus 3). The detection
2
C acknowledge of