next up previous contents
Next: Miscellaneous Up: Elements Previous: Output Elements   Contents

Subsections

Rotor

The rotor element is used to associate the aerodynamic elements that model the blades of a helicopter rotor when some inflow related computations are required. By means of different inflow models, and by means of the aerodynamic load contributions supplied by the aerodynamic elements, the rotor element is able to compute the induced velocity at an arbitrary point on the rotor disk. This velocity term in turn is used by the aerodynamic elements to determine a better estimate of the boundary conditions. The syntax of the rotor element is:
    <normal_arglist> ::= <craft_node> ,
            [ hinge , (Mat3x3)<rotor_orientation> , ]
        <rotor_node> ,
        induced velocity , <induced_velocity_model>
The optional rotor_orientation is required when axis 3 of the craft_node is not aligned with the rotor axis; axis 3 of the rotor_node must be aligned with the rotor axis.

Note: after the keyword induced velocity there used to be a colon is used as separator. This changed for uniformity with the rest of the syntax. No backwards compatibility is provided, so users are urged to update their models.

There are five models of induced velocity. The first is no induced velocity; the syntax is:

    <induced_velocity_model> ::= no
There is no argument list. This element doesn't compute any induced velocity, but still computes the rotor traction for output purposes, if output is required. The others have a fairly common syntax. The first three are uniform, glauert and mangler induced velocity models:
    <induced_velocity_model> ::= { uniform | glauert | mangler } , 
        <reference_omega> , <reference_radius> 
        [ , ground , <ground_node> ]
        [ , delay , (drive_caller) <memory_factor> ]
        [ , max iterations , <max_iterations> ]
        [ , tolerance , <tolerance> ]
        [ , eta , <eta> ]
        [ , correction , <hover_correction_factor> ,
            <ff_correction_factor> ]
the reference_omega field is used to decide whether to inhibit or not the induced velocity computation if the rotor speed is very low; the reference_radius field is used in the adimensionalization of the rotor related parameters.
The memory_factor, the hover_correction_factor and the ff_correction_factor (forward flight) are used to correct the nominal induced velocity, according to the formula
Ueffective = $\displaystyle \left(\vphantom{ 1 - \mathtt{memory\_factor} }\right.$1 - memory$\displaystyle \_factor$$\displaystyle \left.\vphantom{ 1 - \mathtt{memory\_factor} }\right)$Unominal  
      + memory$\displaystyle \_factor$ Uprevious  

with

Unominal = $\displaystyle {\frac{{T}}{{2 \rho A V_{tip} \sqrt{
\cfrac{\lambda^2}{\mathtt{h...
...orrection\_factor}^4}
+ \cfrac{\mu^2}{\mathtt{ff\_correction\_factor}^2}
}}}}$

mathend000#

The memory_factor parameter is used to combine the current reference induced velocity with the induced velocity at the previous step; no delay means there is no memory of the previous value (Note: for historical reasons, the keyword weight can be used instead of delay).
The memory_factor parameter defaults to 0; the hover_correction_factor and the ff_correction_factor parameters default to 1.
The max_iterations, the tolerance and the eta parameters refer to the iteration cycle that is performed to compute the nominal induced velocity; after max_iterations, or when the absolute value of the difference between two iterations of the nominal induced velocity is less than tolerance, the cycle breaks. Only a fraction eta of the difference between two iterations of the nominal induced velocity is actually used; eta defaults to one. The default is to make only one iteration, which is backward-compatible with the original behavior. Note: the syntax of the correction factor input changed from MBDyn 1.1 to MBDyn 1.2, where two different factors, according to conventional models (e.g. CAMRAD/JA), have been considered instead of one. No backward compatibility has been implemented because this is a very specialistic parameter and it was introduced very recently.

The last one uses a dynamic inflow model, based on [11], with inflow states. The syntax is:

    <induced_velocity_model> ::= dynamic inflow , 
        <reference_omega> , 
        <reference_radius> 
        [ , ground , <ground_node> ]
        [ , initial value , <const_vel> ,
            <cosine_vel> ,
            <sine_vel> ]
        [ , max iterations , <max_iterations> ]
        [ , tolerance , <tolerance> ]
        [ , eta , <eta> ]
        [ , correction , <hover_correction_factor> ,
            <ff_correction_factor> ]
Most of the entries are the same as for the previous models; the delay optional entry is missing, while the three states, corresponding to average, fore-aft and lateral inflow, can be explicitly initialized by means of the optional entry initial value.

Output

The following output is available for all rotor elements:
  1. element label
  2. rotor force in x direction (longitudinal force)
  3. rotor force in y direction (lateral force)
  4. rotor force in z direction (thrust)
  5. rotor moment about x direction (roll moment)
  6. rotor moment about y direction (pitch moment)
  7. rotor moment about z direction (torque)
  8. mean inflow velocity, based on momentum theory
  9. reference velocity at rotor center, sum of airstream and craft node velocity
  10. rotor disk angle
  11. advance parameter $ \mu$ mathend000#
  12. inflow parameter $ \lambda$ mathend000#
  13. advance/inflow angle $ \chi$ = arctan$ \left(\vphantom{ \mu/\lambda }\right.$$ \mu$/$ \lambda$$ \left.\vphantom{ \mu/\lambda }\right)$ mathend000#
  14. reference azimuthal direction $ \psi_{0}^{}$ mathend000#, related to rotor yaw angle
  15. boolean flag indicating convergence in reference induced velocity computation iteration
  16. number of iterations required for convergence
The dynamic inflow model adds the columns
  1. constant inflow state
  2. sine inflow state (lateral)
  3. cosine inflow state (longitudinal)

Private Data

The following data is available:
  1. "Tx" rotor force in x direction (longitudinal force)
  2. "Ty" rotor force in y direction (lateral force)
  3. "Tz" rotor force in z direction (thrust)
  4. "Mx" rotor moment about x direction (roll moment)
  5. "My" rotor moment about y direction (pitch moment)
  6. "Mz" rotor moment about z direction (torque)


next up previous contents
Next: Miscellaneous Up: Elements Previous: Output Elements   Contents
MBDyn: MultiBody Dynamics Software
Document version: 1.3.4-Beta
Last update: Mon Aug 25, 2008
Maintained by mbdyn@aero.polimi.it