Each readout increases "dumb" charge count #4
Replies: 3 comments 3 replies
-
|
I'm unable to replicate that. Are you sure it's just not when you plug in the serial adapter? If you plug in the serial adapter without first starting the Python script, the TX would be high (making J2 high), causing the battery to go into dumb charge mode. |
Beta Was this translation helpful? Give feedback.
-
|
Yes, @mnh-jansson, this is indeed the issue, I am sorry, I was unaware of the battery's behavior. Thanks for clarifying that. I ended up watching [004] Reverse-engineering the Milwaukee M18 Redlink Protocol and have a better idea of the protocol now. I think this would be best fixed in hardware to have a software-controlled pull-up for the J2 line and only starting it when the software decides to do that and initiate the communication. I happy to give this a go if you guys think it makes sense. I am not a big fan of introducing charge cycles by mistake 🙂 Are there other requirements for the communication? I am assuming you are trying to keep the components very simple so people are able to build this from random stuff laying around? |
Beta Was this translation helpful? Give feedback.
-
|
I've placed an order for a custom PCB with a fix for this. In this design i have DTR controlling TX through a N-channel mosfet. This will invert the DTR behaviour and should give the wanted effect. Should be available soon. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hey! Thanks for all the work that went into this.
I started playing with it and noticed each readout increased the "dumb" charge count by one - I am assuming this is just because some handshake needs to take place and battery remembers that as a communication with a charger and thus increases the count?
Not sure if anything can be done about it.
Beta Was this translation helpful? Give feedback.
All reactions