clearly identify daly battery with. multiply batteries set up

[teefixx]

Hi all

I have a setup with two daly BMS in my system and cannot distinct them automatically as the driver assigns the same name to the batteries. If the VRM instance or the USB port changes, I don't know which battery is No1 or No2.

So far (at least via MQTT) there is no value read out which distincts a battery clearly.

@transistorgit
you corrected already the daly.py file. Would it be possibel to read out as well eg the battery production date or the battery code from the daly bms and publish it on MQTT? This way, one could set the date or the code accordingly to distinct the batteries as well in MQTT and further in nodered...

I'm open for other suggestions to solve this as well...
thank you

[transistorgit]

Hi,

it would be easy if we get the needed documentation. In any Daly protocol docs that I've seen, there's nothing like a serial number.
I think it would be possible to reengineer the traffic of the daly PCMaster software, but somebody has to spend the effort.

brgds
Bernd

[mr-manuel]

Please address this also, if you are looking into it: #31 Only 2. is left.

[teefixx]

Hi
I reached out to Daly directly, there is a contact which I had once in a while ago. Let's see if there is a respond...

[mr-manuel]

Could you also remove the wildcard imports? That would be great!

I already fixed them.

[mr-manuel]

I requested the documentation from the official Aliexpress dealer. Unfortunately the daly doesn't seem to send much data.

Daly UART_485.pdf

[teefixx]

Hi all
I requested it from Daly directly, no answer so far.
Inbetween I found two ressources which seem to have decoded some stuff:

here is an excel file with most of the hex commands
https://diysolarforum.com/threads/new-daly-smart-bms-w-communication-80-250a.7002/page-29#post-334645

here is a post with even more hex commands
https://diysolarforum.com/threads/decoding-the-daly-smartbms-protocol.21898/

They even are able to set SOC, which would be very helpful. This way you could correct the SOC automatically via node red when it (as in my case) always only charges to 99.5%...

[transistorgit]

very nice, with that info it should be quite easy (if the info is accurate at least)
I can look into it inthe next days.
@mr-manuel is it possible to merge pull request #484 ? It would be much nicer to proceed on a working serial implementation.

[mr-manuel]

Unfortunately I cannot merge into the master branch. I merged your changes into the jkbms_ble branch. #587

You can work on the jkbms_ble branch, since it will be merged once my PR for the master branch is merged. Else you can fork my master branch, there is also the latest Daly driver with my changes from today.

[mr-manuel]

It seems that JBD stopped working after #484: #593

[teefixx]

@mr-manuel
can you tell me, what's the most up to date branch? there are now jkbms_ble in your repository, one in Louisvdw jibes_ble branch and the master branch in your repository...

[mr-manuel]

In my repository the master and jkbms_ble branch are up to date. In the repository of Louisvdw the jkbms_ble branch gets daily updated from my jkbms_ble branch.

[teefixx]

Hi all,

tried to test the hex strings with node red just to make sure they generate the answer which is expected. Somehow I run into problems:
When I send "\xa5\x40\x90\x08\x00\x00\x00\x00\x00\x00\x00\x00\x7d" I expect to get an answer with "\xA5\x01\x90\x08" but this varies. Sometimes I get X94 or X91 instead of X91... (see attached picture where red is input and the array is the output)

I try to test this as my plan is to switch MOS from Noderred in the future, which, btw, does not work either. I'm not sure if I use the right syntax in the nodes. Would be much appreciated, if someone could check my Nodered flow...

What I see as well, just fyi: as soon as I activate the flow, the BMS is no longer connected to the bus-serialbattery driver and so not updated in venusOS. I need to deactivate the flow in Nodered to see the battery updated in VenusOS again. If we want to control the BMS via Nodered in the future, we need to find a way around that as well...

thank you

daly.txt

[transistorgit]

Hi,
I never really used node-red. But at least your request look ok and should generate the desired answer. BUT: you cannot talk to the BMS at the same time from node red and serialbattery. While using node red, serial battery has to be completely off. and even though, the serial probing of the other drivers would probably disturb your requests. That you get wrong answers clearly look like to stations talking on the same channel.
I would strongly recommend not to use node red for serial comm on venus.

brgds
Bernd

[teefixx]

I see, that's what I guessed...

Regarding your question about the trigger for resetting SOC in #31

What still would work is the approach mr-manuel has chosen with the dbus-mqtt-battery driver: if we could make the dbus-serialdriver script polling from the MQTT broker, the possibilities would be great: you could set SOC via MQTT but as well switch off charging or discharging MOS.
The communication with the daly BMS would still be handled via the driver, while the input of the values could be handled by the user or node red...

[transistorgit]

Ok, mqtt would be quite easy. But it sounds a bit strange to mix these communication types. More straight forward would be a message over dbus. Like you can switch modes of the multiplus by button in remote console. This way would be more standard and you can also trigger it by node red.

[teefixx]

either or is ok for me... As long as it can be triggered via Nodered.

Did you get as well the definitions to switch on and off the MOS? if not, it's here: https://diysolarforum.com/threads/decoding-the-daly-smartbms-protocol.21898/page-2#post-385365

hope I get answer how to set the board number of the daly bms from daly quite soon, that way we could address a specific bms via dbus...

[transistorgit]

@teefixx I created a pull request with production date added to the hardware version string. This should solve your identification problem

[teefixx]

Great news. Can we set "allow to charge" and "allow to discharge" as well in the same way?

[mr-manuel]

@teefix could you check, if this date is already populated in your BMS or if you have to fill it out? mr-manuel/venus-os_dbus-serialbattery#5

[teefixx]

I filled it in when I assembled the batteries. I'm not quite sure but think I remember, that the date field was empty initial...

[teefixx]

I'm not at home now, do I just have to exchange daly.py to try this out?

[mr-manuel]

I filled it in when I assembled the batteries. I'm not quite sure but think I remember, that the date field was empty initial...

Thats all I needed. The driver now populates two more fields in the "Device" page. So you can identify your BMS by checking "serial number" and/or "device name".

https://github.com/mr-manuel/venus-os_dbus-serialbattery/blob/f79ce837b9de7e5b940d643838fc251682e95d8a/etc/dbus-serialbattery/dbushelper.py#L132-L137

Since currently at least three people are working on this driver at the same time, I will merge all changes later today. Then you can install the latest nightly ;-)

[teefixx]

serial with date works great, just tested it. THANK YOU
did I get it right: the device name field is populated by the production date?
Wouldn't it be possible to connect the device name field with the Battery Code field. Battery code is a free text field in the Daly BMS...

[mr-manuel]

Could you post a screenshot of how it is now? I did understand, that the production date filed is the free text field. In the protocol documentation I find no battery code, so probably this is not available. But let's wait what @transistorgit says.

[teefixx]

this is how it looks like right now:

[mr-manuel]

Could you post a screenshot of the remote console/GUI -> SerialBattery -> Device page?

[teefixx]

this is a screenshot of the Daly App, the battery production date is not a free text field.
The battery code field is a free text field, although not mentioned in the official documentation.

Luckily a user has decoded the daly communication:

-> a5 40 57 08 00 00 00 00 00 00 00 00 44 // ??? Query the "Battery code"
<- a5 01 57 08 01 32 30 32 30 30 33 30 5d
<- a5 01 57 08 02 36 20 20 20 20 20 20 fd
<- a5 01 57 08 03 20 20 20 20 20 20 20 e8
<- a5 01 57 08 04 20 20 20 20 20 20 20 e9
<- a5 01 57 08 05 20 20 20 20 20 20 20 ea

you can find this on https://diysolarforum.com/threads/decoding-the-daly-smartbms-protocol.21898/#post-258169

[teefixx]

Could you post a screenshot of the remote console/GUI -> SerialBattery -> Device page?

[teefixx]

there seems to be a problem now with the ChargeCycles, did you change something there? It used to work before the update, see screenshot

[transistorgit]

Hi,

we can also use battery code. Sounds even better than production date (which is really a date field), just hope that it has no special meaning? But in my devices, theres is just also date code in:

So it sounds quite safe. What do you think @mr-manuel, especially regarding having comparable functionality over all bms types?

The charge cycles are read with the same transmission that also includes the cell count and hasn't changed.
I just pulled the current jkbms_ble branch and tested here. My cycle count is here:

[teefixx]

The charge cycles are read with the same transmission that also includes the cell count and hasn't changed. I just pulled the current jkbms_ble branch and tested here. My cycle count is here:

My cycle count looks like this:

edit: I installed your latest build right now and now it works again...

[teefixx]

sorry to bother you with this, but after 5min the total charge cycles vanish again.
If I execute the reinstall-local.sh script it comes back...

I see the same behavior with ConsumedAmphours.

[mr-manuel]

@transistorgit I changed it a bit in case, that the field is empty. Additionaly I added a cleanup for the string and removed whitespaces for the unique_identifier.

mr-manuel/venus-os_dbus-serialbattery@8953689

[mr-manuel]

sorry to bother you with this, but after 5min the total charge cycles vanish again. If I execute the reinstall-local.sh script it comes back...

I see the same behavior with ConsumedAmphours.

No errors in the logfile?

[teefixx]

There are errors indeed:

current.txt

[transistorgit]

hm, just checked my device again, no errors. Please check the load with uptime
uptime
and if possible check with ps how many serial-battery processes are running
ps | grep dbus-serial
because I have seen that old processes were not cleaned up correctly (that was while debugging, but just to be shure)
In that case a reboot should fix that.

[mr-manuel]

If the processes are not cleaned up correctly let me know, I had the same problem with the blebattrry services

[teefixx]

root@PiVenusOS:/data/log/dbus-serialbattery.ttyUSB2# uptime
 19:29:10 up 2 days, 50 min,  load average: 0.67, 1.28, 1.41
root@PiVenusOS:/data/log/dbus-serialbattery.ttyUSB2# ps | grep dbus-serial
 1844 root      1612 S    supervise dbus-serialbattery.ttyUSB4
 1847 root      1756 S    multilog t s25000 n4 /var/log/dbus-serialbattery.ttyUSB4
 2427 root      1612 S    supervise dbus-serialbattery.ttyUSB2
 2429 root      1756 S    multilog t s25000 n4 /var/log/dbus-serialbattery.ttyUSB2
11363 root      3048 S    {start-serialbat} /bin/bash /opt/victronenergy/dbus-serialbattery/start-serialbattery.sh tty
11365 root     23472 S    python /opt/victronenergy/dbus-serialbattery/dbus-serialbattery.py /dev/ttyUSB2
11408 root      3048 S    {start-serialbat} /bin/bash /opt/victronenergy/dbus-serialbattery/start-serialbattery.sh tty
11410 root     20256 S    python /opt/victronenergy/dbus-serialbattery/dbus-serialbattery.py /dev/ttyUSB4
11728 root      2692 S    grep dbus-serial
root@PiVenusOS:/data/log/dbus-serialbattery.ttyUSB2# 

[mr-manuel]

@teefixx could you also join the Discord server? https://discord.gg/YXzFB8rSgx so short communication is easier

[teefixx]

@transistorgit Changing the value to 50 did not help. In my opinion it has to do something with the updates in the last week, before that everything worked and I never had the errors / missing values...

[transistorgit]

yes, you're right. And we read some more data from the BMS now, so the load is a bit higher and the loop will take a bit more time.

[transistorgit]

@teefixx mr-manual just pointed me to the fact that you use a daly, so the code change was in the wrong file. can you redo the check in the serial read routine for daly in daly.py Line 519 please? sorry for the confusion

dbus-serialbattery/etc/dbus-serialbattery/bms/daly.py

Line 519 in aff297e

if count > 150:

[mr-manuel]

You could also try to increase

dbus-serialbattery/etc/dbus-serialbattery/bms/daly.py

Line 486 in aff297e

if count > 50:

[Louisvdw]

We have always had issues with Daly BMS. Their comms protocol is badly designed. The amount of requests that has to be done and the baud speed used is terrible. This limits what can be transfered and how fast you can get a new set of data from the BMS.

battery.poll_interval was added to help with Daly's. So we can set a polling interval that is slower (e.g. 2sec) to give time to get all the data back before we request again.
But that is slow. So a poll_step was added (def refresh_data around line 80) so that we can get the important updates every second and others every 2 seconds).
If you add more requests (like identifiers and such) then these steps and poll intervals will need to be adjusted to give time for everything to complete.
Best is to start with changing Daly.py ln19 to
self.poll_interval = 2000
Then if that works tweeking it to the shortest values that works for everyone.

[transistorgit]

there are some more structural problems in the serial receive code. One is that the handling of packet length is broken, I fixed that for daly but can't do that for other BMS because I can't test. MrManuel and I decided to just fix it in Daly.py.

The other thing I mean is the central while loop that waits for the message bytes.
It loop 150 times if it doesn't receive enough bytes. There's a sleep(0.005) so you can think it takes 750ms max.

In reality it can take 15.75s because it hangs in serial.read() each time until it times aus after 100ms. This leads to huge stalls if there are communication issues and e.g. the request got lost.

[mr-manuel]

I made a few more tests.

dbus-serialbattery/etc/dbus-serialbattery/dbus-serialbattery.py

Line 128 in 2184aa6

gobject.timeout_add(battery.poll_interval, lambda: poll_battery(mainloop))

Always waits until the loop finished. Increasing self.poll_interval = 2000 reduces only the stress on the BMS. It's also possible to set self.poll_interval = 10, then the next interval is polled immediately. Therefore

dbus-serialbattery/etc/dbus-serialbattery/bms/daly.py

Lines 101 to 104 in 13a9f41

	if self.busy:
	logger.info("> refresh_data: CURRENTLY BUSY!")
	return False
	self.busy = True

is never triggered, so I removed it again.

Instead of waiting for loops

dbus-serialbattery/etc/dbus-serialbattery/bms/daly.py

Line 519 in aff297e

if count > 150:

@transistorgit introduced waiting by time, which also helped a bit.

Then I added a bit of logging informations:

Logs

09:06:40.086273500 INFO:SerialBattery:refresh_data: start
09:06:40.139481500 INFO:SerialBattery:  |- refresh_data: read_soc_data - result: True - runtime: 0.042559s
09:06:40.183569500 INFO:SerialBattery:  |- refresh_data: read_fed_data - result: True - runtime: 0.042741s
09:06:40.221649500 INFO:SerialBattery:  |- refresh_data: read_cell_voltage_range_data - result: True - runtime: 0.036007s
09:06:40.222599500 INFO:SerialBattery:  |- refresh_data: write_soc_and_datetime - result: True - runtime: 0.036007s
09:06:40.271724500 INFO:SerialBattery:  |- refresh_data: read_alarm_data - result: True - runtime: 0.047698s
09:06:40.313113500 INFO:SerialBattery:  |- refresh_data: read_temperature_range_data - result: True - runtime: 0.040122s
09:06:40.314458500 INFO:SerialBattery:refresh_data: end - result: True
09:06:40.330565500 INFO:SerialBattery:refresh_data: start
09:06:40.380560500 INFO:SerialBattery:  |- refresh_data: read_soc_data - result: True - runtime: 0.04258s
09:06:40.422243500 INFO:SerialBattery:  |- refresh_data: read_fed_data - result: True - runtime: 0.040123s
09:06:40.460652500 INFO:SerialBattery:  |- refresh_data: read_cell_voltage_range_data - result: True - runtime: 0.037029s
09:06:40.461284500 INFO:SerialBattery:  |- refresh_data: write_soc_and_datetime - result: True - runtime: 0.037029s
09:06:40.621744500 INFO:SerialBattery:  |- refresh_data: read_cells_volts - result: True - runtime: 0.159057s
09:06:40.660188500 INFO:SerialBattery:  |- refresh_data: read_balance_state - result: True - runtime: 0.036782s
09:06:40.661085500 INFO:SerialBattery:refresh_data: end - result: True
09:06:40.689674500 INFO:SerialBattery:refresh_data: start
09:06:40.751019500 INFO:SerialBattery:  |- refresh_data: read_soc_data - result: True - runtime: 0.043093s
09:06:40.789329500 INFO:SerialBattery:  |- refresh_data: read_fed_data - result: True - runtime: 0.037235s
09:06:40.835068500 INFO:SerialBattery:  |- refresh_data: read_cell_voltage_range_data - result: True - runtime: 0.044473s
09:06:40.835678500 INFO:SerialBattery:  |- refresh_data: write_soc_and_datetime - result: True - runtime: 0.044473s
09:06:40.884150500 INFO:SerialBattery:  |- refresh_data: read_alarm_data - result: True - runtime: 0.047146s
09:06:40.942884500 INFO:SerialBattery:  |- refresh_data: read_temperature_range_data - result: True - runtime: 0.057415s
09:06:40.944000500 INFO:SerialBattery:refresh_data: end - result: True
09:06:40.966342500 INFO:SerialBattery:refresh_data: start
09:06:41.011208500 INFO:SerialBattery:  |- refresh_data: read_soc_data - result: True - runtime: 0.03874s
09:06:41.049931500 INFO:SerialBattery:  |- refresh_data: read_fed_data - result: True - runtime: 0.037526s
09:06:41.093541500 INFO:SerialBattery:  |- refresh_data: read_cell_voltage_range_data - result: True - runtime: 0.042255s
09:06:41.094373500 INFO:SerialBattery:  |- refresh_data: write_soc_and_datetime - result: True - runtime: 0.042255s
09:06:41.257112500 INFO:SerialBattery:  |- refresh_data: read_cells_volts - result: True - runtime: 0.160911s
09:06:41.302932500 INFO:SerialBattery:  |- refresh_data: read_balance_state - result: True - runtime: 0.044593s
09:06:41.303937500 INFO:SerialBattery:refresh_data: end - result: True
09:06:41.322223500 INFO:SerialBattery:refresh_data: start
09:06:41.373866500 INFO:SerialBattery:  |- refresh_data: read_soc_data - result: True - runtime: 0.042735s
09:06:41.424014500 INFO:SerialBattery:  |- refresh_data: read_fed_data - result: True - runtime: 0.048643s
09:06:41.473728500 INFO:SerialBattery:  |- refresh_data: read_cell_voltage_range_data - result: True - runtime: 0.048171s
09:06:41.474542500 INFO:SerialBattery:  |- refresh_data: write_soc_and_datetime - result: True - runtime: 0.048171s
09:06:41.513666500 INFO:SerialBattery:  |- refresh_data: read_alarm_data - result: True - runtime: 0.037703s
09:06:41.561580500 INFO:SerialBattery:  |- refresh_data: read_temperature_range_data - result: True - runtime: 0.046713s
09:06:41.562690500 INFO:SerialBattery:refresh_data: end - result: True
09:06:41.576771500 INFO:SerialBattery:refresh_data: start
09:06:41.621339500 INFO:SerialBattery:  |- refresh_data: read_soc_data - result: True - runtime: 0.038999s
09:06:41.659577500 INFO:SerialBattery:  |- refresh_data: read_fed_data - result: True - runtime: 0.036944s
09:06:41.702664500 INFO:SerialBattery:  |- refresh_data: read_cell_voltage_range_data - result: True - runtime: 0.041673s
09:06:41.705002500 INFO:SerialBattery:  |- refresh_data: write_soc_and_datetime - result: True - runtime: 0.041673s
09:06:41.864949500 INFO:SerialBattery:  |- refresh_data: read_cells_volts - result: True - runtime: 0.158635s
09:06:41.902589500 INFO:SerialBattery:  |- refresh_data: read_balance_state - result: True - runtime: 0.03689s
09:06:41.903600500 INFO:SerialBattery:refresh_data: end - result: True
09:06:41.920652500 INFO:SerialBattery:refresh_data: start
09:06:41.980650500 INFO:SerialBattery:  |- refresh_data: read_soc_data - result: True - runtime: 0.038988s
09:06:42.023616500 INFO:SerialBattery:  |- refresh_data: read_fed_data - result: True - runtime: 0.041854s
09:06:42.072709500 INFO:SerialBattery:  |- refresh_data: read_cell_voltage_range_data - result: True - runtime: 0.047796s
09:06:42.073572500 INFO:SerialBattery:  |- refresh_data: write_soc_and_datetime - result: True - runtime: 0.047796s
09:06:42.112098500 INFO:SerialBattery:  |- refresh_data: read_alarm_data - result: True - runtime: 0.036891s
09:06:42.152346500 INFO:SerialBattery:  |- refresh_data: read_temperature_range_data - result: True - runtime: 0.038767s
09:06:42.153356500 INFO:SerialBattery:refresh_data: end - result: True
09:06:42.184327500 INFO:SerialBattery:refresh_data: start
09:06:42.233004500 INFO:SerialBattery:  |- refresh_data: read_soc_data - result: True - runtime: 0.041884s
09:06:42.281783500 INFO:SerialBattery:  |- refresh_data: read_fed_data - result: True - runtime: 0.047032s
09:06:42.321111500 INFO:SerialBattery:  |- refresh_data: read_cell_voltage_range_data - result: True - runtime: 0.038439s
09:06:42.321562500 INFO:SerialBattery:  |- refresh_data: write_soc_and_datetime - result: True - runtime: 0.038439s
09:06:43.277045500 ERROR:SerialBattery:>>> ERROR: No reply - returning
09:06:43.281233500 WARNING:SerialBattery:No data received in read_cells_volts()
09:06:43.282238500 INFO:SerialBattery:  |- refresh_data: read_cells_volts - result: False - runtime: 0.954639s
09:06:43.283490500 INFO:SerialBattery:  |- refresh_data: read_balance_state - result: False - runtime: 0.954639s
09:06:43.284866500 INFO:SerialBattery:refresh_data: end - result: False
09:06:43.292441500 INFO:SerialBattery:refresh_data: start
09:06:43.349982500 INFO:SerialBattery:  |- refresh_data: read_soc_data - result: True - runtime: 0.052375s
09:06:43.393974500 INFO:SerialBattery:  |- refresh_data: read_fed_data - result: True - runtime: 0.043109s
09:06:43.437600500 INFO:SerialBattery:  |- refresh_data: read_cell_voltage_range_data - result: True - runtime: 0.042444s
09:06:43.438269500 INFO:SerialBattery:  |- refresh_data: write_soc_and_datetime - result: True - runtime: 0.042444s
09:06:43.482233500 INFO:SerialBattery:  |- refresh_data: read_alarm_data - result: True - runtime: 0.042726s
09:06:43.520568500 INFO:SerialBattery:  |- refresh_data: read_temperature_range_data - result: True - runtime: 0.037184s
09:06:43.524914500 INFO:SerialBattery:refresh_data: end - result: True
09:06:43.535851500 INFO:SerialBattery:refresh_data: start
09:06:43.587253500 INFO:SerialBattery:  |- refresh_data: read_soc_data - result: True - runtime: 0.043622s
09:06:43.637371500 INFO:SerialBattery:  |- refresh_data: read_fed_data - result: True - runtime: 0.049653s
09:06:43.686910500 INFO:SerialBattery:  |- refresh_data: read_cell_voltage_range_data - result: True - runtime: 0.048266s
09:06:43.687545500 INFO:SerialBattery:  |- refresh_data: write_soc_and_datetime - result: True - runtime: 0.048266s
09:06:43.845250500 INFO:SerialBattery:  |- refresh_data: read_cells_volts - result: True - runtime: 0.156302s
09:06:43.882949500 INFO:SerialBattery:  |- refresh_data: read_balance_state - result: True - runtime: 0.036556s
09:06:43.884446500 INFO:SerialBattery:refresh_data: end - result: True
09:06:43.933323500 INFO:SerialBattery:refresh_data: start
09:06:43.980605500 INFO:SerialBattery:  |- refresh_data: read_soc_data - result: True - runtime: 0.042081s
09:06:44.023848500 INFO:SerialBattery:  |- refresh_data: read_fed_data - result: True - runtime: 0.041952s
09:06:44.062022500 INFO:SerialBattery:  |- refresh_data: read_cell_voltage_range_data - result: True - runtime: 0.036863s
09:06:44.062691500 INFO:SerialBattery:  |- refresh_data: write_soc_and_datetime - result: True - runtime: 0.036863s
09:06:44.118699500 INFO:SerialBattery:  |- refresh_data: read_alarm_data - result: True - runtime: 0.05256s
09:06:44.162034500 INFO:SerialBattery:  |- refresh_data: read_temperature_range_data - result: True - runtime: 0.043296s
09:06:44.163030500 INFO:SerialBattery:refresh_data: end - result: True
09:06:44.169496500 INFO:SerialBattery:refresh_data: start
09:06:44.230679500 INFO:SerialBattery:  |- refresh_data: read_soc_data - result: True - runtime: 0.04771s
09:06:44.271116500 INFO:SerialBattery:  |- refresh_data: read_fed_data - result: True - runtime: 0.03931s
09:06:44.309505500 INFO:SerialBattery:  |- refresh_data: read_cell_voltage_range_data - result: True - runtime: 0.03701s
09:06:44.310285500 INFO:SerialBattery:  |- refresh_data: write_soc_and_datetime - result: True - runtime: 0.03701s
09:06:44.455116500 INFO:SerialBattery:  |- refresh_data: read_cells_volts - result: True - runtime: 0.143283s
09:06:44.503649500 INFO:SerialBattery:  |- refresh_data: read_balance_state - result: True - runtime: 0.047373s
09:06:44.504496500 INFO:SerialBattery:refresh_data: end - result: True
09:06:44.521650500 INFO:SerialBattery:refresh_data: start
09:06:44.575319500 INFO:SerialBattery:  |- refresh_data: read_soc_data - result: True - runtime: 0.044345s
09:06:44.622636500 INFO:SerialBattery:  |- refresh_data: read_fed_data - result: True - runtime: 0.045684s
09:06:44.661556500 INFO:SerialBattery:  |- refresh_data: read_cell_voltage_range_data - result: True - runtime: 0.037432s
09:06:44.662144500 INFO:SerialBattery:  |- refresh_data: write_soc_and_datetime - result: True - runtime: 0.037432s
09:06:44.713088500 INFO:SerialBattery:  |- refresh_data: read_alarm_data - result: True - runtime: 0.049475s
09:06:44.751067500 INFO:SerialBattery:  |- refresh_data: read_temperature_range_data - result: True - runtime: 0.036952s
09:06:44.751937500 INFO:SerialBattery:refresh_data: end - result: True
09:06:44.758162500 INFO:SerialBattery:refresh_data: start
09:06:44.813872500 INFO:SerialBattery:  |- refresh_data: read_soc_data - result: True - runtime: 0.043003s
tail: /data/log/dbus-serialbattery.ttyUSB4/current has been replaced; following end of new file
09:06:45.291633500 INFO:SerialBattery:  |- refresh_data: read_alarm_data - result: True - runtime: 0.038075s
09:06:45.343153500 INFO:SerialBattery:  |- refresh_data: read_temperature_range_data - result: True - runtime: 0.050357s
09:06:45.343962500 INFO:SerialBattery:refresh_data: end - result: True
09:06:45.356122500 INFO:SerialBattery:refresh_data: start
09:06:45.400509500 INFO:SerialBattery:  |- refresh_data: read_soc_data - result: True - runtime: 0.039539s
09:06:45.444257500 INFO:SerialBattery:  |- refresh_data: read_fed_data - result: True - runtime: 0.04254s
09:06:45.492988500 INFO:SerialBattery:  |- refresh_data: read_cell_voltage_range_data - result: True - runtime: 0.047604s
09:06:45.493694500 INFO:SerialBattery:  |- refresh_data: write_soc_and_datetime - result: True - runtime: 0.047604s
09:06:45.658294500 INFO:SerialBattery:  |- refresh_data: read_cells_volts - result: True - runtime: 0.163361s
09:06:45.700109500 INFO:SerialBattery:  |- refresh_data: read_balance_state - result: True - runtime: 0.0406s
09:06:45.700939500 INFO:SerialBattery:refresh_data: end - result: True
09:06:45.707867500 INFO:SerialBattery:refresh_data: start
09:06:45.759861500 INFO:SerialBattery:  |- refresh_data: read_soc_data - result: True - runtime: 0.042046s
09:06:45.803793500 INFO:SerialBattery:  |- refresh_data: read_fed_data - result: True - runtime: 0.042897s
09:06:45.852427500 INFO:SerialBattery:  |- refresh_data: read_cell_voltage_range_data - result: True - runtime: 0.047473s
09:06:45.852903500 INFO:SerialBattery:  |- refresh_data: write_soc_and_datetime - result: True - runtime: 0.047473s
09:06:45.890714500 INFO:SerialBattery:  |- refresh_data: read_alarm_data - result: True - runtime: 0.036598s
09:06:45.940859500 INFO:SerialBattery:  |- refresh_data: read_temperature_range_data - result: True - runtime: 0.048956s
09:06:45.941868500 INFO:SerialBattery:refresh_data: end - result: True
09:06:45.951293500 INFO:SerialBattery:refresh_data: start
09:06:46.003982500 INFO:SerialBattery:  |- refresh_data: read_soc_data - result: True - runtime: 0.044017s
09:06:46.041493500 INFO:SerialBattery:  |- refresh_data: read_fed_data - result: True - runtime: 0.03665s
09:06:46.080693500 INFO:SerialBattery:  |- refresh_data: read_cell_voltage_range_data - result: True - runtime: 0.037733s
09:06:46.082652500 INFO:SerialBattery:  |- refresh_data: write_soc_and_datetime - result: True - runtime: 0.037733s
09:06:46.235164500 INFO:SerialBattery:  |- refresh_data: read_cells_volts - result: True - runtime: 0.150802s
09:06:46.279016500 INFO:SerialBattery:  |- refresh_data: read_balance_state - result: True - runtime: 0.042093s
09:06:46.280152500 INFO:SerialBattery:refresh_data: end - result: True
09:06:46.304023500 INFO:SerialBattery:refresh_data: start
09:06:46.349395500 INFO:SerialBattery:  |- refresh_data: read_soc_data - result: True - runtime: 0.036808s
09:06:46.393298500 INFO:SerialBattery:  |- refresh_data: read_fed_data - result: True - runtime: 0.042601s
09:06:46.432352500 INFO:SerialBattery:  |- refresh_data: read_cell_voltage_range_data - result: True - runtime: 0.037484s
09:06:46.432884500 INFO:SerialBattery:  |- refresh_data: write_soc_and_datetime - result: True - runtime: 0.037484s
09:06:46.481984500 INFO:SerialBattery:  |- refresh_data: read_alarm_data - result: True - runtime: 0.047798s
09:06:46.524946500 INFO:SerialBattery:  |- refresh_data: read_temperature_range_data - result: True - runtime: 0.041725s
09:06:46.534300500 INFO:SerialBattery:refresh_data: end - result: True
09:06:46.551645500 INFO:SerialBattery:refresh_data: start
09:06:46.602164500 INFO:SerialBattery:  |- refresh_data: read_soc_data - result: True - runtime: 0.04262s
09:06:46.640260500 INFO:SerialBattery:  |- refresh_data: read_fed_data - result: True - runtime: 0.036955s
09:06:46.681557500 INFO:SerialBattery:  |- refresh_data: read_cell_voltage_range_data - result: True - runtime: 0.039125s
09:06:46.681764500 INFO:SerialBattery:  |- refresh_data: write_soc_and_datetime - result: True - runtime: 0.039125s
09:06:46.834622500 INFO:SerialBattery:  |- refresh_data: read_cells_volts - result: True - runtime: 0.151524s
09:06:46.883363500 INFO:SerialBattery:  |- refresh_data: read_balance_state - result: True - runtime: 0.047552s
09:06:46.884413500 INFO:SerialBattery:refresh_data: end - result: True
09:06:46.895879500 INFO:SerialBattery:refresh_data: start
09:06:46.947417500 INFO:SerialBattery:  |- refresh_data: read_soc_data - result: True - runtime: 0.042823s
09:06:46.992791500 INFO:SerialBattery:  |- refresh_data: read_fed_data - result: True - runtime: 0.043765s
09:06:47.031617500 INFO:SerialBattery:  |- refresh_data: read_cell_voltage_range_data - result: True - runtime: 0.03746s
09:06:47.032026500 INFO:SerialBattery:  |- refresh_data: write_soc_and_datetime - result: True - runtime: 0.03746s
09:06:47.081162500 INFO:SerialBattery:  |- refresh_data: read_alarm_data - result: True - runtime: 0.047845s
09:06:47.120246500 INFO:SerialBattery:  |- refresh_data: read_temperature_range_data - result: True - runtime: 0.037948s
09:06:47.123682500 INFO:SerialBattery:refresh_data: end - result: True
09:06:47.133215500 INFO:SerialBattery:refresh_data: start
09:06:47.182473500 INFO:SerialBattery:  |- refresh_data: read_soc_data - result: True - runtime: 0.037491s
09:06:47.232117500 INFO:SerialBattery:  |- refresh_data: read_fed_data - result: True - runtime: 0.047982s
09:06:47.271615500 INFO:SerialBattery:  |- refresh_data: read_cell_voltage_range_data - result: True - runtime: 0.038638s
09:06:47.272127500 INFO:SerialBattery:  |- refresh_data: write_soc_and_datetime - result: True - runtime: 0.038638s
09:06:47.434551500 INFO:SerialBattery:  |- refresh_data: read_cells_volts - result: True - runtime: 0.161022s
09:06:47.483016500 INFO:SerialBattery:  |- refresh_data: read_balance_state - result: True - runtime: 0.047328s
09:06:47.484039500 INFO:SerialBattery:refresh_data: end - result: True
09:06:47.492214500 INFO:SerialBattery:refresh_data: start
09:06:47.554370500 INFO:SerialBattery:  |- refresh_data: read_soc_data - result: True - runtime: 0.054087s
09:06:47.603755500 INFO:SerialBattery:  |- refresh_data: read_fed_data - result: True - runtime: 0.048027s
09:06:47.654169500 INFO:SerialBattery:  |- refresh_data: read_cell_voltage_range_data - result: True - runtime: 0.049334s
09:06:47.654655500 INFO:SerialBattery:  |- refresh_data: write_soc_and_datetime - result: True - runtime: 0.049334s
09:06:47.691813500 INFO:SerialBattery:  |- refresh_data: read_alarm_data - result: True - runtime: 0.035979s
09:06:47.741594500 INFO:SerialBattery:  |- refresh_data: read_temperature_range_data - result: True - runtime: 0.048553s
09:06:47.743829500 INFO:SerialBattery:refresh_data: end - result: True

With that informations there were very few no reply erros, but as soon as I removed the logging data I got a lot of errors. Then I added sleep(0.005) as first command in read_serialport_data() in the daly.py and now nearly all errors are gone. With sleep(0.020) all no reply errors are gone. Even, if I removed the polling steps.

Conclusion: Without the polling steps and the short sleep before opening the serial connection the refresh_data() is now taking about 650 ms. The sleep time can be dependend of the serial adapter and Daly BMS used. It also works with lower values, but I increased it a bit for greater compatibilty.

mr-manuel/venus-os_dbus-serialbattery@a74cd5d

[mr-manuel]

@teefixx could you try this daly.py? There we made some improvements.

mv /data/etc/dbus-serialbattery/bms/daly.py /data/etc/dbus-serialbattery/bms/daly.py.backup
wget -O /data/etc/dbus-serialbattery/bms/daly.py https://raw.githubusercontent.com/mr-manuel/venus-os_dbus-serialbattery/jkbms_ble/etc/dbus-serialbattery/bms/daly.py

[teefixx]

tried it just remotely, the driver does not start with this daly.py

[teefixx]

Will do, but I‘m more or less not at hume until monday...

[transistorgit]

I've the SOC setting done, see merge request...

[teefixx]

great, could we switch "allow charge / discharge" in the BMS the same way?

[transistorgit]

done ;-)