Venus OS v3.00 released officially

Question

replit

This site is now in read-only archive mode. Please move all discussion, and create a new account at the new Victron Community site.

question

mvader (Victron Energy) asked Apr 28, '23

Venus OS v3.00 released officially

UPDATE 2023-05-30: v3.00 is now released officially.

UPDATE 2023-05-12: v3.00~42 is now available for testing.

UPDATE 2023-05-11: v3.00~41 is now available for testing.

UPDATE 2023-05-06: v3.00~39 is now available for testing.

Good day!

A new version available, and a fresh new thread to put comments in.

Per just now, v3.00~37 is available for testing. It adds some welcome features around generator control: auto stop when grid returns for systems where the generator is connected to AC-in 1, as well as configurable warm-up and cool-down delays.

The status of v3.00 is the same: we're finishing up, ie. testing for stability, making sure all is as it should be; and making good progress with that. The generator start/stop improvements is the last large feature that was on the list to be included.

What is new in v3.00?

Peak shaving for ESS
Disable the touch feature on a GX Touch: great for rental and other systems where the whish is to display system status while not allowing any other user interaction.
Improved ESS control speed - for EM540 meters only
RV-C canbus protocol for (mostly USA-built) motorhomes: lots of improvements
Generator auto stop for systems where the generator is connected to AC-in-1, rather than AC-in-2, as well as as well as configurable warm-up and cool-down delays. Note that wiring the generator to AC in 1 is (becoming) the advised and preferred way to wire a generator. More information on that.
Many other small changes, see below.

Introduction to Venus OS beta testing

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.00~41 -> v3.00~42

All related to the new warm-up and cool-down function, as well as automatically stopping a generator when wired to AC-in 2:

Allow warmup and cooldown to also work with generator wired on AC-in-2.
Only show the warmup/cooldown settings if the Multi firmware is new enough. VE.Bus Firmware 501 or later is required.
Only show option to stop generator when AC input 2 is available if Multi firmware is new enough. This requires VE.Bus firmware 501 or later as well. If older firmware is used, only two options are shown: Disabled, and AC Input 1
Fix a bug that incorrectly showed a toast message when Stop on AC available was disabled.

Changes v3.00~39 -> v3.00~41

System overview: show inverting when inverting. Instead of External Control. On the on-screen overview, as well as on Remote Console and on VRM. This was broken in Venus OS v2.93. External control should only be shown when charging.
GUI: Fix two visualisation bugs:
- fix generator icon, as well as some other icons from no longer showing. Was broken earlier during v3.00 development. Thank you Kevin W for reporting.
- fix bug that caused a non existing Digital input 0 to show while making changes to the other inptus

Changes v3.00~37 -> v3.00~39

VE.Bus BMS v2: fix bug where solar chargers shutted down in Error #67, BMS lost, when the Multi is turned off. Broken since Venus OS v2.90.
Multi RS: fix display of AC in and out values; broken since v3.00~14
Fix bug that caused the state flip between Unknown and Float, or other charge states.Thank you @Roamer105 for reporting.

Changes v3.00~36 -> v3.00~37

Various improvements to generator star/stop control:

Add generator auto stop for systems where the generator is connected to AC-in-1, rather than AC-in-2. Note that wiring the generator to AC in 1 is (becoming) the advised and preferred way to wire a generator. More information on that.
Configurable warm-up and cool-down delays.

Details:

These features require VE.Bus firmware 502 to be installed. This version was released earlier this year. WARNING: updating VE.Bus firmware is recommended to be done only by trained professional installers, since all settings need to be reconfigured after doing an update.
Warm-up and cool-down delays only work when generator is wired to, and configured to be, on AC-in 1. This configuration is done in Setti ngs -> System setup in your GX device.

Screenshot of the updated "Stop generator when AC-input is available":

Screenshot of the new warm-up and cool-down time settings:

Multi, Quattro and EasySolar related changes:

For MultiPlus-II and Multi compact, don't show data when unit is switched off when AC input is available. Purpose of this change is to make the behaviour 100% equal to the other Multis and Quattros.
Fix some errors for systems running VE.Bus firmware versions prior to xxxx307.
Add Smart Lithium pre-alarm warning. Shows as notification in the GUI as well as entry in the alarm log on VRM. Note that this works only with the VE.Bus BMS v2 model. Not the prior model.
Add Error #67 - BMS connection lost alarm, similar to the same alarm code that is already in our MPPT Solar Chargers for a long time. The details: once the inverter/charger has received CVL/CCL or DCL data from a managed battery, it will switch off in case the battery (or GX device) is disconnected. Prior to adding this new Error #67, it would shut down with a Low voltage error. To make trouble shooting easier, we have now added Error #67. Note that the system will still also show a low battery voltage alarm. When in such situation, restore the connection with the BMS, or power cycle the inverter/charger.

GUI related changes:

Update translations
Change the maximum length for the wifi password to 63 characters.
Remove showing the battery voltage as part of an inverter/charger battery low alarm. The voltage shown was read only after the alarm came up; causing the shown voltage to be higher than level that triggered the alarm - confusing.

Changes v3.00~32 -> v3.00~36

For the EM24, ET112, ET330 and ABB meters, the ESS control loop is reverted to be slower and (thus) more stable. The response times are now similar as they are in v2.93 / before working on improving the response speeds. The ESS response speed for the (faster metering) EM540 is still the same: much faster than the other meters. Its actually even a bit faster than it was before v3.00~35. As also discussed in the comments of v3.00~32, having to revert to the previous version for the slow meters is quite a disappointment. The reason is that while working stable and fast for some installations, its also unstable in others. Whether we'll still make improvements on it remains to be seen. In essence those meters are slow, and then to make a stable and fast control loop is difficult and bound to create issues in some system.
Fix connection getting lost every few minutes to MultiPlus 2x120V models. Bug was introduced during v3.00 development, and is not in v2.93. Thank you @derrick thomas for reporting
Some more fixes.

Changes v3.00~29 -> v3.00~32

General

Fix bug related to kWh calculations (= source data for graphs on VRM Dashboards): If the position of a PV-inverter was changed, or the AC input (grid/genset) was changed, this would not take effect until a reboot.
Fix bug that could cause the reported state for a system of six inverter/chargers or more to be stuck; when very quickly switching the system on and then off again.

Modbus-TCP

Add reserved registers to plug a hole in the solarcharger range between 3704 and 3707.
- This gap was inadvertently created in Venus v2.80
- This fix allows fetching the entire block from 3700 to 3730 in a single call.
- This bug only affects MPPT-RS; the data in this block is related to Multiple trackers.

Venus OS large & developer:

Fix mDNS service advertisements for signalk-server; includes updating avahi-daemon from v0.7 to v0.8.
Add python3-can as optional package (see opkg in commandline instructions for how to install)

Changes v3.00~27 -> v3.00~29

DVCC:

Fix bug where data from the battery could get stuck/freeze until GX devices was rebooted. We've seen this happen in a handful of support cases; and it related to certain timing in the canbus messages. Once properly tested, we might release an interim official version v2.94 that includes this fix soon.

NMEA2000-out:

Fix PGN Fluid Level 127505 - fluid level instances not being writable. The fluid level instance is also refered to as the tank instance or data instance. The other instance, Device instance, was working fine and changeable.

Changing the fluid level is necessary on older Raymarine Axioms, since they have a limitation that the fluid instance needs to be same or lower than 5. We're not aware of any other situations where changing that instance is required; but if you do pls leave a comment below, so we can add it into the documentation and make everyones life wrt dealing with instancing easier.
Lastly, Thank you DevoDave for reporting!
Add transmission of battery selected as the System battery in GX settings, with a fixed device instance, as well as battery instance of 239. The aim of sending this PGN is that there is one instance, always the same, for the main battery in the system. Instead of a system with a Lynx Smart BMS using instance 0, and a system with a SmartShunt using different instances.
Update DC Detailed Status PGN: Add Amp Hours field, complies with NMEA200 v2.000.
Fix DC Detailed Status PGN, Time Remaining field: sometimes it showed zero when it shouldn't.

Touch disable function (read further down to learn what that is):

As additional measure to prevent lockout, re-enable touch if the IO that was configured for this is disabled or re-assigned.

Developers / internal:

Serial number was added in a TXT record in the mDNS response, for better "pairing" with other devices such as EV Charging Station.
Update VE.Bus inverter/charger driver, adding VE.Bus BMS Pre-Alarm data and some more; to be used by gui and VRM in the future.
Identify/recognise Pylontech Pelio-L battery. Just recognition for now, a future update will take care of automatic setting of DVCC and SVS and such.

Changes v3.00~26 -> v3.00~27

RV-C protocol, related to VE.Bus Inverter/charger DGNs
- Add the ability to change the maximum charge current using the CHARGER_CONFIGURATION_COMMAND DGN. This is a volatile setting and will be reset to the value the inverter/charger was configured with once the unit restarts.
- Add support for CHARGER_CONFIGURATION_STATUS to report the maximum charge current.
- Report maximum charger current as percentage in CHARGER_CONFIGURATION_STATUS_2 instead of the fixed 100%.

Node-RED (part of Venus OS Large)
- node-red-contrib-victron v1.4.32
- Move ActiveSocLimit to new path
- Fix pathData undefined error
- Added EnableDisplay and Scheduled mode (evcharger) (#169)
- Rename VE.Bus System reset to VE.Bus system restart (#170)
- Updated documentation
- Add L3 current for input-grid meter
- Update dependencies

Changes v3.00~25 -> v3.00~26
All rather minor:

General

Recognise Batrium BMS (this actually wasn't included in the previous version). No functional changes.

Signalk-Server (part of Venus OS Large)

minor change: call sync after modifying files before starting the server, to make sure they're written to disk immediately.

Changes v3.00~24 -> v3.00~25

Signalk-Server (part of Venus OS Large)

On start-up, check if any of the now default installed plugins was installed manually, and remove that one.

Changes v3.00~23 -> v3.00~24

General

Recognise Batrium BMS; no functional change

Signalk-Server (part of Venus OS Large)

Add and default-enable plugins sending NMEA data out on TCP, includes AIS data
- With this change, the GX device is a LAN and wireless AIS and navigation server for popular apps like Navionics, iSailor, iNavX, and Aqua Map on phones and tablets. This blog post by S/V Renaissance explains it nicely; but ignore all explanations about configuring plugins: that is all already done. Two examples: (1) Aqua Map App (link to Wifi connections page), (2) Navionics Boating App (link to AIS feature page).
- This feature requires a NMEA2000 connected AIS receiver on board. No internet is needed.
- The data is available as NMEA0183 packets on the default TCP port (10110), as well as signalk messages on the default websocket port.
- Note that this is not tested. If you have a navigation system, please test and let us know if it works; and if indeed no further configuration was required.
- All powered by the opensource signalk-server.
Fix pre-installing venus-signalk-plugin, it was missing. Unknown since which version; on v2.93 it was missing; most likely many prior versions as well.
Fix disabling updates of the pre-installed plugins
Known issue with signalk-server: mDNS advertisements most likely don't work.

Changes v3.00~22 -> v3.00~23

Internal changes

Changes v3.00~21 -> v3.00~22

RV-C out: increase timeouts on some battery and tank messages to match the maximum send interval. The previous timeout was too strict.

Changes v3.00~20 -> v3.00~21

Developer / Venus OS large related:

Node-RED (v1.4.29 & v1.4.30)
- Fix default for the new "Only changes" setting, it now defaults to off.
- Add option to round float values
- Filling out service and path of a node is now required
- Fix reporting relay state changes when the "only changes" option active. As well as other changes that use the dbus PropertiesChanged instead of ItemsChanged signal.
- New paths:
  - /Settings/SystemSetup/AcInput1 and 2 for input and output-settings
  - /Ac/Frequency for input-gridmeter
- Update documentation
- Thank you @mr-manuel for your help with above!
MQTT: Improve response when receiving a R/<portalid here>/system/0/Serial message. Instead of just activating the keep-alive, it will now always also respond by publishing the VRM Portal id.

Changes v3.00~19 -> v3.00~20

Fix the issue that was introduced in ~19.

Changes v3.00~18 -> v3.00~19

Internal changes only
Has known issue related to MQTT and also the HTML5-App and possibly VRM real time controls. A new version, v3.00~20 is expected later today.

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

Node-RED: fix the Node-RED Victron control nodes. The previous version (v3.00~17) broke all control nodes.

Changes v3.00~15 -> v3.00~17

General

ESS: Add peak shaving option (by observing the AC input current limit using PowerAssist)
- Peak shaving already worked in Keep batteries charged mode; no changes there, other than making it more obvious by adding in the Peak shaving menu entry.
- Peak shaving did not work will in the Optimised modes. It did work as long as battery SOC was above the configured ESS Minimum SOC level, but once discharged there the system would not assist the loads. This is now solved: use the new peak shaving option in the ESS menu, to let the system keep PowerAssisting when needed. And as soon as the peak is over, it will recharge the battery using power from the grid, while prioritising solar. Note that there is a 5% hysteresis on that: lets say Minimum SOC is set to 80%, it will then start recharging back to that 80% once (by peak shaving) the battery dropped to 75%.
- The default setting, when using the Optimised mode, is off. To not change behaviour of running systems.
- Warning: this works for the critical loads only. Not by energy meter.
- For further details, see screenshots below.
GX Touch: add option to disable the touch input. See settings -> I/O -> Digital inputs for the new feature. This is intended for systems where the GX Touch is wanted to show the users what the system is doing; but nothing else. The status of the touch (enabled/disabled) is toggled by pulling the gpio down to ground. More information about locking a system down is here; that text was recently updated, amongst other things a "Hardening a GX device" chapter was added.
EV Charging Station: show progress indication during a firmware update.
GUI, in the Multi & Quattro advanced menu, reword Reset to Restart. Less ambiguous in relation to a factory reset.
VRMLogger: add various new fields to be sent to VRM to improve the dashboard and dashboard controls.
Support the Fronius Tauro via SolarAPI: This is a rare edge case. Customers should use Sunspec instead of SolarAPI whenever possible, as per documentation. This change allows using SolarAPI in cases where Sunspec cannot be used. For example where modbus-RTU is in use on the DataManager and modbus-TCP cannot be used.
Energy meters:
- Fix issue with EM24 reported values being more erratic since earlier v3.00 releases. Now the behaviour is back to how it was pre v3.00
- Fix issue with EM540 phase sequence check for three phase systems. It reported the phase sequence as being incorrect while it wasn't.

Few changes that were also made available in v2.93:

Fix a problem where Remote Console wouldn't work, and required a factory reset to be repaired. Any systems now having the issues will be fixed automatically once updated to v2.93 or v3.00~16.
Fix timezone bug related to ESS Scheduled Charging: after changing the time zone, a reboot was required to make that use the new time zone. Bug was introduced in v2.80. Thank you Patrick M. for your help on this!
Add the new Scheduled mode and more for the EV Charging Station. Fixes "unknown" showing when the EV Charging Station is configured for that mode. For more information on that, read here.

Developer related

RaspberryPis: fix bluetooth connection to VictronConnect using the rpi-built-in bluetooth radio. This was broken during v3.00 development.
Node-RED, update node-red-contrib-victron from v1.4.26 to v1.4.27:
- Added option to input nodes to only broadcast changed values (see issue #147)
- Added missing input-vebus paths: /Bms/PreAlarm and /VebusChargeState
- Update documentation
Update the uPnP data (see this commit)
Update PHP from v7.4.28 to v7.4.33; next step is no longer using PHP at all.

Internals

Update MK3 firmware from v215 to v216. If already on v215, this update will happen automatically. If running an earlier version, the update will need to be triggered manually, as explained below.
Prepare VE.Bus firmware updater for some internal changes.

Changes v3.00~14 -> v3.00~15

General

add logging of generator runtime to VRM Portal (actual visualisation might still need work)
ESS: add support for all EM300 meters
ESS: add option to scheduled charging to allow discharging the battery (if SOC is below the configured minimum) while in the window; and more.
EV Charger: various features and fixes
Add support for Pylontech batteires having 16 cells in series (rather than usual 15 cells). Thank you Brian Finley!
Force good settings for Hubble batteries (DVCC on, STS off, SVS recommended off)

Protocols

Lots of improvements concerning RV-C; to be detailed
Modbus-TCP: fix issue related to inverter/charger state vs “ext control”.

Changes v3.00~8 -> v3.00~14

General

Fix Zigbee (DRF2685C) detection. (also available in Venus OS v2.93)
VE.Bus BMS v2: Improvements to remote firmware update feature
VE.Bus BMS v2: Add sending the pre-alarm status to VRM.
Bluetooth improvements for Cerbo GX with serial-nr HQ2208 and later, as well as all Cerbo-S GX production. The temperature issue which makes the built-in bluetooth unreliable/unusable no longer applies:
- Per mentioned serial numbers, a second Bluetooth radio has been added to the hardware. And per v3.00~14, Venus OS also uses that one; rather than the unreliable one. In more detail:
- For VictronConnect connection, new radio is used.
- For Ruuvis, all radios are used including any externally inserted ones (USB).
Fix bugs in the GUI that could cause it to show glitches and/or get stuck.
Add Thai language

Modbus-TCP

Fix register 31, the /State path for the VE.Bus inverter/chargers. Since v2.89 it returned value 252, Ext Control, for systems where the Inverter/charger is externally controlled. Instead of 3 (Bulk), 4 (Absorption) and so forth. Breaking customer integrations. (also available in Venus OS v2.93)

Venus OS Large

Update signalk-server from 1.44 to 1.46.2

Changes v3.00~4 -> v3.00~8

General

Multi/Quattro: Fix issue causing a repetitive low battery alarm in case the battery is disconnected
ESS: Fix bug introduced in v3.00~2 related to external control mode.
Add progress indicator (0 to 100%) to Venus OS firmware download.
Fix tank temperature unit (Fahrenheit)
Add new VE.Bus product ids (2681, 2723, 2766, 2776)
Add diagnostic fields for Multis/Quattros (uptime counter per unit, terminal voltage, Vsense voltage for L1 master and DC ripple)

Modbus-TCP

com.victronenergy.battery: Add /Dc/0/Power and /Mode, add missing fields to /State enum
com.victronenergy.digitalinput: Add "Generator" to /Type enum
com.victronenergy.multi (applies to RS products): fix in enum /State

Venus OS Large

Major change in node identification. Now using /DeviceInstance to find the correct node on the dbus instead of using the full service path. Full changelog and description here: https://github.com/victronenergy/node-red-contrib-victron/releases/tag/v1.4.25

Changes v2.92 -> v3.00~4

For systems having multiple BMSes connected, allow selecting which one should be used for DVCC. It also allows the use of a BMV for SOC tracking -- by selecting BMV as battery monitor -- while still using the BMS for DVCC. A bit of a niche issue for special systems, more technical background here: https://github.com/victronenergy/venus/issues/901 (but please don't start posting on our github - thanks).
Detect Hubble batteries, untested as of yet.
Add Polish translations, thank you Jakub T for helping with that!
ESS: increase control speed of systems using todays supported meters (ET112, ET330, EM24, and also the ABB ones) a little. But, for faster meters, such as the EM540 which is not available yet, increase it very significantly. Requires updating the built-in MK3-chip, see next bullet.
Include a newer version of onboard MK3-chip firmware, v215. Updating that has a 1 to 10% chance of a short system outage (Multi/Quattro shuts down in VE.Bus Error 14, restarts after 30 seconds). And therefore the update needs to be initiated manually from within the menu. Note that this is a reversible action, no need to worry about being unable to roll back. After updating, and then rolling Venus OS back to v2.92 or some other earlier version, the MK3 will automatically (and silently) be downgraded to the for that version of Venus OS required MK3-firmware version.
Improve text for tank sensor name in pump configuration.
ESS: Fix bug where PV is not used for loads when scheduled charging to 100% during daytime
Fix bug where a PV-inverter on AC-in-2 would not be shown in the ESS overview. The workaround was to configure the PV inverter as being on AC-in-1. Not needed anymore.

Venus OS Large

Fix issue sometimes causing certain values to update slower than necessary.
Add client_max_body_size to nginx config for larger flows.
Update nodejs to v14.17.6, which is the latest v14.17.* LTS. Change log here: https://github.com/nodejs/node/blob/main/doc/changelogs/CHANGELOG_V14.md#14.17.6

Under water / developer

Various small under the hood changes, mostly resulting in small reductions of CPU load
Replace Hiawatha webserver with nginx; which is better kept up to date (security)
Include various OE Dunfell fixes
DVCC: simplify transmission of the charge voltage setpoint by sending it always, rather than only if devices that work with it are detected. This won't make a difference to any commonly known system type.

MK3 firmware update related screenshots

On systems not updated yet, you'll see this (after going to the Device list, and then into the MultiPlus, Quattro or EasySolar listing):

And for anyone wanting to make sure its updated, in that same menu, scrolling all the way down to the Device submenu, and going in there, and scrolling down again, you'll find this listing:

Wherein the 212 digits are the version number, and thats the old one. And here is what you see after the update:

Note that this is necessary only for this one update. Hereafter, updates will be silent again, like they used to be; since there is no longer a risk of a short system outage.

Prior threads:

Venus OS

1682654806241.png (29.5 KiB)

1682654872164.png (45.8 KiB)

8

2 |3000

Attachments: 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) ♦♦ commented · May 12, 2023 at 08:18 PM

Good evening! right before the weekend starts another one, v3.00~42:

All related to the new warm-up and cool-down function, as well as automatically stopping a generator when wired to AC-in 2. Details above.

Have a good weekend; and if you have a generator, either wired on AC-in 1 or AC-in 2, and you are able to update your inverter/charger firmware to 501 or later (not something to do if you never did that before!), then it would be great to hear your experience with the new features!

1 ·

loadshedbuddycoza commented · May 21, 2023 at 10:58 PM

Please allow Venus OS to connect with the SmartShunt and smart mppt over Bluetooth.

Allowing us to ditch the Ve to usb cables.

Please.

1 ·

mvader (Victron Energy) ♦♦ commented · May 06, 2023 at 09:00 AM

Hi all, v3.00~39 is now available for testing.

And, a big THANK YOU, for all the good comments in below thread. Super "actionable" to use a fancy word. Have a good weekend!

0 ·

mvader (Victron Energy) ♦♦ commented · May 11, 2023 at 02:57 PM

v3.00~41 is now available for testing. Difference to prior version, which was v3.00~39 is two small bug fixes.

We're aiming here to release v3.00 next week or the week hereafter.

0 ·

lcoppenr commented · May 11, 2023 at 07:05 PM

I upgraded from 3.00 ~14 to 3.00 ~37 and then to 3.00 ~41 in the process MQTT seems to have broken. I can connect MQTT Explorer directly to my Venus OS RPI, but it only shows a topic tree with the serial number: N/{my VRM ID}/system/0/Serial and $Sys entries. I restarted, turned MQTT SSL and plaintext off/on, etc. It still won't update MQTT with the entries for the SmartMPPT 100/30 and BMV-712 (usb connections), which show just fine in the standard interface, just not in MQTT. I may wipe the RPI and start over, but thought I should check here as the beta has had some MQTT update that could have a bug.

0 ·

mvader (Victron Energy) ♦♦ lcoppenr commented · May 11, 2023 at 07:14 PM

Hi, thank you; yes would be nice to firsr see if something needs fixing. Are you sending any keep alive messages to mqtt? If not, then what you are seeing is normal.

Or open VRM portal to do that for you: whats needed is that at least one client sends keep alives.

See dbus-mqtt readme for details on keep alives.

0 ·

lcoppenr mvader (Victron Energy) ♦♦ commented · May 12, 2023 at 11:45 PM

I'll double check that the keep alive is still working. Forgot all about that process. thx

0 ·

n-dee commented · May 26, 2023 at 06:40 AM

Hi,

Im using my generator to directly load the batteries (DC)
It would be supercool if this type of connection may be configured in cerbo in the future aswell.

Andy.

0 ·

Modifications Space

Node Red Space

Answer 1 · 2023-04-28T09:22:49Z

Michelle Konzack answered · Apr 28, 2023 at 09:22 AM

Changes v3.00~37 -> v3.00~37

Overworked and tired?

I think, it should be

Changes v3.00~36 -> v3.00~37

2

2 |3000

Attachments: 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) ♦♦ commented · Apr 28, 2023 at 11:00 AM

:-) - overworked not, but a bit tired yes; Thanks!

0 ·

Mark Maritz mvader (Victron Energy) ♦♦ commented · May 17, 2023 at 05:35 AM

And this ;)

0 ·

1684301757326.png (36.7 KiB)

Answer 2 · 2023-04-28T14:11:35Z

anieuwstadt answered · Apr 28, 2023 at 02:11 PM

SCENARIO:

Venus: V3.00~37 and V2.94 (did not try other versions)
System: 6x MP II 5k (v502), 3ph, Freedom Won, 2x RS450/200
ESS> Grid feed-in> DC & AC turned OFF
ESS> Grid metering> External EM540
ESS> Mode> Keep charged
Input current limit: 36A

ISSUE: Grid feed-in occurs when feed-in is turned OFF. This does not happen when the PV is disabled.

4

2 |3000

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

nickdb ♦♦ commented · Apr 28, 2023 at 02:33 PM

Change phase regulation to individual phase from total of all phases. This is unrelated to this beta so please use a different thread.

Can be caused by several things beyond this including mismatched inverters, asymmetrical wiring and grid conditions.

0 ·

mvader (Victron Energy) ♦♦ commented · Apr 28, 2023 at 06:20 PM

Hi both,

@nickdb , why would changing the phase regulation setting make a difference? As far as I know the common Eskom calculation method in SA is to look at total sum of power. So then “total of all phases” is correct.

Either way, if feed-in is disabled it should not feed in. When phase regulation is set to total power, then the total of all phases should be above the configured grid set point;

And when set to individual phase regulation then each phase should be above the configured grid set point.

Looks indeed to be unrelated to this beta. Please do make a separate post @anieuwstadt , and drop a link here so I know where it went.

Have a good weekend!

0 ·

nickdb ♦♦ mvader (Victron Energy) ♦♦ commented · Apr 29, 2023 at 05:45 AM

We’re not permitted to feed in to eskom in any form. Not everyone has eskom direct, many are on municipal supply and some of their meters will even just cut you off.

0 ·

anieuwstadt mvader (Victron Energy) ♦♦ commented · May 01, 2023 at 04:21 PM

Hello,

Thank you.

Created a new ticket with the title: ESS feeding into grid when AC PV and DC PV feed-in is disabled

0 ·

Answer 3 · 2023-04-28T23:00:09Z

Kevin Windrem answered · Apr 28, 2023 at 11:00 PM

The generator warm-up and cool-down options do not appear unless one of the system AC inputs is set to generator. All other generator settings appear even of no generator AC input is defined.

Actually I discovered that AC 2 IN must NOT be defined as generator. This seems excessive in order to see the parameters in settings

2

2 |3000

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

Kevin Windrem commented · Apr 29, 2023 at 02:56 PM

And a suggestion: The Don't start generator ... setting is currently set for AC 1 and AC 2 Input. I think the setting should be Don't start generator when Grid/shore power is present. This would eliminate the warnings that pop up to be sure the generator is not connected to the selected input and be more intuitive. Also, this could then be based on a grid meter as well as the Multi/Quattro AC input detectors.

1 ·

mvader (Victron Energy) ♦♦ commented · Apr 29, 2023 at 05:17 AM

Yes, we’ve an issue listed to fix this; thanks!

0 ·

Answer 4 · 2023-04-29T09:44:32Z

janieronen answered · Apr 29, 2023 at 09:44 AM

Where I could find explanation how new functionality ESS -> Scheduled charge -> Self-consumption about "PV" or "PV&Battery" -modes work? Like to test feature. Sorry could not find better place to ask as this is beta related question and not find from previous beta threads.

1

2 |3000

Attachments: 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) ♦♦ commented · Apr 29, 2023 at 11:56 AM

Hi, good question, I had to look for that myself a bit.

Answer is most likely in here: https://github.com/victronenergy/venus/issues/970.

If you have any further questions, please ask them here on community (not on github)

1 ·

Answer 5 · 2023-04-29T15:21:02Z

derrick thomas answered · Apr 29, 2023 at 03:21 PM

Not sure if this is a bug or I am just not understanding the expected behavior.

I have set the generator cool down time to 10 seconds, to which I am seeing a delay between the time I tap on the stop button and when the system initiates a shut down, as expected. What I am not seeing is any change in behavior other than the delay. I would expect a cool down period to initiate an ac input disconnect in order to unload the generator for the cool down time period. The ac input remains connected and drawing power from the generator until it shuts down.

14

2 |3000

Attachments: 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) ♦♦ commented · Apr 29, 2023 at 05:00 PM

Hi what firmware version is the inverter/charger running? That needs to be 502 or above.

(And you are right; what should happen is that first the inverter/charger goes to inverter mode, then ten seconds of cool down without load, and then stop)

0 ·

derrick thomas mvader (Victron Energy) ♦♦ commented · Apr 29, 2023 at 05:22 PM

Inverters are on 502. Dual mp2 3000/24v/2x120 in parallel.

0 ·

derrick thomas mvader (Victron Energy) ♦♦ commented · Apr 29, 2023 at 05:54 PM

I updated the mk3 as well but still not acting as expected.

My air cond really is not happy when the generator shuts down without the inverter switching over first.

0 ·

Show more comments

Answer 6 · 2023-04-29T19:41:37Z

roamer105 answered · Apr 29, 2023 at 07:41 PM

I went back to ~32 after trying this version on my CCGX with Multi, SmartSolar, Tanks, GPS, RUUVIs etc. After the upgrade to ~37, the CCGX periodically rebooted (crashed) and the MULTI Status on the CCGX was flipping between unknown and float (which makes no sense).

On ~32 everything works fine and stable.

4

2 |3000

Attachments: 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) ♦♦ commented · Apr 29, 2023 at 08:15 PM

Hi @Roamer105 , that sounds like some process is crashing and causing cpu overload.

Is it ok if one of us logs in on the Remote Support feature to check the logs?

You can enable that on Settings -> General.

ER105, right?

0 ·

roamer105 commented · Apr 29, 2023 at 08:33 PM

Absolutely! However I rebooted on the ~32 version and maybe the logs are no longer available. What do you need to gain access?

0 ·

mvader (Victron Energy) ♦♦ roamer105 commented · Apr 29, 2023 at 09:03 PM

Hi, nothing was needed - you have enabled Remote support" on that system and that's enough.

I've been able to login, have looked at the logs; and the driver for the inverter/charger was continuously having an issue. Which also explains the flipping between unknown and float.

I have what I needed, it will be worked on. thanks!

1 ·

mvader (Victron Energy) ♦♦ mvader (Victron Energy) ♦♦ commented · May 06, 2023 at 07:31 AM

Hi @Roamer105 , we fixed the flipping back and forth. In v3.00~39, available later today.

I’m not sure if that also fixes the reboots: please keep an eye on that. Thanks!

0 ·

Answer 7 · 2023-04-30T16:28:47Z

Kevin Windrem answered · Apr 30, 2023 at 04:28 PM

The generator icon is missing from the Generator Overview page.

This is with the stock page (GuiMods not installed) (and also with GuiMods installed).

OK in v3.00~36 so problem is new to ~37

2

2 |3000

Attachments: 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) ♦♦ commented · May 06, 2023 at 07:01 AM

Hi Kevin,

Thank you, we’ll fix that.

0 ·

mvader (Victron Energy) ♦♦ mvader (Victron Energy) ♦♦ commented · May 11, 2023 at 12:31 PM

Hey again @Kevin Windrem , fixed per v3.00~41, which is available in a few minutes. Thanks again!

0 ·

Answer 8 · 2023-05-01T05:34:31Z

pedaaa answered · May 01, 2023 at 05:34 AM

i am not sure, if this is really related to V3.00, but i felt it was better before:

I have an 3phase ESS with 3xMP2 5000, 2x Fronius PV-Inverter, 1x MPPT RS450/100 and an EM540 gridmeter

As the update-rate of the EM540 is super fast, but the PV-inverter data isn´t, it leads to very inacurate AC-consumption calculation.

Especially if its sunny with some clouds. That causes the PV-Power to jump up and down quickly.

The EM540 immediately shows this changes, but the PV-Inverters data lacks behind.

This causes the calculated AC-consumption to jump up and down as well.

I can visualize this very well, as i have a separate engery meter for my "actual" AC-Consumption:

- yellow is the total PV-production

- gray is the actual AC-consumption, captured with external energymeter (L1+L2+L3)

- blue is the AC-consumption, Victron calculates and broadcasts (sum of Modbus registers 817+818+819)

As you can see, the actual AC-consumption is kind of smooth and steady.

But the Victron calculated one is fluctuating, following the PV-production.

The reason for this fluctuation is clear: Its because of the different update-rates of fast EM540 gridmeter and slow PV-inverters and MPPT RS450 data.

But i think it got a little worse with V3.00

Maybe you can add some kind of filter, so that AC-consumption is calculated at same time-stamp points, even if data-update-rate is differente?!

Might easier said, than done, i know...

But would be great, if you can do. Or at least have a look at it

1682918667059.png (64.5 KiB)

3

2 |3000

Attachments: 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) ♦♦ commented · May 06, 2023 at 07:02 AM

Hi @Pedaaa , thank you for the detailed report; we’ll look into that.

0 ·

mvader (Victron Energy) ♦♦ mvader (Victron Energy) ♦♦ commented · May 16, 2023 at 09:10 PM

Hi @Pedaaa , we've started working on this; and yes needs an improvement.

Its not something that will be done in v3.00, any improvements will be in a later version; I'll aim for the next (somewhat larger) version that gets released.

1 ·

pedaaa mvader (Victron Energy) ♦♦ commented · May 17, 2023 at 03:17 AM

many thanks!

i have tried to overlay my own filter-strategies for own post processing. But i am 100% sure, you can do better at source level of this data.

Really love your motivation to improve things. That behaviour i totally miss on other products/suppliers

0 ·

Answer 9 · 2023-05-01T18:27:31Z

nebulight answered · May 01, 2023 at 06:27 PM

Add Error #67 - BMS connection lost alarm, similar to the same alarm code that is already in our MPPT Solar Chargers for a long time. The details: once the inverter/charger has received CVL/CCL or DCL data from a managed battery, it will switch off in case the battery (or GX device) is disconnected. Prior to adding this new Error #67, it would shut down with a Low voltage error. To make trouble shooting easier, we have now added Error #67. Note that the system will still also show a low battery voltage alarm. When in such situation, restore the connection with the BMS, or power cycle the inverter/charger.

I can't wait to test this! This is a great feature for those that make additional protections in case of BMS comms failure. Those will still be in place, but at least now there is additional protection, straight from the GX.

1

2 |3000

Attachments: 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) ♦♦ commented · May 06, 2023 at 07:30 AM

Hi! Good to hear you’re enthusiastic. Note that its not a new protection.

The protection was already there.

What changes is that its now more noticable when the protection is active.

0 ·

Answer 10 · 2023-05-01T19:09:46Z

n8lauscher answered · May 01, 2023 at 07:09 PM

@mvader (Victron Energy)
Does this version also try to fix this problem:

VRM Instance Number Changed - Victron Community (victronenergy.com)

1

2 |3000

Attachments: 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) ♦♦ commented · May 06, 2023 at 07:18 AM

Hi @n8lauscher@gmail.com , no sorry.

Most of that has been fixed a long time ago. As far as I remember, the only remaining issue is MK3-USB, mostly/only used in combination with rapsberrypi’s.

I’ll check with the developer how much work this is.

Its taking so long because its in a complex piece of code, and main maintainer/developer has many other things to do.

EDIT: I typed here that we are working on a way to edit VRM instances from the gui, which we are, but it won't solve your issue - sorry.

0 ·

Answer 11 · 2023-05-03T11:12:17Z

jetronic answered · May 03, 2023 at 11:12 AM

@mvader (Victron Energy)

I have noticed the following with version v3.00~37, that my Fronius inverter is no longer displayed on the "Pages" display.
In the menu setting it is visible as PV Inverter.

I then made a downgrade to version v2.94, and there the inverter is again displayed in the "Pages" representation.

3

2 |3000

Attachments: 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) ♦♦ commented · May 06, 2023 at 07:22 AM

Hi @jetronic , If your PV-inverter doesn't show up on the Overview, please check that it is configured for the correct AC-input.

Prior to v3.00, this would self-correct. But in v3.00 and beyond such auto-correction is no longer possible due to another change.

0 ·

jetronic mvader (Victron Energy) ♦♦ commented · May 11, 2023 at 12:04 PM

I have now upgraded to v3.00~39 with a test instance. The behavior is still exactly the same, in the menu the inverter is displayed but not in the overview.

I run the test instance parallel to my production system in the same network without Multiplus. Only to the info

The inverter is configured correctly L1 is selected, if that is meant.

0 ·

mvader (Victron Energy) ♦♦ jetronic commented · May 11, 2023 at 08:23 PM

We’ll check; thank you.

0 ·

Answer 12 · 2023-05-04T09:53:31Z

palle answered · May 04, 2023 at 09:53 AM

Bug?

When I have my MultiPlus in charge only mode and I disconnect the shore line. I get a Alarm notification in Remote Console every 10 or 15 sec. If I set the mode in MP to off, the alarm stop coming.

3:37 and 502

In my other boat I have 3:27 and 502 and I don´t get the alarm.

1

2 |3000

Attachments: 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) ♦♦ commented · May 06, 2023 at 06:41 AM

Hi @Palle , yes thats a bug. Thank you for the report. Its fixed in a newer version, v3.00~39, which I expect to have ready lter today.

0 ·

Answer 13 · 2023-05-05T14:44:20Z

fgingat answered · May 05, 2023 at 02:44 PM

Batrium BMS doesn't work anymore with 30.~ beta versions .. (no SOC display on interface)

if i revert back everything is ok.

2

2 |3000

Attachments: 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) ♦♦ commented · May 06, 2023 at 07:23 AM

Hi @fgingat we’ll look into that, thank you.

0 ·

fgingat mvader (Victron Energy) ♦♦ commented · May 06, 2023 at 08:17 AM

If needed i can allow you remote access

0 ·

Answer 14 · 2023-05-06T06:31:36Z

Morning, i'm loving the new beta, but i've got a problem with Signal K (which I've been using for a year on my boat). I upgraded from v.25 to v.30 and now I cannot add any new plug-ins or save any settings for my existing plug-in (I get "Saving plugin settings failed" or "Failed" on an install).

I see you made some changes to the storage in v. 26, so was wondering if it was related to that... looking in the Signal K error logs, I can see the following:

When trying to update a plug-in:

May 06 06:25:37 Error: ENOSPC: no space left on device, write at Object.writeSync (fs.js:733:3) at Object.writeFileSync (fs.js:1530:26) at savePluginOptions (/usr/lib/node_modules/signalk-server/lib/interfaces/plugins.js:130:26) at /usr/lib/node_modules/signalk-server/lib/interfaces/plugins.js:405:13 at Layer.handle [as handle_request]

When trying to install a new plug-in:

May 06 06:27:23 stderr: npm WARN registry Unexpected warning for https://registry.npmjs.org/: Miscellaneous Warning ENOSPC: ENOSPC: no space left on device, write npm WARN registry Using stale data from https://registry.npmjs.org/ due to a request error during revalidation.
May 06 06:27:27 TypeError [ERR_INVALID_ARG_TYPE]: The "target" argument must be an instance of Buffer or Uint8Array. Received undefined at _copy (buffer.js:212:11) at Buffer.copy (buffer.js:768:12) at Parser._parse (/usr/lib/node_modules/signalk-server/node_modules/@canboat/canboatjs/lib/fromPgn.js:175:26) at Parser.parsePgnData (/usr/lib/node_modules/signalk-server/node_modules/@canboat/canboatjs/lib/fromPgn.js:320:24) at Parser.parse (/usr/lib/node_modules/signalk-server/node_modules/@canboat/canboatjs/lib/fromPgn.js:302:19) at CanboatJs._transform (/usr/lib/node_modules/signalk-server/node_modules/@signalk/streams/canboatjs.js:52:34) at CanboatJs.Transform._read (internal/streams/transform.js:205:10) at CanboatJs.Transform._write (internal/streams/transform.js:193:12) at writeOrBuffer (internal/streams/writable.js:358:12) at CanboatJs.Writable.write (internal/streams/writable.js:303:10) at CanbusStream.ondata (internal/streams/readable.js:726:22) at CanbusStream.emit (events.js:400:28) at addChunk (internal/streams/readable.js:290:12) at readableAddChunk (internal/streams/readable.js:265:9) at CanbusStream.Readable.push (internal/streams/readable.js:204:10) at CanbusStream.Transform.push (internal/streams/transform.js:166:32) { code: 'ERR_INVALID_ARG_TYPE' }
May 06 06:27:29 stderr: npm ERR! code ENOSPC npm ERR! syscall mkdir npm ERR! path /data/conf/signalk/node_modules/.staging npm ERR! errno -28 npm ERR! nospc ENOSPC: no space left on device, mkdir '/data/conf/signalk/node_modules/.staging' npm ERR! nospc There appears to be insufficient space on your system to finish. npm ERR! nospc Clear up some disk space and try again.

Answer 15 · 2023-05-06T09:14:34Z

Interesting - looks like something still isn't quite right....

May 06 09:06:13 GET /skServer/plugins 304 28.184 ms - -
May 06 09:06:13 GET /signalk/v1/api/sources 200 145.021 ms - -
May 06 09:06:13 TypeError [ERR_INVALID_ARG_TYPE]: The "target" argument must be an instance of Buffer or Uint8Array. Received undefined at _copy (buffer.js:212:11) at Buffer.copy (buffer.js:768:12) at Parser._parse (/usr/lib/node_modules/signalk-server/node_modules/@canboat/canboatjs/lib/fromPgn.js:175:26) at Parser.parsePgnData (/usr/lib/node_modules/signalk-server/node_modules/@canboat/canboatjs/lib/fromPgn.js:320:24) at Parser.parse (/usr/lib/node_modules/signalk-server/node_modules/@canboat/canboatjs/lib/fromPgn.js:302:19) at CanboatJs._transform (/usr/lib/node_modules/signalk-server/node_modules/@signalk/streams/canboatjs.js:52:34) at CanboatJs.Transform._read (internal/streams/transform.js:205:10) at CanboatJs.Transform._write (internal/streams/transform.js:193:12) at writeOrBuffer (internal/streams/writable.js:358:12) at CanboatJs.Writable.write (internal/streams/writable.js:303:10) at CanbusStream.ondata (internal/streams/readable.js:726:22) at CanbusStream.emit (events.js:400:28) at addChunk (internal/streams/readable.js:290:12) at readableAddChunk (internal/streams/readable.js:265:9) at CanbusStream.Readable.push (internal/streams/readable.js:204:10) at CanbusStream.Transform.push (internal/streams/transform.js:166:32) { code: 'ERR_INVALID_ARG_TYPE' }
May 06 09:06:13 Could not parse JSON options:Unexpected end of JSON input
May 06 09:06:13 Could not parse JSON options:Unexpected end of JSON input

And also after a reboot:

May 07 06:00:45 2023-05-07T06:00:45.257Z signalk-venus-plugin warning: error getting device instance for com.victronenergy.qwacs
May 07 06:00:45 2023-05-07T06:00:45.260Z signalk-venus-plugin warning: error during GetValue on / for com.victronenergy.qwacs No such interface 'com.victronenergy.BusItem' at object path '/'
May 07 06:00:45 2023-05-07T06:00:45.263Z signalk-venus-plugin warning: error getting device instance for com.victronenergy.settings
May 07 06:00:45 2023-05-07T06:00:45.724Z signalk-venus-plugin warning: error getting device instance for com.victronenergy.vecan.can0
May 07 06:00:46 2023-05-07T06:00:46.125Z signalk-venus-plugin warning: error getting device instance for com.victronenergy.fronius
May 07 06:00:46 2023-05-07T06:00:46.717Z signalk-venus-plugin warning: error getting device instance for com.victronenergy.platform
May 07 06:00:47 2023-05-07T06:00:47.335Z signalk-venus-plugin warning: error getting device instance for com.victronenergy.modbusclient.tcp
May 07 06:00:47 2023-05-07T06:00:47.810Z signalk-venus-plugin warning: error getting device instance for com.victronenergy.logger
May 07 06:00:48 2023-05-07T06:00:48.091Z signalk-venus-plugin warning: error getting device instance for com.victronenergy.adc
May 07 06:00:52 2023-05-07T06:00:52.049Z signalk-venus-plugin name owner change: {"serial":7,"path":"/org/freedesktop/DBus","interface":"org.freedesktop.DBus","member":"NameOwnerChanged","sender":"org.freedesktop.DBus","signature":"sss","type":4,"flags":1,"body":[":1.126","",":1.126"]}
May 07 06:00:52 2023-05-07T06:00:52.052Z signalk-venus-plugin name owner change: {"serial":8,"path":"/org/freedesktop/DBus","interface":"org.freedesktop.DBus","member":"NameOwnerChanged","sender":"org.freedesktop.DBus","signature":"sss","type":4,"flags":1,"body":[":1.126",":1.126",""]}

signalk-venus-plugin warning: error during GetValue on / for com.victronenergy.qwacs No such interface 'com.victronenergy.BusItem' at object path '/'

What do you think? I know it's not core Victron functionality, but it's a real shame it doesn't seem to be working properly.

Answer 16 · 2023-05-13T08:41:41Z

nickdb answered · May 13, 2023 at 08:41 AM

@mvader (Victron Energy) I updated a site to -39 (and onwards to -42) to test peak shaving, which is working well.

We have run into a strange behaviour after (most) grid recoveries (post loadshedding) or if the GX is restarted.

System has a quattro (current firmware) both AC-coupled (Fornius) and DC PV.

When power returns or the GX is restarted the 2 MPPT's (1.61 firmware) both go to sleep, showing 0 or occasionally 5W. They will not charge the battery or be used for loads, unless you force the system onto invert, but they go back to sleep when setting it to "on" again.

They only way to resolve seems to be to set the quattro to "off" losing all power and then bringing the quattro back online.

This started after the -39 updated.

There were very rare occasions of this on < 2.93 but now it is pretty consistent.

Happy to share the site URL.

screenshot-2023-05-13-at-101336.png (66.7 KiB)

screenshot-2023-05-13-at-102811.png (213.0 KiB)

2

2 |3000

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

nickdb ♦♦ commented · May 16, 2023 at 12:54 PM

This may have resolved after the recent updates. It has not reappeared since after grid recovery, it last occurred after that intentional restart of the Cerbo.

0 ·

mvader (Victron Energy) ♦♦ nickdb ♦♦ commented · May 16, 2023 at 09:11 PM

thank you @nickdb . If this happens again, please let me know and we'll look into it.

0 ·

Answer 17 · 2023-05-14T22:16:10Z

derrick thomas answered · May 14, 2023 at 10:16 PM

Has the polling frequency of victron nodes (node red) changed through these 3.00~xx beta releases? I realize there has been a major update to the victron nodes and how they are handled, but I suspect there may be a change to polling? Full transparency I do have guimods and exttransferswitch installed. I am using an external relay module through modbus tcp and controlling the external relays through the gui (guimods adds 4 additional relays to the gui) using node red.

It seemed like when I was on 3.00~32 the response time from pressing the relay on/off on the gui was almost instant, say maybe 1 second delay at most. Now on 3.00~41 it seems that the delay is back to several seconds. I realize that the default behavior before beta 3.00~ was 5 second polling interval for victron nodes. Am I imagining that there was a change in 3.00~32 that is reverted back to 5 seconds in later betas? Is there a way to change the polling interval for individual nodes?

1

2 |3000

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

Dirk-Jan Faber (Victron Energy) ♦♦ commented · May 17, 2023 at 06:00 AM

The way of polling has not changed since I took over the maintenance of the code (about two years ago). It was and is still set to 5 seconds. Besides polling it also responds to value changes, so in practice the frequency of messages is above 5 seconds. The "onlyChanges" options is one of the ways to have less frequent updates coming out of the node. At the moment there is no way to change the polling interval for individual nodes.

That being said, there is always a possibility that things don't act the way they are supposed to. I tried to replicate your issue, but as soon as I change the relay, the response that I get from the output node is instant. Can you file a bug here so I can further investigate why it takes so long on your system?

0 ·

Answer 18 · 2023-05-15T11:42:48Z

anieuwstadt answered · May 15, 2023 at 11:42 AM

SYSTEM: as per screenshots

VERSIONS: V3.00~42, MP II V502,

When ESS is set to:

Keep batteries charged
1. Solar generation is used when no grid. Correct
2. Solar generation is reduced when there is a grid and load power is drawn from the grid, and the sun is largely ignored. Incorrect
Optimised without battery life, the solar "optimise" works as expected. Correct

Oddly if on V3.00~42 and downgrade to V2.94 the problem persists

If on V2.94 without changing to V3.00 and back to V2.94, V2.94 works correctly.

KEEP CHARGED: NO GRID SOLAR USED

KEEP CHARGED: ON-GRID SOLAR IGNORED (ISSUE)

OPTIMISED: BATTERY FULL AND SOLAR IS USED

1684149054871.png (80.1 KiB)

1684149077432.png (86.0 KiB)

1684149130933.png (88.8 KiB)

1

2 |3000

Attachments: 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) ♦♦ commented · May 16, 2023 at 09:39 PM

Hi @anieuwstadt noted! we'll look into this.

0 ·

Answer 19 · 2023-05-16T09:59:45Z

nickdb answered · May 16, 2023 at 09:59 AM

since -41 Node red seems to keep showing this message, despite reboots. It appears to work fine though.

screenshot-2023-05-16-at-115837.png (12.8 KiB)

2

2 |3000

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

nickdb ♦♦ commented · May 16, 2023 at 01:26 PM

Only seems to affect Safari. Firefox behaves fine.

0 ·

mvader (Victron Energy) ♦♦ nickdb ♦♦ commented · May 16, 2023 at 09:19 PM

Hi @nickdb, to which previous Venus OS version are you comparing? The last change I can find was per v3.00~27; quite a while back.

What I'm need to decide is if this a regression that needs fixing before v3.00 release, or not?

0 ·

Answer 20 · 2023-05-16T10:33:03Z

atomykatt answered · May 16, 2023 at 10:33 AM

My system consists of two SOK 48V 100Ah LiFePO4 rack mounted batteries, a RS 450/200-Tr solar charger and 3 Multiplus II 5kVA running three phase. They do NOT charge from the grid. ESS is set to "Optimized (Without Battery Life)". I have set the maximum voltage to 57.6V everywhere I found this to be configurable both on the BMS and all the victron equipment. So far the system seems to work as expected. No alerts in the VRM portal, however, I receive a "High Battery Voltage" alarm whenever the battery nears 100%. This only happens on the GX display:

I'm on V3.0~42

1684233049122.png (85.8 KiB)

3

2 |3000

Attachments: 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) ♦♦ commented · May 16, 2023 at 09:21 PM

hi @Atomykatt , thank you for the report and good to hear all works well except for that over voltage alarm.

What I can tell you is that that is an alert coming from within the battery/bms itself. I can't give any help on that.

1 ·

atomykatt mvader (Victron Energy) ♦♦ commented · May 17, 2023 at 06:13 AM

Cool, thanks. Good to know that it's not a Cerbo/Victrron issue. I'll rummage around the BMS to see if anything can be altered to not get that alarm anymore then.

0 ·

hominidae atomykatt commented · May 31, 2023 at 08:23 AM

that voltage is way too high for pylontechs, which normally are 15s modules.

See: https://www.victronenergy.com/live/battery_compatibility:pylontech_phantom

If the GX does not detect these as pylontechs, set the DVCC voltage manually to 52.24V or even lower.

0 ·

Answer 21 · 2023-05-17T09:15:16Z

towatai answered · May 17, 2023 at 09:15 AM

am i blind or are there no changelogs from v3.00~41 -> v3.00~42?

2

2 |3000

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

derrick thomas commented · May 22, 2023 at 02:43 AM

It's in the first post in this thread

0 ·

towatai derrick thomas commented · May 23, 2023 at 05:51 AM

When I created my post, the entry in the start post was not there, even after days. Thanks for catching up!

0 ·

Answer 22 · 2023-05-31T07:04:02Z

harold answered · May 31, 2023 at 07:04 AM

Hi
Thanks, Now I am on 3.00, my Quattro is on 502.

But I cannot find the new generator warmup and cool down timers!

Harold

2

2 |3000

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

Marc Elvery commented · May 31, 2023 at 09:34 AM

Make sure you have updated your MK3

1 ·

harold Marc Elvery commented · May 31, 2023 at 09:53 AM

THANKS

that was it!

0 ·

Answer 23 · 2023-06-02T18:48:36Z

Mike Dorsett answered · Jun 02, 2023 at 06:48 PM

Ive just tried installing the

"venus-install-sdcard-beaglebone-20230529211714-v3.00 " image on a beaglebone black, and a beaglebone green, in both instances the 2nd stage led remains flashing, and

i2c2 and all of the spi devices are not listed in the /dev folder.

2 |3000

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

Answer 24 · 2023-06-19T19:17:24Z

adahmen answered · Jun 19, 2023 at 07:17 PM

Do I need to update my Multiplus 2 to V502 before upgrading to 3.00?

Currently my Multiplus is on V498.

1

2 |3000

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

derrick thomas commented · Jun 19, 2023 at 07:51 PM

If you plan on using the new generator timer features included in v3.00 then you will need to update the inverter firmware and the mk3 driver in the cerbo. The order in which you update the components makes no difference.

1 ·

Answer 25 · 2023-07-01T07:02:20Z

petajoule answered · Jul 01, 2023 at 07:02 AM

After changing input current while in "inverter only", the select position for the Switch ist "off".

Not a big fan of this.

->

Turning off the installation is just one keypress away now.

As I said: not a big fan. I would expect the selection hovering over "Inverter Only"

vgx1.jpg (59.4 KiB)

vgx2.jpg (61.2 KiB)

vgx3.jpg (52.3 KiB)

3

2 |3000

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

petajoule commented · Aug 03, 2023 at 07:00 AM

"$(/)"($&"$!!!!! And today it happened!

Switched off the installation, when I wanted to go from inverter to "On".
Yeah, it was in the morning, yeah, I had not my glasses on, yeah I pressed before I thought.

Which I believe is natural for most of you - including software engineers @ Victron - before you had your morning coffee.

0 ·

ojack petajoule commented · Aug 03, 2023 at 08:49 AM

Maybe opening a pop off like

"do you really want to turn OFF?"

1 ·

petajoule ojack commented · Aug 17, 2023 at 05:15 PM

Yeah. Anything better than what is now.

0 ·

Answer 26 · 2023-07-11T06:13:37Z

chrisu answered · Jul 11, 2023 at 06:13 AM

Hello,

one Question about this Topic:

For the EM24, ET112, ET330 and ABB meters, the ESS control loop is reverted to be slower and (thus) more stable. The response times are now similar as they are in v2.93 / before working on improving the response speeds. The ESS response speed for the (faster metering) EM540 is still the same: much faster than the other meters.

I checked the Source Code at Github and it seems, that the faster readings were only implemented for the EM24-RS485 when using the dbus-cgwacs Library, but then this was downgraded to 1sec again. (https://github.com/victronenergy/venus/issues/1017)

The Library for the EM24 Ethernet and the ABB Meters is the dbus-modbus-client and there, the refresh rate never changed, it is always 250msec in https://github.com/victronenergy/dbus-modbus-client/blob/master/dbus-modbus-client.py

Maybe you could clarify?

2 |3000

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

question

Venus OS v3.00 released officially

Related Resources

question details

Modifications Space

Node Red Space

question

Venus OS v3.00 released officially

Related Resources

question details

Related Questions

Modifications Space

Node Red Space