When did the M18 batteries first start supporting the serial diagnostics? #30
-
|
I have an older Milwaukee M18 Red Lithium battery that has a "REV03 JUL-32-2014" revision/date code on the BMS circuit board (I do not have the case for the battery so cannot determine the actual manufacturing date from the label). Anyway, when using the "m18.py" tool to read the serial diagnostics, I get unexpected results in the responses from the battery. As an example, when using the "m.health()" command, with debugging enabled, the initial command bytes and responses for the "force_refresh" of the "read_id()" function are as follows: ` I thought the correct response to a '01' command started with an '81' not an '82'. Is what I am seeing the result of a battery that is too old to actually support the serial diagnostics? Thanks. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
Yes, too old. I have a battery from May 2015 (case date) that supports UART communication in charging, but gives mostly no data on diagnostics. So you can prob do m.simulate() and get it to return valid charging messages, but no diagnostics. Earliest diagnostics I've seen is May 2016. |
Beta Was this translation helpful? Give feedback.
Yes, too old. I have a battery from May 2015 (case date) that supports UART communication in charging, but gives mostly no data on diagnostics. So you can prob do m.simulate() and get it to return valid charging messages, but no diagnostics. Earliest diagnostics I've seen is May 2016.