Thank you for your answer,
I have tried. It works, that is, the motor pilot is OK and well connected to the board.
But when i try to start, there are errors because the parameters of the motor are not
exact.
And that is the problem. I want to run the profiler so to obtain the exact parameters,
but it is still stuck when attempting to connect with the same message
But maybe I am wrong, and don't understand your environment. Let me ask you
few essential questions about your system :
* Using motor pilot is adapted when all the FOC software (what you call FW) is already flashed, True ?
* in this case, the program running on board is listening the UART whose signals are carried by the USB cable (via STlink), True ?
Now, if i want to use Profiler :
* i thought that even with a blank flash of my Nucleo board, the system could load a "minimum command" so to allow profiling
motor. Am i wrong here ? Nevertheless, i remember i have read that it was possible. If so, how the flash process is done ? Is it possible with UART ?
Finally, is this flow correct ?
* use Motor control workbench first with a default machine (not mine, approximative param),
* flash the Nucleo Board
* open the Motor pilot and select Discover board, and the connection via UART must be OK
* open profiler to test my motor, hoping the connection stay OK (but for me, it does not work !!)
* save the motor model
* go back to Motor control wb and make the new conf with my new motor param .
If this flow is not OK, can you give me the steps knowing I am using an new motor ? How
to profile ?
Thank you very much
Best regards
