I finally got my "DIY" motor controller with ePaper display on my M600 eMTB working well enough for a weekend of riding. Pictured here with the friends' dirtbikes I was able to keep up with during 4000 feet of elevation gain (30 amps through the motor helps with that!). Thanks again to
@casainho for making my bikes so much more fun to ride!
I came back with a bunch of ideas for improvement, but one I'm a little stumped on is occasionally the motor would halt and jerk a few times when downshifting during a hard hill climb (and then would come back after a few seconds). VESC is still on sensorless, so I will try an encoder... but anyone else have any ideas?
I want you to post pictures details of your build, otherwise I will not believe
Yes, anything wrong driving the motor will cause VESC protection, and that is a very positive thing to protect everything. With my limited experience, I would say that at the very low motor RPM, as you said at "during a hard hill climb", the sensorless algorithm do not work so well and will probably put high currents on the motor/battery and then VESC turns off the motor temporary.
I would try to change the configurations about sensorless... I understand you may not have a Bluetooth module installed, as I don't have due to space restrictions on M500 case. But I have on my Fiido Q1S seated scooter, that is great to look and real time data, log the data and change configurations.
And by the way, I started using the display communication with wireless (ESPNow) and it works well, at least since last week I am being using it.
About that eink display, I bought one for other project and it have a delay of 3 minutes for a new refresh... so for sure you are using a different one, I would say with at least 1 second refresh??
And here is my Fiido Q1S seated micro scooter, where I use a VESC FlipSky 75200, with a 80V battery and 150A motor phase current!! but it runs at very high speed like 160kms/h this little 12 inches direct drive hub motor.