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

GPS HGLRC M100 5883 is taking a long time to capture and fix satellites on inav 7.1 #9994

Open
Marvin1972 opened this issue Apr 30, 2024 · 10 comments

Comments

@Marvin1972
Copy link

I'm having problems using the HGLRC M100 5883 GPS. Using the inav 7.1 version, it's taking more than 20 minutes to capture satellites and fix 3d. The GPS is well isolated from interference and I shielded the cable with copper tape. Using the same GPS model in version 6.1 of INAV, it captures satellites normally and in a reduced time. Please check this bug.

Additional context

https://pastebin.com/evzbGcnq

version

INAV/MATEKF405SE 7.1.0 Mar 27 2024 / 13:52:59 (59a6ee6)

GCC-10.3.1 20210824 (release)

@sensei-hacker
Copy link
Collaborator

New GPS units take a minimum of 12.5 minutes outdoors to download the emperides and almanac.

12 1/2 minutes is the fastest possible, since that's the rate the satellites send them. Interference from a VTX or a telemetry receiver will make it take longer.

You will probably want to enable Galileo as well for best performance.

If you'd like, I can provide further tips if you want to attach a photo of how it's currently mounted and what is mounted near it.

@rx9abc
Copy link

rx9abc commented May 12, 2024

I have exactly the same problem.

INAV 7.1.1 / MATEKF722SE

@sensei-hacker
Copy link
Collaborator

@rx9abc if you'd like some assistance z please provide a copy of your diff and a photo of your GPS mounting. Also be sure to do all testing outdoors. Traditionally, GPS isn't supposed to work indoors - but the newest units are so good they sometimes pull it off even indoors.

@rx9abc
Copy link

rx9abc commented May 13, 2024

@sensei-hacker Yeah, I run all my tests outside. The GPS works like a charm with INAV 6, but as soon as I flash INAV 7, the GPS conks out. Once I reflash INAV 6, the GPS is up and running again.
MyCopter
INAV_7.1.1_cli_20240513_225602.txt

@sensei-hacker
Copy link
Collaborator

sensei-hacker commented May 13, 2024

@rx9abc Can you please post a screenshot of your GPS tab. I want to see the "messages".and "errors" numbers, as well as confirming the config (though I did read your diff).

FYI if you want to use the magnetometer now or in the future, the two of the worst things to have near the mag are a) the main battery wires and b) an active buzzer.

@rx9abc
Copy link

rx9abc commented May 13, 2024

@sensei-hacker
Stat

During flights with INAV6, I had no issues at all with picking up the GPS signal, even with the power cable hooked up. When I'm testing INAV7, I just skip the power battery altogether.
The tBeacon doesn't work in during flight. It only activates after crash.

MyCopter1

@sensei-hacker sensei-hacker pinned this issue May 13, 2024
@sensei-hacker
Copy link
Collaborator

Ah, you also have another mag separate from your GPS, a long with the 5883 built into the HGLRC. Cool. GPS near the power wires and buzzer should be okay.

Since the messages count is high and errors is low, that tells us that communication between the GPS and the FC is okay. The GPS itself just isn't getting a fix. That's odd, if it has had more than 12 minutes outdoors to download the almanac and ephemerides.

Since we're now in strange territory, have you tried turning off Galileo just to see what happens? It shouldn't be necessary, but this should be working exactly as you have it, from everything I can see.

Also I don't suppose you used U-Center to change any GPS settings? I ask because the settings set by INAV assume that other settings are at the default.

@rx9abc
Copy link

rx9abc commented May 13, 2024

Yeah, looks like it's time to get connected with the U-center. I'm not seeing any other way to troubleshoot this right now. I'll disable Galileo for the next test run.

@sensei-hacker
Copy link
Collaborator

sensei-hacker commented May 13, 2024

If you haven't already made any changes via U-Center, please hold off for now. Also I forgot to ask - which GPS unit do you have? You're in a thread titled "GPS HGLRC M100 5883", but I'm starting to suspect that's not what you have.

I'm starting to think maybe you have a Neo 6 or similar. If you're using a 15 year old GPS, that would explain the problem.

@breadoven breadoven unpinned this issue May 14, 2024
@rx9abc
Copy link

rx9abc commented May 14, 2024

Exactly, it`s my mistake, I didn't look at the topic title. I use GPS from RadioLink model TS 100. Is the reason for the failure in this GPS receiver?

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

No branches or pull requests

3 participants