cancel
Showing results for 
Search instead for 
Did you mean: 

STEVAL-CTM009V1 machine does not rotate and bugs

Takumi Lee
Associate III

Hi, 
[PN]: STEVAL-CTM009V1 with F446RE
[VERSION]: 6.3.2
[TOOL]: MC SDK
[DETAILS]: just can't get the engine to turn
[EXPECTED BEHAVIOR]:the engine turns
[HOW TO REPRODUCE]: see below...

First:
There is a bug in RevUp—see the picture below. When changing the torque current values, the input value is automatically reset to 0.

Second:
I identified the motor parameters using the IHM08M1 board and configured the machine accordingly.
The machine successfully rotated!

Third (CTM009V1 Hardware):
I have concerns regarding the current measurement using the ICS. I suspect that they are either not measuring correctly or that there is an underlying issue.
One aspect that frustrates me is that a data stream is not displayed unless MotorPilot is started.
I would like to send a current through a test-cable to verify whether the ICs are functioning correctly.
But if I don't start the Motor-Pilot I don't see any data stream -.-

Fourth:
Next, I attempted to generate an open-loop current, but unfortunately, I failed miserably.
Without the overcurrent protection, the semiconductors on the board would have been destroyed long ago.

Fifth:
Parallel to this test setup, I assembled the new B-G473E with a custom-built machine featuring 12 armatures and 14 magnets.
Highest respect to the ST development team, this setup works exceptionally well!
It is astonishing how smoothly the machine runs without sensors.
Setting up an open-loop current in this case was effortless.

Sixth:
Finally, I would like to share my opinion. The hardware options in the MCSDK should be streamlined slightly. Instead, more emphasis should be placed on improving the software concept in terms of quality.
The idea and the direction in which it is developing is great! I have been following the whole thing since 2017.
Of course, sometimes more or less with long breaks in between.

cheers
Aaron

4 REPLIES 4
Gael A
ST Employee

Hello Takumi Lee,

The first point you mentioned is a known issue and we are working on a fix. We currently have no workarounds, sadly.

Concerning the third point, the MotorPilot is the interface that sends commands to the controller to provide data, it is only normal that it has to be started to see any data stream. I don't understand what you would need from it

Fourth point : Have you tried Open Loop Duty first ? You can put a low duty (low enough to avoid triggering the driver's OC protection) and see if the measured currents are in line with the real ones. This is useful to check the health of your current sensing before adding the current control loop. You can have more info on how the Open Loop feature works in our User Manual : Via WorkBench, you can find it by clicking on About -> Documentations -> Documentation -> in the newly open browser window, click on User Manual.

Fifth and sixth : Thank you for your feedback and your long-term interest in our products ! We put a lot of efforts into developing the best solutions we can provide, and we will try to further improve the way it is presented to the user.

If you agree with my answer, please consider accepting it by clicking on 'Accept as solution'.

Hope this will help,
Gaël A.

Hi Gael A, 
thank you for response, (everything in italics is quoted by you)

I don't understand what you would need from it
-> I think the ICs aren't working properly. I'd like to test the current measurement.

Have you tried Open Loop Duty first ? 
-> Yes, but overcurrent protection as soon as a little current flows.

I must check ICs first!

Best regards 
Aaron 

 

Hello Takumi Lee,

On the CTM009, the Overcurrent Protection feature has a threshold of 200A by default. Unless you have changed it, I don't think you are putting such high current values even with low duty cycle values (a few percents). Thus, I would think that there is a current measurement issue. You can try to first remove the OCP feature in the WB and start looking at your currents on Open Loop, first in duty then in current. Be aware that you will work without any protection, so thread carefully. If your currents are behaving normally, then you probably have an issue with your OCP feature : comparator shunt, filtering, wrong signal polarity...

Please let me know if you have any other question.

If you agree with my answer, please consider accepting it by clicking on 'Accept as solution'.

Hope this will help,
Gaël A.

Hi,
the machine was operated in open-loop duty cycle mode using the specified parameters.
However, a loud rattling noise was observed, and the current measurement showed a very noisy signal.

What steps can be taken next to achieve acceptable and quiet operation of the machine?


ScreenPlot.PNG

ScreenGUI.PNG