Next: Miscellaneous
Up: Elements
Previous: Output Elements
Contents
Subsections
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 |
= |
1 - memory Unominal |
|
| |
|
+ memory Uprevious |
|
with
Unominal =
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.
The following output is available for all rotor elements:
- element label
- rotor force in x direction (longitudinal force)
- rotor force in y direction (lateral force)
- rotor force in z direction (thrust)
- rotor moment about x direction (roll moment)
- rotor moment about y direction (pitch moment)
- rotor moment about z direction (torque)
- mean inflow velocity, based on momentum theory
- reference velocity at rotor center, sum of airstream
and craft node velocity
- rotor disk angle
- advance parameter
mathend000#
- inflow parameter
mathend000#
- advance/inflow angle
= arctan
/
mathend000#
- reference azimuthal direction
mathend000#, related to rotor yaw angle
- boolean flag indicating convergence in reference induced velocity
computation iteration
- number of iterations required for convergence
The dynamic inflow model adds the columns
- constant inflow state
- sine inflow state (lateral)
- cosine inflow state (longitudinal)
The following data is available:
- "Tx" rotor force in x direction (longitudinal force)
- "Ty" rotor force in y direction (lateral force)
- "Tz" rotor force in z direction (thrust)
- "Mx" rotor moment about x direction (roll moment)
- "My" rotor moment about y direction (pitch moment)
- "Mz" rotor moment about z direction (torque)
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