This post was last edited by yang_alex on 2018-7-4 19:41 Advanced Task: Comparative Evaluation of New and Old Versions of Motor Driver Library In general, in recent years, ST's STM32 embedded development platform has implemented a strategy based on STM32CubeMX and HAL/LL libraries. This strategy can make ST's STM32 embedded development platform easier and better support ST's numerous STM32 series. This trace can also be seen in motor driver development. Originally, the development of STM32 was based on the standard peripheral library, so the previous FOC4.3 was based on the standard peripheral library, and now STM32 is based on STM32CubeMX and HAL/LL libraries, so the current SDK5 is based on STM32CubeMX and HAL/LL libraries. Based on this point, many changes are easy to explain: 1. FOC4.3 uses conditional compilation to be compatible with different series of control boards when generating code, which makes it difficult to read the source code and difficult to maintain. SDK5.0 uses the mature STM32CubeMX plus the HAL/LL library of each series of MCU to generate the required code, and does not add the unnecessary parts, so the maintenance is much smaller and it is very smooth to read. 2. Because of this, SDK5.0 now directly generates the entire project when generating code, while FOC4.3 needs to manually copy the files and libraries generated by Motor Workbench to the corresponding directory. By the way, SDK5.0 supports more software development environments (IDEs). 3. ST is becoming more and more open. FOC4.3 has a lot of code provided in the form of libraries, and now SDK5.0 has more code provided in the form of source code. 4. The organization of the code has changed. FOC4.3 is based on classes, and now SDK5.0 is based on components.
Default Task: Suggestions and Feedback on SDK5.0 After such a long evaluation, ST's motor driver SDK5.0 is still very powerful and is a powerful tool for developing motor drivers! I won't say much about recommendations and praises, good things speak for themselves! Netizens who have read the previous posts are probably attracted by ST's motor driver SDK5.0 and can't help but want to try it out quickly. Based on the previous trial, I would like to make some suggestions: 1. Combined with the "empty document" I found in my previous evaluation, ST can check where the problem is. It's not terrible to have a problem, but why there is no error prompt, it is estimated that there is still a bug in the software code. Give prompt information so that developers can find the problem and solve it. Otherwise, you can only guess and try randomly. If you are lucky, you can find it out, but if you are unlucky, you will be stuck there. 2. The interface of Motor Workbench and
STM-STUDIO needs to be improved. I don't ask for more fancy, but the key content on the interface should be clear to everyone. I believe that software developers can see it clearly on their own computers. However, engineers all over the world have computers of various models and screen sizes. Using better human-machine interface technology will help solve this problem. Here is a picture for you to feel. (I deliberately used full screen, you can see that it is not because there is not enough space)
Zoom in and see that some content is blocked.
3.
How can the plotter function in Motor Workbench only display the motor speed? Wouldn't it be better to allow developers to customize the display content like in STM-STUDIO? 4. The sampling points of STM-STUDIO display graphics are too few, probably due to the limitation of ST-LINK. It would be better if there were a higher-speed sampling tool option. In this way, the curve is smoother and closer to reality. 5.
Integrate a PID debugging function in Motor Workbench, which will surely be welcomed by developers. In general, the flaws do not outweigh the merits. I hope ST can bring us more and better development tools! This content is created by yang_alex, a netizen of EEWORLD forum. If you need to reprint or use it for commercial purposes, you must obtain the author's consent and indicate the source