hi my location and range rings are off by about 200 kms to the north east. i have triple checked my adsb config file and it is the same as i used a few days ago, this is is happening for the last few days. i have cleared chrome cache. is it intentional or just something gone wrong?. how can i fix it? i am an occasional feeder for now and have intentions on feeding 24/7 as soon as i get my second dedicated .rpi ciao lied
try /tar1090/?reset Otherwise ... re-check the configuration. To edit the adsbx image configuration use this command: Code: sudo nano /boot/adsb-config.txt Make the changes you want to make. Then save: Ctrl-O and Enter and exit: Ctrl-X To apply the changes, reboot: Code: sudo reboot
If you use the adsbx image then i gave you instructions above. Otherwise .... you need to describe EXACTLY what you installed.
only the exact image 1.0.6. the program for writing win32 disk manger split my sd in two. retried another card but now both yellow and green lan led are on without blinking. if i change sd card to another image for another feed it works. now it says i am in south america......
Which URL do you have in your browser when you see the wrong location? Can you post it please? The global page and the adsbexchange page for your receiver both use the browsers location detection logic. So if you do VPN or something like that ... it'll be wrong. You can permanently set the location for the adsbexchange globe page / receiver page: https://www.adsbexchange.com/map-help/ https://globe.adsbexchange.com/?SiteLat=XX.XXX&SiteLon=-XX.XXX
the right one is the last, the others are with firefox, edge and chrome. my position is incorrect the aircraft are always correct. it did not happen a few days ago. hope it ìs fixed now. i have no vpn but lied is now in region 2c. should not be there....... ciao lied
https://globe.adsbexchange.com/?fee...P3NNfjCORF+7m2eeIM5Dg9nrL4zk&t=16084863797624 and https://globe.adsbexchange.com/?SiteLat=39.457495&SiteLon=8.735165 the one with the correct position.
Once you use the globe.adsbexchange.com/?SiteLat=XX.XXX&SiteLon=-XX.XXX your browser will remember that location and you don't need to use it anymore. That goes for your feed as well.
yes what about mlats now? i am in region 2c instead of 3b . no synced stations. is a fix possible? ciao lied
That can only be fixed by changing the image configuration. I explained how to change that before. Is your name unique? Maybe you just think you're in the wrong region. You can private message me your configuration if you want. I'll take a look what you're doing wrong.
+1: I made a mistake by entering a minus sign in front of my longitude (scripted setup for existing dump-1090) and ended up with a mirrored feeder on the other side of the Greenwich meridian. As I couldn't find an editable configuration file in the adsb-exchange folder to correct my mistake, I decided to run setup.sh again but this time with the correct data. All this has partionally solved my problem but the mirrored feeder is still present and I'm feeding data and mlat to 4 instead of 2 servers according to www.adsbexchange.com/myip/ Data incoming from: *.*.*.* Route: beast.front Backend: beast.back Connected: beast-ingress.06 Age: 4h59m Data incoming from: *.*.*.* Route: beast.front Backend: beast.back Connected: beast-ingress.05 Age: 4h59m Data incoming from: *.*.*.* Route: mlat.front Backend: mlat_back_4b Connected: mlat4b Age: 4h59m Data incoming from: *.*.*.* Route: mlat.front Backend: mlat_back_3a2 Connected: mlat3a2 Age: 4h10m Any suggestions how to rectify this?
That is likely another RPi or something along those lines. Maybe you had an old adsbexchange folder in your home directory and ran that old setup.sh? Try and installing like instructed here: https://github.com/adsbxchange/adsb-exchange#obtaining-and-using-the-scripts If you have an old install in parallel it should remove it. If you have adsbexchange stuff in your home folder you can remove that, it's no longer the method of choice and outdated.
Your assumption about the old install folder was correct, I removed it, ran axfeed.sh again followed by systemctl restart for both processes and the mirror feeder vanished into thin air
