Survey | We can help you overcome the difficulties in motor drive!
[Copy link]
 For those who want to learn motor drive, a great opportunity is here~
The popularity of motor drive is self-evident. EEWorld and Anqu Technology hope to provide you with some unique information and make the motor drive section the center of technical exchanges! In order to do a good job in this section, we hope to understand your R&D needs in motor drive, so we specially made this questionnaire.
Note: All information is visible only to the original poster. There are a lot of questions, but if you want to join the motor drive industry or have difficulties in the motor drive industry, please be sure to fill out the questionnaire in detail (see the questionnaire entrance at the end of the post). We will formulate our motor learning strategy based on the questionnaire results. The more detailed the questionnaire, the more likely you are to get targeted help.
Preface:
Currently, the motor drive industry is on an upward trend. Engineers who can develop motor drives can easily find jobs and have relatively good salaries. For example, drones, scooters, twisting cars, balance cars, fascia guns, etc. were all once popular products.
The product solutions mainly come from MCU manufacturers and solution companies. The motor-driven MCUs mainly include the ARM series represented by ST, including M0, M3, M4 cores plus motor-driven peripherals. In recent years, MCU manufacturers that make motor drives have sprung up everywhere. In addition to being compatible with the pintopin of ST chips, there is even a register compatibility, which means that the product code does not need to be changed and can be directly replaced and burned.
The MCU launched by Fengqi uses 8051 as the application development core, adopts FPGA to complete the most resource-intensive FOC drive calculation, and integrates the bridge drive and power supply. This integrated solution has really become popular in the sensorless FOC application of fans. Nanjing Lingou launched the M0+DSP core+bridge drive+power supply. M0 is used as an application development platform, and DSP is used for FOC drive calculation to improve efficiency. Lingdongwei launched the M0+coprocessor+bridge drive+power supply. The multiplication and division operations in the FOC that also occupy resources are completed by hardware to improve efficiency.
For software solutions, there are two types: open source code and closed source code. The open source code comes from the solutions of foreign manufacturers a few years ago. For example, Ti's FOC open source solution used in servo motors. ST's FOC2.0 open source solution in the consumer field. At present, the source code of domestic ARM core MCU manufacturers and solution companies is basically based on FOC2.0 as the software solution blueprint for improvement and upgrade.
Whether it is the MCU manufacturer or the solution company, the core things are only in the hands of the key technical personnel of each company, and the solutions provided by each company are in the form of closed libraries, not open source. A popular saying in the industry is "If you don't use open source, you don't use it, and if you use it, it's not open source." It's quick to learn and become familiar with a solution, but it's hard to master it well. It's relatively difficult to make a good product quickly.
Since the products are completed in layers based on the core engineers, and the source code is usually closed and not open to junior engineers, the ideas, methods, parameters, etc. of different manufacturers' solutions will be different when debugging the same motor, which is mainly influenced by the core engineers. Generally speaking, if the new product is closer to the product developed by the solution, the debugging will be faster and the probability of product success will be greater.
This section is mainly for embedded software engineers who develop brushless motor FOC drive control. Software engineers for motor drive development can be divided into three categories, including:
1) Core engineers, who are the technical core of each solution company and the original factory, are responsible for the underlying driver, as well as the control algorithms, program architecture, production testing, etc. of different products. They are responsible for the overall technology of the product.
2) Application development engineers, based on the core engineer's program, adjust performance parameters, write programs to achieve motor position, speed, torque control, as well as functions, safety protection, etc. Responsible for the function and performance of the product.
3) Production test maintenance engineers, based on the application development engineer's program, adjust some parameters, write human-machine interface programs, and product working logic, complete product production testing and after-sales service, etc.
One of the directions of the section is for early application development engineers and production test maintenance engineers, whose experience and foundation are quite different, and they are the part of the system starting from scratch. The
second direction is problem-oriented, introducing some technical routes, motors, drives, and some easily confused concepts, for application development engineers and core engineers with certain experience.
The third direction is the solution direction. According to the products completed by the combination of directions 1 and 2, the software, hardware and debugging solutions related to the product are launched. If the engineer's project is similar to these products, it can not only quickly realize product development but also deepen the understanding from the system.
In order to be more targeted, do a questionnaire survey: >> Click here to fill in the questionnaire (before filling in, please read the preface above carefully.)
| 
提升卡
变色卡
千斤顶
京公网安备 11010802033920号
