Sorry, had to shoot back to work.
I’ll get this info back to you a little later.
Chas R.
Hi tomvdhorst, sorry cant cut paste from my piware rig.
Using blue Flightaware Dongle Pro stick plus v1.0 and full size flightaware antenna up above roof.
RasberryPi4.
Ive had the system working before, with Raspberry OS, used as a pc. its more usefull to me this way, but just now, its just piware 7.2
it looks like you are logging in as user root, to my knowlegde the default user for the piaware image is the user pi
Since it doesn’t recognise the user root it will close the session again and keeps repeating that.
My advice would be to start from scratch ( yes I know this is not funny) and load a fresh raspberry image using the raspberry pi imager:
Enable SSH access when you burn the image
You need the hidden control option described on this page to enable that.
After booting up you can start the package install from the flightaware page
When you arrive at step 6 you don’t need to claim the key again, you already have one that you can add to the site.
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
When finished you should be up running again
Thank you.
I’ll give this a try.
i would eventually like to keep a headed setup, to use as a pc when my main pc is tied up/busy, or do both by getting another Pi board?
you can choose to install the Raspberry Pi OS with the desktop option.
That will enable you to use it as a desktop at the same time.
When arriving at the step of reusing your feederkey, that key can be found when you login to flightaware and navigate to the stats page. your key is listed on the right side of the screen, it is called the “unique identifier”
I’m just trying to better understand this statement about my login.
And looking at the links you’ve supplied, ive already done those tasks several times over, but im just in the process of setting up my drive to flash a seperate 64gb sd micro card
Judging the hostname in your screenshot you have used the piaware image. The route I’m describing is to install the OS first and then install the piaware packages separately.
In setting up the pi imager you can choose your own hostname in the hidden options.
Just got to the desktop.
Have enabled SSH, although this is headed using LAN and ive only adjusted the password so far. Just about to download PiAware
UK based, dont need dump978, re-booting
…just gotta wait 30 mins, holding my breath?
you could try the command again
sudo service piaware status
When running normally your output would look like this example
piaware.service - FlightAware ADS-B uploader
Loaded: loaded (/lib/systemd/system/piaware.service; enabled; vendor preset: enabled)
Active: active (running) since Fri 2022-11-25 08:21:01 CET; 13h ago
Docs: PiAware - ADS-B and MLAT Receiver - FlightAware
Main PID: 656 (piaware)
Tasks: 4 (limit: 2059)
CPU: 21min 17.506s
CGroup: /system.slice/piaware.service
├─ 656 /usr/bin/piaware -p /run/piaware/piaware.pid -plainlog -statusfile /run/piaware/status.json
├─ 826 /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout --lat xx.xxx --lon x.xxx
└─5053 /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-transpor>
Nov 25 21:17:14 raspberrypitom4 piaware[656]: 189976 msgs recv’d from dump1090-fa (1398 in last 5m); 187411 msgs sent to FlightAware
Nov 25 21:22:14 raspberrypitom4 piaware[656]: 191435 msgs recv’d from dump1090-fa (1459 in last 5m); 188870 msgs sent to FlightAware
Nov 25 21:27:14 raspberrypitom4 piaware[656]: 192891 msgs recv’d from dump1090-fa (1456 in last 5m); 190326 msgs sent to FlightAware
Nov 25 21:32:03 raspberrypitom4 piaware[656]: mlat-client(5053): Receiver status: connected
Nov 25 21:32:03 raspberrypitom4 piaware[656]: mlat-client(5053): Server status: synchronized with 473 nearby receivers
Nov 25 21:32:03 raspberrypitom4 piaware[656]: mlat-client(5053): Receiver: 567.2 msg/s received 105.9 msg/s processed (19%)
Nov 25 21:32:03 raspberrypitom4 piaware[656]: mlat-client(5053): Server: 0.0 kB/s from server 0.0kB/s TCP to server 1.4kB/s UDP to server
Nov 25 21:32:03 raspberrypitom4 piaware[656]: mlat-client(5053): Results: 17.9 positions/minute
Nov 25 21:32:03 raspberrypitom4 piaware[656]: mlat-client(5053): Aircraft: 11 of 16 Mode S, 27 of 29 ADS-B used
Nov 25 21:32:14 raspberrypitom4 piaware[656]: 194104 msgs recv’d from dump1090-fa (1213 in last 5m); 191539 msgs sent to FlightAware
pi@raspberrypi:~ $ sudo service piaware status
● piaware.service - FlightAware ADS-B uploader
Loaded: loaded (/lib/systemd/system/piaware.service; enabled; vendor preset: enabled)
Active: active (running) since Fri 2022-11-25 20:16:43 GMT; 19min ago
Docs: PiAware - ADS-B and MLAT Receiver - FlightAware
Main PID: 581 (piaware)
Tasks: 2 (limit: 4915)
CPU: 6.772s
CGroup: /system.slice/piaware.service
└─581 /usr/bin/piaware -p /run/piaware/piaware.pid -plainlog -statusfile /run/piaware/status.json
Nov 25 20:35:10 raspberrypi sudo[2017]: pam_unix(sudo:session): session closed for user root
Nov 25 20:35:10 raspberrypi piaware[581]: dump1090 start appears to have been successful
Nov 25 20:35:20 raspberrypi sudo[2022]: piaware : PWD=/ ; USER=root ; COMMAND=/bin/netstat --program --tcp --wide --all --numeric
Nov 25 20:35:20 raspberrypi sudo[2022]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=999)
Nov 25 20:35:20 raspberrypi sudo[2022]: pam_unix(sudo:session): session closed for user root
Nov 25 20:35:20 raspberrypi piaware[581]: no ADS-B data program seen listening on port 30005 for 10 seconds, next check in 60s
Nov 25 20:35:24 raspberrypi sudo[2024]: piaware : PWD=/ ; USER=root ; COMMAND=/bin/netstat --program --tcp --wide --all --numeric
Nov 25 20:35:24 raspberrypi sudo[2024]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=999)
Nov 25 20:35:24 raspberrypi sudo[2024]: pam_unix(sudo:session): session closed for user root
Nov 25 20:35:24 raspberrypi piaware[581]: no ADS-B data program is serving on port 30005, not starting multilateration client yet
pi@raspberrypi:~ $
what is the printout for the following command
lsusb
it should read
pi@raspberrypitom4:~ $ lsusb
Bus 001 Device 004: ID 0bda:2832 Realtek Semiconductor Corp. RTL2832U DVB-T
Bus 001 Device 003: ID 0424:ec00 Microchip Technology, Inc. (formerly SMSC) SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Microchip Technology, Inc. (formerly SMSC) SMC9514 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
pi@raspberrypitom4:~ $ ^C
If you are missing the first option in your overview your dongle isn’t detected. If so we have to look from there
pi@raspberrypi:~ $ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 005: ID 04d9:0006 Holtek Semiconductor, Inc. Wired Keyboard (78/79 key) [RPI Wired Keyboard 5]
Bus 001 Device 004: ID 05e3:0610 Genesys Logic, Inc. Hub
Bus 001 Device 003: ID 145f:01c8 Trust Trust Wireless Mouse
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
your dongle isn’t detected by the Pi.
can you connect it to another USB port on the Pi itself ?
is it hot swappable ?
I’ll power down and try
yes it is hot swappable.
