Hello,

I noticed that consumption in VRM "System overview" dashboard graphs and widgets are always way smaller than they should be. I think I got to the cause of it, hence this report and ask for a fix.

Below in red rectangle you can see how it has been for months - consumption always shown lower than it was. Then I started playing with the settings and got it to show up more or less right - in green rectangle you can see how the consumption is in reality.

[image]

As you can see in "Jun 18", discrepancy is about two times! So what's the reason?

There are various DC chargers in this system, of which mainly two of them generate the bulk of energy:

1. Non-Victron solar charger 80A
2. Victron solar charger 85A

In order to see all the chargers conveniently in the "Remote Console", I have had "Has DC System" enabled. Then I see all chargers summed up in "DC Power" box. If the value is negative there, it means "DC System" is charging and all is great! At least you would think so.

[image]

However, what you can see in the picture above, is that VRM on the left shows very tiny consumption (224 W) compared to the real one (1395 W AC). There is some time lag between these two screens, but I noticed that essentially VRM takes AC consumption and adds DC Power. So, if you have any external chargers (like non-Victron solar, wind or even a generator with DC charger), "DC Power" shows as negative and VRM just blindly deducts that charging power from the consumption.

As soon as I turn off "Has DC System", the consumption shows up more or less correctly:

[image]

This is very inconvenient, because if you have any non-Victron charger and disable "Has DC System" in favour of correct VRM consumption, you can't see it in Remote Console view.

What's the possible real fix? VRM should only add "DC Power" to the consumption if it is positive, but ignore the value if it is negative (in other words, when DC system is charging as opposed to consuming).

Would someone from Victron step up to address this? As it stands right now, the system is not capable to deal with heterogeneous setup :-(

Finally, one more related bug in VRM's "Consumption" dashboard even with the disabled "Has DC System":

[image]

Here you can see that half of the energy is said to be used "from battery", which is just wrong. All that blue energy was generated by the mentioned non-Victron charger. What's worrying here, is that this system has a BMV which knows exactly how much went out of the battery (and in this case it was 0.0Ah), but VRM is using some kind of convoluted formula to get these numbers as opposed to using data from BMV.

It would be really great if this use case with not only Victron chargers be addressed, because as it stands right now, the whole VRM Dashboard tab is just disinformation.

Thank you in advance!

Hello,

the virtual switch in the MultiPlus is a very useful and powerful tool. I'm wondering if this would also be possible to integrate in VenusOS similar to scheduled charging.

Some independent examples:

- Turn Multi off at 10:00 PM. Turn Multi on at 6:00 AM

- Switch critical loads on for 2h every 48h OR if Battery SOC is >90% AND PV Power is >100W

- Don't turn Multiplus on sundays

- Use Multiplus Charger only between 10:00PM and 06:00AM (probably because Energy is cheaper then)

- Switch Solar Charger off when DC-Loads were <5W for more than 24h (don't know why) and VE.Bus state is off

- Set Absorption-Voltage to 14,2V if Battery-SOC hasn't fallen below 90% for more than 72h

- Set Absorption-Voltage to 14,7V if Battery-SOC has fallen below 60%

- Ignore temperature and turn off compensation if voltage is above/under example-voltage

- Limit Output to 500W as soon as SOC reached <60% and AC-In is connected.

- Stop Discharging if PV-Power is lower than 200W for 1h and SOC has fallen under X%

- DON'T limit charge current if loads are higher than X

- Switch 230V to 220V on overload

and so on ..

regards,

Porcini

good afternoon.

i updated to 2.31 early this week, so i could use remote ve configure. After the install, the venus GX rebooted, but then the lights went out, as apparently the multiplus also restarted.

I wasnt expecting that, is it normal? Can i prevent it in future?

i dont recall this last time i upgraded which i think was 2.12.

[image]

[image]

How I can back to Old Graphic Design ?

Dear all,

Just now, we released beta version v2.32~2 for testing. See below for the changes.

For information on how to join, or leave, the Venus OS beta testing program, as well as other information about it, see this document.

In case you see any issues or bugs, please post below as an answer or comment. Thank you!

Changes compared to v2.31:

• Fix CCGX causing VE.Bus communication errors, such as Error 17. Also it can cause a false Error 24, which is normally not related to communication. To be affected by this issue, the system must have a CCGX, with part number BPP010300100R. Also recognisable by the country of origin: Hungary. All other CCGX part numbers, made in China and India, are not affected.
  
  We started shipping the affected model in 2017. And since early 2019 we're only shipping the affected units: by that time there was no more stock of the older units in any of our warehouses. The CCGX as used in some EasySolar models is not affected.
  
  The issue was that that version CCGX transmitted on the VE.Bus network even when it should not. Causing collisions, ie. errors in the communication. More units in a system (three phase, and then especially with parallel units also) means that its more sensitive to this issue. Single system units are very unlikely to be affected by it; I've not yet seen that once.
  
  Thank you to all people that have reported and helped to fix this.
• Fix the System Setup -> DVCC -> Charge current setting not working, if the Venus booted while there is no PV on systems with normal batteries. Systems with intelligent can-bus connected batteries are not affected by the bug. Thank you @John Hagtharp for all your effort in getting this fixed. This issue was introduced in v2.30
• Fix the ModbusTCP register for the PV Inverter serial number(s) no longer working. The recently introduced 32-bit energy registers for PV-inverters overlapped with the serial number registers. This is fixed by moving the new energy registers from 1040 to 1046. The issue was introduced in v2.31.

Should you now go and install the v2.32~2, which is a beta version, on all CCGX systems you installed recently, to prevent Error 17 and other issues? No.

I recommend to do that only for systems that have issues. For systems not having issues, I strongly recommend to wait until this version is made available officially. As always, beta versions are not at all intended to run on production systems.

If you do choose to install this beta version, make sure to set the system back to update to official releases. Don’t leave it configured to auto-update to beta software.

Best regards, Matthijs

I have 200watts of solar. On the sunniest day in Tucson it stays in bulk mode all day, only a few times has it ever floated. My batteries voltage is slowly falling. I am in an RV and on the road. I have been running the generator to get the voltage to 13.6. I have two new AGM group 31 batteries. My system is wired differently. I have no loads connected to the charge controller. I believe the loads are directly wired to batteries. I did not wire the system it was done by a previous owner. I have older Trace 2000 watt inverter. Everything works great other than the charge controller. It barely allows 1 amp to pass trough the charger and seldom uses 20 watts of solar, the norm is single digits. I am using the battery life algorithm. If I try to manually start an equalization it doesn't complete itself.

Hi all,

I have a Victron Atlas Cobi 12/800/30 that does not show any charge current for batteries. charger “on” Boost “on”

Batteries are Victron 12 165 Ah gel ( 3 off )

I have checked fuses F1 & F2 all OK.

Any help appreciated cheers

Rod

Hi,

for nearly one year i am using Raspberry pi with Venus os (latest v2.31) and two energy meters. I noticed that recently several dashboard improvements were released. Unfortunately since June 16 dashboard does not longer shows the data. Strange is that Remote console or Advanced page works perfectly fine and i can access all data. In past this issue occurred but reboot always fixed that, no chance now. Any ideas ?

Br

Martin

yellow shows 1f meter, red is 3f +1f together so do not be confused

[image]

[image]

[image]

I’m new to the pi and Victron in general but I spent this evening getting my pi touch screen setup for touch, dimming and screen off settings. I got everthing calibrated and working, then on a whim I decided to see if there was a new beta build available and 2.30~40 was available. I installed it and it killed most of my settings (touch, dimming, screen off) and is no longer headless. However it kept some of my settings for dvcc, network and WiFi.

Is this normal behavior when upgrading the pi? Or maybe just with beta releases?

Thanks.

Hi,

I used root access to modify /etc/dbus-1/system.conf and made a typing error - rather put the new section

<listen>tcp:host=0.0.0.0,port=78</listen> <auth>ANONYMOUS</auth> <allow_anonymous/>

to the very end of the file instead of inside the correct section.

now my Venus is not accessible anymore. Is there a way to make a full reinstall or any other way to access the device to take the modification back?

The LED indicates a finished boot (green flashing of LED), but I doubt this is correct.

Thank you very much!

I have connected rpi through voltage divider and I was able to read data from 250/85 mppt. I read data every 15 seconds and write data to influxdb/grafana. Everything works fine with exception that after certain period of time current values are not correct. For example, it shows PPV and I values at 10PM like there is a daylight. After I stop program and start it again everything is ok. And then it happens again. Does anyone knows what could cause this?

Hoi @mvader,

I think i've found a bug...

If you place colorgx - quattro - input current limit (AC current) on example 20A

And on the colorgx - settings - system setup - maximum charge current set on 8A

= limit is than 8A to battery and thats ok

AND then you go to colorgx - quattro - advanced - system reset (press to reset) OR you go to colorgx - quattro - switch (on to off and back to on)

Then there is no system check to what current is setup in ESS mode, it charges with full power setup in colorgx - quattro - input current limit ( 20A)

At that stage you can go back to colorgx - quattro - input current limit (AC current) and change to higher value or lower, system is following that value and not ESS value..

ALL is back OK when you hard reset the quattro with front switch to OFF and ON again. And in colorgx - settings - system setup - maximum charge current go from 8A to 10A and back to 8A.(just change value to something else)

Iam using all the last firmwares

All setting are made in colorgx, not in ve.config

AND colorgx - setting - ESS - mode set on "keep batteries charged"

Edit2: no solar attached, only grid

//kg

Hello,

To protect the battery bank (Lead Acid) from too fast discharge - currents too high for the battery capacity - I have set some conditions to start Generator (which in my case is the grid). The setting that I wanted most is:

[image]

The issue that I'm having is that I have just realised that this current is not truly the Battery Current but rather the Multiplus Input current. During the day, this value is the SUM of MPPT output and battery current. My system was triggering generator during the day when I want to take advantage of direct solar use (high loads).

As a workaround, I have set quiet hours and defined 2 values, but this is not ideal since we can have the washing machine working very nicely with 2kw from the MPPTs and suddenly a cloud comes and makes the system draw a lot of current from a small bank.

Is there a way with assistants to start generator from the true battery current? Could this option be changed so we can subtract the MPPT production?

I'd like to read realtime information from a SmartSolar MPPT 75/15 controller and integrate it with a home-grown monitoring system. Pretty much like VictronConnect, except that it wouldn't be from an App on a phone, it would typically be from a script periodically running on something like a Raspberry Pi with builtin Bluetooth LE. If anyone has some experience on this, would you be so kind as to point me in the right direction?

I developed this for a larger project but ended up turning into a basic library.

It provides very simple reading on VE.Direct SOC, Power, Volts, Amps.

Posted in case someone finds it useful.

https://github.com/winginitau/VictronVEDirectArduino

Can someone please send me version 1.05 of the Victron LoraWan files there missing from Github https://github.com/victronenergy/lorawan-connect

Hello,

Sorry for the long post, I hope someone with programming experience can give me a little tip how to solve my problem.

After each VenusGX software update, I always have huge troubles to get my bash-script started again periodically by a cronjob.

Usually I do the following:

1. I duplicate my bash-script (maxinverterpwr) from a backup on /data to /etc.
   The script itself starts with:
   
   #!/bin/bash
   set -e
   
   #---Deactivate Fronius Standby Mode (switch off relais) ---
   dbus -y com.victronenergy.system /Relay/1/State SetValue 0
   ....
   ....
   ....
2. I make the script executable with chmod +x /etc/maxinverterpwr
3. With WinSCP I give the script all root rights too (0777)
4. If I start my script manually in PuTTY with ./maxinverterpwr, it runs without any errors.
5. Cronjob stuff:
6. With nano setpowerlevels I create a new file in /etc/cron.d with the following content:
   */10 * * * * root /etc/maxinverterpwr
7. With crontab setpowerlevels I "convert" it into crontab.
8. After that, crontab -e shows the following (looks ok for me):
   

   [image]

   Is it necessary to delete the setpowerlevels source file or not (I tried both)?
9. I reboot the VenusGX device.
10. I would expect that my script will be started every 10 minutes, but it does not!

I am quite desperate because sometimes I get it working after updates (honestly I don't know why it works) but this time I failed. Wheather it is working or not, in the end everything looks the same for me. Any ideas what else I can try? There must be only a tiny thing that I do not consider.

Thank you and best regards,

Rainer

I recently got a pair of Victron 60 ah NON-SMART 12.8v Lithium iron phosphate batteries on ebay. They were both received at around 13.2v which is fine, but the seller also gave me 2 more of the same spec that were each at around 9.9v.

Being the non-smart versions, I obviously can’t connect with bluetooth to see the individual cell voltage, but is there any way at all that this information can be seen? I currently have a Victron 100/20 MPPT charge controller, and will have a VE.bus BMS on order soon. Will the BMS interterface with the smart solar charger, or with any other device and pass the individual cell voltage on so I can see that?

I also have a rPi if it’s somehow possible to do with that...

I connected the two 9.9v batteries in parallel yesterday and charged them at 1A (the lowest I could set the smart solar 100/20) untll the votlage got to 11.5v this morning (it held at 10.04v overnight), where it seemed to stop, then upped it to 2ah and it’s now at 12.95v.

EDIT: It charged up gradually to 14.0v today, but it has since fallen back down to 10.73 now that no charge is coming in. I’ll se how it does overnight.

Any further thoughts welcome.