DASL Wiki

User Tools

Site Tools

Trace: • getting_started
simulink_quadcopter_simulation

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
simulink_quadcopter_simulation [2025/04/26 21:58] – yehyunsimulink_quadcopter_simulation [2025/04/26 22:21] (current) – yehyun
Line 22: Line 22:
   * Deploy algorithms to a real Parrot Minidrone   * Deploy algorithms to a real Parrot Minidrone
   * Validate the results using motion capture data   * Validate the results using motion capture data
-  * Modify the simulation for new drone specifications 
 \\ \\
 ---- ----
Line 310: Line 309:
  
 The following video shows the experimental setup. The Parrot Mambo drone, loaded with the deployed controller, was flown in the motion capture space while the flight data was simultaneously collected using mocap tracking: The following video shows the experimental setup. The Parrot Mambo drone, loaded with the deployed controller, was flown in the motion capture space while the flight data was simultaneously collected using mocap tracking:
-     {{youtube>ya10C-6nGKU?large}}+{{youtube>ya10C-6nGKU?large}}
  
 In this experiment, a step input was applied to the Z-axis command to observe the altitude control performance. Two different scenarios were tested: In this experiment, a step input was applied to the Z-axis command to observe the altitude control performance. Two different scenarios were tested:
  
 **Scenario 1: Default Drone Weight** **Scenario 1: Default Drone Weight**
-A step input commanding a rise from approximately 0.6 meters to 1.1 meters was given. The comparison between the simulation and real flight data is shown below:+\\ A step input commanding a rise from approximately 0.6 meters to 1.1 meters was given. The comparison between the simulation and real flight data is shown below: 
 +{{ :simulator_part5_8.jpg?nolink&800 |}}
  
 The blue solid and dashed lines represent the simulator and real-world Z positions, respectively. The results demonstrate that the real drone altitude closely followed the simulation prediction, validating the accuracy of the simulated model under nominal conditions. The blue solid and dashed lines represent the simulator and real-world Z positions, respectively. The results demonstrate that the real drone altitude closely followed the simulation prediction, validating the accuracy of the simulated model under nominal conditions.
  
 **Scenario 2: Additional Payload** **Scenario 2: Additional Payload**
-In this test, a 5g weight was attached to the drone to assess the robustness of the controller and the simulator under additional load conditions. The results are shown below:+\\ In this test, a 5g weight was attached to the drone to assess the robustness of the controller and the simulator under additional load conditions. The results are shown below:
  
 Despite the added weight, the actual drone flight trajectory remained highly consistent with the simulator's prediction, especially in the Z-axis control. This suggests that the Simulink-based model maintains its reliability even under moderate payload variations. Despite the added weight, the actual drone flight trajectory remained highly consistent with the simulator's prediction, especially in the Z-axis control. This suggests that the Simulink-based model maintains its reliability even under moderate payload variations.
simulink_quadcopter_simulation.1745729884.txt.gz · Last modified: by yehyun