Open smith0022 opened 4 months ago
Not quite sure but my guess is that both drones will take off 10 meters above the current home altitude as measured at the time. My guess is that GPS altitude can drift for the drones, and so the number shown later is off, as the estimate is corrected.
Or to put it differently, the drone takes off in local coordinates 10 meters above the home altitude but the global estimate drifts or changes slightly. The take off command is a local/relative command, but the altitude you're printing is "global". If you want to get to a "global" same altitude, you could use goto_location which will give you an absolute altitude to aim for.
i actually did try mavsdk with real drones and in simulation where both the drones were same . I tried off board and manual control and yet there was some reason a difference in altitude for mavsdk .I don't understand the reason for this but the drones in simulation and real life show the altitude error without any reason.
when I tried flying two drones at the same altitude using the same function (i.e takeoff) both the drones react in different way (error in altitude ) .Why does this error exist in the simulation ? apart from these when i tried to fly both the drones using the manual control when when both the drones received the same input both reacted differently.there is no significant difference in roll.yaw or pitch but the error in height is persistent even with manual control or offboard mode. here is the code for takeoff :