-
-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Chisage ESS CE48100-R Rack Mounted 5kWh battery (DR-ZHONGZ01-16S50JC09-V1.0.1-T4) supported? #105
Comments
You could just attach an ESP to the RS485 port and give it a try. Do you know any details about the BMS? |
Does the BMS has Bluetooth support? What's the advertised name? Could you ask the seller of your BMS/battery bank about a management software? What's the name of the software and how it looks like? |
Unfortunatly not have bluetoot connection. I connected it with esp32. With esp32-seplos-v3-example-multiple-battery-banks.yaml config file. I saw some kind of communication, but only in bank2 total voltage report 176.64 V (of course this is false information). |
Feel free to provide some logs including RAW traffic. |
|
Please reduce the YAML configuration to:
and provide another log. I will explain what I'm looking for afterwords. |
10 minutes log |
Perfect! One BMS acts as Modbus-Master on the bus and tries to collect the data of 10 other devices on the bus. Two slaves are responding. |
Could you plug the cable into the RS485 port next to the CAN bus als next step? Do you see traffic here too or is there silence as long we don't request data actively from the BMS? |
I tried, with this truncated config there is silence on that port. In the original "esp32-example.yaml" config file, both LEDs (rx, tx) blink on the modbus converter module. |
I will provide an updated YAML later the day including some requests. |
I got this "battery program" from chisage. I'll try it now only. you can change language to english on last tab. |
Could you provide a screenshot of every view? This will help to get an idea whats available. |
Could you ask the seller about a list of the Modbus registers / protocol description? |
Need a bit time for protocoll (I hope they are give it to me), but there is some log from the program: I can make screensots, if realy need, but the most inportant things in CVS file. |
I would be happy about screenshots nevertheless. :-) |
Some example frames for later analysis:
|
|
The request above retrieve 55 registers / 2*55 bytes from the BMS:
|
Please try to retrieve some data using this YAML from the RS485 port next to the CAN port:
|
near can bus:
|
It looks like the protocol isn't Modbus compatible. Let's query the data manually:
|
INFO ESPHome 2024.6.6 |
Your BMS doesn't respond anymore. Did you attach the data cable properly? |
Ok, I done a little test with offical program. |
Log from the right rs485 connector |
My modbus "hardver" for PC connection is a simple yp-05, and a cheap HW-519 modbus modul from ali (I use lots of them). I use this modbus modul for esp32 too. Maybe my cable long? I use 2-2,5m cat5e cable on rs485 side. |
On the right RS485 port all systems are responding to our requests:
But you are ignoring one important detail at the moment: If this is a Modbus protocol there is just one master allowed. At the moment BMS1 (0x01) acts as master and we aren't allowed to query data using another master (the ESP!). This is the reason why I would prefer to use the RS485 port next to the CAN bus. |
It's true. An absolutely suitable solution for me is to read out the data one by one next to the can port. In the worst case, you need 3 esp and 3 modbus modules. |
In best case you can connect a single ESP + single RS485 converter to all RS485 ports and the BMS just responds to the dedicated device address (hopefully!). |
Could you try the YAML configuration with the manual requests another time on the RS485 port next to the CAN bus?
Still silence? |
yes, unfortunatly, still silence What do you think, does it make sense to extract data from PC serial communication with a serial port analyzer? (Reverse enginering from offical softver communication) For example with this: https://freeserialanalyzer.com/ |
We can use an ESP to sniff the traffic:
|
Just for info SOC low alarm on 2 and 3 battrey |
These are Seplos ASCII frames (protocol version 2.2):
|
Here is the snifed datas (allways use the rs485 near can port): bat1.txt bat2.txt bat3.txt I tryed read another battery (just for adresses) |
|
43 temperature |
Not sure, but I got a tip from the reseller. (Pylontech) |
With a modified slepos esp32-example.yaml esphome: esp32: external_components:
wifi: ota: logger: api: uart: Please set the default baudrate of your Seplos BMS model here. It's sometimes 19200 baud instead of 9600.baud_rate: 9600 The increased RX buffer size is important becausethe full BMS response must fit into the bufferrx_buffer_size: 384 seplos_modbus: seplos_bms: Dip switch configuration of a single pack setup / address 0x08 7 6 5 4 3 2 1off, off, off, off, off, off, off, offaddress: 0x01 Known protocol versions: 0x20 (Seplos), 0x26 (Boqiang)protocol_version: 0x22 sensor:
some kind of communication started (adress 0x01, protocoll 0x22): 7E:32:32:30:31:34:36:34:32:45:30:30:32:30:31:46:44:33:33:0D [01:56:12][D][uart_debug:114]: >>> 7E:32:32:30:31:34:36:34:32:45:30:30:32:30:31:46:44:33:33:0D |
I did the same already. The Seplos component isn't compatible. |
It's growing slowly, we need those crazy registers, but give the data back to the homeassistant already, the data is just not in the right place. :) |
Good job! Let's summarize our findings:
TODOs: Compare the different |
Let's move this discussion to the Seplos BMS project because of the Seplos like protocol. |
Are you using chisage inverter? |
Hi I use the batterys with an 6,2Kw PowMr inverter. The pack not conected to the inverter with data cable. I use custom BMS monitoring in HA. |
I have 3pc chisage ess ce48100-r rack mounted 5KWh battery. I need to disassembly one or other way?
https://chisagess.com/wp-content/uploads/2023/03/UM_Lithium-Battery-CE48100-R_20230216_V1.2.pdf
The text was updated successfully, but these errors were encountered: