Errors compiling with STMCubeIDE likely because module libraries aren't included. How do you include missing libraries? Or could it be something else?

Ok,

Happy to read some good news.

Update and Generate are a bit tricky but worth to understand. Let me try an explanation.

The Workbench generate an IOC. this IOC is complete from motor control point of view, but additional IPs can be needed depending on the application.

The update button will guarantee that only the MOTOCONTROL stuff of the IOC will be modified.

The idea behind, is this one :

• The user creates a new project, and an IOC is created by the workbench and used by cubeMX in background to generate the project.
• Once the project is generated, the user wants to add another IP, (a UART or whatever). So opening the IOC with cubeMX and doing the modifications.
• Now that his IOC matches his final application, he wants to tune some motor parameters, so he wants to keep his additional IPs, but just change the PID for instance.

Then the Update button is what he needs. It will update only the MotorControl part of the IOC.

In the case of potentiometer example, this is exactly what we use. The potentiometer is connected to an additional ADC channel, through an additional pin called POTENTIOMETER. This ioc is copied with your project when you save it the first time. If you click on generate, you will erase the IOC we provide with the potentiometer, so the example will not work because the Potentiometer pin will not be configured.

The update button is proposed only when an existing ioc with the same name than the stmcx file is detected.

I hope that the concept is clear.

Now, there are a lot of limitations that are difficult to catch. The biggest limitation is that when you want to update an IOC, only few modifications from the Workbench are possible, but nothing will warn you. We are working to avoid these traps in the future.

For example, the workbench let you change the PWM frequency. this PWM frequency will be used to change the auto-reload value of the PWM Timer. So the information is stored inside the timer section of the IOC. the Update button is not allowed to change the Timer section, only the MotorControl part as explained before, so changing the PWM frequency and generating the project with Update button will lead to a non working project without any warnings from the tool.

We are fully aware of those issues and a complete new Workbench is under heavy development.

I hope that things are more clear now.

On my side I entered a ticket on cubeIDE side to fix the request of lib download while they are already available.

For the rest, from all the trials I did, I did not see any generation issue.

If you agree I think that this two years old post can be closed now. To be honest I do not really understand why a ST guys reactivated it.

Regards

Cedric

Hello Chris,

I will try to answer point by point.

" I should use Generate from the MC Workbench only when creating a new project from the workbench. ANytime I use it again on the same project it is likely to cause problems."

Not really. When you start a project from scratch, you do not have the choice, only the generate button can be clicked, as there is nothing to update.

The rule of thumb, is that as far as you do not change the IOC file generated clicking on generate button is the safest solution.

The trick to understand here is that starting from an example, is NOT starting from scratch. We provide within the example an IOC that you must not override to keep the example functional. This is why we ask you to click on the update button in the provided readme.txt file. The purpose here is to allow the user to change only the motor parameters.

"So the criticla points from this thread are

• Only generate new projects once

You can generate project multiple time, clicking on generate button will guarantee you that the IOC is always coherent but written from scratch.

• Only Update examples because they are already generated

Almost correct ! Whole project is not generated, but the IOC file is already provided. It has just to be updated with your motor parameters. So yes only click on Update button when you start from an example (as stated in the readme.txt file ;) )

• Use stand alone Cube MX on motor control projects

This is our recommendation today.

For the first generation you do not really have the choice. cubeMX version embedded inside cubeIDE is not proposed amongst the possible choices. An action is on going to detect it but It is not the case yet.

Once the code is generated, modification of the IOC could be done by cubeMX or embedded cubeIDE version. I tested both successfully but our preferred way in the dev team is to use standalone cubeMX version. It is an old habit as the cubeMX embedded in cubeIDE is a pretty new feature.

• Be aware that there are technical issues that have not yet been cleared by the dev team (backup, backup, backup) AND version control

Not sure what are you referring to here,

• It may be better in the interrim to adjust parameters in code rather than .ioc
• It may be better in the interrim to add IP via code so as not to confuse the code update

If you need to add IPs or modify the IOC, the safest way to proceed is to do this inside cubeMX, and once the IOC is modified generate the code from cubeMX only. You should avoid to use the MC Workbench and click on update button to update an IOC modified by cubeMX excepting you completely understand what you are modifying.

"They are easy enough to do. An easy work around would be tot create an .ioc specifically to initialise these pins, generate to separate files, then copy these files in to the MC project."

We are working hard to iron this part, For the time being the best advice I can give you is to avoid round-trip between cubeMX and MC Workbench,

Regards

Cedric