Yes, the times are announced one year in advance. However, they vary regionally and are different each quarter.
I actually didn’t want to make it a topic here in the beta section. It’s been a topic on and off for almost a year. Unfortunately, nothing’s been done in this direction. Honestly, I’m a bit disappointed.
DESS isn’t much of a priority, not enough people actively advocating for change is what I’ve heard, and still too niche to get prioritised. I was advocating making DESS a category of it’s own to create more visibility and a better structure to facilitate community collaboration but even that got snowed under.
Our time based grid fees only change if the grid operator decides to increase pricing or the taxes change. Which has been about every 1-3 years.
22-07 is cheaper for us. Most people here with more than 10MWh/year consumption, like me, pay extra to get that lower night pricing.
You are shure, can‘t find anything…
Moved to the new topic for 3.70-37
So, finally an answer to that question. I just picked up the car and tested it straight away. The difference between the ~26 and later versions (tested with the current ~35) is apparently a different version of the can-bus-bms. It used to be v0.69, now it’s v0.70. My system obviously can’t cope with that. This can be found in the log files of /var/log/can-bus-bms.can0/current
I have no idea how to proceed from here. I’ll try to get an update for the BMS of my Supervolt LiFePo and then report back.
@mpvader Will there be any additional improvements to dess in 3.70?
@mikisound I have now tried various things without success. I changed the can2usb-adapter to an alternative device, checked the cable, and contacted the battery manufacturer. The result remains the same: anything above ~26 does not work for me. Then came the change to v0.70 of the can-bus-bms in VenusOS, and that seems to be causing the problem. Have you made any progress here?
@mpvader Is there a changelog for your can-bus-bms from v0.69 to v0.70?
@felixreher – Yes, the issue has been resolved. @mpvader reached out to me. In my case, the problem was caused by a relay board I had added to the RPI. I’m not sure what exactly they did, but it’s working fine now.
The thread has been moved to a new location:
V3.70~beta: issue when adding mods that add relays - Modifications - Victron Community
Apparently, the findings from the analysis of your system led to changes – although these are only referred to in the changelog as ‘Various updates to Venus OS / Linux base system’. However, with the release of 3.70~49, my system is finally fully functional again.
Good day, thank you for all the hard work being put in. Request, wish, I have acquired a GX extender and was wondering if the additional relays available can be added to the relay page - I am planning to control valves on my storage tanks using levels and Tank pump to control the refill of these tanks - if it is possible
Kind Regards,
Hello, I’ve noticed that in version 3.66, the grid meter is sporadically not recognized in several systems. This briefly disrupts the system, causing the battery to feed all available power into the grid. Has anyone else experienced this? I’ve encountered it in three houses.
I have to admit that I see the “lost grid meter error“ more often than before…..
Been running v3.66 for ages now, never encountered this.
Feeding all available energy to the grid when the grid meter is not available is not expected behavior either.
What are you using as grid meter?
I am using a Homewizard P1 meter using a home made http dbus driver (own development)
I am running multiple setups this way and for more than two years without these errors.
Since version 3.66 I encounter some “lost grid meter” errors. (twice now) Not a single one with all previous versions.
I can remember that I have red somewhere on this forum that in previous versions this “lost grid meter error” was not always populated. So maybe I had these errors in the past as well but were not visible (for me)
I know I cannot expect any support from Victron but I just wanted to let you @Reddriver1980 know that I experience these errors as well.
Hello, for all systems the ET340
Thanks Martijn, then I hope that Victron will implement and correct this again.