RadekS
Hi Radek,
Dusty and I used the EVBs,MTRCKTSPNZVM128, to drove the customer's motor together.
(1) We can drive the motor to 2000 rpm in the beginning. After run the motor about 4~5 times (Starting, accelerating to 1000~2000 rpm, and setting to 0 rpm by FreeMASTER to stop), the MCU was very hot, and finally burned.
Because the fault happened suddently, we didn't know what kinds of fault happened, and can't use FreeMASTER to catch some waveform/situation. Two EVB MCUs were burned.
(2) The project code we used was MTRCKTSPNZVM128 software released on official website (http://cache.nxp.com/files/product/software_tools/MTRCKTSPNZVM128-SW.exe) The EVB is 700-27485 rev X3. Carcassonne chip is 1N95G.
(3) The motor is 2 pole-pair and 4000rpm rated. The motor widing is delta-connection.
U-V, R=38.31mΩ, L=0.10050mH
V-W, R=38.01mΩ, L=0.10243mH
U-W, R=37.92mΩ, L=0.09947mH
The motor parameters we filled into the S12ZVM_PMSMFOC_appcfonfig.xlsm were R=19.04mΩ, L=0.0504mH.
(4) The Udc showed on the power supply was 12V. Idc was about 1.9~2.2Amp just before the MCU was damaged.
After the fault, D14 LED1 was alwayse on. VLS out was low. The debugger can run, but the MCU was stuck in --
void cpmu_init(void)
{
// Wait for stable supply after power up
while (GDUF_GLVLSF)
GDUF_GLVLSF = 1;
We need your help to comment what the probable cause is, and which fault protection we can add in the code to prevent the MCU from damaging ? Thanks.
Best regards,
Stanley