{"id":26423,"date":"2023-05-31T01:19:01","date_gmt":"2023-05-30T23:19:01","guid":{"rendered":"https:\/\/www.victronenergy.com\/blog\/?p=26423"},"modified":"2024-09-16T16:41:33","modified_gmt":"2024-09-16T14:41:33","slug":"venus-os-v3-00-generator-start-stop-improvements-ess-peak-shaving","status":"publish","type":"post","link":"https:\/\/www.victronenergy.com\/blog\/2023\/05\/31\/venus-os-v3-00-generator-start-stop-improvements-ess-peak-shaving\/","title":{"rendered":"Venus OS v3.00 – Generator start\/stop improvements, ESS Peak shaving"},"content":{"rendered":"

Good day!<\/p>\n

Today we are releasing Venus OS v3.00.<\/p>\n

For those not familiar with Venus OS: it is the software running on our Cerbo GX monitoring system<\/a>, as well as its predecessors the Color Control GX<\/a>, Venus GX<\/a>. Also, it is in the GX versions of our MultiPlus-II and EasySolar-II inverter\/chargers.<\/p>\n

This new release has improvements in the following main areas:<\/p>\n

    \n
  1. Several improvements to the GX Generator start\/stop functionality<\/li>\n
  2. Peak shaving, and improved control speed for ESS<\/li>\n
  3. Disable the touch feature on a GX Touch<\/li>\n<\/ol>\n

    Let’s go into the details:<\/p>\n

    Improvements to Generator control<\/h3>\n

    There are several new generator start\/stop related improvements.<\/p>\n

    Firstly, warm-up and cool-down options have been added.\u00a0 This allows you to set a configurable time for the generator to run from the relay control, while the AC input relay is open and the inverter\/charger is not connected to it.\u00a0<\/span><\/p>\n

    \"\"<\/a><\/p>\n

    The warm up and cooldown settings are available in the Generator start\/stop menu of the GX device when a relay is enabled for Generator start\/stop, and the VE.Bus Inverter\/Charger firmware has been updated to 502 or later.<\/p>\n

    \"\"<\/a><\/p>\n

    Secondly, we added an option to stop a back-up generator that is connected to either ACin 1 when the grid returns. Until now, that feature was only available for systems with the generator wired to ACin 2. More recent information on wiring systems that have both a generator as well as a connection to the utility grid is here<\/a>.<\/p>\n

    \"\"..<\/a><\/p>\n

    Note that for both features to be available, it is necessary to trigger the update the firmware of the built-in MK3. Doing that is really simple, see further below for instructions.<\/p>\n

    Peak Shaving for ESS<\/h3>\n

    There is a new Peak shaving option for ESS systems set to Optimised modes.<\/p>\n

    \"\"<\/a><\/p>\n

     <\/p>\n

    Previously once an ESS system had discharged to the minimum state of charge it would no longer assist the loads to shave the peaks.<\/p>\n

    This is now improved: the new peak shaving feature will make the system keep PowerAssisting when the loads exceed the AC input current limit. Thereafter, as soon as the peak is over, it will recharge the battery using power from the grid, while still prioritising solar.<\/p>\n

    Note that there is a 5% hysteresis on the recharge: when for example the Minimum SOC is configured to 50%, it will then start recharging only once (by peak shaving) the battery has dropped to 45%. It will then recharge back to 50% SOC, whereafter it continues its normal ESS operation: wait for solar power to further charge the battery.<\/p>\n

    To enable, go to the Peak Shaving menu in the ESS setting on your GX device and change the setting to ‘Always’.<\/p>\n

    \"\"<\/a><\/p>\n

    Note – this works for the critical loads on the AC output only, not those connected to an energy meter.<\/p>\n

    We also fixed some bugs where PV was not used for loads when scheduled charging to 100% during the daytime, and where an AC PV-inverter on AC-in-2 would not be shown in the ESS overview.\u00a0<\/span><\/p>\n

    Scheduled Charging<\/h3>\n

    Scheduled charging is a feature that allows additional control over charging and discharging your ESS system based around time of use.<\/p>\n

    Previously you could set up a scheduled charging window, and once the battery was charged to the target, it would stop charging, and also disable discharging remaining at that state of charge, waiting until the scheduled charging mode finished before it would begin discharging again.<\/p>\n

    In Venus v3.00 there is a new ‘Self-consumption above limit’ option that allows an ESS system to discharge during a scheduled charging period as long as the SOC remains above the programmed SOC limit.<\/p>\n

    \"\"<\/a><\/p>\n

    This new setting can be useful if a scheduled charge slot with a lower SOC limit setting follows another slot with a higher target.<\/p>\n

    This means you can now choose how much of your battery is allowed to discharge during certain periods of the day. This allows you to balance how much and when you charge from the grid, how much battery backup you maintain, ensure your batteries get a good regular recharge, and have some spare capacity to recharge from solar.<\/p>\n

    More flexibility to optimise for the many different grid tariffs, times and conditions around the world.<\/p>\n

    Disable the touch feature on a GX Touch<\/h3>\n

    There are many situations where you want to have the Cerbo GX screen visible to show what the system is doing, but disable any kind of touch interaction or control. We’ve now added a new feature to disable the touch input.\u00a0<\/span><\/p>\n

    \"\"<\/a><\/p>\n

    This additional control restriction should be considered anywhere the touch screen is accessible to the public or an untrained end-user, such as someone renting a hybrid generator system.<\/p>\n

    This is done by installing a small push button switch, and programming one of the digital inputs. When pressed the switch will make a momentary connection of the programmable digital input, enabling or disabling the touch control.<\/p>\n

    \"\"<\/a><\/p>\n

    More details and information about “Hardening a GX device” is available here<\/a>.<\/p>\n

    Node-RED<\/h3>\n

    We continue to see innovative solutions from system designers who are exploring the potential and control that Node-RED offers them over their Victron equipment. Many solutions that previously depended on Victron engineers, or 3rd party hardware, can now be done completely by their own teams with the Victron equipment they already have today.\u00a0<\/span>Given the success we will continue to improve the platform, to make it easier to get started, and more reliable for the long run.<\/p>\n

    This screenshot shows what the Node-RED editor looks like:<\/p>\n

    \"\"<\/a><\/p>\n

    More details on that example for are in a video shared by ENERP<\/a>.<\/p>\n

    These are the Node-RED related changes in Venus OS 3.00:<\/p>\n

      \n
    1. Change how the Node-RED nodes identify which Victron device they configured for. This now uses the dbus \/DeviceInstance path, instead of the the full service path. To use that, all existing flows will need to be manually migrated. But until you migrate, your flows will remain functional. More details on this specific change here: https:\/\/github.com\/victronenergy\/node-red-contrib-victron\/releases\/tag\/v1.4.25<\/a>.<\/li>\n
    2. A few extra nodes have been added (input-pump, output-pump, output-battery), and several existing nodes got extra paths.<\/li>\n
    3. Added two options to output nodes: (1) rounding of values, and (2) output only on value changes.<\/li>\n
    4. Several importable examples have been added and the documentation has been updated.<\/li>\n<\/ol>\n

      Note that Victron cannot offer support for Node-RED flows. If you think you’ve found a bug, or have a feature request, the correct channel to get in touch is via the Victron Commmunity Modifications space<\/a>.\u00a0<\/span><\/p>\n

      To learn more about Node-RED, see our manual for it<\/a>, as well as our library of documented example flows<\/a>.<\/p>\n

      Bluetooth improvements for Cerbo GX\u00a0<\/span><\/b><\/h4>\n

      There was an unfortunate issue that affected Cerbo GX units with serial number HQ2207 and earlier where the built in Bluetooth was limited by internal temperature. The good news is that as of HQ2208 and later, and all Cerbo-S GX, we’ve added an additional improved Bluetooth radio. This v3.00 firmware release will use that one.<\/p>\n

      Note for Ruuvi temperature sensing, it is still fine to have additional external long range USB bluetooth radios to even further improve coverage. All connected Bluetooth radios will be used for reading Ruuvi data.<\/p>\n

      Other i<\/b>mprovements since v2.90<\/b><\/h4>\n

      The last blog post about a Venus release was version v2.90<\/a>. We<\/span> released a few smaller point release bug fixes so they didn’t need to wait for this full release of v3.00.<\/p>\n

      For more details about these and other smaller changes, please also check the v2.90-2.93 change-log:<\/p>\n