ardupilot icon indicating copy to clipboard operation
ardupilot copied to clipboard

Plane: Unexpected Large Target Bearing at WP1

Open isso11 opened this issue 1 year ago • 3 comments

Issue details

This could be a potential issue I've encountered multiple times while using the Software In The Loop (SITL) simulation. During my tests, I observed that upon reaching the first waypoint (WP1), the system consistently outputs a "Large" target bearing value. This occurs despite the fact that the whole mission path is a straight line, and there are no significant bearing errors observed throughout the route.

Course Control2

Version V "4.5.4" commit "e8f937aa"

Platform [ ] All [ ] AntennaTracker [ ] Copter [●] Plane [ ] Rover [ ] Submarine

Airframe type Fixed Wing

Hardware type Issue found in SITL (Built-In SITL and flightaxis SITL)

Logs Log

isso11 avatar Jun 25 '24 22:06 isso11

Indeed, in the log you provided, the target bearing "jumps" after reaching each waypoint. However, the actual navigation bearing seems to "jump" only at the first waypoint, bringing along a jump in the roll demand. image

I can't reproduce the issue on my system, though.

Can you provide the SITL command and the mission you use?

Georacer avatar Jun 26 '24 13:06 Georacer

Indeed, in the log you provided, the target bearing "jumps" after reaching each waypoint. However, the actual navigation bearing seems to "jump" only at the first waypoint, bringing along a jump in the roll demand. image

I can't reproduce the issue on my system, though.

Can you provide the SITL command and the mission you use?

In the Simulation tab command line: --home=49.3137086,30.1507759,226.95,22

Just a trivial mission, Takeoff and then Auto.

Here's the mission.

isso11 avatar Jun 26 '24 13:06 isso11

Your mission has a "misalignment" of ~1.5deg. And yes, with this mission it's reproducible in master: image

I also modified your mission to "misalign" the segments by ~5 degrees and it still happens, to a reduced degree: image

Here's the modified mission and the log. 21217.zip mission_modified.txt

Looks like a veritable bug to me.

Georacer avatar Jun 27 '24 10:06 Georacer