AlexanderHusta wrote: ↑Fri Sep 04, 2020 6:12 pm
I am sorry to say but the part of your post claiming that the keep alive signal is always the same few bytes is wrong. The ES200 uses some kind of rolling code as a heart beat between IoT and BMS. Each heartbeat message differs from the ones before. Afaik this code was yet not broken.
This is not the case for the ES200G. I know this for a fact, because I logged it myself. The motor controller sends 0x3A, 0x13, 0x01, 0x16, 0x79 every five sec, to which the battery replies with a status report (the reply changes, depenging on various factors, but its not important, if you just want to keep the battery from blocking you can ignore the reply alltoghether.)
I've used the battery in a different project, and by just feeding it with this signal every 5 sec it works perfectly fine.
Edit: ES200G, not E200G