Three Mechanical Sets are causing an error

Haidar Diab_21494

Hello, I have a structure that contains three mechanical sets, two sets are moving and one is fixed in a 2D magnetostatic application. Everytime I try to run the project on multiple steps it gives this error:

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 : Ex&eacute;cution impossible. Echec d'ex&eacute;cution 	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:910) 	at cad.flux.kernel.dbmanager.FGCDbManager.executeAlgo(FGCDbManager.java:151) 	at cad.flux.kernel.FGSupervisor.executeNativeCommand(FGSupervisor.java:2213) 	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:2885) 	at cad.core.kernel.Supervisor.executeCommand(Supervisor.java:2063) 	at cad.core.kernel.Supervisor.executeMethod(Supervisor.java:2182) 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) 	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$209(pydb.py:1673) 	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__$176(pydb.py:1444) 	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._pyx9.f$0(<input>:1) 	at org.python.pycode._pyx9.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:632) 	at cad.core.kernel.components.PythonWrapper.runsource(PythonWrapper.java:627) 	at cad.core.kernel.components.PythonWrapper.runsource(PythonWrapper.java:602) 	at cad.core.kernel.components.PythonWrapper.runsource(PythonWrapper.java:597) 	at cad.core.kernel.components.PythonWrapper.execute(PythonWrapper.java:642) 	at cad.core.kernel.components.PythonWrapper.executeFunction(PythonWrapper.java:710) 	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) ​

Which is a very ambiguous and unclear error that I can't deduce anything from. Even if I try to set two of the three mechanical sets into "fixed", the error remains the same. I tried removing one of the mechanical sets to see and the error disappears, but this is not a solution for me because I need 3 mechanical sets for my problem.

The project will run for a single value step. I am getting no errors from my geometry or physics checks. I checked my mesh also and there doesn't appear to be any clear problem in it as well.

 

I wonder if anybody can pinpoint the problem and help me solve it because the error code is really ambiguous for the users which is something that I really hope they improve. Getting clear errors pinpointing the errors or problems would be great and saves alot of our time.

Thanks in advance

Farid zidat_20516

Hello Haidar;

 

In addition of the global coordinate system, it mandatory to have a fixed mechanical sets between two mobile mechanical sets, so i created an air or vacum layer with fixed mechanical sets as you can see bellow:

 

This is somthing you can also see in the tutorial on the example of magnetic gear where we use more than one mobile mechanical sets.

 

You can find your project corrected in attachement.

 

Regards 

Farid zidat_20516

Hello Haidar;

 

Can you please share your Flux project? I can see if it is a Flux issue, or a wrong definition of the project.

 

Regards

Haidar Diab_21494

Hello,

Please find attached the flux project.

Regards

Alexandru-Ionel Constantin

Hi Haidar Diab,

 

Your geometry is not created for multiple mechanical sets, because it's created only in XY1 coordinate system.

 

You need to create the points and lines related to face regions assigned to a specific mechanical set in a unique global coordinate system.

 

In your case to create the points,lines and transformation related to the face regions:

- AIR_ROTOR1, FER_ROTOR1, PM1_ROTOR1 and PM2_ROTOR1 in XY1 (a global coordinate system);

- AIR_ROTOR2 and FER_ROTOR2 in COORDSYS_1(a global coordinate system);

- FER_ROTOR3, PM1_ROTOR3 and PM2_ROTOR3 in GEOM_CORRECT_1(a global coordinate system).

 

Best regards!

 

Haidar Diab_21494

Thank you for the helpful tips. I will try that and see if it will solve the error.

 

Best regards

Alexandru-Ionel Constantin

Haidar Diab_21494 said:

Thank you for the helpful tips. I will try that and see if it will solve the error.

 

Best regards

Hi Haidar Diab,

You're welcome!

Pay attention to the coordinate system for definition when you create transformations.

Best regards!

Farid zidat_20516

Hello Haidar;

 

In addition of the global coordinate system, it mandatory to have a fixed mechanical sets between two mobile mechanical sets, so i created an air or vacum layer with fixed mechanical sets as you can see bellow:

 

This is somthing you can also see in the tutorial on the example of magnetic gear where we use more than one mobile mechanical sets.

 

You can find your project corrected in attachement.

 

Regards 

Haidar Diab_21494

Thank you very much for the help and additional tips. Is it possible by any means to have the corrected project in FLUX version 18? If it's not possible it's ok because the problems in my project are clear and I can correct them by myself.

Farid zidat_20516

You are welcome Haidar!

 

I use to work only with the last commercial version of Flux. By the way, it is an opportunity for you to download the last version and have access to the last features.

 

Best regards 

Haidar Diab_21494

I hope the license we have at the laboratory allows the update to the latest commercial version. I will have to check this with my colleagues.

Thank you.

Best regards