-
Notifications
You must be signed in to change notification settings - Fork 122
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Drop voltage on 3.3V rail after enabling prw_en pin #98
Comments
Same problem on T5+. I note the original T5 does not seem to have this issue. Did the 1000uF fix it? |
Yes, the 1000uF capacitor will prevent the power supply from dropping below 3V. Although this is a fairly short peak, the restart appears to be random. Instead of a capacitor, adding a delay (20 ms) right after switching on the display power branch also helped us a lot. |
1mF capacitor for such small project is totally wrong design. It might be a solution but for sure it is a mistake of the design. Btw where does this 0.89A go? |
Yes, for this type of design, a 1mF capacitor is not the right solution. For example, with LTE 2G, it would mostly be necessary. From the measurements, we found that the pulse is generated when the DC/DC converter LT1945 and display are switched on. (The greatest credit goes to the LT1945 power supply circuit with accompanying regulators) |
from the datasheet of LT1945 it has a limit to 350mA however, the peak current can reach easily even 1A - after 0.1ms the regulator is OFF completely. |
after reviewing the schematic for the T5-PLUS board, and looking at the driver code, I am confused. 1/ epaper power supply control: For power on, it sets bits named "scan_direction=true", "power_disable=false", "neg_power_enable=true", "pos_power_enable=true" and "ep_stv=true", in order, with a delay between them. For power_off, its "pos_power_enable=false", "neg_power_enable=false", "power_disable=true", "ep_stv=false", again in order iwth a delay. HOWEVER:
Where did you add the 20ms delay to avoid the brownout? Is this right? If so, I think some fixes are required in the code:
thanks! |
One of my boards is very sensitive to the voltage drop, the other less so. A 470uF electrolytic across VDD_3V3 seems to fix it, but is kind of ugly. |
Hi all, My board seems to have either a similar, or at least a related issue. It works fine when I have battery attached to BAT. Without battery, it's very picky about power source. It works with some USB ports and non-brand USB wall adapters. It does not work with Apple 5W and 10W wall adapters, as well as with some power banks. I was unable to find a correlation between voltage on VBUS and whether the board works. It works fine with some USB ports providing 4.85V and wall adapters with 5.1V, and does not work with other adapters that give 5.1V on VBUS. What does it mean? When the board does not work, the green LED lights for a few seconds, and then red LED lights. The blue LED never starts. This is what's happening on VBUS (4.85V): In the same time, 3V3 line looks like (my oscilloscope is single-channel, so these are actually different measurements): This is what's happening on VBAT: Do you have any ideas what's going on here? I also tried the sketch in the first message here (with delays of 2000ms), this is what 3V3 line looks line on I haven't tried adding large capacitor to 3V3 yet. I also have other modifications: #93 (comment) (I removed the 22pF capacitors later, only 47uF is in place). |
We using and testing LilyGo 4,7 Plus and have a problem with resetting ESP32 after enabling display with sequences epd_init and epd_poweron. We found a bug on PCB. Enabling display generating 0.9A peak and voltage level on LDO 3.3V drop to 2.2V. There is ESP32 randomly resetting. Used LDO doesn't have the capacity for this current peak. I am testing adding a blocking capacitor on 3.3V rail and 1000uF value can be blocking this peak when the voltage doesn't drop under 3V.
Testing code:
Current measured:
The first sequence is correct and the next is wrong.
The voltage on 3.3V supply during a current surge:
Have you encountered this problem too? Do you have any solution for this?
The text was updated successfully, but these errors were encountered: