Good afternoon today,
v2.85~5 available for testing; adding a missing fix for ModbusTCP register 777.
In case you haven't seen it yet: last Monday we released v2.80, a release packed with new features. Quickly thereafter came v2.81.
The goal with v2.82 is to be a bug fix release; fixing the known regressions of v2.80, aiming to quickly go to a super stable and reliable version.
In case you don't know what this message is about, then please start with reading this link, which explains the Venus OS beta program.
Change log
One new change:
- Add missing fix for Modbus-TCP register 777; thank you @Elvis .
Changes in v2.82~4, released yesterday:
- Fix missing Modbus-TCP register 777: Solar Charger PV current. More information here.
- Fix issue when having a CAN-bus connected battery, DVCC and another battery monitor on the same battery bank. This is fixed by reverting the related code & functionality to how it was on v2.73. Post with more information.
- Fix issue that, sometimes, greyed out the Enable toggles of analog tank inputs.
- Bluetooth wireless sensors (Ruuvis): immediately use an inserted USB Bluetooth Adapter, rather than requiring a reboot first.
- Make the Wireless bluetooth sensors feature, for the Ruuvis, use all connected bluetooth adapters. With this change, it is possible to connect multiple USB bluetooth adapters. And for example by having one on a slightly long USB cable it will be possible to increase the range. There is a list of tested USB Bluetooth adapters, currently we at Victron are not stocking or shipping any of those. And they were tested either briefly by ourselves, or by someone else - see the list.
Known issues:
- There is possibly/most likely an issue with the bluetooth module in the Cerbo GX, causing it to no longer receive data from the Ruuvi sensors. Until now, best, meaning most reliable, available solution is to insert a USB Bluetooth adapter. There is a list of tested USB Bluetooth adapters on Community. The issue is Cerbo GX internal temperature related: when too high, the Bluetooth fails. Nothing else fails, just the Bluetooth. Thank you @stevomyatt for getting is on the right track (temperature) here.
- There still is an issue with register 777, see discussion below.
What to test?
1. CAN-bus connected battery, with or without BMV or SmartShunt added as well.
For details, see this post.
2. Modbus-TCP
The now added fix for Modbus-TCP is more than just adding the 777 register back how it was. Its a bit long story in detail, but the result is that Modbus-TCP requires good testing. So: if you use it, please to update to this version and confirm in an answer below that it all works well.
That is all for now, some common information below and have a good Sunday,
Matthijs.
How to post an issue?
Preferably all issues are organised as answers to this question. One answer per issue. So first check the existing threads. If you have the same as someone else already reported, welcome to add a comment saying "me too". And preferably some more details. And in case its not listed yet, add a new Answer. Note that Answers and Comments are two different things here on community.
Lastly, please first revert to v2.73, to double check if the issue you're seeing was present there as well. Regressions require a different treatment than other issues and bugs, and one of the first things that needs doing in triaging a report is distinguishing between the two.
Running SetupHelper, GuiMods or other customer code?
Please then first remove that, and see if you still have an issue. Or at a minimum mention that, and then don't be surprised if I ask to take that elsewhere directly with @Kevin Windrem, or remove it first.
