Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
B
Baitboat
Manage
Activity
Members
Labels
Plan
Issues
0
Issue boards
Milestones
Wiki
Code
Merge requests
0
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
OpenSource
Baitboat
Commits
77958f8f
Commit
77958f8f
authored
10 years ago
by
Andrew Tridgell
Browse files
Options
Downloads
Patches
Plain Diff
Plane: fixed CONTINUE_AND_CHANGE_ALT command
current_loc should be used, not prev_WP_loc
parent
95d2e793
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
ArduPlane/commands_logic.pde
+2
-2
2 additions, 2 deletions
ArduPlane/commands_logic.pde
with
2 additions
and
2 deletions
ArduPlane/commands_logic.pde
+
2
−
2
View file @
77958f8f
...
...
@@ -514,8 +514,8 @@ static bool verify_continue_and_change_alt()
return
true
;
}
//Is the next_WP less than 200 m away?
if
(
get_distance
(
prev_WP
_loc
,
next_WP_loc
)
<
200.
f
)
{
//
Is the next_WP less than 200 m away?
if
(
get_distance
(
current
_loc
,
next_WP_loc
)
<
200.
f
)
{
//push another 300 m down the line
int32_t
next_wp_bearing_cd
=
get_bearing_cd
(
prev_WP_loc
,
next_WP_loc
);
location_update
(
next_WP_loc
,
next_wp_bearing_cd
*
0.01
f
,
300.
f
);
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment