Update:

for those interested, we got some insight into the BMS bug from someone involved in the Smart development or testing, explained here:
https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/issues/1405#issuecomment-4776519467

We saw two bug events in June prior to implementing the poll timing shifts (released June 24), so far none since. These events took 3 weeks to turn up, so we'll continue monitoring for another week.

From the data collected, Zorg could narrow down the Smart BMS firmware version affected to SW version 0472. It seems the bug has been fixed in later releases, based on these findings Zorg has posted a recommendation:
https://www.smart-emotion.de/forum/thread/7818-xsq-bms-id-ident-data-info-sammelung/?postID=95995#post95995

Regards,
Michael


Am 28.05.26 um 21:38 schrieb Michael Balzer via OvmsDev:
Everyone,

in case you're wondering: we need to delay the main release due to a critical issue reported last week.

https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/issues/1405

While we still don't know if the OVMS / Smart EQ module actually took part in triggering the BMS bug, we need to be sure we've checked and addressed all possible cases that could match the (quite meager) "explanation" given by Mercedes and the most credible assumptions found in the forums, before releasing a new main version.

We also want to make sure the alerts for the condition are working reliably, and all essential indicators of the bug are collected, so hopefully some correlation can be found with some more field data.

Regards,
Michael


Am 19.05.26 um 08:51 schrieb Michael Balzer via OvmsDev:
Andreas,

I tend to delaying publishing to "main" to include the fix, as it seems this is close to done.

Regards,
Michael


Am 19.05.26 um 07:43 schrieb Andreas Jansson:
Mark, Michael 

Heads up: the vwegolf module merged for 3.3.006 has a CAN bus bug. AC charging triggers a
TWDT reset loop, module reboots every few seconds while plugged in.

Background: during capture analysis I saw KCAN-typical IDs (BMS SoC, gear) showing up on
FCAN, and concluded the J533 gateway was merging KCAN traffic onto FCAN. So IncomingFrameCan2 blanket-forwards every FCAN frame into the KCAN handler. The right read
is: J533 bridges a small number of IDs selectively (e.g. 0x131 SoC during DC charging when
the BMS goes quiet on KCAN), not wholesale traffic merging. Wrong assumption, wrong fix.

That alone wouldn't kill anything, but it exposed a latent mcp2515 bug where the acceptance
filter doesn't persist past Start(), so the ISR takes ~860 fps of FCAN instead of the 4-5
IDs we actually decode. Both bugs together = watchdog reset loop on AC charge.

Two fixes in flight (drafts):
- #1403 — mcp2515: persist acceptance filter across power cycles (framework-level)
- #1404 — vwegolf: drop the forwarding, install proper hardware filter, decode FCAN signals
where they belong (depends on #1403)

Mark already commented on #1403 with a cleaner approach — refactor incoming once design is
confirmed. Hardware-verified on my module.

Up to you whether to hold main, drop vwegolf from the tag, or ship + fix in 3.3.007. Sorry
for the trouble.

Sincerely,
Andreas


_______________________________________________
OvmsDev mailing list -- ovmsdev@lists.openvehicles.com
To unsubscribe send an email to ovmsdev-leave@lists.openvehicles.com

-- 
Michael Balzer * Am Rahmen 5 * D-58313 Herdecke
Fon 02330 9104094 * Handy 0176 20698926


_______________________________________________
OvmsDev mailing list -- ovmsdev@lists.openvehicles.com
To unsubscribe send an email to ovmsdev-leave@lists.openvehicles.com

-- 
Michael Balzer * Am Rahmen 5 * D-58313 Herdecke
Fon 02330 9104094 * Handy 0176 20698926


_______________________________________________
OvmsDev mailing list -- ovmsdev@lists.openvehicles.com
To unsubscribe send an email to ovmsdev-leave@lists.openvehicles.com

-- 
Michael Balzer * Am Rahmen 5 * D-58313 Herdecke
Fon 02330 9104094 * Handy 0176 20698926