Matlab Code to Predict Blade Element Theory (BET) for a Rotor in Hover and Axial FlightUse Chapter 3 in Leishman as a guide. You want to predict the behavior of a rotor in hover and...

Matlab Code to Predict Blade Element Theory (BET) for a Rotor in Hover and Axial Flight

Use Chapter 3 in Leishman as a guide. You want to predict the behavior of a rotor in hover and axial flow using BET.

Guidelines:

• 
  
  
  

  
  
  
  The Matlab code should ask the user for the following inputs:
  
  
  
  
  

  
  
  
  
  
  
  
  
  • 
    
    
    

    
    
    
    –
    
    
    
    
    Rotor Definition: rotor radius, twist and taper (use 3/4R reference values along with linear twist and taper ratios), lift-curve slope, airfoil drag coefficients (to use in drag estimates),
    
    
    
    
    M
    
    
    DD
    
    
    
    
    (to account for compressibility), number of rotor blades, solidity
    
    
    
    
    

    
    
    
    
  
  
  
  
  • 
    
    
    

    
    
    
    –
    
    
    
    
    Flight Condition: Axial velocity, weight, angular rotor velocity (in r/s), Prandtl loss factors for both root and tip (
    
    
    f
    
    
    root
    
    
    , f
    
    
    tip
    
    
    ).
    
    
    
    
    

    
    
    
    
  
  
  
  
  
  
  
  




• 
  
  
  

  
  
  
  The Matlab code should provide the following outputs: output variables for hover, one climb and one descent (identify conditions); plot of inflow across radius for hover and one climb condition (identify it), plot of lift coefficient (or thrust coefficient) across radius for hover and one climb condition (identify it), plot of thrust versus power (like Fig. 3.23 and 3.24 for trends), plot of thrust and power coefficient for the ratio of climb to hover velocities (like Fig. 3.25).
  
  
  
  
  

  
  
  
  




• 
  
  
  

  
  
  
  You are encouraged to use information in the textbook and elsewhere to verify your code. If you do, cite where the data are from, how you verified/validated the item, and write it up in the project report.
  
  
  
  
  

  
  
  
  




• 
  
  
  

  
  
  
  The code should be commented and include Leishman (2nd edition) equation numbers.
  
  
  
  
  

  
  
  
  




• 
  
  
  

  
  
  
  The professor and/or TAs will run conditions where answers are known, which will be used to ensure that the
  
  
  
  
  

  
  
  
  

  
  
  
  code is correct.
  
  
  
  
  

  
  
  
  




• 
  
  
  

  
  
  
  Along with the Matlab code (include a paper version and an electronic version), a project report is needed. The project report should be typed up, showing what you did in the code, as well as results of your validation runs. Plots should be labeled nicely and using engineering units. Any references you used should be cited and referenced in order of their use. Use AIAA or VFS reference notation. The project report should be approximately 5-10 pages.