Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


lombard last won the day on March 5 2019

lombard had the most liked content!


About lombard

  • Rank

Profile Information

  • Gender
  • Are you University user?

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hello, When you follow the document step by step you need this file. You will find it attached there. I hope it will help. Best regards Create_NonMesh_Coils_SPM.zip
  2. Hello, I think we need your Flux and Activate files in order to better understand what is going on. Note: it seems this request has also been sent to direct support. Please send us your project, or a similar basic project where you can reproduce the case. regards Patrick
  3. Hello, You can do it by following the next steps: - open Flux project - in the tree on the left click on [Tools] [Colors] (in fact on the cross in front of the menu) to open the menu with colors - click on one color (or more than one, using the CTRL keyboard function to add colors in the same list) (I would recommend to select only NEW colors) - then right click - then select [Python export] - give a name inthe [pyton file] part, for instance colors - click on the [OK] button - close your current Flux project - open the Flux project where you want to import your new colors - select the menu [Project] [Command file] [execute in direct mode] - select the python file you have generated (for instance colors.py) - it will generate your new colors (note: there will be an error if the name of the color is already defined) I hope it will work on your side. Another way to do it one by one is the following: - select your color in the tree on the left - right click - selelct [Display PyFlux command] - it will display the command to generate the color in the [output] window - copy the command (for instance Color(name='CYAN_1', code=[0, 0, 255]) - then open your second Flux project where you want to create this color - paste the lines in the [PyFlux Command] window - click on the green arrow on the left - it will execute the pyFlux command, and generate this color (without error if the name does not exist yet) I hope it will help. regards Patrick
  4. Hello, The Application[1] is always the preprocessor. Application[2] is for the physical application. I propose you to use a specific command (which is valid for all Flux entities): A=Application[2].getPyFluxCommand() print A It should display something like this for transient application: ApplicationMagneticTransient2D(domain2D=Domain2DPlane(lengthUnit=LengthUnit['MILLIMETER'], depth='75'), solverFE=SolverFEFlux3D(), coilCoefficient=CoilCoefficientAutomatic(), transientInitialization=TransientInitializationStaticComputation()) I hope it will help. regards Patrick
  5. Hello, Would it be possible to send us your Flux project (directory name_of_project.FLU in a zip format)? I think it will be difficult to have an idea without it. Thanks Patrick Lombard
  6. Hello, With periodicity, it is forbidden to use compressible mechanical set. Please remove it, and assign the AIRGAB region either to ROTOR or STATOR mechanical set.. Note that it is better to have 2 layers in the airgap, one belonging to ROTOR mechanical set, and one belonging to STATOR. Please have a look at the way it is done in our demo case given with Flux supervisor (for instance Brushless IPM motor (embedded magnets). It is surprising that the rotor is fully circular. It seems that the geometry is not fully done. You should define the rotor as solid cnductor to get a torque. I hope it will help.
  7. Hello, Probably, the name of your components or the comments are too long. In fact Flux is going to concatenante name plus commment and the number of characters must be lower than 80. I hope it will help. Patrick
  8. Hello, Do you have student version or a regular version ? The student version is limited in number of nodes but the message should be more clear. Regards Patrick
  9. Hello, In fact there is a possibility to avoid to have to recompile. The procedure is as follow: - copy the file user_flux.dll (my_Sup.f3d_usr/dll) in the followin g directory (for a standard installation) C:\Program Files\Altair\2018\flux\Flux\Bin\dll\win64 Normally it should work directly. I hope it will help. regards Patrick Lombard
  10. Hello, I think somes lines are missing. You currently have input and output faces highlighted. In fact you also need to have more internal faces (4 faces are missing). In order for Flux to create theses faces, you need to create 8 more lines. This is compulsory for Flux to be able to create the meshed coil. I hope it will help. Patrick
  11. Hello, It is difficult to find what is going on without the project. would it be possible to zip the Flux directory (nameproject.FLU) and to send us this zip file so we can better help ?
  12. Hello, Sorry fo rhte delay in this answer. You should have same results for losses in AC and in transient magnetic analysis. I am surprised you can model PMSM in AC as normally when you have magnet you can not use the AC steady state magnetic module. Indeed, in this module we assume all quantities are varying sinusoidally, which is not the case of magnet where you have a DC component. Can you give us more detail on the device you are modeling, and which working point ? For induction motor, in AC analysis, we do not take into account of the slot effect, as only the rotating flux due to the electric frequency is taken into account. Maybe this is what you are looking at. In this case only the transient analysis will give you the right value. Regards Patrick
  13. Hello, The flux can be directly computed on the coil as you have done (this is the flux going through the coil). If you want to have it on the iron, one possible way is to define a sensor, which will integrate flux density on an existing face (top or bottom one).
  14. Hello, You will find the file in version Flux 12.3 (it seems you have it). there is a warning when opening it, but at least you can see what I have done. Basically, I have reduced the radius of the coil to 21, and add a volume of air around the non meshed coil (radius 22). I have defined boudary condition to allow the flux to go out of the cylinder (on top and bottom). And when there is no boundary condition, by default it is set to parallel flux (flux is parallel to the faces). This is why the flux becomes constant in the iron part. I hope it will work on your side. 12_3_Coil_withIronCore_automaticFormulations_3D_altair_2_solved.FLU.zip
  15. Hello, I have seen what the support has tried to explain you. I will do it differently. When applying the Ampere's law, we assume that the magnetic field is only going through the iron part (and is constant in it). then we have: H.L = N.I with H magnetic field (B=Mu0.MuR.H) (B flux density L length of the iron part N number of turns I current in one turn Then we have : B=Mu0.MuR.N.I/L B=4E-7.Pi.1200.1600.0.5/0.4=3T When I try with your initial device, I have B=0.167T Then I have modified the device and model only the iron plus a small volume of air around non-meshed coil. In this case the magnetic field is nearly constant in the iron part (following the initial hypothesis of Ampere's law) and equal to 2.935T (to be compared to 3T found out analytically) In the first case, all of the flux is going in the air (the flux leakage), leading to the low value of magnetic field (and different from "analytical" result). I hope this case will convince you: - that Flux is giving right result - that it is not easy to compute "manually" the magnetic field (you must be sure of your hypothesis) You will find attached my model, already meshed and solved (it is not too big). I hope it will help. Coil_withIronCore_automaticFormulations_3D_altair_2_solved.FLU.zip
  • Create New...