Hey! Due to my project I need to do a simulation with Fluent. Everything went well until I started the simulation. After some time there was an error and Fluent simply closed. Since then Fluent fails to start when I want to open the project. I can still
I would recommend to mark this one as resolved (Is Solution) for the Cortex issue since it's a separate issue. Then, create a new thread in that section. If you like to reference some info here, you can provide the link to this thread in that new thread. Thanks, Win ...
发现读入了case之后，fluent自动退出，运行路径绝对没有中文字符，只是会出现一个cortexerror的文本文档，...
Ansys.Fluent.Cortex.CortexCommandFailedException: 应用案例和设置信息时,FLUENT中发生错误。应用案例和设置信息时,FLUENT中发生错误。在Ansys.Fluent.Cortex.CortexCommunicator.SendMessage(String msg, String msgKey, String errorMessage, Boolean waitForReply)在Ansys.Fluent.FluentCommunicator.UpdateSetupInfo(Dictionary...
报错7:Error: floating point exception 1.可能是公式里的数值太夸张了,建议用计算器验算 2.operating 气压太大,导致一些物性参数溢出,可以把气压先改小再改大;或者把物性改为定值 3.可在udf对一个数值作限制,避免负数出现(尤其是所有作为商的部分) if 语句:if (X < 0) X=0; 报错8:Cortex received a fa...
报错8:Cortex received a fatal signal (unrecognized signal)./Error Object: () 1.重启fluent 2.网格优化 3.检查边界条件和初始条件 4.检查udf是否有语法错误 报错9:Stabilizing Coupled to enhance linear solver robustness. 报错10:reversed flow in 3 faces on pressure-outlet ...
-byaboluocn Error cortex time 2/21/12 14:3:32 FLUENT received fatal signal (ACCESS_VIOLATION)5 , + o O1 A0 Z y- F 1. Note exact events leading to error.7 m9 Z+ |7 - 6 O( c: o 2. Save case/data under new name.6 r4 & k% u: ? 3. Exit program and restart to ...
4.error:divergence detected in AMG solver 代数多重网格计算发散,出现原因一般是网格质量比较低,或者是时间步长太大。此时应提高网格质量,对网格加密,采用结构化四边形或六面体网格。 5.error:temperature divergence detected in AMG solver 代数多重网格计算发散,出现原因一般是网格质量比较低,或者是时间步长太大。此...
这些都无所谓，最不能让人忍受的就是软件的自动退出，使用ANSYS 14.5.2的Fluent进行计算总是在计算了一定时间后，Fluent就自动退出并且在当前文件夹下生成一个叫做“cortexerror.log”的文件，重复了很多次做了很多设置，这个问题依然存在，并且无论在是Windows Server上还是Redhat上还是CentOS上都是如此，并且打开这个...
这些都无所谓,最不能让人忍受的就是软件的自动退出,使用ANSYS 14.5.2的Fluent进行计算总是在计算了一定时间后,Fluent就自动退出并且在当前文件夹下生成一个叫做“cortexerror.log”的文件,重复了很多次做了很多设置,这个问题依然存在,并且无论在是Windows Server上还是Redhat上还是CentOS上都是如此,并且打开这个日志...