Seplos - Unknown Version (ATG Batteries)

[saffrey]

Hi team, I have an ATG 5kWh 48V battery (local Australian guy "designed" them, but they are made over seas.) It uses a Seplos BMS, but I am unsure of the version - it seems like an old version and factory test cert is from Sep 2022. I cannot pull the battery apart to confirm as this will void the warranty. I can confirm the port and switch layout is the same as the standard three RJ45 style Seplos BMS, as below.

dbus-serialbattery does detect the BMS and stops as Seplos in the logs and goes no further.

I'm happy to give one of the devs access to my Venus OS device so they can see what data is being returned and perhaps adapt the driver etc for others to benefit from. I can be contacted here or via email - john@saffrey.id.au

2024-01-10 11:25:22.345127500 INFO:SerialBattery:Starting dbus-serialbattery
2024-01-10 11:25:22.345702500 INFO:SerialBattery:dbus-serialbattery v1.1.20231224dev
2024-01-10 11:25:38.350472500 INFO:SerialBattery:-- Testing BMS: 1 of 3 rounds
2024-01-10 11:25:38.350863500 INFO:SerialBattery:Testing Daly at address "\x40"
2024-01-10 11:25:38.482502500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2024-01-10 11:25:38.482860500 INFO:SerialBattery:Testing Daly at address "\x80"
2024-01-10 11:25:38.612374500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2024-01-10 11:25:38.612677500 INFO:SerialBattery:Testing Ecs
2024-01-10 11:25:38.677773500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2024-01-10 11:25:38.678069500 INFO:SerialBattery:Testing HeltecModbus
2024-01-10 11:25:42.388699500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2024-01-10 11:25:42.389182500 INFO:SerialBattery:Testing HLPdataBMS4S
2024-01-10 11:25:43.199886500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2024-01-10 11:25:43.200169500 INFO:SerialBattery:Testing Jkbms
2024-01-10 11:25:43.476169500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2024-01-10 11:25:43.478126500 INFO:SerialBattery:Testing Lifepower
2024-01-10 11:25:43.696022500 ERROR:SerialBattery:>>> ERROR: Incorrect Reply
2024-01-10 11:25:43.696313500 INFO:SerialBattery:Testing LltJbd
2024-01-10 11:25:43.969652500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2024-01-10 11:25:43.971405500 INFO:SerialBattery:Testing Renogy at address "\x30"
2024-01-10 11:25:44.192299500 ERROR:SerialBattery:>>> ERROR: Incorrect Reply
2024-01-10 11:25:44.192885500 INFO:SerialBattery:Testing Renogy at address "\xf7"
2024-01-10 11:25:44.465452500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2024-01-10 11:25:44.466971500 INFO:SerialBattery:Testing Seplos
2024-01-10 11:31:16.286521500 *** CCGX booted (0) ***

[mdkeil]

Did you check the trouble-shoot-faq?
Which RS485/USB Cable do you use? Is the device /dev/ttyUSB[0..99] present in VenusOS?
Pls post your config.ini / config.default.ini

[saffrey]

@mdkeil

Thank you for your reply, much appreciated.

Yes I have been through the guide - hence the log output supplied with time stamps in my post.

The RS485 device I am using is this one (has been proven to work by others):

Yes, the device is showing up in /dev in Venus OS, but of course it is not displaying in the Victron GUI as the driver is stalling on Seplos, I have assumed because my BMS version is not 16E which is the only one listed in the tested BMS section.

Also, I have tried the dev and master versions of the driver, along with v1.0.0 they all behave the same, stopping once getting to Seplos. I can get the driver to continue and try again by setting switch 0 to on on the address selector of the BMS. Here is the additional log output when doing this - showing there is at least some communication via the RS485 adaptor and that it appears to be working on the os side.

2024-01-10 22:50:53.441686500 INFO:SerialBattery:Testing Seplos
2024-01-10 23:00:42.955435500 ERROR:SerialBattery:Unexpected err=UnicodeDecodeError('ascii', b'\x06\x00f\xe6', 3, 4, 'ordinal not in range(128)'), type(err)=<class 'UnicodeDecodeError'>
2024-01-10 23:00:42.955982500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2024-01-10 23:00:43.457148500 ERROR:SerialBattery:ERROR >>> No battery connection at /dev/ttyUSB1
2024-01-10 23:01:05.301439500 INFO:SerialBattery:

Note that with each different version of the driver I have tried the ttyUSB# has changed, this has not been an issue as the driver has just changed with it. So I don't suspect any issue here either.

[mdkeil]

Hm.. if you have an old Seplos 48100 10C (V1) with Fw 2.x (same switch layout like the 10E) the driver will not work. You can check the Fw-Version via Seplos BMS Battery Monitor

[mr-manuel]

There are two seplos drivers now implemented. Probably it works now.