-
Notifications
You must be signed in to change notification settings - Fork 112
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
Repetitive brownout reset upon power-on when battery is not connected #3
Comments
I ran into the same thing today (just got my two boards yesterday). I happened to have a D-Link powered hub that does allow it to power up, but any of my other powered hubs do not. The lack of documentation is abysmal. Their "BBS" is down. No schematics. No indications as to what the LEDs are for. Seems to come with some soft of flight controller software installed, once you manage to guess the password to the soft AP ('12345678'). If they're to be taken seriously, they're going to need to put some effort into providing at least some minimal semblance of documentation. |
They send schematics upon request. AFAIK, 2 LEDs are for battery status. One is for GPS PPS. And one is software controlled (GPIO14) They ship the board with my firmware been pre-installed, free of charge. If you don't need built-in firmware - just overwrite it with your own one. |
I've noticed that TTGO BBS is up today. |
TTGo is terrible I have been looking for docs for days.. :( Icant access to the AP with de "12345678"key with the SoftRF firmware, The Schematics are wrong... The LilyGo repository doesnt have explanation... what a mess!! |
Wait until you find out that your NEO-M6M GPS is probably a Chinese counterfeit. I had to order a couple NEO-M8Ms to replace mine. I already had code that speaks UBX protocol to a uBlox GPS, and it wasn't working on the T-Beam. Determined it wasn't responding to NMEA commands, the UBX messages were ignored, etc. Swapped in the NEO-M8M's, boom, worked the first time. |
Hi Have ordered a whole class set of these T-Beam boards for a highschool programming class. Do these boards work fine off of a 18650 battery in the holder? I have ttgo lora32 v1 and it works fine, but have just found that the v2 reboots due to brownout when starting bluetooth or wifi when using the same code on ttgo lora32 v2 Starting with USB power plugged in, and then removing it to just be battery powered works fine, but cold booting or resetting on battery only makes is brownout Thanks |
The modules work fine with battery powered or with cap changed as lyusupov shows. I have two of them. |
Thanks for getting back to me. Great to hear. All students will be getting a T-Beam,18650, USB cable, female pin headers and a 128x64px OLED. I guess they won't experience any power issues as the 18650 will always be connected. Almost made the mistake of buying a class set of the TTGO Lora32 v 2.1 Was almost going to pull the trigger on them until I read the charging circuit is wired incorrectly and batteries overcharge and blow up! Me thinks they should test a little more before releasing these boards. |
Saving costs! xD |
All 32 boards work fine off battery |
The boards work fine with a 18650 mounted, however 500mA via USB are not enough for permanent operation as SoftRF in Legacy mode, and the power supply is quite weak to power additional equipment like OLED, RS232 driver, without a battery as buffer. So my conclusion is you need a 18650 and a powerful power supply. |
it is possible to replace the battery 18650 with lipo battery.. because the 18650 is to big and it make the casing also big |
With appearance of V10 (a.k.a. V1.0) revision of T-Beam"s hardware this issue is no longer pertinent. |
Hardware: T-Beam T22_V06 20180706
Firmware: SoftRF 1.0-rc4+
Power is supplied from 2A rated 5V power source.
18650 battery is not connected.
The board does not start well.
UART log contains repetitive lines:
"+5V" supply voltage been measured at power switch point with assistance of a DSO shows significant
drop, quite similar to this picture:
I had quite similar issue with my own ESP32-based design. I've resolved it by additional 1000uF capacitance. Please, read this issue for details.
Solution for this issue is full up to you !
I would just suggest you to try to increase value of C47:
The text was updated successfully, but these errors were encountered: