PHILIPS BJ 3.0E CHASSIS- 37 INCH LCD POWER SUPPLY- ERRORS CODES
PHILIPS BJ 3.0E CHASSIS- 37 INCH
Error Codes
Introduction
The error code buffer contains all detected errors
since the last 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 occurs, it is added to the list of errors, provided the list is
not
full. 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 more than 50 hrs. of operation. When
multiple errors occur (errors occurred within a short time span),
there is a high probability that there is some relation between them.
Basically there are three kinds of errors:
* Errors detected by the Stand-by Processor. These errors will always lead to
protection and an automatic start of the blinking LED for the concerned error
(see paragraph “The Blinking LED Procedure”). In these cases SDM can be used to
start up (see chapter “Stepwise Start-up”). Note that it can take up to 90
seconds before the TV goes to protection and starts blinking the error (e.g.
error 53)
* Errors detected by VIPER that lead to protection. In this case the TV will go
to protection and the front LED should also blink the concerned error.
Depending on the software version it is possible that this mechanism does not
work. See also paragraph “Error Codes” -> “Error Buffer” -> “Extra Info”.
* Errors detected by VIPER that do not lead to protection. In this case the
error will be logged into the error buffer and can be read out via ComPair, via
blinking LED method, or in case you have picture, via SAM.
How to Read the Error Buffer
Use one of the following methods:
* On screen via the SAM (only if you have a picture). E.g.:
– 00 00 00 00 00: No errors detected
– 06 00 00 00 00: Error code 6 is the last and only detected error
– 09 06 00 00 00: Error code 6 was first detected and
error code 9 is the last detected error
– 00 00 00 00 00: No errors detected
– 06 00 00 00 00: Error code 6 is the last and only detected error
– 09 06 00 00 00: 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.
How to Clear the Error Buffer Use one of the
following methods:
* By activation of the “RESET ERROR BUFFER” command in the SAM menu.
* With a normal RC, key in sequence “MUTE” followed by “062599” and “OK”.
* If the content of the error buffer has not changed for 50+ hours, it resets automatically.
* With a normal RC, key in sequence “MUTE” followed by “062599” and “OK”.
* If the content of the error buffer has not changed for 50+ hours, it resets automatically.
Error Buffer
In case of non-intermittent faults, clear the error buffer before you begin the
repair (before clearing the buffer, write down the content, as this history can
give you significant information).
This to ensure that old error codes are no longer present. If possible, check the
entire contents of the error buffer. In some situations, an error code is only
the result of another error code and not the actual cause (e.g., a fault in the
protection detection circuitry can also lead to a protection).
There are several mechanisms of error detection:
* Via error bits in the status registers of ICs.
*Via polling on I/O pins going to the stand-by processor.
* Via sensing of analogue values on the stand-by processor or the Viper.
* Via a “not acknowledge” of an I2C communication Take notice that some errors need more than 90 seconds before they start blinking. So in case of problems wait 2 minutes from start-up onwards, and then check if the front LED is blinking.
* Via error bits in the status registers of ICs.
*Via polling on I/O pins going to the stand-by processor.
* Via sensing of analogue values on the stand-by processor or the Viper.
* Via a “not acknowledge” of an I2C communication Take notice that some errors need more than 90 seconds before they start blinking. So in case of problems wait 2 minutes from start-up onwards, and then check if the front LED is blinking.
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 compare interface and Hyperterminal (for
Hyperterminal settings,). 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.
* Error 1 (I2C bus 1 blocked). When this error occurs, the TV will go to
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 ignore the
error. Depending on the problem it is even possible that you have picture.
* Error 2 (I2C bus 2 blocked). Due to hardware restriction (I2C bus 2 is the
fast I2C bus) it will be impossible to start up the VIPER when I2C bus 2 is
blocked. When this error occurs, the TV will not start up (but probably you
will seethe green LED). 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 (allthough
it will be logged). Use ComPair for further diagnose (e.g. read out the NVM content).
* Error 3 (I2C bus 3 blocked). There are only three devices on I2C 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 I2C 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 I2C bus 3. So, a missing 12 V can also lead to an error 3.
* Error 4 (I2C 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, I2C link
between VIPER and 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 theaudio 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 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 (I2C bus 3). The detection mechanism for error 3 checks on an I2C
acknowledge of 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.
* 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.
Note that it takes 90 seconds before the TV goes to protection in this case.
* Error 55 (SPIDER error). Same remark as for error 27.
* 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 I2C communication towards the display. Allthough several
display types communicate via I2C, this error will only work for TV’s with a
FHP display.
The Blinking LED Procedure
Introduction
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:
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. 1 long blink of 3 s to finish the sequence,
6. The sequence starts again.
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. 1 long blink of 3 s to finish the sequence,
6. The sequence starts again.
