would you be happy with one parameter, that defines an exponent? You could trim the curve to a progressive or a degressive characteristic. Just one 8bit parameter would be all we need to be user defined. Orange: exponent = 0.3, green: exponent = 2
I think it will be great, I have to try it.
you can play around with the online GDB debugger meanwhile
That's done now also. The field "Speed Limit Enabled" in the canable tool is used for the exponent. The value is divided by 100 internally.
Tested. "Speed Limit Enabled" field can only be set to 0 or 1.
OK, then we have to ask @mdi, if he can make the field freely editable, or choose another parameter. But there are not many 8bit fields without function left...
I've set the exponent to the field "Cadence Sensor Signals / Rotation" now, but I don't have tested, if this field is editable freely.
I checked it out. It's set up fine, and it's working. I'll take it for a test drive tomorrow. Thanks!
Are you now getting to the stage that the EBICS firmware is now so different to the the Bafang firmware and getting mature in development enough to just have an EBICS version of the Canable Pro with the correct naming of the parameters, it would make it a lot easier for any new users ?
I think easier would be to have double labels. And for new custom parameters create separate tab.
Yes, it would be possible to add both descriptions, mayby two lines in different colours. As the GUI is a HTML file, you can edit it quite easily. But I don't know, if @mdi will do this service for the EBiCS project. Of course, someone else could do this scut work and submit a pull request.
<th style="display: inline-block;">
<div style="color: black; text-align: right;">Cadence Sensor Signals/Rotation</div>
<div style="color: blue; text-align: right;">Throttle exponent * 100</div>
</th>I've done it for the controller tab, the Assist (Full) Tab is still missing.
github.com
Great news! The torque sensor is very sensitive at the beginning of the range. I think it can be limited even further if needed, without a noticeable reduction in sensitivity.
yesterday try to flash the firmware with besst tool and works, but no assist on motor. And Besst tool pro can't read the controller and off course the parameter can' be changed. So I revert back to original Bafang firmware. Wait for my canable arrive.Then your display is not sending the button down flag with the CAN protocol. The button down pulls down the voltage on the On/Off button pin to a certain value so this analogue voltage would have to be checked. I simply returned to the old logic, where you don't have to hold the button, but just have to switch to the walk mode level.
I guess, you didn't increased the decay parameter from the default setting? I've set the default value to 255 now and have the integral part is reset as soon as the iq setpoint is zero.
I've set the PI control parameters a little less agressive.
The attached bin file is not tested!
Yes, and you can return to the original Bafang firmware at any time.
I don't know, if someone ever tried to set the parameters with the BESST tool also. Maybe this works also even
Edit:
I went for a test ride, I'm quite satisfied with the behaviour now
I had to set the multiplier to 20 to get sufficient assistance in sport mode, but that's just the process of fine tuning the parmeters to your personal preferences. The M820 bootloader seems to erase the whole flash memory on the firmware update, so you have to restore all your personal settings after flashing. The position sensor calibration has to be redone also. That's different to the BL3 and BL38, they don't erase the memory page of the virtual EEPROM. That's more convenient of course.
Sometimes the setpoint drops quite sharply, I don't now why, but you don't notice that during riding. Perhaps I'm really pedaling that unevenly ....
View attachment 388567
Thank you for your feedback, on which motor you did your tests? There are quite a few inconsistencies in what you've said:
The Walk Assist works, as long as the display is sending the walk assist level and the speed shown in the display is lower 6kph.
This parameter don't has to be user settable, as there are different bin files for different motors anyway. If the cadence reading on the M820 is not correct actually, we can simply correct it with the next release.
I never "felt" something unstable, there are a lot of logs of real test rides in this thread where you can see how the motor and battery current control works.
This is not a matter of the EBiCS firmware, but a general issue with any firmware file.
?! The allowed power is ramped down lineary with the temperature between 110 and 130 °C.
In EBiCS the source code is availabe freely and everyone who is interested, can read in detail how each function works and can contribute improvements.
Hello. Please specify which motor and firmware version you are referring to. Of what you have indicated, only a couple of points are true for the M510/M560 motors:
Only m820.
There is a wiki page about the normal ride mode:
github.com
I've updated the tab also, but I want to test it with the canabale connected, before I submit a pull request...
Looks much better with left align.
github.com
github.com
github.com
Hm, the M820 bin file has not the increased torque threshold yet to prevent the motor from running without effort from the rider when some thermal drift of the torque signal happens. So it should work with low torque on the pedal and low cadence quite good. Can you log the debug data? Then you could check, if the iq setpoint gets zero, or if the calculated setpoint is just very low. Both would need different measures to improve the behaviour.
