Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Sub: do not use rangefinder for control #10974

Closed
jaxxzer opened this issue Apr 2, 2019 · 1 comment · Fixed by #11493
Closed

Sub: do not use rangefinder for control #10974

jaxxzer opened this issue Apr 2, 2019 · 1 comment · Fixed by #11493
Assignees
@jaxxzer
Labels
Sub
Milestone
Sub-3.5.5

Comments

@jaxxzer
Copy link
Member

jaxxzer commented Apr 2, 2019

The rangefinder handling doesn't handle sonar glitches like locking on to reflections very well. We will remove the rangefinder as an input to the controllers until we can do a more robust implementation.
@jaxxzer jaxxzer added the Sub label Apr 2, 2019
@jaxxzer jaxxzer added this to the Sub 3.5.4 milestone Apr 2, 2019
@jaxxzer jaxxzer self-assigned this Apr 2, 2019
@jaxxzer
Copy link
Member Author

jaxxzer commented Apr 3, 2019

We will need to archive this after merge: https://github.com/bluerobotics/ardusub-gitbook/blob/master/operators-manual/altimeters.md

@jaxxzer jaxxzer modified the milestones: Sub 3.5.4, Sub-3.5.5 Apr 5, 2019
@Williangalvani Williangalvani mentioned this issue Jun 4, 2019
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jaxxzer jaxxzer

Labels
Sub
Projects
None yet
Milestone
Sub-3.5.5
Development

Successfully merging a pull request may close this issue.

Sub: Remove rangefinder support of control loops Williangalvani/ardupilot
1 participant
@jaxxzer