cancel
Showing results for 
Search instead for 
Did you mean: 

Motor Profiler connection error: Port Open and try to configure the board

JsonM
Associate

I'm using the Nucleo-F302R8 and the X-Nucleo-IHM07M1 with the small kit motor it comes with.  I'm having trouble getting the motor profiler to connect to the board.

The F302R8 seems to have the demo motion program running, since I can hit the blue button to start the motor turning.  But if I want to run the profiler windows application and try to connect to the board, I get this error:

"Port Open and try to configure the board"

JsonM_0-1752116429199.png

I've tried updating STLink, and it's on the latest (v2.j37.m26).  I've updated my USB driver.  I can connect to the board using ST-Link Utility.  But the motor profiler can't connect.

JsonM_1-1752116628380.png

What might be preventing motor profiler from connecting?

 

1 ACCEPTED SOLUTION

Accepted Solutions

Hello @JsonM,

Does it mean that you haven't flashed it? If yes, if you want to use MC Pilot 6.4, it is mandatory to create, and to flash a MCSDK6.4 Motor profiler project as described on "Motor Profiler Application Note".

If you agree with the answer, please accept it by clicking on 'Accept as solution'.
Best regards.
GMA

View solution in original post

4 REPLIES 4
GMA
ST Employee

Hello @JsonM,

It may come from the Baudrate Speed setting. It is set to 115200. Try with 1843200.
Refer to User Manual documentation available through "Workbench tool">About>Documentations>Documentation>"User manual" tab, "Motor Profiler Application Note" link for Motor profiler generation and usage.

If you agree with the answer, please accept it by clicking on 'Accept as solution'.
Best regards.
GMA

Hi, I've tried both 1843200 and 115200, and both baud rates resulted in the same result, "Port Open and try to configure the board".  This error seems to indicate that it's able to connect to the port, but having some other issues configuring the device?

 

I was using motion control SDK 6.4.0.  I tried SDK 5.4.8 and profiler was able to connect, update the code, and start moving the motor for the profile operation.  So I'm not sure why v6.4.0 is having issues but v5.4.8 is able to proceed.

 

v5.4.8 runs into an issue of "taking too long" and not completing the profile operation, but at least it's able to connect and move the motor.

Hello @JsonM,

Does it mean that you haven't flashed it? If yes, if you want to use MC Pilot 6.4, it is mandatory to create, and to flash a MCSDK6.4 Motor profiler project as described on "Motor Profiler Application Note".

If you agree with the answer, please accept it by clicking on 'Accept as solution'.
Best regards.
GMA

Thank you, I'm new to this.  That fixed the problem, I loaded the profiler application by generating a new project with the profiler checked under application configuration.  Now I'm able to run the profiler and get a json of the motor profile.