Closed johndparker closed 8 months ago
Oh - I missed this log file
/data/log/serial-starter/current
2024-01-17 19:45:11.029505500 INFO: Start service dbus-fzsonick-48tl.ttyUSB2 once
2024-01-17 19:45:17.110954500 INFO: Start service dbus-imt-si-rs485tc.ttyUSB2 once
2024-01-17 19:45:22.657169500 INFO: Start service dbus-modbus-client.serial.ttyUSB2 once
2024-01-17 19:45:32.494473500 INFO: Start service dbus-serialbattery.ttyUSB2 once
2024-01-17 19:46:18.096106500 INFO: Start service gps-dbus.ttyUSB2 once
2024-01-17 19:46:27.897256500 INFO: Start service vedirect-interface.ttyUSB2 once
2024-01-17 19:46:31.782333500 INFO: Start service dbus-cgwacs.ttyUSB2 once
2024-01-17 19:57:08.220142500 INFO: Start service dbus-fzsonick-48tl.ttyUSB2 once
2024-01-17 19:57:14.082369500 INFO: Start service dbus-imt-si-rs485tc.ttyUSB2 once
2024-01-17 19:57:19.849634500 INFO: Start service dbus-modbus-client.serial.ttyUSB2 once
2024-01-17 19:57:30.004049500 INFO: Start service dbus-serialbattery.ttyUSB2 once
2024-01-17 19:58:15.171582500 INFO: Start service gps-dbus.ttyUSB2 once
2024-01-17 19:58:24.982766500 INFO: Start service vedirect-interface.ttyUSB2 once
2024-01-17 19:58:28.464374500 INFO: Start service dbus-cgwacs.ttyUSB2 once
2024-01-17 20:04:18.807548500 INFO: Start service dbus-fzsonick-48tl.ttyUSB2 once
2024-01-17 20:04:24.773427500 INFO: Start service dbus-imt-si-rs485tc.ttyUSB2 once
2024-01-17 20:04:30.548925500 INFO: Start service dbus-modbus-client.serial.ttyUSB2 once
2024-01-17 20:04:40.274294500 INFO: Start service dbus-serialbattery.ttyUSB2 once
2024-01-17 20:05:25.892674500 INFO: Start service gps-dbus.ttyUSB2 once
2024-01-17 20:05:35.573451500 INFO: Start service vedirect-interface.ttyUSB2 once
2024-01-17 20:05:39.089072500 INFO: Start service dbus-cgwacs.ttyUSB2 once
2024-01-17 20:14:34.189821500 INFO: Start service dbus-fzsonick-48tl.ttyUSB2 once
2024-01-17 20:14:39.954296500 INFO: Start service dbus-imt-si-rs485tc.ttyUSB2 once
2024-01-17 20:14:45.631621500 INFO: Start service dbus-modbus-client.serial.ttyUSB2 once
2024-01-17 20:14:55.629409500 INFO: Start service dbus-serialbattery.ttyUSB2 once
2024-01-17 20:15:40.881468500 INFO: Start service gps-dbus.ttyUSB2 once
2024-01-17 20:15:50.615057500 INFO: Start service vedirect-interface.ttyUSB2 once
2024-01-17 20:15:56.120442500 INFO: Start service dbus-cgwacs.ttyUSB2 once
2024-01-17 20:18:15.788605500 INFO: Start service dbus-fzsonick-48tl.ttyUSB2 once
2024-01-17 20:18:21.449173500 INFO: Start service dbus-imt-si-rs485tc.ttyUSB2 once
2024-01-17 20:18:25.272817500 INFO: Start service dbus-modbus-client.serial.ttyUSB2 once
2024-01-17 20:18:35.222458500 INFO: Start service dbus-serialbattery.ttyUSB2 once
2024-01-17 20:19:22.903842500 INFO: Start service gps-dbus.ttyUSB2 once
2024-01-17 20:19:33.147009500 INFO: Start service vedirect-interface.ttyUSB2 once
2024-01-17 20:19:38.617022500 INFO: Start service dbus-cgwacs.ttyUSB2 once
2024-01-17 20:28:03.963116500 INFO: Start service dbus-fzsonick-48tl.ttyUSB2 once
2024-01-17 20:28:09.941473500 INFO: Start service dbus-imt-si-rs485tc.ttyUSB2 once
2024-01-17 20:28:15.900071500 INFO: Start service dbus-modbus-client.serial.ttyUSB2 once
2024-01-17 20:28:25.808802500 INFO: Start service dbus-serialbattery.ttyUSB2 once
2024-01-17 20:29:12.951994500 INFO: Start service gps-dbus.ttyUSB2 once
2024-01-17 20:29:23.005303500 INFO: Start service vedirect-interface.ttyUSB2 once
2024-01-17 20:29:28.528030500 INFO: Start service dbus-cgwacs.ttyUSB2 once
Looks like something is struggling to do something with USB2 when it should be leaving it alone!
I thought I had fixed the ttyUSB2 problem but alas not!
I added ttyUSB2 to the exclude list but it is still being bothered by the serial-starter every 5 minutes.
2024-01-17 21:09:52.556506500 INFO: Start service dbus-imt-si-rs485tc.ttyUSB1 once
2024-01-17 21:09:54.264423500 INFO: Start service dbus-imt-si-rs485tc.ttyUSB3 once
2024-01-17 21:10:00.565903500 INFO: Create daemontools service dbus-modbus-client.serial.ttyUSB1
2024-01-17 21:10:02.730805500 INFO: Create daemontools service dbus-modbus-client.serial.ttyUSB3
2024-01-17 21:10:06.765045500 INFO: Start service dbus-modbus-client.serial.ttyUSB1 once
2024-01-17 21:10:09.014974500 INFO: Start service dbus-modbus-client.serial.ttyUSB3 once
2024-01-17 21:10:19.844939500 INFO: Start service dbus-serialbattery.ttyUSB1 once
2024-01-17 21:10:23.450401500 INFO: Start service dbus-serialbattery.ttyUSB3 once
2024-01-17 21:19:06.721438500 INFO: Create daemontools service dbus-fzsonick-48tl.ttyUSB2
2024-01-17 21:19:12.889849500 INFO: Start service dbus-fzsonick-48tl.ttyUSB2 once
2024-01-17 21:19:21.882777500 INFO: Create daemontools service dbus-imt-si-rs485tc.ttyUSB2
2024-01-17 21:19:28.037792500 INFO: Start service dbus-imt-si-rs485tc.ttyUSB2 once
2024-01-17 21:19:32.090322500 INFO: Create daemontools service dbus-modbus-client.serial.ttyUSB2
2024-01-17 21:19:38.144210500 INFO: Start service dbus-modbus-client.serial.ttyUSB2 once
2024-01-17 21:19:48.392957500 INFO: Create daemontools service dbus-serialbattery.ttyUSB2
2024-01-17 21:19:54.588415500 INFO: Start service dbus-serialbattery.ttyUSB2 once
2024-01-17 21:20:58.752736500 INFO: Create daemontools service gps-dbus.ttyUSB2
2024-01-17 21:21:04.838485500 INFO: Start service gps-dbus.ttyUSB2 once
2024-01-17 21:21:15.526938500 INFO: Create daemontools service vedirect-interface.ttyUSB2
2024-01-17 21:21:21.614435500 INFO: Start service vedirect-interface.ttyUSB2 once
2024-01-17 21:21:25.843677500 INFO: Start service dbus-cgwacs.ttyUSB2 once
2024-01-17 21:31:32.959378500 INFO: Start service dbus-fzsonick-48tl.ttyUSB2 once
2024-01-17 21:31:38.653844500 INFO: Start service dbus-imt-si-rs485tc.ttyUSB2 once
2024-01-17 21:31:42.336021500 INFO: Start service dbus-modbus-client.serial.ttyUSB2 once
2024-01-17 21:31:49.884570500 INFO: Start service dbus-serialbattery.ttyUSB2 once
2024-01-17 21:32:54.321329500 INFO: Start service gps-dbus.ttyUSB2 once
2024-01-17 21:33:03.978018500 INFO: Start service vedirect-interface.ttyUSB2 once
2024-01-17 21:33:09.576659500 INFO: Start service dbus-cgwacs.ttyUSB2 once
2024-01-17 21:36:17.963332500 INFO: Start service dbus-fzsonick-48tl.ttyUSB2 once
2024-01-17 21:36:23.680755500 INFO: Start service dbus-imt-si-rs485tc.ttyUSB2 once
2024-01-17 21:36:28.212978500 INFO: Start service dbus-modbus-client.serial.ttyUSB2 once
2024-01-17 21:36:39.394713500 INFO: Start service dbus-serialbattery.ttyUSB2 once
2024-01-17 21:37:47.475228500 INFO: Start service gps-dbus.ttyUSB2 once
2024-01-17 21:37:57.421021500 INFO: Start service vedirect-interface.ttyUSB2 once
2024-01-17 21:38:02.978176500 INFO: Start service dbus-cgwacs.ttyUSB2 once
2024-01-17 21:42:04.401150500 INFO: Start service dbus-fzsonick-48tl.ttyUSB2 once
2024-01-17 21:42:10.164738500 INFO: Start service dbus-imt-si-rs485tc.ttyUSB2 once
2024-01-17 21:42:16.075143500 INFO: Start service dbus-modbus-client.serial.ttyUSB2 once
2024-01-17 21:42:26.373322500 INFO: Start service dbus-serialbattery.ttyUSB2 once
2024-01-17 21:43:30.827707500 INFO: Start service gps-dbus.ttyUSB2 once
2024-01-17 21:43:40.665283500 INFO: Start service vedirect-interface.ttyUSB2 once
2024-01-17 21:43:44.317479500 INFO: Start service dbus-cgwacs.ttyUSB2 once
and the system is going into passthrough which is not acceptable.
config.ini is now
[DEFAULT]
; If you want to add custom values/settings, then check the values/settings you want to change in "config.default.ini"
; and insert them below to persist future driver updates.
; Example (remove the semicolon ";" to uncomment and activate the value/setting):
MAX_BATTERY_CHARGE_CURRENT = 140.0
MAX_BATTERY_DISCHARGE_CURRENT = 100.0
SOC_RESET_VOLTAGE = 3.450
BMS_TYPE = Seplos
EXCLUDED_DEVICES = /dev/ttyUSB2
If you have two identical BMS you have to increase the capacity of one battery by one, else you don't have an unique id for the battery. E.g. change the capacity for each battery to be different 280 281 279 282 278 ...
The small difference makes no serial impact.
Hi Mr Manuel
I'll try that but I'll also be looking for a better way to generate a unique ID - the adaptors have unique serial numbers in /dev/serial/by-id so we should be able to do that.
The problem with USB2 looks like a separate problem so I'll open a new ticket for that.
Having disabled the driver it looks like the grid meter is being left alone and the system is not going into passtrough.
Kind regards
John
I'll try that but I'll also be looking for a better way to generate a unique ID - the adaptors have unique serial numbers in /dev/serial/by-id so we should be able to do that.
The unique ID has to be fetched from the BMS and not the serial adapter. What if you swap the adapters? If you build a solution for this it won't be implemented, since it's not applicable for the wide community.
For your other problem try to swap the 0
with 1
in https://github.com/Louisvdw/dbus-serialbattery/blob/976ef061eca12e3fa4c8f95c6119cd4f3f9302ed/etc/dbus-serialbattery/dbus-serialbattery.py#L149
I'll try the sys.exit change in the morning, and will consider if there is something else unique in the Seplos BMS - it just does not feel right to mess with the capacity whereas linking it to how it is connected makes some sense - at least to me. I'll sleep on it.
Thank you for all your assistance.
Kind regards John
Since your batteries are for sure not exactly 280 Ah but have a deviation of +/- 2 % which are 5,6 Ah on a 280 Ah battery it's no big deal.
Describe the bug
I have installed and configured this driver together with dbus-aggregate-batteries and all is working very well so far except both individual batteries have the same VRM id of 1 instead of having separate ids. (The virtual combined battery has an id of 0) I see other discussion around this issue, but not for Seplos.
How to reproduce
Connect 2 Seplos BMS on separate USB to 485 adaptors
Expected behavior
Each serialbattery instance should have a separate VRM id.
Driver version
v1.0.20240102beta
Venus OS device type
Cerbo GX
Venus OS version
v3.13
BMS type
Seplos
Cell count
16
Battery count
2
Connection type
Serial USB adapter to RS485
Config file
Relevant log output
Any other information that may be helpful
I did not have to configure anything for both serialbatteries to appear in the RemoteConsole, and the aggregatebattery virtual found the instances and combined them again without any specific configuration.
Note also that this driver is interfering with ttyUSB2 which is actually one of my ET112 power meters. The other ET112 is on ttyUSB0 and that does not seem to be affected.
Perhaps the Seplos driver needs to use the connection (USB1 vs USB3) to create a unique ID?