CFX Error: Unsupported physical type

Tingting Wu · February 19, 2019, 05:12

Dear all,

I am simulating a blood pump with CFX, but an error accured:

Error #001100279 has occured in subroutine ErrAction
Message:
FBCTYP: Unsupported physical type

Error #001100279 has occured in subroutine ErrAction
Message:
Stopped in routine FBCTYP

I don't really understand where went wrong. Your help will be very appreciated!

Tingting

ghorrocks · February 19, 2019, 05:38

Please attach an image of what you are modelling and your output file including the error.

Opaque · February 19, 2019, 14:10

It seems there is an unsupported boundary condition type. Either a defect in the software since the boundary types are well specified in the UI, or some strange combination triggered the error.

As Glenn suggested, your output file will help a great deal to diagnose the source of your problem

Tingting Wu · February 21, 2019, 06:30

Quote:

Originally Posted by ghorrocks

Please attach an image of what you are modelling and your output file including the error.

Here it the whole output file and a picture of what I'm simulating. Let me know if you need any further questions. Thank you in advance!

Opaque · February 21, 2019, 11:59

There are several issues with the setup; however, let us try to make it run first.

I noticed an expression for torque()@REGION: Impeller. Is that region the surface of the rotor (2D region), or the volume of the impeller (3D region), or the mesh assembly for the impeller (2D+3D region). If any of the last two, that may be the problem.

I would start by removing any reference to a REGION:xxx, and go from there.

Tingting Wu · March 6, 2019, 23:04

Quote:

Originally Posted by Opaque

There are several issues with the setup; however, let us try to make it run first.

I noticed an expression for torque()@REGION: Impeller. Is that region the surface of the rotor (2D region), or the volume of the impeller (3D region), or the mesh assembly for the impeller (2D+3D region). If any of the last two, that may be the problem.

I would start by removing any reference to a REGION:xxx, and go from there.

Thank you! I tried your method and solve the problem it really is the location error. Sorry for the late response and thank you again.

February 19, 2019, 05:12	CFX Error: Unsupported physical type	#1
Tingting Wu New Member Tingting Wu Join Date: Nov 2018 Location: Suzhou, Jiangsu, China Posts: 7 Rep Power: 8	Dear all, I am simulating a blood pump with CFX, but an error accured: Error #001100279 has occured in subroutine ErrAction Message: FBCTYP: Unsupported physical type Error #001100279 has occured in subroutine ErrAction Message: Stopped in routine FBCTYP I don't really understand where went wrong. Your help will be very appreciated! Tingting

February 19, 2019, 05:38		#2
ghorrocks Super Moderator Glenn Horrocks Join Date: Mar 2009 Location: Sydney, Australia Posts: 17,870 Rep Power: 144	Please attach an image of what you are modelling and your output file including the error. __________________ 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
[Other] simulation of closing the gate using moving mesh	simin_ds	OpenFOAM Meshing & Mesh Conversion	8	April 12, 2019 06:49
buoyantBoussineqPimpleFoam Gravity Current	Bish	OpenFOAM	0	February 1, 2018 10:36
Wrong Boundary Conditions (maximum number of iterations) in compressibleInterDyMFoam	silencebreak	OpenFOAM Running, Solving & CFD	0	September 11, 2017 08:05
boundary conditions for simpleFoam calculation	foam_noob	OpenFOAM Running, Solving & CFD	8	July 1, 2015 09:07
Divergent temperature in chtMultiRegion(Simple)Foam	akrasemann	OpenFOAM Running, Solving & CFD	13	March 24, 2014 03:54

February 19, 2019, 14:10		#3
Opaque Senior Member Join Date: Jun 2009 Posts: 1,880 Rep Power: 33	It seems there is an unsupported boundary condition type. Either a defect in the software since the boundary types are well specified in the UI, or some strange combination triggered the error. As Glenn suggested, your output file will help a great deal to diagnose the source of your problem

February 21, 2019, 11:59		#5
Opaque Senior Member Join Date: Jun 2009 Posts: 1,880 Rep Power: 33	There are several issues with the setup; however, let us try to make it run first. I noticed an expression for torque()@REGION: Impeller. Is that region the surface of the rotor (2D region), or the volume of the impeller (3D region), or the mesh assembly for the impeller (2D+3D region). If any of the last two, that may be the problem. I would start by removing any reference to a REGION:xxx, and go from there.