Will fix! I actually read your great suggestions. But when developing and testing I noticed that with enough debounce time I had time to switch assist level without disengaging Walk Assist. Was almost like a feature that I thought would be appreciated when going uphill or in challenging terrain. The assistance does not have to disengage to increase or decrease the assist level. And it is set so that if there is a single button bounce it will not change anything. But if there are multiple bounces it will change.thineight wrote: ↑Aug 27 2019 2:46amYes, I mentioned this "issue" in one of my previous posts:buba wrote: ↑Aug 26 2019 2:46pmGood points! Will fix and deactivate the button events during Walk Assist and Cruise!Rafe wrote: ↑Aug 26 2019 1:26pmI think you may need to look at the debounce again. As you asked I have tried A8 out on the route that I use walk assist. Very steep steps in flights of about 6 or 7 steps cut into a cliff. I set assist level to 9 at the bottom as I always do and lifting the front wheel up to start each flight and pushing the saddle to help get some traction I also always use panniers and run a heavy bike. Then I noticed that the assist was getting weaker and weaker and this was because the assist level had dropped down to 5 so I upped the assist level back to 9 and it was not long before the assist level had fallen down again. When I got to the top I discovered that this was due to fast finger bounce on the walk assist button (the down button) manually lowering the assist level.
- during the w.a. the DOWN button should not change the current assistance level
- of course the brake sensors shall reset everything, if activated
The use of the DOWN button shall of course be restored once the walk assist is interrupted (whether if brake sensors are applied or just the DOWN button is released for the proper amount of time).
At this point I will wait directly the A9 to test the latest features (I'm currently on A7).
However, I understand that this is maybe not that necessary so will of course disable the buttons! Maybe only disable the DOWN button and keep the other buttons active? Regardless, I understand the problem reported and will fix!