2 HIGH LIFT FUNCTIONAL
ARCHITECTURE
The following describes the High Lift Functional
architecture. The architecture shown in Figure 2 is
the result of a previous study presented in Hardwick,
Hanna, and Panella, 2017. It describes a generic
medium sized commercial aircraft flap system,
characterised by a single transmission line and
distributed actuators spaced symmetrically with
respect to the aircraft centreline. This architecture
presents only a flap system and does not include the
slat actuators.
The physical layout includes elements of the
functionalities that a high lift system needs to
present which are:
• Central source Power Drive Unit (PDU) which
provides the power drive actuation to the
system and has position sensing capability;
This interfaces with the secondary flight
controller for control and monitoring functions.
The PDU is dual channel for redundancy.
Hydraulic valves are controlled by the flight
controller and regulate the flow to the
hydraulic motors. The motors drive a
mechanical gearbox that drives the
transmission.
• Transmission shafts connect the PDU to the
actuators on the wing and hence enabling
synchronous movement of both wings.
• Mechanical wing actuation with four rotary
geared actuators (RGA) per wing; These
contain gearboxes which provide mechanical
advantage to the transmission drive torques.
This enables the transmission to drive
aerodynamic loads with large torques.
• The secondary flight control system interfaces
with the PDU, sensors and safety devices
which arrest the system during failure case
scenarios. It also interfaces with the main
aircraft flight controller.
3 MATHEMATICAL MODEL
Herein, the mathematical model of a High Lift
System is described and mapped into a Simulink
model, which is then described.
The model is used to perform a sensitivity study
to support optimal design point for the selection of
the PDU, considering as the key parameter its gear
ratio. A discussion of the model verification is also
presented.
The first step is to define the model
requirements. Requirements enable the definition of
the overall performance requirement for the system,
operational and environmental conditions, as well as
regulatory considerations are needed to ensure
safety. They set the “boundary conditions” for the
systems, which will need to be validated and
verified.
It is important to consider another constraint
when implementing a simulation model. The model
complexity is proportional to run time. Therefore,
the model fidelity needs to be traded with the speed
of simulation that we want to achieve.
Once the requirements are defined, specific
performance descriptions need to be allocated to the
functional blocks, and model outputs are linked to
the systems requirements, such as:
• Flap system deployment times;
• Flap system hydraulic flow rate;
• Dynamic and steady state transmission
loads;
• PDU normal operating velocity.
Dynamic modelling has been achieved through
the application of first order differential equations.
These equations are represented in the form of a
state-space model within the Simulink modelling
environment, which utilises a non-stiff variable step
ordinary differential solver (ODE). The model
contains continuous states but the governing
equations are non-linear and hence the system is a
non-linear time invariant system. State space
modelling is a control systems technique to represent
the dynamic behaviour of a system as reported in
ZadehandDesoer, 1963.
3.1 Model Architecture
The functional architecture is now mapped into the
simulation environment through the application of
mathematical equations capturing the individual
functions’ behaviour, according to mechanical,
hydraulic and electrical physics laws.
Examples of the equations used to create the
blocks are provided in the following sections.
The principle of operation is the following.
Mechanical transmission blocks connect the PDU to
the actuators. The drive to the PDU is generated by
transferring hydraulic power into mechanical using
hydraulic motors.
Figure 3 highlights the system architecture
mapped into a Simulink model. This contains the
following subsystems: