website saying "Offline" but local page and systemd status saying all is ok.

[abcd567]

This may be because of two reasons:

1. The clock of your pi is not properly synchronized. You can synchronize it by following commands
   

   sudo /etc/init.d/ntp stop
   sudo ntpd -q -g
   sudo /etc/init.d/ntp start

2. You are not receiving enough number of ADS-B messages. If you are using the Whip antenna which came with the DVB-T,
   1. place it over a metal sheet or food can
   2. change its location close to a glass window or outer wall where signals are strong.

[RunnerFL]

There is no trackable aircraft within range/uploaded. So the server sends a kill command to restart it.

Pings are keep alive. Too many means no data received

Sent from my XT1092 using Tapatalk

I'm 2 miles from a very active airport. I refuse to believe nothing is within range.

[RunnerFL]

This is the receiver I have:

https://smile.amazon.com/gp/product/B01K5KAN60/ref=oh_aui_detailpage_o03_s00?ie=UTF8&psc=1

I'll move it to another location tonight when I get home and see what happens. It is occasionally seeing aircraft where it is now, 96 reported yesterday, but that does seem low with KPBI within 2 miles.

[abcd567]

This is the receiver I have:

https://smile.amazon.com/gp/product/B01K5KAN60/ref=oh_aui_detailpage_o03_s00?ie=UTF8&psc=1

Equipment is good.

I'll move it to another location tonight when I get home and see what happens. It is occasionally seeing aircraft where it is now, 96 reported yesterday, but that does seem low with KPBI within 2 miles.

At 2 miles from KPBI and ONLY 96 in one day!!!
Must be something wrong either with Location of Antenna, or Bad Connections, or defective hardware. Do you use any cables (other than in the Amazon kit) between antenna and DVB-T?

[RunnerFL]

Equipment is good.



At 2 miles from KPBI and ONLY 96 in one day!!!
Must be something wrong either with Location of Antenna, or Bad Connections, or defective hardware. Do you use any cables (other than in the Amazon kit) between antenna and DVB-T?

No, I only used the cables and antennas provided. I have the ability to put it in my attic, I'll try that tonight. lol

[RunnerFL]

Moved the pi to the attic and there for a bit everything seemed better but then dropped off again. Seems like I only collect data for about 5 minutes then I go right back to "No ADS-B time reference available" and ping numbers incrementing.

2017-11-22 02:40:46 | [main][i]Reader thread started
2017-11-22 02:40:46 | [master][i]Starting processing thread
2017-11-22 02:40:46 | [main][i]MLAT data feed started
2017-11-22 02:40:46 | [reader][i]Initializing reader
2017-11-22 02:40:46 | [mlat][i]Waiting for MLAT configuration
2017-11-22 02:40:46 | [reader][i]Connecting to DVBT receiver via (exe:///usr/lib/fr24/dump1090 --net --raw --mlat)
2017-11-22 02:40:46 | [reader][i]Connected to the receiver, configuring
2017-11-22 02:40:46 | [reader][i]Configured, processing messages
2017-11-22 02:40:47 | [time][i]Synchronizing time via NTP
2017-11-22 02:40:49 | [reader][w]Setting new UTC offset: 0!
2017-11-22 02:41:26 | [time][i]Time synchronized correctly, offset -0.0007 seconds
2017-11-22 02:41:26 | [main][i]Feed Network client started
2017-11-22 02:41:26 | [feed][i]Downloading configuration
2017-11-22 02:41:27 | [feed][c]Interval: 5s
2017-11-22 02:41:27 | [feed][c]Latitude: 26.6214
2017-11-22 02:41:27 | [feed][c]Longitude: -80.1064
2017-11-22 02:41:27 | [feed][c]GND: YES
2017-11-22 02:41:27 | [feed][c]NonADSB: YES
2017-11-22 02:41:27 | [feed][c]Timestamps: optional
2017-11-22 02:41:27 | [feed][c]Max range AIR: 350.0nm
2017-11-22 02:41:27 | [feed][c]Max range GND: 100.0nm
2017-11-22 02:41:27 | [feed][i]defined 5 servers
2017-11-22 02:41:27 | [feed][n]KPBI10@83.140.21.85:8099/UDP
2017-11-22 02:41:27 | [feed][n]connecting
2017-11-22 02:41:27 | [stats][i]Stats thread started
2017-11-22 02:41:27 | [feed][n]connected via UDP (fd 9)
2017-11-22 02:41:27 | [feed][n]working
2017-11-22 02:41:28 | [mlat][i]MLAT configuration received, service ENABLED
2017-11-22 02:41:28 | [mlat][i]Starting MLAT with preconfigured position: 26.62,-80.11, 3.0
2017-11-22 02:41:28 | [mlat][i]MLAT bandwidth reduction active, level 1
2017-11-22 02:41:28 | [mlat][i]Configuring UDP connection udp://usa-2.fr24.com:19788
2017-11-22 02:41:28 | [feed][i]sent 1,0 AC
2017-11-22 02:41:33 | [feed][i]sent 2,0 AC
2017-11-22 02:41:38 | [mlat][i]Registering MLAT station
2017-11-22 02:41:38 | [mlat][i]Registering MLAT station: SUCCESS
2017-11-22 02:41:38 | [feed][i]sent 3,0 AC
2017-11-22 02:41:40 | [mlat][i]Received ADS-B time references AC:
2017-11-22 02:41:40 | [mlat][i] A320C9
2017-11-22 02:41:40 | [mlat][i]Pinging the server
2017-11-22 02:41:40 | [mlat][i]Stats 857/857
2017-11-22 02:41:44 | [feed][i]sent 3,0 AC
2017-11-22 02:41:49 | [feed][i]sent 4,0 AC
2017-11-22 02:41:55 | [feed][i]sent 5,0 AC
2017-11-22 02:42:00 | [feed][i]sent 5,0 AC
2017-11-22 02:42:00 | [mlat][i]Pinging the server
2017-11-22 02:42:00 | [mlat][i]Stats 857/0
2017-11-22 02:42:06 | [feed][i]sent 6,0 AC
2017-11-22 02:42:11 | [feed][i]sent 4,0 AC
2017-11-22 02:42:16 | [feed][i]sent 4,0 AC
2017-11-22 02:42:20 | [mlat][i]Received ADS-B time references AC:
2017-11-22 02:42:20 | [mlat][i] A4C735
2017-11-22 02:42:20 | [mlat][i] A821E4
2017-11-22 02:42:20 | [mlat][i] C066A2
2017-11-22 02:42:20 | [mlat][i]Pinging the server
2017-11-22 02:42:20 | [mlat][i]Stats 861/4
2017-11-22 02:42:21 | [feed][i]sent 5,0 AC
2017-11-22 02:42:26 | [feed][i]sent 5,0 AC
2017-11-22 02:42:31 | [feed][i]sent 5,0 AC
2017-11-22 02:42:37 | [feed][i]sent 4,0 AC
2017-11-22 02:42:40 | [mlat][i]Pinging the server
2017-11-22 02:42:40 | [mlat][i]Stats 867/6
2017-11-22 02:42:42 | [feed][i]sent 4,0 AC
2017-11-22 02:42:52 | [feed][i]sent 4,0 AC
2017-11-22 02:42:58 | [feed][i]sent 4,0 AC
2017-11-22 02:42:58 | [feed][n]syncing stream async: 1
2017-11-22 02:42:59 | [feed][n]syncing stream result: 1
2017-11-22 02:43:00 | [mlat][i]Pinging the server
2017-11-22 02:43:00 | [mlat][i]Stats 872/5
2017-11-22 02:43:03 | [feed][i]sent 4,0 AC
2017-11-22 02:43:04 | [feed][i]removed 1 of 7 AC
2017-11-22 02:43:08 | [feed][i]sent 4,0 AC
2017-11-22 02:43:14 | [feed][i]sent 4,0 AC
2017-11-22 02:43:20 | [feed][i]sent 3,0 AC
2017-11-22 02:43:20 | [mlat][i]Received ADS-B time references AC:
2017-11-22 02:43:20 | [mlat][i] A821E4
2017-11-22 02:43:20 | [mlat][i] C066A2
2017-11-22 02:43:20 | [mlat][i]Pinging the server
2017-11-22 02:43:20 | [mlat][i]Stats 884/12
2017-11-22 02:43:25 | [feed][i]sent 3,0 AC
2017-11-22 02:43:32 | [feed][i]sent 2,0 AC
2017-11-22 02:43:37 | [feed][i]sent 3,0 AC
2017-11-22 02:43:40 | [mlat][i]Pinging the server
2017-11-22 02:43:40 | [mlat][i]Stats 884/0
2017-11-22 02:43:42 | [feed][i]sent 3,0 AC
2017-11-22 02:43:44 | [feed][i]removed 1 of 7 AC
2017-11-22 02:43:57 | [feed][i]sent 3,0 AC
2017-11-22 02:44:00 | [mlat][i]Pinging the server
2017-11-22 02:44:00 | [mlat][i]Stats 911/27
2017-11-22 02:44:10 | [mlat][i]No ADS-B time reference available (0/0)
2017-11-22 02:44:13 | [feed][i]sent 3,0 AC
2017-11-22 02:44:17 | [feed][i]removed 1 of 6 AC
2017-11-22 02:44:18 | [feed][i]sent 2,0 AC
2017-11-22 02:44:20 | [mlat][i]Received ADS-B time references AC:
2017-11-22 02:44:20 | [mlat][i] A821E4
2017-11-22 02:44:20 | [mlat][i] C066A2
2017-11-22 02:44:20 | [mlat][i]Pinging the server
2017-11-22 02:44:20 | [mlat][i]Stats 911/0
2017-11-22 02:44:24 | [feed][i]sent 2,0 AC
2017-11-22 02:44:30 | [feed][i]sent 2,0 AC
2017-11-22 02:44:35 | [feed][i]sent 2,0 AC
2017-11-22 02:44:40 | [feed][i]sent 4,0 AC
2017-11-22 02:44:40 | [mlat][i]Pinging the server
2017-11-22 02:44:40 | [mlat][i]Stats 934/23
2017-11-22 02:44:47 | [feed][i]sent 2,0 AC
2017-11-22 02:45:01 | [mlat][i]Pinging the server
2017-11-22 02:45:01 | [mlat][i]Stats 934/0
2017-11-22 02:45:10 | [mlat][i]No ADS-B time reference available (0/0)
2017-11-22 02:45:17 | [feed][n]ping 1
2017-11-22 02:45:18 | [feed][n]syncing stream result: 1
2017-11-22 02:45:20 | [mlat][i]No ADS-B time reference available (0/0)
2017-11-22 02:45:20 | [mlat][i]Pinging the server
2017-11-22 02:45:20 | [mlat][i]Stats 934/0
2017-11-22 02:45:30 | [mlat][i]No ADS-B time reference available (0/0)
2017-11-22 02:45:40 | [mlat][i]No ADS-B time reference available (0/0)
2017-11-22 02:45:40 | [mlat][i]Pinging the server
2017-11-22 02:45:40 | [mlat][i]Stats 934/0
2017-11-22 02:45:47 | [feed][n]ping 2
2017-11-22 02:45:48 | [feed][n]syncing stream result: 1
2017-11-22 02:45:50 | [mlat][i]No ADS-B time reference available (0/0)
2017-11-22 02:46:00 | [mlat][i]No ADS-B time reference available (0/0)
2017-11-22 02:46:00 | [mlat][i]Pinging the server
2017-11-22 02:46:00 | [mlat][i]Stats 934/0
2017-11-22 02:46:11 | [mlat][i]No ADS-B time reference available (0/0)
2017-11-22 02:46:17 | [feed][n]ping 3
2017-11-22 02:46:18 | [feed][n]syncing stream result: 1
2017-11-22 02:46:20 | [mlat][i]No ADS-B time reference available (0/0)
2017-11-22 02:46:20 | [mlat][i]Pinging the server
2017-11-22 02:46:20 | [mlat][i]Stats 934/0
2017-11-22 02:46:30 | [mlat][i]No ADS-B time reference available (0/0)
2017-11-22 02:46:40 | [mlat][i]No ADS-B time reference available (0/0)
2017-11-22 02:46:40 | [mlat][i]Pinging the server
2017-11-22 02:46:40 | [mlat][i]Stats 934/0
2017-11-22 02:46:47 | [feed][n]ping 4
2017-11-22 02:46:48 | [feed][n]syncing stream result: 1
2017-11-22 02:46:50 | [mlat][i]No ADS-B time reference available (0/0)
2017-11-22 02:47:00 | [mlat][i]No ADS-B time reference available (0/0)
2017-11-22 02:47:00 | [mlat][i]Pinging the server
2017-11-22 02:47:00 | [mlat][i]Stats 934/0
2017-11-22 02:47:10 | [mlat][i]No ADS-B time reference available (0/0)
2017-11-22 02:47:17 | [feed][n]ping 5
2017-11-22 02:47:18 | [feed][n]syncing stream result: 1
2017-11-22 02:47:21 | [mlat][i]No ADS-B time reference available (0/0)
2017-11-22 02:47:21 | [mlat][i]Pinging the server
2017-11-22 02:47:21 | [mlat][i]Stats 934/0
2017-11-22 02:47:30 | [mlat][i]No ADS-B time reference available (0/0)
2017-11-22 02:47:40 | [mlat][i]No ADS-B time reference available (0/0)
2017-11-22 02:47:40 | [mlat][i]Pinging the server
2017-11-22 02:47:40 | [mlat][i]Stats 934/0
2017-11-22 02:47:47 | [feed][n]ping 6
2017-11-22 02:47:48 | [feed][n]syncing stream result: 1
2017-11-22 02:47:50 | [mlat][i]No ADS-B time reference available (0/0)
2017-11-22 02:48:00 | [mlat][i]No ADS-B time reference available (0/0)
2017-11-22 02:48:00 | [mlat][i]Pinging the server
2017-11-22 02:48:00 | [mlat][i]Stats 934/0
2017-11-22 02:48:10 | [mlat][i]No ADS-B time reference available (0/0)
2017-11-22 02:48:17 | [feed][n]ping 7
2017-11-22 02:48:18 | [feed][n]syncing stream result: 1
2017-11-22 02:48:20 | [mlat][i]No ADS-B time reference available (0/0)
2017-11-22 02:48:20 | [mlat][i]Pinging the server
2017-11-22 02:48:20 | [mlat][i]Stats 934/0
2017-11-22 02:48:30 | [mlat][i]No ADS-B time reference available (0/0)
2017-11-22 02:48:40 | [mlat][i]No ADS-B time reference available (0/0)
2017-11-22 02:48:40 | [mlat][i]Pinging the server
2017-11-22 02:48:40 | [mlat][i]Stats 934/0

[Oblivian]

You did expand the Pi Filesystem from the 15mb or whatever it opens with right.. so its not full and crashing or anything silly.

[RunnerFL]

You did expand the Pi Filesystem from the 15mb or whatever it opens with right.. so its not full and crashing or anything silly.

Yes, I did. This isn't my first time working with a Pi.

pi@raspberrypi:/etc/cron.d $ df -ah
Filesystem Size Used Avail Use% Mounted on
/dev/root 7.2G 642M 6.3G 10% /
devtmpfs 458M 0 458M 0% /dev
sysfs 0 0 0 - /sys
proc 0 0 0 - /proc
tmpfs 462M 4.0K 462M 1% /dev/shm
devpts 0 0 0 - /dev/pts
tmpfs 462M 6.3M 456M 2% /run
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 462M 0 462M 0% /sys/fs/cgroup
cgroup 0 0 0 - /sys/fs/cgroup/systemd
cgroup 0 0 0 - /sys/fs/cgroup/cpu,cpuacct
cgroup 0 0 0 - /sys/fs/cgroup/blkio
cgroup 0 0 0 - /sys/fs/cgroup/memory
cgroup 0 0 0 - /sys/fs/cgroup/devices
cgroup 0 0 0 - /sys/fs/cgroup/freezer
cgroup 0 0 0 - /sys/fs/cgroup/net_cls
systemd-1 0 0 0 - /proc/sys/fs/binfmt_misc
debugfs 0 0 0 - /sys/kernel/debug
mqueue 0 0 0 - /dev/mqueue
configfs 0 0 0 - /sys/kernel/config
tmpfs 100M 2.5M 98M 3% /var/log
/dev/mmcblk0p1 60M 22M 39M 37% /boot

[abcd567]

Seems a hardware problem: the dvb-t is wedging after few minutes. Since there is no logging of integral dump1090 of Pi24 image, we cant check this.

The wedging of dvb-t can either due to insufficient current reaching it, or defective hardware.

The kit you have purchased has 2 dvb-t dongles. If you have plugged-in both, remove one to reduce drain on power supply.

If running single dvb-t does not solve problem, change the running dvb-t by spare dvb-t to see if the running dvb-t is defective or not.

If all above does not solve the problem, then try another good and larger power supply adapter. Most of such problems are caused by power supply (insufficient current capacity, actual capacity less than name plate rating, poor voltage regulation resulting in low voltage and ripple etc).

[abcd567]

I just now remembered that only 3 weeks ago, I have posted a method to log dump1090 output in thread "fr24feed logging", post #4

This method is for Windows version of FR24 feeder. However this is equally applicable to Pi24 feeder. The only difference is in configuration of PuTTY. Instead of using "localhost" in "Host name (or IP address)" field, use the ip-of-pi which will be something like 192.168.0.20.

The display on PuTTY will continously scroll as the messages are output by dump1090. If DVB-T wedges, the flow will stop.

[abcd567]

Post moved to thread where it logically belongs: FR24feed logging, scroll down to post #10

[RunnerFL]

Seems a hardware problem: the dvb-t is wedging after few minutes. Since there is no logging of integral dump1090 of Pi24 image, we cant check this.

The wedging of dvb-t can either due to insufficient current reaching it, or defective hardware.

The kit you have purchased has 2 dvb-t dongles. If you have plugged-in both, remove one to reduce drain on power supply.

If running single dvb-t does not solve problem, change the running dvb-t by spare dvb-t to see if the running dvb-t is defective or not.

If all above does not solve the problem, then try another good and larger power supply adapter. Most of such problems are caused by power supply (insufficient current capacity, actual capacity less than name plate rating, poor voltage regulation resulting in low voltage and ripple etc).

I've tried with only one dongle (1090 running 978 disconnected), with a bigger power supply and even new receivers/antennas and it makes no difference. It totally craps out after 5 minutes. I'm getting PO'd...

[RunnerFL]

I just now remembered that only 3 weeks ago, I have posted a method to log dump1090 output in thread "fr24feed logging", post #4

This method is for Windows version of FR24 feeder. However this is equally applicable to Pi24 feeder. The only difference is in configuration of PuTTY. Instead of using "localhost" in "Host name (or IP address)" field, use the ip-of-pi which will be something like 192.168.0.20.

The display on PuTTY will continously scroll as the messages are output by dump1090. If DVB-T wedges, the flow will stop.

First, I don't use Windows for anything. Mac or linux only. (I wouldn't be a good Unix Sys Admin if I used Windoze)

Second, that method calls for you to go to port 30003. Previously you told me to set "Decoded Data (30003)" to "No" in the settings. Can't connect to a port if nothing is there.

Not trying to give you a hard time, I'm just getting super frustrated. A co-worker with the exact same dongles, exact same pi, etc, has 0 issues...

[RunnerFL]

I turned "Decoded Data (30003)" back on and rebooted. Telnet'd to port 30003 on the pi, the data stops after about 4 mins. That's with only the 1090 dongle hooked up.

[RunnerFL]

Well.. It may be fixed. As crazy as this sounds.... The dongles wouldn't sit side by side on the pi because they were too wide to do so. For the heck of it I pulled the plastic covers off the dongles and plugged them in side by side. Now things are working. Been streaming for over an hour now.

No idea why that made a difference though.