I had an issue with 3.80~4 that made me switch back to 3.70, although I need the peak shaving fix very much. In my case 3.80~4 sent integer values to the Cerbo for target SoC in stead of decimal values. Is this fixed in 3.71 beta? I will try of course.
Please keep to the beta topic instructions and create dedicated topics, please don’t add to the main release notes topic. It makes for confusing and hard to follow requests. We’re trying to avoid locking it. Thanks.
1 Like
@nickdb I was not sure, because this was not an issue yet, but a question about the release. So I was in doubt were to put in.
I tried 3.71~2 anyway, and I see decimal values, so that is correct and I expect charging later to run smoothly
Glad it is resolving the issue. You should be safe to run on the 3.71 beta as it is focused on the fixes for 3.70 so shouldn’t see any other major changes that could cause issues.
Hi Nick,
I had an issue with 3.80 beta with integers for SoC plan. I was curious if this was also in 3.71 beta, since Jeroen stated that this release is almost identical to 3.80~5 beta.
Dirk-Jan Faber confirmed that integer values will be abandoned totally in 3.80. So I will step into the beta program again as soon as that has been done. Maybe they are gone already, but I did not find it in the release notes.
Hi,
3.70 and 3.80+ will use decimal values, you can switch right now 
Technical side-node: Whenever the gx is restartet, it will first start with an integer-soc-assumption. As soon, as it “sees” a decimal soc value, it’ll switch to use decimal precision for targets.
So, restarting during a extended phase on 100% or minsoc may cause dess to stick with the integer assumption for a while, if the BMS reports a round value (20.0 or 100.0) for an extended period.
2 Likes
Interesting, sees from what/where? I tried to figure it out from github but I got lost, could you provide a hint on where to look?
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.