Read all the tecnhical information here: https://opensourceebikefirmware.bitbuck ... velopment/apple2 wrote: ↑Feb 12 2019 5:29pmOk, I read the document and although I didn't understand all of it it seems that all phases are centered around 50% duty cycle when the commanded duty is 0. Is there any good reason behind this?stancecoke wrote: ↑Feb 09 2019 4:02pmThere are several approaches how to calculate the SVPWM pattern.
You can't switch off any channel as we are using center aligned PWM. Zero in the lookup table does not mean zero DutyCycle on the phase wire. Look at the figure 31 of ST's User Manual 1052.
Glad to hear, that you are happy with our firmware
I actually tried changing this so that 0 duty is actually 0 duty on the phase and the controller seems to work fine. That way 1/3 of the mosfets are not switching which should increase efficiency... I have tested this on a 6 fet (because I didn't want to mess up my 18fet) and tried it up to 20A and works ok. So I have ben getting good results from the firmware on both 6 fet and 18fet. The pwm off when idle feature also works fine although its mentioned as experimental.
Another thing I tried is decreasing the dead time (from 16 to which happily didn't cause burnt mosfets but caused something strange that I have no explanation for: the duty cycle (setpoint) never drops below 20 even with no torque request and throttle at 0. Requested current and actual current values are both 0 (or -0.1) so I don't see where that duty is coming from. The wheel is actually rotating slowly.. until I stop it with the brakes and duty goes to 0. Then after the next throttle application it is stuck at 20. I am only using throttle and no pas or torque sensor. Any ideas why that could be happening or how to debug?
https://opensourceebikefirmware.bitbuck ... mware.html