Update JK-PB doc - 120 Ohm bus resistor and SoC 100% reset
This commit is contained in:
1 parent
a3fa519f41
commit
ed4dc7f522
2 files changed
+26
-1
No files matched your search
@@ -105,6 +105,11 @@ The example below uses an `AtomS3` (display) with the `Atomic CAN base` and `RS4
|
||||
> Galvanic isolation of the `RS485` connection is strongly recommended.
|
||||
> The diagrams below does not show the galvanic isolation of the `RS485` connection !
|
||||
|
||||
> [!IMPORTANT]
|
||||
> If you are unable to read your BMS from the `RS485` bus, add a `120 Ohm`
|
||||
> resistor between the `A` and `B` wires connected to your `RS485` board.
|
||||
> This must be done with the `M5Stack RS485 unit`, some boards have a switch to enable the bus termination resistor.
|
||||
|
||||
**Note:** the choice of RS485 board is not related to the chosen ESP32.
|
||||
|
||||
### AtomS3 with unisolated RS485 board
|
||||
@@ -142,13 +147,20 @@ The example below uses an `AtomS3` (display) with the `Atomic CAN base` and `RS4
|
||||
|
||||
## BMS DIP switch config (mode 2)
|
||||
|
||||
With mode 2, the sniffer (ESP32) will automatically take the address 0x00 and act as master BMS (max 15 BMS).
|
||||
With `mode 2`, the sniffer (ESP32) will automatically take the address `0x00` and act as master BMS (max 15 BMS).
|
||||
This is the preferred mode with YamBMS.
|
||||
|
||||
- BMS 1 RS485 address : 0x01
|
||||
- BMS 2 RS485 address : 0x02
|
||||
- BMS 3 RS485 address : 0x03
|
||||
- etc.
|
||||
|
||||
## MODE 1 vs MODE 2
|
||||
|
||||
`MODE 1`. If there is a JK-BMS acting as REAL MASTER (i.e. it has set 0x00 address), the code will be sniffing all the traffic in the network. The problem is that there is some information that is NEVER in the sniffed traffic information (device info frame type 03): device-name, hw version, sw version, password, RCV Time, RFV Time... So, periodically, ESP code will act as a PSEUDO-MASTER to try to get this information. It works for every slave device, but not for master device. At this moment, master device does NOT broadcast by itself the "frame type 03" info. And it does not answer to a "frame type 03" request sent by PSEUDO MASTER.
|
||||
|
||||
`MODE 2`. If every JK-BMS are set as SLAVES (all of them), the ESP code will act as MASTER. So, if ESP code does not detect any REAL MASTER in the network, it will act as a MASTER. Remember to adapt DIP switches and the YAML (addresses) as well. Changing the addreses of the devices does not affect to the historic data gathered from that device, because the config is based on the NAME of the device and not on the address of the device. So, change the address, but not the name. In this mode, ESP will gather all the information (cell info, device settings and device info). If anytime, a REAL MASTER arrives to the network, ESP will detect it and will stop acting as MASTER.
|
||||
|
||||
## JK-PB RS485 functions
|
||||
|
||||
### Broadcasting JK-PB settings to all BMS
|
||||
@@ -156,3 +168,16 @@ With mode 2, the sniffer (ESP32) will automatically take the address 0x00 and ac
|
||||

|
||||
|
||||
When enabled, this function synchronizes the settings of all your BMS connected to the same RS485 network as soon as you make parameter changes.
|
||||
|
||||
## JK-PB SoC 100% reset
|
||||
|
||||
> [!NOTE]
|
||||
> During the `Bulk` phase the YamBMS `SoC` cannot be more than `98%`.
|
||||
> When the battery is fully charged, the `real SoC` will be sent.
|
||||
|
||||
The `RCV`, `RFV`, and `RCV timer` values are not used by YamBMS.
|
||||
But they are used by the `JK-BMS` to reset the SOC to `100%`.
|
||||
If you are instructing YamBMS to charge at `3.45V/cell`, set the JK `RCV` value lower to `3.40V` and reduce the `RCV timer` to `15` minutes.
|
||||
This will reset the `SoC` to `100%` faster.
|
||||
|
||||

|
||||
Binary file not shown.
|
After Width: | Height: | Size: 180 KiB |
Reference in new issue
Block a user