Whats up with Reporting ??

FlightAware ADS-B Flight Tracking
1

Piware says its connected

pi@raspberrypi ~ $ sudo piaware-status
dump1090 is not running.
faup1090 is running.
piaware is running.
dump1090-mutab is listening for connections on port 30005.
faup1090 is connected to port 30005.
piaware is connected to FlightAware.
dump1090-mutab is producing data on port 30005

Then I see this

Data Feed: Live - 53 minutes ago
Feeder Check-in: Live - 4 minutes ago
Joined: 06-Oct-2015
Longest Streak: 5 days (07-Oct-2015 - Today)
Feeder Type: PiAware (Debian Package Add-on) 2.1-3
Multilateration (MLAT): Supported / Enabled

If I view live data I see planes

2

Now Im getting this

Anomaly report for PiAware feeder with a MAC address of b8:27:eb:bd:44:6e:
This feeder is not being used for multilateration because its timing information appears to be unreliable. This can be caused by the site location being incorrect, or because your Pi is running out of free CPU.

3

top - 13:04:24 up 1 min, 1 user, load average: 1.36, 0.66, 0.25
Tasks: 94 total, 2 running, 92 sleeping, 0 stopped, 0 zombie
%Cpu(s): 37.3 us, 7.5 sy, 0.0 ni, 51.6 id, 0.0 wa, 0.0 hi, 3.6 si, 0.0 st
KiB Mem: 445044 total, 140732 used, 304312 free, 15936 buffers
KiB Swap: 102396 total, 0 used, 102396 free, 60296 cached

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
1851 dump1090 15 -5 18280 9424 1884 R 38.0 2.1 0:30.50 dump1090-mutabi
2412 root 20 0 11368 9664 5360 S 3.2 2.2 0:02.42 fa-mlat-client
2146 root 20 0 17404 7916 4520 S 1.3 1.8 0:02.42 piaware
2486 pi 20 0 4672 2476 2100 R 1.3 0.6 0:00.42 top
7 root 20 0 0 0 0 S 0.3 0.0 0:00.56 rcu_preempt
1605 root 20 0 1752 1212 1120 S 0.3 0.3 0:00.09 ifplugd
2400 root 20 0 2652 2016 1832 S 0.3 0.5 0:00.15 faup1090
1 root 20 0 2148 1312 1208 S 0.0 0.3 0:01.77 init
2 root 20 0 0 0 0 S 0.0 0.0 0:00.00 kthreadd
3 root 20 0 0 0 0 S 0.0 0.0 0:00.21 ksoftirqd/0
4 root 20 0 0 0 0 S 0.0 0.0 0:00.00 kworker/0:0
5 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 kworker/0:0H
6 root 20 0 0 0 0 S 0.0 0.0 0:00.06 kworker/u2:0
8 root 20 0 0 0 0 S 0.0 0.0 0:00.00 rcu_sched
9 root 20 0 0 0 0 S 0.0 0.0 0:00.00 rcu_bh
10 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 khelper
11 root 20 0 0 0 0 S 0.0 0.0 0:00.01 kdevtmpfs
12 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 netns
13 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 perf
14 root 20 0 0 0 0 S 0.0 0.0 0:00.00 khungtaskd
15 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 writeback
16 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 crypto
17 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 bioset
18 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 kblockd
19 root 20 0 0 0 0 S 0.0 0.0 0:00.46 kworker/0:1
20 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 rpciod
21 root 20 0 0 0 0 S 0.0 0.0 0:00.00 kswapd0
22 root 20 0 0 0 0 S 0.0 0.0 0:00.00 fsnotify_mark
23 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 nfsiod
29 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 kthrotld
30 root 1 -19 0 0 0 S 0.0 0.0 0:00.00 VCHIQ-0
31 root 1 -19 0 0 0 S 0.0 0.0 0:00.00 VCHIQr-0
32 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 VCHIQs-0

4

When I look at 8080 Im seeing AIRCRAFT and Mutibility reports … They say I’m synced with 16 receivers yet no feed for an hour ??

Data Feed: Today - about an hour ago
Feeder Check-in: Live - 3 minutes ago
Joined: 06-Oct-2015
Longest Streak: 5 days (07-Oct-2015 - Today)
Feeder Type: PiAware (Debian Package Add-on) 2.1-3
Multilateration (MLAT): Supported / Enabled (synchronized with 16 nearby receivers)

5

Different parts of the system. The mlat status comes direct from the mlat servers. The data feed time comes from where the stats processing (a separate thing) has got up to.