Everyone, I'd say release 3.3.005 is due. 3.3.004 was 03/2024, we've since collected quite some fixes and new features, including extensions for Smart EQ & the new MG4 support. There are lots of new Smart users now, as Mercedes have stopped support for the official Smart EQ App (see https://www.smart-emotion.de/article/415-mercedes-discontinues-smart-eq-app-...). The current state is also very stable, I had no issue reports. Any objections / open fixes or additions that should be included in 3.3.005? Regards, Michael -- Michael Balzer * Am Rahmen 5 * D-58313 Herdecke Fon 02330 9104094 * Handy 0176 20698926
We delayed the release due to the CAN bus crashing issues initially assumed to be related to the new poller: * Simon Ehlen (Ford Focus Electric, in development) * Derek Caudwell (Leaf) * Chris Box (Leaf) * Developer from Jokela (Leaf) * on Github: Jaroslav Horak, with detailed bus analysis by Richard Taylor (Leaf) o → https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/issues/980 I've lost track of the current status of the different issues & investigations. My current impression is, none of the tested software/config changes actually had any impact. Richard Taylor found out the Leaf issue with boots & reboots of the module is triggered by the switched off SN65 transceiver. But it's still unclear why that happens, why a terminator doesn't help and why it only seems to affect the Leaf (what about the Ford Focus, Simon?). So this points to some hardware issue, possibly something more on the Leaf than the OVMS side. The SW changes meant to minimize SN65 off time are not yet complete, there's a Housekeeping init change to be tested & possibly added (see github issue). Did the changed CAN timing to better follow the SAE recommendations actually have any benefits? I currently don't think so. Developer From Jokela posted:
After this change poller now sends tx commands, compared to before when it did not. … but that claim didn't match the statistics and wasn't confirmed.
Simon, is it correct the poller filter additions solved your issues, and the changed timing didn't have any effect? Richard still needs to test the timing change, but the Leaf issue is clearly correlated to boots/reboots. So, does/did anybody see any positive effect from the SAE timing patch? Besides the SN65 control enhancement, is there anything else open that needs to be included in 3.3.005? Thanks & regards, Michael Am 14.01.25 um 13:35 schrieb Michael Balzer via OvmsDev:
Everyone,
I'd say release 3.3.005 is due. 3.3.004 was 03/2024, we've since collected quite some fixes and new features, including extensions for Smart EQ & the new MG4 support. There are lots of new Smart users now, as Mercedes have stopped support for the official Smart EQ App (see https://www.smart-emotion.de/article/415-mercedes-discontinues-smart-eq-app-...).
The current state is also very stable, I had no issue reports.
Any objections / open fixes or additions that should be included in 3.3.005?
Regards, Michael
-- Michael Balzer * Am Rahmen 5 * D-58313 Herdecke Fon 02330 9104094 * Handy 0176 20698926
I'm still hunting the regression that causes high hologram usage. My search so far shows: 3.3.004-298-gd00134c2 16Nov24 good 3.3.004-327-ge8bac6d4 31Dec24 bad I just built/booted 3.3.004-323-gbc1f75c9 (24Nov24). I've been letting test versions run at least a few days before checking the hologram dashboard usage graph. But I must admit, once I found a version that I got the charges down from $45/month (back to ~$5/month), I've been less aggressive in my testing. Craig
On 2025-04-06 11:03, Michael Balzer via OvmsDev wrote:
Did the changed CAN timing to better follow the SAE recommendations actually have any benefits?
I haven't experienced any Leaf errors using the SAE timing over the past month. As a result my intention is to continue with this new timing, although I can't prove the timing is the reason for the lack of issues. I also improved 12 volt levels. If you're looking for hard data, please advise what I should do to gather that data. It's not particularly clear to me, because I understand that "normal" can bus statistics for the Leaf include some expected errors. Thanks Chris
Chris, as you changed two parameters at once, you cannot currently tell which helped. I suggest keeping the improved 12V level and returning to the old CAN timing to see if that makes a difference. Reviewing your report & findings, I'd say your issue was caused by the 12V dips. Regards, Michael Am 11.04.25 um 20:01 schrieb Chris Box:
On 2025-04-06 11:03, Michael Balzer via OvmsDev wrote:
Did the changed CAN timing to better follow the SAE recommendations actually have any benefits? I haven't experienced any Leaf errors using the SAE timing over the past month. As a result my intention is to continue with this new timing, although I can't prove the timing is the reason for the lack of issues. I also improved 12 volt levels. If you're looking for hard data, please advise what I should do to gather that data. It's not particularly clear to me, because I understand that "normal" can bus statistics for the Leaf include some expected errors. Thanks Chris
-- Michael Balzer * Am Rahmen 5 * D-58313 Herdecke Fon 02330 9104094 * Handy 0176 20698926
Mark, everyone, as we don't make any progress on the CAN issues (affecting only few users), and "main" users struggle with bugs that have long been fixed in "edge", I'd say we release 3.3.005 now. Regards, Michael Am 12.04.25 um 09:37 schrieb Michael Balzer via OvmsDev:
Chris,
as you changed two parameters at once, you cannot currently tell which helped.
I suggest keeping the improved 12V level and returning to the old CAN timing to see if that makes a difference.
Reviewing your report & findings, I'd say your issue was caused by the 12V dips.
Regards, Michael
Am 11.04.25 um 20:01 schrieb Chris Box:
On 2025-04-06 11:03, Michael Balzer via OvmsDev wrote:
Did the changed CAN timing to better follow the SAE recommendations actually have any benefits? I haven't experienced any Leaf errors using the SAE timing over the past month. As a result my intention is to continue with this new timing, although I can't prove the timing is the reason for the lack of issues. I also improved 12 volt levels. If you're looking for hard data, please advise what I should do to gather that data. It's not particularly clear to me, because I understand that "normal" can bus statistics for the Leaf include some expected errors. Thanks Chris
-- Michael Balzer * Am Rahmen 5 * D-58313 Herdecke Fon 02330 9104094 * Handy 0176 20698926
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
-- Michael Balzer * Am Rahmen 5 * D-58313 Herdecke Fon 02330 9104094 * Handy 0176 20698926
On 7/13/25 01:31, Michael Balzer via OvmsDev wrote:
as we don't make any progress on the CAN issues (affecting only few users), and "main" users struggle with bugs that have long been fixed in "edge", I'd say we release 3.3.005 now.
Am I really the only one who sees a 10X increase in cellular usage when running anything newer than 3.3.004-313-g78a49a59? I've been busy with other projects but the last time I looked at this I was having trouble testing git hash/versions in chronological order. I have been running 3.3.004-323-gbc1f75c9 without issue and I *think* 78a49a59? is the next hash and I tested that it's problematic for me. Craig
Craig, I know of no other reports regarding increased traffic. But there are few using MQTT, who also need to monitor their data volume, so maybe you're just the only one noticing. Yet I still think testing in chronological order is not going to produce sensible results, as you mix unfinished intermediate commits from different development branchs, their commit order normally does not match the chronological order of each other or of the master branch. As written before, you need to concentrate on single branches when doing that. The recommended tool for narrowing down bugs by commits is git bisect. In your case, 78a49a59 is not a master commit, it's one part of pull request #1081. Just as an example, commit 98606bb5304a5c2b832ffbb0d26391a632e5fc17 is dated after 78a49a59 but was added to master before. So it doesn't make any sense to test 78a49a59, unless you're on the #1081 development branch. Use gitk, git log --graph, or similar to view the branch/commit associations. Regards, Michael Am 13.07.25 um 19:08 schrieb Craig Leres:
On 7/13/25 01:31, Michael Balzer via OvmsDev wrote:
as we don't make any progress on the CAN issues (affecting only few users), and "main" users struggle with bugs that have long been fixed in "edge", I'd say we release 3.3.005 now.
Am I really the only one who sees a 10X increase in cellular usage when running anything newer than 3.3.004-313-g78a49a59?
I've been busy with other projects but the last time I looked at this I was having trouble testing git hash/versions in chronological order. I have been running 3.3.004-323-gbc1f75c9 without issue and I *think* 78a49a59? is the next hash and I tested that it's problematic for me.
Craig
-- Michael Balzer * Am Rahmen 5 * D-58313 Herdecke Fon 02330 9104094 * Handy 0176 20698926
Michael, No objection from me. I think we’re 1,264 commits past 3.3.003. Let me know what you need from me. Regards, Mark.
On 13 Jul 2025, at 4:31 PM, Michael Balzer via OvmsDev <ovmsdev@lists.openvehicles.com> wrote:
Signed PGP part Mark, everyone,
as we don't make any progress on the CAN issues (affecting only few users), and "main" users struggle with bugs that have long been fixed in "edge", I'd say we release 3.3.005 now.
Regards, Michael
Am 12.04.25 um 09:37 schrieb Michael Balzer via OvmsDev:
Chris,
as you changed two parameters at once, you cannot currently tell which helped.
I suggest keeping the improved 12V level and returning to the old CAN timing to see if that makes a difference.
Reviewing your report & findings, I'd say your issue was caused by the 12V dips.
Regards, Michael
Am 11.04.25 um 20:01 schrieb Chris Box:
On 2025-04-06 11:03, Michael Balzer via OvmsDev wrote:
Did the changed CAN timing to better follow the SAE recommendations actually have any benefits?
I haven't experienced any Leaf errors using the SAE timing over the past month. As a result my intention is to continue with this new timing, although I can't prove the timing is the reason for the lack of issues. I also improved 12 volt levels.
If you're looking for hard data, please advise what I should do to gather that data. It's not particularly clear to me, because I understand that "normal" can bus statistics for the Leaf include some expected errors.
Thanks Chris
-- Michael Balzer * Am Rahmen 5 * D-58313 Herdecke Fon 02330 9104094 * Handy 0176 20698926
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com <mailto:OvmsDev@lists.openvehicles.com> http://lists.openvehicles.com/mailman/listinfo/ovmsdev
-- Michael Balzer * Am Rahmen 5 * D-58313 Herdecke Fon 02330 9104094 * Handy 0176 20698926 _______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
Mark, everyone, I've just tagged the 3.3.005 release, created the maintenance/backport branch "release-3.3.005" and published the build as "edge", "pre" and "eap" on my server. I'll release this as "main" in a week, unless eap/pre users report issues. Announcement: * German: https://dexters-web.de/firmware-release-3.3.005-text_115.htm * English: https://dexters-web.de/firmware-release-3.3.005-text_115.en.htm Mark, I suggest following up accordingly on your server. Regards, Michael Am 17.07.25 um 02:06 schrieb Mark Webb-Johnson:
Michael,
No objection from me. I think we’re 1,264 commits past 3.3.003.
Let me know what you need from me.
Regards, Mark.
On 13 Jul 2025, at 4:31 PM, Michael Balzer via OvmsDev <ovmsdev@lists.openvehicles.com> wrote:
Signed PGP part Mark, everyone,
as we don't make any progress on the CAN issues (affecting only few users), and "main" users struggle with bugs that have long been fixed in "edge", I'd say we release 3.3.005 now.
Regards, Michael
Am 12.04.25 um 09:37 schrieb Michael Balzer via OvmsDev:
Chris,
as you changed two parameters at once, you cannot currently tell which helped.
I suggest keeping the improved 12V level and returning to the old CAN timing to see if that makes a difference.
Reviewing your report & findings, I'd say your issue was caused by the 12V dips.
Regards, Michael
Am 11.04.25 um 20:01 schrieb Chris Box:
On 2025-04-06 11:03, Michael Balzer via OvmsDev wrote:
Did the changed CAN timing to better follow the SAE recommendations actually have any benefits? I haven't experienced any Leaf errors using the SAE timing over the past month. As a result my intention is to continue with this new timing, although I can't prove the timing is the reason for the lack of issues. I also improved 12 volt levels. If you're looking for hard data, please advise what I should do to gather that data. It's not particularly clear to me, because I understand that "normal" can bus statistics for the Leaf include some expected errors. Thanks Chris
-- Michael Balzer * Am Rahmen 5 * D-58313 Herdecke Fon 02330 9104094 * Handy 0176 20698926
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
-- Michael Balzer * Am Rahmen 5 * D-58313 Herdecke Fon 02330 9104094 * Handy 0176 20698926 _______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
-- Michael Balzer * Am Rahmen 5 * D-58313 Herdecke Fon 02330 9104094 * Handy 0176 20698926
3.3.005-1 is now in "main" on my server. Regards, Michael Am 18.07.25 um 09:15 schrieb Michael Balzer via OvmsDev:
Mark, everyone,
I've just tagged the 3.3.005 release, created the maintenance/backport branch "release-3.3.005" and published the build as "edge", "pre" and "eap" on my server.
I'll release this as "main" in a week, unless eap/pre users report issues.
Announcement:
* German: https://dexters-web.de/firmware-release-3.3.005-text_115.htm * English: https://dexters-web.de/firmware-release-3.3.005-text_115.en.htm
Mark, I suggest following up accordingly on your server.
Regards, Michael
Am 17.07.25 um 02:06 schrieb Mark Webb-Johnson:
Michael,
No objection from me. I think we’re 1,264 commits past 3.3.003.
Let me know what you need from me.
Regards, Mark.
On 13 Jul 2025, at 4:31 PM, Michael Balzer via OvmsDev <ovmsdev@lists.openvehicles.com> wrote:
Signed PGP part Mark, everyone,
as we don't make any progress on the CAN issues (affecting only few users), and "main" users struggle with bugs that have long been fixed in "edge", I'd say we release 3.3.005 now.
Regards, Michael
Am 12.04.25 um 09:37 schrieb Michael Balzer via OvmsDev:
Chris,
as you changed two parameters at once, you cannot currently tell which helped.
I suggest keeping the improved 12V level and returning to the old CAN timing to see if that makes a difference.
Reviewing your report & findings, I'd say your issue was caused by the 12V dips.
Regards, Michael
Am 11.04.25 um 20:01 schrieb Chris Box:
On 2025-04-06 11:03, Michael Balzer via OvmsDev wrote:
Did the changed CAN timing to better follow the SAE recommendations actually have any benefits? I haven't experienced any Leaf errors using the SAE timing over the past month. As a result my intention is to continue with this new timing, although I can't prove the timing is the reason for the lack of issues. I also improved 12 volt levels. If you're looking for hard data, please advise what I should do to gather that data. It's not particularly clear to me, because I understand that "normal" can bus statistics for the Leaf include some expected errors. Thanks Chris
-- Michael Balzer * Am Rahmen 5 * D-58313 Herdecke Fon 02330 9104094 * Handy 0176 20698926
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
-- Michael Balzer * Am Rahmen 5 * D-58313 Herdecke Fon 02330 9104094 * Handy 0176 20698926 _______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
-- Michael Balzer * Am Rahmen 5 * D-58313 Herdecke Fon 02330 9104094 * Handy 0176 20698926
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
-- Michael Balzer * Am Rahmen 5 * D-58313 Herdecke Fon 02330 9104094 * Handy 0176 20698926
participants (4)
-
Chris Box -
Craig Leres -
Mark Webb-Johnson -
Michael Balzer