Navigation Functionalities for an Autonomous UAV Helicopter
Navigation Functionalities for an Autonomous UAV Helicopter
Navigation Functionalities for an Autonomous UAV Helicopter
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
3.5. SIMULATION RESULTS 23<br />
3.5 Simulation results<br />
The validation of the RMAX helicopter model c<strong>an</strong> be found in [4]. In this<br />
section, the validation of the simulation procedure with the control system<br />
in the loop will be described. The results of two simulation tests of the<br />
PFCM, which will also be described later in the thesis, will be provided.<br />
The PFCM is a control function that enables the helicopter to follow 3D<br />
path segments. The path segments will be given to the PFCM which is in<br />
a closed loop with the simulator. The simulation results will be compared<br />
to the same PFCM implemented on the helicopter plat<strong>for</strong>m. This is not a<br />
validation of the simulator since the control function is in the loop. What<br />
is interesting is the <strong>an</strong>alysis of the differences of the closed loop behavior<br />
between the flight-test <strong>an</strong>d the simulation. The helicopter is comm<strong>an</strong>ded<br />
to fly a segment path starting from a hovering condition until reaching a<br />
target speed. The path also presents a curvature ch<strong>an</strong>ge. The same control<br />
function has been used <strong>for</strong> the two tests. In Fig. 3.5 <strong>an</strong>d Fig. 3.6 the<br />
simulation (dashed line) <strong>an</strong>d flight-test (continuous line) are overlapped on<br />
the same graph. The upper-left plot of Fig. 3.5 represents the helicopter<br />
path seen from above. The difference in position between the simulation<br />
<strong>an</strong>d flight-test is very small, below one meter <strong>an</strong>d c<strong>an</strong>not be seen in detail<br />
from the plot. In the same diagram the velocity components <strong>an</strong>d the total<br />
velocity are plotted. This shows that the simulated velocity <strong>an</strong>d the real<br />
velocity are quite close. In this test the helicopter was accelerated to 5 m/s<br />
<strong>for</strong>ward speed. In Fig. 3.6 the results <strong>for</strong> the pitch <strong>an</strong>d roll inputs <strong>an</strong>d the<br />
attitude <strong>an</strong>gles are presented. The pitch <strong>an</strong>d roll inputs present a steady<br />
state error compared to the simulation while the pitch <strong>an</strong>d roll <strong>an</strong>gles are<br />
in good agreement.<br />
In Fig. 3.7 <strong>an</strong>d Fig. 3.8 the same path segment is tested but the helicopter<br />
accelerates until 10 m/s is reached. The simulated position <strong>an</strong>d<br />
velocity are still in good agreement with the flight-test experiment while<br />
the pitch <strong>an</strong>d roll <strong>an</strong>gles are worse. This is due to the fact that the aerodynamics<br />
of the rotor is not modeled. Taking into account such effects is<br />
necessary <strong>for</strong> flight conditions far from hovering. It is interesting to notice<br />
that the simulation c<strong>an</strong> predict quite accurately the saturation of the roll<br />
input (Fig. 3.8) at around 845 sec. This could be a sign that the helicopter<br />
is flying too fast <strong>for</strong> the current path curvature, <strong>an</strong>d <strong>an</strong> adjustment in the