Jump to content


  • Content Count

  • Joined

  • Last visited

About Magneto

  • Rank

Profile Information

  • Country
  • Are you University user?
  1. Hello, sorry for the late response. In fact I solved the problem. First of all the fact, that the flux project can be solved in a static scenario, without a translation part, let me think that FLUX could have some issues with geometry identification and/or remeshing during the multistatic simulation. The failure was caused by the Geometry (*.stp). For this analysis I modified an existing step-model in hypermesh. This leads to the fact, that in the exported new *.step file there where two "parts" in the part browser in hypermesh. When I modified the stepfile again by deleting one of the "parts" (not components!!!) Flux was able to solved the project. To find this problem I was in contact with the Altair Flux support. He has no idea, why this caused such a problem. He forward the Support-Ticket to Hypermesh-Support. Maybe they have an idea. Best regards.
  2. Hello, I have a problem solving a Flux 2d magneto static project (axissymmetric). The geometry check, mesh check and physical check shows no error. If I start solving the scenario this is written in the output window: Begin of physical check ... The final derivative of points defining the spline curve of material E235C must be equal to Mu0. The final relative permeability is equal to: 0.27947406883797 Please, verify the properties of the material: E235C An electric circuit exists. The active physical application does not take account of it. End of physical check. Automatic selection between local and distributed MUMPS... Setting solver for presolving : Mumps Local Automatic selection between local and distributed MUMPS... Setting solver for solving : Mumps Local 08:07:15 5776 sec. Start save ... 08:07:16 5777 sec. ... end save Active formulation(s) : MSAVEC : Axisymmetric magnetostatic vector potential formulation Matrix system : non linear, real, symmetrical Setting solver for presolving : Mumps Local Setting solver for solving : Mumps Local 08:07:16 5778 sec. Start solving problem ... Step number 1 Value of parameter ELFORC_TRANSLATION_ANKER : None Value of parameter LINPOS_TRANSLATION_ANKER : -.3E-03 Value of parameter VAR_STROM : 0.3 The final derivative of points defining the spline curve of material E235C must be equal to Mu0. The final relative permeability is equal to: 0.27947406883797 08:07:30 5791 sec. Start creating Dirichlet constraints at points... 08:07:30 5791 sec. ... end creating Dirichlet constraints at points. 08:07:30 5791 sec. Start save ... 08:07:32 5793 sec. ... end save Mesh of compressible domains ... 08:08:07 5828 sec. Generating 2nd order elements is running Total number of nodes --> 551232 08:08:10 5831 sec. End generating 2nd order elements RAN1 unknowns are initialized to zero 08:08:16 5837 sec. Numbering of 551232 nodal values done. 08:08:16 5837 sec. Number of non zero matrix elements estimated to be 22055440 Non managed error which has stopped solving process 08:08:16 5837 sec. Start save ... 08:08:16 5837 sec. ... end save 08:08:16 5838 sec. Start reading ... 08:08:18 5839 sec. ... end reading 08:08:18 5839 sec. ... end solving problem. The final derivative of points defining the spline curve of material E235C must be equal to Mu0. The final relative permeability is equal to: 0.27947406883797 executeAlgo_c : Execution failed.Failed execution ERROR: Advanced PBEPAV_3 => Error 49, no treated error type PBCEVL_4 => failed PBCEVL_3 => Failed PBERES_3 => failed FL5RE4 => Command not executed correctly FL5ERS => failed FL5ERS_1 => failed executeAlgo_c => failed stdcom.error.SoftwareFortranException: executeAlgo_c : Execution failed. Failed execution at cad.core.common.error.ErrorManager.createFortranException(ErrorManager.java:170) at cad.flux.kernel.dbmanager.FGCProjectDbWrapper.executeAlgo(Native Method) at cad.flux.kernel.dbmanager.FGCProjectDbAdapter.executeAlgo(FGCProjectDbAdapter.java:902) at cad.flux.kernel.dbmanager.FGCDbManager.executeAlgo(FGCDbManager.java:151) at cad.flux.kernel.FGSupervisor.executeNativeCommand(FGSupervisor.java:2169) at cad.flux.kernel.actions.implementation.algo.project.KSolveScenarioAction.doAction(KSolveScenarioAction.java:83) at cad.core.common.dynamic.actions.UIActionManager.postAction(UIActionManager.java:145) at cad.core.kernel.KernelCommon.postAction(KernelCommon.java:347) at cad.core.kernel.Supervisor.executeJavaCommand(Supervisor.java:2862) at cad.core.kernel.Supervisor.executeCommand(Supervisor.java:2040) at cad.core.kernel.Supervisor.executeMethod(Supervisor.java:2159) at sun.reflect.GeneratedMethodAccessor380.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.python.core.PyReflectedFunction.__call__(PyReflectedFunction.java:188) at org.python.core.PyReflectedFunction.__call__(PyReflectedFunction.java:206) at org.python.core.PyObject.__call__(PyObject.java:545) at org.python.core.PyObject.__call__(PyObject.java:551) at org.python.core.PyMethod.__call__(PyMethod.java:171) at pydb$py.executeMethod$205(pydb.py:1617) at pydb$py.call_function(pydb.py) at org.python.core.PyTableCode.call(PyTableCode.java:171) at org.python.core.PyBaseCode.call(PyBaseCode.java:171) at org.python.core.PyFunction.__call__(PyFunction.java:434) at org.python.core.PyMethod.__call__(PyMethod.java:156) at pydb$py.__call__$172(pydb.py:1390) at pydb$py.call_function(pydb.py) at org.python.core.PyTableCode.call(PyTableCode.java:171) at org.python.core.PyBaseCode.call(PyBaseCode.java:308) at org.python.core.PyBaseCode.call(PyBaseCode.java:199) at org.python.core.PyFunction.__call__(PyFunction.java:482) at org.python.core.PyMethod.instancemethod___call__(PyMethod.java:237) at org.python.core.PyMethod.__call__(PyMethod.java:228) at org.python.core.PyMethod.__call__(PyMethod.java:223) at org.python.core.PyObject.invoke(PyObject.java:3715) at org.python.core.PyInstance.instance___call__(PyInstance.java:377) at org.python.core.PyInstance.__call__(PyInstance.java:372) at org.python.core.PyObject.__call__(PyObject.java:424) at org.python.pycode._pyx237.f$0(<input>:1) at org.python.pycode._pyx237.call_function(<input>) at org.python.core.PyTableCode.call(PyTableCode.java:171) at org.python.core.PyCode.call(PyCode.java:18) at org.python.core.Py.runCode(Py.java:1625) at org.python.core.Py.exec(Py.java:1669) at org.python.util.PythonInterpreter.exec(PythonInterpreter.java:276) at cad.core.kernel.components.PythonWrapper.runCode(PythonWrapper.java:628) at cad.core.kernel.components.PythonWrapper.runsource(PythonWrapper.java:623) at cad.core.kernel.components.PythonWrapper.runsource(PythonWrapper.java:598) at cad.core.kernel.components.PythonWrapper.runsource(PythonWrapper.java:593) at cad.core.kernel.components.PythonWrapper.execute(PythonWrapper.java:638) at cad.core.kernel.components.PythonWrapper.executeFunction(PythonWrapper.java:706) at cad.core.kernel.encoder.CommandServerRequestsInputPlug.executeCommand(CommandServerRequestsInputPlug.java:79) at stdcom.protocole.commandserverrequests.CommandServerRequestsRouter.executeCommand(CommandServerRequestsRouter.java:70) at stdcom.protocole.commandserverrequests.CommandServerRequestsOutputPlug.executeCommand(CommandServerRequestsOutputPlug.java:111) at cad.core.frontal.decoder.FrontalDecoder.executeCommand(FrontalDecoder.java:692) at cad.core.frontal.actions.implementation.GeneralAction.executeBox(GeneralAction.java:286) at cad.flux.frontal.actions.implementation.algo.project.FAbstractSaveAsAction.executeBox(FAbstractSaveAsAction.java:93) at cad.core.frontal.actions.implementation.GeneralAction.postAct(GeneralAction.java:254) at cad.core.frontal.actions.implementation.GeneralAction.interpret(GeneralAction.java:315) at cad.core.frontal.components.box.frontaldialog.FrontalDescriptorDialogBox.internalRun(FrontalDescriptorDialogBox.java:296) at cad.core.frontal.frontalthread.WorkerThread.executeImplementer(WorkerThread.java:226) at cad.core.frontal.frontalthread.WorkerThread.run(WorkerThread.java:274) Someone an idea which can cause this error? I have build up nearly the same model last week, without any complication.
  3. Hello, thank you for your fast answer. Your advise helps me a lot. But do I have to model the airgab between two parts always, although the parts are in contact in reality? Regards, Magneto
  4. Hello all, I'm have build up a 3D model which 4 parts in it. This model I can mesh and solve without any problems. Now I had split 1 part into 3 party, because of different material behavoiurs. These three parts contact at the splitting surfaces. Because I was not able to mesh this geometry, I have insert a 0,5mm air gab between the parts. Now I can mesh the geometry, but without the infinitiy box. If i complete the infinity box first, it comes to a problem at meshing the volumes: "Meshing by inserting nodes has aborted. Please check mesh on lines: 331 43 44" My question is now: What can I do to avoid the meshing problems? Do I need the 0,5mm air gab between the parts? Thanks for your support. Magneto
  • Create New...