Hi!
Maybe somebody could help with my problem…
I got a receiver which gets a lot of planes over 500km (MLAT). But in the statistics the peak range stays always at 500km (498.2 km to be exact)… Never rising. This image is in miles as I tried if it will change when going to the imperial setting… But it stays the same.
I searched and tried everything… no chance 
Any idea?
https://s29.postimg.org/eab5vmaon/dump1090_localhost_range_imperial_statute_30d.pnggratis bilder
Thanks!
@GeorgLichtblau
Exactly same happens with my 3 receivers.
It appears that the rrd/collectd graphs do not use MLAT data fedback by Flightaware. These tools use only the data received by the antenna. Consequently due to lack of position coordinates in data received by antenna from the mlat planes, their distance cannot be established by dump1090/rrdtools/collected. Hence these planes do not contribute to maximum range.
Above is my inference from my observation. Joe Prochazka and Oliver (obj) are the right persons to give an answer.
I thought the same… But these flights are all MLAT-only. I would never get this range at this receiver without mlat. Normal ADSB-Range is at 350-380km. But these peaks at 500km are in the statistics. But not more than 500km. I can see them them in the live view up to 600km or more. Strange.
In VRS it snips it at 600km… Must be coded inside VRS.
Just waited for a plane over 500km…
Definitively I got messages. This plane was at this position (checked at FA) and was MLAT-only all the time…
https://s30.postimg.org/j7bi5xjkx/atwork_517km.jpgbilder kostenlos
Statistics stopped as always at 500km… So MLAT-Range is recorded, but somewhere there have to be a max. Range… But I don’t know where. That’s my problem.
https://s27.postimg.org/fvd5vcwlf/dump1090_localhost_range_imperial_statute_6h.pngkostenlos bilder hochladen
My VRS plot also shows that ADSB range (dark grey) is greater than MLAT Range (Light grey).
Seems VRS snips far away MLAT planes
Ever since I have been running these scripts I have had permission issues with files.
I use WinSCP to go into the file area on the Pi. I want to change the gain and I dont have permission to modify and save the file.
What am I missing?
Depends what user you installed them under. You may need to use CHOWN to correct. What does
ls -l
show?
I always get reports from further away by ADS-B than I do by MLAT and my maximum distance in the Performance Graphs page is never reported above 500km either.
Is it only me?
I am not able to open the ADS-B Receiver Project Webseite.
Also my ADS-B Receiver Project Portal SQLITE Logging stopped working today (14) in the morning. But i have nothing changed, wasn’t even at home!
Not just you. Website seems to be down.
Well…
I came home today and sat down to get this info and the system had basically crashed at around 1pm. It looked like it was idling. I tried restarting it a few times then shut it down, unplugged and re plugged. Tried to update the software. Nothing, so I created a new image and started from scratch. I still have the old card in case it has anything useful.
It had been running flawlessly until I fooled around last night trying to run the script to check the gain.
This is what it has now but that is different from before:
pi@raspberrypi:~ $ ls -l
total 4
drwxr-xr-x 5 pi pi 4096 Dec 14 21:15 adsb-receiver
I’m using WinSCP to try to modify the dump1090-fa file to change the gain but I get denied trying to save it.
I never have been able to get it to change the password even though it says it does.
easy way may be to reinstall the software with
sudo ./install.sh
I found instructions by abcd to modify the gain using sudo commands, so I have that accomplished.
The python file to test gain settings that I ran two nights ago would not run last night with the new image. I had to Ctrl-C out of it. By that time I was tired of fooling with it so I did a reboot and just let it run.
Lots of great info in this thread though.
It is but I am able to get in with a link to one of the pages, just not the main page.
Cool looks like the thread is fixed!
Anyways I will try to catch up on what I have missed pertaining to questions asked within this thread since my last post here. These are some of the newer ones anyone who is still having an issue I may have over looked can feel free to point their problem out again.
@keithma
If you are still having issues with lighttpd not starting let me know. Might be the file got corrupted or edited improperly at some time. If anything try purging the lighttpd package and reinstall it. Use the purge switch to remove all traces including the configuration files. After setting up lighttpd reinstall dump1090 and the portal so the proper configuration changes are put in place.
sudo apt-get purge lighttpd
sudo apt-get install lighttpd
dump1090-mutability uses a switch --max-range which sets the max range used by the device. More than likely you are hitting the ceiling of this setting. The setting is located in the file /etc/init.d/dump1090-mutability and looks like this in the file: MAX_RANGE=300.
Firstly you are more than likely unable to overwrite this file sue to the permissions set on this file. More than likely the file is owned by another user. Try to SSH into the device and edit the file there using the sudo command.
sudo nano /path/to/the/dump1090-fa/file/in/question
Just so you know permissions are set on the dump1090-fa files automatically by the dump1090-fa package not the scripts. I am sure you would encounter the same problem on the FlightAware PiAware image as well.
As for changing the password make sure you use the following command without sudo while logged in as the user pi.
passwd
The website adsbreceiver.net is back up and running once again. What ended up happening was the debit card used to purchase the adsbreceiver.net domain name was replaced by a new card containing the “chip” feature. The auto renewal for the domain did not go through due to the fact the new card has a new expiration date and security code assigned to it. Sadly I used an email address to register the domain name which I do not check as often as I should.
hi guys,
I have build back my setup using the script.
Planefinder and flightradar24 feeding with no issues.
I manage to claim my piaware device, but** it does not show anymore online and fed**.
What can I do about it?
[2016-12-21 18:59 SGT] Started faup1090 (pid 844) to connect to dump1090-mutabi
[2016-12-21 19:29 SGT] ADS-B data program 'dump1090-mutabi' is listening on port 30005, so far so good
[2016-12-21 19:29 SGT] Starting faup1090: /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout
[2016-12-21 19:29 SGT] Started faup1090 (pid 862) to connect to dump1090-mutabi
~/adsb-receiver $ **sudo piaware-status
**PiAware master process (piaware) is not running.
PiAware ADS-B client (faup1090) is not running.
PiAware mlat client (fa-mlat-client) is not running.
Local ADS-B receiver (dump1090-mutabi) is running with pid 463.
dump1090-mutabi (pid 463) is listening for connections on port 30005.
**faup1090 is NOT connected to the ADS-B receiver.
piaware is NOT connected to FlightAware.**
dump1090 is producing data on localhost:30005.
It will not show on your account until it is logged out and locks back into Flightaware’s system. This is something they fail to tell people. Issue a shutdown command or shutdown via the graphical interface and after the shutdown is complete wait a few minutes. Then turn the device back on and it will log back into Flightaware’s system and it should show on your account either immediately or within 30 minutes.
[quote=“mcrieman”]
It will not show on your account until it is logged out and locks back into Flightaware’s system. This is something they fail to tell people. Issue a shutdown command or shutdown via the graphical interface and after the shutdown is complete wait a few minutes. Then turn the device back on and it will log back into Flightaware’s system and it should show on your account either immediately or within 30 minutes.
Did it, issue remains 
Did it, issue remains
Did you wait 30 minutes before doing. Do it again, shut off the PI for several minutes and turn it on again. Eventually a properly claimed receiver should show on your account. Most of mine too around an hour to appear. The last one I had to do the power cycle trick and then it worked. A reboot doesn’t seem to be long enough. Shut if off, remove power, wait and then turn it back on.