PHILIPS 32PFL5332 _ SERVICE MODE & LED BLINKING CODES.
PHILIPS 32PFL 5332.
PHILIPS 32PFL 5332.
ENTERING THE [SDM] Service Default Mode.
- Use the standard remote control transmitter and key in the code [062596], directly followed by the "Menu" button. It is possible that together with the SDM, the main menu will appear. To switch it Off, push the Menu button, once again.
- Short the two solder pads on the SSB, with the indication SDM for a moment. These solder pads are located on the top of the SSB. Activation can be performed in all modes, except when the set has the problem with the Standby processor.
- After activating this mode, SDM will appear at the upper right corner of the screen ; if you have picture.
HOW TO NAVIGATE
- When you press the Menu button on the remote control, the set will toggle between SDM and normal user menu, with SDM mode still active in the background.
- To exit from SDM mode,
- Switch the set to Standby via remote transmitter.
- Via a standard customer RC transmitter: Key in "00" sequence.
BLINKING LED PROCEDURE
The blinking LED procedure can be split up into two situations.
- Blinking LED procedure in case of a protection detected by the standby processor. In this case the error is automatically blinks. Therefore you do not have to do anything special, just read out the blinks. A long blink indicate the decimal digit, and a short one 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 blinking LED procedure is
activated in ON state, the front LED will show the contents of error
buffer by blinks. Error code >10 are shown as follows.
- "n" long blinks (where "n"= 1 to 9), indicating decimal digit,
- A pause of 1.5s,
- "n" short blinks (where n = 1 to 9),
- A pause of approx: 3s,
- When all error codes are displayed, the sequence finishes with a LED blink of 3s,
- And the sequence starts again.
Example: Error 12 9 6 0 0
After activation of SDM, the front LED will show:
- One long blinks of 750ms (Which is an indication of the decimal digit), followed by a pause of 1.5s.
- Two short blinks of 250ms followed by a pause of 3s,
- Nine short blinks followed by a pause of 3s,
- Six short blinds followed by a pause of 3s,
- One long blink of 3s to finish the sequence,
- The sequence starts again.
HOW TO ACTIVATE THIS FUNCTION?
- Activate SDM. The blinking front LED will show the entire contents of error buffer (this works in normal operation mode).
- Transmit the commands 'Mute"- "062500" - "OK" with normal remote control. The complete error buffer is shown. Take notice that it take some seconds before the blinking LED starts.
- Transmit the commands "Mute"-"06250x"-"Ok" with a normal remote control, where "x" is the number between 1 and 5. When "x" =1; the last detected error is shown, "x" =2; the second last error etc:- Take notice that it take some seconds before the LED starts blinking.
ERROR -1
I2C bus 1 blocked.
TV will go to protection and the front
LED will blink at 3Hz. Now it can partially restart the TV via SDM
shortcut pins on the SSB. Depending on the software version it is
possible that no further diagnose is possible. With knowledge that only
errors 1,2,4 and 63 result in a 3Hz blinking LED, the range of possible
defects is limited.
ERROR -2
I2C bus 2 blocked.
When this error occurs the TV will go
to protection and the front LED will blink at 3Hz. No can restart the
the TV partially via the SDM shortcut pins on the SSB. Due to hardware
restriction [I2C bus 2 is the fast I2C bus]; it will be not possible to
start up the VIPER and therefore, it is also impossible to read out
error codes via ComPair or via blinking LED method. With knowledge that
only errors 1,2,4 and 63 result in a 3Hz blinking LED, the range of
possible defects is limited. When restarted the TV via the SDM shortcut
pins and then pressed "CH+" on the remote control, the TV will go to
protection again, and the front LED blink at 3Hz again. This could be
an indication that the problem is related to error-2.
ERROR-3
I2C bus 3 blocked.
There are only thre devices on I2C
bus-3. VIPER, Standby processor, and NVM. Standby processor is the
detection device of the error, so this will only occur if the VIPER or
the NVM is blocking the Bus. This error is also be logged when the NVM
gives no acknowledge on the I2C bus. Note that, if the 12V supply is
missing [connector M46 on the SSB], 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 12V can also lead to an error-3.
ERROR-4
I2C bus-4 blocked.
Error-4 is displayed in SAM. No protection.
ERROR-5
Error-5 (Viper doesn't boot)
This error will point to a severe
hardware problem around the VIPER [sypplies not OK, VIPER completely
dead, I2C between VIPER and standby processor broken etc:-.
ERROR-7
Error-7 (8-6V error)
Except a physical problem at the 8.6V itself, it is also possible that there is something wrong with the audio DC protection.
ERROR-12
Error-12 (12V error)
Except a physical problem at the 12V itself, it is possible that there is something wrong with the audio DC protection.
PHILIPS 32PFL5332 - LED BLINKING CODES INORMATION
ERROR-14
Error-14: (Audio supply)
This error is triggered in case of two low voltage of the audio supplies and therefore a drop of audio supply voltage of below approx: 9V per supply rail or lower than 18V rail to rail. Also a DC voltage of higher than 1 VDC on speakers will lead to protection and error 14 blinking. For LCD set, this circuit can be found on schematics SA3, for PDP set this can be found on schematic C. It should be noted that for 26" models there is only a supply link between the amplifers and standby microcontroller, where as in all other models this link is implemented by audio port line- Pin7 on 1 Mo2
ERROR-18
Error-18 (MPIF-1)
Error-18 is displayed in SAM. No protection.
ERROR-21
Error-21(HDMI) switch. When this error occurs the TV will go to protection and the front LED will blink at 3Hz.
ERROR-29
Error-29[AVIP-1]
This error will probably generate extra errors. Will probably also see errors 31(MPIF) and error-31(AVIP 2). Error 29 and 31 will always be logged together due to the fact that both AVIPs are inside the PNX2015 and are on the same I2C bus. In this case, start looking for cause around AVIP(Part ofPNX2015).
ERROR-31
[AVIP 2].
ERROR -34
Error-34 (Tuner-1)
When this error is logged, it is not sure that there is something wrong with the with the tuner itself. It is also possible that there is something wrong with the communication between the channel decoder and tuner.
ERROR-37
Error-37 [Channel Decoder]
This error will always log error 34 (tuner) extra. This is due to the fact that the tuner I2C bus is coming from the channel decoder.
ERROR-44
Error-44 [NVM]
This error will never occur because it is masked by error-3(I2C bus 3). The detection mechanism for error-3 checks on I2C acknowledge of the NVM. If NVM gives no acknowledge, the standby software assumes that this bus is blocked, the tv goes to protection and error-3 will be blinking.
ERROR-53
Error-53 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 initilization problems. Possible cause could be that there is no valid software loaded. Try to upgrade to the latest main software version.
*********************************************************************************