Why is there a unnecessary limit of number of slots per pole per phase (Q<0.25) in FluxMotor?

Christian_SEW
Christian_SEW Altair Community Member
edited March 13 in Community Q&A

Hi, i would like to create a motor with number of stator slots = 6 and number of rotor poles = 10. I am not allowed to do this, because "Windings with Q < 0.25 are not allowed. The found value is 1 / 5".

Why is there a limit and how can i create to motor that i want to?

With best regards

Christian

Tagged:

Welcome!

It looks like you're new here. Sign in or register to get started.

Answers

  • Charishma_Modem
    Charishma_Modem
    Altair Employee
    edited February 17

    Hello Christian,

    Thanks for writing to us.

    I believe you are taking about FluxMotor, where for three-phase machines, where if a number of slots per pole per phase strictly lower than 0.25, such cases are not allowed in FluxMotor tool. You can still use Flux 2D and carry out the required computations.

    You can also read the MotorFactory_2024.1_Windings in document to read section of Altair FluxMotor help. https://2024.help.altair.com/2024.1/FluxMotor/topics/4020-Documentationtobedownloaded.htm

    Best Regards,
    Charishma.

  • Christian_SEW
    Christian_SEW Altair Community Member

    Hello Charisma,

    your software has unnecessarily set this hard boundary condition. I understand that you want to prevent a user from making an incorrect design. However, with the large number of input parameters – even in a "simple" tool such as FluxMotor – this can also result in an unusable motor. The boundary condition of number of slots per pole per phase of 0.25 follows from the pitch factor. However, this is not a hard boundary and lower values are allowed.

    Is there a possibility of a patch or a trick on how to "trick" your code at this point? The procedure via Flux2D is much more complex. Our standard prodedure is via FluxMotor, because this program allows you to create motor designs very quickly and conveniently.

    With best regards, Christian

  • fzidat
    fzidat
    Altair Employee

    Hello Christian,

    I'm delighted that you find FluxMotor easy to use, which is likely due to its ability to "Create motor designs very quickly and conveniently," as you aptly put it. However, this apparent simplicity should not obscure the complexity of the underlying calculations, and the remarkable work of our colleagues to make the user experience as pleasant as possible.

    Regarding your question, the limitation you mentioned is indeed documented in the help section, as shown in the attached screenshot.

    It's specified that configurations with a Q<0.25 are not permitted by our processes. This restriction stems from some tests on this type of machine. We established this limit to ensure the robustness and accuracy of our results. As you likely know, FluxMotor combines the Park model with quantities calculated by Flux 2D in magnetostatics (magnetic flux). This approach strikes a balance between calculation precision and speed. The Park model, however, requires working with the fundamental signal component and that the machine not be overly saturated. Configurations with a Q-ratio below 0.25 typically exhibit a magnetomotive force (MMF) rich in harmonics.

    For these types of machines, it's therefore preferable to use Flux 2D, as my colleague suggested.

    Best regards

Welcome!

It looks like you're new here. Sign in or register to get started.

Welcome!

It looks like you're new here. Sign in or register to get started.