STM32 MCUs Motor control

Hello. I'm using B-G431B-ESC1 to operate drone motorThe operation was successful using FOC, but from 28,000 RPM and above,it changes to - speed as seen on the Pilot screen. (When the rpm becomes negative, speed control becomes impossible.)In fact, using betaflight, I have seen it go up to 45,000 rpm.Any idea how I can change the minus speed or what I need to change?? 

Can anyone help me understand how these two arrays have been made#define M1_ANGC                            {-116,-363,-611,-843,-1091,-1338,-1571,-1833}#define OFST {0,17,51,99,167,252,348,474}these arrays are used in MTPA calculation with y=mx+c equation.These are the motor parameters for which the array has been calculated. Your assistance will be appreciated.

Hello,I am below Hardware and Software setup:Hardware:MCU Board: NUCLEO F401REPower Board: X-NUCLEO IHM08M1BLDC Motor: Portescap 22ECP45-8B-154.01 (specifications_22ecp45.pdf attached)Software:MC Workbenach v6.4.1I am using sensorless FOC (STO-PLL) in WorkBench tool. I am trying to increase the speed of the motor to its MAX 47000 RPM. But, I am getting only 7200 RPM with Parameters from Motor Datasheet in MC Workbench tool. I have changed the HW to short 3-SHUNT and removed mentioned capacitors.Below are my parameter configurations:

Hello,I am using STM32 Motor Control SDK / MC Workbench with sensorless FOC (STO + PLL) to drive a low-speed, high-inertia 24V 40W BLDC fan motor.Power Board: X-NUCLEO-IHM07M1Issues observed:Motor rotates stably but produces intermittent (not continuous) rubbing noise, mainly after settling at certain RPM.Large speed oscillations are visible in Motor Pilot (speed dial deviation).Motor does not reach max speed even when increasing current limit in MC Workbench.Reducing Iq PI gains(cut off frequency) does not significantly reduce the noise.Very low PLL gains are required for stable rotation; higher PLL gains cause oscillation or loss of speed feedback.

Hello. I try to start a new project with two non-listed motors in Workbench. I use two gimbal 3-phase BLDC motor with encoder AS5048A https://cdn.sparkfun.com/assets/d/6/b/5/8/27477_27478_Datasheet.pdf Based on the motorShinano.json file, I built my own JSON file, please see below. However, I have the following questions. What to write in the compatibility: "sixStep"? The motor has the encoder. Hence, should TRUE be for HasHallSensor? I use a Pololu power board (voltage regulator) https://www.pololu.com/product/5576 and two Sparkfun 3-phase BLDC motor drivers https://www.sparkfun.com/sparkfun-brushless

Hi,How can one calculate the maximum phase current of a BLDC motor using sinusoidal control with the nominal voltage and power of the motor?I have a 36 V / 560 W motor.Is the peak current equal to:560 W / 36 V * SQR(2) =  22 Aor beacuse of the star topology of the motor:560 W / 36 V / SQR(3) * SQR(2) = 16.33 AI need this to select the proper FETs.Thanks!

Hi,Currently I am evaluating HSO [High Sensitivity Observer (Sensorless)] in our custom Inverter board () with B-MOTOR-PMSMA1 motor. But when I start the motor it jerks and giving Over Current SW Fault. Our custom board has following key components.Infineon 6ED2230S12TXUMA1 gate driverMCS1806GS-3-30-Z Current sensor 

Hi,Could you please let me know where I can download the 3D CAD model (e.g., STEP/IGES) of the EVSPIN32G4-DUAL evaluation board?Thank you!Best regardsPelino

Hello. I have been researching how to use the STEVAL-ESC002V1 with a NUCLEO-F031K6 board to run a BLDC motor. The documentation mentions using the IAR Embedded Workbench for ARM 8.22, but I am programming with the STMCubeIDE and the MotorControl Workbench 6.3.2. Could someone help direct me on how to do this?

Hi - What is the best algorithm for a very low speed and low current application, <50 RPM and <1 Amp with a high resolution encoder (~4096 counts per revolution) on a 3 phase brushless motor? Do the HSO or ZEST algorithms provide any advantage over the standard FOC algorithm when running with an encoder like this? I'm assuming the FOC algorithm is better than the 6 step algorithm, is that correct? Are there any other tips for this application? Thanks

Dear ST Technical Support Team,I am currently working with the EVSPIN32G4-DUAL evaluation board.I understand that this board uses a single-shunt current sensing topology, and therefore the Motor Profiler feature in Motor Pilot is not available (Profiler requires three-shunt current sensing with STO-PLL).In this context, I would like to ask for ST’s recommended procedure to obtain the following motor parameters when using EVSPIN32G4-DUAL:Stator resistance (Rs)Inductances (Ld / Lq or equivalent)Back-EMF constant (Ke)Could you please advise:Whether ST recommends specific manual measurement methods for these parameters with single-shunt hardwareWhich Application Notes or User Manuals describe this procedureAny best practices for entering these values into MC Workbench for stable FOC operationThank you for your support.Best regards,Hyunseok

 I am currently working with the EVSPIN32G4-DUAL board and have a question regarding the I2C pin configuration.According to the EVSPIN32G4-DUAL schematic, the I2C signals are connected to pins PC4 and PA8.However, when generating a project using MCSDK version 6.4.1 and checking the pin mapping, the I2C interface is assigned to PC9 and PC8.When I modify the project to change the I2C pins from PC9/PC8 to PC4/PA8 and then update the firmware image, the system does not operate correctly.Could you please clarify the reason for this discrepancy between the schematic and the MCSDK pin configuration, and advise on the correct way to configure the I2C pins for this board?

If this is configured incorrectly, will it trigger overcurrent protection?   

Hello all,I am planning to purchase the EVLSERVO1 to control an industrial three-phase PMSM servo motor (rated 220V AC) for a hobby project. I will be running it at a lower voltage and accept the speed loss.The motor has a 17-bit absolute encoder using RS485 physical layer (protocol is currently unknown, likely proprietary, which I plan to reverse engineer).The EVLSERVO1 manual states: "The 120 Ohm termination resistors R84/R85 must be removed if termination is embedded at encoder side." My encoder has a built-in 100 Ohm termination resistor.While I understand the manual's instruction to prevent double termination, I would prefer not to modify a new board if possible.If I leave the resistors on the board, the parallel combination results in a ~54.5 Ohm load. Given that I plan to use a short cable (< 1 meter), is the EVLSERVO1's transceiver robust enough to drive this lower impedance without signal collapse? Or is the "must remove" warning critic

Good day,I'm trying to get motor profiler running on an X-Nucleo-IHM17M1. The only compatible Nucleo board I have is a F303RE.To enable the motor profiler application, it requires the selection of 3 shunt current sensing. According to this link, it seems that both the IHM17M1 and F303RE support 3 shunt current sensing.Yet, when I try and configure the project, only single shunt is available. This is not the case for the other Nucleo bo

I am currently evaluating the X-NUCLEO-IHM16M1 motor control expansion board and would like to ask whether it is suitable for measuring the electrical parameters of the motor described below.The motor specifications (translated from the datasheet image) are as follows:Rated Voltage: DC 24 VRated Torque: 0.063 N·mRated Speed: 4,000 RPM ±10%Rated Current: < 1.7 ARated Output Power: 26 WNo-load Speed: 5,000 RPM ±10%No-load Current: < 0.3 ANumber of Poles / Phases: 8 poles / 3 phasesInsulation Class: Class BOperating Temperature: –10 °C to 40 °CAccording to the X-NUCLEO-IHM16M1 documentation, the maximum output current is specified as 1.5 A RMS. 

Motor Proiler 识别无刷空心杯电机的时候，卡在28%,套件用的是 Translation: When the Motor Profiler identifies a brushless coreless motor, it gets stuck at 28%. The kit uses...  

Dear ST Support Team,We are using the STM platform in our motor controller for the past one year. Our controller is developed for the automotive EV application.Currently, we are facing challenges at the software and code level related to motor control performance and optimization. We are stuck with code-level improvements and require technical support to analyze and fix the issues completely.We are looking for guidance and support on:Motor control software optimizationCode-level improvements and debuggingA complete and stable software solution suitable for automotive EV requirementsWe request your support from the STM motor control software team to help us resolve these issues.Please let us know the next steps to proceed further.Regards,Govind Dhongadi

Hello,I am new to STM and have been using TI MCUs in the past for motor control. I am considering using STM for a new project. I need to be able to control 5 BLDC motors with position control. They will each have their own closed loop control but will be somewhat be intertwined. I would like to start with an STM dev board and start with the control of one motor and move to more then continue to develop my own PCB. Any guidance on MCU selection/dev board selection would be greatly appreciated. And any suggestions on example projects to start with and easily modify for 5 motors. Also, I would like to know if it is possible to use absolute encoders for the motors rather than incremental for the position feedback. Thanks you!

HelloI am working on an academic research project involving a hybrid converter topology, where a controlled shoot-through state is intentionally required as part of the converter’s operating principle.I am currently using:STM32F446REIHM16M1 inverter driver boardMCSDK (Motor Control SDK)From my understanding, the IHM16M1 gate driver enforces hardware-level interlocking and dead-time, which prevents simultaneous conduction of the high-side and low-side devices in each inverter leg. Even when overlapping PWM signals are generated at the MCU level, the driver appears to mask them internally.My question is:Is there any supported or undocumented method to override or bypass the hardware interlocking / cross-conduction protection on the IHM16M1 board?I would like to clarify whether:This limitation is strictly hardware-bound, orAny alternative c

We noticed that the Overcurrent warning appears even when Overcurrent Protection is disabled. Could this be related to the missing feedback capacitors C38 and C42 on the OPAMPs for current sensing? Thank you for your support.Best regardsPelino

Hi Everybody!At this time I would like to use two EVAL6498L board for a DC brushed motor, (H-bridge setup).Selected mosfet is: IRFZ34NPBF.Selected PWM frequency: 20kHz width the STM32G431 MCU.The PWM signals are generated on the GPIOs, and I’ve verified that they reach the driver’s HIN and LIN pins. The low-side MOSFETs switch correctly, but the high-side MOSFETs won’t turn on. The bootstrap capacitors are charged to about 12 V (measured directly across the capacitor leads). The control table is the following:TIM1 chDriver InputForwardRevers1A LINForced HighForced Low2A HIN

my mcsdk ver is 6.3.2，I want to driver my BLDC moto with steval_esc001v1,but the moto will stop and shake after 3-phases speed up. as the motor shake,and bus voltage(current) shakes.i want to know the Possible causes and how shuld to solve it.my motor is a2212， 2200kv ，7pole pairs，7.4V - 12.6V。appendix is my stwb6 filesthanks a lot。

 Hello ST Support Team,While reviewing the current sensing configuration of the EVSPIN32G4-DUAL board, I noticed a mismatch between the schematic and the description shown in Motor Control Workbench.In Motor Control Workbench, the current sensing section explains the presence of resistors related to the current sensing configuration.However, when I check the EVSPIN32G4-DUAL schematic, it is difficult to identify where these resistors are located, or which components correspond to the description shown in the tool.Could you please help clarify the following

Dear All, I just stat to evaluate the MC SDK. My platform: MC SDK v6.3.0, NUCLEO-H563ZI, X-NUCLEO-IHM08M1. Have anyone know what's the difference between "Dead Time" and "SW Dead Time" as follow figure?Per it's default configuration, (SW dead-time is 850ns,  dead time is 1000ns), what is the exact value of dead-time to the power stage?Best Regards,