Closed jmaunder closed 4 months ago
Please read carefully how to provide logs in correct format. Check the documentation or read carefully the instructions when you open an issue.
Please read carefully how to provide logs in correct format. Check the documentation or read carefully the instructions when you open an issue.
Thanks for your reply, not sure what I've done wrong? I tried to follow the instructions as best I could. Happy to supply more information, whatever is needed.
When opening an issue:
Please copy and paste any relevant log output here. See here how to get the driver log files. The content will be automatically formatted into code, so no need for backticks. ⚠️ IMPORTANT: Do not forget to pipe the output through
tai64nlocal
, if you don't copy the commands from the documentation.
When checking the here
link:
Anyway, your problem seems to be a unreliable USB to TTL adapter, since it disappears from the USB port. You could also check with lbusb
, if your adapter is still recognized after a failure.
I'm not sure it is, I have tried two different USB-TTL adapters and the problem persists. I tried 'lsusb' and the FTDI adapter appears there, so the adapter is present, but the serial-battery is not.
root@nanopi:~# lsusb
Bus 003 Device 023: ID 0403:6001 Future Technology Devices International, Ltd FT232 Serial (UART) IC
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 0bda:d723 Realtek Semiconductor Corp. 802.11n WLAN Adapter
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
When I run the command <tail -F -n 100 /data/log/serial-starter/current | grep dbus-serialbattery | tai64nlocal> I get no output. Opening 'current' directly from WinSCP below is a snippet of recent entries. There are no error or warning entries in the log.
@40000000665bd1f6181aa974 INFO: Start service dbus-modbus-client.serial.ttyUSB0 once
@40000000665bd1f924d6afdc INFO: Start service dbus-serialbattery.ttyUSB0 once
@40000000665bd2c833d5ef84 INFO: Start service gps-dbus.ttyUSB0 once
@40000000665bd2d2087fdd7c INFO: Start service vedirect-interface.ttyUSB0 once
@40000000665bd2d7167c2444 INFO: Start service dbus-cgwacs.ttyUSB0 once
@40000000665bd2dc23e5914c INFO: Start service dbus-fzsonick-48tl.ttyUSB0 once
@40000000665bd2df300df2d4 INFO: Start service dbus-imt-si-rs485tc.ttyUSB0 once
@40000000665bd2e300dc256c INFO: Start service dbus-modbus-client.serial.ttyUSB0 once
@40000000665bd2e60cfc266c INFO: Start service dbus-serialbattery.ttyUSB0 once
@40000000665bd2fd253faadc INFO: Start service gps-dbus.ttyUSB0 once
@40000000665bd3003190a6ec INFO: Start service vedirect-interface.ttyUSB0 once
@40000000665bd30402509144 INFO: Start service dbus-cgwacs.ttyUSB0 once
@40000000665bd30910b219ec INFO: Start service dbus-fzsonick-48tl.ttyUSB0 once
@40000000665bd30c1da6eb64 INFO: Start service dbus-imt-si-rs485tc.ttyUSB0 once
@40000000665bd30f2a38578c INFO: Start service dbus-modbus-client.serial.ttyUSB0 once
@40000000665bd31236e02a14 INFO: Start service dbus-serialbattery.ttyUSB0 once
Did you go through the whole troubleshooting section? There is exactly explained what to check.
Make sure to also check What to check, if it doesn't work.
Also try the latest nightly.
Describe the problem
My system: EasySolar-II GX, 6 x 50 Ah 17s LiFePO4 with JBD (Jiabaida) SP22S003 BMS. BMS communication is BMS UART <> Isolation module ADUM1201 <> Generic USB to TTL module <> USB cable <> USB port on GX card. Communication works OK with JBDtools. BMS modules have Bluetooth as well, but I found this to also be too unreliable, hence I am trying to do the serial connection. Problem: seemingly random intermittent loss of the serial connection, eventually it does not re-connect. Not reliable enough to put it into service. If I leave it long enough, it eventually re-established the connection but this might take more than 15 minutes, which is too long without BMS information for useful control. What I've tried: With USB hub and 2 x batteries, without USB hub and 1 x battery (direct connection). With aggregate-batteries and without it. Log file corresponds to 1 x battery and no USB hub, aggregate-batteries inactive.
Driver version
v1.2.20240401
Venus OS device type
GX Card (integrated in Victron device)
Venus OS version
v3.13
BMS type
Smart BMS (LLT, JBD, Overkill Solar)
Cell count
17
Battery count
1
Connection type
Serial USB adapter to TTL
Config file
Relevant log output
Any other information that may be helpful
The log output above is with the driver seemingly trying and re-trying to connect and failing. serial-battery is promising, but unless I can have reliable BMS communication I cannot use it. Motivated to get it working 100%. Very little dbus, Raspberry Pi, Unix and Python knowledge but I can learn. Some electronics knowledge. Rest of the system working well. Until I have serial-battery working I will rely on Multi charging algorithm and BMS only for protection, not control.