Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | Next revision Both sides next revision | ||
|
searchwing-px4-analyse [2018/10/28 23:39] natwati [Results] |
searchwing-px4-analyse [2018/10/28 23:40] natwati [Results] |
||
|---|---|---|---|
| Line 42: | Line 42: | ||
| The PX4 firmware does not support altering an ongoing mission. This requires a full clear of the mission. Afterwards the mission needs to be uploaded using multiple mavlink messages and roundtrip times (see [[https://mavlink.io/en/protocol/mission.html|Mission Protocol]]).\\ | The PX4 firmware does not support altering an ongoing mission. This requires a full clear of the mission. Afterwards the mission needs to be uploaded using multiple mavlink messages and roundtrip times (see [[https://mavlink.io/en/protocol/mission.html|Mission Protocol]]).\\ | ||
| - | If all commands of a mission have been executed and the plane is in mission mode it will loiter. Missions can be paused in hold mode which also loiters. | + | If all commands of a mission have been executed and the plane is in mission mode it will loiter. Missions can be paused in hold mode which causes the plane to loiter. |
| The PX4 firmware implements the possibility to upload a second mission in the background while another mission is active. QGroundControl does not support this and forces the user to pause the mission when uploading a new mission. | The PX4 firmware implements the possibility to upload a second mission in the background while another mission is active. QGroundControl does not support this and forces the user to pause the mission when uploading a new mission. | ||