You have yet more decoders installed …
pgrep -fa dump
Let’s see which.
Probably misconfigured fr24feed or rbfeeder.
770 /usr/local/share/adsbfi/venv/bin/python3 /usr/local/share/adsbfi/venv/bin/mlat-client --input-type dump1090 --no-udp --input-connect 127.0.0.1:30005 --server feed.adsb.fi:31090 --user obiwan --lat 40.779112 --lon -73.968844 --alt 31m --results beast,connect,127.0.0.1:30104 --results basestation,listen,31009 --results beast,listen,30157 --results beast,connect,127.0.0.1:30169
2529 /usr/lib/piaware/helpers/fa-mlat-client --input-connect localhost:30005 --input-type dump1090 --results beast,connect,localhost:30104 --results beast,listen,30105 --results ext_basestation,listen,30106 --udp-transport 206.253.80.196:10785:2550329137
6424 /usr/bin/dump1090-fa --quiet --device-type rtlsdr --device-index 1090 --gain 60 --adaptive-range --fix --lat 39.08472 --lon -77.14979 --max-range 360 --net-ro-port 30002 --net-sbs-port 30003 --net-bi-port 30004,30104 --net-bo-port 30005 --json-location-accuracy 1 --write-json /run/dump1090-fa
Well now it’s running, is the webinterface showing aircraft?
I guess i didn’t post the correct command for the log and you didn’t scroll to the end.
I think it does - I clicked on the link in the FlightAware page
https://www.flightaware.com/adsb/stats/user
And the link “View Live Data”
Which proved to be incorrect for some reason picking up the old IP address from the prior install on Buster-32 (I allocated them different local IP addresses on my network)
I will leave it overnight to make sure I don’t get an alert as I did yesterday
Then if all is working I will finish the piHole install and then clone the SDCard back to the original so I have a backup
Thanks to everyone for weighing in and providing guidance. I wish I understood more to be abel to trouble shoot this myself but grateful for the help from everyone
Easiest way is map it out on paper.
Usb → decoder (pick one) → everything else.
1 usb. 1 decoder using usb. (This is where claim 6 comes from)
Everything else not using usb but network data/ports.
Which is why wiedehopf has so many fixits. Everyone tries to automate their own stuff without looking for pre-existing stuff. And try stack them ontop.
2 Likes
Thanks helpful but I need a little more if you can @oblivian
What would be a ‘decoder’
I am guessing the following are decoders?
dump1090-fa
dump978-fa
readsb ??
AND I need PiAware and all its components installed to receive the data
Sadly while I thought the unit was producing data (it did apparently for some short period as I got a “Your PiAware Receiver Site XXXXXX is now sending data to FlightAware.” yesterday in the morning by the following day whatever mess I had created was not generating data.
So I blew it all up, reimaged and I am starting afresh
I am starting here (Build a new Piaware Receiver)
or maybe this
I think I got into trouble by following @abcd567 guidance up above:
After writing image, inserting microSD card in Pi, and powering up Pi, do following:
OPTION-1:
You can manually run following command one by one in the same order given below…
The piece I need help with is transferring my station ID?
From my earlier posts, I discovered mine which was in /etc/piaware.conf
Do I take the station ID from my old Buster-32 setup and manually edit that into this file on Bookworm-64 setup?
Thanks
The key can be located on your stats page while logged in.
in order to use your old feeder key:
sudo piaware-config feeder-id xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
# Replace xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
# by your actual feeder-id
sudo systemctl restart piaware
Looking at your stats it is already running? or is the old system still active?
Something of deja vu as I tried again to get things up and running
When I ran Status I do get this on the new Config
PiAware master process (piaware) is running with pid 3574.
PiAware ADS-B client (faup1090) is running with pid 3588.
PiAware ADS-B UAT client (faup978) is not running (disabled by configuration settings)
PiAware mlat client (fa-mlat-client) is not running.
Local ADS-B receiver (dump1090-fa) is running with pid 3433.
dump1090-fa (pid 3433) is listening for ES connections on port 30005.
faup1090 is connected to the ADS-B receiver.
piaware is connected to FlightAware.
dump1090 is producing data on localhost:30005.
Your feeder ID is XXXXXX
But my stats page looks like it has plummeted and as such not receiving data. I will leave it running overnight and see if I get a system generated note to say I am not generating data
Some additional thoughts on what might be causing problems here.
Since the Raspberry Pi’s are both on my network at the same time is that possibly why I am having problems? I leave the old one up and running as it runs PiHole DNS for the network. The Pihole on the new setup is not enabled so there are not any probelms/conflicts for the DNS.
However, since this has been challenging I am leaving the setup in place for FlightAware on the Buster32 running and just unplugging the USB Arial and plugging it into Boookworm64.
I just cannot work this out - My new Bookworm64 was a clean install and plugged in the trial but there is no data
sudo journalctl -u piaware -n 15 |tee
Oct 30 09:31:46 pi2 sudo[2268]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=995)
Oct 30 09:31:46 pi2 sudo[2268]: pam_unix(sudo:session): session closed for user root
Oct 30 09:31:46 pi2 piaware[1478]: logged in to FlightAware as user nickvt
Oct 30 09:31:46 pi2 piaware[1478]: my feeder ID is <>>
Oct 30 09:31:46 pi2 piaware[1478]: site statistics URL: nickvt ADS-B Feeder Statistics - FlightAware
Oct 30 09:31:47 pi2 sudo[2309]: piaware : PWD=/ ; USER=root ; COMMAND=/bin/netstat --program --tcp --wide --all --numeric
Oct 30 09:31:47 pi2 sudo[2309]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=995)
Oct 30 09:31:47 pi2 sudo[2309]: pam_unix(sudo:session): session closed for user root
Oct 30 09:31:47 pi2 piaware[1478]: ADS-B data program ‘dump1090-fa’ is listening on port 30005, so far so good
Oct 30 09:31:47 pi2 piaware[1478]: Starting faup1090: /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout
Oct 30 09:31:47 pi2 piaware[1478]: Started faup1090 (pid 2311) to connect to dump1090-fa
Oct 30 09:32:07 pi2 piaware[1478]: 637 msgs recv’d from dump1090-fa (380 in last 1m); 637 msgs sent to FlightAware
Oct 30 09:37:07 pi2 piaware[1478]: 4882 msgs recv’d from dump1090-fa (4245 in last 5m); 4882 msgs sent to FlightAware
Oct 30 09:42:07 pi2 piaware[1478]: 9051 msgs recv’d from dump1090-fa (4169 in last 5m); 9051 msgs sent to FlightAware
Oct 30 09:47:07 pi2 piaware[1478]: 13485 msgs recv’d from dump1090-fa (4434 in last 5m); 13485 msgs sent to FlightAware
sudo journalctl -u dump1090-fa -n 10 |tee
Oct 30 09:31:38 pi2 dump1090-fa[2137]: Found Rafael Micro R820T tuner
Oct 30 09:31:38 pi2 dump1090-fa[2137]: rtlsdr: tuner gain set to about 58.6 dB (gain step 29) (tuner AGC enabled)
Oct 30 09:31:38 pi2 dump1090-fa[2137]: adaptive: using 50% duty cycle
Oct 30 09:31:38 pi2 dump1090-fa[2137]: adaptive: enabled adaptive gain control with gain limits 0.0dB (step 0) … 58.6dB (step 29)
Oct 30 09:31:38 pi2 dump1090-fa[2137]: adaptive: enabled dynamic range control, target dynamic range 30.0dB
Oct 30 09:31:38 pi2 dump1090-fa[2137]: Allocating 4 zero-copy buffers
Oct 30 09:31:48 pi2 dump1090-fa[2137]: adaptive: available dynamic range (24.5dB) < required dynamic range (30.0dB), switching to downward scan
Oct 30 09:31:48 pi2 dump1090-fa[2137]: adaptive: changing gain from 58.6dB (step 29) to 49.6dB (step 28) because: probing dynamic range gain lower bound
Oct 30 09:31:48 pi2 dump1090-fa[2137]: rtlsdr: tuner gain set to 49.6 dB (gain step 28)
Oct 30 09:31:58 pi2 dump1090-fa[2137]: adaptive: available dynamic range (34.1dB) >= required dynamic range (30.0dB), stopping downwards scan here
piaware-status
PiAware master process (piaware) is running with pid 1478.
PiAware ADS-B client (faup1090) is running with pid 2311.
PiAware ADS-B UAT client (faup978) is not running (disabled by configuration settings)
PiAware mlat client (fa-mlat-client) is not running.
Local ADS-B receiver (dump1090-fa) is running with pid 2137.
dump1090-fa (pid 2137) is listening for ES connections on port 30005.
faup1090 is connected to the ADS-B receiver.
piaware is connected to FlightAware.
dump1090 is producing data on localhost:30005.
Your feeder ID is <>> (from /var/cache/piaware/feeder_id)
You have 3 Sites.
You are currently feeding site 235581 as you have used feeder-id for this site.
Please choose the site which you want to use & retain, and use feeder-id of this site in your RPi. Please see “How-to” linked below
For Beginners - How to Get Back Existing Station Number in A Fresh Install
2 Likes
Outstanding - thanks for catching this. I (obviously) completely missed this 
Now I have this working correctly I found this useful thread/instruction on how ot remove old/unusued sites
[For Beginners - How-to Remove Unused Site from Your Account](https://Thread to remove old unused sites)
Now I need to do some clean up and then clone this back to the old Buster Setup
Many thanks
2 Likes