Skip to main content

meshing wind turbine blade in Turbogrid


     Can't export points when importing CAD in Blade modelor (DesignModeler)
    Answer:
    The problem was with the split in the blade solid. This works when you Boolean/unite the two solids.

    You will also need to ensure the last profile in the Export Points is No for export, as there is no intersection because of the tip gap. This will export the blade.



    1. How is blade tip represented in Turbogrid? the original blade is flat at tip, Does the blade tip (Turbogrid) reprensented by the last layer loop cut near the tip? if so, then the blade geometry has been changed a little at the tip.

    2. how to set up the tip shroud gap distance? I noticed the blade is extends to the shroud in Turbogrid, but the LE (green line in zx plane/meriondional plane) and TE (red) doesn't not.

    3. How is the shape of periodic Boundary ( auxillary view ) defined?
    In my mode, the shape of periodic Boundary is highly twisted (not good for mesing), while the example CAD is good. see attached figures. In turbogrid tutorial input, I've learned the hub and shourd curves are defined as curves follow the camber line of blade section (airfoil shape).




    Answer:
    BladeEditor generates profiles on surfaces of revolution, so it will not generate flat profile as you want.

    One option would be use the exiting export points and write out the crv files.
    You will then need to edit the profile.crv Then add a new profile or replace the last profile with a loop of points for the flat profile.

    You can then load this into TurboGrid and set the Shroud tip to the last profile. This will cut blade using the specified profile.

     As for the periodic boundary, it will follow the twist of the blade. But the generated mesh should give you a reasonable mesh.

    Important Also note that you can have mesh issues if blade angle is close 90 degree with regard to axial direction.

    Is so then you will need to use ICEM CFD Hexa to generate a reasonable mesh.


    Feedback 2
    Typically wind turbine blades are highly twisted and as you have noted do not have a shroud. So this cannot be meshed in TurboGrid.

    The best option is to use ICEM CFD Hexa to generate a grid for such blades.

    One way to overcome this is to split the blade near the tip, so that you put an artificial shroud. This can then be mesh in TurboGrid.

    As for the tip section you can generate a mesh in ICEM CFD Hexa or tetra and use ggi's to connect the two meshes in CFX Pre.

Labels:

Comments

Post a Comment

Popular posts from this blog

TUI Fluent

‎ Table of Contents 1. TUI 1.1. Examples 1.1.1. Steady 1.1.2. Unsteady 1.2. discretization schemes 1.3. Turbulence model 1.4. Reference 1.5. Save residual 1.6. Journal 1.6.1. record journal GUI 1.6.2. The interactive TUI inside Fluent helps: 1.7. define 1.7.1. boundary-conditions 1.8. change rotational velocity of moving reference frame 1.8.1. batch model 1.8.2. interactive console TUI 1.9. set background color 1.9.1. invalid command [background] 1.10. syntax 1.11. Batch model 1.12. Boundary condition 1.12.1. Inlet BC 1.13. Animation/residual/monitor on cluster 1.14. Solver 1.15. Change pressure-velocity-coupling model in batch mode 1.16. time step size 1.17. Modifying the View 1.18. initialization 1.19. discretization schemes 1.20. Set under relaxation 1.21. log of execute makefile 1 TUI keywords: Background Execution on Linux Systems, journal file Programming language : Scheme , as a Lisp d...
1 comment
Read more

Fluent Error FAQ

  Process 1928: Received signal SIGSEGV. Running on windows Mesh size, 12M serial     Error:  received a fatal signal (Segmentation fault).     Error Object: #f parallel     select 4 processors         error information     Node 0: Process 1928: Received signal SIGSEGV.         Node 5: Process 2824: Received signal SIGSEGV.     MPI Application rank 0 exited before MPI_Finalize() with status 2      The fl process could not be started.         Reason         This is primarily a Windows issue.                 If running Fluent with -t1 or higher number of processes and leave the session for an extended period of time (2-20 hours), it receives the following message in the console: ...
1 comment
Read more

Turbulent viscosity limited to viscosity ratio of 1e+05

** Turbulent viscosity limited to viscosity ratio of 1e+05 *** reason The possible *causes* for large turbulent viscosity ratio include: - Bad initial conditions for the turbulence quantities (k and e) - Improper turbulent boundary conditions - Skewed cells *** solution If the problem is not caused by *bad mesh*, then *the beginning of the phenomena* can usually be avoided by: -Turn off solving *turbulence equations* for the first 100-200 iterations -Turn on turbulence and continue iterations If the problem occurs *in the middle of the iteration process*, then use the following procedure: - Stop the iteration - Turn *off* all equations except the *turbulence equations* - Increase turbulence under relaxation factors (URFs) (k and e) to 1 and iterate for 20-50 iterations - *Turn back all equations* and reduce the turbulence URFs to 0.5-0.8 and then continue iterations - Repeat the above steps for several times For *faster convergence*, it might be useful to obtain an initial solution wit...
3 comments
Read more