Repository navigation
U-turn: say the turn is missed when AutoSteer starts too close to the headland to plan one - #836
Merged
Merged
Conversation
… headland to plan one Field job T10 (2026-11-14 nightly): AutoSteer switched off ten seconds into a U-turn and on again three seconds later. The turn is dropped and planned again from scratch, but the tractor was back on its line in the cultivated area only 6 m before the headland, closer than a turn is planned (10 m). No turn was planned and nothing was said: it drove on through the headland and 25 m out of the field. AgOpenGPS can't turn there either and sounds "too close". In the cultivated area on the line, heading for the headland, with no turn planned or under way and closer to it than a turn is planned, the missed turn now sounds once with "U-turn missed: too close to the headland to turn. Take over manually." Not after an end of field or a refused turn; on a curve the pass is walked ahead first, as for creation. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ld further on The Runner run of the first commit: on Baetas (field jobs W1 and J3) the first pass cuts across a corner of the cultivated area, meets the headland line a few metres on and comes back into the field further on. The new warning took that for the end of the pass and the operator was told to take over at the start of the job; the turn is planned at the real end. The warning now walks the pass past the crossing (CultivatedAhead) and is said only at its last one; the same walk covers the curve whose straight ray meets the headland early on the outside of a bend (J10). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Field job T10, 2026-11-14 nightly (
RAN-OFF, Safety).What happened
GpsPipelineServiceclears it). But the tractor was back on its line in the cultivated area only 6 m before the headland, closer than a turn is planned (MinDistanceToCreate, 10 m).Change (
YouTurnStateMachine.Tick, "too close to plan")Tests
Too_close_to_the_headland_to_plan_a_turn_the_operator_is_told_once: fails without the change.A_turn_planned_in_time_says_nothing_near_the_headland.CultivatedAhead) and is said only at its last one; unit testA_pass_crossing_a_corner_of_the_field_is_not_a_missed_turn.🤖 Generated with Claude Code