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

Follow failed: Home position not set #11966

Open
twistedwings opened this issue Oct 3, 2024 · 6 comments
Open

Follow failed: Home position not set #11966

twistedwings opened this issue Oct 3, 2024 · 6 comments
Assignees

Comments

@twistedwings
Copy link

If "Stream GCS Position" is enabled in Application settings, the message "Follow failed: Home position not set" pops up.

System Information

When posting bug reports, include the following information

  • Operating System: Windows 10
  • QGC Version:
    image
  • QGC build: daily
  • Flight Controller: SITL
  • Autopilot (with version): Ardupilot Copter 4.6.0

Detailed Description

Provide further details about your issue/bug.

Log Files and Screenshots

image

@HTRamsey
Copy link
Collaborator

HTRamsey commented Oct 6, 2024

This will probably happen until takeoff when you get your new home position. But actually I don't see why the vehicle position is needed for the gcs, seems kinda like a trick that assumes GCS and Vehicle are at same altitude initially and then the GCS is always at that altitude. I would think this is not a valid assumption to make and altMetersAMSL from the motion report should be used instead. @DonLakeFlyer thoughts on this? relevant code is here

@HTRamsey HTRamsey self-assigned this Oct 6, 2024
@twistedwings
Copy link
Author

twistedwings commented Oct 6, 2024

The code looks like it's related to follow mode.
In the stable version is an option Stream GCS Position-only in follow mode.
In the daily the option is on/off only.
So there shouldn't be any dependency to follow.

@twistedwings
Copy link
Author

twistedwings commented Oct 7, 2024

I remember a years lasting discussion about follow mode with the Ardupilot folks.
I think the code uses the home altitude of the vehicle instead of gps altitude.
Assuming gcs and vehicle are both at the same altitude, which is true in most cases.
The reason for this trick is that the altitude information is garbage on most smartphones.
So the code makes sense, only the error message is confusing and should be changed in "waiting for home" or the like.

@HTRamsey
Copy link
Collaborator

HTRamsey commented Oct 7, 2024

first thing to do is to restore the settings #11975

@DonLakeFlyer
Copy link
Contributor

I think the code uses the home altitude of the vehicle instead of gps altitude.
Assuming gcs and vehicle are both at the same altitude, which is true in most cases.
The reason for this trick is that the altitude information is garbage on most smartphones.

Correct.

The original pull is here: #8350.

@DonLakeFlyer DonLakeFlyer self-assigned this Oct 9, 2024
@DonLakeFlyer
Copy link
Contributor

So the code makes sense, only the error message is confusing and should be changed in "waiting for home" or the like.

I'll take a look...

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

No branches or pull requests

3 participants