Search results

Are you talking about this diagram? It's possible to change the position of the wires to connect JST. Use a needle to push them out and then reposition them.

For my part, I flash the ESP32 or ESP32-S3 from the command line from Linux without any problems and I don't need a web interface. I find it very simple. When the firmware is compiled, the choice is offered to upload it via UART or IP. esphome run jk-bms-can.yaml To flash an ESP32 already in...

I'm currently working to finalize the multi-bms version with everything connected on a single ESP32. This is mainly intended for the PVbrain2 card but this should therefore work with 2 or 3 BMS and a classic ESP32 (to be tested). https://github.com/SeByDocKy/pvbrain2 Thank you for the links...

Not having an Atom S3, I cannot develop or test anything but there is already code available and tested by @arzaman. This will be part of the new packaged version. https://github.com/Sleeper85/esphome-jk-bms-can/blob/development/packages/device_atom-s3-display.yaml

Thanks, that’s interesting. @arzaman and @Der_Hannes can you share your procedure? I could then do a how to in github.

Thank you for taking the time to document your procedure.

Thank you for taking the time to document your procedure.

OK. Sorry but I don't have Atom S3 board.

https://github.com/Sleeper85/esphome-jk-bms-can/blob/main/config/config_atom-s3-lite-esp32-s3.yaml

More infos : https://diysolarforum.com/threads/jk-bms-can-with-new-cut-off-charging-logic-open-source.79325/post-1016990

These are functions that help prevent OVP from triggering with an unbalanced battery or with runner cells. If your battery is well balanced and of good quality then it is not necessary to activate these functions...

Yes 0.003V is very low, default is 0.01V. I personally use 0.005V.

In addition, with a charging voltage of 54.2V, the cutoff amps is close to 0A, see the links cited above.

Because one of the end-of-charge conditions is that the equalization of your cells is completed, which is not the case.

With switch balancing enabled, charging only ends when your cells are equalized. Delta cell V. must be smaller than Balance Trigger V.

https://github.com/Sleeper85/esphome-jk-bms-can/blob/main/documents/README/Cut-Off_Charging_Logic.md You have a large delta cell V. It is necessary to have the complete list of your parameters to analyze them. The code has been tested, there is no need to modify it.

Wait a moment. The EOC then Float status arrives when the equalization is completed.

If you use TimeOfUse you must at least have a time slot where you request a 100% charge otherwise you will never charge to 100%. You can also try without TOU.

In the case of using an ESP32 JK-BMS-CAN, the ESP32 and our software is the only component that communicates with the inverter. The 100% BMS is completely ignored, 100% is sent only at the end of the full charging process.

Because the 100% BMS is not always true and some brand of inverter stops charging at 100%. If you remain stuck at 99%, your battery has not finished charging. Check this post concerning DEYE TOU : https://diysolarforum.com/threads/deye-weird-voltage-behavior-when-time-of-use-is-enabled.80908/

54.2V is a very low charging voltage for LFP. Do you use TimeOfUse with Deye? Can you send a screenshot of your BMS settings?

Hi, 99% means charging is not complete. The canbus sends 100% only when the charging phase is completed when the status is EOC or Float.

@chaosnature The multi-bms code (several BMS connected on the same ESP32 as with PVbrain2) will soon be ready to test. I have been very busy on another project in recent weeks and still have to code the multi-bms alarm system. We haven't changed the part of the code you cite, it's defaulted to...

The documentation says 15min. Could be another reason?

Yes of course 😉 I sent you an example YAML privately. Supervision of 2 BMS works well, the more the number of BMS increases, the harder it is for the ESP32.

2x JK-BMS supervised via Bluetooth.

There should be no limit for a multi-bms bms Master Slaves version. (still needs to be developed). I ask the question because if you wish you could test the multi-bms version (2x JK-BMS BLE) on the same Atom S3. The first tests could begin in a few days.

PYLON and PYLON+ I don't really know what impact this information can have on the inverter. This makes me think that I could change this in the multi-bms version. How many packs do you have?

This is normal, the PYLON protocol counts one pack per 5kWh of battery.

Glad to hear that the Wire version works well with a JK-BMS SW version > 11.28 👌 ( @paulsteigel ) What framework do you use for Atom S3 Lite, ESP-IDF or Arduino? What can name and protocol version did you choose? What battery mode on the XP6000? I am asking you these questions to add you to...

In the case below the API is not disabled (possibility of connecting the ESP32 to HA) but this prevents reboots every 15 minutes. This is not equivalent to fully commenting api: api: reboot_timeout: 0s

The default behavior of the api: and wifi: components is a reboot every 15 minutes in the event of loss or no connection. If you don't use Home Assistant the api: line must be configured like this to avoid reboots. api: reboot_timeout: 0s Same for wifi: wifi: reboot_timeout: 0s

My JK-BMS-CAN ESP32 ;)

If router1 and router2 are the kind of router installed by your ISP you can't do much right. If you want to discuss it, open a new topic because this type of discussion can quickly become long.

https://www.espressif.com/en/products/socs/esp32-s3