Radio and MLAT orange/green back and forth since few days

Hi,
I don’t know why but since a few days I got some black/white strip square in my hourly received report. myip/dump1090-fa/ don’t show any aircraft. My total position normally varies from 210k and 254k but since that problem 33k and 50k, I know it’s normal if no radio is detected and orange in status page. My setup is roof mounting since over 6 month without any problem. All my connections and connectors look good. I use Piaware 3.5, Flightaware 1090MHz antenna with PI2 and NooElect DVB-T dongle.

What I can check to know what’s going wrong? Log? params? Reinstall piaware 3.5 image?

Thanks

run following commands and post output generated:

lsusb

sudo systemctl status dump1090-fa

sudo systemctl status piaware

My Pi is running ok, and I get this response:

pi@piaware:~$ lsusb
Bus 001 Device 004: ID 0bda:2832 Realtek Semiconductor Corp. RTL2832U DVB-T
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

pi@piaware:~$ sudo systemctl status dump1090-fa
● dump1090-fa.service - dump1090 ADS-B receiver (FlightAware customization)
Loaded: loaded (/lib/systemd/system/dump1090-fa.service; enabled)
Active: active (running) since Mon 2017-06-19 22:17:10 UTC; 1 day 7h ago
Docs: flightaware.com/adsb/piaware/
Main PID: 497 (dump1090-fa)
CGroup: /system.slice/dump1090-fa.service
└─497 / usr / bin / dump1090-fa --net-bo-port 30005 --fix --device-index 0 --gain 30 --ppm 0 --max-range 360 --net --net-heartbeat 60 --net-ro-si…

Jun 19 22:17:10 piaware systemd[1]: Started dump1090 ADS-B receiver (FlightAware customization).
Jun 19 22:17:10 piaware dump1090-fa[497]: Mon Jun 19 22:17:10 2017 UTC dump1090-fa 3.5.0 starting up.
Jun 19 22:17:10 piaware dump1090-fa[497]: rtlsdr: using device #0: Generic RTL2832U (Realtek, RTL2832UFA, SN 00001000)
Jun 19 22:17:10 piaware dump1090-fa[497]: Found Rafael Micro R820T tuner
Jun 19 22:17:11 piaware dump1090-fa[497]: rtlsdr: tuner gain set to 29.7 dB

pi@piaware:~$ sudo systemctl status piaware
● piaware.service - FlightAware ADS-B uploader
Loaded: loaded (/lib/systemd/system/piaware.service; enabled)
Active: active (running) since Mon 2017-06-19 22:17:10 UTC; 1 day 7h ago
Docs: flightaware.com/adsb/piaware/
Main PID: 498 (piaware)
CGroup: /system.slice/piaware.service
├─498 / usr / bin / piaware -p / run / piaware / piaware.pid -plainlog -statusfile / run / piaware / status.json
├─678 / usr / lib / piaware / helpers / faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout --lat 43.5xx --lon -79.6xx
└─914 / usr / lib / piaware / helpers / fa-mlat-client --input-connect localhost:30005 --input-type dump1090 --results beast,connect,localhost:30104 …

Jun 21 05:33:18 piaware piaware[498]: 346214 msgs recv’d from dump1090-fa (218 in last 5m); 346076 msgs sent to FlightAware
Jun 21 05:38:18 piaware piaware[498]: 346521 msgs recv’d from dump1090-fa (307 in last 5m); 346383 msgs sent to FlightAware
Jun 21 05:43:18 piaware piaware[498]: 346848 msgs recv’d from dump1090-fa (327 in last 5m); 346710 msgs sent to FlightAware
Jun 21 05:43:40 piaware piaware[498]: mlat-client(914): Receiver status: connected
Jun 21 05:43:40 piaware piaware[498]: mlat-client(914): Server status: synchronized with 58 nearby receivers
Jun 21 05:43:40 piaware piaware[498]: mlat-client(914): Receiver: 42.6 msg/s received 21.0 msg/s processed (49%)
Jun 21 05:43:40 piaware piaware[498]: mlat-client(914): Server: 0.0 kB/s from server 0.0kB/s TCP to server 0.3kB/s UDP to server
Jun 21 05:43:40 piaware piaware[498]: mlat-client(914): Results: 7.1 positions/minute
Jun 21 05:43:40 piaware piaware[498]: mlat-client(914): Aircraft: 3 of 7 Mode S, 11 of 11 ADS-B used
Jun 21 05:48:18 piaware piaware[498]: 347115 msgs recv’d from dump1090-fa (267 in last 5m); 346977 msgs sent to FlightAware

Hi,
I’ve got suprise this morning: Radio is come back alone… So this is the result with the running radio and MLAT. When it will fall again, I’ll post you the same test with the RADIO out.

Thanks alot for the moment. You show me new commands to check my running station.

Mathieu

pi@piaware:~$ lsusb

Bus 001 Device 004: ID 0bda:2838 Realtek Semiconductor Corp. RTL2838 DVB-T
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

pi@piaware:~$ sudo systemctl status dump1090-fa

● dump1090-fa.service - dump1090 ADS-B receiver (FlightAware customization)
Loaded: loaded (/lib/systemd/system/dump1090-fa.service; enabled)
Active: active (running) since Thu 2017-06-22 01:38:17 UTC; 2min 4s ago
Docs: flightaware.com/adsb/piaware/
Main PID: 475 (dump1090-fa)
CGroup: /system.slice/dump1090-fa.service
└─475 /usr/bin/dump1090-fa --net-bo-port 30005 --fix --device-index 0 --gain -10 --ppm 0 --max-range 360 --net --ne…

Jun 22 01:38:17 piaware systemd[1]: Started dump1090 ADS-B receiver (FlightAware customization).
Jun 22 01:38:17 piaware dump1090-fa[475]: Thu Jun 22 01:38:17 2017 UTC dump1090-fa 3.5.0 starting up.
Jun 22 01:38:17 piaware dump1090-fa[475]: rtlsdr: using device #0: Generic RTL2832U OEM (Realtek, RTL2838UHIDIR, SN 00000001)
Jun 22 01:38:17 piaware dump1090-fa[475]: Found Rafael Micro R820T tuner
Jun 22 01:38:17 piaware dump1090-fa[475]: rtlsdr: enabling tuner AGC

pi@piaware:~$ sudo systemctl status piaware

● piaware.service - FlightAware ADS-B uploader
Loaded: loaded (/lib/systemd/system/piaware.service; enabled)
Active: active (running) since Thu 2017-06-22 01:38:17 UTC; 2min 27s ago
Docs: flightaware.com/adsb/piaware/
Main PID: 476 (piaware)
CGroup: /system.slice/piaware.service
├─476 /usr/bin/piaware -p /run/piaware/piaware.pid -plainlog -statusfile /run/piaware/status.json
├─566 /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout --lat 45.513 --lon -…
└─757 /usr/lib/piaware/helpers/fa-mlat-client --input-connect localhost:30005 --input-type dump1090 --results beast…

Jun 22 01:39:33 piaware sudo[754]: pam_unix(sudo:session): session closed for user root
Jun 22 01:39:33 piaware piaware[476]: Starting multilateration client: /usr/lib/piaware/helpers/fa-mlat-client --input-…3734502
Jun 22 01:39:34 piaware piaware[476]: mlat-client(757): fa-mlat-client 0.2.9 starting up
Jun 22 01:39:34 piaware piaware[476]: mlat-client(757): Using UDP transport to 70.42.6.191 port 7659
Jun 22 01:39:34 piaware piaware[476]: mlat-client(757): Listening for Beast-format results connection on port 30105
Jun 22 01:39:34 piaware piaware[476]: mlat-client(757): Listening for Extended Basestation-format results connection on…t 30106
Jun 22 01:39:34 piaware piaware[476]: mlat-client(757): Input connected to localhost:30005
Jun 22 01:39:34 piaware piaware[476]: mlat-client(757): Input format changed to BEAST, 12MHz clock
Jun 22 01:39:35 piaware piaware[476]: mlat-client(757): Beast-format results connection with 127.0.0.1:30104: connectio…blished
Jun 22 01:39:43 piaware piaware[476]: piaware has successfully sent several msgs to FlightAware!
Hint: Some lines were ellipsized, use -l to show in full.
pi@piaware:~$

Gone again… Even after restarting /rebooting… Radio and MLAT is orange…

Here is the ouptut as requested:

pi@piaware:~$ lsusb
Bus 001 Device 006: ID 0bda:2838 Realtek Semiconductor Corp. RTL2838 DVB-T
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
pi@piaware:~$ sudo systemctl status dump1090-fa
● dump1090-fa.service - dump1090 ADS-B receiver (FlightAware customization)
Loaded: loaded (/lib/systemd/system/dump1090-fa.service; enabled)
Active: active (running) since Tue 2017-07-04 00:30:36 UTC; 42min ago
Docs: flightaware.com/adsb/piaware/
Main PID: 1330 (dump1090-fa)
CGroup: /system.slice/dump1090-fa.service
└─1330 /usr/bin/dump1090-fa --net-bo-port 30005 --fix --device-index 0 --gain -10 --ppm 0 --max-range 360 --net --net-heartbeat 60 --net-ro-size 1000 --net-ro-interval 1 --net-http-port 0 --net-ri-port 0…

Jul 04 01:03:13 piaware dump1090-fa[1330]: Tue Jul 4 01:03:13 2017 UTC No data received from the SDR for a long time, it may have wedged
Jul 04 01:04:13 piaware dump1090-fa[1330]: Tue Jul 4 01:04:13 2017 UTC No data received from the SDR for a long time, it may have wedged
Jul 04 01:05:14 piaware dump1090-fa[1330]: Tue Jul 4 01:05:14 2017 UTC No data received from the SDR for a long time, it may have wedged
Jul 04 01:06:14 piaware dump1090-fa[1330]: Tue Jul 4 01:06:14 2017 UTC No data received from the SDR for a long time, it may have wedged
Jul 04 01:07:14 piaware dump1090-fa[1330]: Tue Jul 4 01:07:14 2017 UTC No data received from the SDR for a long time, it may have wedged
Jul 04 01:08:14 piaware dump1090-fa[1330]: Tue Jul 4 01:08:14 2017 UTC No data received from the SDR for a long time, it may have wedged
Jul 04 01:09:15 piaware dump1090-fa[1330]: Tue Jul 4 01:09:15 2017 UTC No data received from the SDR for a long time, it may have wedged
Jul 04 01:10:15 piaware dump1090-fa[1330]: Tue Jul 4 01:10:15 2017 UTC No data received from the SDR for a long time, it may have wedged
Jul 04 01:11:15 piaware dump1090-fa[1330]: Tue Jul 4 01:11:15 2017 UTC No data received from the SDR for a long time, it may have wedged
Jul 04 01:12:16 piaware dump1090-fa[1330]: Tue Jul 4 01:12:16 2017 UTC No data received from the SDR for a long time, it may have wedged
pi@piaware:~$ sudo systemctl status piaware
● piaware.service - FlightAware ADS-B uploader
Loaded: loaded (/lib/systemd/system/piaware.service; enabled)
Active: active (running) since Mon 2017-07-03 23:28:58 UTC; 1h 43min ago
Docs: flightaware.com/adsb/piaware/
Main PID: 466 (piaware)
CGroup: /system.slice/piaware.service
├─ 466 /usr/bin/piaware -p /run/piaware/piaware.pid -plainlog -statusfile /run/piaware/status.json
├─ 719 /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,…
└─1350 /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout --lat 45.513 --lon -73.286

Jul 04 00:49:34 piaware piaware[466]: 169 msgs recv’d from dump1090-fa (0 in last 5m); 169 msgs sent to FlightAware
Jul 04 00:54:34 piaware piaware[466]: 169 msgs recv’d from dump1090-fa (0 in last 5m); 169 msgs sent to FlightAware
Jul 04 00:59:34 piaware piaware[466]: 169 msgs recv’d from dump1090-fa (0 in last 5m); 169 msgs sent to FlightAware
Jul 04 00:59:55 piaware piaware[466]: mlat-client(719): Receiver status: connected
Jul 04 00:59:55 piaware piaware[466]: mlat-client(719): Server status: not synchronized with any nearby receivers
Jul 04 00:59:55 piaware piaware[466]: mlat-client(719): Receiver: 0.0 msg/s received 0.0 msg/s processed (0%)
Jul 04 00:59:55 piaware piaware[466]: mlat-client(719): Server: 0.0 kB/s from server 0.0kB/s TCP to server 0.0kB/s UDP to server
Jul 04 00:59:55 piaware piaware[466]: mlat-client(719): Aircraft: 0 of 0 Mode S, 0 of 0 ADS-B used
Jul 04 01:04:34 piaware piaware[466]: 169 msgs recv’d from dump1090-fa (0 in last 5m); 169 msgs sent to FlightAware
Jul 04 01:09:34 piaware piaware[466]: 169 msgs recv’d from dump1090-fa (0 in last 5m); 169 msgs sent to FlightAware
pi@piaware:~$

Thank you
Math


Jul 04 01:12:16 piaware dump1090-fa[1330]: Tue Jul 4 01:12:16 2017 UTC No data received from the SDR for a long time, it may have wedged

Looks like hardware problem.

It may be due to a defective dvb-t. If you have another dvb-t, try it.

Another possible reason is power supply. Either it has insufficient capacity, or of poor quality or gone defective.

Also check antenna and antenna connections.

Although you are in Canada, the long summer sun may be overheating some components.

td

Thank you for your knowledges. I will try a cable to remove my components from the roof and direct under the sun… Effectively, this winter and on colder days, it seem work well…

Thanks!

Mathieu