Closed the-duke closed 9 months ago
Ok, i found a solution that works for me in the issue https://github.com/jblance/mpp-solar/issues/389 by editing the jkserial protocol. I deleted all other cell response messages and left only the cells 1-4. now the result data seems to be correct.
Reopening as reminder / tracking Solution needs a variable length decode
passed to decode: b''
Yeah the jkserial protocol is the one needed - but I need to work out how to make it deal with variable length Can you post a BMS response in text form so I can use it for testing (effectively what was in the screenshot from cutecom.log or a debug run using the jkserial protocol) Thanks
implemented in dev branch in powermon using construct library
Of course cutecom.log
I check out the branch jk-variable-length to give it a try
thanks powermon serial probably wont work - I need to adjust it to work for jk serial connections
might work now with latest commit in branch - can you try and post a debug
I am using a JK-B2A8S20P BMS with heating port over a serial connection. The hardware setup seems to work fine (USB-Serial-Adapter connected to the 4-pin GPS-Port).
Wenn i send 4E 57 00 13 00 00 00 00 06 03 00 00 00 00 00 00 68 00 00 01 29 hex sequence via CuteCom to the BMS i receive hex data with the custom BMS name inside.
But the "jkbms -p /dev/ttyUSB0 -P JKV11 -b 115200 -c getInfo -D" command returns parsing errors:
Are there any hints to fix the protocol for my BMS. It may be related to the special software version for the heat port status and heat-current?