HSO disabled in MCSDK for NUCLEO-G474RE + EVLDRIVE102BH: Hardware limitation or MCSDK restriction?

[vi007]

 

Hello,

I am evaluating sensorless FOC on a NUCLEO-G474RE combined with the EVLDRIVE102BH power board using the STM32 Motor Control SDK (MCSDK).

While configuring the project in MC Workbench, I noticed that the HSO (High Sensitivity Observer) option is disabled/unavailable for this hardware combination.

From my understanding, HSO requires both current sensing and phase-voltage measurements. The STM32G474RE appears to have sufficient ADC resources, and the EVLDRIVE102BH includes phase-voltage sensing circuitry. Because of this, I am trying to understand what prevents HSO from being available for this setup.

Could anyone familiar with HSO support help clarify the following?

1. Why is the HSO option disabled when selecting NUCLEO-G474RE + EVLDRIVE102BH in MCSDK?
2. Is the restriction due to:
   • Hardware limitations of the NUCLEO-G474RE or EVLDRIVE102BH?
   • ADC/channel allocation requirements?
   • Phase-voltage sensing implementation requirements?
   • MCSDK board support restrictions?
   • ST validation/support policy for this board combination?
3. If the required current and phase-voltage measurements are available, is there a supported method to enable or evaluate HSO on this platform?
4. Is there a list of officially supported hardware platforms for HSO in the current MCSDK release?

5. I am primarily trying to understand the technical prerequisites and support limitations that determine HSO availability within MCSDK rather than motor tuning or application-specific configuration.

   Any clarification on this would be greatly appreciated.

[cartergray733]

HSO availability in MCSDK depends on more than just having ADC channels and voltage sensing. The hardware setup, sensing topology, timing requirements, and ST validation all need to match supported configurations.

If NUCLEO-G474RE + EVLDRIVE102BH is not in the supported HSO list, MC Workbench will disable the option. A custom implementation may be possible, but it would require manual changes and validation outside the standard SDK flow.

[GMA]

Hello ​@vi007,

As mentioned in the HSO current and voltage sampling in three-shunt topology chapter of the MCSDK User manual, HSO samples all three currents and voltages at each PWM periods. HSO will not be available if the condition is not supported.