Jump to content

Alejandro Rodríguez

  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by Alejandro Rodríguez

  1. You are welcome. If the material is not the problem I will need the project in order to help you further. If you want and the project is not confidential, please attach it to this topic and I will check it. Best regards,
  2. Hello Romain, Actually, this is the first time that this bug is reported and it is very difficult to know the reasons with this information. A possibility is that it is caused by an excessive requirement of HW units: in fact, run several projects in the same machine and with the same user requires less HW units than running the same amount of projects distributed between different machines launched, possibly, by different users. Best regards,
  3. Hello Reid, Please, verify the materials properties of the rotor part, it really seems that your rotor is made of non-magnetic material and that is the reason why the magnetic induction is avoiding it. In order to verify this a representation of the magnetic induction is maybe easier to interpret than the representation of the magnetic potential. Hope this helps. Best regards,
  4. Compose 2019 is an environment for doing calculations, manipulating and visualizing data (including from CAE simulations or test results), programming and debugging scripts and matrix calculus. It is developed by Altair. You can download it from Altair Connect (https://connect.altair.com/CP/downloads.html ) Best regards.
  5. Hello Alpha, In Altair Flux documentation you will find a “how to” devoted to this subject: go to Flux help in the supervisor -> pdf documentation -> 03_HowToLaunchFluxviaCommandLine.pdf. There the options to launch Flux from Linux command line is fully explained. In general lines, if you want just launch Flux from command line, you should provide the path to the flux “exec.” file. On the other hand, if you want to change some parameters I advise you to see the different options explained in the documentation. Best regards,
  6. Hello, In fact, a coupling FLUX-FLUX allows to interchange any spatial quantity between the thermal and the magnetic projects through .DEX files stored in a specific folder usually called “EXCHANGE”. In this case, your interest is to send the TIME from the transitory project to the steady state one. Unfortunately, it is not possible to share parameters between applications in a straight way (except spatial quantities). I propose you this bypass: define a spatial variable which value is equal to TIME at any geometrical point. Export this variable from the transient project and import it in the steady state one, where you will be able to read the TIME from any point. Best regards,
  7. Hello, Please find attached the tool to estimate Preisach’s model coefficients, you can run it in Compose 2019. All the needed information to use this tool is provided in the comments of “main.oml”. You just have to open this script in Compose 2019, update it with your measures and run it. Best regards. Preisach_Fitting_Tool.zip
  8. Hello Oscar, I am sorry but I do not have enough information to help you, to do so I will need the answers to this questions: What Flux version are you working with? Which command and which options are you using to import your mesh file? This file is stored in which format? Best regards,
  9. Hi, In fact, if you are not able to properly select the point (0,0) in the sketcher you can adjust the point position by clicking in it and updating its coordinates to (0,0), as desired. If this point is part of another entity definition (e.g. the centre of a circle), the associated elements will be also updated. I do not know why your ".dxf" file is not importing properly, it may be for some errors in the ".dxf" file or in the import options you have selected. Best regards,
  10. Hello Romain, Unfortunately, I think there is not such command in PyFlux. I think you are not able to see the solving pop-up because you are probably running your script in batch mode. A solution to see this windows and its progression bar is to launch your script in direct mode instead. This mode is more time consuming but it allows to see all the displays at real time. Best regards,
  11. Hello Hamza, I think the best way to get into induction heating applications with Altair Flux is take advantage of the examples which are already provided in Flux Supervisor. You will find two Flux projects with very detailed documentation going to Open Example (2D) -> Technical tutorials -> Induction heating/ Induction heating with multiphysics coupling (see image). Hope this helps with your project. Best regards,
  12. Hello, Please, find attached a pdf explaining all the necessary steps to define a geometry in Flux and then import it into FluxMotor Part Library. Best regards, CreateFluxMotorInnerMagnet.pdf
  13. Hello Felix, This warning message arises since the line is used by another entities, most likely by faces or volumes. You can check these usages by using “find usages” command. I advise you to check these dependences carefully before deleting your line. I advise you to delete first all the entities using the line and them delete the line itself in the usual way. Another possible solution is just use the command "force delete" over the line, instead of "delete" command. It will works and all the entities depending on the line will be also deleted. Anyway, I only advise you to use this second method once you are totally sure about what entities are using the line (and, thus, what entities will be deleted). Best regards,
  14. Hello, I think the problem is your project name. I think that character "." between 26 and 02 is forbidden since it seems to identify an extension instead of a name. Please, change this and try again. Best regards,
  15. Hello Holo, In fact, there exists an easy solution to this problem: you may define your second variable just as current_angle=rotor_angle+90. In this case, rotor_angle must be defined as "parameter controlled via scenario" and "current_angle" as "" (see image attached) Then, just change rotor_angle in your parametric scenario: the value of current_angle will be recalculated automatically in each iteration. Best regards
  16. Hello, In fact, you can do all these things you have asked for (inductance simulation for different currents, rotor position and saturation levle, display flux lines at any instant,etc.) Please, look at the example I have talked you about in the Flux Supervisor ( Flux Supervisor (2D) -> Open example -> Technical tutorials -> Brushless IPM motor (embedded magnets) ). There, you will find very detailed explanation about how to calculate all these variables. Best regards.
  17. Hello , In fact, Flux still taken into account that an odd periodicity exists. If you are not using an infinity box (this is not compulsory but only advised) you should set boundary conditions in your motor borders. In any case, with or without infinity box, you will need to use linked mesh on the lines just at it was explained by Flux support. Best regards,
  18. Hello, The reason why you are not finding the currents definition in this example is that they are no needed at all, since the cogging torque is only due to the interaction between the rotor's magnets and the stator slots. In fact, this is the simplest simulation you can carried out using a given motor geometry. In your case, you should define a circuit (menu Physics -> Circuit -> Circuit editor context) and then linked the coil's surfaces with a stranded coil conductor in the circuit side. Anyway, if you are searching for tutorials you have many of them in Flux Supervisor! They will explain you how to build your motor step-by-step, including all the Flux project and very detailed explanations in both, pdf and in ppt. In your case, I advise you to choose in Flux Supervisor (2D) -> Open example -> Technical tutorials -> Brushless IPM motor (embedded magnets), where you will find a very detailed example, including cogging torque calculation but also back EMF and motor performances under different working conditions. (Please, see image attached). Best regards,
  19. Hello, It seems that there is a path in Simulink that is not well parametrized. Maybe, that is the reason why your S-function is not able to find Flux. I think Flux path should be indicated in Simulkin in order to properly do the coupling. Best regards,
  20. Hello Qchen, I really think that the second image is not more blurry than the 1280x1024 one but less bright. It also seems that both images are not exactly the same since the flux lines are a little different. Maybe this effect is due to the echelle. In fact, what I propose you is to play with different echelles and number of lines to find an optimum in your visualization. You can also choose a picture size “Custom”” in the “printing into file” option and see the results. Best regards.
  21. Hello, This problem may have very different causes. Perhaps your voltage rms value is wrong or, more probably, the phase angle between the voltage source and the rotor position is not the right one (in the case of synchronous machines). Both causes may lead to great increment in the currents through your machine. Another potential cause is a bad estimation in winding resistance or in the end-winding inductance. Anyway, in order to better answer your question more information about your machine topology and the type of study you are carrying out will be needed. Best regards.
  22. Hello, Unfortunately there is no way to save the isovalues max/min limits of one step and use them in another one. Best regards.
  • Create New...