STM32 MCUs Motor control

Hello,I need confirmation that the Hall Delay in the below waveform i have taken is 180Degrees. Hall sensors are 120Degrees apart as below in the diagramI find the motor running in reverse direction. 

Hello!I am trying to connect the B-G483-ZEST1S and STEVAL-IPM30B boards together for motor control. The connectors on the two boards have a different number of pins. Is there a ribbon cable that connects these? Or should these two boards not be used to evaluate the SLLIMM module?Thanks,DJ

Hi, I am working on developing a new motor driver using ST motor control.I am trying to understand current sensing circuitry (three shunt resistors) but I don't understand the offset circuitry as shown in this picture: As I currently understand it this R1/R2/R3 circuitry is there to add a voltage offset so that when there is reverse current the shunt resistor generating negative voltage. But what I don't understand is that this offset voltage(in the reference designs I have looked at) that offset voltage is very high (2 volts) because it is still being amplified by the Opamp resulting in a way to high ADC voltage??What am I missing here?

Hi,I recently purchased the STEVAL-IPMM15B motor control board and am studying its schematic (Figure 7 as attached). However, I am having trouble understanding the role of certain resistors in the circuit.From my analysis:R44, R45, and R46 appear to be pull-up resistors.R47, R48, and R49 seem to function as current-limiting resistors.R50, R51, and R52—their purpose is unclear to me.I have the following questions:If SW13, SW14, and SW15 are open (disconnected) and H1/A+ of J5 provides a HIGH signal (+5V), will M_phase_A output a HIGH signal (+5V)?If SW13, SW14, and SW15 are closed (connected) and H1/A+ of J5 provides a HIGH signal (+5V), will M_phase_A still output a HIGH signal (+3.4V)?Can R50, R51, and R52 be considered a voltage divider circuit along with R47, R48, and R49 (i.e., R47 in series with R50, R48 in series with R51, and R49 in series with R52)? or R50, R51 and R52 serve as another purposes?I appreciate any clarification on how these components interact.Thanks you.RegardsYW

Hello Everybody,MCSDK:6.3.0CubeMX: 6.1.1Workbench : 6.3.0CubeIDE : 1.15.0 When using Workbench to regenerate the FOC code, the additional peripheral settings I configured in CubeMX, such as IO, Timer, and ADC, are all cleared. As a result, I have to manually reconfigure them every time. Could you please provide a solution to avoid this issue? Thank you.I remember that in earlier versions of Workbench (v5.4.x), there was an "Update CubeMX" button after generating the code. Pressing this button would preserve the additional peripheral settings. Could you please advise where to enable this feature in the current version?

Hello,I am currently working with MC Workbench 6.3.2.I have a 2Pole pair motor 4800kV and I want to use the 6 step algorithm and Quasi-Synchronous Rectification.In this configuration I can only make open loop because :- When Sensing BEMF during PWM OFF phase --> Speed estimation is incorrect  (and very unstable)- When Sensing BEMF during PWM ON phase --> Speed estimation is correct I don't understand why the speed estimation in incorrect because the motor is running fine, so it commutes at the right time and the speed estimation should be ok ?Here is a video to illustrate the issue :  And this is my configuration in open loop :Any advice ?Thanks for your help !Xavier

Hi Recently, I am working on a 3-phase hub motor with hall sensor to be able to drive low speed accurately. I came across the EVSPIN32G4 and works fine with sensorless-PLL speed sensing by using the MC Workbench V6.3.2. I precedeed to modify the hardware board to a single-shunt resistor (Instead of 3 shunk resistors)When changing the speed sensing to hall sensing, I started to see driver protection fault errors. Occasionally when I start ST Motor Pilot V1.2.12, the Driver Protection flickers between Orange and red, with no way of clearing the fault condition, unless I reset the STSPIN32G4 (Reset button). I tried increasing the Driver protection digital filter duration (Default 47.06 ns) to 941.18ns but it made no difference.I tried unplugging the hall sensor, but the fault condition still happens. I checked the cubeMX code configuration and the driver protection pin (PE15) is set to Open drain with pull-up. I later found out that it's something to do with boot-up is

I used the G431 to configure the HSO correctly, passed the Profiling test step, and the closed loop also started and stopped the motor correctly.However, there are cases where the startup is unsuccessful: when starting with Pol.Pulse, sometimes the motor will reverse, and sometimes it will stop after a few swings. PulseDuty has been adjusted to 0.97.It is found that when running Observing, for example, the angle displayed at the beginning is 300 degrees, and after manually rotating the motor axis, the position will change, but it will eventually stop at about 300 degrees, regardless of the actual position of the motor. What do I need to adjust to make the position observation correct?

Hello Everybody,MCSDK:6.3.0CubeMX: 6.3.0Workbench : 6.3.0CubeIDE : 1.15.0I encountered an issue after generating FOC code using Workbench v6.3.0.I then used CubeMX to configure PB15 as ADC2_IN15 to read the torque sensor voltage.However, after regenerating the code in CubeMX, I observed two problems:1) The configuration for ADC2_IN15 was not automatically generated by CubeMX. I had to manually set it up. Is this expected behavior?2) During initialization, I first measured PIN PB15 using a multimeter, and its voltage level was 0.7V (which is the correct baseline voltage for the torque sensor).However, once the program executes MX_MotorControl_Init();, this pin is pulled up to 3.3V.I checked Workbench, and this pin does not appear to be used by the FOC configuration.How can I resolve this issue? Please help me...Note: In the FOC code generated by Workbench, ADC2 uses injection mode, while the additional ADC I configured uses regular mode.

getting following error while generatingMotorControl reference pack not found: "../../../../Middlewares/ST/MotorControl"I have STEVAL SPIN3202 board for controlling BLDC motor in FOC mode, but while generating I got this error, please guide.

Hello,This is my first post here, and just putting it out there from the start, I am no expert in electronics. I am looking for some guidance on putting together a small temperature controller for an EV vehicle conversion. What I am missing is a simple controller that will measure temperatures of two cooling loops and use PWM signals to control two pumps, a heater, and switch on a fan. Below is a more detailed description. BTW if this is not the right place to post this, by all means let me know. I am using a LM7805 along with the recommended two capacitors to power a Nucleo-L432KCI am reading out 2 automotive temp sensor, supplying a 5V reference signal and reading out the resistance through a voltage divider setup (R1 & R2). I am not sure yet the total resistance required to ensure not to exceed 3.3V at A0 and A1 as I have to get the sensor and measure their resistance/voltage over the temperature rangeI use 3 2N2222 transistors with 2 resistors each to level shift the PWM s

Hello,I am currently using High Sensitivity Observer (sensorless) mode for speed sensing in my project.When the motor is running and I turn OFF the power, the motor continues to rotate due to inertia.If I turn the power ON again while the motor is still spinning and attempt to restart the motor, the control becomes unstable. Even if I completely stop the motor and then try to run it again, the control remains unstable.It seems that when the MCU is powered on while the motor is still moving, there is an initialization issue affecting motor control. Q:1. Is there a way to handle this issue and ensure stable motor control after a power cycle?2. Are there recommended methods to properly reinitialize the motor state when power is restored while the motor is still spinning? Any guidance on how to avoid this issue would be greatly appreciated.Thank you!  

Hello i want to build a drone esc. So I need to control 4 bldc motors with a mcu. How would i do this? In the MC Workbench i can only select 2 Motors max.

Hi, I'm currently using the STMC Board Designer but seem to be unable to create a "Bridge" board. I was hoping to use this to create a temp pinout into connecting 2 IHM08-M1 power boards to a Nucleo-H755ZI-Q evaluation board. The documentation on the BRIDGE section isn't clear as well.  I tried adding a new board but am unable to select Bridge here:  Then I tried creating a .json for a Bridge board but I'm unable to import it because I'm unable to select the bridge section. Import failed due to "type board not match" which makes me assume that he's only able to import Control board since that tab is selected. Could you guys help me out into creating a Bridge board? 

Hi,What happens if I want to use high side driver this way: Thank you,Tim

Hello all,I have an application in which I want to control four BLDC motors independently using the FOC. I want to use a STM32G484 for this. The question now is how I can distribute the interrups so cleverly that I can control all motors with 16kHz without them blocking each other.Many thanks for your answers :) 

I am using a small outrunner motor to try to use  Motor Profiler.  When I select Start Profile, it times out as shown in screen below.  I have only enabled Potentiometer feature.The pole pairs is 11, and the snapshot below shows max speed also changed to a lower value of 4000 since the default of 16000 also did not work. I also lowered max current to 20 A, but of no use. Since I could not get Profiler to work, I tried to spin the motor after closing the Profiler. Changing potentiometer settings ( from low to high) did  not spin the motor.  I then enabled ESC and disabled the potentiometer feature, regenerated the code, built and programmed the board.  Using an Arduino board, I generated a PWM signal with  a period of 490 hz and  high time of 1218 us, which should have armed and start spinning the motor, but nothing happens according to the user manual. I want to check that the kit that I got is working.  Any hel

Hello Everybody,MCSDK:6.3.0CubeMX: 6.3.0Workbench : 6.3.0Motor Pilot : 1.2.9Power Board : IHM08M1(Rshunt=0.01Ω)Control Board : NUCLEO-G431RBMotor : BLDC 26w 24v/8 pole pairs / rpm=4k / rated current=1.8A/hall sensor Currently, I am testing the motor startup using Open Loop Voltage Mode and then switching to Torque Mode (SMO + PLL). However, when switching to Torque Mode, the motor fails to spin, yet no error codes are triggered.I suspect that this might be due to the fact that in Open Loop Mode, the motor does not rely on electrical angle feedback, whereas in Closed Loop Mode, accurate electrical angle synchronization is required. This could lead to an electrical angle desynchronization issue, preventing the motor from operating correctly after switching.If this is the case, what possible solutions could be implemented to address this issue?Or are there any other potential causes that might be contributing to this problem?

I have designed a board similar to B-G431B ESC1 kit and using the FOC code from the motor control work bench. But at present i have an issue where the Gate to Source Voltage is equal to Bus Voltage (VDC) instead of the 12V. What could be the problem? The Mosfet driver IC i am using is 2ED2182S06FXUMA1.  

Hello, I have a custom motor controller that I've developed that uses the STSPIN32G4. After a bunch of goof ups I finally managed to get it configured, presumably correctly, in the MC Workbench Board Designer. However once I upload the compiled program to the board, I cannot connect to it using the motor profiler or motor pilot software. I have checked that I have the right baud rate (115200), I've enabled motor profiler in the project, and I've tested my UART connection with CubeProgrammer (which functioned as expected). I'm wondering what the issue is? My assumption is that if I have UART communication at the correct baud rate with CubeProgrammer, then the only issue could be in software somewhere because ASPEP just isn't getting a response beacon. My assumption could be totally wrong though and I could have also configured something wrong in hardware. Just let me know if you have any ideas as to what could be going wrong, or if you need any more information to diagnose. Thank y

I see in the schematic the potentiometer is referenced on pin 25, however I only see the PWM firmware setup example. Can someone point me to the correct setup?

I am trying to control a 24V PMSM type motor using ST Motor Control Workbench version 6.3.1 with the FOC.I have run Motor Profiler and then gotten the electrical and mechanical parameters.I have three questions and can anybody help/answer them?I am running Motor Profiler without load? Am I doing correct?When creating a project using Motor Control Workbench, do I need to update the inertia and friction coefficients in the motor stage depending on the load (please see attachment)? If the answer is no, where should I include the inertia and friction of the load in the project?May I measure PMSM type motor inertia and friction coefficients with load? If yes, how can I do it?Thanks in advance.

Dear All, I am developing a high-voltage motor driver using the Nucleo-H563ZI  with the STEVAL-IPM30B.I have set up the entire hardware and want to first verify whether the voltage output is normal (using SVPWM).My three-phase outputs are not connected to anything; they are floating. I am using a differential probe to check the voltage (specifically, the line voltage UV).When the duty cycle is below 85%, it appears normal, as shown in the image below.It is a nice sinusoidal voltage.   However, when the duty cycle exceeds 85%, the voltage output starts to show abnormalities, as shown below for the cases of 85% and 100%. I have confirmed that my PWM signals are still normal at 85% and 100%, so I believe the issue lies with the IPM rather than the control signals. Since it is a bootstrap circuit, I believe the issue lies in this part. I checked the bootstrap capacitor voltage(TP4 to phase_A). When the system is normal, the bootstrap voltage is around 12.

Hi everybody,First of all I don't have experience in FOC.I have profiled the motor, and the procedure was succesfully completed.I use the motor profile to create a FOC project.When I try to start the motor using the Motor Pilot an Overcurrent Error appen (in both mode speed and torque).Now in normal motor drive the closed current loop regulate the 3-phases motor current by monitoring the current and comparing it to the setpoint created with torque reference respectto the electrical motor angle, this means that if no short circuit is present, is not possible to get Overcurrent error.Now in FOC the electrical angle before the motor start must be generated in some way that is not clear to me.I try to change some paramiter as suggested in the help of Overcurrent error, but nothing change.Any try give always Overcurrent error.Using an osclilloscope to investigate, no current flow to the motor phases but systems give this error.Board is ok because with 6 step methode everything work correct.

Hello everyone,I’m working on a project where I am using the motor controller’s current sense circuitry (shunt + op amp). Here are my key details:1. Hardware Setup:- Board: X-NUCLEO-IHM08M1 with NUCLEO-H755ZI-Q- Op Amp: TSV994- Shunt Resistor: 0.01 Ω, 3 W rating (from BOM)- Supply: 12 V, measured ~0.45 A from the power supply2. Observations:- At no load (no supply connected, only 3.3 V to the controller), the amplifier output is around 1.65–1.7 V, which I treat as the zero-current offset.- When I measure actual load with the 12 V, 0.45 A supply, my code calculates 8–9 A from the ADC, which seems impossible because the supply is only delivering ~0.45 A total.- I attempted to validate the amplifier gain using resistor ratios and the op amp datasheet. It suggests a total gain of around 13.7.- I also used the approach of “maximum possible voltage” across the shunt (0.01 Ω) with a 3.3 V rail, concluding ~13–14× hardware gain.- Yet, the measured “current” is far too high compared to the actu