CFD Online Discussion Forums

CFD Online Discussion Forums (https://www.cfd-online.com/Forums/)
-   CFX (https://www.cfd-online.com/Forums/cfx/)
-   -   What is this errorError detected by routine NAMLST1 CNAMS = MESH_ALIAS/NAMES CVALU (https://www.cfd-online.com/Forums/cfx/227912-what-errorerror-detected-routine-namlst1-cnams-mesh_alias-names-cvalu.html)

Madhu Kalyan June 14, 2020 07:34

What is this errorError detected by routine NAMLST1 CNAMS = MESH_ALIAS/NAMES CVALU
 
I am simulating a heat exchanger and this is the first time I got this error message
Error detected by routine NAMLST1
CNAMS = MESH_ALIAS/NAMES CVALUE

I have simulated a part of this heat exchanger assuming symmetry conditions and I never got this error and the results were satisfactory. Now when I am modelling the whole thing this message came up out of the blue. Can anyone suggest me how to go about this error?

karachun June 14, 2020 09:07

Post whole .out file.

Madhu Kalyan June 14, 2020 22:35

1 Attachment(s)
Attached the out file. kindly take a look

ghorrocks June 15, 2020 03:21

Looks like the mesh or your def file are corrupted. I would go back to CFX-Pre and generate them again.

Madhu Kalyan June 15, 2020 06:14

It didn't work. I tried to re run with a new definition file but couldn't. The interfaces were also good. Only some primitive 2D surfaces are present which I don't know how they got there. They were present in my previous simulation too but that didn't pose any problem.have you got any other advice for me?

ghorrocks June 15, 2020 07:35

No other advice as the error message does not say anything useful and you have not described much about what you are doing.

All I can say is that it appears something on your mesh or def file appears to be corrupted. The error message seems to mention a boundary condition, so it might be something to do with that.

But this is all very vague. You are just going to have to try some things out until it starts working. Start with a tutorial example or some other known working simulation, and change it to your simulation one object at a time. That might help identify which object is causing the problem.

Opaque June 15, 2020 08:02

It seems one of the domain interface sides "Location" has too many long names.

The message comes from BCP17, i.e. a boundary. Which one? hard to tell.

However, the only boundary with many names in your setup seems to be the domain interface sides.

How to solve the problem? Not a clue, but perhaps creating a composite region (see Insert/Mesh Region/Composite) and join the individual locations into a single name may bypass the problem.


All times are GMT -4. The time now is 17:33.