I flashed a new image to my SD card per instructions. Edited the .config file with my WiFi info but the Pi does not appear in my router listing. Connected a monitor to the Pi but the user interface is not what I had previously. I do not know Linux. What do I do now? Thank you in advance for any help…
What is the new image?
What was the old image?
What changes did you make to the new image, specifically?
What’s shown on the monitor after you start it up?
1 Like
The new image is 3.8.1. The old image was 3.8.0 I believe and was installed on the pi when I bought it. It had noobs as well.
I edited the config file per the instructions on the FlightAware flash and install instructions. I edited config with my WiFi SSID and password. Originally I had the pi using static IP. I changed config file to DHCP to try to get pi to be seen on my WiFi.
That wasn’t a 3.8.0 image, then (we’ve never built an image that uses NOOBS). Not sure what you had there originally.
“wlan0 down” means that wireless is configured but it’s not associating with your AP.
Doublecheck your SSID & password.
You were correct … I had the SSID incorrect.
What do I have to do to associate my unique identifiers with my station again?
On the command line, enter
piaware-config feeder-id <your feeder id>
and then restart piaware
sudo systemctl restart piaware
1 Like
Thank you ! How do I do the same for Flightradar24 ?
In the previous build when I had a monitor hooked to the Pi there was a user friendly interface that was displayed. Can I get that back again ??
I am not familiar with FlightRadar24’s method. Perhaps others can help or you can ask on their forums.
What did the user interface look like? The screenshot that you posted is what you’d expect of FlightAware’s PiAware SD card image when hooked up to a monitor. You may have had some other image installed.
I don’t have an image of what I had before. However. I think this now explains what happened to me when I first powered up the original Pi. I believe that there was malware along with the SW that was preinstalled on the Pi. Because When I powered up the Pi shortly thereafter two computers that I used to communicate with the Pi crashed and would not boot. I cannot explain what all happened but I believe that the SW that was preloaded had malware imbedded.
Raspbian Lite: ADS B receiver · wiedehopf/adsb-wiki Wiki · GitHub
This shows how to install FR24 without auto-updater and the other nonsense they do.
The FR24 install part you can do on the piaware image just as well.
Besides installing a decoder everything on that page should work.
I have no idea what I’m doing so I ask your indulgence… I ran your code the first time with both the newer and older lines. Then I thought that maybe I was supposed to comment out the older line and leave only the newer. So I reran your code again. The following is what happened… I’m not sure if there is a problem or if things worked as expected?
pi@piaware:/tmp $ sudo apt update
sudo rm /usr/bin/fr24feed
sudo cp fr24/usr/bin/fr24feed* /usr/bin
sudo wget -O /etc/systemd/system/fr24feed.service https://raw.githubusercontent.com/wiedehopf/adsb-scripts/ master/fr24feed.service
sudo systemctl enable fr24feed
sudo fr24feed --signup
Hit:1 http://flightaware.com/mirror/raspbian/raspbian buster InRelease
Hit:2 http://flightaware.com/adsb/piaware/files/packages buster InRelease
Hit:3 http://flightaware.com/mirror/raspberrypi/debian buster InRelease
Reading package lists… Done
Building dependency tree
Reading state information… Done
75 packages can be upgraded. Run ‘apt list --upgradable’ to see them.
pi@piaware:/tmp $ sudo apt install -y perl wget
Reading package lists… Done
Building dependency tree
Reading state information… Done
perl is already the newest version (5.28.1-6).
wget is already the newest version (1.20.1-1.1).
0 upgraded, 0 newly installed, 0 to remove and 75 not upgraded.
pi@piaware:/tmp $ sudo apt remove -y fr24feed
Reading package lists… Done
Building dependency tree
Reading state information… Done
E: Unable to locate package fr24feed
pi@piaware:/tmp $ sudo rm /tmp/fr24 -rf
pi@piaware:/tmp $ mkdir /tmp/fr24
pi@piaware:/tmp $ cd /tmp
pi@piaware:/tmp $
pi@piaware:/tmp $ # current version:
pi@piaware:/tmp $ wget -O fr24.deb https://repo-feed.flightradar24.com/rpi_binaries/fr24feed_1.0.26-5_armhf .deb
–2020-09-29 01:11:50-- https://repo-feed.flightradar24.com/rpi_binaries/fr24feed_1.0.26-5_armhf.deb
Resolving repo-feed.flightradar24.com (repo-feed.flightradar24.com)… 2606:4700::6811:2b34, 2606:4700::681 1:2c34, 2606:4700::6811:2a34, …
Connecting to repo-feed.flightradar24.com (repo-feed.flightradar24.com)|2606:4700::6811:2b34|:443… connec ted.
HTTP request sent, awaiting response… 503 Service Temporarily Unavailable
2020-09-29 01:11:51 ERROR 503: Service Temporarily Unavailable.
pi@piaware:/tmp $ # or slightly older version if you have issues with the current one:
pi@piaware:/tmp $ # wget -O fr24.deb https://repo-feed.flightradar24.com/rpi_binaries/fr24feed_1.0.25-3_arm hf.deb
pi@piaware:/tmp $
pi@piaware:/tmp $ dpkg -x fr24.deb fr24
dpkg-deb: error: ‘fr24.deb’ is not a Debian format archive
pi@piaware:/tmp $ sudo rm /usr/bin/fr24feed
rm: cannot remove ‘/usr/bin/fr24feed’: No such file or directory
pi@piaware:/tmp $ sudo cp fr24/usr/bin/fr24feed* /usr/bin
cp: cannot stat ‘fr24/usr/bin/fr24feed*’: No such file or directory
pi@piaware:/tmp $ sudo wget -O /etc/systemd/system/fr24feed.service https://raw.githubusercontent.com/wiede hopf/adsb-scripts/master/fr24feed.service
–2020-09-29 01:11:51-- https://raw.githubusercontent.com/wiedehopf/adsb-scripts/master/fr24feed.service
Resolving raw.githubusercontent.com (raw.githubusercontent.com)… 151.101.0.133, 151.101.64.133, 151.101.1 28.133, …
Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|151.101.0.133|:443… connected.
HTTP request sent, awaiting response… 200 OK
Length: 651 [text/plain]
Saving to: ‘/etc/systemd/system/fr24feed.service’
/etc/systemd/system/fr24fe 100%[=======================================>] 651 --.-KB/s in 0s
2020-09-29 01:11:51 (3.84 MB/s) - ‘/etc/systemd/system/fr24feed.service’ saved [651/651]
pi@piaware:/tmp $ sudo systemctl enable fr24feed
pi@piaware:/tmp $
pi@piaware:/tmp $ sudo fr24feed --signup
sudo: fr24feed: command not found
pi@piaware:/tmp $ sudo systemctl restart fr24feed
Job for fr24feed.service failed because the control process exited with error code.
See “systemctl status fr24feed.service” and “journalctl -xe” for details.
pi@piaware:/tmp $ pi@piaware:/tmp $ sudo apt update
sudo fr24feed --signup
Hit:1 http://flightaware.com/mirror/raspbian/raspbian buster InRelease
Hit:2 http://flightaware.com/adsb/piaware/files/packages buster InRelease
Hit:3 http://flightaware.com/mirror/raspberrypi/debian buster InRelease
Reading package lists… Done
Building dependency tree
Reading state information… Done
75 packages can be upgraded. Run ‘apt list --upgradable’ to see them.
pi@piaware:/tmp $ sudo apt install -y perl wget
Reading package lists… Done
Building dependency tree
Reading state information… Done
perl is already the newest version (5.28.1-6).
-bash: pi@piaware:/tmp: No such file or directory
wget is already the newest version (1.20.1-1.1).
0 upgraded, 0 newly installed, 0 to remove and 75 not upgraded.
pi@piaware:/tmp $ sudo apt remove -y fr24feed
Reading package lists… Done
Building dependency tree
Reading state information… Done
pi@piaware:/tmp $ sudo rm /usr/bin/fr24feed
pi@piaware:/tmp $
pi@piaware:/tmp $ # current version:
pi@piaware:/tmp $ wget -O fr24.deb https://repo-feed.flightradar24.com/rpi_binaries/fr24feed_1.0.26-5_armhf .deb
–2020-09-29 01:11:50-- https://repo-feed.flightradar24.com/rpi_binaries/fr24feed_1.0.26-5_armhf.deb
Resolving repo-feed.flightradar24.com (repo-feed.flightradar24.com)… 2606:4700::6811:2b34, 2606:4700::681 1:2c34, 2606:4700::6811:2a34, …
Connecting to repo-feed.flightradar24.com (repo-feed.flightradar24.com)|2606:4700::6811:2b34|:443… connec ted.
HTTP request sent, awaiting response… 503 Service Temporarily Unavailable
2020-09-29 01:11:51 ERROR 503: Service Temporarily Unavailable.
pi@piaware:/tmp $ # or slightly older version if you have issues with the current one:
pi@piaware:/tmp $ # wget -O fr24.deb https://repo-feed.flightradar24.com/rpi_binaries/fr24feed_1.0.25-3_arm hf.deb
pi@piaware:/tmp $
pi@piaware:/tmp $ dpkg -x fr24.deb fr24
dpkg-deb: error: ‘fr24.deb’ is not a Debian format archive
pi@piaware:/tmp $ sudo rm /usr/bin/fr24feed
rm: cannot remove ‘/usr/bin/fr24feed’: No such file or directory
pi@piaware:/tmp $ sudo cp fr24/usr/bin/fr24feed* /usr/bin
cp: cannot stat ‘fr24/usr/bin/fr24feed*’: No such file or directory
pi@piaware:/tmp $ sudo wget -O /etc/systemd/system/fr24feed.service https://raw.githubusercontent.com/wiede hopf/adsb-scripts/master/fr24feed.service
–2020-09-29 01:11:51-- https://raw.githubusercontent.com/wiedehopf/adsb-scripts/master/fr24feed.service
Resolving raw.githubusercontent.com (raw.githubusercontent.com)… 151.101.0.133, 151.101.64.133, 151.101.1 28.133, …
Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|151.101.0.133|:443… connected.
HTTP request sent, awaiting response… 200 OK
Length: 651 [text/plain]
Saving to: ‘/etc/systemd/system/fr24feed.service’
/etc/systemd/system/fr24fe 100%[=======================================>] 651 --.-KB/s in 0s
2020-09-29 01:11:51 (3.84 MB/s) - ‘/etc/systemd/system/fr24feed.service’ saved [651/651]
Run it line by line, read the errors.
HTTP request sent, awaiting response… 503 Service Temporarily Unavailable
FR24’s website isn’t available at the moment, they are either compromised or have an issue with a DDOS attack.
When I step thru line by line I get to here and then this…
Saving settings to /etc/fr24feed.ini…OK
Settings saved, please run “sudo systemctl restart fr24feed” to use new configuration.
pi@piaware:/tmp $ sudo systemctl restart fr24feed
Job for fr24feed.service failed because the control process exited with error code.
See “systemctl status fr24feed.service” and “journalctl -xe” for details.
Well then you misconfigured it.
beast tcp network 127.0.0.1 30005 is what you want.
Yes… I have used those as input and it still does not work. When I execute this command journalctl -xe which is one of the commands it says to look at for errors I get the following…
A start job for unit fr24feed.service has begun execution.
– The job identifier is 655239.
Sep 29 16:42:37 piaware systemd[17808]: fr24feed.service: Failed to determine user credentials: No such process
Sep 29 16:42:37 piaware systemd[17808]: fr24feed.service: Failed at step USER spawning /bin/rm: No such process
– Subject: Process /bin/rm could not be executed
– Defined-By: systemd
– Support: Debian -- User Support
– The process /bin/rm could not be executed and failed.
No need to break your head in debugging. Easier is to do a fresh install again as follows. I have used this method lot of times without any problem.
STEP 1 of 2 - PIAWARE
Re-image microSD card with latest piaware 3.8.1 sd card image. You will have dump1090-fa, dump978-fa, and piaware data feeder pre-installed
Direct download:
http://piaware.flightcdn.com/piaware-sd-card-3.8.1.img.zip
To Configure, follow instructions here:
Howto : Piaware SD card image 3.8.0 Quickstart Guide
STEP 2 of 2 - FR24 FEEDER
Run following bash command to install FR24 feeder
sudo bash -c "$(wget -O - https://repo-feed.flightradar24.com/install_fr24_rpi.sh)"
Above script after installing FR24 feeder starts configuration by asking email or receiver type. At this point dont enter anything, instead, break the process by pressing Ctrl+C.
Now open file fr24feed.ini
sudo nano /etc/fr24feed.ini
Delete all its contents and copy-paste contents from below (replace xxxxxxxxxx by your actual fr24 key)
receiver="beast-tcp"
host="127.0.0.1:30005"
fr24key="xxxxxxxxxxxxxxxx"
logmode="1"
bs=no
raw=no
mlat="yes"
mlat-without-gps="yes"
Save file (Ctrl+O), then close (Ctrl+x)
Now restart fr24feed
sudo systemctl restart fr24feed
Wait for few minutes, then check status
fr24feed-status
3 Likes
When attempting to do Step 2 with all of the parameters correct as indicated above I get…
pi@piaware:~ $ sudo nano /etc/fr24feed.ini
pi@piaware:~ $ sudo systemctl restart fr24feed
Job for fr24feed.service failed because the control process exited with error code.
See “systemctl status fr24feed.service” and “journalctl -xe” for details.
pi@piaware:~ $
Wgat are outputs if first a d fhurd cimmabds?
fr24feed-status
sudo killall fr24feed
sudo fr24feed
I’m not sure what your question is however after running the three commands it now seems like the FR24 feed is running ! FR24 now shows on line and appears to be feeding data. However I get an red error message that pops up stating no recent data for this radar. I assume that might go away after it feeds for a while? If that is correct assumption can you explain what was happening and what was done to correct the situation please ?
Now I am getting the following… it appears that the feed stopped
2020-10-02 10:49:17 | [mlat][i]Pinging the server
2020-10-02 10:49:17 | [mlat][i]Stats 9674/295
2020-10-02 10:49:37 | [mlat][i]Pinging the server
2020-10-02 10:49:37 | [mlat][i]Stats 10024/350
2020-10-02 10:49:43 | error | [stats] Timeout was reached
2020-10-02 10:49:57 | [mlat][i]Pinging the server
2020-10-02 10:49:57 | [mlat][i]Stats 10364/340
2020-10-02 10:50:01 | [feed][i]Feed disconnected
2020-10-02 10:50:01 | [feed][e]Could not connect feed!
2020-10-02 10:50:01 | [feed][n]Error: Could not connect feed! (result -1, fd -1)
2020-10-02 10:50:01 | info | [feed][n]waiting 17 seconds
2020-10-02 10:50:17 | [mlat][i]Pinging the server
2020-10-02 10:50:17 | [mlat][i]Stats 10740/376
2020-10-02 10:50:18 | [feed][n]KIAG4@185.218.24.22:8099/UDP
2020-10-02 10:50:18 | [feed][n]connecting
2020-10-02 10:50:18 | info | Network thread connecting to 185.218.24.22:8099 for feed KIAG4
2020-10-02 10:50:28 | error | [stats] Timeout was reached
2020-10-02 10:50:37 | [mlat][i]Pinging the server
2020-10-02 10:50:37 | [mlat][i]Stats 11127/387
2020-10-02 10:50:57 | [mlat][i]Pinging the server
2020-10-02 10:50:57 | [mlat][i]Stats 11395/268