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

JP1 pads doesn't match documentation? #1

Open
m-kozlowski opened this issue Nov 6, 2019 · 5 comments
Open

JP1 pads doesn't match documentation? #1

m-kozlowski opened this issue Nov 6, 2019 · 5 comments
Assignees
Labels
bug Something isn't working

Comments

@m-kozlowski
Copy link

Documentation says that in order to reduce charging current to 500mA I need to cut existing trace on JP1 and connect two bottom pads, but it looks to me that pads are, top to bottom:
PAD1: R13 -> PROG1
PAD2: GND
PAD3: R23 -> GND
So doing as docs says we'd end up with PROG1 floating and R23 connecting ground to ground.

@omzlo omzlo self-assigned this Nov 6, 2019
@omzlo omzlo added the bug Something isn't working label Nov 6, 2019
@omzlo
Copy link
Owner

omzlo commented Nov 6, 2019

Well, this is embarrassing: you are absolutely correct. This is a bug in our hardware :-(
The only workaround is to replace R13 with a 2K resistor and keep the original solder trace as is (uncut).

There seems to have been some kind of version mismatch or regression in our production. The correct schematic (from a prior prototype) looks like this:

Screenshot 2019-11-06 at 21 49 34

@meinnamehier
Copy link

So i already cut the trace and soldered across the other pad.
Do i need to revert that? What if I keep it like this?
I only just hooked up a battery last night and read about the bug today.

@m-kozlowski
Copy link
Author

m-kozlowski commented Nov 20, 2019

You're running out of specification. I can't find anything in datasheet about leaving PROG1 floating, so let's just assume you're somewhere far, far right on this chart
You should revert. Or solder another 1K resistor across the cut trace, so you'll have desired 500mA charge current.

@meinnamehier
Copy link

I reverted last night and everything seems to be working fine.
Based on your assumption, at least the current would have been very low instead of catastrophically high.
I just wish that I had bee informed in a more active way about this fault, considering we are dealing with LiPo batteries, that can be dangerous when handled incorrectly.

@omzlo
Copy link
Owner

omzlo commented Nov 21, 2019

I just wish that I had bee informed in a more active way about this fault, considering we are dealing with LiPo batteries, that can be dangerous when handled incorrectly.

We are sorry about this bug, which was only discovered recently thanks to the input provided by @m-kozlowski . This should not have happened of course, and we will correct this in the next version.

As noted above, the simplest way to go down to 500mA charging current is to keep the default trace on JP1 (or bridge it if it has already been cut) and replace R13 with a 2K resistor.

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

No branches or pull requests

3 participants