question

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

Venus OS v3.20~51 available for testing

UPDATE 2024-02-13 - v3.20 has been released officially (announcement). v3.30 beta testing will start within days.
UPDATE 2024-02-12 - v3.20~51 is now available
UPDATE 2024-02-10 - v3.20~50 is now available


Good evening!

With Venus OS v3.14 out and released officially, we can resume beta testing of the v3.20 beta series.

The highlights in the v3.20 beta series are:

  1. A new user interface, work name gui-v2, more information at the bottom of this post. Note that that gui will not be part of the v3.20 official release.

  2. New HTML5 Marine MFD user interface, see screenshots at the bottom of this post (search for "highlight")


Aside from above, there are many many more changes, to learn about them, see the many change log entries below.


Yours sincerely,

Matthijs Vader


Instructions: 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.


Instructions: 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 (v3.10), 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.


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

In case you are running Node-RED or SignalK, 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 can cause a compatibility issue with the GuiMods; and these betas report pages are for official firmware only.


Changes v3.20~51 - and official release

  • Fix bug that caused the Orion XS state to show Low Power or AES some times. That state doesn't exist, and when showing that it is off. Now it just shows Off in that case.


Changes v3.20~50

  • Orion XS: set internal profile to Alternator when configured as a DCDC Charger. Note that VRM Portal will needs an update to work properly with this.
  • GUI: Update translations


Changes v3.20~48 & v3.20~49

  • Marine MFD HTML5 app: better support for smaller/low screens
  • PV Inverters -> SMA TriPower: work around for an issue in the recent SMA firmware update 3.04.16R.
  • RS: Fix alarm configuration of short circuit alarm. Configuration changes were not written to the device.


Developers / under the hood

  • FlashMQ is updated from v1.8.4 to v1.9.1, to fix it running away on certain DNS failures.


Changes v3.20~47

  • Change the page in the devicelist for the Orion XS, use the term Output rather than Battery, since voltage shown there is the voltage at the Orion XS terminals rather than the (optionally-) corrected or sensed battery voltage, and similar small changes.
  • Better handle the situation that the Aux input setting of a connected BMV/SmartShunt is changed from Temp or Voltage input to None. By invalidating the reading.


Changes v3.20~46

  • Remove ESS AC import and AC export current limit settings, which were introduced in v3.20~38. They will be added back after the official release of v3.20, which is expected a few weeks from now.
  • RS: Add tracker names to the daily history page.


Changes v3.20~44 & ~45

  • GUI: Reword online update options to make it more clear. Latest release became Official release and Release candidate became Beta release.
  • ESS: fix bug where the Minimum SOC was not observed in systems without a managed battery (introduced in v3.20~39). Thank you @PF_1 and others!
  • Generator start/stop: add a new setting called "Generator stop time". The mechanism used to allow for up to 15 seconds for the generator to stop, after receiving the stop signal. But in some cases that proved to be too short. See this thread for details.
  • Generator monitoring:
    • add DSE 6120 MKIII model
    • remove Comap Engine/Load as it is not consistently available in all installations and causes issues.
  • RS Series:
    • add more error descriptions and alarms that have been added to RS firmware recently.
    • fix bug that could cause timeout during remote firmware update (max time increased from 60 to 90 seconds).
    • add custom names for RS products to VRM (more work is required before its actually visible!)
  • Ruuvi tags: add low battery alarm to VRM (more work is required before its actually visible!)
  • Fix inverter/charger notifications while booting - thank you @beat!
  • Update translations (more updates are coming before release of v3.20)


Changes v3.20~43

  • MPPT RS: add custom tracker names. Note that this is work in progress, having them on VRM is now the last missing piece.
  • GUI / Lynx Smart BMS
    • Add missing BMS Error #36: ATC/ATD failure
    • Fix rendering issue on diagnostics page
  • gui-v2
    • Fix certain the Settings -> Display & language menu not loading as well as a crash when opening Settings -> I/O -> Digital inputs. Thank you for the continuous feedback on this; it turned out to be various issues left and right; we're certain that the above are fixed and still continue testing.
    • Fix various bugs in Tanks/Sensors
    • Performance improvements.
  • Orion XS: increase firmware update speed, applies to remote firmware updates, done over VRM.

Venus OS Large

  • Fix issues with node-red flow; now included version of node-red-contrib-victron is v1.5.10. thank you @beat for reporting.

Changes v3.20~42

  • Multi RS: Properly visualise three phase systems on gui, gui-v2 and VRM.
  • gui-v2:
    • Fix crash in WebAssembly due to Qt Dialog bug
    • Fix crash in VeQItem when QML sets invalid uid
    • Fix firmware version display bug
    • Fix battery details page bugs Fix generator page "total run time" display bug;
    • Fix generator page auto-start uid bug
    • Fix NumberSelectionDialog stepSize bug
    • Fix Global.evChargers.power value synchronization
    • Disallow pushing components with errors to PageStack
    • Add "time to service" value to generator page
    • Change order of control cards
    • Show EVCS current value on Overview if only one charger
    • Remove unnecessary translation ids
    • Implement image provider for monospaced digits

Changes v3.20~41

  • Can-bus BMS batteries: add debouncing to warnings and alarms to fix a rare spurious notifications.
  • Orion XS: add shared current sense to DVCC. When enabled, the Orion uses that to stop charging / switch to float when battery is full. DVCC function is now complete (SVS, STS, SCS)
  • N2K: add support for reading generic alternator data. Reauiremenrs: N2K device class=35 (electrical generation), function=141 (DC generator), PGN 127506 DC Details with DC type set to alternator, PGN 127508 Battery Status (voltage, current and temperature). Works with the Curent monitor of Across Ocean Systems.
  • RS: Add support for custom tracker names. Requires an upcoming VictronConnect version to set them; and does not show in VRM yet.
  • RS: add passthrough mode
  • RS: add AC disconnect reason
  • RS: Log MPP mode per tracker (on maximum powerpoint vs limited)

Changes v3.20~38, ~39 and ~40

  • ESS:
    • Show the ESS grid setpoint also when ESS mode is set to Keep Batteries Charged. The grid setpoint is still followed for feeding AC- and DC-coupled energy into the grid, this allows setting the setpoint without first changing to Optimised. Thanks to Warwick C. for reporting
    • Added the option to make an ESS system limit the AC current at the grid meter; see the two new options, "Limit system AC import current" and "Limit system AC export current" in the Settings -> ESS menu. Note that that is work in progress, its known to not yet limit export when having a DC-coupled system and feed-in enabled. Other details:
      • Works for both single- and three phase systems
      • The configured limit is applied to each phase
      • This new setting only works if there is a grid meter in the system. For systems without a grid meter, use the AC input limit setting in the inverter/charger in combination with the Peak shaving option in the GX. See this blog post for more information.
      • The ESS setting "Minimum SOC (unless grid fails)" defines down to what percentage the battery capacity will be used by the system for ESS and Dynamic ESS. The rest of the battery capacity, ie. when the battery state of charg is below that threshold, is reserved for when the grid fails as well as this new feature - peak shaving.
  • gui:
    • update translations
    • Make the temperature calibration parameters accessible to "user and installer", so that users and installers can now manually correct and optimise the temperature readings of the Cerbo and Ekrano built-in temperature ports.
  • Ekrano GX: fix the display showing garbled data when cold (freezer temperatures)
  • Color Control GX: fix VRM instance number of Multis and Quattros. Bug was introduced in v3.20~37.
  • VRM:
    • Update data-paths for Orion XS DC/DC Converter
    • Transmit generator service interval to VRM
  • gui-v2-beta
    • Minimize QML module loading and register all qml types at compile time

    • Fix vecan/rvc and generator settings pages when used in a browser (WASM)

    • Add support for ARCO Zeus alternator controller

    • Avoid runtime theme lookups, generate constants at compile time

    • Fix position selection in PV inverter settings

    • Fix bug in 'Settings -> Ethernet' page when used in a browser (WASM)

    • Use veutil for unit conversions and drop custom implementations

    • Fix display of battery '100%' SOC in Brief/Overview pages

    • Fix naming of 'DC system' devices to not be called 'DC Generator'

    • Show temperature inputs in Levels page regardless of /Status; fixes missing temperature inputs.

    • Device List: add settings for inverter, temperature, meteo, motordrive, pulsemeter, digitalinput

    • Show proper error descriptions for BMS, charger and wakespeed errors

    • Fix issue where combo box popup does not open

    • Show individual (not combined) tracker power in solar device list

    • Load qml files from the file system, not from compiled resources (pending CI integration to enable custom QML editing on device)


Venus OS Large


Developers / deep under the hood:

  • Add wireguard-tools as optional package (opkg) as well as enable the wireguard driver in the kernel.
  • update dunfell, fixes CVE-2023-48795 and others


Changes v3.20~36 and v3.20~37

  • gui-v2-beta
    • Flatten theme with strongly-typed theme object+properties
    • Allocated fixed-width geometry for QuantityLabel values
    • Construct brief page monitor panel on-demand to reduce CPU usage
    • Register singleton types at compile time with QML_SINGLETON
    • Consolidate AC input widgets on Overview Page into one
    • Only read data from the active AC input data source
    • Add Inverter/Charger page to DeviceList
    • Improve UI for generator start/stop flow with intermediate dialogs
    • Fix bug in Units::scaledQuantity()
    • Fix missing RPM units in an AC input setting
    • Fix various bugs in generator settings


Venus OS Large & Developer related:

  • Prepare to support remote access to Node-RED dashboard2, aka the new Dashboard solution by Node-RED, which is announced as the successor as the well known Node-RED dashboard. More about the new version here: https://dashboard.flowfuse.com/about.html. I've briefly looked for a page that explains nicely what the main improvements are, but haven't found one yet.
  • Dynamic-ESS: fix a bug in a system health monitoring parameter. (last reported time slot could not be in the future).


Changes v3.20~35

Venus OS Large & Developer related:

  • Node-red-contrib v1.5.4 -> v1.5.7
    • this was already announced in v3.20~34, but wasn't included then.
  • dbus-flashmq various changes, mostly required for finishing some user settings pages in the gui-v2 project:
    • Adds support for /Identifier to supplement /DeviceInstance in cases there is more than one of something.
    • Fixes writing arrays as values, including null, which becomes an array.
    • Fix dealing with signals that don't contain the values of paths
    • Fix publishing all known item data on read/getvalue
  • signalk-n2kais-to-nmea0183 1.3.1 -> 1.4.0
    • feature: add option to send self data (note that this was already announced in the change log for v3.20~20, but then wasn't included)


Changes v3.20~33 -> v3.20~34

General

  • Add support for the new Orion XS 12/12 50A DC DC Charger; including DVCC, shared temperature sense and shared voltage sense.
  • VM-3P75CT Energy Meter: add position setting for PV Inverters. Requires latest energy meter firmware; which is included per VictronConnect v5.101. (also backported to v3.14)
  • Improve robustness of BMS-Can port in the Cerbo GX by making it auto recover from a CAN-Bus bus off state. Until now a power cycle was needed. To get it into that state, the communication wires would for example need to get shorted, or data at the wrong baudrate would have to be sent on the same network. Note that the same
  • Fix (most likely extremely) rare bug in the energy counters, used for the kWh graphs on VRM, in related to VE.Bus systems. They could get stuck; not anymore; we've seen this once on a support case. Existed since 2015.
  • Fix remote firmware updates for EV Chargers, introduced in v3.20~33.
  • Fix an non-existing "Digital input 0" showing up sometimes in the configuration menu.


DVCC

  • Add support for FinDreams battery (includes forcing DVCC on)
  • Add support for Weco battery (includes forcing DVCC on)


Modbus-TCP

  • Add registers for setting the boost factor, PowerAssist & Inverter output voltage settings for VE.Bus devices (Multis, Quattros). Of use in certain advanced hybrid generator systems to further optimise them (automatically).
  • Add registers for Orion XS DC-DC Charger


Node-RED

  • node-red-contrib-victron 1.5.4 -> 1.5.7
    • New nodes: input-dcdc / output-dcdc, supporting the new Orion XS
    • Show changed values under the node, instead of just "(dis)connected" or "ok"

    • Add total power to grid meter

    • Remove solar charger from relay control


Advanced/developers

  • Add Ignore AC in option for Multis. The same was already available for Quattros. (com.victronenergy.vebus /Ac/Control/IgnoreAcIn1)
  • MQTT: Support GetValue on sub-paths (super nodes in the dbus tree). It will publish all topics of items below it.
  • Add the qt6/qtshadertools to the SDK


gui-v2-beta:

  • Make animations more efficient: decreases CPU load
  • Don't aggregate AC current in multiphase systems
  • Remove unnecessary DC services and loads from DC inputs aggregator
  • Add DC services and loads to Device List, add DC Loads drilldown
  • Replace BatteryWidget charging animation by one that needs less CPU load
  • Improve translation file handling
  • Load faster in the webbrowser (MQTT: transition to Ready state after receiving full_publish_complete)
  • Fix bug in modal dialog show/hide
  • Fix bug in component URL handling
  • Fix bug related to WLAN connection
  • Show per-tracker entries in solar drilldown list
  • Ensure solar history dialog appear


Changes v3.20~31 -> v3.20~33

  • Replace Mosquitto by FlashMQ. FlashMQ was already used for all local MQTT traffic (HTML5 app and gui-v2-beta), and now it is also used for all remote traffic (VRM Portal dashboard, Remote firmware updates); In normale operation, this changing nothing. More on a developer level this reduces CPU usage and opens up the road to further remote features, most importantly running gui-v2-beta remotely over VRM.
  • ComAp: Fix Runtime hours display which was off by a factor of 60 (also released in v3.13)
  • DSE: fix engine speed reporting
  • DSE: fix 7xxx MKII support (also released in v3.13)
  • PV Inverter integration (also backported to v3.14)
    • Fix issues in detecting newer models of Fronius inverters that caused them to be recognised as single phase inverters rather than what they are: three phase; when not using the Sunspec/ModbusTCP type of integration (which is disabled by default).
  • HTML5 app
    • Add Ukrainian language + update various translations.
  • Dynamic ESS: various improvements.


Node-RED:

    - Custom output node: ability to set `msg.path` as well
    - Add new paths for existing nodes:
      - input-vebus: `/Alarms/BmsPreAlarm`, `/Ac/State/RemoteGeneratorSelected`, `/Dc/0/PreferRenewableEnergy`
      - output-vebus: `/Ac/Control/RemoteGeneratorSelected`, `/Dc/0/PreferRenewableEnergy`
      - input-solarcharger: `/Pv/[0-3]/MppOperationMode`
      - input-settings: `/Settings/CGwacs/BatteryLife/SocLimit`
      - input-inverter:` /Pv/[0-3]/MppOperationMode`
      - input-genset: `/Engine/OilPressure`
      - input-generator: `/ServiceCounter`
      - output-generator: `/ServiceCounterReset`
      - input-meteo: `/ExternalTemperature2`
      - input-multi: `/Pv/[0-3]/MppOperationMode`
      - output-settings: `/Settings/Pump0/AutoStartEnabled`, `/Settings/Pump0/Mode`, `/Settings/Pump0/StartValue`, `/Settings/Pump0/StopValue`
    - Updated documentation


Changes v3.20~28 -> v3.20~30

  • ComAp generater integration: add support for tank sensor on the ComAp
  • Add support for new Mopeka sensor models: Universal Pro, TD40, Pro 200 and Pro+ (also released in Venus OS v3.14)
  • Dynamic ESS improvements
  • Security updates for many used components (OS level)


Changes v3.20~27

  • DSE generators: add showing tank data.
  • Stability fix for Energy Meter, EVCS, CoMap, DSE and other modbus connected devices. Fixes occasional lock-ups.
  • Small Dynamic ESS improvements.
  • FlashMQ improvements
    • Publish N//full_publish_completed after full publish.
    • Add min/max to the json.
    • And more internal changes.
  • Further harden resize2fs and remount-rw scripts. Those scripts are used by tinkerers / people modding the GX device.


Changes v3.20~23 -> 26

  • Further updates to boat/motorhome 2 demo


Changes v3.20~22

  • Update boat/motorhome 2 demo


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

  • Add Ukranian language
  • Fix bug related to some SolarEdge inverters, bug was introduced per v3.20~18; thank you to those that quickly reported this! (also backported to v3.14)
  • Add support for new SMA TriPower X PV-inverters, and possibly even more models. All PV-inverters that use the newer Sunspec models in the 700 series (IEEE1547) will now be supported. Limiting, aka Zero-feedin is not (yet) supported on any of these. (also backported to v3.14)
  • FlashMQ stability improvements
  • Update Boat/Motorhome demo 2; it includes an alternator, and a few tanks and temperature sensors.
  • RV-C: Fix tank out DGN
  • Dynamic ESS: fix repeated charge/discharge pattern for batteries using the (third part) dbus-serial driver. This driver reports SOC as a floating point number, but jumps over some values, sending DESS directly from charge to discharge and skipping idle. New hysteresis implementation ensures that idle is always entered.


Developers:

  • fix /etc/fstab being empty after remounting the rootfs as writable, issue on RaspberryPis as well as Cerbo with large image.


Venus OS Large

  • Update signalk-venus-plug from v1.33.1 to v1.34.0


Changes v3.20~18

  • Add support for read-out of KACO PV Inverters. Note that Zero feed-in is not supported at the moment (also backported to v3.14)


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

Note: due to a possible issue, see discussion below, we have disabled the online updates for all raspberrypi models. Downloading the .swu file and then manually installing it is still possible.


  • Various Dynamic ESS related improvements:
    • Remove the separate DESS MinSoc setting. DynamicESS now uses the ESS MinSoc.
    • Stop showing "Low Soc" errorcode when DynamicEss reaches the target SOC.
    • Fix bug that limited solar chargers in relation to the target SOC. Rather than limiting, get there early, and power loads or feed excess into the grid.
    • Implement restrictions for the German market:
      • Two modes are supported: Disallow export from battery to grid, and Disallow import from grid to battery.
      • When converting from DC to grid is disallowed, export-power is limited to local consumption, plus DC-coupled PV (which is green).
      • When converting from grid to DC is disallowed, import-power is limited to AC-coupled PV.
  • Fix bug where DVCC user charge current limit is ignored with VE.Bus BMS. Introduced in Venus OS v3.00.
  • Managed batteries: Detect WeCo battery
  • Re-add the Marine MFD HTML5 app, including various improvements already announced for v3.20~14 (but not visible then due to a mistake in the build):
    • Fix missing data.
    • Fix power conversions (W/kW) for generators.
    • Fix inconsistent energy values between pages.
    • Fix tank warning colors.
    • Fix rounding of device component values.
    • Fix issue where values were shown while the device was unplugged/not running.
    • Remove active current limit from inverter/charger on system overview.
    • Remove artificial Charged state from batteries.
    • Make charger and inverter/charger input current limit adjustable in steps of 0.5A.
    • Show the same power unit for multi-phase devices.
    • Made modals responsive
    • Remove the word "overview" from the energy detailed page.
    • Add Ukrainian translations.

  • A few more improvements on the Marine MFD HTML5 App:
    • Multi phased data visual alignment
    • Fix value overflows
    • Lock description translations
  • Add support for the second temperature sensor on newer versions of the IMT-SI meteorological sensor
  • DSE Gensets:
    • hide menu entries that are not relevant for DSE gensets.
    • Add "Number of engine starts" item for DSE gensets.
  • VRM Logging:
    • Transmit EV Charger energy data
    • Transmit a few Dynamic ESS parameters
  • EV Chargers:
    • Fix TCP connection remaining open for disabled devices (this is an improvement introduced earlier during v3.20 development which had a bug, fixed now).


Changes v3.20~12 and v3.20~14

  • Add DSE generator error messages
  • Fix MultiPlus II 2x120V device screen shows large negative current on AC-Out L2 when inverting or with single phase grid connection (also released in v3.12)


Development / internals:

  • Fix issue for certain electric drive / motor controllers causing the device to not show on the device list.

  • Fix packaging of Python multiprocessing package


Changes v3.20~11 and v3.20~12

  • Support additional DSE generator models. The complete list is now:
    • 4510 MKII
    • 4620
    • 6110 MKII
    • 7310 MKII
    • 7410 MKII
    • 7420 MKII
    • 8610 MKII
    • 8660 MKII
  • VM-3P75CT: update minimum required firmware version to v1.03

Developers

  • Update Qt6 to QT 6.5.2


Changes v3.20~10

  • Fix issue that caused the energy meter its role setting to get lost and return to the default. The issue affected systems having energy meter setup to measure output of a PV Inverter, a grid meter or an AC load. We recommend to double check the system, any system that has ran v3.20~9 for a while, might need this setting to be restored manually. Issue was introduced in v3.20~9


Changes v3.20~8 and v3.20~9

ESS:

  • Increase limit of 32.7kW per phase limit to 138kW. (also released as Venus OS v3.1x)
  • Fix problem where the recently introduced setting "Self-consumption from Battery" to "only critical loads" did not work correctly if a Multi on L1 was compensating for loads on other phases. (also released as Venus OS v3.1x)


Managed batteries:

  • Add menu entry showing module-level alarms. Note that there are no batteries that support this yet. (also released as Venus OS v3.1x)


Quattro-II

  • Add support for new Error 128 as well as transmit more diagnostic data to VRM. (also released as Venus OS v3.1x)


EV Charger and VE-Energy Meter

  • Add enable/disable switch for EV Chargers and VE-energy meters. Defaults to disabled: from now onwards, when installing an EV Charger with a GX, the EV Charger needs to be enabled in the GX. Any EVCS already seen in a prior GX firmware version will be enabled automatically. (also released as Venus OS v3.1x)
  • Add option to manually add VE Energy Meter, mostly intended in case the meter is not on the same network, which might happen in systems having a more complex ethernet/IP network. (also released as Venus OS v3.1x)


Energy Meters, SmartShunt and Inverter and Multi RS:

  • Fix issue in reporting to VRM that happens in some cases. Installing the new version will solve the issue automatically.
  • Note that there might also be a bug in v3.20~9, that makes systems with an energy meter configured to measure a PV Inverter change the role by themselves to Grid, which we are working on.


RV-C: (also released as Venus OS v3.1x)

  • Fix bugs in the VE.Bus related DGNs:
    • Fix external control state in CHARGER_STATE DGN.
    • Improve CHARGER_STATE in case the charger is disabled or mains is not present.
    • Improve INVERTER_STATE in case the inverter is disabled or cannot invert due to low battery.
  • Fix sending of DGNs of the main interface (the GX itself). Broken since VenusOS v3.00. Mostly harmless, since this only contains GX firmware version and similar data.


Venus OS Large

  • Update Signal K Server from v1.46.3 to v2.3.0
  • Update NodeJS from v1.18.16 to v1.18.18


Changes v3.20~5, 6 and 7

  • Fix Ekrano GX remote firmware update issues with VE.Can products: the remote firmware update mechanism did not accept having two ports configured with the VE.Can profile, which the Ekrano has by default. (Officially released in v3.11)
  • Add support for DSE 4620 genset controllers (this connects via ModbusTCP, just like ComAp. More details, as well as more models, will follow later). (also released as Venus OS v3.1x)
  • Various fixes related to Generator start/stop (also released as Venus OS v3.1x)
  • Show a warning if the firmware for the MK3 controller built into the GX device has not been updated yet. For details, see the v3.00 blog post. (also released as Venus OS v3.1x)
  • Dynamic ESS:
    • Fix problem with oscillation around the Dynamic ESS minsoc point. Once the system reached the minimum SOC, it would go back into normal ESS mode. This could cause the battery to start recharging, causing oscillation. Now we remain in DESS mode, but we go to idle, and set the ErrorCode accordingly (Low SOC).
  • Solar and wind priority: fix a small bug around charge battery to 100% visualisation. (also released as Venus OS v3.1x)


RaspberryPi:

  • Add files for the RaspberryPi 3a Plus model. Thank you @Head!


Changes v3.20~3 and v3.20~4

  • Fix various bugs in the gui related to generator start/stop, all regressions introduced per v3.10; and all also released officially as v3.11:
    • Fix generator start stop reported run time
    • Fix an info toast message is not shown when setting service timer
    • Fix bug where FischerPanda gensets sometimes lose the engine values (Oil Pressure, RPM, etc)
  • IMT Irradiance sensors: Log the value of second temperature probe to VRM.
  • Dynamic ESS:
    • Fix bug where the maximum system feed-in setting was exceeded during automatic DynamicESS use


Venus OS Large

  • Victron Palette, aka node-red-contrib-victron, v1.5.0 to v1.5.2
    • Add option to show the values in the flow. Instead of OK and Connected. A very nice improvement, see below screenshot. Activate in the configuration node.
    • Update dependencies
    • Send only changed rounded values
  • Node-RED: update from v3.0.2 to v3.1.0.


The 23.8 in below screenshot is what is new in Node-RED per Venus OS v3.20~4:



Changes v3.10 -> v3.20~2

  • Re-add HTML5 app. Changes compared to the previous version:
    • Increase performance / response speed
    • Fix tank levels showing NaN sometimes
  • Remote Multi/Quattro firmware updates: fix bug where the Multis and Quattros don't show on on the VRM firmware update device list if the mk3 firmware has not been upgraded. (also released as Venus OS v3.1x)
  • IMT Irradiance sensors:
    • add support for second temperature probe on devices with two temperature probes
    • add support for IMT sensors running firmware versions older than v1.53.
  • VE-3P75CT meter: increase ESS speed slightly
  • Update FzSonick batteries product name


Developers:

  • re-enable FlashMQ



Previous posts on v3.20:



Highlight #1: Completely renewed Marine MFD / HTML5 App

1685824333731.png

(click for large)


And here a more extended system, with more tanks, and more energy sources:

1685824162825.png

(click for large)

Note that above two screenshots are taken from the design files, it might differ a bit from actual implemenation.

These are screenshots taken from the new implementation, but there I'm not able to now have them embedded in actual look on a marine MFD like above:
1685821774230.png


And light mode:

1685821833984.png


And for comparison, here is a screenshot of the old version:

1685823688829.png



Highlight #2 - New user interface, gui-v2

There is a new page, called Brief:

1700597863477.png


The button on the upper right opens and closes a side pane for it:

1700597875345.png


The overview page has been redesigned as well. And the idea behind it is different. Rather than an (almost) correct electrical diagram, its more a functional one. With all generation on the left, conversion & storage in the middle, and consumption on the right.

1700599761868.png


Above is the dark mode. There is also a light mode:

1700597940491.png


And its no longer necessary to go deep into the Device list to, for example, start and stop the generator or modify the shore current limit. Day to day controls are now accessible using that small button on the top left. Here is how those controls look:

1700597981524.png


Further details on gui-v2:

  • It is still in beta, porting all the features and functions of the old UI over to the new one is an enormous task, and I expect that to take several more months. Our internal deadline is March 2024.
  • The gui-v2 will not be part of the official v3.20 release. After we've released v3.20, planned for February, beta testing of gui-v2 will continue in v3.30.
  • Beta testing is best done using a browser, http://<ipaddress>/gui-beta. And you need to enable the MQTT on LAN (Plaintext) setting for that to work.
  • More screenshots as well as further instructions and a list of known issues is here:

    https://bit.ly/gui-v2

  • Feedback is very welcome, especially positive feedback of course ;o). Before posting issues, please do check the known limitations list in the slide deck behind that bit.ly link. We're well aware that not all works yet.


Venus OS
15 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.

Good day all, per just now, v3.20~45 is available is a beta version. Various fixed and a few minor additions.
2 Likes 2 ·
Hello all, per just now v3.20~46 is available as a beta version. Small changes, and one “step back”: we’re preparing for official release, and have removed the recently added ESS import and export current limit settings, as those new features and algorithms need more testing first.
2 Likes 2 ·
ojack avatar image ojack mvader (Victron Energy) ♦♦ commented ·
Do you guys never have to sleep ;-)
0 Likes 0 ·
mvader (Victron Energy) avatar image mvader (Victron Energy) ♦♦ ojack commented ·
unfortunately sleeping can't be skipped! ;o)
0 Likes 0 ·
Good morning, per this morning we released v3.20~47 for beta testing. What has changed are some entries in the Orion XS page.
2 Likes 2 ·
Hello all!


Per just now we have made v3.20~51 available as a beta version.

The change is only one small fix related to the Orion XS, see change log.


Unless new issues show up, we're planning to release v3.20 officially still this week. (and as said before, gui-v2 is not part of that, beta testing of that resumes with v3.30 beta testing).




2 Likes 2 ·
Good day, per just now is v3.20~42 available. One long overdue fix: properly visualise the Multi RSes when in a three phase system.


And change is various fixes in gui-v2; including that the display got locked up / showing multiple pages on top of each other.

1 Like 1 ·
Hey all, per just now, v3.20~43 is available. Mostly to fix the various reported regressions in gui-v2 and Node-RED palette
1 Like 1 ·

Hello all! Its done, v3.20 was released officially just now.

You can read the announcement here: https://professional.victronenergy.com/news/detail/236/.

Thank you for all help and feedback! Next up is beta testing of v3.30, which I expect to start in a few days.

1 Like 1 ·
Hello! Per just now, a new beta version to test: v3.20~49 .


Especially with regards to the HTML5 app it would be nice to hear confirmations from a users that all works well on their MFDs!

0 Likes 0 ·
Good morning! Per just now, v3.20~50 is available for beta testing. Changes to Orion XS and added translations


Feedback welcome, but no need to report issues on gui-v2.

Our focus right now is on getting v3.20 ready for official release - and gui-v2 is not part of that.


have a good weekend!


0 Likes 0 ·
Juha Tuomala avatar image Juha Tuomala mvader (Victron Energy) ♦♦ commented ·
Could you please make the "firmware update available" visible via Modbus? I could then show it in Home Assistant which I see much more frequently than Cerbo's console. If you do, please add version numbers and URL to release notes whatever also, those will make it even better.
1 Like 1 ·
mvader (Victron Energy) avatar image mvader (Victron Energy) ♦♦ Juha Tuomala commented ·
Hi, not any time soon I'm afraid.
1 Like 1 ·
Juha Tuomala avatar image Juha Tuomala commented ·
  • Beta testing is best done using a browser, http://<ipaddress>/gui-beta. And you need to enable the MQTT on LAN (Plaintext) setting for that to work.

This stopped working after today beta update. There is no beta gui anymore in language and display either. Am I missing something?

0 Likes 0 ·
Marc Elvery avatar image Marc Elvery Juha Tuomala commented ·
The new beta gui is not in 3.20 release version, so you have to wait until 3.30 goes in beta
1 Like 1 ·
58 Answers
thomasw-1 avatar image
thomasw-1 answered ·

Thanks, I can confirm, the visualization issue in beta-gui is fixed in 3.20-40 (see below previous issue).

However I realized: Ethernet menu now shows "State", but "State" is "unplugged" with a connected ethernet cable.


69207-1705846238936.png


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.

Good to hear its solved! That ethernet state is a known issue
1 Like 1 ·
thomasw-1 avatar image
thomasw-1 answered ·

Issue observed:
Root-Password cannot be set via beta-gui

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.

Yes, known issue.
0 Likes 0 ·
synker avatar image
synker answered ·

Hello,

on 3.20.40 nodered still 3.0.2

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.

Hi @Synker , that would be really strange; I see Node-RED 3.1.3 in both in the build logs and on a test system here that runs v3.20~40.


Please double check.

0 Likes 0 ·
ojack avatar image ojack mvader (Victron Energy) ♦♦ commented ·

I have 3.1.3 at 3.20~40

0 Likes 0 ·
synker avatar image synker ojack commented ·
sorry I made an error! I checked nodered version on signalk
0 Likes 0 ·
mvader (Victron Energy) avatar image mvader (Victron Energy) ♦♦ synker commented ·
ah that explains it. no problem and thanks for confirming back!
0 Likes 0 ·
kudos50 avatar image
kudos50 answered ·

Probably VRM, not 3.20 but just throwing it out here. If you have 2 chargers, from the looks of it, Venus is OK but VRM is mixing and merging information in the graphic. Not sure in which forum to put this:

image-25-01-2024-at-1604.jpg


2 |3000

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

kudos50 avatar image
kudos50 answered ·

Can you elaborate on the ESS grid limiting feature pls. I ran a quick test and noticed if I overload L1, the L2 multi starts balancing it out by consuming more from grid to prevent punishing the battery. But L3 is untouched.

Would be good to better understand the logic so we can help test using our probably rather unique individual setups :-)

11 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.

Hey @kudos50 yes will do. If only all those unique individual setups could be harmonized... ;o).


Here is a quick attempt, but to explain this properly needs a longer sit down behind the computer, which will have to be some later moment. For now, bear with me:

This new feature doesn't work by having one phase compensate the other. Its really individual per phase, and what it does is perhaps best explains as preventing that a main fuse blows due to over current.

For example, in case you set the import limit to 25 Amps, the inverter/charger(s) on that phase will make sure to reduce charging in case they'd otherwise draw more than that 25 Amps. Also knows as PowerControl. And taking that one step further, in case the total loads, minus solar, on that phase exceed 40 amps, it will PowerAssist = take power from the battery and push it into the system, to keep the current drawn from the grid to a maximum of 25 Amps. This allows using a smaller utility connection than what would normally be needed by just considering the loads.

Note that all this are that new features in the Victron world, when you look up PowerAssist you'll see we've had this for decades. But what is new here is to have it working with an external meter that is part of an ESS system.


0 Likes 0 ·
kudos50 avatar image kudos50 commented ·

In that case I think you have a bug. As my comment was not about how I thought it would work but what I observed during a quick test.

Once the whole family has cleared the house I can control variables a bit better and will re-run the test. Until then, fairly sure this is what I observed:

  • set limiting to 25A
  • note current consumption (3x2A heatpump)
  • charge 3-phase EV at 16A (makes 18A in total)
  • turn on cheap heater on phase 1, makes 24,18,18
  • slowly increase phase 1 only further using induction cooking
  • observe individual multi setpoints using modbus (37,40,41 on 227)
  • observe battery consumption in VRM
  • observe grid meter, doing 25, 23, 18

Battery was about 100~200W going up and down a little

Phase 1 multi was feeding in ~1300W by inverting

Phase 2 multi was consuming ~1300W by charging

Phase 3 was sitting idle

Maybe my bad so will re-run.

0 Likes 0 ·
mvader (Victron Energy) avatar image mvader (Victron Energy) ♦♦ kudos50 commented ·
Ok thanks.


What you need to observe is the current at the grid meter: that is what needs to be limited to 25A if you set it there.


And once battery is empty then its game over ofcourse. No more compensation aka peakshaving.

0 Likes 0 ·
kudos50 avatar image kudos50 mvader (Victron Energy) ♦♦ commented ·

My bad. corrected my post. This is what happened during the test. Picture and 1000 words and so...

Again, will test and see if I get the same results.

image-27-01-2024-at-1659.jpg

0 Likes 0 ·
kudos50 avatar image kudos50 mvader (Victron Energy) ♦♦ commented ·
Need to do it a third time as the graphs of grid setpoint end up completely different if you have a heavy load on AC-OUT as well. Did not have that in the first test.

But on the grid meter, the results are the same as in the first test. If phase 1 is exceeding 25A it starts inverting / feeding in on phase 1 from DC bus. But DESS seems to keep battery consumption minimal and the multi on phase 2 is starting to charge.

In other words, the graphics look different but from a grid meter perspective the outcome is the same. 25-23-18.

0 Likes 0 ·
kudos50 avatar image kudos50 mvader (Victron Energy) ♦♦ commented ·

3rd time. Without any heavy loads on AC-OUT. Did a few variations to show the following things:

  • all of the above still stands. So it prefers using L2 to help L1 via DC bus. Not battery
  • once L2 is running short as well it will pick from L3
  • once L3 hits 25A due to put it's remaining amps on the DC bus to help L1 and L2, battery will be punished a lot more
  • once overload on L1 stops, L3 will stop helping L2 and L1 takes over that role

Not sure if that is how it is supposed to work but man I'm loving this!!!

image-27-01-2024-at-1944.jpg


0 Likes 0 ·
kudos50 avatar image kudos50 mvader (Victron Energy) ♦♦ commented ·

@mvader (Victron Energy) I noticed you temporary pulled the import/export current limit feature to adjust the algorithm:

<CUT>

And once battery is empty then its game over ofcourse. No more compensation aka peakshaving.

<PASTE

Not so sure current observations are a bad thing. Taking power from battery to assist instead of first trying to consume it from grid on other phases means battery losses that we do not have with the current algorithm.

Can you share a little about the plans and about what Victron feels is currently wrong with the algorithm ?

0 Likes 0 ·
kudos50 avatar image kudos50 kudos50 commented ·

@mvader (Victron Energy)

~50 has been released and I'm still not sure if I can update or not. Can you please review my previous post about the new import/export limit ?

0 Likes 0 ·
mvader (Victron Energy) avatar image mvader (Victron Energy) ♦♦ kudos50 commented ·
Hey @kudos50


Yes, sorry. I missed that.


Import /export current limit settings are still out; we’ll put them back once we start beta testing v3.30.


Maybe already next week, and otherwise one or two weeks later.

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

There is nothing wrong btw; some features are missing, and since this is not part of v3.20; and code changes by taking it out, we took it out already.


I hope that makes sense :-)

1 Like 1 ·
kudos50 avatar image kudos50 mvader (Victron Energy) ♦♦ commented ·
Jup, makes total sense. Something about certain cities in Germany not being build in one day. I misinterpreted your comment about taking it out because more testing was needed.

Happy to continue testing once it's back in. Will stay tuned.

1 Like 1 ·
dajestia avatar image
dajestia answered ·

Big graphic problems on GX Touch with the new ui, it is unusable so. Even more serious problem is that now there is no way to return to the old ui because it does not allow you to enter the display menu. Entering instead in the new ui via web you can access the display menu, but then there is the option to change from new to old ui, just missing the entry. Luckily the firmware menu works and I managed to go back to version 3.14.

21 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.

fitmydashcam avatar image fitmydashcam commented ·

the visualization issue in beta-gui still exists for me in beta 3.20-40.

i cannot change back to the standard UI due to this.

There is also a lack of the Orion XS in this new beta-gui, although it appears in the device list for the old-ui.

0 Likes 0 ·
anthonya avatar image anthonya commented ·
I have the same problem on the GX touch. It is unusable. I was able to get to the Firmware screen and had boot to previous 3.14 firmware.
0 Likes 0 ·
clayfree avatar image clayfree commented ·
I'm having this same issue. Some screens are displayed on top of others. Unable to access the display menu to switch back. I'm also having an issue where the screen wants to dim but wakes itself up the the screen is constantly dimming and brightening. Thanks dejestia for the solution to revert back.
0 Likes 0 ·
mvader (Victron Energy) avatar image mvader (Victron Energy) ♦♦ clayfree commented ·
Hey all three @Dajestia , @anthonya and @Clayfree , that is strange, I can't reproduce that at all on my Cerbo + GX Touch 50.

Is there anything specifically that you do that causes that?

0 Likes 0 ·
clayfree avatar image clayfree mvader (Victron Energy) ♦♦ commented ·
The latest beta versions have a constant dimming issue for me. I usually set it to just stay on without screen timeout. So when the latest version loaded I went into display to adjust the timeout. I am unable to click on the display sub menu. I started checking other sub menus and that's when I got the screens laid on top of each other. I rebooted thecerbo 3 times with the same results. I only encountered this with -40, the earlier beta versions displayed fine except for the dimming issue. Worth noting I am on a 7" display.
0 Likes 0 ·
dajestia avatar image dajestia mvader (Victron Energy) ♦♦ commented ·

nothing special. I installed the 3.20-40, then went into the display menu and selected the new ui. Luckily I was able to access the fw menu and reload the fw 3.14.

0 Likes 0 ·
anthonya avatar image anthonya mvader (Victron Energy) ♦♦ commented ·
I've done nothing in particular.I have a similar issue to @Clayfree where I can't open the Display sub-menu and when checking other sub-menus I get screens overlaying each other making the display unusable. I had to do a reboot to get it back working. Luckily I was then able to go into the Firmware sub-menu and select 3.14. I am on a Touch 50 display.
0 Likes 0 ·
clayfree avatar image clayfree mvader (Victron Energy) ♦♦ commented ·
Just loaded and checked -42 and it still has the UI bugs.
0 Likes 0 ·
mvader (Victron Energy) avatar image mvader (Victron Energy) ♦♦ clayfree commented ·
Which ones @Clayfree ? The same as @fmac reported below an hour ago?


Can you otherwise add a screenshot or photo?

0 Likes 0 ·
dajestia avatar image dajestia mvader (Victron Energy) ♦♦ commented ·

same problem as @fmac, but on GX Touch 70

0 Likes 0 ·
mvader (Victron Energy) avatar image mvader (Victron Energy) ♦♦ dajestia commented ·
hey @Dajestia , reproduced in v3.20~42, and now solved per v3.20~43.
0 Likes 0 ·
fmac avatar image fmac commented ·

Hallo

On my Ekrano I get this :

Can't go back , can't change the screen

had to go back to 3.14

Its not a productive system, I am just building

0 Likes 0 ·
ohne-titel.png (295.2 KiB)
fmac avatar image fmac fmac commented ·

The problem is the site : VRM Online-Portal

if i enter this, the system gets crazy

1 Like 1 ·
fmac avatar image fmac fmac commented ·
New problem with 3.20.42 on Ekrano GX

Entering I/O and then Digital inputs, the gui restarts

Can't open Display&Language

on Remote Console both menus are working


0 Likes 0 ·
mvader (Victron Energy) avatar image mvader (Victron Energy) ♦♦ fmac commented ·

Hi, I reproduced the restart issue here as well, I’ll pass it a long.


> Can't open Display&Language


Reproduced here as well. Thanks!



1 Like 1 ·
mvader (Victron Energy) avatar image mvader (Victron Energy) ♦♦ mvader (Victron Energy) ♦♦ commented ·
solved @fmac , per v3.20~43
1 Like 1 ·
fmac avatar image fmac mvader (Victron Energy) ♦♦ commented ·
Hallo

This are working

But there's another issue :

Brightness setting is not working

Display off time also not working

on my Ekrano

Thanks

0 Likes 0 ·
fmac avatar image fmac fmac commented ·

Hello, I don't know whether the language switch should work

It doesn't work

If I select German, nothing happens for a long time

When I touch the screen everything stays in English

or today I had Dutch in it

It wasn't that easy to go back to English

despite it

good job

0 Likes 0 ·
gilli avatar image gilli commented ·
New to this. Hope this all makes sense and that I’m posting in the right place. Loaded beta 3.20 ~43 today on a Cerbo GX 50. After installing, set the display for the beta. Came up well and all settings and display options seem function. Decided to go back to standard display for comparison. That caused the screen to go black and freeze there. No response to touch. Seemingly “dead.” Tried rebooting Cerbo. Could see that the screen was responding (got lighter, but without any gui display, etc). But then screen went black and unresponsive to touch.


Ran out of time. Not sure what I should do next to get back to either a working beta screen or even reinstall the non-beta software. Suggestions?

0 Likes 0 ·
gilli avatar image gilli gilli commented ·

Follow-up to my post: The issue I rant into was self-created the problem, but happily it is now also self-solved. While in the beta gui, I tried to adjust the brightness on the light screen. I set it all the way to the left (dark) without success. I discovered what appears to be the known issue that display brightness isn't functional. After doing that, I failed to move the brightness slider back to the right, and I in fact totally forgot I had moved it. When I later reloaded the standard screen, it was black. I had no idea it was because the brightness setting (all the way to the right) now worked. I thought the screen was unresponsive and the Cerbo was not communicating with the Touch 50. They were probably communicating fine, but I couldn't see anything on the display and had no way to readjust the brightness without any screen image on the Touch. I figured it out what I'd done after pulling up the remote console on local network and changing the brightness adjustment.

Bottom line: No issue with the beta software, other than the known issue of the brightness adjustment not working. I did discover along the way that the beta version does not let the screen go to sleep. Not sure if that is also a known issue, so I'll mention it..

0 Likes 0 ·
Russell Brown avatar image Russell Brown gilli commented ·
Yup same brightness doesn't work and screen wont go to sleep.
0 Likes 0 ·
dutchsolarfreak avatar image
dutchsolarfreak answered ·

Hello,

100% battery state not fixed (yet)

1706207058049.png

1706207109330.png


1706207058049.png (36.5 KiB)
1706207109330.png (45.4 KiB)
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.

dutchsolarfreak avatar image dutchsolarfreak commented ·

<CTRL> <F5> did the trick :)

1706285811786.png

0 Likes 0 ·
1706285811786.png (147.1 KiB)
mvader (Victron Energy) avatar image mvader (Victron Energy) ♦♦ dutchsolarfreak commented ·
Sounds like we have an issue there, CTRL-F5-ing should not be necessary!
0 Likes 0 ·
dutchsolarfreak avatar image dutchsolarfreak mvader (Victron Energy) ♦♦ commented ·

FYI

I had to do this on multiple computers/browsers to get the 100% correctly showed.

On my iphone/chrome I had to manually reload the page as well. Just opening a new tab/session was not enough.

1 Like 1 ·
bohne avatar image
bohne answered ·

Hallo


es sollen die Batterie Spannungen von der Cerro an den Orion xs übersendet werden. Diese kann ich leider nicht feststelen . Bei mir wird nur die Temperatur übertragen. Muss da noch zusätzlich was eingestellt werden?

8 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.

Hi @Bohne , yes, DVCC Shared Voltage Sense is implemented for the Orion XS. Why do you think it doesn’t work?
0 Likes 0 ·
bohne avatar image bohne mvader (Victron Energy) ♦♦ commented ·
Weil die Spannung in der App nichtvangrzeigt wird bzw. die ist nicht identisch mit der aus dem DVCC
0 Likes 0 ·
Matthias Lange - DE avatar image Matthias Lange - DE ♦ bohne commented ·
Bin mir nicht 100% sicher, aber wird einfach so sein, das der Orion weiterhin SEINE Ausgangsspannung anzeigt, nicht die Spannung, die am Akku ankommt.

Im Hintergrund wird aber nach den DVCC Werten gearbeitet.

Das sollte man am dann sehen, wenn es Richtung Ladeschlussspannung geht.
Vorher macht es ja auch noch keinen großartigen Sinn.

1 Like 1 ·
mvader (Victron Energy) avatar image mvader (Victron Energy) ♦♦ Matthias Lange - DE ♦ commented ·

Hi both, I've checked the Orion XS manual, and this is what it says about the voltage shown in VictronConnect:


> Output voltage: Voltage measured at the output terminals of the device.


For the Solar Chargers its the same.


We've tested GX DVCC functions SVS, STS, and SCS, and they all work correctly.


Please confirm if that explains it and all works well now @Bohne

1 Like 1 ·
bohne avatar image bohne mvader (Victron Energy) ♦♦ commented ·
Hallo


Kann mich da nur für entschuldigen. Habe das so nicht in der Anleitung gelesen . Hatte gedacht das der Wert sich dann in der App auch ändert.


Gibt es vielleicht schon einen aktuelle modbus Liste ? Würde das gerne auch testen bzw benutzen . Danke für diesen super Service!

Mit freundlichen Grüßen

0 Likes 0 ·
bohne avatar image bohne mvader (Victron Energy) ♦♦ commented ·
Hallo


Ich habe es jetzt noch mal getestet . Ich habe die einganspannung auf 12.8 Volt gesetzt . Diese wird auch so begrenzt . Es wird aber nicht die reale Spannung der startet Batterie genommen die liegt bei 13,4 Volt . Gemessen und auch vom smartshunt so angezeigt . Lg

0 Likes 0 ·
mvader (Victron Energy) avatar image mvader (Victron Energy) ♦♦ bohne commented ·
Hi, Shared voltage sense works as Vsense for the output, not the input.
1 Like 1 ·
bohne avatar image bohne mvader (Victron Energy) ♦♦ commented ·
Hm das ist aber nicht so ideal. finde ich. Es würde Sinn machen auch die starte Batterie dort ein zu pflegen. Dadurch werden die spannungs Verlusten in der leitung kompensiert. Ds machen eigentlich alle anderen hersteller auch so.
-1 Like -1 ·
andrii-podanenko avatar image
andrii-podanenko answered ·

This time I caught it @mvader (Victron Energy)

After upgrade to v ~40, reboot, white screen of nothing. Went to gui-beta, reboot, all good

See https://youtu.be/QWEN_wdUqGw

Faced with this couple of times already

7 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.

andrii-podanenko avatar image andrii-podanenko commented ·

Issue with fitting 100% SOC is now fixed

Thank you

1000012977.jpg

1 Like 1 ·
1000012977.jpg (138.4 KiB)
andrii-podanenko avatar image andrii-podanenko commented ·

Issue with 4 MultiRS Dual Tracker now fixed

Thank you, back to a single one, which is correct

1000012975.jpg

0 Likes 0 ·
1000012975.jpg (120.2 KiB)
andrii-podanenko avatar image andrii-podanenko commented ·

Still issue exits with a lot of free property, unused, can't be scaled to viewport on mobile

1000012978.jpg

0 Likes 0 ·
1000012978.jpg (254.9 KiB)
mvader (Victron Energy) avatar image mvader (Victron Energy) ♦♦ andrii-podanenko commented ·
Correct, its not so high yet on the list
1 Like 1 ·
andrii-podanenko avatar image andrii-podanenko mvader (Victron Energy) ♦♦ commented ·
Got it, thank you.


Let's hope the world will land on Ekrano dimensions for all mobiles :))))). Just kidding.

0 Likes 0 ·
andrii-podanenko avatar image andrii-podanenko commented ·

Found error in gui2 @mvader (Victron Energy) after visiting Genset device menu

https://youtu.be/GW9gaJ5qhSg

0 Likes 0 ·
andrii-podanenko avatar image andrii-podanenko commented ·
Ukrainian translation in old gui updated - thank you.


No Ukrainian in gui v2...

0 Likes 0 ·
kampfiltis avatar image
kampfiltis answered ·

Hello,

i noticed the Problem "Dynamic ESS slow discharge on idle when reached target SOC" described here: Dynamic ESS slow discharge

This behaviour seems to be startet with this change:

Changes v3.20~15 -> v3.20~17
Various Dynamic ESS related improvements:
Remove the separate DESS MinSoc setting. DynamicESS now uses the ESS MinSoc.
Stop showing "Low Soc" errorcode when DynamicEss reaches the target SOC.

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.

pf-1 avatar image pf-1 commented ·

I have experienced a similar problem with Battery Live, although I do not use dynamic ESS.

The discharging of the battery does not stop and continues with normal discharge when the dynamic SOC limit is reached (Active SOC limit) although the BatteryLivfe state shows "Discharge disabled" and showing "ESS #1 and #2 on the old gui.

The problem did not exist with 3.20~37.

0 Likes 0 ·
h2009 avatar image
h2009 answered ·

Loving the GUI, will report back with my findings

Is it possible for us non-shunt users to get a time to go feature? @mvader (Victron Energy)


Thanks.

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.

Hey @h2009 , yes that would be nice indeed. Its on the list for "some day".
0 Likes 0 ·
palle avatar image
palle answered ·

In 3.20-40 my Orion xs charger has been renamed to Orion xs converter. In the VRM widget there is only data for what I think is a converter. In 3.20-37 it wasn't named converter and there was more data In the VRM widget.screenshot-20240126-190111-samsung-internet.jpg


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.

Hi yes, thats correct. Next week we’ll be finishing / correcting all that further.
3 Likes 3 ·
beat avatar image
beat answered ·

I upgraded from v3.20-34 to v3.20-40, and my NodeRed scripts are now broken by strange inputs from Victron inputs. In particular:

- EDIT: NO: "VE.Bus System" node for MultiPlus-II 48/5000/70-50, Output power phase 1 (W), to 3

- EDIT YES: ISSUE with: Energy Meter Power L1-L3 nodes (see reply below).

- "PV Inverter" node for Fronius Symo 12.5-3-M, Total Power (W)

give sometimes wrong outputs:

- For "Energy meter", a "W" is appended to round values only. E.g. msg contains number "11.8" correctly, but when the number is not floating, it contains string "12W". That ONLY if ALL 3 phases Power are round numbers!

- For "PV Inverter" node, it outputs string "0W" when the Fronius is in night sleep mode, instead of number "0". Maybe the same happens also for round watts values, wasn't around to debug during daytime.

Maybe other AC Watts values of other nodes behave same, but this is a backwards-compatibility break bug.

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.

Hey @beat thank you for the report, we’ll look into that.

(note to self: v#1205)

0 Likes 0 ·
beat avatar image beat mvader (Victron Energy) ♦♦ commented ·

Hey Thank you @mvader (Victron Energy) !


Here some precisions and screenshots:

Actually, it's not the MultiPlus that appends "W", but the the energy meter NodRed node, and only if *all 3 phases* have an integer (without decimals) watts-reading (correcting my message above with visible corrections).

Not sure if it's also the case on dbus, but it's really at the input of NodeRed, for Energy Meter and for AC Solar inverter Fronius. Here the screenshots of the 2 versions of readings (number/float, integer, and string with number without decimals and W appended (which is the bug):


Here the issue with the Fronius total power input:

Correct:

screenshot-from-2024-01-28-10-48-05.png

Wrong when a round value without decimals value (and when off in night mode, there is a "0W" string, instead of a number):


And here the issue with the Energy Meter input (Carlo Gavazzi):

Correct:

screenshot-from-2024-01-28-17-55-37.png


Wrong, but ONLY when ALL 3 phases have no decimals:

screenshot-from-2024-01-28-18-26-55.png


This was working in v3.20~34 but is broken in ~40 and ~41.

0 Likes 0 ·
Thank you for reporting. I managed to reproduce this and will make a new update, fixing the bug.


The bug was introduced in release v1.5.8 of node-red-contrib-victron.
1 Like 1 ·
beat avatar image beat Dirk-Jan Faber (Victron Energy) ♦♦ commented ·
Thank you!
0 Likes 0 ·
beat avatar image beat Dirk-Jan Faber (Victron Energy) ♦♦ commented ·

Confirming that this issue is fixed in today's 3.20~43 large with node-red-contrib-victron 1.5.10 included - Awesome fixing speed! Thanks! Now can remove workaround script, cool!

0 Likes 0 ·
mvader (Victron Energy) avatar image mvader (Victron Energy) ♦♦ beat commented ·

Good! Thank you for reporting it; right on time (we're getting ready to finalise v3.20 - without gui-v2 that is).

0 Likes 0 ·
andrii-podanenko avatar image
andrii-podanenko answered ·

Installed via VRM this time.

Caught again white screen of nothing after reboot

screenshot-2024-01-27-14-24-12-903-nlvictronenergy.jpg

https://vrm.victronenergy.com/installation/370388/share/c0152a83


Seems like it's only UI issue, all other operational, connection with VRM is working.


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.

andrii-podanenko avatar image andrii-podanenko commented ·
Did reboot via gui-v2 - all good now.
0 Likes 0 ·
andrii-podanenko avatar image andrii-podanenko commented ·

Gui-v2 is crashing on InteliLite device menu

0 Likes 0 ·
mvader (Victron Energy) avatar image mvader (Victron Energy) ♦♦ andrii-podanenko commented ·

Hey @Andrii Podanenko , we expect that that issue is fixed per v2.30~43. Can you confirm?

(crashing when entering the InteliLite device menu)

0 Likes 0 ·
andrii-podanenko avatar image andrii-podanenko mvader (Victron Energy) ♦♦ commented ·

Not crashing , thank you @mvader (Victron Energy) and the team!!!1706896622410.png

1 Like 1 ·
1706896622410.png (126.8 KiB)
Henry Pearson avatar image
Henry Pearson answered ·

Upgraded and liked the new GUI BUT not on a touch screen.

Mouse works but cursor does not show so it's a guess as to where it is. Will have to do a factory boot from USB as remote console stuck on "connecting".

Please allow mouse cursors to show for those of use without a touch screen.

2 |3000

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

pf-1 avatar image
pf-1 answered ·

Since version 3.20~40 BatteryLife no longer works. Both the "Active SOC limit" and the "Minimum SOC" are not taken into account.

Although the system recognizes that the battery is below the lower limit (BatteryLife state "Discharge disabled" and "ESS #1 and #2") the battery continues to discharge.

1706376954723.png


1706376954723.png (179.9 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.

Hi @PF_1 noted, thank you.


(note to self: v #1204)

0 Likes 0 ·
Hi @PF_1 , could you look at your email, I'm trying to contact you about this.
0 Likes 0 ·
derrick thomas avatar image
derrick thomas answered ·

Sorry if this is a known issue already covered, but I didn't find it. From the overview screen of the beta gui, if I click on the AC input panel I get a page that shows three phases with blank information on the phases. I have parallel MP2 2x120 connected to split phase input.

screenshot-20240127-123405.png



2 |3000

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

h2009 avatar image
h2009 answered ·

Custom RS name trackers coming. Love it.

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.

If you want to try it already, you can set them using VictronConnect App v6.00-beta-10

https://www.victronenergy.com/live/victronconnect:beta


1 Like 1 ·
CM avatar image CM mvader (Victron Energy) ♦♦ commented ·
Loaded
0 Likes 0 ·
juf avatar image
juf answered ·

Hi,


there are weather forecast at the new UI.
it would be nice to get this vis MQTT also.


Reagrds

2 |3000

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

ppr avatar image
ppr answered ·

Hi
I read that the new gui is not part of 3.20.
What can we expect? I am insanly waiting for such new look and feel. Is there any roadmap or milestone what needs to be reached before it can be expected? Nice to have a roadmap.

Best Regards, p

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.

Hi, not something I have in a easily shareable format, but on a high level its this:


- Alarms and notifications still need to be implemented.
- Security when running on local network.
- Various bugs and small missing features.


1 Like 1 ·
beat avatar image
beat answered ·

Btw, After almost every 3.20~xx upgrade i'm getting a "Low Battery" alert, and sometimes also a "Lost Connection to BMS" on the Cerbo GX from the Multiplus, when I switch them On from the GUIv1 (I'm switching them off for now during Cerbo GX upgrades).

The alerts clear within a second, so no biggie, but still a bip or two, and two to four alert emails from VRM.

It doesn't happen when switching on by Cerbo GX when not just after a software upgrade.

Note: It's a 3-phase system, and they all switch on simultaneously, so there might be a power surge, even though I've cabled them with 70 mm² and large industrial HPC fuses. btw, maybe it would make sense to switch them on with half a second delay, especially in 3-phas+/or parallel systems ?

5 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.

beat avatar image beat commented ·

Here the errors as they appear for a second on CerboGX (this is in v3.20~42, but it's since v3.20~34 at least):


victron-switch-on-errors-2024-01-31-00-41-49.jpg

1 Like 1 ·

Hi @beat,

Just to make sure I understand it correctly. When you update Venus you first switch off the Multi's through the GUI V1. Than update Venus, and afterwards switch the Multis back on. Correct?

What firmware version of the Multi's are you on?

The Multis have a 5 minute timeout time on the battery management frames. It seems that somehow they time out on your system during the update. I wonder what could take 5 minutes.

Do the alarms pop up directly after you switch on the Multis?

0 Likes 0 ·
beat avatar image beat jpasop (Victron Energy Staff) ♦♦ commented ·

Hi @jpasop (Victron Energy Staff) ,

- yes, correct, Multis switched off (sometimes way) before upgrade, and switching on (sometimes way) after upgrade.

- All 3 multis are on v508.

- This happened at each v3.20~34+ upgrade

- The Multis are off (by Venus off/charge/invert only/on soft config switch) between minutes and hours before the software upgrade (that doesn't seem to matter to reproduce)

- And if I turn on a couple of minutes after upgrade and reboot of Cerbo GX, I often see only one warning (battery low). If I turn on hours later, I often see both warnings like screenshot above, but it's not systematic to have both, but one at least is systematic, but only after upgrade

- The alarm(s) come on immediately (<5 seconds) after turning on multis (as always by Venus off/charge/invert only/on soft config switch), and on VRM notification mails, they clear immediately too.

- Once, I upgraded while multis were on, and no alarms came.

So it looks like a glitch or a missing anti-rebound or averaging. Nothing catastrophic, but a little annoying and alarming.


- EDIT: Yes, it's from GUIv1, remotely on local network.

0 Likes 0 ·
Hi Beat, Multi RS? Or a VE.Bus MultiPlusses?
0 Likes 0 ·
beat avatar image beat mvader (Victron Energy) ♦♦ commented ·

@mvader (Victron Energy) :

Wierd, wanted to edit, my reply disappeared (the forum layout is bezek on Firefox-latest-Linux).

I've a 3-phase VE.Bus Mulitplus II 3x5kVA 230V/400V~ 48V= system with many Pylontech batteries, cabled 2 by 2 via 120A HPC fuses to industrial 600A busbar

(btw, electrical safety advice: the Victron "1000A" busbar's 48V fuses have only....also 1000A surge-cutting capacity (!), and Pylontech specifies 20kA surge-cutting capacity, so it isn't conform to IEEE regulations, and had to return the Victron's and to custom-build one from ground up...)

0 Likes 0 ·
andrii-podanenko avatar image
andrii-podanenko answered ·

Installed v3.20~42

1.

> Multi RS: Properly visualise three phase systems on gui, gui-v2 and VRM.

I can confirm this is fixed now on my setup @mvader (Victron Energy) - in VRM, gui, gui-v2 ( tested all 3 )


2. No white screen of nothing after firmware upgrade this time

3. No phases on Grid meter card in gui-v2

1706541442901.png

4. Same issue when I open InteliLite menu

https://www.youtube.com/watch?v=GW9gaJ5qhSg

1706541586852.png

1706541600615.png


1706541442901.png (77.7 KiB)
1706541586852.png (178.0 KiB)
1706541600615.png (88.2 KiB)
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.

andrii-podanenko avatar image andrii-podanenko commented ·

Seems like AC charger stopped working in VRM on this firmware -

v3.20~42

1706545215314.png

Showing current in Venus gui 59A

1706545232817.png

Revert to v3.20~41 didn't help

No AC charger at all
1706545756942.png


Also, power usage calculation is not correct @mvader (Victron Energy)
I have to record a full video later this week to show the issue

0 Likes 0 ·
1706545215314.png (1.5 MiB)
1706545232817.png (137.1 KiB)
1706545756942.png (120.4 KiB)
mvader (Victron Energy) avatar image mvader (Victron Energy) ♦♦ andrii-podanenko commented ·
Hi @Andrii Podanenko , what charger is that King 5000 AC charger? A Victron charger?
0 Likes 0 ·
Thank you for the feedback, all noted!
0 Likes 0 ·
ojack avatar image
ojack answered ·

I just installed v3.20~42.

I still find the scaling of the graphics inappropriate. The graphic for the network fidgets across the entire scale even though the value only changes by +/- 50W and the 700W is only about 3% of the more than 22kW connected load. The graphics for solar also fidget with only +/-4W of up to 17kW of installed solar power.

The right scale for the load, on the other hand, only fills a tiny part and hardly moves. That could be more like 3% of 22kW, but it doesn't really help either.

Dynamic scaling might be better, but it should also be displayed. In addition, the graphics should be muted so that they don't fidget so restlessly. Maybe scaling and damping can be set as parameters in the menu.

1706556664654.png

1706556680884.png



1706556664654.png (54.1 KiB)
1706556680884.png (39.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.

broesel avatar image
broesel answered ·

Set Custom Tracker Names with VictronCOnnect Beta - but not showing up in VRM.
Where are they expected to be shown or is it not implemented yet for MPPT RS?

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.

Hi @Broesel , no not yet, soon. I'll make the change log a bit more clear on this.
0 Likes 0 ·
broesel avatar image broesel mvader (Victron Energy) ♦♦ commented ·
Thank you - but even in Cerbo i can nowhere see them. Correct?
0 Likes 0 ·
mvader (Victron Energy) avatar image mvader (Victron Energy) ♦♦ broesel commented ·
In gui-v1 you can see them, see the Multi RS or MPPT RS entry in the Device list.


In gui-v2 not yet; I think. Its on the list to verify.

0 Likes 0 ·
anthonya avatar image
anthonya answered ·

I have 3.14 installed which is currently running. The stored backup firmware is V3.20~40 which I was having problems with. I would like to test ~42. If I install V3.20~42 will this overwrite V3.20~40. I don't want to lose V3.14.

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.

derrick thomas avatar image derrick thomas commented ·
If you install v3.20~42 while running on v3.14 it will overwrite whatever is on the backup image. You will then be able to restore v3.14 backup.
0 Likes 0 ·
maxtosea avatar image
maxtosea answered ·
Love this. How can I access Remote Console on this?
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.

luka-renko avatar image luka-renko commented ·

Remote console from VRM finally works for me since ~47 via the following URL:

https://vrm.victronenergy.com/remote-console-2/xxxxxx

Replace xxxxxxx with your ID from VRM url.

0 Likes 0 ·
xavier-64 avatar image
xavier-64 answered ·

Hello,

My system on a Ekrano device Firmware v3.20~43, is following 2 Shunts. 1 connected to VE.Direct port and one other comming from an other system using the VE.can bus.

If I double click on the battery symbol from the overview screen, it to list the both SHUNT.... but impossible to go further with the details.

1706628537520.png

even clicking on one or the other of the SHUNT, it wont go into detailled view of the device.

But if I go to settings, device list

1706628674593.png

I can go inside SHUNT device details. (was also the case with previous versions of v3.20)

I also lose one of my MPPT 15 from the device list.

1706629131672.png


Xavier.



1706628537520.png (49.3 KiB)
1706628674593.png (37.6 KiB)
1706629131672.png (40.7 KiB)
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.

xavier-64 avatar image xavier-64 commented ·

second MPPT retrieved after a reboot !

1706630283850.png



0 Likes 0 ·
1706630283850.png (25.2 KiB)
bohne avatar image
bohne answered ·

Hallo gibt es schon eine neue register für die modbus schnistellen für den victron Orion xs ? oder finde ich den nur nicht in der aktuellen Liste.

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.

Hi @Bohne , yes, here are the ones that work with v3.20-beta versions:

1706916966438.png

1 Like 1 ·
1706916966438.png (43.1 KiB)
bohne avatar image bohne mvader (Victron Energy) ♦♦ commented ·
Super danke es Läuft einwandfrei . Danke für die Rückmeldung.


0 Likes 0 ·
beat avatar image
beat answered ·

The GUIv1 main page representation of the AC PV inverter, as well as of the DC chargers varies depending on a series of elements in 3.20~42 & ~43:

After reboot during night, while Fronius sleeps (configured, disconnected): it disappears:

(note also the different less clean representation of DC chargers here compared to below)

victron-1.jpg

The Fronius is configured grid-side (ACIN1) of the multipluses. But if the Multiplus II is in OFF state when the Fronius starts up in the morning (After a reboot), it is displayed on the output side, despite being configured to be in the input side:

vicron-2.jpg

Then, only after MultiPlus-II are turned on (from GX menu), the fronius is displayed correctly on the correct side:

vicron-3.jpg


Note: When MultiPlus are off, the flow from grid-side AC inverters is not represented correctly in VRM too.



victron-1.jpg (65.0 KiB)
vicron-2.jpg (73.3 KiB)
vicron-3.jpg (80.0 KiB)
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.

Noted, thanks. We'll look into this - starting with seeing if this is a regression in v3.20, and should thus block its release.
0 Likes 0 ·
mvader (Victron Energy) avatar image mvader (Victron Energy) ♦♦ mvader (Victron Energy) ♦♦ commented ·
Hi we checked, and same happens in Venus OS v3.14. So not a regression.


we’ll look at this later - thanks!

0 Likes 0 ·
beat avatar image beat commented ·
Update: Now, since 3.20~43, the Fronius AC PV inverter also disappears in the evening from the v1GUI homepage, when it disconnects for deep night sleep mode.

Maybe it's something I didn't notice before, but i don't think so. This part would then be normal expected behavior I guess. Leaving only the "wrong side" at startup left as a cosmetic non-release-blocking bug. ;-)

(btw something that's something that Venus could do as an option with MultiPluses, once there is no PV and batteries are at minimum SOC and no power backup is set ;-), as an active but idle 3-phase Multiplus system consumes around 50-100W).

0 Likes 0 ·
arnold-de-maa avatar image
arnold-de-maa answered ·

Thanks for the nice work! Please need 3 digit for the cell voltage. Cerbo GX Firmware v3.20~43, 2x pylontech RT1200G31

schermafbeelding-2024-01-31-101510.jpg


schermafbeelding-2024-01-31-101614.jpg


I think that pylontech not give information about the cell number.



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.

Christian Lindermann avatar image Christian Lindermann commented ·

Hi.

Cell Number shuould be there with Pylontech, under 3.13 it looks correct:


1706700542990.png


0 Likes 0 ·
1706700542990.png (23.8 KiB)
Alex Pescaru avatar image
Alex Pescaru answered ·

Hi developers,

@mvader (Victron Energy) , @Thiemo van Engelen (Victron Energy staff)

Don't forget, please, before release, about the fact that sometimes the data is sent on VRM during MPP scans and it really ruins the beauty of a good MPP graph... :-))

Many thanks!

mpp-graph.jpg


mpp-graph.jpg (94.4 KiB)
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.

Alex Pescaru avatar image Alex Pescaru commented ·

Hi @mvader (Victron Energy)

Looking closely at the internals of the system, I believe the solving of the above will be more elegant if the inverter itself, during those 5 seconds of scanning, to not publish anymore on dbus/canbus the trackers voltage and power and therefore the dbus values will hold the previous valid information.

Then the vrmlogger will just send a good and valid (previous) information to the vrm.

Sorry to keep coming with these ideas, for sure you know best... but I can't help it... :-))

Alex


2 Likes 2 ·
mvader (Victron Energy) avatar image mvader (Victron Energy) ♦♦ Alex Pescaru commented ·
Hey, i’ve planned this to look at a bit later.


Appreciated

2 Likes 2 ·
Alex Pescaru avatar image Alex Pescaru mvader (Victron Energy) ♦♦ commented ·

Hi @beat , @mvader (Victron Energy)

Maybe you know the below and Mathias can confirm if what I am saying is correct or not.
From what I know the inverter's firmware is sending over the canbus its internal data.
From canbus, the vecan-dbus daemon is processing and storing the data on Venus OS dbus.
From dbus all programs are taking the info and use it. Including vrmlogger daemon, which sends the data over internet to victron servers.
Now, you realize that individual information like instant voltage and current doesn't take much bandwith to be sent over canbus.
But a full swipe it will contain serious amount of data and sendind it over canbus to Venus OS can be difficult.
Let's think a little... Let's say 256 sampling point with 4 bytes per sample (2 words for voltage and current) will result in 1024 bytes (1K) of information.
At a speed of canbus of 250000 kbit/s it will take about 50ms to be transmited. Not much, but sometimes difficult when you must handle 8 bytes frames.
So implementing a feature for making available all the swipes can prove to be challenging.
Maybe something that will be executed on request could be more easily to do, because there the user acknowledges the operation.
Alex


1 Like 1 ·
beat avatar image beat mvader (Victron Energy) ♦♦ commented ·
Indeed, and it would be great to transmit, separately, to the dbus the full U/I "graph" of each swipe, so that e.g. NodeRED scripts could display, store or evaluate them. Swipe details contain precious information on the strings.

dbus and NodeRED integration into VenusOS large are one of the very best features of Victron VenusOS and are a key decision factor in the use of Victron products.

0 Likes 0 ·
anthonya avatar image
anthonya answered ·

Installed V3.20~43 and is more stable than ~40. However, in the device list on the gui-beta it does not show my Orion XS. If I revert to standard gui the Orion XS does show in the device list. @mvader (Victron Energy)

2 |3000

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

beat avatar image
beat answered ·

Not sure if this is a regression in Venus OS 3.20~43 or unrelated and in VRM, but on VRM, my custom widget for system-wide PV yield disappeared and I do not find a way to re-display the graph of AC+DC PV power. 100% sure it was there 2-3 days ago, but it disappeared. Having 6 victron PV chargers and one AC PV inverter, for a total of 5 roof orientations, seeing the graph of the sum of all PV sources was useful!

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.

Hey @beat , that was a bug in vrm, I’ve heard it was solved.
0 Likes 0 ·
beat avatar image beat mvader (Victron Energy) ♦♦ commented ·
Hey @mvader (Victron Energy) Thanks! Confirming that VRM bug is fixed too!

Hey, your guys fixed 2 minor bugs today that I reported yesterday! You guys rock, fixing some bugs faster than I report them :-) !

0 Likes 0 ·
CM avatar image CM mvader (Victron Energy) ♦♦ commented ·
How can we get the network total power bug in VRM fixed too , so it’s consistent with what’s actually reported by the mppts
0 Likes 0 ·
dajestia avatar image
dajestia answered ·

Screen timeout and automatic brightness control on GX Touch 70 still not working.

10 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.

Observed Issue:


Automatic Brightness and display shutoff after x seconds still does not work on GUI-2 on GX Touch 70

0 Likes 0 ·
anthonya avatar image anthonya commented ·

@mvader (Victron Energy) I can confirm that I get the same issue.

0 Likes 0 ·
clayfree avatar image clayfree anthonya commented ·
I can confirm this also in -43. In addition to the above mentioned issues my screen dims about 25% and slowly brightens again. This happens every 5 seconds. I'm using a GX touch 70.
0 Likes 0 ·
mvader (Victron Energy) avatar image mvader (Victron Energy) ♦♦ clayfree commented ·

Hi @Dajestia , @anthonya , @Clayfree , is that GX Touch issue when using gui-v2? Or the normal gui?



0 Likes 0 ·
clayfree avatar image clayfree mvader (Victron Energy) ♦♦ commented ·
I am using gui- v2
0 Likes 0 ·
dajestia avatar image dajestia mvader (Victron Energy) ♦♦ commented ·

gui-v2

0 Likes 0 ·
mvader (Victron Energy) avatar image mvader (Victron Energy) ♦♦ dajestia commented ·
Ok, glad to hear that. Its a known issue for gui-v2.



0 Likes 0 ·
anthonya avatar image anthonya mvader (Victron Energy) ♦♦ commented ·
@mvader (Victron Energy) GXTouch 50 with gui-v2
0 Likes 0 ·
anthonya avatar image anthonya anthonya commented ·
@mvader (Victron Energy) I've updated to ~45 and the problem still exists in this version.
0 Likes 0 ·
mvader (Victron Energy) avatar image mvader (Victron Energy) ♦♦ anthonya commented ·
Hi @anthonya Correct. There is still lots of work to do on gui-v2 by us, and making these settings work is part of that.
1 Like 1 ·
wynir avatar image
wynir answered ·

versions v3.20~41 and v3.20~43 ends up in pasthrough mode. v3.14~3 did restore normal operation. best regards

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.

Hi @wynir , ok noted, we’ll look into this.


Is it ok if we login to your system if needed?


(note to self: v-p #307)

0 Likes 0 ·
wynir avatar image wynir mvader (Victron Energy) ♦♦ commented ·

Of course, thanks for looking at it. With v3.20~45 the same problem.

0 Likes 0 ·
zolimar avatar image
zolimar answered ·

I am not able to detect neither with 3.14 firmware neither with 3.20~43 beta firmware my SMA Tripower STP10.0-3SE-40 PV inverter with latest firmware (3.4.16R) and latest MODBUS protocol.. Worked before updating the SMA to the latest MODBUS protocol (latest firmware). Any idea?


10 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.

Hey @zolimar , is it ok we login to take a look? You then need to enable remote support, see settings -> general menu.


And confirm that its MZE Home.


Thanks for reporting, Matthijs

1 Like 1 ·
zolimar avatar image zolimar mvader (Victron Energy) ♦♦ commented ·
Sure, anytime. Enabled support. Confirm is MZE Home. Please help, I tried a lot of things none worked. connecting to inverter through telnet 192.168.0.45:502 works just fine from Cerbo (with Putty), everything enabled in inverter TCP server, UDP server , ID:3. Let me know if you need more date / info. Even teamviewer I can provide, just to see it solved :-)
0 Likes 0 ·
zolimar avatar image zolimar zolimar commented ·
I even tried removing the inverter from /data/conf/settings.xml of Cerbo completly and reboot, hoping that the inverter will be detected again, but no go. Now I placed back the inverter config in settings.xml, also added manually the IP of inverter: 192.168.0.45
0 Likes 0 ·
mvader (Victron Energy) avatar image mvader (Victron Energy) ♦♦ zolimar commented ·
Hi @zolimar , we checked, and the issue is that the modbus tcp unit id is not set correct on the SMA. Its set to 127 now; and as per our documentation it needs to be set to 126.


Can you check that?


0 Likes 0 ·
zolimar avatar image zolimar mvader (Victron Energy) ♦♦ commented ·
The unit ID for modbus on SMA is set to 3. Possible values are: 3..123. It worked before the new firmware on SMA. Should I set to different value? Port is 502 on both UDB and TCP server.
0 Likes 0 ·
zolimar avatar image zolimar zolimar commented ·

I read from the SMA spec:

"The Unit ID in the SMA Modbus profile is freely configurable within the area 3 to 123. The default value is 3.

The Unit ID in the SunSpec Modbus profile for SMA products derives from the preset Unit ID in the SMA Modbus profile + 123. The preset value for the Unit ID in the SunSpec Modbus profile is therefore 126."

In my case the ID is set to 3.

0 Likes 0 ·
zolimar avatar image zolimar zolimar commented ·

Just wanted to mention that this is not a singular case. With same inverter running on 3.01.09R firmware we did the experiment at Victron representative in Romania (Timisoara - EEE) on a different Cerbo GX. Result: inverter detected immediately. Updating the firmware on SMA to the latest one: 3.04.16R (containing newest Modbus Sunspec protocol) rendered the inverter not working anymore on Cerbo GX.

If you want I can grant you acces in my inverter and also Cerbo GX, even SSH is possible on demand.

0 Likes 0 ·
mvader (Victron Energy) avatar image mvader (Victron Energy) ♦♦ zolimar commented ·
Hi thanks for the reply. A colleague or myself will come back on this tomorrow.
0 Likes 0 ·
mvader (Victron Energy) avatar image mvader (Victron Energy) ♦♦ mvader (Victron Energy) ♦♦ commented ·
Hey @zolimar thank you again for all your help with this. Fixed per v3.20~49!
0 Likes 0 ·
zolimar avatar image zolimar mvader (Victron Energy) ♦♦ commented ·
The pleasure was on my side. Thanks again for your incredibly fast reaction time to solve the issue. I really appreciate your third level support. It's one of the best I have ever experienced.
0 Likes 0 ·
andrii-podanenko avatar image
andrii-podanenko answered ·

Multi RS Dual Tracker

Renaming (custom tracker names) works in first inverter menu in Venus OS

1000013243.jpg

Doesn't work in Daily History menu

1000013242.jpg

Also, renaming doesn't work in gui-v2 (~45 build)

1000013244.jpg


1000013243.jpg (265.0 KiB)
1000013242.jpg (319.5 KiB)
1000013244.jpg (135.4 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.

bohne avatar image
bohne answered ·

Hallo


Mir ist aufgefallen das der Orion xs wegen in der alten noch in der gui Version nicht als Erzeuger angezeigt wird . Wird das noch geändert ? So ist es leider nicht ideal . Wichtig währe auch noch die Spannung von der startet Batterie das diese von der cerbo übernommen wird . Mit freundlichen Grüßen

2 |3000

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

ulfilas avatar image
ulfilas answered ·

Hello,

the charge limit is not working, when i set the limit to 500W, a charging power of 1000-1100W could be observed. Even when i set the limit to 50W, there is no chnage in the behavior. I can not say since which version this behaviour took place, becaus i had the system fore some time in sustain mode.

charge-limits.jpg
rc-view.jpg
Setup:- MultiPlus-II 48/5000/70-48 FW:506
- Cerbo FW:v3.20~45
- MultiPlus internal BMS

Greetings, Ulfilas


1707128345578.png (111.7 KiB)
1707128361854.png (169.5 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.

ulfilas avatar image ulfilas commented ·

I updated the cerbo to v3.20~46 and Multiplus to v508 but it's still the same.

Only the current limit in the VE.config of the MultiPlus is limiting the chaging.

0 Likes 0 ·
mvader (Victron Energy) avatar image mvader (Victron Energy) ♦♦ ulfilas commented ·

Hey @Ulfilas , we found & fixed a bug that causes this.

Its quite specific to your setup, the bug only manifests in systems with no solar chargers, no RS devices, no battery monitor, and where the VE.Can port is also disabled.

We’ll release that fix after more testing, meaning not as part of v3.20 - but in a later release.

0 Likes 0 ·
Juha Tuomala avatar image
Juha Tuomala answered ·

1707134044257.png


I second that grid-meter phases are missing, as well is the frequency. Old one had freq in output side. Frequency could also be in generator (not active since it's not running). I have EM540 meter on generator side as well so could have it without going into settings.



1707134044257.png (59.5 KiB)
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.

pf-1 avatar image pf-1 commented ·

I have observed the same, but the grid-meter phases stay away, even if I switch back to V3.20~37.

1 Like 1 ·
andrii-podanenko avatar image
andrii-podanenko answered ·

Installed

v3.20~47

On my MultiRS Dual Tracker system, with Node-Red (Venus OS Large ), upgraded from ~45

After installation - white screen of nothing

screenshot-2024-02-07-17-29-39-280-comandroidchrom.jpg

Rebooted via gui-v2 and it started working.


Confirming renamed trackers appear in Venus OS Gui correctly now, this is fixed @mvader (Victron Energy) . Thank you

screenshot-2024-02-07-17-32-44-958-comandroidchrom.jpg

New names are not appearing in gui-v2

screenshot-2024-02-07-17-37-24-307-comandroidchrom.jpg

Trackers renamed in VRMbeta

screenshot-2024-02-07-17-38-41-622-comandroidchrom.jpg

Not renamed in VRM just yet

screenshot-2024-02-07-17-39-21-409-comandroidchrom.jpg



2 |3000

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

beat avatar image
beat answered ·

I don't see a way to assign names to the 2 trackers of my MPPT RS 450/100. Is that new feature only for MultiRSes ?

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.

Hi @beat , no also for the MPPT RS. But did you try this using the latest VictronConnect v6.00 beta?

0 Likes 0 ·
beat avatar image beat mvader (Victron Energy) ♦♦ commented ·

No, I didn't try VictronConnect v6.00 beta, I searched in VenusOS GUIv1 under Device to find individual MPPT Names setting, similar to name individual MPPT 100/20 and 150/35 units, as that was in coherence with VictronConnect's settings. ;-)

0 Likes 0 ·
beat avatar image beat mvader (Victron Energy) ♦♦ commented ·

@mvader (Victron Energy) FYI I tried to start VictronConnect v6.00beta10 Linux AppImage downloaded from the changelog page here https://www.victronenergy.com/live/victronconnect:beta , but it exits immediately with error 127, while latest stable version runs fine (Ubuntu 20.04LTS Intel).

0 Likes 0 ·
mvader (Victron Energy) avatar image mvader (Victron Energy) ♦♦ beat commented ·

Thanks, we’ll look at that.

0 Likes 0 ·
bohne avatar image
bohne answered ·
  1. img-1198.pngimg-1194.pngHallo der Orion XS zeigt aktuell noch keine Lade Zyklen an . Desweitern wird er immer noch als Verbrauch angezeigt . Man könnte ihnen ja direkt bei den moppt anzeigen. Es ist ja ein Erzeuger.


img-0016.png



img-0016.png (252.5 KiB)
img-1194.png (363.9 KiB)
img-1198.png (162.6 KiB)
5 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.

bohne avatar image bohne commented ·

img-1199.png

Mion


Super jetzt wird der Orion xs als Generator dargestellt!!

0 Likes 0 ·
img-1199.png (474.3 KiB)
img-1200.png (472.5 KiB)
Show more comments
luka-renko avatar image
luka-renko answered ·

I just tried new build and I am very happy that Remote Console works now with new GUI from VRM: https://vrm.victronenergy.com/remote-console-2/xxxxxxx (put your id instead of xxxxxx).

Remote console is now fast and responsive. Looking forward to new GUI getting into production. Great job!

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.

hahaha, you found the secret - welcome!



1 Like 1 ·
luka-renko avatar image
luka-renko answered ·

Is temperature sensor display final?
1707340703643.png

I have problem with readability of the bars, as the color does not tell much about the current state and you have to search for white bar and then read the scale. This makes it unusable to quickly glance the screen and see the current temperature, therefore you have to resort to reading numbers below.

Maybe single color bars, filled only to the current level would improve this?


1707340703643.png (150.9 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.

Not sure if this is final, but noted. thanks!
1 Like 1 ·
luka-renko avatar image luka-renko mvader (Victron Energy) ♦♦ commented ·
BTW, it would be also great if temperature sensors would be sorted by name. It seems that they are currently listed in the order of IDs (20, 21, 22, 23)
0 Likes 0 ·
David Marks avatar image
David Marks answered ·

Having frequent crashes on ~47 that were not crashing on earlier 4x versions last week. What I observe is that after some period of time, the device stops logging to VRM and becomes inaccessible over the network. But the screen still works but is laggy. Then, after some random period of time the display crashes to a black screen with a blinking cursor.

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.

Hey @David Marks , thank you for your report. Can we login remotely to see the logs? For that you'll have to enable Settings -> General -> Remote Support.


Looks like I was able to find the system, Sea D.


(note to self, #vp-317)

0 Likes 0 ·
David Marks avatar image David Marks mvader (Victron Energy) ♦♦ commented ·
Sorry for the slow response, yes I've enabled remote support and you're welcome to grab the logs to see if you can spot the issue. FWIW, I switched back to the old UI and things have been stable since. If you need me to load the new GUI to get useful logs, just let me know.
0 Likes 0 ·
mvader (Victron Energy) avatar image mvader (Victron Energy) ♦♦ David Marks commented ·
Ok thank you. We’ll login and look at gui-v2 first.


Sounds like you’re running that on the LCD of GX Touch or Ekrano GX?



0 Likes 0 ·
mvader (Victron Energy) avatar image mvader (Victron Energy) ♦♦ mvader (Victron Energy) ♦♦ commented ·
Hi again @David Marks , I logged in, saw something but not enough: yes, please load the GUI again - thanks!
0 Likes 0 ·
mvader (Victron Energy) avatar image mvader (Victron Energy) ♦♦ mvader (Victron Energy) ♦♦ commented ·

ps. I had another look, and your Cerbo is just fairly busy all the time. Especially SignalK is taking quite the amount of resources.


And gui-v2 requires more CPU than gui-v1. Which is something we'll improve before official launch, but now it is what it is.


Here for your info a screenshot. Note the 16% idle, which is not a lot of head room, and the top heavy processes:


1707593334192.png


So for now, either stick to gui-v1, disable signal-k server, or get an Ekrano since that has a 4 core CPU instead of just 2 like the Cerbo has.

1 Like 1 ·
1707593334192.png (96.1 KiB)
mvader (Victron Energy) avatar image mvader (Victron Energy) ♦♦ mvader (Victron Energy) ♦♦ commented ·

ps. depending on what type of system you have connected to SignalK server, it might pay off to have it filter certain N2K messages on inbound. Ie in the n2k plugin or dataconnection.

Adding such filtering, for example on some compass PGNs that came in at 10Hz, helped a tremendous amount wrt dropping SignalK CPU load on my own boat.


But discussing about that is not something for in this thread, better in the SignalK Slack or elsewhere.

1 Like 1 ·
Jeremy Albrecht avatar image
Jeremy Albrecht answered ·

I've been testing GUI-v2 on my CerboGX and GX Touch 50 and I've noticed a few issues that I can't find anyone else mentioning.

1. The "Display Brightness setting" does not work. Changing it does not affect the brightness of the display.

2. Auto brightness also does not work.

3. The "Display Off Time" does not work. My screen remains on all the time no matter what I set it to or how long I leave it alone.

4. With the temperature units set to Fahrenheit the sidebar on the "Brief" page still shows Celsius.

5. On the remote console, either direct via the /gui-beta/ page or via the beta VRM page the controls are unresponsive, and as such I cannot turn the inverter on or off.

6. On the levels page the graph is inconsistent between the display on the base page and if you tap on one of the levels itself. (see attached screenshots).

I have one additional comment, and it's not something broken, but more of a request. If the relays are set to manual mode they should be available to control from the controls button on the UI, without having to go into the Relay menu.

screenshot-2024-02-08-at-133416.pngscreenshot-2024-02-08-at-133423.png


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.

Hey Jeremy, thank you for your report. Most of those we know; many are even fixed already.


We have quite the list of things to fix and work on - pls await a few further versions.

1 Like 1 ·
Henry Pearson avatar image
Henry Pearson answered ·

I've been following and upgrading my cerbo - using the beat GUI through remote interface through iPad. Overall happy and a great improvement but 2 bugs

  1. Can't easily see the aux or engine battery voltage from BMV
  2. When selecting devices from "home" screen, takes you to device list but can't go any further, just doesn't respond when you select a device.
2 |3000

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

mauri avatar image
mauri answered ·

1000023097.jpg

On local display there is part of keyboard visible all the time. Maybe because of non standard screen size?


1000023097.jpg (838.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.

beat avatar image
beat answered ·

I was running v3.20~49, and the solar production suddenly dropped to 0 at noon today for a couple of minutes.

Logging into ssh, I saw in /var/log/messages.0 that the Cerbo rebooted by itself due to CPU overload: Don't have an explanation for the reason. Will upgrade to ~50 soon, maybe tonight. @mvader (Victron Energy) Let me know if you need remote access, or any specific log file to find the reason of the overload/reboot.


Feb 10 11:00:45 einstein daemon.err watchdog[710]: loadavg 9 7 4 is higher than the given threshold 0 6 6!
Feb 10 11:00:46 einstein daemon.err watchdog[710]: repair binary /usr/sbin/store_watchdog_error.sh returned 253 = 'load average too high'
Feb 10 11:00:46 einstein daemon.alert watchdog[710]: shutting down the system because of error 253 = 'load average too high'
Feb 10 11:00:46 einstein daemon.err watchdog[710]: /usr/sbin/sendmail does not exist or is not executable (errno = 2)
Feb 10 11:00:56 einstein syslog.info syslogd exiting
Feb 10 11:03:15 einstein syslog.info syslogd started: BusyBox v1.31.1
Feb 10 11:03:15 einstein user.notice kernel: klogd started: BusyBox v1.31.1 (2024-02-03 00:43:23 UTC)
Feb 10 11:03:15 einstein user.info kernel: [ 0.000000] Booting Linux on physical CPU 0x0
Feb 10 11:00:45 einstein daemon.err watchdog[710]: loadavg 9 7 4 is higher than the given threshold 0 6 6!
Feb 10 11:00:46 einstein daemon.err watchdog[710]: repair binary /usr/sbin/store_watchdog_error.sh returned 253 = 'load average too high'
Feb 10 11:00:46 einstein daemon.alert watchdog[710]: shutting down the system because of error 253 = 'load average too high'
Feb 10 11:00:46 einstein daemon.err watchdog[710]: /usr/sbin/sendmail does not exist or is not executable (errno = 2)
Feb 10 11:00:56 einstein syslog.info syslogd exiting
Feb 10 11:03:15 einstein syslog.info syslogd started: BusyBox v1.31.1
Feb 10 11:03:15 einstein user.notice kernel: klogd started: BusyBox v1.31.1 (2024-02-03 00:43:23 UTC)
Feb 10 11:03:15 einstein user.info kernel: [ 0.000000] Booting Linux on physical CPU 0x0


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.

Hey @beat ; Thank you for the report! Sounds similar to what @David Marks reported.


Do you have a GX Touch connected to your Cerbo and are you running gui-v2 on that?

And is it ok if we log in to see more logs?

0 Likes 0 ·
beat avatar image beat mvader (Victron Energy) ♦♦ commented ·

Hi @mvader (Victron Energy) ,

I don't think my issue is same as @David Marks ' issue (with Signal K and GUI-v2, as I don't run either of them), and I didn't notice reboots or all chargers dropping to zero simultaneously over any day of since testing 3.20~.... . To answer your questions:

  • yes, a gx touch is connected, as well as remote web console over local wifi.
  • no, both gx touch and local wifi are running GUI-v1, which is for now way more informative to an engineer like me than GUI-v2. Running standard large image, no guimods.
  • sure you can log in, enabled VRM 2-ways coms and remote support (my VRM instance name is "test", and level 3 support mails have the details.
  • I'm not running Signal K, only Node-RED, without a huge script.
  • Below my "top" at night once batteries are at their 20%SOC (Fronius is auto-off, and MP-II are off by software (Node-RED script)): CPU is 66% idle, NodeRED consumes 10% CPU and remote console 2%, so plenty of free CPU room, RAM is 50% free too, and load is typically between 0.3 and 2. Sometimes it goes a bit beyond 2, not visible why with "top":
  • iotop is not installed, so can't check what generates the load higher than 1 from time to time, while CPU stays 66% idle. Must be an I/O, but which?

night-screenshot-from-2024-02-10-22-58-00.png

Btw, should I upgrade from 3.20~49 to 3.20~50, or wait for your remote access ?

0 Likes 0 ·

Related Resources