question

Just a note and its not Victron Problem I think - but Kevin Windrem add on system did not survive the upgrade.

The DVCC Max Charge Voltage does NOT seem to control The multiplus II (Early version) charge voltage (its not just the Multiplus II as well and I am sure one site I have tried it with It is not working on standard multiplus units with CCGX with release software), The max current control is working fine. This Max Charge Voltage has not worked even for earlier versionsas well - Unless I am miss interpreting what it does.

Any way my system is currently outputting its set voltage in the Multiplus being 56.00 and is not being controlled back to 55v as per the DVCC indication. Fw 487 on the Multiplus II

In various places we removed the solar charger PV array current (Amps) values. From D-Bus, MQTT, VRM Logger, Modbus-TCP, Node-red. And instead made sure that Power and Voltage is available for each array. This reduces unnecessary D-Bus traffic and as such optimises the maximum number of installable Solar Chargers.

PV current was much more useful than PV voltage in VRM (but I would rather have both).

Firstly thanks for your work on this latest iteration, big leaps forward.

This is running stable on my system, all I noticed was in the BMV 712 firmware when using as a dc load meter alternator is missing an r in the spelling.

Another thought, it might be a useful addition to be able to set the temp input as the alternator temperature in this application!?

BUG: PV Power is not being reported.

I am displaying PV voltage and current in my GuiMods PV tiles. When I went to recode to use power instead of current (which is removed in this version of Venus OS, I noticed it is not a parameter at least for my BlueSolar 100 | 30. All that's reported is PV/V now.

In this release, the connection to the HTML5 MFD is very long or no connection.

I updated my Cerbo from v2.80~19 to this new v2.80~21 a few minutes ago.

At first boot Remote Console partially loaded and then I lost connection (over Wi-Fi).

I connected a LAN cable and I could access my Cerbo with Remote Console, but it was very sluggish.

I performed a reboot (from Cerbo's menu) and after that I could access it more or less normally using Remote Console (including via Wi-Fi) for a few minutes. Then Wi-Fi failed again. And over LAN it was again very sluggish.

I power cycled the Cerbo - same sluggish Remote Console (over LAN/UTP cable).

I booted back into v2.80~19.

Will there be any plans, at some later date, to incorporate the motion input from the Ruuvi sensors since that is part of their configuration? That would be an excellent theft detection input for many types of installations.
"Sensors:

• Add support for the Ruuvi Wireless temperature sensors. Besides temperature, also humidity and atmospheric pressure are supported."

I am having issues with ~21, wifi signal is a lot weaker than in ~17 and everything loads a lot slower. Cerbo and wifi AP are 3 feet away and are physically secured in place.

I can confirm the Wi-Fi connection on my Cerbo is significantly impacted by v2.80. Response is fine with v2.73 but not with v2.80~21. I don't recall this problem with earlier versions of v2.80 but could be wrong. (Ethernet is unaffected, just Wi-Fi.)

I also feel overall responsiveness is slower (looking at the Touch 70) also. For example, discovery of a VE.Bus inverter seems to take longer.

After changing the function of BMV-712 smart DC battery monitor to DC monitor, the device is not visible in the N2K network.

Another topic when I use garmina 19 garmin in n2k network is visible through Cerbo for VRM positioning, when I use Furuno SCX-20 satellite compass it is not possible to use VRM installation positioning.

The PGNs responsible for the gps data are standard, the remaining PGNs are related to other parameters, where is the problem?

1 NMEA2000 port

Input: 059392/904, 060160/416/928, 061184, 065240, 126208/720, 130847

Output: 059392/904, 060928, 061184, 065280,126208 / 464/720/992/993 / 996/998, 127 250/251/252/257/258, 129 025/026/029/538/539 / 540,130310 / 312/314/316/577/578/816/817/818/819/822/823, 130833/834/842/843/845/846/847

Hi all. I'm running the following system: 3 x MultiplusII 48/5000, 3 x Smart Solar, 1 x Cerbo GX with a a touchscreen and 6 x Pylontech US 3000c with a capacity of 21 kwH. Everything is runnung on the newest firnware. I'm running the ESS with the modus "optimized withbattery life".

When the grid is lost, the system works fine. But when the grid is back, the 3 Multiplus doesn't switch back. That means, that the LED "mains" are not illuminated. This behaviour can only be solved, when I select the modus "Optimized without battery life". Then the relais in the Multiplus are switching and the grid power comes to the inverters.

Has anyone an idea, why this behaviour is so?

Thanks Klaus

I have seen a strange issue that I am unable to solve. This is running VenusOS on Pi3+.

I upgraded from firmware v2.72 large~19 to v2.80~16-large-21 (and later v2.80~21-large-23) and one of my devices connected to USB1 did not want to start anymore. It use the same driver and the device on USB0, and I also swopped to two devices. It's always the one on USB1 that does not start with serial-starter.
Switching back to v2.72 where both worked before, USB1 now also does not start there.

I can manually run the USB1 device, so there is nothing wrong with the hardware, connection or cables.

I have removed my /data/conf/settings.xml and recreated the setup, but still it does not start USB1.

dmesg show that the tty is detected.

[    3.872365] ftdi_sio 1-1.2:1.0: FTDI USB Serial Device converter detected
[    3.879752] usb 1-1.2: Detected FT232RL
[    3.892518] usb 1-1.2: FTDI USB Serial Device converter now attached to ttyUSB0
[    3.904320] ftdi_sio 1-1.4:1.0: FTDI USB Serial Device converter detected
[    3.923677] usb 1-1.4: Detected FT232RL
[    3.937019] usb 1-1.4: FTDI USB Serial Device converter now attached to ttyUSB1

And the serial-starter service does seem to start the device.

@40000000615efe6223da3edc serstart starting
@40000000615efe622407ceec INFO: loading config file /etc/venus/serial-starter.conf
@40000000615efe630b49270c INFO: loading config file /data/conf/serial-starter.d
@40000000615efe6403bb96dc INFO: Create daemontools service dbus-serialbattery.ttyUSB0
@40000000615efe651619092c INFO: Create daemontools service dbus-serialbattery.ttyUSB1
@40000000615efe661f029b34 INFO: Create daemontools service vedirect-interface.ttyUSB2
@40000000615efe6725b9b124 INFO: Create daemontools service vedirect-interface.ttyUSB3
@40000000615efe682c721aec INFO: Create daemontools service mk2-dbus.ttyUSB4
@40000000615efe6a06be2494 INFO: Start service dbus-serialbattery.ttyUSB0 once
@40000000615efe6b1877d504 INFO: Start service dbus-serialbattery.ttyUSB1 once
@40000000615efe6e139659d4 INFO: Start service vedirect-interface.ttyUSB2
@40000000615efe6e13b5288c INFO: Start service vedirect-interface.ttyUSB3
@40000000615efe6e3b311d44 INFO: Start service mk2-dbus.ttyUSB4

But no log file is created for dbus-serialbattery.ttyUSB1, only for dbus-serialbattery.ttyUSB0

Is there anything I can look at?

Hi.

RasPi 3B+, Multiplus-II 24/3000/70, VenusOs Large v2.80_21-large-23.

I am controlling charge amperage via modbus register 2705 (com.victronenergy.settings/DVCC system max charge current). It works fine. But I have found one inconsistency. In the CCGX-Modbus-TCP-register-list the range of that address is described as -32768 to 32767, but when I send -1 to it to disable the charger, the response I get is this:

"RangeError: The value of "value" is out of range. It must be >= 0 and <= 65535. Received -1"

Best Regards,

Mr Happy

I lost WIFI connectivity alltogether, it can see my WiFi access point (Teltonika RUT955) but refreshes every minute or so, and it disappears. If I get to connect page, and manage to enter wifi passphrase (WPA2/PSK security), it just tries a few minutes and then cant connect. Found accesspoint keeps disappearing. Downgraded to latest solid 2.73 and now wifi working again.

Also, the HTML5 MDF app, how is it supposed to work? turned both MQTT switches on, but still writing the IP of my venus GX and \app doesnt seem to work. Marine label on browser, but Cant connect to MQQT server... dowsnt work on 2.80 or 2.73 FW

BUG: I have been testing 4ea. RuuviTag this week with my CerboGX and like them along with the Victron implementation of them. They will be an excellent tool for us going forward, I hope the implementation doesn't get scrubbed.

I have noticed a couple of anomalies.

1. In the VRM Dashboard display, the order of them is not configurable even if all inputs are named to be alphanumeric and/or alphabetical. In this photo, all analog inputs are named and list properly in the Remote console but not in the Dashboard. It appears that the Dashboard lists them solely on order of initial contact reading from the CerboGX.
2. A RuuviTag that is removed either by deselecting the "enable" tab or completely removing it from the Remote Console does not become deleted from the Remote Console as long as it is still within BT range of the CerboGX. The way that I was able to get the RuuviTag to not show up inside the Remove Console was to move it out of BT range AND then reboot the CerboGX.
3. A RuuviTag that is removed from the Remote Console does not become deleted from the Dashboard. Even taking the RuuviTag out of range of the CerboGX doesn't work. See photo above, item "03_Battery hold(36FE)". In the photo below, the RuuviTag "Ruuvi 36FE" has been removed from the Remote Console by deselecting it from this Bluetooth Sensor menu, then from the Remote Console device list "device remove" switch, and finally by rebooting the CerboGX. Without rebooting, it will remain in the Bluetooth device list.
4. The RuuviTag(s) do not show up in the Device List within VRM controls. I believe that this is why any that are removed via the Remote Console can not be deleted in VRM. A physically attached temperature input to the CerboGX can be removed in VRM by this Device List.

Have just upgraded a site with a cerbo from 2.63 to 2.80~21, The Raymarine MFD was working on 2.63 but now that the 2.80~21 firmware is active on that site the Victron Icon just shows a white page.

Reason we have a few test sites out on 2.80~21 - Have upgraded a few for our sites for testing as I am testing the new 123smart software for interfacing to the GX devices with Sebastiaan's help, ( there new software only works on 2.80 and the newer Python)

Hi!
I still do not understand what to expect from the new DC meter function: There is a 115A alternator, a Silentwind generator and MPPT100/50 (500Wp solar panels) in my system as charging sources for my 330Ah lithium (cruising sailboat setup).

All negatives of the charging sources are connected to a central minus distribution busbar and this minus busbar is connected to the shunt of aSmart BMV712 which then is connected to a 330Ah smart lithium from Victron.

So far I am getting fine readings on the VRM screen from the MPPT100/50 which is connected to the Raspi4 running Venus V2.80-16-large21, but no additional widgets for additional charging sources or something like that.

So when switching the BMV712 to DC meter mode: What shall happen when getting charging amps from the wind generator and/or alternator? Maybe I am completely misunderstanding the whole topic about the new DC meter feature?