Hi all,
Iām attempting to simulate a set of three x500 drones carrying a slung load in Gazebo (see image below) with PX4 SITL.
The drones are able to take off successfully using offboard control messages from ROS2 (both position and velocity setpoints individually). However, after flying for a while (exact time differs on each simulation), I get the following warning and error:
INFO [commander] Armed by external command
INFO [tone_alarm] arming warning
INFO [commander] Takeoff detected
WARN [failsafe] Failsafe activated
INFO [tone_alarm] battery warning (fast)
ERROR [flight_mode_manager] Matching flight task was not able to run, Nav state: 2, Task: 1
INFO [commander] Landing detected
INFO [commander] Disarmed by landing
INFO [tone_alarm] notify neutral
The failsafe that kicks in results in the drones landing at their current positions.
I donāt really understand the root cause of this issue/what is causing the failsafe to trigger and therefore donāt know how to fix it. My current hypothesis (given that the error doesnāt appear when the tethers arenāt present) is that the additional tethered load (although negligible at 0.05 kg - perhaps it is more of the effect of other drones than the weight of the load) is making it difficult for the drones to reach the position/velocity setpoints and so a failsafe is triggered because āsomething appears wrongā to PX4. The position (and velocity) setpoints I have selected are physically feasible given the cable length constraints howeverā¦
Does this error mean anything more to someone else?
What Iāve tried:
- Removing the cables - the issue no longer appears (drones are able to hover indefinately from ROS2 offboard control commands).
- Setting SIM_BAT_DRAIN, SIM_BAT_MIN_PCT and BAT1_CAPACITY to max (given the error, thought that the simulated battery could be running out quickly) - this doesnāt change anything.
- Sending offboard position commands from ROS2 and offboard velocity commands from ROS2 - the error appears in both cases.
- Simulating the ācablesā as singular rigid links and as multiple (3 links each) rigid links (thought that perhaps rigid links were preventing drones from reaching the desired setpoints). The error appears in both cases.
I am on commit: a6d2c2cf5e21ecdad8d737c31de81fab128898c5.
Logfile of takeoff in velocity mode showing the error: https://logs.px4.io/plot_app?log=c9cb9702-a3bc-456e-a08e-16ce2b5c7b82.
Thanks in advance for your help!