# Issue when creating plan in QGC 5.1.4 and Rover

**URL:** <https://discuss.px4.io/t/issue-when-creating-plan-in-qgc-5-1-4-and-rover/49564>\
**Category:** QGroundControl\
**Created:** [October 1, 2026, 8:10am UTC](https://discuss.px4.io/t/issue-when-creating-plan-in-qgc-5-1-4-and-rover/49564 "2026-10-01T08:10:06Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Karl\_S](https://discuss.px4.io/user_avatar/discuss.px4.io/karl_s/32/14567_2.png) [@Karl\_S](https://discuss.px4.io/u/Karl_S)\
**Post date:** [October 1, 2026, 8:10am UTC](https://discuss.px4.io/t/issue-when-creating-plan-in-qgc-5-1-4-and-rover/49564/1 "2026-10-01T08:10:07Z")

</div>

QGC 5.1.4

ArduRover 4.7.1

Been building and flying drones for many years. In recent years also started using Rover.

I have encountered an unusual issue linked to QGC:

I have a default altitude set in QGC. But recently when I have created a waypoint plan in QGC and vehicle set to “Rover”, I had a rather surprising result.- Rover appeared to go crazy, running in circles, not finding next waypoint and when finally on a waypoint, it was not recognized.

After downloading and analyzing a log, I did notice that all waypoints appear up in the air at the minimum altitude I have set in general settings.

Shouldn’t the “Rover” setting in Plan view pull all waypoints down to ground level?

Additional info: When just using a WP file it works as expected. Problem only occurs when using a .plan mission.

Thanks

---

<div class="post-metadata">

**Author:** ![yigitcan-ozturk](https://discuss.px4.io/user_avatar/discuss.px4.io/yigitcan-ozturk/32/22039_2.png) [@yigitcan-ozturk](https://discuss.px4.io/u/yigitcan-ozturk)\
**Post date:** [October 1, 2026, 12:27pm UTC](https://discuss.px4.io/t/issue-when-creating-plan-in-qgc-5-1-4-and-rover/49564/2 "2026-10-01T12:27:02Z")

</div>

The difference between the `.waypoints` and `.plan` cases is probably the most useful clue here.

Before looking at the Rover navigation behaviour itself, I would compare the mission items actually produced by QGC in the two cases.

In particular:

- altitude value for each waypoint
- MAVLink frame (`MAV_FRAME_*`)
- altitude mode / relative-altitude semantics
- whether the QGC default mission altitude is being serialized into the `.plan`
- the final `MISSION_ITEM_INT` values received by ArduRover

If the same ground waypoint is represented differently by `.plan` and `.waypoints`, that would help determine whether this originates in QGC mission generation or later in ArduRover mission interpretation.

Could you attach a minimal `.plan` that reproduces the problem and the equivalent working `.waypoints` file?

A 2–3 waypoint example should be enough. Comparing those side by side may expose the first difference immediately.

I would avoid changing the default altitude as a workaround until that comparison is done, because it could hide the serialization/interpretation issue rather than explain it.
