diy solar

diy solar

Seplos BMS: Simultaneous CAN to GX and RS485 to PC for Battery Manager?

johndpar

New Member
Joined
May 29, 2022
Messages
4
Hi all

I now have two 200A Seplos BMS, each with 16 280Ah Eve cells.

DIP switches are set as per the manual, ie pack 0 is all off except sw 5, pack 1 only has sw 1 on.

Pack 0 has Victron/SMA protocol selected

Pack 0 and 1 are interconnected with a standard RJ45 patch cable

CAN cable is connected from Victron Cerbo GX to pack 0 and the Cerbo is reporting an SHEnergy battery and the pack voltage and SOC are being reported.

I'm not sure if the two packs are communicating with each other in this mode - how do I tell?

And then there is the real problem - if I then connect the Seplos supplied white USB to RS485 adaptor to pack 0 and fire up Battery Monitor, it will only talk to pack 1.

I'd like to be able to see what is happening on both packs while the CAN connection is doing its thing.

If I change the DIP switches so that they are set as pack 1 and 2 (with sw 5 off on the first pack), then Battery Monitor talks to both packs at the same time (proving that the cables are all good).

So, is this possible, or does a multipack config with CAN to the inverter/GX preclude using Battery Monitor at the same time?

Many thanks
Kind regards

John
 
As far as I know you can set your dip switches for CAN or RS communication not both.
The dip settings are different.
 
As far as I know you can set your dip switches for CAN or RS communication not both.
The dip settings are different.
wrong.
it depends on the hardware version of your bms.
if you have a canbus version, the only port to be used for inverter/comms is the canbus port
the rs485 ports can only be used for interbattery comms and the management software

in the rs485 version, the port labelled canbus is actually talking rs485 for inverter comms

the other 2 port are interbattery comms only

also beaware there is a baud rate difference between the canbus version and the rs485 version
 
wrong.
it depends on the hardware version of your bms.
if you have a canbus version, the only port to be used for inverter/comms is the canbus port
the rs485 ports can only be used for interbattery comms and the management software

in the rs485 version, the port labelled canbus is actually talking rs485 for inverter comms

the other 2 port are interbattery comms only

also beaware there is a baud rate difference between the canbus version and the rs485 version
So if you have a BMS with CAN then you can readout true the software on the computer and let the BMS communicate with your inverter true CAN?
At the same time.
Please tell me how.
 
I dont think you can do it if you have multiple packs in parallel. The DIP switches are not the same.
 
Hi, had the seplos 200A talking with pc using rs485 while bats charged. Connected bats to inverter, communicating with BMS via CAN but immediately lost comms with pc using rs485. Does anyone have any reasons why. Changed rj45 cable, tried both ports (its a bus), on the seplos battery monitor on the pc the tx light flashes about 1 per second, and the red error flashes about like 3 times per sec, removed can connection to inverter same error lights.
 
Done the full gamut of testing, power reset, changed cables, changed usb/rs485 connecter, same results. I have a couple of diy bats Im building testing just now, tried the bms on second bat string and it is working ie pc and bms talking, same same can connected inverter. Im confused and happy for now.
 
Andy, didn't understand what he was doing and people complains about the product. everything is working as expected, just read the documentation.

- you must have the same type of battery in a stack. (CANBUS or RS485 bms version, not both)
- there is a dip sw configuration for CANBUS and on other for RS485, choose the right one according to your stack
- the left port is for your inverter only,
- the 2 right ports are for battery-to-battery coms and PC
 
I have the same problem, connected to BMS in a row and connected the master to Victron by CAN.
In parallel i can read some data via RS485 of the master BMS, i am doing it with ESPHome to get the data into my home automation.

I can read out the data of one pack, but could not read the data of the second one.
Is this really confirmed by Seplos that it doesn't work?
In the logs i can see a lot of unhandled data:

[08:33:59][D][uart_debug:114]: <<< 7E:32:30:30:31:34:36:35:41:30:30:30:30:46:44:39:44:0D:7E:32:30:30:31:34:36:35:41:43:30:34:30:30:30:30:31:30:43:41:37:30:42:43:37:30:42:38:36:30:42:38:33:46:43:41:37:31:34:32:30:34:30:41:41:36:44:36:30:30:32:34:46:31:34:32:34:30:30:30:30:30:30:30:30:30:30:30:30:30:33:30:30:30:30:30:31:46:30:33:38:0D [08:34:00][W][seplos_bms:023]: Unhandled data received: 20.01.46.5A.00.00 (6) [08:34:00][W][seplos_bms:023]: Unhandled data received: 20.01.46.5A.C0.40.00.01.0C.A7.0B.C8.0B.86.0B.83.FC.AD.14.20.40.A9.6D.60.02.4F.14.24.00.00.00.00.00.00.03.00.00.01 (38) [08:34:00][D][uart_debug:114]: <<< 7E:32:30:30:31:34:36:35:41:30:30:30:30:46:44:39:44:0D:7E:32:30:30:31:34:36:35:41:43:30:34:30:30:30:30:31:30:43:41:37:30:42:43:38:30:42:38:36:30:42:38:33:46:43:41:44:31:34:32:30:34:30:41:39:36:44:36:30:30:32:34:46:31:34:32:34:30:30:30:30:30:30:30:30:30:30:30:30:30:33:30:30:30:30:30:31:46:30:33:32:0D [08:34:00][D][uart_debug:114]: >>> 7E:32:30:30:30:34:36:34:32:45:30:30:32:30:30:46:44:33:37:0D [08:34:01][W][seplos_bms:023]: Unhandled data received: 20.01.46.5A.00.00 (6) [08:34:01][W][seplos_bms:023]: Unhandled data received: 20.01.46.5A.C0.40.00.01.0C.A6.0B.C7.0B.86.0B.83.FC.AD.14.20.40.A9.6D.60.02.4F.14.24.00.00.00.00.00.00.03.00.00.01 (38) [08:34:01][D][uart_debug:114]: <<< 7E:32:30:30:31:34:36:35:41:30:30:30:30:46:44:39:44:0D:7E:32:30:30:31:34:36:35:41:43:30:34:30:30:30:30:31:30:43:41:36:30:42:43:37:30:42:38:36:30:42:38:33:46:43:41:44:31:34:32:30:34:30:41:39:36:44:36:30:30:32:34:46:31:34:32:34:30:30:30:30:30:30:30:30:30:30:30:30:30:33:30:30:30:30:30:31:46:30:33:34:0D [08:34:02][W][seplos_bms:023]: Unhandled data received: 20.01.46.5A.00.00 (6) [08:34:02][D][uart_debug:114]: <<< 7E:32:30:30:31:34:36:35:41:30:30:30:30:46:44:39:44:0D:7E:32:30:30:31 [08:34:02][D][uart_debug:114]: >>> 7E:32:30:30:31:34:36:34:32:45:30:30:32:30:31:46:44:33:35:0D [08:34:02][W][seplos_bms:023]: Unhandled data received: 20.01.46.5A.C0.40.00.01.0C.A7.0B.C8.0B.86.0B.83.FC.B2.14.20.40.A9.6D.60.02.4F.14.24.00.00.00.00.00.00.03.00.00.01 (38) [08:34:02][D][uart_debug:114]: <<< 34:36:35:41:43:30:34:30:30:30:30:31:30:43:41:37:30:42:43:38:30:42:38:36:30:42:38:33:46:43:42:32:31:34:32:30:34:30:41:39:36:44:36:30:30:32:34:46:31:34:32:34:30:30:30:30:30:30:30:30:30:30:30:30:30:33:30:30:30:30:30:31:46:30:34:33:0D:7E:32:30:30:31:34:36:30:30:31:30:39:36:30:30:30:31:31:30:30:43:41:34:30:43:41:30:30:43:41:32:30:42:43:38:30:43:41:30:30:43:41:36:30:43:41:34:30:43:41:37:30:43:41:35:30:43:41:36:30:43:38:45:30:43:41:33:30:43:41:33:30:43 [08:34:02][seplos_bms:031]: Telemetry frame received [08:34:02][D][sensor:126]: 'seplos-bms-1 bank 0 min cell voltage': Sending state 3.01600 V with 3 decimals of accuracy [08:34:02][D][sensor:126]: 'seplos-bms-1 bank 0 max cell voltage': Sending state 3.23900 V with 3 decimals of accuracy [08:34:02][D][sensor:126]: 'seplos-bms-1 bank 0 delta cell voltage': Sending state 0.22300 V with 3 decimals of accuracy [08:34:02][D][sensor:126]: 'seplos-bms-1 bank 0 average cell voltage': Sending state 3.22050 V with 3 decimals of accuracy [08:34:02][D][sensor:126]: 'seplos-bms-1 bank 0 current': Sending state -9.91000 A with 2 decimals of accuracy [08:34:02][D][sensor:126]: 'seplos-bms-1 bank 0 total voltage': Sending state 51.52000 V with 2 decimals of accuracy [08:34:02][D][sensor:126]: 'seplos-bms-1 bank 0 power': Sending state -510.56320 W with 2 decimals of accuracy [08:34:02][D][sensor:126]: 'seplos-bms-1 bank 0 state of charge': Sending state 59.10000 % with 1 decimals of accuracy [08:34:02][D][uart_debug:114]: <<< 41:34:30:43:41:35:30:43:41:31:30:36:30:42:38:35:30:42:38:36:30:42:38:33:30:42:38:34:30:42:39:45:30:42:38:33:46:43:32:31:31:34:32:30:34:30:41:39:30:41:36:44:36:30:30:32:34:46:36:44:36:30:30:30:30:32:30:33:45:38:31:34:32:34:30:30:30:30:30:30:30:30:30:30:30:30:30:30:30:30:44:44:34:32:0D
DOWNLOAD LOGSEDITCLOSE

So probably the data is there but it must be handled.
Did anyone already tried to handle this data?
 
Andy, didn't understand what he was doing and people complains about the product. everything is working as expected, just read the documentation.

- you must have the same type of battery in a stack. (CANBUS or RS485 bms version, not both)
This is a huge limitation. Not sure why Seplos did not keep the protocol and baudrate the same for battery-to-battery coms.
I am sure Seplos can fix/solve this incompatibility in firmware.
At least then the two types (CANBUS and RS485 version) can then be used together .
 
This is a huge limitation. Not sure why Seplos did not keep the protocol and baudrate the same for battery-to-battery coms.
I am sure Seplos can fix/solve this incompatibility in firmware.
At least then the two types (CANBUS and RS485 version) can then be used together .
hey have solved it in their new bms version ( v16)
 
Well done to Seplos!
Let's trust that Seplos release updated firmware for the pre v16 BMSs to also have compatible battery-to-battery comms in terms of protocol and baudrate.
as i understood it, this was caused by hardware, so i am not sure this will be fixable by a firmware update, but you can always ask them :)
 
Back
Top