|
[Sponsors] |
Changing magUInf does not affect lift calculation |
|
LinkBack | Thread Tools | Search this Thread | Display Modes |
October 8, 2022, 05:27 |
Changing magUInf does not affect lift calculation
|
#1 |
New Member
Marius
Join Date: Sep 2022
Posts: 27
Rep Power: 4 |
Hello,
I am currently simulating a s1223 airfoil and want to test it at different speeds. My first test was with magUInf = 22.22 and this was the result for the lift: -112,908 N So the second try was to change the magUInf in the forceCoeffs file to 36.11. After running everything again I still get the same lift of -112,908 N. Is there something that I am missing? I run: blockMesh surfaceFeatureExtract decomposePar mpirun -np 8 snappyHexMesh -overwrite -parallel reconstructParMesh -constant rm -rf processor* rm -rf 0 mv 0.orig 0 decomposePar mpirun -np 8 simpleFoam -parallel reconstructPar -latestTime My calculation is done in Paraview using GenerateSurfaceNormals and calculate the force with Code:
(p*Normals-wallShearStress)*1.225 My forceCoeffs file looks like that: Code:
/*--------------------------------*- C++ -*----------------------------------*\ | ========= | | | \\ / F ield | OpenFOAM: The Open Source CFD Toolbox | | \\ / O peration | Version: v2206 | | \\ / A nd | Website: www.openfoam.com | | \\/ M anipulation | | \*---------------------------------------------------------------------------*/ forceCoeffs1 { type forceCoeffs; libs (forces); writeControl timeStep; timeInterval 1; log yes; patches (clio3rs); rho rhoInf; // Indicates incompressible rhoInf 1; // Required when rho = rhoInf liftDir (0 0 1); dragDir (1 0 0); CofR (3.5 0 0); // Axle midpoint on ground pitchAxis (0 1 0); magUInf 22.22; // 80 km/h lRef 0.2; // chord length Aref 0.28; // Aref=(airfoil chord length)*(length in the spanwise direction of your 2D domain) } /* binField1 { type binField; libs (fieldFunctionObjects); binModel singleDirectionUniformBin; fields (forceCoeff); patches (clio3rs); decomposePatchValues true; CofR ${..forceCoeffs1.CofR}; binData { nBin 20; // output data into 20 bins direction (1 0 0); // bin direction cumulative yes; } writeControl timeStep; } */ // ************************************************************************* // Any ideas? Thank you! Cheers, Marius |
|
October 10, 2022, 06:27 |
|
#2 |
Senior Member
Yann
Join Date: Apr 2012
Location: France
Posts: 1,236
Rep Power: 29 |
Hi Marius,
forceCoeffs is used to compute aerodynamic coefficients (drag coefficient Cd, lift coefficient Cl, etc...) in a file in the postProcessing directory. It does not have any effect on the simulation, it is only a post-processing function. You can also use the forces function object to report forces right from OpenFOAM instead of computing it in ParaView. If you want to change the flow velocity in the simulation, you need to update the velocity boundary condition in 0/U file. Cheers, Yann |
|
October 10, 2022, 06:29 |
|
#3 |
New Member
Marius
Join Date: Sep 2022
Posts: 27
Rep Power: 4 |
Hi Yann,
thanks a lot for your answer. I just updated the U file and now everything is fine. Cheers, Marius |
|
Tags |
airfoil, forcecoeffs, lift and drag, maguinf |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Lift and drag coefficient calculation | Lowt3ch | FLUENT | 1 | March 5, 2018 12:04 |
[PyFoam] having problems with pyfoam Installation | vitorspadetoventurin | OpenFOAM Community Contributions | 3 | December 2, 2014 08:18 |
Wrong Drag and Lift Coefficient when changing AoA | inspiron | FLUENT | 1 | November 27, 2013 14:00 |
Changing inflow velocity direction deteriorates lift and drag | ziggo | FLUENT | 3 | July 24, 2013 09:39 |
Thin foil analsis (sail) - Lift Coeff Problem | Kelvin | CFX | 3 | December 22, 2008 17:22 |