https://www.mathworks.com/help/uav/ug/uav-package-delivery.html
Hi!
I’m using the UAV Package Delivery example model (shortcut 8: photorealistic environment with high-fidelity plant model) and I want to simulate multiple UAVs in the same Simulink simulation (start with 2 UAVs).
My current assumption is that I need to duplicate some subsystems per UAV (plant, controller, sensors, etc.), but this model is large and complicated, so I’m not sure:
Which blocks/subsystems must be duplicated per UAV (plant + controller + estimator + guidance + sensors?)
Which blocks should be shared across all UAVs (scenario/world, environment, visualization, mission planner, etc.)
How the data flow should be organized so each UAV stays independent (namespaces, buses, variants, model references, data dictionaries, etc.)
How to correctly handle multiple instances of the Simulation 3D UAV Vehicle block / visualization, including transforms and coordinate frames, without conflicts
In addition, I eventually want each UAV to have its own mission plan coming from QGroundControl (QGC) (live mission feed). I found this related topic and plan to try it later, after I can run multiple UAVs first:
https://www.mathworks.com/matlabcentral/answers/1744715-how-to-get-multiple-mission-plan-from-q-ground-control-for-uav-package-delivery-example
Extra context:
I’m feeding a live predefined mission from QGC into the model.
I modified the Simulation 3D Scene Configuration block to use Cesium ion visualization instead of the default Unreal environment.
I’m currently working with the high-fidelity plant setup.
I’m using MATLAB R2025b
If possible, I’d appreciate guidance like “duplicate these subsystems, keep these shared,” and any best practices (Model Reference, For Each Subsystem, variant subsystems, buses, etc.).
Thanks a lot. I appreciate any help.https://www.mathworks.com/help/uav/ug/uav-package-delivery.html
Hi!
I’m using the UAV Package Delivery example model (shortcut 8: photorealistic environment with high-fidelity plant model) and I want to simulate multiple UAVs in the same Simulink simulation (start with 2 UAVs).
My current assumption is that I need to duplicate some subsystems per UAV (plant, controller, sensors, etc.), but this model is large and complicated, so I’m not sure:
Which blocks/subsystems must be duplicated per UAV (plant + controller + estimator + guidance + sensors?)
Which blocks should be shared across all UAVs (scenario/world, environment, visualization, mission planner, etc.)
How the data flow should be organized so each UAV stays independent (namespaces, buses, variants, model references, data dictionaries, etc.)
How to correctly handle multiple instances of the Simulation 3D UAV Vehicle block / visualization, including transforms and coordinate frames, without conflicts
In addition, I eventually want each UAV to have its own mission plan coming from QGroundControl (QGC) (live mission feed). I found this related topic and plan to try it later, after I can run multiple UAVs first:
https://www.mathworks.com/matlabcentral/answers/1744715-how-to-get-multiple-mission-plan-from-q-ground-control-for-uav-package-delivery-example
Extra context:
I’m feeding a live predefined mission from QGC into the model.
I modified the Simulation 3D Scene Configuration block to use Cesium ion visualization instead of the default Unreal environment.
I’m currently working with the high-fidelity plant setup.
I’m using MATLAB R2025b
If possible, I’d appreciate guidance like “duplicate these subsystems, keep these shared,” and any best practices (Model Reference, For Each Subsystem, variant subsystems, buses, etc.).
Thanks a lot. I appreciate any help. https://www.mathworks.com/help/uav/ug/uav-package-delivery.html
Hi!
I’m using the UAV Package Delivery example model (shortcut 8: photorealistic environment with high-fidelity plant model) and I want to simulate multiple UAVs in the same Simulink simulation (start with 2 UAVs).
My current assumption is that I need to duplicate some subsystems per UAV (plant, controller, sensors, etc.), but this model is large and complicated, so I’m not sure:
Which blocks/subsystems must be duplicated per UAV (plant + controller + estimator + guidance + sensors?)
Which blocks should be shared across all UAVs (scenario/world, environment, visualization, mission planner, etc.)
How the data flow should be organized so each UAV stays independent (namespaces, buses, variants, model references, data dictionaries, etc.)
How to correctly handle multiple instances of the Simulation 3D UAV Vehicle block / visualization, including transforms and coordinate frames, without conflicts
In addition, I eventually want each UAV to have its own mission plan coming from QGroundControl (QGC) (live mission feed). I found this related topic and plan to try it later, after I can run multiple UAVs first:
https://www.mathworks.com/matlabcentral/answers/1744715-how-to-get-multiple-mission-plan-from-q-ground-control-for-uav-package-delivery-example
Extra context:
I’m feeding a live predefined mission from QGC into the model.
I modified the Simulation 3D Scene Configuration block to use Cesium ion visualization instead of the default Unreal environment.
I’m currently working with the high-fidelity plant setup.
I’m using MATLAB R2025b
If possible, I’d appreciate guidance like “duplicate these subsystems, keep these shared,” and any best practices (Model Reference, For Each Subsystem, variant subsystems, buses, etc.).
Thanks a lot. I appreciate any help. uav, drone, simulink, simulation, visualization MATLAB Answers — New Questions

​