Eomys/pyleecan

Roadmap for the performance optimization of electrical motors

EmileDvs opened this issue · 0 comments

Hello everyone,

This is a general issue to discuss on the mid/long-term roadmap of pyleecan (v1-v2) around the performance optimization of electrical motors, as one of the main objectives of PYLEECAN project (https://www.pyleecan.org/).

This general issue aims at organizing all the future issues on any pyleecan developments on the performance optimization topic along the following axes:

  1. electromechanical performances (power, torque, torque ripple)
  2. motor losses:
    • joule losses
    • iron losses
    • magnet losses
  3. other losses: converter losses, mechanical losses
  4. motor temperature due to losses
  5. efficiency calculation on specific duty cycles, including standard duty cycles for EV/HEV applications (NEDC, WLTP)
  6. optimal control strategy (MTPA, MTPV, switching, etc.)

The future issues can be organized around the existing and new pyleecan objects that will be developed, by putting object names in the title such as:

  • machine: PMSM, SRM, SCIM, SynRM, DFIM, WRSM etc.
  • inputs/outputs: perf / (iron, joule, magnet) losses / temperature / control strategy / standard duty cyle
  • models: EEC (Electric Equivalent Circuit) / MagFEMM (Magnetic simulation using FEMM) / MagElmer (Magnetic simulation
    using FEMM) / HeatTransferFEMM (Heat transfer simulation using FEMM)

We will then assign the proper labels to each issue.

Some issues are already “work in progress” and could be used as example:

  • Iron losses calculation using FEMM for any topologies (#59)
  • 3D electromagnetics calculation in Elmer to model SCIM for performance calculation (#202, #205)
  • Electrical Equivalent Circuit to model SCIM for performance/losses calculation (#165)

We have already created some issues with the "help wanted" label to indicate to new contributors where we need some help, especially regarding new models and coupling.

Of course, we invite everyone to discuss below on how to organize the future developments and feel free to directly open an issue to begin with technical discussions.

Best regards,
Emile