Powerstep01 burned out

[Ellison]

I am using Powerstep01 for stepmotor driving , comminucate with stm32H743 via SPI , and using x-cube-spn3's firmware for testing (IHM03A1_ExampleFor1Motor), but after initial function running , motor can not run. and after reset the power , powerstep01 is alway burned out .   below is the schematic , Does someone could help to check what's the issue ? (VS=24V , VCC=3.3V)

[Ellison]

I found the pin9 (SENSEB_S)and pin20 (SENSE_A)is dirrectly to ground , do you think this is the key point for the problem? 

[Peter BENSCH]

Welcome @Ellison, to the community!

Thanks a lot for sharing the schematic.

Yes, wiring the current‑sense pins directly to ground is almost certainly the root cause of the failures:

• SENSEB_S (pin 9) and SENSE_A_S (pin 20) are both connected straight to GND in your design.
• On the official ST boards (e.g. X‑NUCLEO‑IHM03A1) these pins are never tied directly to ground. Each phase uses a small sense resistor (in the tens of milliohms range) to ground, and the device measures the voltage drop across this resistor to control and limit the motor current.

By shorting the sense pins to ground:

1. The chip cannot sense the phase current correctly
2. Over‑current protection will not work as intended
3. Very high, uncontrolled current can flow in the power stage, which can very easily destroy the POWERSTEP01 at power‑up or as soon as the motor is enabled

Regards
/Peter

[Ellison]

@Peter BENSCH , Thanks Peter for your kindly and quickly response.

I checked the datasheet , it seems when when sensea_s and senseb_s pin tie to ground could work in voltage mode .

I change the initial code to voltage mode .

the chipset did not burned out . but the motor still can not work . 

and I notice that

(1) FLAG pin and always LOW . 

I try to read back the register value to check what the issue . the status =0x0100. 

the MAX_SPEED value is 0 after power up 

Any idea to find out the issue ? Thanks in advance.

 

 

 

 

[Ellison]

more hardware information in my board :

pin54(ADCIN) = 0.459V

pin56(VBOOT) = 23.76

pin57(CP) = 9.58V

pin58(VCC) = 14.81V 

pin60(VCCREG) = 3.3V

pin61(VSREG) = 23.74V

pin62(VREG) =3.3V 

VS = 23.72V

VDDIO =3.3V 

 

[Peter BENSCH]

Right: in voltage mode tying SENSEA_S and SENSEB_S to GND is allowed and should not, by itself, damage the device - provided all other voltage‑mode components (Rs, Ra/Rb, Cvs, boot‑strap network, etc.) follow the data sheet reference design.

Regarding the current behaviour:

• STATUS = 0x0100 means only the SWITCH turn‑on event is set (bit 8 = 1), no UVLO, OCD, thermal or stall flags. So the device is not reporting a fault that would prevent motion. Remember that reading STATUS also clears the flags; after you read it once, check its value again during operation
• MAX_SPEED = 0 after power‑up is expected: all motion parameters (e.g. ACC, DEC, MAX_SPEED, FS_SPD, KVAL*, etc.) must be written after each power‑up / reset.
  With MAX_SPEED = 0 the motor will not move even if you send a RUN or MOVE command.

Do a minimal test sequence in voltage mode and read back MAX_SPEED, STEP_MODE, KVAL_* and CONFIG to verify they are actually written.

Regards
/Peter

P.S. Please do not insert code as a screenshot, but use the button </> (Insert/Edit code sample).

[Ellison]

Today , I got one IHM03A1 board for testing , fly wire to my board . but unfortunately , still some issues . 

(1)I changed "CURRENT MODE" in the firmware . on the first time power up, It seems everything works fine .and motor could run. below is my test code version :

==============

/**************************************************************************//**

  * @file    powerstep01.c

  * @author  IPC Rennes

  * @version V1.6.0

  * @date    June 4th, 2018

  * @brief   Powerstep01 motor driver (Microstepping controller with power MOSFETs)

  * @note    (C) COPYRIGHT 2016 STMicroelectronics

  ******************************************************************************

 =============

(2)but after one or 2 times later, it works become unnormal , and the SPI comunication is not correct, and It could not read back the correct parameters in debug mode (using JLINK). some times motor run,some times not . :( .

(3)I thought the hardware of SPI interface is good. (because I could use to drive other brand's motor driver very well) (4) My platform is STM32H743VIT, sysclk is 480MHz, Do you think you could help to give me a simple test code ? so that I could find out what's the problem ,

 

Thanks in advance. @Peter BENSCH