The speed table is speed-dependent, not cadence-dependent. Even if you modify the speed table, it has no effect on engine behavior, that's why the FT project was created..
Developer info
Interesting point, but after looking at your table and the README I do not see any clear indication that the assist logic is actually speed-dependent.
In the documentation you mainly change torque related parameters (start torque / max torque / return torque) and current limits, as well as battery limit values.
This looks very similar to parameters that can also be modified with OpenBafangTool, which I have tested myself. The changes did not only affect ride feel, but also resulted in measurable differences in power output shown on the display.
One thing that is often overlooked is that after changing parameters the sensors may need to be recalibrated.
If torque / speed / wheel settings are not calibrated again, the motor behaviour can appear unchanged even though the values were actually written to the controller.
The table labeled as “speed table” does not seem to contain actual speed values, but rather torque thresholds and current settings, so I am not sure how this proves that assist is controlled by speed instead of cadence.
Could you explain in more detail where exactly in the firmware the speed dependency is implemented?
I could not find a clear proof of that in the thread you linked either.
Also, the official specifications mention support up to about 120 rpm cadence, which would suggest cadence-based control at least to some extent.
From my testing, some parameters clearly influence the motor behaviour, while others (for example max current) seem to remain internally limited, so I am trying to understand which parts of the control logic are actually affected.
.
