Skip to content
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

[Bug]: Heltec Wireless Tracker Battery issues - possible fix #3760

Closed
madeofstown opened this issue May 1, 2024 · 5 comments
Closed

[Bug]: Heltec Wireless Tracker Battery issues - possible fix #3760

madeofstown opened this issue May 1, 2024 · 5 comments
Labels
bug Something isn't working

Comments

@madeofstown
Copy link
Contributor

Category

Other

Hardware

Heltec Wireless Tracker

Firmware Version

2.3.7.30fbcab

Description

THE PROBLEM
The heltec wireless tracker has poor battery performance and battery monitoring doesn't seem to work at all. It always shows that it is powered by USB and will over drain the battery and potentially cause a fire.

POSSIBLE FIX
There is a recent (within the last 15 days) post on the Meshtastic discourse forums with a potential fix that I'm hoping can be implemented. https://meshtastic.discourse.group/t/heltec-tracker-v1-and-v1-1-power-config/12016/4

Relevant log output

No response

@madeofstown madeofstown added the bug Something isn't working label May 1, 2024
@madeofstown
Copy link
Contributor Author

Turns out my battery monitoring issues were caused by hardware defects. I'm still wondering if the "possible fix" would help with battery life though.

mkgin added a commit to mkgin/meshtastic_firmware that referenced this issue Jun 21, 2024
https://meshtastic.discourse.group/t/heltec-tracker-v1-and-v1-1-power-config/12016/4

WORK IN PROGRESS

TL;DR.

Output high to measure voltage in the same why as other heltec device forces the ESP32 to try to pump 3.3v into the base of Q3.
Solution, use internal pullup and pulldown resistors.
http://community.heltec.cn/t/wireless-tracker-power-consumption/13841/6

Progress so far:

* Hasn't caught fire yet.
* Battery measurements seems ok

TODO:

* Measure current, check voltages at pins.
  * Not in a position to measure or a differences for a few days.
* take a better look at code
* CLA issues? credit to OP?
* check circuit for tracker v1.0

Related to this open issue.
meshtastic#3760
mkgin added a commit to mkgin/meshtastic_firmware that referenced this issue Jun 21, 2024
https://meshtastic.discourse.group/t/heltec-tracker-v1-and-v1-1-power-config/12016/4

WORK IN PROGRESS

TL;DR.

Output high to measure voltage in the same why as other heltec device forces the ESP32 to try to pump 3.3v into the base of Q3.
Solution, use internal pullup and pulldown resistors.
http://community.heltec.cn/t/wireless-tracker-power-consumption/13841/6

Progress so far:

* Hasn't caught fire yet.
* Battery measurements seems ok

TODO:

* Measure current, check voltages at pins.
  * Not in a position to measure or a differences for a few days.
* take a better look at code
* CLA issues? credit to OP?
* check circuit for tracker v1.0

Related to this open issue.
meshtastic#3760
caveman99 pushed a commit to mkgin/meshtastic_firmware that referenced this issue Jul 22, 2024
https://meshtastic.discourse.group/t/heltec-tracker-v1-and-v1-1-power-config/12016/4

WORK IN PROGRESS

TL;DR.

Output high to measure voltage in the same why as other heltec device forces the ESP32 to try to pump 3.3v into the base of Q3.
Solution, use internal pullup and pulldown resistors.
http://community.heltec.cn/t/wireless-tracker-power-consumption/13841/6

Progress so far:

* Hasn't caught fire yet.
* Battery measurements seems ok

TODO:

* Measure current, check voltages at pins.
  * Not in a position to measure or a differences for a few days.
* take a better look at code
* CLA issues? credit to OP?
* check circuit for tracker v1.0

Related to this open issue.
meshtastic#3760
@mkgin
Copy link
Contributor

mkgin commented Jul 24, 2024

I have been ill the past three weeks, better now but a lot of things have piled up. Nice that it has been committed. Let's keep this open for now. I'll try to set up a raspberry pi in the next week to measure current and collect logs to see what the actual difference is.

@geeksville
Copy link
Member

sorry - I just noticed this bug (thanks @GUVWAF !). I think I just pushed identical changes in geeksville@d017fc7 . I'll also be adding a commit tomorrow to fix the Vext enable problem on this board.

@mkgin
Copy link
Contributor

mkgin commented Aug 22, 2024

sorry - I just noticed this bug (thanks @GUVWAF !). I think I just pushed identical changes in geeksville@d017fc7 . I'll also be adding a commit tomorrow to fix the Vext enable problem on this board.

No problem... I've been overloaded this summer.

@fifieldt
Copy link
Contributor

Fixed in d017fc7

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants