I have started uploading ADSB data lately. I see that I should be able to visit http://192.168.8.108:8080/
Unfortunately, the website is not responding. Which of the files should I edit? Or maybe what configuration should I share, so you could advise me something?
I’m a beginner, so I see that I have installed dump978 which wasn’t needed. I can see it here: http://192.168.8.108/skyaware978/ The map is empty, because I live in Europe. Is there a way of configuration so that dump1090 would be available in this position instead of dump978. I use raspberry pi with Flightradar image. The IP given above is static. If I forgot to write about something, please answer and I will send it.
Instead of going directly to port 8080, try http://192.168.8.108/dump1090-fa. Sometimes it doesn’t seem to make up the port 8080 link. I don’t know why, but I am sure that others here can explain.
I have noticed that the websites like: Flightradar, Planefinder offer their graphic interfaces. I thought that it would be possible to run GUI here as well. I would be grateful, if anyone told me how to make it happen.
If that’s not an option in the short term, the automatic install scripts on the above page for both readsb and dump1090-fa should work fine if the image isn’t super old.
Indeed, but FR24 programmers seem to be happy with it.
Their Pi24 image has dump1090-mutability (D EB_VER) pre-installed.
If user has Raspbian image, and performs a package install of fr24feed, the fr24feed on first run installs dump1090-mutability (D EB_VER), if the user is not careful to change default setting from receiver=dvbt to reciever=beast-tcp.
In both the above cases, the dump1090-mutability runs in a walled garden. During dump1090-mutability’s installation, the install script changes dump1090-mutability’s default configuration to start at boot from YES to NO. Now it is started, stopped, restarted by fr24feed, which starts it passing following argumets read from fr24feed’s configuration file /etc/fr24feed.ini:
Chemitox,
In your piaware-config.txt file, did you remove the # from the 978 UAT lines at the bottom?
I did that after mine was working with 1090, and it killed the 1090 sigs and only showed the 978 returns.
I’d suggest doing it to a diff SD card so as to preserve your info as it stands now, just to see if things will work with minimum config changes, then if it DOES work, you can change a line or two in the new config setup to have your feeder ID reflected in it that you currently have.
What hardware are you using?
My setup is a Rpi that was laying in my desk, a USB power supply, an RTL-SDR dongle laying in my desk, and an old trucker cellphone antenna that I modded the antenna connector to fit the SDR, and I changed the IP addy’s and the password and it’s running top shelf (also added the ssh file {from the advanced config page] so I could remotely access my system) straight off the web.
Once my feeder was live, I came on here and set up my acct and entered my location coords and things are working as they should (far as I can tell with over 3 million position reports in the last month)
I’d be curious what your piaware-config.txt file looks like (it’s in the BOOT folder)
I am a beginner. Running Flightradar, ADSBExchange, Planefinder, Radarbox, has taken a while, so I would not like to start from the scratch. Everything else work fine, and I would only like to get into flightaware GUI. I’m sending the configs below, about which other users are usually asked.
The SkyAware map is part of dump1090-fa. You will need to replace dump1090-mutability with dump1090-fa. You can continue to feed the other feeders with this, the data format it produces is the same.
dump1090-mutability is no longer maintained upstream (I know this because I was the maintainer). If you need help with the version that flightradar is apparently using, you’d need to contact them directly for support.
2- Make following changes:
Change receiver="dvbt" to receiver="beast-tcp"
Change path="/usr/lib/fr24/dump1090" to host="127.0.0.1:30005"
Change bs=“yes” to bs=“no”
Change raw=“yes” to raw=“no”
It all seems so easy, but are you sure that after the update all of the current services that I have (ADSBExchange, Radarbox, Flightradar, Planefinder, etc.) will still work?
If you don’t mess it up they will continue to work.
Well and if abcd567 hadn’t messed up with the instructions, leaving bs/raw enabled on fr24feed will create a TCP port conflict for port 30003 i believe.
Both of those will use port 30003 leading to a conflict.
Dec 04 11:29:53 pi readsb[17046]: Error opening the listening port 30003 (Basestation TCP output): bind: Address already in use
It’s still a conflict that should be avoided by disabling the fr24feed basestation output … as you don’t need it anyhow.
That conflict is a bit elusive as it requires fr24feed to start before dump1090-fa/readsb. (fr24feed doesn’t even give an error when it can’t use the port that’s why most of the time people get away with it as it usually starts after dump1090-fa but that doesn’t change the fact that it’s a misconfiguration)
The fr24feed raw output on 30334 is just useless when you have a properly programmed application providing you with data outputs. (fr24feed will crash if more than 2 clients or so connect to that port … or it did at some point)
When dump1090-mutability works ok with these settings, why dump1090-fa cant work and cause conflict? The default ports for both versions are identical.
I have posted the method after testing dump1090-fa with fr24feed having settings bs=yes and raw=yes and it works ok. Please see screenshots below.
Please read again that it will only be apparent when you start dump1090-fa after fr24feed and that usually doesn’t happen.
Port 30003 and 30334 (and maybe 30002 … not sure) aren’t provided by dump1090-mutability but rather by fr24feed itself.
Also i just tried and showed you the error that can occur if fr24feed is started before dump1090-fa.
So … as i already tried … no need to do it again rather i’d recommend that you try stopping both services, start fr24feed then start dump1090-fa.
