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.

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

added sf45 as a seperate rangefinder #3448

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open

added sf45 as a seperate rangefinder #3448

wants to merge 3 commits into from

Conversation

Claudio-Chies
Copy link
Contributor

@Claudio-Chies Claudio-Chies commented Nov 11, 2024

  • Adapted and updated the documentation for the SF45 Rangefinder
  • Added it to sensors instead of a chapter in collision prevention, although thats the main usecase.
  • marked the Lanbao Sensor as EOL, as i cant find it available anymore, and some sellers marked it as EOL

Relevant PR's

From testing, 30 degrees is a good balance, although different vehicles may have different requirements.

::: info
The guidance feature will never direct the vehicle in a direction without sensor data.
If the vehicle feels 'stuck' with only a single distance sensor pointing forwards, this is probably because the guidance cannot safely adapt the direction due to lack of information.
If the vehicle feels stuck with only a single distance sensor pointing forwards, this is probably because the guidance cannot safely adapt the direction due to lack of information.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

FYI we only need to indicate something like "stuck" the first time, to highlight that we don't "exactly" mean stuck :-). I know this predates you, just wanted to explain why I did it.

@hamishwillee
Copy link
Collaborator

This is IMO ready when your PR is ready - thanks very much!!! I did some restructure to make the new rangefinder doc a sub-doc - that allows us to expand the structure if we want in future.

Note that the build error can be ignored. It happens because I moved one of the image files alongside the other, and the existing translations depend on that location. This will be fixed after merging by crowdin.

Copy link

No flaws found

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants