Bms 3.0 seplos

[jolly12f]

Hello, is this compatible with new generation bms?

[syssi]

I don't know. Could you ask the manufacturer about protocol details / specs?

[jolly12f]

If you tell me exactly what to ask I will, I'm not very practical

[syssi]

"Dear customer support, could you provide a communication protocol description applicable for your new Seplos BMS v3.0?"

[jolly12f]

[syssi]

Let's try something like this: https://github.com/syssi/esphome-seplos-bms/blob/add-seplos-v3-support/esp32-seplos-v3-example.yaml

[jolly12f]

I use esp8266

[syssi]

In this case please use this YAML: https://github.com/syssi/esphome-seplos-bms/blob/add-seplos-v3-support/esp8266-seplos-v3-example.yaml

And attach the RS485 converter to GPIO4/GPIO5. Does the BMS respond?

[jolly12f]

I'll try this evening, I use AZ delivery, the TX and RX pins or D1 o D2?

[syssi]

Please use D1 (GPIO5) and D2 (GPIO4). RX/TX is connected to your USB-to-TTL converter and useful to monitor the log output of the ESPHome node via the micro-USB cable.

[jolly12f]

Then something I managed to upload, but the 4 entities remain unknown

[syssi]

Could you provide a photo of your wiring? Which communication port of the BMS do you use?

[jolly12f]

I solved everything there was a writing error in the yaml the register_type entry must be read now I read all the values

[jolly12f]

[syssi]

Could you contribute your YAML and some details about your wiring? I would like to extend this project. Thanks in advance!

[jolly12f]

I'm checking because it was going last night but I'm not getting any data today

[jolly12f]

now my problem is that the TTL 485 card burns out after 10 minutes and I don't understand why.

[syssi]

It's hard to provide any support of you don't share details.

[jolly12f]

Maybe I had a USB power supply that didn't fit I'm trying another one

[jolly12f]

Ok fixed everything was the power supply that was not good, I don't know how my yaml loads can you tell me? So I put it online

[syssi]

If you rename the YAML file to .txt the file can be attached to a comment here.

[jolly12f]

seplos_bms_3.0.yaml.txt

[jolly12f]

Same wiring as for d1 mini

[jolly12f]

Do you think it is possible to read another bms using 2 other inputs??

[syssi]

Yes. This is possible.

[jolly12f]

Will I have to rewrite at the end of my yaml all the same but with different pins?

[syssi]

Some sections must be lists and you have to address to different instances using IDs. Do you own two Seplos BMS V3 devices?

[jolly12f]

I will get another battery later, I have to understand if with the master bms I can also read the slave bms otherwise I have to read them individually one by one

[jolly12f]

Some sections must be lists and you have to address to different instances using IDs. Do you own two Seplos BMS V3 devices?

Hi everyone, I integrated my seplos bms with modbus protocol with my esp8266, when I only had one battery everything worked, now I added a second battery with a second BMS which is connected to the first via port 485, and my entire esp system has often doesn’t work, I have no idea how to reconfigure my file. can anyone give me a hand?? I attach my current configuration that works with a single battery and the description of the Modbus protocol of my BMS. Please if anyone can help me I would be grateful

this is my configuration:

esp8266:
board: esp01_1m

wifi:
ssid:…

password:…
ota:
password: “…”

logger:
level: DEBUG

api:
encryption:
key: “…”

uart:

id: uart_0
baud_rate: 19200
tx_pin: GPIO4
rx_pin: GPIO5
debug:
direction: BOTH
dummy_receiver: false
modbus:

id: modbus0
uart_id: uart_0
send_wait_time: 200ms
modbus_controller:

id: bms0
address: 0x00
modbus_id: modbus0
command_throttle: 200ms
update_interval: 10s
sensor:

platform: modbus_controller
modbus_controller_id: bms0
name: “${name} cicli carica”
address: 0x1007
register_type: read
value_type: S_WORD
unit_of_measurement: “”
device_class: battery
state_class: measurement
accuracy_decimals: 0
filters:
multiply: 1

[jolly12f]

I read that other people have the same problem as me, with just one battery the Modbus system is able to read the data, but with two batteries no one has yet managed to get a reading of the batteries?

[ferelarg]

As I answered you in the other message, you can only read using this method when you have only one battery.
Since you set the esphome as Master. In Modbus communication, there can only be one master, that is, only one device can consult registers, etc.