motor profiler error using IHM07M1

Posted on April 21, 2016 at 08:39

Ciao Imtiaz

This seems a communication problem. Did you check that the programmed USART speed is the same settled in the motor profiler dialog? Another suggestion is to update the STLink version using the STLink utility.

Ciao

Gigi

Posted on April 21, 2016 at 20:53

Hi Gigi,

Its not a communication issue as I can communicate with the ''Monitor'' tool on the same settings baudrate and Port and also a communication error has a different error message - for example if I change to a differnt baudrate (other than 115200) the error message is ''Connection failed , no response .....'' etc.

Posted on April 22, 2016 at 09:50

Ciao Imtiaz

Ok I understand.

This message appear when the FW that is present into the micro is not configured for Motor Profiler.

For instance if you are using the default FW that is present on the MC Kit when you buy it is a firmware that is configured for the Bull running in sensorless mode but the Motor Profiler is disabled.

To use the motor profiler you have to generate a new firmware, starting from the WB, creating new project based on MC Nucleo Kit and setting generic motor. Then you have to go in the motor setting and verify that motor profiler checkbox is selected. Then you have to generate the parameter .h file in the SystemDriveParam folder and use an IDE like IAR or Keil to compile the firmware.

There is a small video that explain this steps:

https://youtu.be/D4bTL-bH7Ag

I suggest to try the option ''Start from the example'' mentioned in the video.

Ciao

Gigi

Posted on April 26, 2016 at 23:24

Hi Gigi,

I have the motor profiler ticked , generated the files and programmed the nucleo using the Keil project. I am using teh default location of the project - C:\Program Files (x86)\STMicroelectronics\FOC SDK\STM32 PMSM FOC LIBv4.2\Web\SystemDriveParams.

 The motor profiler gives the same error as described before ''The process is in error because the start command procedure failed....''. I am an experienced embedded developer and a long time user of Keil and STM32 so I am sure I am doing it correctly.

I have tried using a new project and a bull running example project both with same results. 

Can you please try to replicate this issue and give me a solution as I need to make progress on this issue. I can send you an files you wish or the binary I am generating. If you give me a direct email it will be much easier to attach files.

I need to get the motor profiler working so I can make progress with slow FOC control on other motors with a quadrature encoder.

Thanks for your help so far.

Posted on May 02, 2016 at 09:39

Ciao Imtiaz

The FW configured for MP can be started with the Monitor section of the WB. So, after you have configured and flashed the code into the micro, you can connect to the FW using the Monitor section.

In this way you can verify if there are communication problems.

Then if you are able to connect you can send a start motor command pushing the relative button. If the firmware is correctly configured the MP procedure will start and so you can see the motor that spend some time to execute the required test before to run.

In this way you can test two things: the first is the communication is ok and the second is that the FW is correctly configured for the MP.

Ciao

Gigi