Fan curve table

totocros · September 20, 2015, 07:34

Hello,

I am doing aeroacoustic simulation on a fan in a cylinder domain.
I use "in-place" interfaces and "fan interfaces" as type in the properties windows.

In physics conditions, I setted fan curve as "Table" and then I need to input the table in the physic values.

The problem is I don't know how could I get this table ??

If someone knows something about this, please I would appreciate some help.

Thank you.

fluid23 · September 21, 2015, 10:18

Typically when someone elects to use the fan interface or the fan source you are trying to approximate the behavior of a fan with known performance. Either that or you have some idea of the delta P and swirl characteristics you want to duplicate.

Are you trying to examine the aeroacoustic properties of the fan itself? If so, the interface/source approach is wholly inappropriate. You should be modeling the fan and using rigid body motion and modeling the blades of the fan rather than approximating their effect.

totocros · September 22, 2015, 02:56

Quote:

Originally Posted by MBdonCFD

Typically when someone elects to use the fan interface or the fan source you are trying to approximate the behavior of a fan with known performance. Either that or you have some idea of the delta P and swirl characteristics you want to duplicate.

Are you trying to examine the aeroacoustic properties of the fan itself? If so, the interface/source approach is wholly inappropriate. You should be modeling the fan and using rigid body motion and modeling the blades of the fan rather than approximating their effect.

Thank you, I understood that I must used the rigid body motion for the unsteady simulation because I am trying to examine the aeroacoustic properties of the fan itself. But when I did it, a warming windows appears saying: "a floating point exception has occurred: floating point exception [Overflow] Context: star.segregatedflow.SegregatedFlowSolver"
maybe it comes from my under relaxation factor values for velocity and pressure, I really do not know ... by the way thank you for your quick answer

fluid23 · September 22, 2015, 09:47

Try using a coupled solver if the segregated approach is failing. Its a better method for this anyway.

September 20, 2015, 07:34	Fan curve table	#1
totocros New Member thomas Join Date: Jul 2015 Posts: 8 Rep Power: 11	Hello, I am doing aeroacoustic simulation on a fan in a cylinder domain. I use "in-place" interfaces and "fan interfaces" as type in the properties windows. In physics conditions, I setted fan curve as "Table" and then I need to input the table in the physic values. The problem is I don't know how could I get this table ?? If someone knows something about this, please I would appreciate some help. Thank you.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
How to build current blower fan model in Flotherm	eric0722	FloEFD, FloWorks & FloTHERM	3	January 2, 2021 03:36
Fan Curve Model with CHT simulation	mariconeagles96	CFX	5	April 22, 2015 02:31
Considering the operating point instead of the fan curve	saisanthoshm88	CFX	8	August 9, 2012 07:57
Propeller Fan Curve Simulation	Teng_YJ	FLUENT	2	February 16, 2009 20:37
CFX4.3 -build analysis form	Chie Min	CFX	5	July 13, 2001 00:19

September 21, 2015, 10:18		#2
fluid23 Senior Member Matt Join Date: Aug 2014 Posts: 947 Rep Power: 18	Typically when someone elects to use the fan interface or the fan source you are trying to approximate the behavior of a fan with known performance. Either that or you have some idea of the delta P and swirl characteristics you want to duplicate. Are you trying to examine the aeroacoustic properties of the fan itself? If so, the interface/source approach is wholly inappropriate. You should be modeling the fan and using rigid body motion and modeling the blades of the fan rather than approximating their effect.

September 22, 2015, 09:47		#4
fluid23 Senior Member Matt Join Date: Aug 2014 Posts: 947 Rep Power: 18	Try using a coupled solver if the segregated approach is failing. Its a better method for this anyway.