question

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

Venus OS v3.10~38 available for testing

UPDATE 2023-09-09: v3.10~38 is now available, details in the change log below.

UPDATE 2023-09-07: v3.10~37 is now available, details in the change log below.

UPDATE 2023-09-06: v3.10~36 is now available, details in the change log below.


Good evening this Friday!

Per just now, a new pre-release of v3.10 is available, v3.10~34.

Note that we're in the phase of wrapping up, to release v3.10 soon. One thing we did is take the new HTML5 app out, since that is not good enough for prime time yet.


The detailed change log is below, but first more details and screenshots of the v3.10 highlights:

  1. Solar and wind priority for boats, vans, and other systems with a shore power connection.
  2. New ESS "Self consumption from battery" setting
  3. Generator improvements: CoMap integration, a resettable service interval counter and autostart-disabled alarm.


Here are the details for those:


1. Solar and wind priority for boats & vans

The new Solar & wind priority gets to work when plugged into shore. It then ensures that solar & wind power are used to charge the battery, while the shore power is only used to prevent the battery from becoming too deeply discharged.

Its a new installer setting in our range of inverter/chargers, and a new charger mode: Sustain. Here is a screenshot, also note the graphics in the battery icon:

1690869884140.png

For further details, see the Solar and wind priority draft manual.


2. New ESS "Self consumption from battery" setting

This setting allows for ESS to only use battery power for essential loads. This is relevant for ESS systems with (a) a grid meter, (b) quite significant non-essential loads, (c) Feed-in disabled. The setting allows battery banks to be sized to get critical loads through the night, without the battery being discharged into the non-essential loads.

Screenshots of the new setting, first one shows the default, all system loads:

1690870064759.png


And here the other, new, option: only critical loads:

1690870065236.png



3. Next, there are three more improvements related to Generators

  1. adds support for ComAp generator controllers. Integration via ethernet/ModbusTCP; using the ComAP CM Ethernet module.
  2. adds resettable down counting service interval for generators
  3. add an alarm when generator is not in autostart mode for more than 10 minutes. This is to help prevent systems shutting down because during service someone had to enable manual mode; and then forgot to put it back to auto mode. The alarm is optional and can be enabled from generator start/stop settings.


Here is a screenshot on how to enable this on a CoMap generator controller.

1685821985137.png

(click for large)


The data that is being read from the controller is:

  • AC Power, Voltage, Current and Frequency and Energy
  • Engine speed, coolant temperature, Oil Pressure, Load percentage, Operating hours and starter battery voltage.
  • Status (init, stopped, error, preheat, and so forth)
  • Auto-start status (off, manual, auto, test)

We'll later publish a list of ModbusTCP registers.

For the developers amongst you, the driver that reads that data is public; commit here. And we'll be looking to integrate other popular generator controllers as well. In case anyone can help; or has a generator with for example DSE or Deif, then please post some details (which model / modules for example) and perhaps it can be of help. A large part of the work is figuring out which model is the popular one, which is the right protocol to use, and so forth. As you can see in that commit, the actual integration is not that much code.


Then, onto the other two new features, service interval and autostart-is-off-alarm:

Here is how the new service interval is visible in the menu:

1685822170349.png


Here is how to configure and reset the new service interval:

1685822077955.png


Here is how it looks when the interval is exceeded:

1685822143912.png


Still open for this is to show this, for a whole fleet, on VRM.


The new autostart alarm setting:

1685822305012.png


Short explanation when enabling it:

1685822326891.png


Alarm notification:

1685822341197.png


Introduction to Venus OS beta testing & how to join/install

In case you don't know what this message is about, please start with reading this link, which explains the Venus OS beta program. Venus OS is the software running on all our GX devices, such as the Cerbo GX.


How to post an issue?

By posting an answer below. Do please keep all findings organised: one answer issue per issue. So first check the existing threads if your issue has already been seen. And if it does, 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 on this portal.

Lastly, before posting issues, preferably first revert to the latest official release (v2.93), 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 include information about the results/differences in behaviour in your report.


Running, Node-RED, Kevin’s GuiMods or other add-ons?

Then please at least say so in your bug report.

GuiMods and other 3rd party add-ons: don’t report your gui issues here. Do it elsewhere instead.

Changes made by us often cause a compatibility issue with the GuiMods; and these betas report pages are for official firmware only.


Changes v3.10~38

  • gui: further solar and wind priority fixes
    • Fix overview battery icon not reporting the override charge state
    • Fix stop charge button while in override state


Changes v3.10~37

  • gui: fix showing incorrect "Charge to 100%" description when Quattro is connected.
  • VE.Bus products: update the product name list, fixes generic text showing for new models, instead of full name.
  • Dynamic ESS: add mode for when Node-RED is in control.


Changes v3.10~35 and v3.10~36

  • Fix bug causing SmartShunt IP65 not always working on GX device. Thank you @Catta12 for reporting.
  • Update the translations. We already spotted one that is too long and needs amending; can you find more?
  • Last fixes for the Solar and Wind priority feature. More details on that new feature here. This includes fixing systems with Quattros where the GUI would say Generator on the AC-in box even when configured to be Shore or Grid.
  • Improve remote firmware update discovery for EVCS.
  • Ekrano GX: Fix remote firmware updates for VE.Can connected devices. This never worked on an Ekrano.
  • Generator start/stop
    • Add option to set a start and stop delay for the SOC condition. For background, see here.
    • Fix generator detection alarm being triggered during warmup and cooldown.
  • Dynamic ESS
    • don't show "Dynamic ESS" as a state.
    • improve internals to prepare for next version control methods, both using the Node-RED implementation as well as then soon coming mainstream implementation (which consists of VRM + normal Venus OS; no Node-RED needed).
    • Further details on Dynamic ESS here.


Changes v3.10~33 and v3.10~34

  • gui
    • Hide the Dynamic ESS menu, unless already enabled. It can be enabled from VRM side; and Dynamic ESS is in beta - showing a menu is confusing. Issue was introduced earlier during v3.10 development.
    • Fix incorrect displaying of "Charge to 100% - In Progress" when the Prefer Renewable Energy feature is not configured on the Multi. Bug was introduced earlier during v3.10 development.
  • Revert the HTML5 Marine MFD app back to the same version shipped in v3.01.
  • Revert all FlashMQ/Mosquitto related changes: v3.10 will ship with Mosquitto. FlashMQ development will continue in the next cycle, v3.20; expected in week of Sept 11th.
  • Generator management
    • Send the service warning to VRM, allows showing a warning on VRM when a service is due.
    • Transmit the service counter to VRM.
    • Log the PE-N (earth to neutral voltage) to VRM for meters that support it, which currently is only the upcoming new Victron meter.
  • Modbus-TCP: Add 32-bit registers for power values, for grid meter and pv-inverter services. Thanks to Simon H.


Venus OS Large

  • signalk-venus-plugin 1.30.2 -> 1.32.0
  • Better manage versions of nodejs dependencies being installed (fix npm-shrinkwrap not working).


Changes v3.10~31 and v3.10~32

ModbusTCP:

  1. Make the ESS max discharge current a signed integer
    • This is so that -1 can be set, which is needed to disable the limit
  2. Add MppOperationMode registers Individual Trackers on RS devices
    • adds registers 3731 t/m 3734 for MPPT RS
    • adds registers 3169 t/m 3172 for Inverter RS
    • adds registers 4605 t/m 4608 for Multi RS
  3. Add registers for reading- and resetting generator service interval: Registers 3510 (32-bit) and 3512


Other:


  1. Dynamic ESS beta: Correct a situation in DynamicESS where it locked out charging/buying under the DESS MinSoc.
  2. Further improve vrmlogger stability in case of storage issues, to enhance remote diagnostic options.


Venus OS Large:

  1. node-red-contrib-victron v1.5.0
    • Adds a custom input and output node. This is an extremely powerful new tool in the Node-RED tool box, which I’m sure many will enjoy. Here is the summary, also in the documentation:
    • The input node allow to read from and the output node allows to write to all found dbus services and paths. This obviously comes with a risk, as not all services and paths are supposed to be written to. So only use the custom output node if you have read the documentation and know what you are doing. Also note that used services and paths might change, so there is no guarantee that a node will remain functional after a Venus firmware update.
    • So, enjoy, but be careful!


Changes v3.10~28, 29 and ~30

  • Fix connection issue with ABB meters
  • Further developments on the new MFD/HTML5 app.
    • Add 'time to go', voltage and amps to batteries
    • Make the Batteries Overview component bigger
    • Show tanks with missing remaining and total capacity
    • Add support for all tank measurement units
    • UI improvements: change icons and make them bigger, increase text size and line height based on screen size, decrease box padding on smaller screens.
    • Fix battery names not showing on Garmin in certain splits
    • Fix missing spacing on Furuno due to unsupported CSS properties
    • General layout and spacing improvements
    • Change the breakpoints for box components.
    • Add padding for phases.
    • Remove hidden overflowed text in Boxes.

  • Fix issue causing GX Touch 50 showing the wrong resolution in case the GX device can't read the resolution data from the display. Note that this only fixes it for the GX Touch 50, not GX touch 70. What it does now is use GX touch 50 resolution by default, rather than some much larger resolution. In case you have such issue, remove/re-insert the HDMI plug a few times, that is known to solve it. And otherwise, RMA.
  • Improve vrmlogger fallback in case storage is corrupt.
  • DVCC / Managed batteries: add per module diagnostics, so that technicians and support personall can more easily identify, especially remotely, which battery module has an issue. There are currently no battery makers yet that support this.
  • Improvements for EM300 and EM500 meters in case using them for single phase systems, with their main measurement on L1, + piggybacking an inverter on L2.


Changes v3.10~26 and ~27

  • Developer only: changes to mqtt, introducing heartbeat topic. Further details will be added to the mqtt issue, and see meta-victronenergy as well as dbus-flashmq commitlog


Changes v3.10~24 and ~25

  • Internal changes


Changes v3.10~23

  • Fix bug where sometimes, consumption from a Multi-RS is not correctly logged to VRM
  • Add support for upcoming Victron Energy Meter (VM-3P75CT)
  • Few Modbus-TCP additions:
    • Add 32-bit registers for ESS/Hub4 setpoints. This is for systems larger than 32kW, using external control. The existing registers were only 16-bit.
    • Add registers for PreferRenewableEnergy and Generator selection. This allows using modbus-tcp to force a charge cycle on a system with Prefer Renewable Energy enabled. Indicating that a generator is running, or reading the state of generator selection has been added as well.


Venus OS Large:

  • Update SignalK server from signalk-server v1.46.2 to v1.46.3
  • Update signalk-venus-plugin from v1.29 to v1.30.2


Changes v3.10~22

  • Finish work for the new "Solar and wind priority" feature, for boats, vans, campers and other systesm with a shore-power connection. More details on that feature here.
  • Add new ESS setting that allows for ESS to only use battery power for essential loads. This is relevant for ESS systems with (a) a grid meter, (b) quite significant non-essential loads, (c) Feed-in disabled. The setting allows battery banks to be sized to get critical loads through the night, without the battery being discharged into the non-essential loads. Thank you @Warwick Bruce Chapman for your help in that!
  • Prepare for Dynamic ESS in VRM, the next step that is coming after our Node-RED implementation of Dynamic ESS.


Changes v3.10~21

  • fix bug in digital inputs, related to recent generator changes.


Venus OS large:

  • signalk-server: fix issue that caused the app overview page on Navico MFDs be slowish every 30 orso seconds.


Changes v3.10~18 -> v3.10~20

  • Stability improvements related to recent digital inputs change icm generator/transferswitch status
  • Internal changes


Changes v3.10~17 -> v3.10~18

Various improvements to the new HTML5 Marine MFD App:

  • Update the keep-alive mechanism to include missing data
  • Add Amps to battery overview component
  • Change theme settings menu UI&UX
  • Fix Remote Console control buttons
  • Fix "Request denied for security" issue


Changes v3.10~16 -> v3.10~17

  • Add new solar and wind priority feature for boats, motorhomes, trailers, service vans and other systems that (a) hook up to shore power regularly, (b) have solar or wind or other renewables, and (c) have a Multi or Quattro. More on this asap.
  • Add “stopping” state to the generator. Its now first running, then, if enabled, cooling down as long as configured in GX, then 15 seconds stopping to accomodate generators that take a while to stop, and only after those seconds the inverter/charger will reconnect to mains; if available. Fixes issues with generators that take a while to stop in combination with the recently added cooling down option.
  • Digital inputs: when configured to measure generator- (or perhaps more precise, external transfer switch- ) state, pass that info over to the Multi. Used for new solar in wind priority option when used on systems with shore, generator, external transferswitch and Multi; rather than Quattro.


Changes v3.10~12 -> v3.10~16

  • Fix issue in CAN-Bus timing for Ekranos, as well as RaspberryPis icm FD HaTs based on the MCP2518FD chipset.
  • Add support for Quattro-II 12/3000/120-2x50 2x120V
  • Add support for 12V Pylon batteries


Venus OS Large:

  • node-red-contrib-victron v1.4.33

    • When 'only changes' is checked make sure the initial is reported.
    • Updated documentation.
    • Support for reading from and writing to ESS schedules.
    • New examples: generator, load shedding and sum power inputs.
    • Don't show rounding on output node.
    • Minor fixes in the services file.


Changes v3.10~11 -> v3.10~12

  • Marine MFD HTML5 App: improve load speed on the MFD as well as reduce CPU load on the GX device induced by opening that app, by changing the underlying data connection. Previously this used Mosquitto MQTT broker (and a python script), now this uses a new broker called FlashMQ (and a Cpp plugin). Its mainly an (enormous) performance improvement. For comparison, on a system having 1500 data points, in the old solution this took 3 seconds and 2900 TCP packets to transmit. In the new solution this is down to 10ms and 179 TCP packets. Tech details in next bullet point:
  • Local MQTT websockets connection: use FlashMQ + dbus-flashmq instead of Mosquitto + dbus-mqtt, see above for details. Details:
    • FlashMQ and Mosquitto are now running side by side.
    • Local websocket requests, ie Marine HTML5 app, are served by FlashMQ + dbus-flashmq. All other requests, ie local MQTT requests as well as all that comes from VRM, still goes over Mosquitto + dbus-mqtt + mqtt-rpc. Changing that is the next stel.
    • Further details in this github issue. Though please don't clutter that issue with all sorts of requests, doing so triggers mails to many developers, and I'd like to keep focus / efficiency.


Changes v3.10~9 -> v3.10~11

  • vrm real time mode / mqtt: fix bug where a network issue could cause the data connection to VRM be lost, and real time display to not work properly.
  • Modbus-TCP: fix Multi/Quattro state register reporting "External control", while it should not.
  • Renewed HTML5/MFD app:
    • The back button has been moved to the footer making it reachable on Simrad devices.
    • The pagination buttons are now in the center of the footer.
    • Sensors in the Environment tab are now identifiable by the custom name of the sensor or device.
    • Implement data unavailable state for tanks.
    • Increase button touch area.
    • Fix tanks not being displayed correctly.
    • Fix Inverter control.
    • More contrast on the settings page.
  • GUI
    • Update translations
    • Add support for new Quattro-II 2x120V model
  • Various internal changes to prepare for the full featured version of Dynamic ESS, that works with Solar irradiance forecasts and dynamic tariffs as we have in the Netherlands. Proof of concept here.
  • raspberrypi: support the RS485 on the Waveshare RS485 CAN HAT (B). Thank you herrfrei!


Changes v3.10~8 -> v3.10~9

  • Add support for Pylontech Pelio-L model, including auto detect and configuration. (DVCC on, SVS off)
  • Fix bug in remote firmware updates for systems of three units and more. Bug was introduced earlier in v3.10 beta series.
  • Complete ModbusTCP mapping list for unit ids above 255. From now on it will not longer be required to get into difficulties when having a VE.Direct-connected or other type of device that has a VRM Instance above 255.


Changes v3.10~7 -> v3.10~8

  • GUI: Fix energy meter showing only a blank page. This was missing in ~7.


Changes v3.10~2 -> v3.10~7

General:

  • Allow temperature sensors to measure down to -40 °C, was -20 °C.

Under water / developer / Venus OS Large:

  • Add wifi for raspberrypi zero2w and rpi4. Thank you @Bathnm for your work on this!
  • Remote VE.Bus firmware updates: changes to accommodate new models.
  • NodeJS: update from v14.17.6 to v18.16.0. This brings us on the latest version of an LTS branch: all good for some time to come. Thank you @Bathnm for your work on this!
  • Various updates to system packages, including security issues.
  • MQTT: pre-install, but not activate, a new broker: FlashMQ. We're replacing Mosquitto, plus our dbus-mqtt service, by FlashMQ + dbus-flashmq. Further details are here.


Changes v3.00 -> v3.10~2

  • New html5/Marine MFD app. First time we’re beta testing this new UI. Its a complete redesign (totally new look including larger font size, adds tank levels, adds temperature and humidity, and more improvements) looking forward to hear what everyone thinks of it. Some things still need fixing:
    • Temperature, Humidity and Pressure sensors are not shown using their name.
    • On Simrad, the tank levels are not all aligned on the left side
    • On smaller split views, the section title, graphs and values are very squeezed together
    • On Raymarine the component in the top left overlaps the home button
    • Scroll behavior is different when component is horizontally aligned (pagination vs scroll to see more tanks)
    • Locking controls not clickable in horizontal split
    • When more than 2 batteries, battery component overflows. Not sure if this is a bug or a feature
    • Changing the units to Fahrenheit in remote console doesn’t change them in html5
  • Support for ComAp generator controller, details above
  • Adds resettable down counting service interval for generators
  • Add option to get an alarm when generator is not in autostart mode for more than 10 minutes
  • Fix VRM Portal connection for a small batch of EasySolar-II GXes (double VRM Portal ID)
  • Add Inverter and Multi RS DC Power path; fixes an issue with the EV Charger.

Developers:

  • Change how venus-data files are handled:
    • pass extraction result as argument to the post-hook ('success' or 'extraction-failed'), so it can cleanup in case of failure and/or stop continuing.
    • look for venus-data-*.suffix as well, so the file name can be changed to describe what it does. Multiple files can be present now.


Previous posts

Venus OS
6 comments
2 |3000

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 ·
Hi all, per just now, v3.10~36 is available. Todo lists are getting empty here, except for further testing and some translation corrections: fingers crossed for a release soon - best case already next week.
1 Like 1 ·
mvader (Victron Energy) avatar image mvader (Victron Energy) ♦♦ commented ·
Hi all, thank you for all feedback as usual. Super helpful. Per just now, v3.10~37 is now available for testing. Details above
1 Like 1 ·
mvader (Victron Energy) avatar image mvader (Victron Energy) ♦♦ commented ·
Hi all, v3.10~38 released just now. It contains a last few solar and wind priority related fixes.


Any feedback is welcome, including that all display and texts around that feature are as you'd expect them.

0 Likes 0 ·
cleaver avatar image cleaver commented ·
I had a generator failure and had to replace. And when I tried to reset the total generator hours, it doesn't. It changes in menu for run/service menu. But doesnt update on the GUI (generator screen).

Not sure if everyone would have this problem. Or even notice, the service time settings are working correctly.

0 Likes 0 ·
Kevin Windrem avatar image Kevin Windrem cleaver commented ·

I can confirm this. The settings menu sets

/AccumulatedTotalOffset

It does NOT set the actual total time:

/AccumulatedTotal

The settings menu displays the DIFFERENCE between those two parameters while the Generator Overview displays only /AccumulatedTotal.

BTW, my tests were with v3.10, not a beta version.

In v3.01, the settings menu resets /AccumulatedTotal and there is no /AccumulatedTotalOffset.

It seems to me the way it was before is more correct. If generators that communicate run time to the GX device, maybe the menu should not allow resetting the accumulated time. The generator running time indicator should match what the GX device shows. It's probably best to limit setting the total accumulated time to installer permissions.

0 Likes 0 ·
mvader (Victron Energy) avatar image mvader (Victron Energy) ♦♦ Kevin Windrem commented ·
Hi both, thank you for the report. Fixed per v3.20~3, will be available shortly.
0 Likes 0 ·
16 Answers
iand avatar image
iand answered ·

For the "sustain" mode for boats/RVs with LFP batteries (like mine!), having the batteries charged to 100% SoC after 7 days is not a good idea for longer-term mooring/storage since this will degrade battery life -- typically around 50% SoC is recommended for this. Can an option be added to enable this?

6 comments
2 |3000

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

ojack avatar image ojack commented ·

It would also be interesting for ESS to be able to set a max. SoC if you don't need the full capacity of the battery in summer.

0 Likes 0 ·
iand avatar image iand ojack commented ·
Unless you want the solar to keep the battery close to maximum SoC to minimise use of any shoreline/generator power...

What's really needed are two modes, one for when the boat is cruising (use as much solar as possible to top batteries up to (for example) 90% SoC, and one for when it's moored to keep SoC around 50%.
Additionally when cruising any excess solar when the batteries are charged can be used to trigger an immersion heater for hot water.
And when moored and plugged into shoreline -- when the inverter will normally be off to save the zero-load power (quite high for a Quattro 48/10000), if the SoC drops to a minimum (e.g. 10%) in winter (too little solar) the Quattro should be switched into charger mode to top the batteries back up.
All possible in theory, but needs support from the OS... :-)


0 Likes 0 ·
mvader (Victron Energy) avatar image mvader (Victron Energy) ♦♦ iand commented ·
Hi! keeping a LiFePO4 based battery around 50% is practically impossible due to the flat voltage curve. What is possible is to keep it anywhere between say 20 and 80% SOC.


And I'd have to study the science on this again, but as far as I remember without looking it up is that LiFePO4 is OK as long as you don't keep the voltage up all the time. It is the voltage that matters; not the SOC per se. But - I can be wrong.

Our charge profiles do lower the voltage. They go to float and then storage. And if the by us recommended voltages for that are not low enough to your preference, then they can be lowered.

Perhaps some day we'll make further improvements on this, but its not something for now - we need to finish the ongoing projects I'm afraid.

1 Like 1 ·
iand avatar image iand mvader (Victron Energy) ♦♦ commented ·
Maybe I should have been clearer -- "50%" is an ideal as you say, actually any midrange SoC is fine. But when using solar to keep the batteries topped up (priority over shoreline) there are still two cases, one when you want to keep them full (because the boat/RV is occupied and you want to make use of solar as much as possible instead of shoreline), and one when you want to float them for long periods when the boat/RV is unoccupied.


The documentation for the solar priority mode suggested that after a week it default to the "keep them full" mode, which is not what is needed -- or have I misread this?


1 Like 1 ·
Show more comments
hjohnson avatar image hjohnson iand commented ·

On my boat, when along side, I tend to use the DVCC override to let my system voltage drop down to 13.3 or 13.4v, which puts the voltage into the flat part of the charge curve for LiFePO4. This approximately translates to a SoC of around 60% (13.3v) or 75% (13.4v). Then, the night before I'mg oing to take the boat out, I'll remote in via VRM and remove the override, letting it go back up to 100%.

For reference, I'm running a DIY LFP battery using a REC ABMS, connected to my Cerbo via CANBUS.

0 Likes 0 ·
Juan Fco Guerrero avatar image
Juan Fco Guerrero answered ·

Have you found an issue with Fronius Gen24 Primo inverters that shows as Tauro and are unable to be set in one phase being unable to use them in one phase system? I've tried to reboot inverters, GX device but after attempting everything had to swap back to 2.94. Thanks in advance!

2 comments
2 |3000

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 ·
hi, we'll look into this - thanks!
1 Like 1 ·
Juan Fco Guerrero avatar image Juan Fco Guerrero mvader (Victron Energy) ♦♦ commented ·

Hello!! Any updates?? TIA

0 Likes 0 ·
towatai avatar image
towatai answered ·

Hey Guys, i am missing the flashmq-folder in this Version! The Large-Image is installed and runs... connections to flashmq via port 1884 are broken too. mosquitto via port 1883 works as it should be.

1693925986943.png


Back to ~32 and the flashmq-folder is back and works.


1693925986943.png (114.3 KiB)
2 comments
2 |3000

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 ·
Hi @towatai , yes my apologies: I forgot to put that in the change log.


Per v3.10~33, we reverted all changes related to FlashMQ, and Mosquitto is back in place.

We'll resume the FlashMQ work per v3.20.

Added it to the change log now - thanks!

3 Likes 3 ·
matthiasu avatar image matthiasu mvader (Victron Energy) ♦♦ commented ·
Can you tell us why? Too many bugs in FlashMQ, or is there a deeper problem?
0 Likes 0 ·
elko avatar image
elko answered ·

Hello,

where and how can I activate Dynamic ESS in VRM?


1 comment
2 |3000

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

ojack avatar image ojack commented ·

As I understand it, Dynamic ESS is just beta and there is no integration with VRM yet.

Here you can find Dynamic ESS beta https://github.com/victronenergy/dynamic-ess

0 Likes 0 ·
nesswill avatar image
nesswill answered ·

Not that this is a big deal, but this issue is back again... running Venus OS v3.10~34. A reboot of the CERBO GX sometimes fixes the issue but not this time.

Dave.

After the latest update to Venus OS v3.10~20 one of my Inverters RS 48/6000 (two running in parallel) has lost the custom name, see below. Was there in the previous version OS v3.10~18.

rs-1.jpg

and the other is fine?

rs-2.jpg

3 comments
2 |3000

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 ·
Hi, we'll look into that thank you!
1 Like 1 ·
nesswill avatar image nesswill mvader (Victron Energy) ♦♦ commented ·
Thank you very much it seems to be fixed now.

Dave.

0 Likes 0 ·
mvader (Victron Energy) avatar image mvader (Victron Energy) ♦♦ nesswill commented ·
Hi Dave, good that it worked this time, but note that it isn't fixed. We have it on the list for later, most likely v3.20.
2 Likes 2 ·
l81ker avatar image
l81ker answered ·

Hi all.

I loaded 10~32 on Sept 1st, and since then I have some battery monitor alarms appearing but without due cause. The alarms last 2s then clear.

I'm aware there's a lot of sun related (CME's) going on so these may be the cause.

I have MP2 5000-70, 4x Pylontech 5000 and solar. I do use GuiMods and also RuuviTags.


Today I installed 10~36 so if the alarms continue to show up, I'll roll back to pre-10~32 and update this report. If they don't show up anymore in the next 7 days, I'll report back.

See screenshots. Anyone is welcome to check for themselves in the advanced tab.

https://vrm.victronenergy.com/installation/201760/share/a974e841


1000024792.jpg




1000024552.jpg

1000024555.jpg

1000024559.jpg



1000024792.jpg (413.9 KiB)
1000024555.jpg (170.9 KiB)
1000024552.jpg (196.7 KiB)
1000024559.jpg (174.6 KiB)
2 comments
2 |3000

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 ·
Hi @l81ker , we’ve not made any changes to this recently.


I recommend to start with checking the Pylontech battery.

0 Likes 0 ·
l81ker avatar image l81ker mvader (Victron Energy) ♦♦ commented ·
Thanks, I later found another thread with a similar subject, it appears that there is a newer software for Pylontech batteries. I will check with my supplier for guidance, and keep you updated.


No other issues.

0 Likes 0 ·
Kevin Windrem avatar image
Kevin Windrem answered ·

This may still be work in progress but ...

With the changes in v3.10~36, the status and instructions for Charge battery to 100% is no longer recognizing AC input set to generator, and also not recognizing the generator digital input.

/Ac/Control/RemoteGeneratorSelected is still being set by the generator digital input but not affecting the messaging in the Charge battery ... dialog nor the battery icon in the flow overview.

This is WITHOUT GuiMods and ExtTransferSwitch installed.

Shouldn't all logic be based on com.victronenergy.system /Ac/ActiveIn/Source ?

3 comments
2 |3000

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 ·
Hi Kevin, v3.10~37 was released just now, does that fix this for you? We've made a change that is related. (but in all honesty, I'm not involved in the details there at the moment).


1 Like 1 ·
Kevin Windrem avatar image Kevin Windrem mvader (Victron Energy) ♦♦ commented ·

I did some work on GuiMods in the battery tile for renewable energy. Thought something like it might be of interest to the stock GUI.

I've combined the solar/wind icon with the orange override icon. The generator override is based on AC input source. The grid override is based on prefer renewable energy being off.

Prefer renewable energy on, AC is grid

screenshot-2023-09-07-at-50835-pm.png


Prefer renewable energy is off, AC is grid

screenshot-2023-09-07-at-51009-pm.png


AC is generator (prefer renewable energy doesn't matter)

screenshot-2023-09-07-at-50908-pm.png


Of course, if the VE.Bus config does not have prefer renewable energy on, this space is blank.

The solar/wind icon is white in this screen shot because I'm in dark mode and the dark icon was nearly invisible. The stock dark icon is used in light mode.

I did not tweak the grid and generator icons. They are a bit hard to see but that's the way they were in the stock battery tile also.

1 Like 1 ·
Kevin Windrem avatar image Kevin Windrem mvader (Victron Energy) ♦♦ commented ·

No I do not see a change in v3.10~37.

Maybe I was wrong about the instructions changing based on the generator is running digital input (indirectly through /Ac/Control/RemoteGeneratorSelected.

For now, disregard.


0 Likes 0 ·
derrick thomas avatar image
derrick thomas answered ·

I updated from 3.10~32 to 3.10~36 and node red would not work. I disabled node red in the menu, then reboot the cerbo, then re-enabled node red in the menu...no node red, so I reboot the cerbo again, still no node red. I rolled back to 3.10~32 and node red reappeared. Is anyone else experience this issue? Or should I just try and install again?

I am running guimods and exttransferswitch but I wouldn't think there would be anything that would conflict with node red.

I tried accessing node red locally as well as thru vrm with no success.

4 comments
2 |3000

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 ·
Hi @derrick thomas that is strange; I can login and have a brief look if you want. You'll have to enable the Remote Support setting for that. Pls then put it in that situation. (update to v3.10~36 again).
0 Likes 0 ·
derrick thomas avatar image derrick thomas mvader (Victron Energy) ♦♦ commented ·
@mvader (Victron Energy) I updated to ~37 and node red is working. I guess no need to worry about ~36 anymore. Thanks!
0 Likes 0 ·
mvader (Victron Energy) avatar image mvader (Victron Energy) ♦♦ derrick thomas commented ·

Ok. Really strange though, since nothing was changed to Node-RED in ~37. And not in any other recent versions either.

0 Likes 0 ·
derrick thomas avatar image derrick thomas mvader (Victron Energy) ♦♦ commented ·
@mvader (Victron Energy) I agree it is strange. I suppose it's completely possible that something just got borked during the update. This happened once several months ago but just like this time, I reverted back to a previous version and all was well.
0 Likes 0 ·
ppr avatar image
ppr answered ·

Hi @mvader (Victron Energy)
Any idea when HTML5 is a subject again? At least for me a big downside that this got kicked.

1 comment
2 |3000

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 ·
Hi, yes as soon as we release v3.10 officially - hopefully already next week.
1 Like 1 ·
pb3 avatar image
pb3 answered ·

I have noticed with recent past versions and and have just confirmed using v3.10~36 that there are issues with the rate of message reception from the victron nodes.

I am finding that the '5 second' transmission rate does not work, for example I count messages received for gps speed and see a continuous stream rather than one every 5 seconds (this did work sometime back).

Another 'related' issue is with multiplus switch position, here again the 5 second rule doesn't work, but further 'on change' doesn't either. Again I see multiple messages coming in even when there is no actual switch change (and the payload is unchanged from the previous)!

The result of this issue is heavily loading my dashboard.

1 comment
2 |3000

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

So far I haven't seen this problem before. Can you file a bug report here? https://github.com/victronenergy/node-red-contrib-victron/issues

0 Likes 0 ·
kelzamedic avatar image
kelzamedic answered ·

v3.10-38 VRM portal showing multiplus to 12v system as "Unknown" with solar and wind priority enabled. This was "sustain" prior to one of the last 2 beta updates.screenshot-2023-09-09-133921.jpg


2 comments
2 |3000

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 - we’ll look a lt that.
0 Likes 0 ·
kelzamedic avatar image kelzamedic mvader (Victron Energy) ♦♦ commented ·
Fixed!


Thx for continuing to provide such a great product!

1 Like 1 ·
Kevin Windrem avatar image
Kevin Windrem answered ·

DISREGARD. OK AS-IS

Not sure what was wrong. Refreshed the SD card and everything works fine.

Raspberry PI no longer boots if a CANbus hat is enabled.

u-boot is failing with:

libfdt fdt_check_header(): FDT_ERR_BADMAGIC

Not sure when this crept in but checked v3.01 and it's OK so somewhere during the v3.10 beta.

This has to do with the naming of mcp2515-can0 and mcp2515-can1.

At some point the extension of these files was changed from .dtb to dtbo

It now appears that the extension needs to be .dtb again.

1 comment
2 |3000

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

Rob Duthie avatar image Rob Duthie commented ·
Hi

Just uploaded ver 3.10.38 and canbus is ok now ver 3.10.37 can bus was missing.

Regards

Rob D

NZ

0 Likes 0 ·
Mark avatar image
Mark answered ·

img-0520.pngUpdated to 3.10~38 and serial numbers are unavailable!



img-0520.png (184.9 KiB)
2 |3000

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

wirehead avatar image
wirehead answered ·

Potential Bug:

In installations with EM24/EM540/EM530 RS485 Modbus RTU the value of the grid current in com.victronenrgy.grid is signed. The sign depends on the direction of the activ power value for the respectiv phase. This behavior doesn't exist in installations with EM24 ETH. The sign of the phase current with EM24 ETH installation is allways positiv.

Is the behavior with modbus RTU meters intensional?

Technicaly the scalar value of the current reading from the energymeter is unsigned.

1 comment
2 |3000

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 ·
Hi @wirehead yes, we add a sign to the currents. I'm aware that it is technically unsigned, but we still prefer to include direction somehow.


To conclude: sounds like no-one ever noticed the missing sign for the EM24 ETH; we'll add that.

0 Likes 0 ·
wilm avatar image
wilm answered ·

Potential bug:

Node Red looses installed Palletes, eg. Dashbaord, InfluxDB, etc.
Reinstalling is impossible and ends with an error, despite the palettes show up after a reboot

13 comments
2 |3000

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 ·
Hi @Wilm , that is strange - I can’t remember having seen such issue elsewhere.


Is it ok if we login to see the issue? Can you enable Remote Support for that?


Is the system your MultiPlus-II GX?


Any thing in particular that can have happened? Have installed or modified anything other than Venus OS Large and Node-RED Pallettes? i’m asking since I noticed that the root partition seems to be full.


And extra pallettes are installed on a different partition, the data partition.

0 Likes 0 ·
wilm avatar image wilm mvader (Victron Energy) ♦♦ commented ·
Hi @mvader (Victron Energy)

Remote-acces is granted.
Only the script for open-DTU is installed in the system to see the micro-inverter. Some palletes are installed too, but you can see yourself.

Have fun with the system and don't burn it ;)


0 Likes 0 ·
mvader (Victron Energy) avatar image mvader (Victron Energy) ♦♦ wilm commented ·
Hi, thanks. We had a brief look, and indeed the rootfs is full which is not good; and must be the result of something you did. Did you use our resize2fs command? You should / I recommend it.


We’re going ahead the the Venus OS v3.10 release now - in the coming minutes it will be live.


And you’ll have to do more digging yourself I’m afraid.

I recommend to login, check the logs of node-red. Which can be done with this command:


cat /data/logs/node-red/* | tai64nlocal

Or some very similar one.


Lastly: please make a new post with all answers; this is outside of the scope of Venus OS beta testing

Thanks and succes!

1 Like 1 ·
wilm avatar image wilm mvader (Victron Energy) ♦♦ commented ·
Please drop me an email how to resize the root. resize2fs is uncommon to me. Thanks in advance
0 Likes 0 ·
raphael avatar image raphael mvader (Victron Energy) ♦♦ commented ·

FIXED: Update the MultiPlus-II to MK3!
Than they show up in Venus OS v3.10

Hi, I discoverd a bug in the VRM for some installations of mine for Venus OS v3.10

When you want to update the firmware of your MulitPlus-II, they don't show up in the VRM anymore.

Venus OS v3.10:
screenshot-2023-09-13-085600.png

Venus OS v3.01:
screenshot-2023-09-13-090332.png


0 Likes 0 ·
mvader (Victron Energy) avatar image mvader (Victron Energy) ♦♦ raphael commented ·
Hi @Raphael , thank you for the report - looks like you found a bug (regression) in v3.10.


Remote updating a multi should work both with and without first updating the MK3.


We’re looking into it.

1 Like 1 ·
ojack avatar image ojack raphael commented ·
Maybe this could be a new feature.

Many users have killed their assistants using this simple possibility to start an update for the multis.


0 Likes 0 ·
raphael avatar image raphael ojack commented ·

Update: It has nothing to do with Modifications! It is fixed by updating the MP-II to MK3.

0 Likes 0 ·
ojack avatar image ojack raphael commented ·
I have the entry to update my multiplus

3Phases MP3000 at v502, CerboGX at VRM 3.10, GuiMods 8.05, SetupHelper 5.5


1 Like 1 ·
raphael avatar image raphael ojack commented ·

Interesting...I just updated to GuiMods 8.05, SetupHelper 5.5 now. But still the same behavior with v3.10.

This is the device list:
Maybe I have too many temp. sensors...

screenshot-2023-09-13-094528.png

0 Likes 0 ·
Kevin Windrem avatar image Kevin Windrem raphael commented ·
Please, if you are running ANY enhancements to Venus OS, uninstall them before posting in the beta threads.


If you do find an issue that is present only with the enhancement installed, it's best to contact the author of the enhancement even if you post here. We may miss the post. For GuiMods, SetupHelper and my other mods, post an issue the the appropriate GitHub issue section. Thank you.

1 Like 1 ·
raphael avatar image raphael Kevin Windrem commented ·

Thank you! The Issue was not related to the GuiMods or the SetupHelper. I just wanted to mention, that is was installed. But the same behaviour occured in a normal installation. But I could fix it by updating the MuliPlus-II to the newes MK3.
On both systems, the one with and the one without any Modifications...no problems anymore.

0 Likes 0 ·
raphael avatar image raphael ojack commented ·

I could fix it:

The MP-II where not updated to MK3 jet.

screenshot-2023-09-13-103028.png

Now it woks just fine!

0 Likes 0 ·
kladz avatar image
kladz answered ·
  1. New ESS "Self consumption from battery" setting

Please add a time slot for this function.

2 |3000

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

Related Resources