-
-
Notifications
You must be signed in to change notification settings - Fork 147
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Frequent driver restarts stop, when logging is reconfigured to DEBUG #877
Comments
here the same with 2 Batterys It looks like it only happens during discharge **Nr. 1**
@400000006564d9be339b0964 INFO:SerialBattery:
@400000006564d9be33ae4344 INFO:SerialBattery:Starting dbus-serialbattery
@400000006564d9be33da509c INFO:SerialBattery:dbus-serialbattery v1.0.20231126dev
@400000006564d9c918578b64 INFO:SerialBattery:
@400000006564d9c9186041dc INFO:SerialBattery:Starting dbus-serialbattery
@400000006564d9c91874279c INFO:SerialBattery:dbus-serialbattery v1.0.20231126dev
@400000006564d9d91931554c INFO:SerialBattery:-- Testing BMS: 1 of 3 rounds
@400000006564d9d9193c422c INFO:SerialBattery:Testing LltJbd
@400000006564d9da116a9c4c INFO:SerialBattery:Connection established to LltJbd
@400000006564d9da11736a34 INFO:SerialBattery:Battery LLT/JBD connected to dbus from /dev/ttyACM0
@400000006564d9da117af3e4 INFO:SerialBattery:========== Settings ==========
@400000006564d9da11825684 INFO:SerialBattery:> Connection voltage: 56.88V | Current: 0.0A | SoC: 28.44%
@400000006564d9da118a45c4 INFO:SerialBattery:> Cell count: 18 | Cells populated: 18
@400000006564d9da1191d35c INFO:SerialBattery:> LINEAR LIMITATION ENABLE: True
@400000006564d9da119a08ec INFO:SerialBattery:> MAX BATTERY CHARGE CURRENT: 100.0A | MAX BATTERY DISCHARGE CURRENT: 100.0A
@400000006564d9da11a22edc INFO:SerialBattery:> MAX BATTERY CHARGE CURRENT: 190.0A | MAX BATTERY DISCHARGE CURRENT: 190.0A (read from BMS)
@400000006564d9da11aa452c INFO:SerialBattery:> CVCM: True
@400000006564d9da11b2058c INFO:SerialBattery:> MIN CELL VOLTAGE: 2.9V | MAX CELL VOLTAGE: 3.45V
@400000006564d9da11b9be1c INFO:SerialBattery:> CCCM CV: True | DCCM CV: True
@400000006564d9da11c16edc INFO:SerialBattery:> CCCM T: True | DCCM T: True
@400000006564d9da11e9599c INFO:SerialBattery:> CCCM SOC: True | DCCM SOC: True
@400000006564d9da11ed0aec INFO:SerialBattery:Serial Number/Unique Identifier: 40_280.0Ah
@400000006564d9da2f0fe7ac INFO:SerialBattery:Found existing battery with DeviceInstance = 1
@400000006564d9da39b1284c INFO:SerialBattery:DeviceInstance = 1
@400000006564d9da39bd6904 INFO:SerialBattery:Used device instances: ['1']
@400000006564d9da39c78eac INFO:SerialBattery:com.victronenergy.battery.ttyACM0
@400000006564d9eb01d064c4 ERROR:SerialBattery:>>> ERROR: No reply - returning [len:31/36]
@400000006564d9eb020c298c ERROR:SerialBattery:ERROR >>> Problem with battery set up at /dev/ttyACM0
@400000006564d9eb022877a4 #0
@400000006564d9eb022892fc #1
@400000006564d9eb022896e4 #2
@400000006564d9eb02289acc #3
@400000006564d9eb0228a29c #4
@400000006564d9eb0228a684 #5
@400000006564d9eb0228aa6c #6
@400000006564d9eb0228b23c #7
@400000006564d9eb0228b624 #8
@400000006564d9eb0228ba0c #9
@400000006564d9eb0228bdf4 #10
@400000006564d9eb0228c5c4 #11
@400000006564d9eb0228c9ac #12
@400000006564d9eb0228cd94 #13
@400000006564d9eb0228d564 #14
@400000006564d9eb0228d94c #15
@400000006564d9eb0228dd34 #16
@400000006564d9eb0228e504 #17
@400000006564d9eb022969d4 Setted setting /Settings/Devices/serialbattery_40_280_0Ah/LastSeen to 1701108176
@400000006564d9fa00ffb2fc INFO:SerialBattery:
@400000006564d9fa010734dc INFO:SerialBattery:Starting dbus-serialbattery
@400000006564d9fa0116d0f4 INFO:SerialBattery:dbus-serialbattery v1.0.20231126dev
@400000006564da0a01ec9784 INFO:SerialBattery:-- Testing BMS: 1 of 3 rounds
@400000006564da0a01f5750c INFO:SerialBattery:Testing LltJbd
@400000006564da0a36208f4c INFO:SerialBattery:Connection established to LltJbd
@400000006564da0a3630d744 INFO:SerialBattery:Battery LLT/JBD connected to dbus from /dev/ttyACM0
@400000006564da0a36430b6c INFO:SerialBattery:========== Settings ==========
@400000006564da0a364326c4 INFO:SerialBattery:> Connection voltage: 56.91V | Current: 1.29A | SoC: 28.44%
@400000006564da0a366e789c INFO:SerialBattery:> Cell count: 18 | Cells populated: 18
@400000006564da0a368081cc INFO:SerialBattery:> LINEAR LIMITATION ENABLE: True
@400000006564da0a368563cc INFO:SerialBattery:> MAX BATTERY CHARGE CURRENT: 100.0A | MAX BATTERY DISCHARGE CURRENT: 100.0A
@400000006564da0a36b9dd64 INFO:SerialBattery:> MAX BATTERY CHARGE CURRENT: 190.0A | MAX BATTERY DISCHARGE CURRENT: 190.0A (read from BMS)
@400000006564da0a36bbd934 INFO:SerialBattery:> CVCM: True
@400000006564da0a3715ebcc INFO:SerialBattery:> MIN CELL VOLTAGE: 2.9V | MAX CELL VOLTAGE: 3.45V
@400000006564da0a3720b584 INFO:SerialBattery:> CCCM CV: True | DCCM CV: True
@400000006564da0a3729642c INFO:SerialBattery:> CCCM T: True | DCCM T: True
@400000006564da0a3731e3f4 INFO:SerialBattery:> CCCM SOC: True | DCCM SOC: True
@400000006564da0a373b3e7c INFO:SerialBattery:Serial Number/Unique Identifier: 40_280.0Ah
@400000006564da0b151aafe4 INFO:SerialBattery:Found existing battery with DeviceInstance = 1
@400000006564da0b1efa1784 INFO:SerialBattery:DeviceInstance = 1
@400000006564da0b1f02ed3c INFO:SerialBattery:Used device instances: ['1']
@400000006564da0b1f0ac8f4 INFO:SerialBattery:com.victronenergy.battery.ttyACM0
@400000006564da0c051e5744 INFO:SerialBattery:publish config values = 1 **Nr.2**
@400000006564d9be37a264bc INFO:SerialBattery:
@400000006564d9be37a283fc INFO:SerialBattery:Starting dbus-serialbattery
@400000006564d9be37adeddc INFO:SerialBattery:dbus-serialbattery v1.0.20231126dev
@400000006564d9c917fcdc8c INFO:SerialBattery:
@400000006564d9c9180a9c14 INFO:SerialBattery:Starting dbus-serialbattery
@400000006564d9c9182196e4 INFO:SerialBattery:dbus-serialbattery v1.0.20231126dev
@400000006564d9d918c871bc INFO:SerialBattery:-- Testing BMS: 1 of 3 rounds
@400000006564d9d918c88d14 INFO:SerialBattery:Testing LltJbd
@400000006564d9da114881d4 INFO:SerialBattery:Connection established to LltJbd
@400000006564d9da11530d0c INFO:SerialBattery:Battery LLT/JBD connected to dbus from /dev/ttyACM1
@400000006564d9da115b429c INFO:SerialBattery:========== Settings ==========
@400000006564d9da1166a4ac INFO:SerialBattery:> Connection voltage: 56.84V | Current: 0.0A | SoC: 31.26%
@400000006564d9da117202d4 INFO:SerialBattery:> Cell count: 18 | Cells populated: 18
@400000006564d9da117dab34 INFO:SerialBattery:> LINEAR LIMITATION ENABLE: True
@400000006564d9da11883284 INFO:SerialBattery:> MAX BATTERY CHARGE CURRENT: 100.0A | MAX BATTERY DISCHARGE CURRENT: 100.0A
@400000006564d9da1194251c INFO:SerialBattery:> MAX BATTERY CHARGE CURRENT: 190.0A | MAX BATTERY DISCHARGE CURRENT: 190.0A (read from BMS)
@400000006564d9da119e6a04 INFO:SerialBattery:> CVCM: True
@400000006564d9da11a8e1b4 INFO:SerialBattery:> MIN CELL VOLTAGE: 2.9V | MAX CELL VOLTAGE: 3.45V
@400000006564d9da11b47e5c INFO:SerialBattery:> CCCM CV: True | DCCM CV: True
@400000006564d9da11be9c34 INFO:SerialBattery:> CCCM T: True | DCCM T: True
@400000006564d9da11ce6efc INFO:SerialBattery:> CCCM SOC: True | DCCM SOC: True
@400000006564d9da11f6618c INFO:SerialBattery:Serial Number/Unique Identifier: 40_280.0Ah
@400000006564d9da2f40e2bc INFO:SerialBattery:Found existing battery with DeviceInstance = 1
@400000006564d9da3a88f664 INFO:SerialBattery:DeviceInstance = 1
@400000006564d9da3a97f254 INFO:SerialBattery:Used device instances: ['1']
@400000006564d9da3aa26dec INFO:SerialBattery:com.victronenergy.battery.ttyACM1
@400000006564d9db203c6354 INFO:SerialBattery:publish config values = 1
@400000006564dd7a01e6985c ERROR:SerialBattery:>>> ERROR: No reply - returning
@400000006564dd7b01f12b64 ERROR:SerialBattery:>>> ERROR: No reply - returning
@400000006564dd7c0fdea904 ERROR:SerialBattery:>>> ERROR: No reply - returning
@400000006564dd7d01c9f83c ERROR:SerialBattery:>>> ERROR: No reply - returning
@400000006564dd7e108e654c ERROR:SerialBattery:>>> ERROR: No reply - returning
@400000006564dd7f106019bc ERROR:SerialBattery:>>> ERROR: No reply - returning
@400000006564dd80025a5d14 ERROR:SerialBattery:>>> ERROR: No reply - returning
@400000006564dd8101f7ce9c ERROR:SerialBattery:>>> ERROR: No reply - returning
@400000006564dd8202435e5c ERROR:SerialBattery:>>> ERROR: No reply - returning
@400000006564dd830225c054 ERROR:SerialBattery:>>> ERROR: No reply - returning
@400000006564dd84103f243c ERROR:SerialBattery:>>> ERROR: No reply - returning
@400000006564dd85039198dc ERROR:SerialBattery:>>> ERROR: No reply - returning
@400000006564dd8610b33afc ERROR:SerialBattery:>>> ERROR: No reply - returning
@400000006564dd87025bff0c ERROR:SerialBattery:>>> ERROR: No reply - returning
@400000006564dd89029cd4b4 ERROR:SerialBattery:>>> ERROR: No reply - returning
@400000006564dd8b02badc34 ERROR:SerialBattery:>>> ERROR: No reply - returning
@400000006564dd8c032f0294 ERROR:SerialBattery:>>> ERROR: No reply - returning
@400000006564dd8d02ca5cf4 ERROR:SerialBattery:>>> ERROR: No reply - returning
@400000006564dd8e11630acc ERROR:SerialBattery:>>> ERROR: No reply - returning
@400000006564dd8f033714fc ERROR:SerialBattery:>>> ERROR: No reply - returning
@400000006564dd90122e982c ERROR:SerialBattery:>>> ERROR: No reply - returning
@400000006564dd91031eaafc ERROR:SerialBattery:>>> ERROR: No reply - returning
@400000006564dd920377a454 ERROR:SerialBattery:>>> ERROR: No reply - returning
@400000006564dd93036cde84 ERROR:SerialBattery:>>> ERROR: No reply - returning
@400000006564dd94044fa14c ERROR:SerialBattery:>>> ERROR: No reply - returning
@400000006564dd9503768efc ERROR:SerialBattery:>>> ERROR: No reply - returning
@400000006564dd9603db925c ERROR:SerialBattery:>>> ERROR: No reply - returning
@400000006564dd9703932f1c ERROR:SerialBattery:>>> ERROR: No reply - returning
@400000006564dd9803b2d0c4 ERROR:SerialBattery:>>> ERROR: No reply - returning
@400000006564dd99048157dc ERROR:SerialBattery:>>> ERROR: No reply - returning
@400000006564dd9a047987dc ERROR:SerialBattery:>>> ERROR: No reply - returning
@400000006564dd9b045b2a6c ERROR:SerialBattery:>>> ERROR: No reply - returning
@400000006564dd9c04e6e00c ERROR:SerialBattery:>>> ERROR: No reply - returning
@400000006564dd9d04a308dc ERROR:SerialBattery:>>> ERROR: No reply - returning
@400000006564dd9e04e85edc ERROR:SerialBattery:>>> ERROR: No reply - returning
@400000006564dd9f0513c054 ERROR:SerialBattery:>>> ERROR: No reply - returning
@400000006564dda005402784 ERROR:SerialBattery:>>> ERROR: No reply - returning
@400000006564dda105d0de64 ERROR:SerialBattery:>>> ERROR: No reply - returning
@400000006564dda205fba784 ERROR:SerialBattery:>>> ERROR: No reply - returning
@400000006564ddab12499a3c ERROR:SerialBattery:>>> ERROR: No reply - returning
@400000006564ddac0628b2c4 ERROR:SerialBattery:>>> ERROR: No reply - returning |
You have also the unique identifier on both batteries the same. Change the capacity on one + or - 1 amp |
i changed it... but the failure is the same... Nr1. Nr.2 |
every time it is the same BMS... |
@stixif Does your problem go away when you change the logging to DEBUG? To me it does not look like it. So it might be something else, given that it is only the one BMS that fails not both. Are You using isolated interfaces? Are the two ground lines of the two interfaces isolated from each other. It should be yes in both cases. |
@beliffm yes to both... In the Last months it worket normaly |
with the newest dev from 28.11 it looks like good! |
Are you using Ruuvi tags? |
@mr-manuel |
@beliffm could you also test the latest build? |
@mr-manuel @4000000065676b3611eb8c1c INFO:SerialBattery:-- Testing BMS: 1 of 3 rounds |
Probably one value is out of the bounds. I will add some debugging to check that. |
i checked my values in the BMS and found an empty one... |
Will do... |
No change, restarts happening on both BMS every ten minutes or so. Any thoughts on the impact of the logging setting? |
Try to set this to 2000.
|
That helped. No more restarts. All that is left now since 8:07, when i made the change, is what can be seen in the log excerpt below. Those errors may result from a different issue though. ==> /data/log/dbus-serialbattery.ttyUSB1/current <== ==> /data/log/dbus-serialbattery.ttyUSB2/current <== ==> /data/log/dbus-serialbattery.ttyUSB1/current <== |
Maybe your BMS gets overloaded with polling every 2 seconds. What is your cpu usage of the gx card when you set it again to 1000? |
CPU usage is about 10% in both cases... Maybe polling every second really is too fast for the BMSes. Since this morning there have been some occurances, but by far not as many as before. |
If you did not already try other USB to serial converters it could also be that the converter is the problem. |
Finally the quad-converter from duppa.net arrived yesterday. Since i changed my build-up to this converter the restarts have stopped completely even if i reset the polling rate back to 1000ms. Mind you, the LLTJBD-BMS has 12V supply on the UART connector which has to be converted to 5V to suit the Duppa.net converter. Formerly i used two converters which came with the BMSs together with an Auge USB hub. Maybe the GX card does not provide enough power for such a construction at high polling rates. |
Describe the problem
I have been experiencing frequent driver restarts on both of my two BMSes. They all take place in a similar pattern which can be seen in the log below, In order to gain more information to tackle the problem i switched the log level to debug, only to find that the restarts stopped. I monitored the situation for more than two hours, not a single driver restart. What happened after i reconfigured to default logging can be seen below. Only after some minutes there was a restart.
My guess is, given that the serial connection is only 9600 baud, the polling is somewhat to "fast" and the serial buffer is not yet filled, which is then interpreted wrongly and triggers the restart. A higher log level slows the polling loop down, thus avoiding the situation of an empty buffer.
Driver version
v1.0.20231117dev
Venus OS device type
GX Card (integrated in Victron device)
Venus OS version
V3.20~26
BMS type
Smart BMS (LLT, JBD, Overkill Solar)
Cell count
16
Connection type
Serial USB adapter to TTL
Config file
Relevant log output
Any other information that may be helpful
No response
The text was updated successfully, but these errors were encountered: