Seems to be an issue with compatibility of PMSM (FluxMotor) block with LUTs exported from FluxMotor 2023
Answers
-
Hi Chris,
Thanks for reaching out!
At which stage of your workflow did this error occur?
Did it happen immediately upon starting the simulation? -> possibly an import issue
Or did it occur while the simulation was running? -> possibly a problem with the working range
BR,
Nikos
0 -
Nikos Dimitrakopoulos said:
Hi Chris,
Thanks for reaching out!
At which stage of your workflow did this error occur?
Did it happen immediately upon starting the simulation? -> possibly an import issue
Or did it occur while the simulation was running? -> possibly a problem with the working range
BR,
Nikos
Hi Nikos
It occurs immediately upon starting the simulation. It seems that the export of the iron loss components has changed for FluxMotor 2023.
Thanks
Chris
2 -
I checked that the same error occurred.
The error message is the same.1 -
Chris L_22616 said:
Hi Nikos
It occurs immediately upon starting the simulation. It seems that the export of the iron loss components has changed for FluxMotor 2023.
Thanks
Chris
Hi Chris,
Looks like an error in the process of the .mat file generation from Flux. Is this specific to FluxMotor 2023? Can you get this to work with version 2022.3?
BR,
Nikos
0 -
Yong Jun Lee_21635 said:
I checked that the same error occurred.
The error message is the same.Thanks for sharing this! Is this a FluxMotor 2023 related issue for you too?
BR,
Nikos
0 -
Nikos Dimitrakopoulos said:
Thanks for sharing this! Is this a FluxMotor 2023 related issue for you too?
BR,
Nikos
So am I.
There was a problem with Flux Motor 2023.
I haven't tried the 2022 version yet.0 -
Nikos Dimitrakopoulos said:
Hi Chris,
Looks like an error in the process of the .mat file generation from Flux. Is this specific to FluxMotor 2023? Can you get this to work with version 2022.3?
BR,
Nikos
Hi Nikos
Yes, seems specific to FluxMotor 2023. It worked fine for me previously.
Regards
Chris
1 -
Thanks everyone for your feedback on this. It seems to be a bug with FluxMotor v2023.
I will make sure to document this issue in order to get that fixed.
Best regards,
Nikos
2 -
I'd like to report the same issue. Please let us know if it will be fixed. Thank you
0 -
Hi all,
I'm getting in touch to offer a workaround for this issue. FYI we anticipate it will be resolved in FluxMotor 2024.
It seems the issue is due to a difference in the name of "iron losses" and "torque" headers.
With FluxMotor 2022.3 it was LOSS_IRON
with FluxMotor 2023, it is LOSS_IRON_STATOR.______________________________________________________________________
With FluxMotor 2022.3 it was TORQUE
with FluxMotor 2023, it is ELEMENT_TORQUE_ELECTROMAG._______________________________________________________________________
As a workaround, you can open the .mat file exported from FluxMotor using Compose and the MAT Explorer tool. From there, you can rename the headers accordingly. Once modified, you should save the altered file using the save('path/name.mat') command.
BR,
Nikos Dimitrakopoulos
1