Hey! I have an LN-S3241DX that I think has a bad t-con board but I wanted to check here to see if anyone had any ideas on anything else I could do to conrifm the issue
Occasionally, colored vertical lines would appear across the screen and the screen would freeze while slowly turning black. Usually, if I just power cycled the TV this would go away.
Slowly it's started happening more and more and starting a few days ago it would happen shortly after turning the set on. Power cycling would still work, but it would only last a short amount of time (less than 1 minute). Sometimes the screen would exhibit the symptoms and would pop back to normal before doing it again after a little while.
I took apart the panel to see if I see anything obvious and at first, flexing the tcon board and reseating the ribbon cables seemed to help but that might have just been a coincidence. From there the symptoms got a bit worse and now it just powers on with no picture (the backlight does come on). I did run it for a bit with the panel off the main board so I could check values and that had a heatsink touching the video processing (STP03) chip which did get a bit hot to the touch.
Here is an example of a picture I managed to get 1 time it happened (this was September of last year so it's been mostly fine for the last 4 months)
The output voltages of the power board match the values written on the board so I don't think it's that (although there are a few caps that look a little suspect)
Checking the connector off of the main board to the t-con the powered pins are reading 5.4v or 1.2v, The tv turns on via the remote and panel buttons and functions work (changing input, volume, setting the sleep timer - you can't see them, but I've had it long enough I can set this without needing to see the screen)
Power levels on the t-con board seems suspiciously low. The test points near the main board connector (RX1. RX2. RX3) read 1.2v, the voltage regulator (U14) reads 2.5mV, the fuse (F1) reads between 20 and 100mv, and the value for all of the GAMMA test points fluctuate pretty wildly.
Does that seem like a t-con issue or something else? Anything else to check?
Thanks!
Occasionally, colored vertical lines would appear across the screen and the screen would freeze while slowly turning black. Usually, if I just power cycled the TV this would go away.
Slowly it's started happening more and more and starting a few days ago it would happen shortly after turning the set on. Power cycling would still work, but it would only last a short amount of time (less than 1 minute). Sometimes the screen would exhibit the symptoms and would pop back to normal before doing it again after a little while.
I took apart the panel to see if I see anything obvious and at first, flexing the tcon board and reseating the ribbon cables seemed to help but that might have just been a coincidence. From there the symptoms got a bit worse and now it just powers on with no picture (the backlight does come on). I did run it for a bit with the panel off the main board so I could check values and that had a heatsink touching the video processing (STP03) chip which did get a bit hot to the touch.
Here is an example of a picture I managed to get 1 time it happened (this was September of last year so it's been mostly fine for the last 4 months)
The output voltages of the power board match the values written on the board so I don't think it's that (although there are a few caps that look a little suspect)
Checking the connector off of the main board to the t-con the powered pins are reading 5.4v or 1.2v, The tv turns on via the remote and panel buttons and functions work (changing input, volume, setting the sleep timer - you can't see them, but I've had it long enough I can set this without needing to see the screen)
Power levels on the t-con board seems suspiciously low. The test points near the main board connector (RX1. RX2. RX3) read 1.2v, the voltage regulator (U14) reads 2.5mV, the fuse (F1) reads between 20 and 100mv, and the value for all of the GAMMA test points fluctuate pretty wildly.
Does that seem like a t-con issue or something else? Anything else to check?
Thanks!
Comment