question

mvader (Victron Energy) avatar image
mvader (Victron Energy) asked

Venus OS v2.80~32 available for testing

Good evening!

A new version available for field testing, v2.80~32.

In case you don't know what this message is about, please start with reading this link, which explains the Venus OS beta program.


v2.80 summary

The version we're working on, v2.80, has a few highlights: the new AC Load monitoring, the new DC metering function, and also various improvements to the HTML5 MFD App, including the addition of translations as well as the added support for the Ruuvi Tag wireless temperature sensors.


What to test?

Same as before: the new features I mentioned in the above summary as well basically everything:

There are several major changes in v2.80, which can each make things break in unexpected places. For those interested in the details, the changes I'm referring to here are (a) that the used Python version has been updated from 2.7 to 3, (b) the Open Embedded release was upgraded from Zeus to Dunfell, and we changed to a read-only rootfs. Also, various application level changes that reduce the CPU load per Victron device, useful when connecting many solar chargers for example, were made. That caused some regressions earlier, which are now fixed.

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.


The plan for v2.80

We still need more time to both finish and test all the changes made. And as such I'm not sure yet when v2.80 will become official.


Change log below.


All the best and have a good one!


Matthijs Vader


v2.80~32 change log, comparing to v2.80~29

  • Further complete the support for the Multi RS. In more detail, a page in the UI has been added
  • Change how Shared Voltage Sense, Shared Current Sense and Shared Temperature Sense are transmitted out on VE.Can; note that this still needs further improvements, coming in the next v2.80 update.
  • Inverter RS: Add showing an error - if there is an error
  • Reduce CPU load induced by Fronius, SMA and other PV Inverters.
  • Fix bug where Shared Temperature Sense (STS) did not work between an analog temperature sensor connected directly to a GX Device and VE.Can-connected chargers such as MPPTs. This bug has been in the system since its introduction, approx v2.40, and does not affect any other combinations.
  • Add various data to allow the details in the Generator block on VRM Dashboard. See one of the slides in here and then the orange star.
  • Add transmission to VRM of humidity % as well as barometric pressure of the wireless Ruuvi sensors.


Developers, ModbusTCP, Node-RED, MQTT:

  • Note that, throughout various v2.80 beta versions, we removed the Pv/Current path aka register from our internal databus. Going forward, to use that, you need to calculate it by dividing the power by the voltage.


Various fixes for regressions introduced earlier in v2.80 development:

  • Fix poor wifi performance that either in some or all cases occurred when enabling Bluetooth connection to the wireless temperature sensors. Introduced earlier during v2.80 development
  • Fix bug in NMEA2000-out. The PV array current (Amps) was no longer transmitted. Bug was introduced earlier during v2.80 development.
  • Fix issue in Generator Start/Stop. Bug was introduced earlier in v2.80 development. Thank you @Kevin Windrem and @Elimac for reporting.
  • Fix bug where data flow from VE.Can connected devices could get stuck after a connection issue. Bug introduced earlier during v2.80.



Changes between v2.80~24 and v2.80~29:

  • Support SmartShunt DC Energy meters configured as "DC System". Two things happen when one or more SmartShunts are configured as such: (1) the power shown in the DC system box is the sum of powers reported by all SmartShunts configured as such. Allowing multiple meters is done to accommodate for example a catamaran, then you can measure the DC Systems on Port side and on Starboard side. Use the Custom name setting to give each of the meters configured as DC System their own name. (2) the DC System Current is being compensated for when setting DVCC charge current limits to Multis, Quattros and Solar Chargers. Which in more detail mains that for example when a load of 50A is being measured, and CCL by the battery is 25A, the limit given to the Multis & Solar Chargers is 75A.

    And the notes: (A) instead of a SmartShunt, also a BMV-712 can be used. (B) Setting it to be a DC System is done in the settings of the BMV/SmartShunt itself.

  • VRM Portal Connection: prepare for more details on Generator box on the VRM Dashboard.

  • Reduce CPU load. By making various changes, all relating how the different software components exchange their data, the CPU load is reduced. Note that by how much this is reduced, and if and how this changes the maximum number of connectable devices is not yet known, we still need to measure that in detail.

  • Fix broken status updates during VE.Bus (Multi/Quattro) firmware updates

  • Fix missing "Recharge" text in ESS BatteryLife state field. It said "Uknown" since Venus OS v2.20.

  • Fix Garmin MFD issue that appeared in a certain start-up sequence, this issue most likely existed in the design since the beginning.

  • NMEA2000-out: fix Solar sender DC instance storage to non-volatile memory. This never worked right, until now.

  • Fix support for Multi firmware versions prior to version 153. This was broken in v2.80~2.

  • Some more VE.Bus protocol related stability improvement, mostly affecting quite specific systems or circumstances.

  • Update recognition of Fimer grid-tie PV Inverters: Fimer recently acquired ABB and is now updating the names and recognition strings in the code.


Previous changelogs:


Complete v2.80 change log, compared to v2.73:

(still..) no time for that now, I'll make that later.

Venus OS
2 |3000
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

3 Answers
Kevin Windrem avatar image
Kevin Windrem answered ·

I can confirm performance with the internal WiFi is much improved over v2.80~29 even with Bluetooth sensors enabled.

I had been using a WiFi dongle but think the internal WiFi is much faster now than with the dongle.

Nicely done.

1 comment
2 |3000
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

mvader (Victron Energy) avatar image mvader (Victron Energy) ♦♦ commented ·
thank you! passed along to the developer, and also good to get the confirmation.
0 Likes 0 ·
Kevin Windrem avatar image
Kevin Windrem answered ·

Note to GuiMods users, v5.4 is available to support v2.80~32.

2 comments
2 |3000
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

nebulight avatar image nebulight commented ·
When is Victron going to get you on the payroll and just build this into Venus with toggle options in the GUI ;)
0 Likes 0 ·
Show more comments
Chad Heiser avatar image
Chad Heiser answered ·

An issue was pointed out to me regarding the beta version of Venus OS software. I have the beta version installed on two different systems currently. One is a single Multiplus II, MPPT 150/100, 500 A SmartShunt, Cerbo GX and Touch 50 display. The other system is a dual Quattro, MPPT 150/100, 1000 A SmartShunt, Cerbo GX and Touch 70. In both of my installations, as well as a third installation with a Multiplus II and Cerbo GX (not sure what else as it belongs to someone else), the Input Current Limit when accessing it through VRM was maxed out at 40 amps and could not be set higher.

After this was pointed out to me, I started testing various input methods and was able to change the Input Current Limit to 50 amps via Victron Connect and a VE.Bus Bluetooth Dongle. Once I made the change this way, I was then able to go back into VRM remote portal and change the value to whatever I wanted above 40 amps, but prior to that VRM was limited to 40 amps. After I did my testing, the owner of the third system set his value to less than 40 amps through VRM remote portal and saved it and then went back and was able to set it above 40 amps. Prior to doing that he was not able to get the limit to go above 40 amps.


Here is the topic being discussed on the Victron Powered Camper Facebook Group for further information, https://www.facebook.com/groups/3008836042495631/posts/4801161083263109/?comment_id=4801360256576525&reply_comment_id=4801443876568163&notif_id=1640454848670323&ref=notif&notif_t=group_comment_mention

1 comment
2 |3000
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

Chad Heiser avatar image Chad Heiser commented ·
I reverted to version 2.73 and did not have the same issue. I left the Input Current Limit set at 50 amps and then reinstalled beta version 2.80. When I went to the Input Current Limit, the setting was changed to 40 amps and I could not set it higher through VRM (problem from above duplicated). I set the limit to something lower (30 amps) and saved it. After I did this, I was able to then go in and set it to 50 amps again. This was all through VRM and remote console.
0 Likes 0 ·

Related Resources

Victron Venus OS Open Source intro page

Venus OS GitHub (please do not post to this)