Update README

This commit is contained in:
Sleeper85 committed 2025-04-20 22:37:27 +02:00
1 parent e0ccd7d07d
commit 82493b0a6a
10 files changed
+114 -40

No files matched your search

@@ -1,4 +1,4 @@
# YamBMS - JK-B BMS UART Solution
# YamBMS - JK-B BMS
[![Badge License: GPLv3](https://img.shields.io/badge/License-GPLv3-brightgreen.svg)](https://www.gnu.org/licenses/gpl-3.0)
[![Badge Version](https://img.shields.io/github/v/release/Sleeper85/esphome-yambms?include_prereleases&color=yellow&logo=DocuSign&logoColor=white)](https://github.com/Sleeper85/esphome-yambms/releases/latest)
@@ -6,9 +6,40 @@
![GitHub forks](https://img.shields.io/github/forks/Sleeper85/esphome-yambms)
![GitHub watchers](https://img.shields.io/github/watchers/Sleeper85/esphome-yambms)
## External component
## JK-B BMS overview
[esphome-jk-bms](https://github.com/syssi/esphome-jk-bms) by [@syssi](https://github.com/syssi)
### UART1 (GPS) port
The `GPS` port sometimes called `RS485` is not an `RS485` port but `3V3 UART-TTL` port.
```
# UART-TTL GPS port on JK-BMS (4 pin, JST 1.25mm pitch)
┌─── ─────── ────┐
│ │
│ O O O O │
│GND RX TX VBAT│
└────────────────┘
│ │ │ └ VBAT is full battery volatge eg. 56V (possible to use it via an isolated DC-DC converter)
│ │ └──── TX to TTL-isolator AI (input)
│ └──────── RX to TTL-isolator AO (output)
└──────────── GND to TTL-isolator GND
```
The `UART1` (labeled as `GPS`) socket of the BMS can be attached to any UART pins of the ESP32.<br>
A hardware UART should be preferred because of the high baudrate (115200 baud).<br>
The connector is called 4 pin JST with 1.25mm pitch.
![Image](../../images/JK-BMS_24S_GPS_port.png "JK-B BMS GPS port")
## JK-B BMS protocol
Historically it was not possible to change the protocol of the `UART1 (GPS)` port and the protocol used was `4G-GPS Remote module Common protocol V4.2` with the component [esphome-jk-bms](https://github.com/syssi/esphome-jk-bms) of [@syssi](https://github.com/syssi).
If you cannot change the protocol of the `UART1 (GPS)` port you can only monitor one BMS per UART port of the ESP32, so a maximum of `3x BMS` without adding a UART expander.
If you have a recent BMS, it is now possible to change the protocol of the `UART1 (GPS)` port and with the `JK BMS RS485 Modbus V1.0` protocol you can assign an address (via JK app) to your BMS and monitor several of them from a single `UART-RS485` connection in the same way as the [JK-PB](BMS_JK-PB.md). To use this protocol and monitor all your BMS on a single `RS485 bus` you will need to add the `UART to RS485 adapter` sold by JK or another RS485 board of your choice.
<img src="../../images/BMS_JK_RS485_Modbus_protocol.png" width="400">
## Schematic and setup instructions
@@ -32,8 +63,8 @@ You need to import this YAML into the main YAML.
```
UART-TTL RS232-TTL CAN BUS
┌──────────┐ ┌──────────┐ ┌────────────┐ ┌──────────┐
│ │<TX------RX>│2 5│<TX-------TX>| | | |
│ JK-BMS │<RX------TX>│1 6│<RX-------RX>| CA-IS3050G |<---CAN H --->| Inverter |
│ │<TX------RX>│1 5│<TX-------TX>| | | |
│ JK-BMS │<RX------TX>│2 6│<RX-------RX>| CA-IS3050G |<---CAN H --->| Inverter |
│ │<----GND--->│ ESP32 │ | CAN |<---CAN L --->| |
│ │ 5V---->│5V 3V3| | | | |
└──────────┘ └──────────┘ └────────────┘ └──────────┘
@@ -51,8 +82,8 @@ You need to import this YAML into the main YAML.
```
UART-TTL RS232-TTL CAN BUS
┌──────────┐ ┌──────────┐ ┌────────────┐ ┌──────────┐
│ │<TX------RX>│26 22│<TX-------TX>| | | |
│ JK-BMS │<RX------TX>│32 19│<RX-------RX>| CA-IS3050G |<---CAN H --->| Inverter |
│ │<TX------RX>│32 22│<TX-------TX>| | | |
│ JK-BMS │<RX------TX>│26 19│<RX-------RX>| CA-IS3050G |<---CAN H --->| Inverter |
│ │<----GND--->│ ESP32 │ | CAN |<---CAN L --->| |
│ │ 5V---->│5V 3V3| | | | |
└──────────┘ └──────────┘ └────────────┘ └──────────┘
@@ -105,25 +136,3 @@ You need to import this YAML into the main YAML.
```
### JK-B BMS UART-TTL GPS port
The `GPS` port sometimes called `RS485` is not an `RS485` port but `3V3 UART-TTL`.
```
# UART-TTL GPS port on JK-BMS (4 pin, JST 1.25mm pitch)
┌─── ─────── ────┐
│ │
│ O O O O │
│GND RX TX VBAT│
└────────────────┘
│ │ │ └ VBAT is full battery volatge eg 51.2V (possible to use it via an isolated DC-DC converter)
│ │ └──── TX to TTL-isolator AI (input)
│ └──────── RX to TTL-isolator AO (output)
└──────────── GND to TTL-isolator GND
```
The UART-TTL (labeled as `GPS`) socket of the BMS can be attached to any UART pins of the ESP.<br>
A hardware UART should be preferred because of the high baudrate (115200 baud).<br>
The connector is called 4 pin JST with 1.25mm pitch.
![Image](../../images/JK-BMS_24S_GPS_port.png "JK-B BMS GPS port")
@@ -1,4 +1,4 @@
# YamBMS - JK-PB BMS RS485 Solution
# YamBMS - JK-PB Inverter BMS
[![Badge License: GPLv3](https://img.shields.io/badge/License-GPLv3-brightgreen.svg)](https://www.gnu.org/licenses/gpl-3.0)
[![Badge Version](https://img.shields.io/github/v/release/Sleeper85/esphome-yambms?include_prereleases&color=yellow&logo=DocuSign&logoColor=white)](https://github.com/Sleeper85/esphome-yambms/releases/latest)
@@ -6,11 +6,76 @@
![GitHub forks](https://img.shields.io/github/forks/Sleeper85/esphome-yambms)
![GitHub watchers](https://img.shields.io/github/watchers/Sleeper85/esphome-yambms)
## External component
## JK-PB BMS overview
[JK_RS485](https://github.com/txubelaxu/esphome-jk-bms/blob/main/components/jk_rs485_bms/README.md) by [@txubelaxu](https://github.com/txubelaxu)
|![Image](../../images/BMS_JK-PB_Inverter_BMS.png)|
|-|
|![Image](../../images/BMS_JK-PB_communication_connectors.jpg)|
|![Image](../../images/BMS_JK-PB_communication_board.png)|
## Hardware
## JK-PB BMS protocol
The datas from this BMS can be retrieved from the `RS485-2 (UART2)` network using the component [JK_RS485](https://github.com/txubelaxu/esphome-jk-bms/blob/main/components/jk_rs485_bms/README.md) of [@txubelaxu](https://github.com/txubelaxu).
The BMS DIP switches must be set from `1` to `15` (server mode) and connected to each other using the `RS485-2` network available on the **two ports at the right ends**. `YamBMS` also connects to one of these two ports.
### **UART2 configuration**
> [!NOTE]
> The protocol of the `UART2` port is not selectable from the JK application.
> It is automatically set based on the address (DIP switch) of the BMS.
In the last software version only two protocols are available on the **RS485-2 (UART2)** ports:
- **001** - JK BMS RS485 Modbus V1.0 **(DIP switch 1 to 15)**
- **015** - UART Protocol 015 **(DIP switch 0)**
### **UART1 configuration**
The following protocols are supported on the **RS485-1 (UART1)** port:
(*italic options ane not settable*)
- **000** - 4G-GPS Remote module Common protocol V4.2
- **001** - **JK BMS RS485 Modbus V1.0**
- **002** - NIU U SERIES
- **003** - China tower shared battery cabinet V1.1
- **004** - PACE_RS485_Modbus_V1.3
- **005** - PYLON_low_voltage_Protocol_RS485_V3.5
- **006** - Growatt_BMS_RS485_Protocol_1xSxxP_ESS_Rev2.01
- **007** - Voltronic_Inverter_and_BMS_485_communication_protocol_20200...
- **008** - China tower shared battery cabinet V2.0
- **009** - WOW_RS485_Modbus_V1.3
- **010** - JK BMS LCD Protocol V2.0
- **011** - *UART1 User customization*
- **012** - *UART2 User customization*
- **013** - (9600)JK BMS RS485 Modbus V1.0
- **014** - (9600)PYLON_low_voltage_Protocol_RS485_V3.5
- **015** - *UART Protocol 015*
### **CAN port configuration**
The following CAN protocols are supported on the CAN port:
(*italic options ane not settable*)
- **000** - JK BMS CAN Protocol (250K) V2.0
- **001** - Deye Low-voltage hybrid inverter CAN communication protocol V1.0
- **002** - PYLON-Low-voltage-V1.2
- **003** - Growatt BMS CAN-Bus-protocol-low-voltage_Rev_05
- **004** - Victron_CANbus_BMS_protocol_20170717
- **005** - MEGAREVO_Hybird_BMSCAN_Protocol_V1.0
- **006** - JK BMS CAN Protocol (500K) V2.0
- **007** - INVT BMS CAN Bus protocol V1.02
- **008** - GoodWe LV BMS Protocol (EX/EM/S-BP/BP)
- **009** - FSS-ConnectingBat-Tl-en-10 | Version 1.0
- **010** - MUST PV1800F-CAN communication Protocol1.04.04
- **011** - LuxpowerTek Battery CAN protocol V01
- **012** - *CAN BUS User customization*
- **013** - *CAN BUS Protocol 013*
- **014** - *CAN BUS Protocol 014*
## YamBMS hardware
> [!TIP]
> This solution only requires an ESP32 with a CAN transceiver and a RS485 transceiver.
@@ -1,4 +1,4 @@
# YamBMS - JK-B BMS RS485 DISPLAY Solution
# YamBMS - JK RS485 DISPLAY
[![Badge License: GPLv3](https://img.shields.io/badge/License-GPLv3-brightgreen.svg)](https://www.gnu.org/licenses/gpl-3.0)
[![Badge Version](https://img.shields.io/github/v/release/Sleeper85/esphome-yambms?include_prereleases&color=yellow&logo=DocuSign&logoColor=white)](https://github.com/Sleeper85/esphome-yambms/releases/latest)
@@ -9,7 +9,7 @@
## Contents
1) [Galvanic isolation](Galvanic_isolation.md)
2) [JK-B BMS UART (GPS port) solution](BMS_JK-B_UART_solution.md)
3) [JK-B BMS RS485 (Display port) solution](BMS_JK-B_RS485_DISPLAY_solution.md)
4) [JK-PB BMS RS485 solution](BMS_JK-PB_RS485_solution.md)
5) [Victron SmartShunt How To](Shunt_Victron_SmartShunt_HowTo.md)
2) [JK-B BMS](BMS_JK-B.md)
3) [JK-PB BMS](BMS_JK-PB.md)
4) [JK RS485 DISPLAY](BMS_JK_RS485_DISPLAY.md)
5) [Victron SmartShunt](Shunt_Victron_SmartShunt.md)
@@ -1,4 +1,4 @@
# Victron SmartShunt How To
# Victron SmartShunt
[![Badge License: GPLv3](https://img.shields.io/badge/License-GPLv3-brightgreen.svg)](https://www.gnu.org/licenses/gpl-3.0)
[![Badge Version](https://img.shields.io/github/v/release/Sleeper85/esphome-yambms?include_prereleases&color=yellow&logo=DocuSign&logoColor=white)](https://github.com/Sleeper85/esphome-yambms/releases/latest)
+1 -1
View File
@@ -41,7 +41,7 @@ Combine condition :
1) BMS `Online Status` is `ON / Connected` (to detect a loss of connection with the BMS e.g. cable, BMS OFF or dead)
2) The BMS `Battery Capacity` is `> 0` (to ensure that the data received is correct)
If one of these three conditions is not met, the BMS is automatically uncombined.
If one of these two conditions is not met, the BMS is automatically uncombined.
> [!IMPORTANT]
> In RS485 modbus `multi-node`, if a server does not respond (cable or hardware failure) the `Online Status` of the BMS will be set to `OFF` and it will be uncombined.
Binary file not shown.

After

Width:  |  Height:  |  Size: 587 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 106 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 38 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 176 KiB