Overcurrent Error When Applying Motor Parameters from P-NUCLEO-IHM03 to EVSPIN32G4-DUAL

[pelino]

After obtaining the motor configuration parameters using the P-NUCLEO-IHM03, I applied the same motor parameter values to the EVSPIN32G4-DUAL board, which is used to drive two motors.

However, when operating the motors with these settings on the EVSPIN32G4-DUAL, an overcurrent error occurs.

Could you please explain the possible reasons for this overcurrent condition?
In particular, I would like to know whether differences in the power stage, current sensing topology, or dual-motor operation could cause this issue, even when the same motor parameters are used.

Thank you for your support.

Best regards,
Pelino

[GMA]

Hello @pelino,

Do you mean that you used the motor profiler tool with the P-NUCLEO-IHM03 pack to profile the motor, and after saving the result, you created a new project with EVSPIN32G4-DUAL and the motor profile result?

For Error description and management, refer to documentation available through "Workbench tool">About>Documentations>Documentation>"User manual" tab, "(FOC) Firmware errors" link.

[pelino]

I continuously see the following warning:

NOTICE: Please disable the overcurrent protection of Stage 2 to avoid resource assignment conflict on COMP2. The power stage is already protected by STDRIVE101.

I have already disabled the Overcurrent Protection in Stage 2, however the warning still appears.

Could you please clarify:

1. Is there any additional configuration required to completely remove this warning?

2. Is this warning only informational, and can it be safely ignored if STDRIVE101 hardware OCP is used?

3. Which specific setting or module is still allocating COMP2, causing this notice?

4. Is this warning expected behavior for STDRIVE101-based boards in Motor Control Workbench?

Even after disabling Stage 2 OCP, the message remains unchanged, so I would like to confirm whether this is a known limitation or a configuration issue.

Thank you for your support.

[GMA]

Hello @pelino,

This is a warning message to avoid resource assignment conflicts on COMP2 and, as you mention, is independent of OCP usage.
It does not prevent project generation.

[pelino]

Why does this warning still appear even though the Overcurrent Protection is disabled?

[pelino]

"C38 and C42 are not populated. Could this cause false overcurrent detection?"

[GMA]

Hello @pelino,

This message is a default warning, not an error. The message appears regardless of the configuration.

[pelino]

So, if Overcurrent Protection was triggered, does that mean the current exceeded 23.5 A?

[pelino]

Regarding the Overcurrent Protection,

if the current exceeds the maximum current value of 1.7 A, will the protection be triggered?

Also, was the current waveform shown below measured using a shunt resistor?

Is there a way to measure or monitor the current using Motor Pilot instead?

Thank you for your support.

[pelino]

I created an EVSPIN32G4-DUAL project using MK Workbench.

I am currently testing with only one motor connected to the EVSPIN32G4-DUAL.

As shown below, an Overcurrent Fault occurs on Motor 1.

Even after changing the environment settings as shown below, the Overcurrent error still occurs.

1. Check of the current sensing topology

2. Change the PWM frequency

3. Change the start-up profile

4.Modify the sensorless start-up parameters