Skip to content

About

No description, website, or topics provided.

Resources

Stars

0 stars

Watchers

0 watching

Forks

Latest commit

 

History

1 Commit

Folders and files

Repository files navigation

pilotaro_easyfleet

An EasyFleet drone flown by the pilotaro autopilot. The drone offers three capabilities (flight, navigation, imaging), and a mission calls them to photograph the victims of a disaster scenario in Gazebo.

The example mission runs the pilotaro x500 in disaster_nathan_benderson_park_world (disaster_world): it takes off, flies over four victims, takes a picture of each one with the downward camera, comes back and lands.

Folder Package
pilotaro_easyfleet/ Capabilities, behavior trees, drone and mission BT nodes, launch files.
pilotaro_easyfleet_interfaces/ Flight and Imaging actions.
thirdparty.repos The other sources it needs: pilotaro, disaster_world and EasyFleet.
LICENSE Apache License 2.0.
colcon.meta Build options: turns off the tests of the EasyFleet packages, which do not configure in a new workspace.

Requirements

  • Ubuntu 24.04 with ROS 2 Jazzy (ros-jazzy-desktop) and Gazebo Harmonic, the Gazebo version paired with Jazzy (ros-jazzy-ros-gz).
  • Build tools: sudo apt install python3-vcstool python3-colcon-common-extensions python3-rosdep
  • An internet connection the first time: the world and the x500 download their models from Gazebo Fuel (they are cached in ~/.gz/fuel afterwards).

Setup

The commands below use ~/fleet_ws as the workspace; any folder works.

  1. Create the workspace and put this folder (pilotaro_easyfleet, with both packages and thirdparty.repos) in its src:

    mkdir -p ~/fleet_ws/src
    cp -r /path/to/pilotaro_easyfleet ~/fleet_ws/src/
    cd ~/fleet_ws
  2. Download pilotaro, the disaster worlds and EasyFleet:

    vcs import src < src/pilotaro_easyfleet/thirdparty.repos

    This creates src/pilotaro, src/disaster_world and src/ThirdParty/EasyFleet.

  3. Install the system dependencies. Only the packages that are used are listed: EasyFleet also contains EasyNav packages that this example does not need.

    source /opt/ros/jazzy/setup.bash
    sudo rosdep init   # only once per computer; skip it if it says it is already initialized
    rosdep update
    rosdep install -y --ignore-src --from-paths \
      src/pilotaro_easyfleet src/pilotaro src/disaster_world \
      src/ThirdParty/EasyFleet/easyfleet_core src/ThirdParty/EasyFleet/easyfleet_interfaces \
      src/ThirdParty/EasyFleet/easyfleet_bt_nodes src/ThirdParty/EasyFleet/easyfleet_tools
  4. Build. --packages-up-to builds pilotaro_easyfleet and everything it depends on, and skips the EasyNav packages. --metas applies colcon.meta, which builds the EasyFleet packages without their tests:

    colcon build --symlink-install --metas src/pilotaro_easyfleet/colcon.meta \
      --packages-up-to pilotaro_easyfleet

    It ends with Summary: 17 packages finished.

Run the mission

Use three terminals. In each one, start from the workspace root and source it:

cd ~/fleet_ws
source install/setup.bash

Terminal 1: simulation. Gazebo with the disaster world and the pilotaro x500 at (-120, 950), in its x500 namespace. headless:=true runs it without the Gazebo window, which is lighter.

ros2 launch pilotaro_gazebo disaster.launch.py

The first launch can take a few minutes while the models download. Wait until the drone is ready: ros2 topic echo /x500/mode --once prints data: DISARMED.

Terminal 2: drone capabilities. The flight, navigation and imaging actions under /x500. The pictures are saved in pilotaro_photos/ inside the folder you launch it from, here ~/fleet_ws/pilotaro_photos.

ros2 launch pilotaro_easyfleet drone_capabilities.launch.py

To save them somewhere else, add output_dir:=/absolute/path.

Terminal 3: mission.

ros2 launch pilotaro_easyfleet mission.launch.py

It takes about 6 minutes. Each step is printed as it ends, and the last line is:

[pilotaro_mission]: Mission finished: SUCCESS

The drone is back at the start point, DISARMED, and the pictures are in ~/fleet_ws/pilotaro_photos:

1_rescue_randy_2_8m_camera_down_<time>.png
2_rescue_randy_sitting_5_15m_camera_down_<time>.png
3_rescue_randy_25m_camera_down_<time>.png
4_rescue_randy_3_40m_camera_down_<time>.png

To run it again, keep terminals 1 and 2 running and launch the mission again.

Use the capabilities by hand

With terminals 1 and 2 running, each capability is an action that can be called directly:

ros2 action send_goal /x500/flight pilotaro_easyfleet_interfaces/action/Flight "{command: takeoff}"
ros2 action send_goal /x500/navigation easyfleet_interfaces/action/Navigation \
  "{parameters_json: '{\"goal_id\": \"rescue_randy\"}'}"
ros2 action send_goal /x500/imaging pilotaro_easyfleet_interfaces/action/Imaging \
  "{camera: camera_down, label: test}"
ros2 action send_goal /x500/navigation easyfleet_interfaces/action/Navigation \
  "{parameters_json: '{\"goal_id\": \"home\"}'}"
ros2 action send_goal /x500/flight pilotaro_easyfleet_interfaces/action/Flight "{command: land}"
  • Flight commands: takeoff, land, loiter, arm, disarm.
  • Waypoints: home, rescue_randy_2, rescue_randy_sitting_5, rescue_randy, rescue_randy_3.
  • Cameras: camera_down, camera_front.

ros2 easyfleet fleet lists the robots and their capabilities.

Customize

To change Edit
The steps of the mission pilotaro_easyfleet/behavior_trees/disaster_photo_mission.xml
Waypoints, cruise altitude, cameras pilotaro_easyfleet/config/x500/capabilities_params.yaml
How each capability works The trees in pilotaro_easyfleet/behavior_trees/

Waypoint z values are absolute heights in the odometry frame; at the start point the drone rests at z ≈ 4.7. Built with --symlink-install, edits to these files only need the launch restarted (terminal 2 for the capabilities, terminal 3 for the mission); otherwise run the colcon build command again first.

The architecture, the BT nodes and the configuration are described in the pilotaro_easyfleet package README.

Troubleshooting

Problem Cause and fix
rosdep wants to install ros-jazzy-easynav-* packages --from-paths includes all of src or of src/ThirdParty/EasyFleet. They are not needed: use the list of step 3.
easyfleet_core fails with Target "test_..." links to: GTest::gtest but the target was not found The build ran without --metas src/pilotaro_easyfleet/colcon.meta. Run the command of step 4.
colcon build fails in easyfleet_easynav_* or easyfleet_navigation_manager A plain colcon build builds the EasyNav packages too. Use --packages-up-to pilotaro_easyfleet.
vcs import fails with Permission denied (publickey) Your git configuration rewrites https://github.com/ to SSH (url.<...>.insteadOf). Add an SSH key to GitHub or remove that rewrite.
Gazebo stays loading the first time It is downloading the Fuel models; wait. Later launches use ~/.gz/fuel.
The mission fails at the first step The simulation was not ready yet. Wait for DISARMED on /x500/mode and launch the mission again.
CallImaging fails The camera name must be camera_down or camera_front, as in capabilities_params.yaml.
Warning [real_time] ... failed, running without it pilotaro could not get real-time priority. The simulation works anyway; see "Real time" in the pilotaro README to enable it.
The pictures are not in ~/fleet_ws/pilotaro_photos Terminal 2 was launched from another folder. Launch it from the workspace root or pass output_dir:=.

License

Apache License 2.0, Copyright 2026 Juan S. Cely G. and Intelligent Robotics Lab, Universidad Rey Juan Carlos. The repositories in thirdparty.repos keep their own licenses.

About

No description, website, or topics provided.

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages