No, that all looks like it is connected.
If anything, maybe the autodetection logic from modesmixer2 is hanging because it’s not getting data for so long.
But if you soon have a plane nearby you’ll see if it’s on the modesmixer map.
I haven’t worked with modesmixer and actually suggested a different approach as you can see in my first post in this thread.
Yes, this could be the reason. Is there a way to specify a data format - In this case AVR with the --inconnect configuration ModeSMixer2?
I also noticed that there’s been zero aircraft ‘seen’ in the last 24hrs since setting up ModeSMixer2 with FlightAware, so there’s defiantly something wrong.
I don’t think so.
As i said, use my suggestion, it has no autodetection and uses dump1090-fa to turn AVR into beast.
Tested that locally by feeding some AVR into a dump1090-fa, sure produces output on beast.
Feed data to PiAware in AVR Format from External ADS-B Receiver - #5 by wiedehopf
Could also be that your microADSB is just not receiving anything.
Hi wiedhopf,
I created a new PiAware install and ran through your setup. Could you please confirm that the target=127.0.0.1:29001 and piaware-config receiver port 29005 is correct? As the FA receiver can’t connect.
Should be.
Let’s check if it’s running
pgrep -a dump1090-fa
sudo journalctl --no-pager -u combine1090-dump
journalctl --no-pager -u combine1090-dump
– Logs begin at Thu 2016-11-03 17:16:42 UTC, end at Fri 2019-07-19 14:48:33 UTC. –
Jul 19 14:21:57 piaware systemd[1]: Started combine1090-dump - combine1090 dump1090-fa instance.
Jul 19 14:21:57 piaware combine1090-dump[1317]: Fri Jul 19 14:21:57 2019 UTC dump1090-fa 3.7.1 starting up.
Jul 19 14:21:57 piaware combine1090-dump[1317]: Net-only mode, no SDR device or file open.
Looks likeQF9 is right over the top of you.
I had a friend on Cocos last year who fed flightaware for me. I believe he left the gear there but it has not been switched on since he left.
There is a Pi3 and and a Prostick Plus on the island not doing anything if you would like to use that until you can debug the external receiver.
S.
You also need to specify localhost
piaware-config receiver-host localhost
piaware-config receiver-port 29005
also
piaware-config receiver-type other
Can you show what piaware is saying?
pi@piaware:~ $ sudo piaware-status
PiAware master process (piaware) is running with pid 492.
PiAware ADS-B client (faup1090) is not running.
PiAware ADS-B UAT client (faup978) is not running.
PiAware mlat client (fa-mlat-client) is not running.
dump1090-fa (pid 502) is listening for connections on port 29005.
no program appears to be listening for connections on port 30978.
faup1090 is NOT connected to the ADS-B receiver.
faup978 is NOT connected to the ADS-B UAT receiver.
piaware is connected to FlightAware.
got ‘couldn’t open socket: connection refused’
pi@piaware:~ $ sudo piaware-config
allow-auto-updates yes # value set at /boot/piaware-config.txt:67
allow-manual-updates yes # value set at /boot/piaware-config.txt:71
allow-mlat yes # value set at /boot/piaware-config.txt:75
allow-modeac yes # value set at /boot/piaware-config.txt:79
image-type piaware # value set at /usr/share/piaware-support/piaware-image-config.txt:5
manage-config yes # value set at /usr/share/piaware-support/piaware-image-config.txt:4
receiver-host localhost # value set at /boot/piaware-config.txt:84
receiver-port 29005 # value set at /boot/piaware-config.txt:85
receiver-type other # value set at /boot/piaware-config.txt:86
rtlsdr-gain max # value set at /boot/piaware-config.txt:60
wired-network yes # value set at /boot/piaware-config.txt:27
wireless-network yes # value set at /boot/piaware-config.txt:33
wireless-password # value set at /boot/piaware-config.txt:49
wireless-ssid MyWifiNetwork # value set at /boot/piaware-config.txt:48
sudo nano /etc/default/combine1090
#Append all IP addresses running dump1090/piaware in the next line, 127.0.0.1 is just an example you should replace it
SOURCES= 192.168.1.7
#which ports to collect beast data from (for piaware/dump1090-fa this is 30005 for ADS-B and 30105 for MLAT)
PORTS= 30005
#for the IP addresses in SOURCES all PORTS are used, if you want to only forward a single or non-standard port use the following:
#uncomment and add IP addresses with ports for redirection
#CUSTOM=127.0.0.1:29005 127.0.0.1:29999
#where the data shall go, for display under /combine1090 leave it as is.
TARGET=127.0.0.1:29001
#options for dump1090-fa where all the data goes
RECEIVER_OPTIONS=“–net-only”
DECODER_OPTIONS=“–max-range 360”
NET_OPTIONS=“–net --net-heartbeat 60 --net-ro-size 1000 --net-ro-interval 0.2 --net-ri-port 29001 --net-ro-port 29002 --net-sbs-port 29003 --net-bi-port 29004 --net-bo-port 29005”
JSON_OPTIONS=“–json-location-accuracy 1”
That all looks good, maybe you just need to restart piaware?
sudo systemctl restart piaware
Then check the log:
journalctl --no-pager -u piaware
Hi wiedenhopf,
The restarting of the PiAware worked and the receiver is now connected.
Unfortunately QF9 is now out of range so I’ll need to wait for another aircraft to see if any data is outputted.
pi@piaware:~ $ sudo piaware-status
PiAware master process (piaware) is running with pid 1293.
PiAware ADS-B client (faup1090) is running with pid 1309.
PiAware ADS-B UAT client (faup978) is not running.
PiAware mlat client (fa-mlat-client) is running with pid 1330.
dump1090-fa (pid 502) is listening for connections on port 29005.
no program appears to be listening for connections on port 30978.
faup1090 is connected to the ADS-B receiver.
faup978 is NOT connected to the ADS-B UAT receiver.
piaware is connected to FlightAware.
got ‘couldn’t open socket: connection refused’
1 Like
You can install the graphs if you want a local record if you receive any messages.
The setup will show this:
Non-standard configuration detected, you need to change the data URL in /etc/collectd/collectd.conf!
But that’s easily rectified:
sudo sed -i -e 's?localhost/dump1090.*?localhost/combine1090"?' /etc/collectd/collectd.conf
sudo systemctl restart collectd
Anyhow i have the strong suspicion there is something wrong with the receiver itself.
So all this might not help.
But with the graphs you can at least check if there was anything received.
Hi wiedehopf,
I’ve installed the graphs and modified the collectd.conf
pi@piaware:~ $ systemctl restart collectd
AUTHENTICATING FOR org.freedesktop.systemd1.manage-units
Authentication is required to restart ‘collectd.service’.
Authenticating as: root
Password: Failed to restart collectd.service: Connection timed out
See system logs and ‘systemctl status collectd.service’ for details.
polkit-agent-helper-1: pam_authenticate failed: Authentication failure
pi@piaware:~ $ 2019-07-19 15:46:08Z failed to reopen /var/log/piaware.log: couldn’t open “/var/log/piaware.log”: permission denied
2019-07-19 15:46:08Z ****************************************************
2019-07-19 15:46:08Z piaware version 3.7.1 is running, process ID 19144
2019-07-19 15:46:08Z your system info is: Linux piaware 4.14.98-v7+ #1200 SMP Tue Feb 12 20:27:48 GMT 2019 armv7l GNU/Linux
2019-07-19 15:46:09Z Connecting to FlightAware adept server at piaware.flightaware.com/1200
2019-07-19 15:46:10Z Connection with adept server at piaware.flightaware.com/1200 established
2019-07-19 15:46:11Z ADS-B data program ‘dump1090-fa’ is listening on port 29005, so far so good
2019-07-19 15:46:11Z Starting faup1090: /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 29005 --stdout --lat -12.111 --lon 96.493
2019-07-19 15:46:11Z Started faup1090 (pid 19248) to connect to dump1090-fa
2019-07-19 15:46:11Z UAT support disabled by local configuration setting: uat-receiver-type
2019-07-19 15:46:12Z TLS handshake with adept server at piaware.flightaware.com/1200 completed
2019-07-19 15:46:12Z FlightAware server certificate validated
2019-07-19 15:46:12Z encrypted session established with FlightAware
2019-07-19 15:46:14Z adept reported location: (removed) -15203ft AMSL
2019-07-19 15:46:14Z logged in to FlightAware as user ypcc1
2019-07-19 15:46:14Z my feeder ID is (removed)
2019-07-19 15:46:14Z Failed to update feeder ID file at /var/cache/piaware/feeder_id: couldn’t open “/var/cache/piaware/feeder_id.new”: permission denied
2019-07-19 15:46:14Z site statistics URL: https://flightaware.com/adsb/stats/user/ypcc1#stats-107377
2019-07-19 15:46:14Z multilateration data requested
2019-07-19 15:46:14Z Starting multilateration client: /usr/lib/piaware/helpers/fa-mlat-client --input-connect localhost:29005 --input-type auto --results beast,connect,localhost:30104 --results beast,listen,30105 --results ext_basestation,listen,30106 --udp-transport 70.42.6.156:5618:749450666
2019-07-19 15:46:14Z mlat-client(19339): fa-mlat-client 0.2.10 starting up
2019-07-19 15:46:14Z mlat-client(19339): Using UDP transport to 70.42.6.156 port 5618
2019-07-19 15:46:14Z mlat-client(19339): Warning: Could not create results output ‘beast,listen,30105’: [Errno 98] Address already in use
2019-07-19 15:46:14Z mlat-client(19339): Warning: Could not create results output ‘ext_basestation,listen,30106’: [Errno 98] Address already in use
2019-07-19 15:46:15Z mlat-client(19339): Input connected to localhost:29005
2019-07-19 15:46:15Z mlat-client(19339): Beast-format results connection with ::1:30104: [Errno 111] Connection refused
2019-07-19 15:46:42Z 0 msgs recv’d from dump1090-fa; 0 msgs sent to FlightAware
2019-07-19 15:46:46Z mlat-client(19339): Beast-format results connection with 127.0.0.1:30104: [Errno 111] Connection refused
2019-07-19 15:47:16Z mlat-client(19339): Beast-format results connection with ::1:30104: [Errno 111] Connection refused
2019-07-19 15:47:41Z mlat-client(19339): Detected BEAST format input
2019-07-19 15:47:41Z mlat-client(19339): Input format changed to BEAST, 12MHz clock
2019-07-19 15:47:46Z mlat-client(19339): Beast-format results connection with 127.0.0.1:30104: [Errno 111] Connection refused
2019-07-19 15:48:17Z mlat-client(19339): Beast-format results connection with ::1:30104: [Errno 111] Connection refused
2019-07-19 15:48:47Z mlat-client(19339): Beast-format results connection with 127.0.0.1:30104: [Errno 111] Connection refused
2019-07-19 15:49:18Z mlat-client(19339): Beast-format results connection with ::1:30104: [Errno 111] Connection refused
I don’t believe there’s anything wrong with the receiver. I was using it until two days ago when I switched from FlightRadar to Flightaware.
you missed the sudo 
Anyway all the errors for piaware look like you tried to start piaware on the console?
Yep. I forgot the sudo. I’ve reapplied the command and the graphs1090 are now showing correctly.
I’ll check the graphs in a few hours and advise if any aircraft are reported.
Thanks again.
Just to reiterate, don’t open piaware on the console.
It is running as a service.
If you want to follow the log:
journalctl -f
Also it seems you accidentally put in a strange altitude when entering the Location.
(also wrong location)
But that shouldn’t matter for getting positions reported with flightaware.
You might want to just configure an existing feeder-id when using a new sd-card:
For Beginners - How to Get Back Existing Station Number in A Fresh Install
That means you don’t need to reconfigure the location.
No worries wiedenhopf. I wont open piaware on the console.
I never added an altitude. That’s strange. Thanks for the info on getting back the Feeder-ID.
Out of curiosity, replicated @ypcc1 's install
1. On Windows Desktop
(a) Plugged-in DVB-T into windows Desktop and ran dump1090-win.1.10.3010.14 (by Malcom Rob). The default output of AVR is at port 30002
(b) Checked in browser in Windows computer
localhost:30002
2. On RPI
(a) Wrote Raspian Buster to microSD card
(b) Installed Piaware (package install), but NO dump1090-fa or mutab
NOTE: Did NOT modify any settings of Piaware. Used default settings
.
(c ) Installed ModeSMixer2
(d) Modified file mm2.sh. It now reads as follows:
sudo nano /home/pi/mm2/mm2.sh
#!/bin/sh
/home/pi/mm2/modesmixer2 \
--inConnect 192.168.0.10:30002 \
--outServer beast:30005 \
--web 8787 \
--location 43.xxx:-79.xxx \
Checked Piaware
pi@raspberrypi:~ $ sudo systemctl status piaware
● piaware.service - FlightAware ADS-B uploader
Loaded: loaded (/lib/systemd/system/piaware.service; enabled; vendor preset: enabled)
Active: active (running) since Fri 2019-07-19 18:50:47 BST; 4s ago
Docs: https://flightaware.com/adsb/piaware/
Main PID: 614 (piaware)
Tasks: 4 (limit: 2200)
Memory: 11.5M
CGroup: /system.slice/piaware.service
├─614 /usr/bin/piaware -p /run/piaware/piaware.pid -plainlog -statusfile /run/piaware/status.json
├─646 /usr/lib/piaware/helpers/fa-mlat-client --input-connect localhost:30005 --input-type dump1090 --results beast,co
└─657 /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout --lat 43.xxx --lon -79.xxx
Jul 19 18:50:50 raspberrypi sudo[637]: pam_unix(sudo:session): session opened for user root by (uid=0)
Jul 19 18:50:51 raspberrypi sudo[637]: pam_unix(sudo:session): session closed for user root
Jul 19 18:50:51 raspberrypi piaware[614]: Starting multilateration client: /usr/lib/piaware/helpers/fa-mlat-client --input-connec
Jul 19 18:50:51 raspberrypi sudo[647]: piaware : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/netstat --program --tcp --wide -
Jul 19 18:50:51 raspberrypi sudo[647]: pam_unix(sudo:session): session opened for user root by (uid=0)
Jul 19 18:50:51 raspberrypi sudo[647]: pam_unix(sudo:session): session closed for user root
Jul 19 18:50:51 raspberrypi piaware[614]: ADS-B data program 'modesmixer2' is listening on port 30005, so far so good
Jul 19 18:50:51 raspberrypi piaware[614]: Starting faup1090: /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo
Jul 19 18:50:51 raspberrypi piaware[614]: Started faup1090 (pid 657) to connect to modesmixer2
Jul 19 18:50:51 raspberrypi piaware[614]: UAT support disabled by local configuration setting: uat-receiver-type
Checked ModeSMixer2 Map
Checked Data in SSH
pi@raspberrypi:~ $ nc 192.168.0.10 30002
@00063482DE948DC02EC7580D84A8157062092A00;
@00063484570202A1833D20B2CB;
@0006348986DC02C18B18613B98;
@0006349B88C85DC07F3902E67B;
@0006349BED1800C608B305BB0F;
@000634A8007420000793925F44;
@000634A82BFA2000033DAC92D3;
@000634AC7B6A5DC006DDDBEFC6;
@000634ACFDC08DC02EC799146F8D48388731DFBD;
@000634B5E3148DC07F37990CA092B84402372C60;
@000634B6C9A8026181975AAFC3;
@000634B78F9602A1833D20B2CB;
@000634B8672A8DC0173F9945109A48642A71E332;
@000634BDB2AC00C188B3DD86EC;
@000634C0A0708DC006DD5041C531901A051266A6;
@000634C0AFE220000B18229FFB;
@000634C3D868026181975AAFC3;
@000634C4A32459C009AED31C00;
@000634C518720281829892C823;
@000634C70B5C026181975AAFC3;
@000634C88B5002A1833D20B2CB;
@000634C8BFACA00002988DB00000000000D8ED63;
@000634CDFB1402C1873BD71231;
@000634D39ADE0281829892C823;
@000634D8F7A65DC01DCCA65997;
@000634DF16EA5DC0179136F17C;
@000634DF594402A6033DF88F28;
@000634E198EA5DC01DCCA65997;
@000634E27AB62000081C30A400;
@000634E4BFF020000C32091613;
@000634E507D2026181975AAFC3;
@000634E7936E8DC02EC7580D74A809705B9AEDB8;
^C
pi@raspberrypi:~ $
Jul 19 19:26:43 raspberrypi piaware[877]: mlat-client(915): Listening for Beast-format results connection on port 30105
Jul 19 19:26:43 raspberrypi piaware[877]: mlat-client(915): Listening for Extended Basestation-format results connection on port 30106
Jul 19 19:26:43 raspberrypi piaware[877]: mlat-client(915): Connection to localhost:30005 lost: [Errno 111] Connection refused
Jul 19 19:26:43 raspberrypi piaware[877]: mlat-client(915): Reconnecting in 0.5 seconds
Jul 19 19:26:44 raspberrypi piaware[877]: mlat-client(915): Beast-format results connection with ::1:30104: [Errno 111] Connection ref
Jul 19 19:26:44 raspberrypi piaware[877]: mlat-client(915): Input connected to localhost:30005
Jul 19 19:26:44 raspberrypi piaware[877]: mlat-client(915): Input format changed to BEAST, 12MHz clock
Jul 19 19:26:44 raspberrypi piaware[877]: piaware has successfully sent several msgs to FlightAware!
Jul 19 19:27:14 raspberrypi piaware[877]: 58 msgs recv'd from modesmixer2; 58 msgs sent to FlightAware
.
Noted following:
Beast-format results connection with ::1:30104: [Errno 111] Connection refused
.
Will add following line to mm2.sh to allow Mlat feed-back from Piaware to connect to ModSMiixer2
--inConnectId 127.0.0.1:30104:MLAT \
Afraid above may cause loop-back mlat to piaware/flightaware ???