diy solar

diy solar

JK-BMS-CAN with new Cut-Off Charging Logic (open-source)

chaosnature said:
I have just left the S3 setup alone for now until there is an official YAML file release for it....i too experienced the loop talked about and i don't think its HA as i can flash wireless and the module works as it should do.
Click to expand...
If you look at my repo and the latest changes i described here based on @MrPablo feedback, it should work ...

I'll update my repo when I get back to the main house. Here in the garage it's a mess and don't have passwords etc :rolleyes: .
 
@MrPablo Is there a way to see if the CAN communication is being initiated from the ESP32 ? Possibly via Webserver / Home Assistant ?

Something seems to be happening ESP32 wise for CAN
1711290062334.png

But inverter still sees nothing. Maybe I need to swap CAN_H and CAN_L :rolleyes:
 
Last edited:
silverstone said:
@MrPablo Is there a way to see if the CAN communication is being initiated from the ESP32 ? Possibly via Webserver / Home Assistant ?
Click to expand...
What is the CANbus Status sensor state?
If off then that suggests that the inverter is not sending an acknowledgement message.
If that's the case, either the CAN wiring is the wrong way around or possibly wrong profile is selected on the inverter.
 
MrPablo said:
What is the CANbus Status sensor state?
If off then that suggests that the inverter is not sending an acknowledgement message.
If that's the case, either the CAN wiring is the wrong way around or possibly wrong profile is selected on the inverter.
Click to expand...
1711290323967.png

Unknown ...

I reversed PIN 4 and PIN 5 now and power cycled the Atom S3 Lite ...

EDIT: now it's doing the same but it seems like the Deye Inverter isn't answering (Still NOT in "Normal" state)
1711290871927.png

Are we sure about those "cutoff" values ? 3.62V seems VERY high for my configuration ...
Is the ESP32 taking the OVP value stored in the JK BMS ???
 
Last edited:
@Sleeper85: if I recall correctly you were using lithium 00 profile and PYLON profile for your Deye, correct ?

I'm doing the same and something is obviously not working in my case. I reversed pin 4 and pin 5 to make sure CAN_L and CAN_H weren't swapped up. But neither seem to work. Inverter gets 100% SOC, all cell voltages are 0.0V and goes full power by default. "Normal" LED on inverter is NOT lit up (something is wrong basically).

I am using Deye SUN-12K-SG04LP3-EU if that helps.

I tried to change to Pylon 1.2 instead of Pylon+ now ...

1711291374857.png
 
Last edited:
Hold on, cell voltages are zero?
This means you do not have data flowing from the BMS to the ESP32.

If wired, you would check the wiring between BMS and ESP32.
If over BLE, ensure that the MAC address set up in the YAML is correct. I don't know for certain but I also think that only one BLE connection can be made to the BMS at a time. If the app or another ESP32 is connected, that may block it.
 
MrPablo said:
Hold on, cell voltages are zero?
This means you do not have data flowing from the BMS to the ESP32.

If wired, you would check the wiring between BMS and ESP32.
If over BLE, ensure that the MAC address set up in the YAML is correct. I don't know for certain but I also think that only one BLE connection can be made to the BMS at a time. If the app or another ESP32 is connected, that may block it.
Click to expand...
Nonono ... JK BMS -> ESP32 WORKS correctly (I can see the data in Home Assistant / MQTT).

The issue is ESP32 <--> DEYE

Strangely enough on the Webserver it doesn't look like it saves any change in CAN Protocol.
Is this normal ?
 
Hi guys, related to this thread, I just created a new post (listed below) asking someone to explain the main benefit of having the JK-BMS talking to the inverter.

Are there any safety advantages or any battery longevity advantages? Just the fact that they can talk to each other and maybe you can do different charging schemes, for example, by itself, is not a major incentive (at least in my case), to try to connect them.

If someone here could respond it would be much appreciated.
Thank you! Here's the post:
diysolarforum.com

Connecting JK-BMS to Inverter - Any major advantage?

The newer version of the JK-BMS will talk to inverters, and there's a project to allow the JK-BMS to talk to the inverter. It would mean my JK BMS could talk to my Deye inverter. Sure it's cool, I get it. Maybe you can implement some cool charging strategies, etc., but beyond things like that...
diysolarforum.com diysolarforum.com
 
kolek said:
Hi guys, related to this thread, I just created a new post (listed below) asking someone to explain the main benefit of having the JK-BMS talking to the inverter.

Are there any safety advantages or any battery longevity advantages? Just the fact that they can talk to each other and maybe you can do different charging schemes, for example, by itself, is not a major incentive (at least in my case), to try to connect them.

If someone here could respond it would be much appreciated.
Thank you! Here's the post:
diysolarforum.com

Connecting JK-BMS to Inverter - Any major advantage?

The newer version of the JK-BMS will talk to inverters, and there's a project to allow the JK-BMS to talk to the inverter. It would mean my JK BMS could talk to my Deye inverter. Sure it's cool, I get it. Maybe you can implement some cool charging strategies, etc., but beyond things like that...
diysolarforum.com diysolarforum.com
Click to expand...
In a few words I'd say ... PREVENTION instead of PROTECTION ;). Let cells time to balance out. Avoid OVP and UVP as much as possible.

I used to think it wasn't necessary ,.. until one battery started getting more and more unbalanced and I hit OVP all the time, 5 disconnections an hour each day, etc. Long term that can damage BMS ... So it's better if inverter reduces load (current) as well as voltage near the top of the charge (or discharge) rather than the BMS cutting out "at full load".
 
@MrPablo: the mystery deepens ... In the webserver, it states

jk-bms-bat02 CANBUS Status = OFF (NOT UNKOWN !)

I reversed the RJ45 pin 4 and 5 to how it was originally

1711292483669.png

Why is it OFF and not ERROR or something ?

The ESP32 rebooted on its own by the way ...
 
silverstone said:
In a few words I'd say ... PREVENTION instead of PROTECTION ;). Let cells time to balance out. Avoid OVP and UVP as much as possible.

I used to think it wasn't necessary ,.. until one battery started getting more and more unbalanced and I hit OVP all the time, 5 disconnections an hour each day, etc. Long term that can damage BMS ... So it's better if inverter reduces load (current) as well as voltage near the top of the charge (or discharge) rather than the BMS cutting out "at full load".
Click to expand...
@silverstone Ok that is compelling. I appreciate your response.

I already have a couple of the older JK (JK-B2A24S20P) that are still in the box and haven't been connected. Is it a better idea to sell those and buy the new JK-BMS that has this feature built in, or do the approach described in this thread with my existing older JK-BMS models?
 
kolek said:
@silverstone Ok that is compelling. I appreciate your response.

Can I follow up with 2 questions?

I already have a couple of the older JK (JK-B2A24S20P) that are still in the box and haven't been connected. Is it a better idea to sell those and buy the new JK-BMS that has this feature built in, or do the approach described in this thread with my existing older JK-BMS models?
Click to expand...
Don't know. Don't know.

I am also buying NEW (OLD model without inverter feature) JK BMS ... It's better to NOT have 300 different variations. In terms of footprint, they are also quite different. I don't really have the space for the new one.

Maybe for you it's better to just get the new one instead ... Make sure you correctly upgrade the firmware based on Andy findings from Off Grid Garage. There was a nasty bug resetting everything to Li-Ion (NOT LFP !) in case an invalid parameter was entered (and no warning was issued).

Your OVP will NOT work in that case, so make sure you check that and upgrade accordingly !

Old BMS ... meh ... you cannot upgrade firmware anyways :rolleyes:
 
silverstone said:
@MrPablo: the mystery deepens ... In the webserver, it states

jk-bms-bat02 CANBUS Status = OFF (NOT UNKOWN !)

I reversed the RJ45 pin 4 and 5 to how it was originally

View attachment 204234

Why is it OFF and not ERROR or something ?

The ESP32 rebooted on its own by the way ...
Click to expand...
If you are reviewing logs via the web server, you're likely hitting memory limits on the ESP32. That's likely causing the reboots.

As for inverter comms, I don't have a Deye so know nothing about the settings.
 
MrPablo said:
If you are reviewing logs via the web server, you're likely hitting memory limits on the ESP32. That's likely causing the reboots.

As for inverter comms, I don't have a Deye so know nothing about the settings.
Click to expand...
Is there an alternative way to view logs ? Besides pulling a 10m USB extension lead to my laptop of course :rolleyes: ...

Should I disable the Webserver ?
 
Last edited:
@Sleeper85 : Assuming Lithium 00, Pylon, Pylon+ (tried also Pylon1.2) are correct, then are we sure that RJ45 pin 4 + 5 are correct for CAN communication ?

I tried to reverse pin 4 + 5 but nothing changes ...
 
paulsteigel said:
I recommend not to use web server but MQTT or API (if you have the Esp in the same network) Web server chew up memory quickly and alot!
Click to expand...

Looks like i'll need to test how OTA works after all :rolleyes: .

But for instance changing CAN name or CAN protocol via MQTT is NOT supported ... (or at least, it's not in home assistant)
 
No OTA joy.

It does NOT even ask for OTA password ...

Code: 
Requirement already satisfied: esphome in ./venv/lib/python3.11/site-packages (2024.3.0)
Requirement already satisfied: cryptography==42.0.2 in ./venv/lib/python3.11/site-packages (from esphome) (42.0.2)
Requirement already satisfied: voluptuous==0.14.2 in ./venv/lib/python3.11/site-packages (from esphome) (0.14.2)
Requirement already satisfied: PyYAML==6.0.1 in ./venv/lib/python3.11/site-packages (from esphome) (6.0.1)
Requirement already satisfied: paho-mqtt==1.6.1 in ./venv/lib/python3.11/site-packages (from esphome) (1.6.1)
Requirement already satisfied: colorama==0.4.6 in ./venv/lib/python3.11/site-packages (from esphome) (0.4.6)
Requirement already satisfied: icmplib==3.0.4 in ./venv/lib/python3.11/site-packages (from esphome) (3.0.4)
Requirement already satisfied: tornado==6.4 in ./venv/lib/python3.11/site-packages (from esphome) (6.4)
Requirement already satisfied: tzlocal==5.2 in ./venv/lib/python3.11/site-packages (from esphome) (5.2)
Requirement already satisfied: tzdata>=2021.1 in ./venv/lib/python3.11/site-packages (from esphome) (2024.1)
Requirement already satisfied: pyserial==3.5 in ./venv/lib/python3.11/site-packages (from esphome) (3.5)
Requirement already satisfied: platformio==6.1.13 in ./venv/lib/python3.11/site-packages (from esphome) (6.1.13)
Requirement already satisfied: esptool==4.7.0 in ./venv/lib/python3.11/site-packages (from esphome) (4.7.0)
Requirement already satisfied: click==8.1.7 in ./venv/lib/python3.11/site-packages (from esphome) (8.1.7)
Requirement already satisfied: esphome-dashboard==20240319.0 in ./venv/lib/python3.11/site-packages (from esphome) (20240319.0)
Requirement already satisfied: aioesphomeapi==23.1.1 in ./venv/lib/python3.11/site-packages (from esphome) (23.1.1)
Requirement already satisfied: zeroconf==0.131.0 in ./venv/lib/python3.11/site-packages (from esphome) (0.131.0)
Requirement already satisfied: python-magic==0.4.27 in ./venv/lib/python3.11/site-packages (from esphome) (0.4.27)
Requirement already satisfied: ruamel.yaml==0.18.6 in ./venv/lib/python3.11/site-packages (from esphome) (0.18.6)
Requirement already satisfied: kconfiglib==13.7.1 in ./venv/lib/python3.11/site-packages (from esphome) (13.7.1)
Requirement already satisfied: pyparsing>=3.0 in ./venv/lib/python3.11/site-packages (from esphome) (3.1.2)
Requirement already satisfied: argcomplete>=2.0.0 in ./venv/lib/python3.11/site-packages (from esphome) (3.2.3)
Requirement already satisfied: aiohappyeyeballs>=2.3.0 in ./venv/lib/python3.11/site-packages (from aioesphomeapi==23.1.1->esphome) (2.3.2)
Requirement already satisfied: async-interrupt>=1.1.1 in ./venv/lib/python3.11/site-packages (from aioesphomeapi==23.1.1->esphome) (1.1.1)
Requirement already satisfied: protobuf>=3.19.0 in ./venv/lib/python3.11/site-packages (from aioesphomeapi==23.1.1->esphome) (5.26.0)
Requirement already satisfied: chacha20poly1305-reuseable>=0.12.1 in ./venv/lib/python3.11/site-packages (from aioesphomeapi==23.1.1->esphome) (0.12.1)
Requirement already satisfied: noiseprotocol<1.0,>=0.3.1 in ./venv/lib/python3.11/site-packages (from aioesphomeapi==23.1.1->esphome) (0.3.1)
Requirement already satisfied: cffi>=1.12 in ./venv/lib/python3.11/site-packages (from cryptography==42.0.2->esphome) (1.16.0)
Requirement already satisfied: bitstring>=3.1.6 in ./venv/lib/python3.11/site-packages (from esptool==4.7.0->esphome) (4.1.4)
Requirement already satisfied: ecdsa>=0.16.0 in ./venv/lib/python3.11/site-packages (from esptool==4.7.0->esphome) (0.18.0)
Requirement already satisfied: reedsolo<1.8,>=1.5.3 in ./venv/lib/python3.11/site-packages (from esptool==4.7.0->esphome) (1.7.0)
Requirement already satisfied: intelhex in ./venv/lib/python3.11/site-packages (from esptool==4.7.0->esphome) (2.3.0)
Requirement already satisfied: bottle==0.12.* in ./venv/lib/python3.11/site-packages (from platformio==6.1.13->esphome) (0.12.25)
Requirement already satisfied: marshmallow==3.* in ./venv/lib/python3.11/site-packages (from platformio==6.1.13->esphome) (3.21.1)
Requirement already satisfied: pyelftools==0.30 in ./venv/lib/python3.11/site-packages (from platformio==6.1.13->esphome) (0.30)
Requirement already satisfied: requests==2.* in ./venv/lib/python3.11/site-packages (from platformio==6.1.13->esphome) (2.31.0)
Requirement already satisfied: semantic-version==2.10.* in ./venv/lib/python3.11/site-packages (from platformio==6.1.13->esphome) (2.10.0)
Requirement already satisfied: tabulate==0.* in ./venv/lib/python3.11/site-packages (from platformio==6.1.13->esphome) (0.9.0)
Requirement already satisfied: ajsonrpc==1.2.* in ./venv/lib/python3.11/site-packages (from platformio==6.1.13->esphome) (1.2.0)
Requirement already satisfied: starlette<0.36,>=0.19 in ./venv/lib/python3.11/site-packages (from platformio==6.1.13->esphome) (0.35.1)
Requirement already satisfied: uvicorn<0.26,>=0.16 in ./venv/lib/python3.11/site-packages (from platformio==6.1.13->esphome) (0.25.0)
Requirement already satisfied: wsproto==1.* in ./venv/lib/python3.11/site-packages (from platformio==6.1.13->esphome) (1.2.0)
Requirement already satisfied: ruamel.yaml.clib>=0.2.7 in ./venv/lib/python3.11/site-packages (from ruamel.yaml==0.18.6->esphome) (0.2.8)
Requirement already satisfied: ifaddr>=0.1.7 in ./venv/lib/python3.11/site-packages (from zeroconf==0.131.0->esphome) (0.2.0)
Requirement already satisfied: packaging>=17.0 in ./venv/lib/python3.11/site-packages (from marshmallow==3.*->platformio==6.1.13->esphome) (24.0)
Requirement already satisfied: charset-normalizer<4,>=2 in ./venv/lib/python3.11/site-packages (from requests==2.*->platformio==6.1.13->esphome) (3.3.2)
Requirement already satisfied: idna<4,>=2.5 in ./venv/lib/python3.11/site-packages (from requests==2.*->platformio==6.1.13->esphome) (3.6)
Requirement already satisfied: urllib3<3,>=1.21.1 in ./venv/lib/python3.11/site-packages (from requests==2.*->platformio==6.1.13->esphome) (2.2.1)
Requirement already satisfied: certifi>=2017.4.17 in ./venv/lib/python3.11/site-packages (from requests==2.*->platformio==6.1.13->esphome) (2024.2.2)
Requirement already satisfied: h11<1,>=0.9.0 in ./venv/lib/python3.11/site-packages (from wsproto==1.*->platformio==6.1.13->esphome) (0.14.0)
Requirement already satisfied: bitarray<3.0.0,>=2.8.0 in ./venv/lib/python3.11/site-packages (from bitstring>=3.1.6->esptool==4.7.0->esphome) (2.9.2)
Requirement already satisfied: pycparser in ./venv/lib/python3.11/site-packages (from cffi>=1.12->cryptography==42.0.2->esphome) (2.21)
Requirement already satisfied: six>=1.9.0 in ./venv/lib/python3.11/site-packages (from ecdsa>=0.16.0->esptool==4.7.0->esphome) (1.16.0)
Requirement already satisfied: anyio<5,>=3.4.0 in ./venv/lib/python3.11/site-packages (from starlette<0.36,>=0.19->platformio==6.1.13->esphome) (4.3.0)
Requirement already satisfied: sniffio>=1.1 in ./venv/lib/python3.11/site-packages (from anyio<5,>=3.4.0->starlette<0.36,>=0.19->platformio==6.1.13->esphome) (1.3.1)
[1]
     Hostname: jk-bms-bat01
     MAC Address: C8:47:8C:EC:1E:60
     Protocol: JK02_32S
[2]
     Hostname: jk-bms-bat02
     MAC Address: C8:47:8C:E5:98:96
     Protocol: JK02_24S
Enter desired configuration: 2
Hostname set to <jk-bms-bat02>
MAC Addres set to <C8:47:8C:E5:98:96>

INFO ESPHome 2024.3.0
INFO Reading configuration esp32-ble-1.17.4.yaml...
INFO Updating https://github.com/syssi/esphome-jk-bms.git@main
INFO Detected timezone 'Europe/Copenhagen'
INFO Generating C++ source...
INFO Compiling app...
Processing jk-bms-bat02 (board: esp32-s3-devkitc-1; framework: espidf; platform: platformio/espressif32@5.4.0)
---------------------------------------------------------------------------------------------------------------------------------------
HARDWARE: ESP32S3 240MHz, 320KB RAM, 8MB Flash
 - framework-espidf @ 3.40406.240122 (4.4.6)
 - tool-cmake @ 3.16.4
 - tool-ninja @ 1.7.1
 - toolchain-esp32ulp @ 2.35.0-20220830
 - toolchain-riscv32-esp @ 8.4.0+2021r2-patch5
 - toolchain-xtensa-esp32s3 @ 8.4.0+2021r2-patch5
Reading CMake configuration...
Dependency Graph
|-- ArduinoJson @ 6.18.5
Compiling .pioenvs/jk-bms-bat02/src/main.o
Linking .pioenvs/jk-bms-bat02/firmware.elf
RAM:   [==        ]  16.3% (used 53552 bytes from 327680 bytes)
Flash: [========  ]  77.9% (used 1429945 bytes from 1835008 bytes)
Building .pioenvs/jk-bms-bat02/firmware.bin
Creating esp32s3 image...
Successfully created esp32s3 image.
esp32_create_combined_bin([".pioenvs/jk-bms-bat02/firmware.bin"], [".pioenvs/jk-bms-bat02/firmware.elf"])
Wrote 0x16d320 bytes to file /root/ESPHome/esphome-jk-bms-can-1.17.4/.esphome/build/jk-bms-bat02/.pioenvs/jk-bms-bat02/firmware-factory.bin, ready to flash to offset 0x0
==================================================== [SUCCESS] Took 58.85 seconds ====================================================
INFO Successfully compiled program.
INFO Resolving IP address of jk-bms-bat02.solar.MYDOMAIN.home
INFO  -> 172.22.249.91
INFO Uploading .esphome/build/jk-bms-bat02/.pioenvs/jk-bms-bat02/firmware.bin (1430304 bytes)
ERROR Error receiving acknowledge version: timed out
 
Or directly uploading most recent builds is stuck at 4%

Code: 
esphome upload esp32-ble-1.17.4.yaml

INFO ESPHome 2024.3.0
INFO Reading configuration esp32-ble-1.17.4.yaml...
INFO Updating https://github.com/syssi/esphome-jk-bms.git@main
INFO Detected timezone 'Europe/Copenhagen'
INFO Resolving IP address of jk-bms-bat02.solar.MYDOMAIN.home
INFO  -> 172.22.249.91
INFO Uploading .esphome/build/jk-bms-bat02/.pioenvs/jk-bms-bat02/firmware.bin (1430304 bytes)
Uploading: [==                                                          ] 4% ERROR Error receiving acknowledge chunk OK: timed out
 
I flashed using USB as usual 😪.

Now I toggled in home assistant the CAN switch to see if something happens in the logs ....
Code: 
Client null received PUBLISH (d0, q0, r0, m0, 'jk-bms-bat02/debug', ... (94 bytes))
jk-bms-bat02/debug [W][component:232]: Component esp32_ble took a long time for an operation (131 ms).
Client null received PUBLISH (d0, q0, r0, m0, 'jk-bms-bat02/debug', ... (73 bytes))
jk-bms-bat02/debug [W][component:233]: Components should block for at most 30 ms.
Client null received PUBLISH (d0, q0, r0, m0, 'jk-bms-bat02/debug', ... (54 bytes))
jk-bms-bat02/debug [I][main:1525]: send can id: 0x35C hex: 0 0
Client null received PUBLISH (d0, q0, r0, m0, 'jk-bms-bat02/debug', ... (69 bytes))
jk-bms-bat02/debug [I][main:1552]: send can id: 0x70 hex: b7 0 b6 0 4c 1 4c 1
Client null received PUBLISH (d0, q0, r0, m0, 'jk-bms-bat02/debug', ... (66 bytes))
jk-bms-bat02/debug [I][main:1586]: send can id: 0x371 hex: 2 0 1 0 1 0 3 0
Client null received PUBLISH (d0, q0, r0, m0, 'jk-bms-bat02/switch/jk-bms-bat02_can_charge_enabled/command', ... (2 bytes))
jk-bms-bat02/switch/jk-bms-bat02_can_charge_enabled/command ON
Client null received PUBLISH (d0, q0, r0, m0, 'jk-bms-bat02/debug', ... (67 bytes))
jk-bms-bat02/debug [I][main:1746]: send can id: 0x379 hex: 18 1 0 0 0 0 0 0
Client null received PUBLISH (d0, q0, r0, m0, 'jk-bms-bat02/switch/jk-bms-bat02_can_charge_enabled/state', ... (2 bytes))
jk-bms-bat02/switch/jk-bms-bat02_can_charge_enabled/state ON
Client null received PUBLISH (d0, q0, r0, m0, 'jk-bms-bat02/debug', ... (59 bytes))
jk-bms-bat02/debug [I][main:1795]: send can id: 0x35E ASCII : PYLON
Client null received PUBLISH (d0, q0, r0, m0, 'jk-bms-bat02/debug', ... (66 bytes))
jk-bms-bat02/debug [I][main:1168]: send can id: 0x359 hex: 0 0 0 0 3 0 0 0
Client null received PUBLISH (d0, q0, r0, m0, 'jk-bms-bat02/debug', ... (49 bytes))
jk-bms-bat02/debug [I][main:1395]: Alarm Status : NoAlarm
Client null received PUBLISH (d0, q0, r0, m0, 'jk-bms-bat02/sensor/jk-bms-bat02_charging_status/state', ... (4 bytes))
jk-bms-bat02/sensor/jk-bms-bat02_charging_status/state Bulk
Client null received PUBLISH (d0, q0, r0, m0, 'jk-bms-bat02/sensor/jk-bms-bat02_requested_charge_voltage/state', ... (4 bytes))
jk-bms-bat02/sensor/jk-bms-bat02_requested_charge_voltage/state 55.2
Client null received PUBLISH (d0, q0, r0, m0, 'jk-bms-bat02/debug', ... (69 bytes))
jk-bms-bat02/debug [I][main:1441]: send can id: 0x351 hex: 28 2 62 2 0 0 d0 1
Client null received PUBLISH (d0, q0, r0, m0, 'jk-bms-bat02/debug', ... (47 bytes))
jk-bms-bat02/debug [I][main:1442]: Charge Status : Bulk
Client null received PUBLISH (d0, q0, r0, m0, 'jk-bms-bat02/debug', ... (71 bytes))
jk-bms-bat02/debug [I][main:1478]: send can id: 0x355 hex: 5e 0 63 0 b8 24 51 a
Client null received PUBLISH (d0, q0, r0, m0, 'jk-bms-bat02/debug', ... (72 bytes))
jk-bms-bat02/debug [I][main:1503]: send can id: 0x356 hex: c1 14 ce ff b6 0 2b 0
Client null received PUBLISH (d0, q0, r0, m0, 'jk-bms-bat02/switch/jk-bms-bat02_can_discharge_enabled/command', ... (2 bytes))
jk-bms-bat02/switch/jk-bms-bat02_can_discharge_enabled/command ON
Client null received PUBLISH (d0, q0, r0, m0, 'jk-bms-bat02/debug', ... (55 bytes))
jk-bms-bat02/debug [I][main:1525]: send can id: 0x35C hex: 80 0
Client null received PUBLISH (d0, q0, r0, m0, 'jk-bms-bat02/switch/jk-bms-bat02_can_discharge_enabled/state', ... (2 bytes))
jk-bms-bat02/switch/jk-bms-bat02_can_discharge_enabled/state ON
Client null received PUBLISH (d0, q0, r0, m0, 'jk-bms-bat02/debug', ... (69 bytes))
jk-bms-bat02/debug [I][main:1552]: send can id: 0x70 hex: b7 0 b6 0 4c 1 4c 1
Client null received PUBLISH (d0, q0, r0, m0, 'jk-bms-bat02/debug', ... (66 bytes))
jk-bms-bat02/debug [I][main:1586]: send can id: 0x371 hex: 2 0 1 0 1 0 3 0
Client null received PUBLISH (d0, q0, r0, m0, 'jk-bms-bat02/debug', ... (67 bytes))
jk-bms-bat02/debug [I][main:1746]: send can id: 0x379 hex: 18 1 0 0 0 0 0 0
Client null received PUBLISH (d0, q0, r0, m0, 'jk-bms-bat02/switch/jk-bms-bat02_can_float_charge_enabled/command', ... (2 bytes))
jk-bms-bat02/switch/jk-bms-bat02_can_float_charge_enabled/command ON
Client null received PUBLISH (d0, q0, r0, m0, 'jk-bms-bat02/switch/jk-bms-bat02_can_float_charge_enabled/state', ... (2 bytes))
jk-bms-bat02/switch/jk-bms-bat02_can_float_charge_enabled/state ON
Client null received PUBLISH (d0, q0, r0, m0, 'jk-bms-bat02/debug', ... (59 bytes))
jk-bms-bat02/debug [I][main:1795]: send can id: 0x35E ASCII : PYLON
Client null received PUBLISH (d0, q0, r0, m0, 'jk-bms-bat02/debug', ... (79 bytes))
jk-bms-bat02/debug [I][jk_bms_ble:327]: Cell info frame (version 2, 300 bytes) received
 
You must log in or register to reply here.

Similar threads

uksa007
JBD/Overkill BMS CAN bus comms support for inverters
2 3
Replies
47
Views
9K
Tropco
T
uksa007
JK BMS CAN bus comms now possible for inverters that support Goodwe and Pylontech batteries
40 41 42
Replies
838
Views
76K
Sleeper85
Sleeper85
B
JK BMS issue with charging
2
Replies
32
Views
5K
upnorthandpersonal
upnorthandpersonal
green-bms
New open source smart BMS
Replies
8
Views
2K
brandnewb
brandnewb
H
200A BMS with low-temp cut-off?
Replies
13
Views
2K
Horsefly
H
Back
Top