Bugzilla – Bug 12861
LCD Rain problem
Last modified: 2009-09-08 09:16:40 UTC
James & Steven noticed that the PA5 boards have the LCD 'Rain' problem. Verified with Ricahrd's board, it has it too. The root cause is too much ripple on the 3.3V power supply. I have not been able to determine the reason for the differences in ripple from board to board, but there is a significant difference from one board to another. Presumably, this is due to capacitor or inductor variation. The capacitors look like not too much variance. The bad board's capacitors were the specified 10uF. I have not measured the inductors yet. This issue was reported by SZ on PB1, but not on PB2. We got 1 PCB in MV from SZ that was supposed to have the rain problem, but we didn't see the issue on that board. Since we never saw the issue here, we never knew to look at the power supply for the problem. By doubling the capacitance from 2x10uF to 4x10uF on the 3.3V rail, it virtually eliminates the rain on the worst offending board. There is still a very slight amount left, but it's nearly undetectable. By going another 50% to 6x10uF, it's undetectable. We can get 22uF and even 47uF capacitors in the same 0805 size, so we will be able to resolve this issue with a component change only (no PCB change). The plan is to change the 2x10uF to 2x22uF caps (111650-A226). Some of these caps are on order from digikey, and the solution will be verified july 15. MPQ will proceed as planned.
Steven, could you describe the symptom so that I can keep an eye out for this here at the factory? Thanks!
Looking at the baby display in its normal orientation the "rain" effect looks to me like thin vertical bars of distortion on the display that run the entire screen from top to bottom that seem to shimmy horizontally and are always in motion. Almost like little ripples or waves moving across the screen horizontally. I seem to remember we had the same issue on some of the early jive displays.
Updated BOM under MP1 directory.
Updated BOM in Agile for SZ Mfg.
Reopening and sending over to chris for final closure after the MPQ build.
This can be "resolved, fixed" for now and I will mark it "closed" after MP (if it turns out to be true)