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

pixhawk is not allowing GPS to be fixed #14787

Open
mhk4zemi opened this issue Apr 29, 2020 · 9 comments
Open

pixhawk is not allowing GPS to be fixed #14787

mhk4zemi opened this issue Apr 29, 2020 · 9 comments
Labels

Comments

@mhk4zemi
Copy link

Hi guys

Recently I have an issue with my flight controller. I can see on the Qgroundcontrol that GPS recognizes many satellites for instance 10 or more, although Pixhawk seems cannot sense it so it is not reading the position of the drone. The value of the HDOP and VDOP of the GPS signal is low. I have also uploaded a picture of the noise and jamming level of the GPS.

This is happening once we have a power tether attached to the drone close to GPS, I am not sure if I can reduce the noise.

image
image
image

I also increase the minimum acceptable values in the EK2_REQ_* section but it did not help at all.

Any comments would be much appreciated. :)

@julianoes julianoes added question Sensors All the sensors! labels Apr 29, 2020
@julianoes
Copy link
Contributor

Could you share the link to the log?

@ryanjAA
Copy link
Contributor

ryanjAA commented May 1, 2020

What’s contained in the power tether? Just power or are communications on the same bundle of wires? Also, what is the power type? Ac or dc? And if ac is there and ac converter onboard the plane and if dc is it high voltage with an onboard step down, etc. we have a bit of experience with high voltage power tethers and switching frequency and quite a few things can cause havoc. Definitely a log but more detailed info on your setup would be helpful from a diagnostics perspective.

@mhk4zemi
Copy link
Author

mhk4zemi commented May 1, 2020

@ryanjAA . Tether line is just carrying DC power and we have dc converter onboard as well. If you can tell me what part is interesting I can take it out from the log file and share it here.

@ryanjAA
Copy link
Contributor

ryanjAA commented May 1, 2020

It’s a little more involved than that. Generally if you’re seeking help you should share as much detail as possible and definitely at a minimum the entire log if you’d like someone to look at it as there is often things you might not see as important that someone else might spot the problem.

You have an atypical setup which yields more to understanding what you have onboard and what you’re doing to try and help. The log is the best first step. I’d detail what I have onboard as well given you could possibly be sending up 400-600v dc and then bringing it down back to 25 or 50v for onboard motor use which means understanding your hardware and power is a huge area of concern given you’re saying the gps issues arise when connecting the power tether.

How are creating the voltage up and down? Are they isolated? Etc etc, there are a lot of questions but rather than questions it’s easier to get help if you just provide whatever information you can about your setup and that aside which often is r necessary, a log is. I’d turn logging on from boot and turn it all on then plug in the tether and share that log too (any log that has both cases).

We used vicor units to bring 500v dc back down to something useable and I can tell you, there is a lot to consider and shield when doing this...

@mhk4zemi
Copy link
Author

mhk4zemi commented May 1, 2020

@ryanjAA @julianoes

Here is the complete logfile. In this one, pixhawk locked the GPS but in the middle of the hovering phase. You can see it in the log data as well. The tether voltage is 400 and we have converters on board to take it down to 36. We did not use any special shielding for the autopilot or the GPS antenna.

https://review.px4.io/plot_app?log=5eb72abd-8794-4f31-b985-b695c1da4b16

@julianoes
Copy link
Contributor

From the log it looks indeed like the GPS accuracy is not very "good", and not "good enough". The estimated accuracy is around 4 meters when I would expect values around 1-2 meters max.

@mhk4zemi
Copy link
Author

mhk4zemi commented May 4, 2020

From the log it looks indeed like the GPS accuracy is not very "good", and not "good enough". The estimated accuracy is around 4 meters when I would expect values around 1-2 meters max.

I don't think it would be the problem because for this setup I changed the following parameters. So PIXHAWK should be able to read the position from GPS. Unless there would be some other parameters that I am missing.

EKF2_REQ_EPH, 10.0
EKF2_REQ_EPV, 15.0
EKF2_REQ_GDOP, 3.5
EKF2_REQ_HDRIFT, 1.0
EKF2_REQ_NSATS, 6
EKF2_REQ_SACC, 1.5
EKF2_REQ_VDRIFT, 0.6000000238418579

@ryanjAA
Copy link
Contributor

ryanjAA commented May 4, 2020

The main easy and topical things you can do are going to be:

Move the physical GPS unit

Try a different unit (something with an Active antenna might help or add a larger ground plane just to increase the amount of sats)

Shield the unit and if possible measure surrounding EMF.

It looks like you are also using a custom version of PX4 so not sure what else you may have changed but unlikely that is hurting raw GPS reception. What's the highest amount of sats and lowest HDOP/VDOP you've been able to attain in your area? With and without your tether?

If your sat amount is high and hdop/vdop low until you plug in the tether then you know the issue. If you have a low baseline in terms of gps accuracy already (when the tether is not plugged in) then it is getting swamped from the tether itself and likely the fast voltage switching, if that's not the case then i'd look at the physical unit or its placement as well (of the GPS and wiring). Did you make or buy the DC-DC converters?

Also, are you using any onboard video? Specifically in the 1.3ghz range? That effects GPS a lot as well if the transmitter is too close and/or not good quality.

Also, you're having a lot of log drop outs, try changing the SD card (or format it if its already a high quality one).

@stale
Copy link

stale bot commented Aug 2, 2020

This issue has been automatically marked as stale because it has not had recent activity. Thank you for your contributions.

@stale stale bot added the stale label Aug 2, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants