Hi all,
v3.70 is back out for public testing.
Change log added above!
2 Likes
SignalK 2.15.x please, please
2 Likes
Battery Percentage missing from Overview Display on 3.70~32
It does appear on device detail display ok, just not the overview.
2 Likes
When will it be possible to disable peak shaving?
1 Like
Thanks for another set of promising features (and fixes).
1 Like
A feature request for the next release, not specific to 3:70…
I have 4mA-20mA pressure sensors on tanks on the boat, which have current levels defined for empty (e.g. 5mA=0%) and full (e.g. 10mA=100%).
Due to things like temperature variation, these can sometimes read <0% when the tank is empty or >100% when it’s full. In this case the reading disappears and isn’t updated any more in either VRM or remote console, sometimes for several days.
Can these readings be clipped to 0%/100% instead?
1 Like
Some issues I noticed when trying out 3.70~33 today…
The GX relays do not show up in device list when set to manual (also running a GX IO Extender 150, which may have some bearing on this).
One of my tank levels also disappeared, but returned when reverting firmware
1 Like
Have you checked the status in those cases?
Probably it is detecting a sensor issue, like open circuit or short circuited? And please check the raw sensor value as well.
Btw it does sound a but unusual, for a 4-20mA sender, quite the industrial type usually, to behave like this?
1 Like
It’s not that It’s open or short, just that it’s gone outside the currents which are set as 0% and 100%. For example the black tank 0% level missing set as 4mA – it’s a pressure sensor at the top of a tube, 4mA should be atmospheric pressure. But if there’s some “water” at the bottom of the tube not flowing.out it might read 3.9mA. Similarly when it’s full, 100% is the current when the tank is full (e.g 8mA), but if it overfills the inlet pipe starts to fill and the reading can go above this (e.g. 8.5mA). In either case VRM doesn’t read anything, the sensor “disappears” and updates stop.
1 Like
Good morning! Per last night already, v3.70~34 is available for public beta testing. Details above!
1 Like
I cant find the setting controlling this
@mpvader the name configured in the cerbo for the CANbus battery is not being pulled into VRM or some settings pages after changing the connected battery, although it is using the same VRM instance as the previous bettery.
explained:
instance 512 has been BRAND A battery on my system for some time.
I have since disconnected this, and put in place BRAND B.
the VRM instance remained the same, at 512.
the name has been changed in the device > name menu.
This displays in the breadcrumb bar at the top, but the device list still shows the old name, as does VRM (in the main page as a battery monitor in the rectangular box, but the VERM device list shows the new name).
A function to “refresh” the data of all VRM instances would be nice. 
1 Like
Hey, heads up: later tonight we’ll put v3.70 aside, for v3.66 beta testing.
A bit quickly this time, its because there are a few improvements that we prefer to have out asap.
1 Like
Does 3.66 have any release notes?
1 Like
15 posts were split to a new topic: Alpha beta and official release discussion
Yes! Available now; as well as the update itself.
1 Like
Sorry but no. We need to have those point releases tested on many systems as well.
I’m aware it’s a bit much this time.
1 Like
The 3.70 beta isn’t gone forever, it will be back after 3.66 has been released and you can go back to testing.
Just be a bit patient.
3 Likes
I installed v3.70~34 on three of my systems. Two of the systems work fine, but my 3-phase ESS system with Pytes batteries constantly cycles with no data on the Touch 50, then data, no data, etc. and the inverters are in pass-thru mode. It’s as if it’s losing and reconnecting to the Pytes batteries, but the Pytes device always shows in the device list. Reverting back to ~26 solves the issue. The other two systems use Victron batteries and BMS’s and no issues.
1 Like
ha Matthijs, a bit awkward response from your side… I for one am on 3.77.32. When I read about the .34 i wanted to update but could not because it only offers 3.66 beta. To avoid distrubiong the DESS setup and history I do not go back to a 3.6x beta while already running a 3.7x beta. So this means I will stick with the old 3.77 beta and cannot test anything further… I’m fine with that but but it will not help you in getting ‘as much testers for the 3.66 beta.
1 Like