Strange torque calculation
1 Attachment(s)
Hello,
I have trouble calculating the shaft torque of a mixer. The problem can be illustrated on the mixerVesselAMI2D tutorial example, though appears on more complex geometries as well. In order to reproduce, the error, I did the following:  in ControlDic file I added the following lines for the torque calculation: libs ("libforces.so"); functions { forces { type forces; functionObjectLibs ("libforces.so"); patches (rotor); rhoName rhoInf; rhoInf 1.0; // meaning that you need to multiply result with your assumed density in kg/m3 in order to get N m CofR (0 0 0.001); //Origin for moment calculations outputControl outputTime; outputInterval 1; } } Then I altered transportProperties: transportModel Newtonian; nu nu [ 0 2 1 0 0 0 0 ] 300; This means a high viscous fluid as I intend to simulate. You can use a Cross model too, has the same effect. In decomposeParDict, I changed the number of processors to the number I have: numberOfSubdomains 6; The I did run it using mpi. This example did not work, meaning it did not converge. The calculation did hang at 0.0046 s calculated time and did only minor progress over time. I then changed relaxation in U by manipulating the fvSolution file: relaxationFactors { fields { } equations { "U.*" 0.1; } } This example did work. I did then the calculation again using 0.6. The attached graph shows the z axis torque value. As one can see, the results differ significantly. An additional hint: I have computed another example of a vessel with no baffels. In this case, using the Cross model, I get a realistic end values since there are no fluctuating forces (due to baffels). However the starting value (0.1 s) and the slope to the end value differ significantly depending on which relaxation I use. My question: Does this make sense? I think relaxation should not affect end results, but convergence only. Is this a known issue? My impression is that one of the iteration routines uses delta result to stop iteration instead of functional value (e.g. f(x_n) < small error). Needless to say that I want to use this model for a vessel having interactions between agitator and wall mounted elements. Fluctuations of torque are therefore to be expected. Regards, Daniel 
Well, is there anybody who could help?

rhoInf 1.0; // meaning that you need to multiply result with your assumed density in kg/m3 in order to get N m
If it was water, isnt should be 1000 kg/m3? 
Hello Sharonyue,
Yes, since this is an incompressible solver (pimpleDymFoam), calculation is independent on rho, or in other words: all calculated forces (including pressure) divided by rho have an identical solution. Same applies for pressure: you need to multiply all values by rho to get standard pressure units such as Pa. Unit for p in OpenFoam is m/s2. Regards, Daniel 
1 Attachment(s)
Quote:
And recently I dont what is Code:
forces output: With respect to my case. In my rotate region,there are some impellers and shaft. I want to sum the torque.How can I do this? Code:
functions Code:
Time = 1 
Hello Sharonyue,
What I figured is that the output of "forces" is the following:  the left column is obviously the time scale  the next 3 columns are the forces, which act in CofR  the next 3 columns are the moments, which act in CofR The patch should be the one in rotation (I guess that is what is on your picture), but I would think the stator may work as well). The axis of rotation should cross CofR. Since one of the Cartesian axis is the axis of rotation (defined in dynamicMeshDic) then you should be able to identify the drive torque (moment in direction of the axis of rotation) and the 2 bending moments in the plane perpendicular to the axis of rotation. If your rotor protrudes the stator only on one side, you should define CofR being in the plane where it protrudes. If it protrudes on both sides you need the calculation on both ends. The net torque then is the difference between the 2 and the actual torque on both ends depends on your drive motor situation (which OpenFoam cannot know). Regards, Daniel Hope that helps, Daniel 
All times are GMT 4. The time now is 14:49. 