Starling: Containerisation Architecture for Scalable Local Development, Deployment and Testing of Multi-UAV Systems

Mickey H L Li*, Robert J Clarke, Arthur G Richards

*Corresponding author for this work

Research output: Contribution to conferenceConference Abstractpeer-review

Abstract

A major challenge of UAV research is facilitating the
local development, deployment and testing of multi-UAV systems.
Inspired by cloud computing, this work proposes Starling, a fullstack, compositional, containerised UAV infrastructure utilising
ROS2, Gazebo, PX4, Docker and Kubernetes. By modelling
individual UAVs as nodes in a compute cluster, our architecture
is natively scalable, fault tolerant and allows for the flexible
deployment of custom applications in both simulation and in
reality. These technologies allow us to facilitate reproducible
research while provide a lower barrier of entry for potential
users, as well as the reuse of flight hardware for multiple
projects. A multi-UAV path planning case study is presented to
demonstrate the streamlined workflow of developing a controller
from simulation to reality
Original languageEnglish
Number of pages5
Publication statusPublished - 1 Jul 2022
EventRobotic Science and Systems 2022 Workshop on Envisioning an Infrastructure for Multi-Robot and Collaborative Autonomy Testing and Evaluation - Virtual and In Person at Morningside Campus, Columbia University, New York, United States
Duration: 1 Jul 20221 Jul 2022
http://raaslab.org/rss2022/

Workshop

WorkshopRobotic Science and Systems 2022 Workshop on Envisioning an Infrastructure for Multi-Robot and Collaborative Autonomy Testing and Evaluation
Abbreviated titleEMIRCATE
Country/TerritoryUnited States
CityNew York
Period1/07/221/07/22
Internet address

Keywords

  • Robotics
  • Software engineering
  • Deployment tools

Fingerprint

Dive into the research topics of 'Starling: Containerisation Architecture for Scalable Local Development, Deployment and Testing of Multi-UAV Systems'. Together they form a unique fingerprint.

Cite this