Since upgrade to ~11 version, my connection to VRM drops for several hours every other day. I did not experience this before. Are there any logs on Cerbo I could check?
Now is working fine
1 Like
Why does the Victron AC meter display a negative value, and why does the animation appear as if the system is feeding power back into the grid, when in fact itâs actually showing the camperâs current consumption? I was hoping this issue would be resolved in the beta version.
Hey @tux , Iâm not sure why that happens; Iâll get it checked later.
Good day all, already per yesterday evening - apologies for the late notification! - we have made a new version available for public beta testing:
v3.53~2. For details, see here: Venus OS beta v3.53~2 available for public testing.
The goal of that is to release various fixes as an official release as soon as possible, and thereafter continue public testing of the v3.60 beta series.
Please, at the v3.53 topic - not this one, let us know how v3.53 is working for your system.
Thank you and have a good weekend, Matthijs
1 Like
Hey @patxitoller , that is an exceptionally small tank you have there? Iâve made a note, but this needs some consideration as for most people showing decimals for liters is not a good idea.
Hi @Lure is that still happening in your system? Is it OK if one of us logs in remotely and checks?
What you could check is /data/vrmlogger/* logs.
Yep Matthijs, the 2,75 kg GPL tank of my van is equal to 5,288 litres. Even a decimal (5,3 lts) should be more accurate than just the actual 5 lts. Thank you for your reply
Ah its GPL, ie gas. Thanks; understand it better now.
Sorry for that, Matthijs.
It should be handy to gauge small GPL tank, in order to avoid to run out of gas.
Anyway, thank you for your work
A post was merged into an existing topic: Venus OS beta v3.53~2 available for public testing
Hi all, available per today, v3.60~15.
Change log is available above.
Have a good night.
3 Likes
Off topic, but youâre not a 9 tot 5 person it seems 
Just wanted to share that I waited to test this specific version (v3.60~15) because your merged a few fixes from the linux kernel related to canbus
(been struggling with this for 4 months now, decided to make a venus with linux 6.x because I know it works, but while doing this I saw the current commits and decided to wait)
Before this version I had problems with my rpi zero 2 w and a new waveshare pi hat
I got stuff like this:
[ 52.157476] IPv6: ADDRCONF(NETDEV_CHANGE): can0: link becomes ready
[ 52.167715] NOHZ tick-stop error: Non-RCU local softirq work is pending, handler #08!!!
[ 53.040857] mcp251xfd spi0.1 can0: bus-off, scheduling restart in 100 ms
[ 53.047739] NOHZ tick-stop error: Non-RCU local softirq work is pending, handler #08!!!
[ 53.167475] IPv6: ADDRCONF(NETDEV_CHANGE): can0: link becomes ready
[ 54.038527] mcp251xfd spi0.1 can0: bus-off, scheduling restart in 100 ms
[ 54.045380] NOHZ tick-stop error: Non-RCU local softirq work is pending, handler #08!!!
[ 54.164644] NOHZ tick-stop error: Non-RCU local softirq work is pending, handler #08!!!
[ 54.177464] IPv6: ADDRCONF(NETDEV_CHANGE): can0: link becomes ready
[ 55.038128] mcp251xfd spi0.1 can0: bus-off, scheduling restart in 100 ms
[ 55.187477] IPv6: ADDRCONF(NETDEV_CHANGE): can0: link becomes ready
[ 56.040062] mcp251xfd spi0.1 can0: bus-off, scheduling restart in 100 ms
[ 56.197468] IPv6: ADDRCONF(NETDEV_CHANGE): can0: link becomes ready
And it didnât work
After the update - the canbus works!
I still get
[ 54.164644] NOHZ tick-stop error: Non-RCU local softirq work is pending, handler #08!!!
But it doesnât seems to break something
Found this issue if you want to take a look
So thank you, I can now continue to finish my setup
3 Likes
A post was split to a new topic: 360~15 How to set inverter status
@BartonB good to hear and thanks for letting us know 
Noted and reproduced @Markus_001, weâll fix that.
Thank you for reporting
Good day, per just now weâve made v3.60~16 available for public testing.
Changelog above.
1 Like
A post was split to a new topic: DESS selling to grid
3 posts were split to a new topic: V3.60~16 feature request mode schedule