Abstract

A comprehensive experimental investigation was undertaken to explore the flow field in the tip clearance region of a turbine rotor to understand the physics of tip leakage flow. Specifically the paper looks at its origin, nature, development, interaction with the secondary flow, and its effects on performance. The experimental study was based on data obtained using a rotating five-hole probe, laser doppler velocimeter, high-response pressure probes on the casing, and static pressure taps on the rotor blade surfaces. The first part of the paper deals with the pressure field and losses. Part II presents and interprets the vorticity, velocity, and turbulence fields at several axial locations. The data provided here indicates that the tip leakage vortex originates in the last half chord. The leakage vortex is confined close to the suction surface corner near the blade tip by the relative motion of the blade and the casing, and by the secondary flow in the tip region. The tip leakage flow clings to the blade suction surface until midchord then lifts off of the suction surface to form a vortex in the last 20% of the blade chord. The relative motion between blades and casing leads to the development of a scraping vortex which, along with the secondary flow, reduces the propagation of the tip leakage flow into the mainflow. The rotational effects and corriolis forces modify the turbulence structure in the tip leakage flow and secondary flow as compared to cascades.

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call

Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.