What is this errorError detected by routine NAMLST1 CNAMS = MESH_ALIAS/NAMES CVALU

Madhu Kalyan · June 14, 2020, 08:34

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, 10:07

Post whole .out file.

Madhu Kalyan · June 14, 2020, 23:35

Attached the out file. kindly take a look

ghorrocks · June 15, 2020, 04: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, 07: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, 08: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, 09: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.

June 14, 2020, 08:34	What is this errorError detected by routine NAMLST1 CNAMS = MESH_ALIAS/NAMES CVALU	#1
Madhu Kalyan New Member Madhu Kalyan Join Date: Jun 2020 Posts: 7 Rep Power: 6	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?

June 15, 2020, 04:21		#4
ghorrocks Super Moderator Glenn Horrocks Join Date: Mar 2009 Location: Sydney, Australia Posts: 17,870 Rep Power: 144	Looks like the mesh or your def file are corrupted. I would go back to CFX-Pre and generate them again. __________________ Note: I do not answer CFD questions by PM. CFD questions should be posted on the forum.

June 15, 2020, 08:35		#6
ghorrocks Super Moderator Glenn Horrocks Join Date: Mar 2009 Location: Sydney, Australia Posts: 17,870 Rep Power: 144	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. __________________ Note: I do not answer CFD questions by PM. CFD questions should be posted on the forum.

June 15, 2020, 09:02		#7
Opaque Senior Member Join Date: Jun 2009 Posts: 1,880 Rep Power: 33	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. __________________ Note: I do not answer CFD questions by PM. CFD questions should be posted on the forum.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
How to make user routine just be called once in one time step?	doublestrong	CFX	3	October 22, 2018 00:06
user subroutine error	CFDUSER	CFX	2	December 9, 2006 07:31
user defined function	cfduser	CFX	0	April 29, 2006 11:58

June 14, 2020, 10:07		#2
karachun Senior Member Join Date: Nov 2015 Posts: 246 Rep Power: 12	Post whole .out file.

June 15, 2020, 07:14		#5
Madhu Kalyan New Member Madhu Kalyan Join Date: Jun 2020 Posts: 7 Rep Power: 6	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?