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

Add warning GPS Jamming #200

Open
MartinStokelj opened this issue Sep 2, 2020 · 4 comments
Open

Add warning GPS Jamming #200

MartinStokelj opened this issue Sep 2, 2020 · 4 comments

Comments

@MartinStokelj
Copy link

According to link

GPS Noise & Jamming
The GPS Noise & Jamming plot is useful to check for GPS signal interferences and jamming.
The jamming indicator should be around or below 40. Values around 80 or higher are too high and the setup must be inspected.

It would be nice that graph shows some kind of warning that values are to hight.

@dagar
Copy link
Member

dagar commented Oct 27, 2020

Can you reference the documentation for the relevant receiver?

@MartinStokelj
Copy link
Author

We are using uBlox NEO-M8N modul core of GNSS receiver made by our company.
On some drones we see this bellow 40 on some we have 250. For this with 250 we made shielding on cables and now we are around 150. This is high when we connect IP camera. Without ethernet connection cables the noise is low.

@dagar
Copy link
Member

dagar commented Oct 27, 2020

We are using uBlox NEO-M8N modul core of GNSS receiver made by our company.
On some drones we see this bellow 40 on some we have 250. For this with 250 we made shielding on cables and now we are around 150. This is high when we connect IP camera. Without ethernet connection cables the noise is low.

My interpretation was you can only interpret it as a relative metric. From the ublox 8 protocol specification.

Screenshot from 2020-10-27 17-14-47

@MartinStokelj
Copy link
Author

MartinStokelj commented Oct 28, 2020

thanks for this info.
I think it would be a good feature if graphs shows some kind of warning if values are to high, for example:

  • to high GPS noise
  • to high vibrations
  • ...
    So you can see sooner what is wrong with the platform when checking ulog file

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

2 participants