Board Manager: difference of "features" object in an inverter board

[DMeie.2]

Can you explain to me the difference between the features object inside the motorDrives object, compared to the standalone features object? Most object inside motorDrives make sense as a Feature of the motor drive itself, but not all.

We're using the B-G431B-ESC1 board JSON for reference.

For example the TemperatureSensing feature, what would happen if I put this into the standalone features object instead?

Or vice versa, with the ElectronicSpeedControl feature, why is this in the standalone features object even though it is directly related to the motorDrives functionality?

I cannot make sense of the logic behind this right now.

[cedric H]

Hello @DMeie.2 ,

The idea is easier to explain in case of Dual drive.

Let's imagine you have a dual drives inverter board. The Electronic speed control is just a timer input pin. Whether it controls Motor 1 or Motor 2 is not defined by the pin but by your software implementation. It is the same for the Push button, or for the communication interface. 

But, if your feature is embedded inside a motor drive, it is linked to your motor by the schematic.

If you look at the STM32G474-EVAL board, it is a control board supporting two motors. The control board has some resistors to set the gain of the internal Opamp. So, we described it as a 

CurrentSensing feature implementing the hardware variant : 

ThreeShunt_RawCurrents_SingleEnded_ExternalGain, but the definition of this feature is physically connected to Motor control connector 1 for a specific set of signals, and another description is provided dedicated to Motor control connector 2. These two descriptions can not be defined at board level.

 

Hope it is clear.

Cedric