lizardmech
10 W
- Joined
- May 19, 2017
- Messages
- 67
casainho said:lizardmech, I started this thread to discuss the developement of firmware for KT and BMSBattery motor controllers.lizardmech said:I think you're having issues with this because the controller is not running any sort of FOC control scheme. I don't see how you can try and reference any sort of d,q point when there is no point where data from the controller is converted to a 2 axis coordinate.
Refer to this article discussing FOC vs sinusoidal commutation https://www.controleng.com/single-article/got-field-oriented-control-in-your-servosthis-article-includes-online-material/37ab28025a3dd3e9ab551567b510795a.html
You are not welcome here. Please don't start again, leave and start a new thread to discuss that topic.
It is enough what you did on EUC forum. I will just ignore you.
Umm what exactly did I do on the EUC forum? Please elaborate. It's impossible for people to develop the firmware if they're operating under the incorrect impression that they're fixing an issue with FOC, transforming 3 phase current and voltage data into a 2 axis coordinate system for a FOC control loop is fundamentally different to this controller. It may in fact be possible to develop a sinusoidal controller with good performance but understanding the differences in how they operate is crucial. In addition to inductance and resistance you may need to contend with factors such as any rotor saliency or rise time and latency of hall sensors etc. While FOC is computationally expensive it's popular because as long as it's provided with motor values and the rotor position its quite robust. Prior to modern DSPs and MCUs adoption of 3 phase BLDC/PMAC motors was less common due to the difficulty of controlling them without the computational power to do FOC which had been around since the 1980s.
If you think anything I have posted is scientifically incorrect or somehow not relevant to maximizing torque per amp of a sinusoidal motor controller please point it out.