dk7xe
3
For me it was because we needed something more powerful than a usual flight control.
I’m not developing myself but managing a team that is working on a project using ROS2 for drone Mission control.
I had a bachelor student who did a drone collision avoidance as ROS module based on just the MavLink UTM_GLOBAL_POSITION message.
Part of that was a Mission Plan file conversion in ROS (converting QGroundcontrol Plan file into Mission).
We also use automotive 77GHz radar on our drone that delivers pointcloud data into ROS2.
A Partner company is working on integration UWB into ROS2.
Our goal is to have a multirotor drone flying full autonomous mission based on ROS2 navigation by mid of next year.
One of the biggest challenges i see is to have a standard ruleset for collision avoidance. Because if two or more drones are on collision it needs to be predictable what the other airspace user will do next.
Cheers, Gerald
3 Likes