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

Webinterface Help #159

Open
fishbum opened this issue Nov 29, 2021 · 13 comments
Open

Webinterface Help #159

fishbum opened this issue Nov 29, 2021 · 13 comments

Comments

@fishbum
Copy link

fishbum commented Nov 29, 2021

I apologize in advance for what is most assuredly a basic issue. I’m having troubles with the webinterface. It appears I’m tracking Aircraft, the table on the bottom right has AC data, but they aren’t showing up on the map. I’ve looked for some documentation on this but haven’t found anything. I’ll attach a screenshot of what I’m currently seeing.
FBF1DA2A-8A4B-486C-A4FA-FDA1064329A4

Appreciate any help you could provide.

@wiedehopf
Copy link
Owner

location in decoder set wrong.

@wiedehopf
Copy link
Owner

or reception is just really bad, to get a position you might need better reception.

@rcarsey1
Copy link

rcarsey1 commented Nov 29, 2021

This is peculiar. the aircraft list, of course inherently has the ICAO hex, but also shows the callsigns and altitudes.. but no squawk codes (and I presume no GPS coordinates). Even if the decoder's GPS position was not set, these entries should at least display the squawk codes. I can't imagine the receiver "missing" everyone's squawk and position frames. speed too?

The Persistence button is pressed.. so I'm thinking the aircraft list on the right is stale anyway.

@fishbum
Copy link
Author

fishbum commented Nov 29, 2021

or reception is just really bad, to get a position you might need better reception.

I’ll try to move the antenna to a better position. Thanks for the reply!

@wiedehopf
Copy link
Owner

Improve the whip antenna:
First place it on a can, the shape and size isn't too terribly important, a large metal surface will work as well:
https://media.discordapp.net/attachments/676004018463571989/741376804303929564/581ec3250ace8ce45f961f2a0b3f6e5b7d7bb5dc_2_460x500.png?width=401&height=436
Cut it to length or unscrew the whip and bend some wire around the threads so that the length of the whip is as described here:
https://media.discordapp.net/attachments/676004018463571989/741376818547916891/8d675f88b554d309a628ac92b32d859a34db0513_2_394x500.png?width=343&height=436

You might also want to run

sudo systemctl stop readsb
sudo rtl_test

check which tuner you have ..... might be a wrong tuner if it's a no-name SDR.

General setup advice: https://github.com/wiedehopf/adsb-wiki/wiki/Raspbian-Lite:-ADS-B-receiver
Some hardware choices: https://github.com/wiedehopf/adsb-wiki/wiki/adsb-receiver-shopping-list

@wiedehopf
Copy link
Owner

wiedehopf commented Nov 30, 2021

FC0012/13 are the tuner types that work really poorly, one of the RTL820 types is the tuner type you want.

@fishbum
Copy link
Author

fishbum commented Nov 30, 2021

Improve the whip antenna: First place it on a can, the shape and size isn't too terribly important, a large metal surface will work as well: https://media.discordapp.net/attachments/676004018463571989/741376804303929564/581ec3250ace8ce45f961f2a0b3f6e5b7d7bb5dc_2_460x500.png?width=401&height=436 Cut it to length or unscrew the whip and bend some wire around the threads so that the length of the whip is as described here: https://media.discordapp.net/attachments/676004018463571989/741376818547916891/8d675f88b554d309a628ac92b32d859a34db0513_2_394x500.png?width=343&height=436

You might also want to run

sudo systemctl stop readsb
sudo rtl_test

check which tuner you have ..... might be a wrong tuner if it's a no-name SDR.

General setup advice: https://github.com/wiedehopf/adsb-wiki/wiki/Raspbian-Lite:-ADS-B-receiver Some hardware choices: https://github.com/wiedehopf/adsb-wiki/wiki/adsb-receiver-shopping-list

Thank you so much for the help!

@duan78
Copy link

duan78 commented Apr 15, 2024

Hi, I've exactly the same problem; what do you mean by "location in decoder is set wrong" ? How can I check this ? I would like to investigate since it's not a quatlity reception problem ...
image

@wiedehopf
Copy link
Owner

This is not a webinterface issue, you gotta know which underlying decoder you're running without that info ... no chance to even point you somewhere.

@wiedehopf
Copy link
Owner

wiedehopf commented Apr 15, 2024

That looks like a container thing ('stats available here' is a custom modificiation to that webinterface) ... well the location is set wrong.
What is so complicated about me saying the receiver location is set wrong?
I guess receiver location is clearer than decoder location.

Wrong latitude / longitude set!

@duan78
Copy link

duan78 commented Apr 15, 2024

You are right i'm using "ultrafeeder" from this tuto : https://sdr-enthusiasts.gitbook.io/ads-b ; thx for your reply, I'll try to find this out or install your tool a proper way.

@wiedehopf
Copy link
Owner

wiedehopf commented Apr 15, 2024

Press H on the tar1090 interface and it'll show you which location you've set.
That might help you correct the error.

@duan78
Copy link

duan78 commented Apr 15, 2024

Press H on the tar1090 interface and it'll show you which location you've set. That might help you correct the error.

Lol, thank you ! ^^
image

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

4 participants