bbs-fw icon indicating copy to clipboard operation
bbs-fw copied to clipboard

Sport mode sometimes switches to standard mode without command

Open CitizenDev opened this issue 2 years ago • 4 comments

I have noticed 2 occasions now where firmware has dropped from sport to standard without me giving required input which is PAS 0 + Light button.

I was also not on PAS 0 at these moments.

Light sensor has been turned off on 850C display unit.

CitizenDev avatar Sep 09 '22 16:09 CitizenDev

Can pretty much only happen if there was a reset/crash/hang... Will likely be hard to find. A watchdog is enabled to reset if program hangs for 600ms.

Any more info, did you notice it the moment it happened? Just doing steady riding using pedal assist?

danielnilsson9 avatar Sep 10 '22 06:09 danielnilsson9

I'm not sure how much additional info I can currently provide because there isn't anything indicating the change except the PAS & throttle changes so I probably did not notice it instantly because it happened at lower speeds.

My standard has throttle turned off and speed limited to 25kmh. So then I was going less or around 25 with PAS only there was nothing to indicate that it happened. Both times I noticed when throttle no longer worked.

Btw, just a bit unrelated but can it be configured so that after system restart / error last used profile would be used? Currently it will always revert to standard. I would much prefer it to stay in sport until I change it myself. And If I changed to standard, it also would remain active until change input is given.

CitizenDev avatar Sep 10 '22 12:09 CitizenDev

Any additional crashes? Let me know if you have been able to see any connection to a specific use case.

danielnilsson9 avatar Sep 23 '22 16:09 danielnilsson9

Sorry I haven't driven my bike recently because of crap weather. I'm not sure how much I will be driving at winter. But i'll definitely keep u posted when I get to drive.

CitizenDev avatar Sep 24 '22 16:09 CitizenDev

This is likely related to #114 and the same solution should apply. A communication error with the display could cause this behavior since fallback was to return to standard mode if an invalid mode switch command was received, checksum of received command was not verified either.

danielnilsson9 avatar Jul 05 '23 11:07 danielnilsson9

Most likely fixed in #153

danielnilsson9 avatar Aug 01 '23 18:08 danielnilsson9