Radarcape FA Stats


#1

I now have 2 feeds to FA all from the same Radarcape receiver.

  1. Via Planeplotter TCP/IP Port 10002
  2. Via Radarcape FA feeder.

Feed Nr1 maintains my Top User position whilst the direct feed Nr2 stats are very erratic with poor results and long periods of zero uploads. The “no position” reports are not recorded by stats

See below the RC Status Report

FlightAware Feeder Status

Last 30 Messages

14.02.2015 15:39:52(G) HTTP/1.1 200 OK X-FA-Backend: miloh Vary: Accept-Encoding Content-Type: text/html;charset=utf-8 Content-Length: 0 Accept-Ranges: bytes Date: Sat, 14 Feb 2015 15:39:51 GMT X-Varnish: 638909211 Age: 0 Via: 1.1 varnish Connection: close Server: FlightAware/3.1 X-FA-Cache: MISS cache-control: max-age=5, must-revalidate
14.02.2015 15:39:52(G) Next feeding after 18 sec
14.02.2015 15:40:12(G) Create report (BIN ALL CRC TSgps RTS FEC ACoff)
14.02.2015 15:40:12(G) Sending 259 reports, (71 position less)
14.02.2015 15:40:12(G) posting 46544 bytes
14.02.2015 15:40:12(G) done
14.02.2015 15:40:12(G) HTTP/1.1 200 OK X-FA-Backend: miloh Vary: Accept-Encoding Content-Type: text/html;charset=utf-8 Content-Length: 0 Accept-Ranges: bytes Date: Sat, 14 Feb 2015 15:40:11 GMT X-Varnish: 638916213 Age: 0 Via: 1.1 varnish Connection: close Server: FlightAware/3.1 X-FA-Cache: MISS cache-control: max-age=5, must-revalidate
14.02.2015 15:40:12(G) Next feeding after 13 sec
14.02.2015 15:40:26(G) Create report (BIN ALL CRC TSgps RTS FEC ACoff)
14.02.2015 15:40:27(G) Sending 261 reports, (70 position less)
14.02.2015 15:40:27(G) posting 46897 bytes
14.02.2015 15:40:27(G) done
14.02.2015 15:40:27(G) HTTP/1.1 200 OK X-FA-Backend: royoh Vary: Accept-Encoding Content-Type: text/html;charset=utf-8 Content-Length: 0 Accept-Ranges: bytes Date: Sat, 14 Feb 2015 15:37:31 GMT X-Varnish: 1439160362 Age: 0 Via: 1.1 varnish Connection: close Server: FlightAware/3.1 X-FA-Cache: MISS cache-control: max-age=5, must-revalidate
14.02.2015 15:40:27(G) Next feeding after 18 sec
14.02.2015 15:40:47(G) Create report (BIN ALL CRC TSgps RTS FEC ACoff)
14.02.2015 15:40:47(G) Sending 260 reports, (69 position less)
14.02.2015 15:40:47(G) posting 46739 bytes
14.02.2015 15:40:47(G) done
14.02.2015 15:40:47(G) HTTP/1.1 200 OK X-FA-Backend: elaan Vary: Accept-Encoding Content-Type: text/html;charset=utf-8 Content-Length: 0 Accept-Ranges: bytes Date: Sat, 14 Feb 2015 15:40:46 GMT X-Varnish: 668083837 Age: 0 Via: 1.1 varnish Connection: close Server: FlightAware/3.1 X-FA-Cache: MISS cache-control: max-age=5, must-revalidate
14.02.2015 15:40:47(G) Next feeding after 17 sec
14.02.2015 15:41:06(G) Create report (BIN ALL CRC TSgps RTS FEC ACoff)
14.02.2015 15:41:06(G) Sending 262 reports, (71 position less)
14.02.2015 15:41:06(G) posting 47108 bytes
14.02.2015 15:41:06(G) done0

Today I added a Piaware feed with a Raspberry Pi 2/820T2/PiAware on Raspbian Linux 1.20-1 which is looking very promising.

The antenna setup:-
Antenna: 1090SJ mk 2 Antenna
PreAmp: KU LNA 1090 A TM
30m Ecoflex 15 Plus
Sunher 3 way Power Divider to Radarcape,SBS3 and DVB-T+FM+DAB 820T2 with Minicircuits Bandpass Filtera VBFZ-1065+

http://flightaware.com/adsb/stats/user/peterbenney#stats-178

Cheers,

Peter

a


#2

Damn Peter! Don’t run off just as i had you in sight :laughing:
That’s a nice setup and doing a stable job! The Pi is really great and you might even change to the dump1090-mutability after a week or so to see even more improvement! And i’m starting to be convinced that a really low noise amplifier (not the 4 dB e-bay ones) does help in squeezing the last 5% out of it.
Today the power supply of the ethernet switch died. Would have found out sooner if i had not ignored the wife and kids complaining that half of the WiFi was down :frowning:
Keep up!
/paul


#3

Peter, I envy your setup and your stats :mrgreen: I have a homebrew Coax Collinear, RPi, ebay amp and too long a run of RG6. I have managed to get to #19 on the stats page though.

I seem to have a large number of Positions Reported (440,000/day) and approx 4300 aircraft seen. Others in the list, vern3773 have many fewer positions reported but many more aircraft seen. I don’t understand :question:


#4

The ratings are derived from a 30 day average of the Aircraft Seen total. Your reception improved on 5th Feb so you will see an improvement in your rating 30 days from that date. Those receiving distant ADS-B transponders will be receiving fewer reports hence positions from the weaker signal but will increase their aircraft seen total.

HTH

Peter


#5

The increase was because I took a DC blocker out of the feedline. I’d forgotten it was there after testing a Franklin collinear.

Thanks for your help - I’m coming to get you 8)


#6

Peter
Currently your Radarcape feed is offline since 5 hours

I have the same problem from time to time that my Radarcape feed stops out of the blue and in most cases I need to reboot the cape to get it started again. ticking and unticking it in the setup does not work.
Günter told me that there is no watchdog function built in and when the connection to the FA server fails , the feeder can stop aswell and needs a manual restart.

Which Firmware Version do you use?

However my Radarcape feed is pretty stabil, apart form the hickups…and my stats look much smoother than yours.

Be aware that the Cape feeder does not send all data to FA, but only if certain parameters have changed from a plane, thats the reason why the amount of reported planes between PP and the cape is much more different…

Tom


#7

Tom, Thanks for your feedback. FA stats shows the feed stops between 0600-1800 daily with just a few intermittent burst of data. The RC feeder shows consistent 15 sec feed sent. I do not know the FA server IP to check the connection and I have a stable 150Mb broadband service.

Firmware Version 150125.10.31

PM’d Daniel Baker.

Otherwise a very happy owner of two Radarcapes :smiley:

73’s

Peter


#8

Hi Peter
pretty easy to find out :smiley:
connect to your cape via ssh (using putty or whatever) and enter netstat, then you should see all open connections to/from your cape.
one of them is webfarm.flightaware.com which is 70.42.6.250.

same can be done on a windows pc by opening up a command window if you are feeding e.g out of planeplotter to FA etc. but here netstat -f should be used


#9

I’ve looked into a bit and think there might be a problem receiving the data. Can you send me an entire day or two of your log file from the radarcape?

Problems in the stats system itself tend to manifest in zero updates, not in missing parts of updates.


#10

I can only retrieve the last 30 msgs but will check if possible to collect a full 24/48 hours.

C:\ping 70.42.6.250

Pinging 70.42.6.250 with 32 bytes of data:
Reply from 70.42.6.250: bytes=32 time=136ms TTL=47
Reply from 70.42.6.250: bytes=32 time=134ms TTL=47
Reply from 70.42.6.250: bytes=32 time=135ms TTL=47
Reply from 70.42.6.250: bytes=32 time=135ms TTL=47

Ping statistics for 70.42.6.250:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 134ms, Maximum = 136ms, Average = 135ms

Also a glithch in Piaware stats at 10am


#11

With no stats update since 0600

Radarcape FA feeder log and server ping.

FlightAware Feeder Status

Last 30 Messages

17.02.2015 13:47:39(G) Create report (BIN ALL CRC TSgps RTS FEC ACoff)
17.02.2015 13:47:39(G) Sending 296 reports, (132 position less)
17.02.2015 13:47:39(G) posting 52121 bytes
17.02.2015 13:47:40(G) done
17.02.2015 13:47:40(G) HTTP/1.1 200 OK X-FA-Backend: royoh Vary: Accept-Encoding Content-Type: text/html;charset=utf-8 Content-Length: 0 Accept-Ranges: bytes Date: Tue, 17 Feb 2015 13:47:39 GMT X-Varnish: 722948777 Age: 0 Via: 1.1 varnish Connection: close Server: FlightAware/3.1 X-FA-Cache: MISS cache-control: max-age=5, must-revalidate
17.02.2015 13:47:40(G) Next feeding after 12 sec
17.02.2015 13:47:53(G) Create report (BIN ALL CRC TSgps RTS FEC ACoff)
17.02.2015 13:47:53(G) Sending 298 reports, (132 position less)
17.02.2015 13:47:53(G) posting 52474 bytes
17.02.2015 13:47:54(G) done
17.02.2015 13:47:54(G) HTTP/1.1 200 OK X-FA-Backend: royoh Vary: Accept-Encoding Content-Type: text/html;charset=utf-8 Content-Length: 0 Accept-Ranges: bytes Date: Tue, 17 Feb 2015 13:47:53 GMT X-Varnish: 722953443 Age: 0 Via: 1.1 varnish Connection: close Server: FlightAware/3.1 X-FA-Cache: MISS cache-control: max-age=5, must-revalidate
17.02.2015 13:47:54(G) Next feeding after 17 sec
17.02.2015 13:48:12(G) Create report (BIN ALL CRC TSgps RTS FEC ACoff)
17.02.2015 13:48:12(G) Sending 295 reports, (132 position less)
17.02.2015 13:48:12(G) posting 51862 bytes
17.02.2015 13:48:13(G) done
17.02.2015 13:48:13(G) HTTP/1.1 200 OK X-FA-Backend: royoh Vary: Accept-Encoding Content-Type: text/html;charset=utf-8 Content-Length: 0 Accept-Ranges: bytes Date: Tue, 17 Feb 2015 13:45:18 GMT X-Varnish: 1523291277 Age: 0 Via: 1.1 varnish Connection: close Server: FlightAware/3.1 X-FA-Cache: MISS cache-control: max-age=5, must-revalidate
17.02.2015 13:48:13(G) Next feeding after 15 sec
17.02.2015 13:48:29(G) Create report (BIN ALL CRC TSgps RTS FEC ACoff)
17.02.2015 13:48:29(G) Sending 292 reports, (131 position less)
17.02.2015 13:48:29(G) posting 51358 bytes
17.02.2015 13:48:30(G) done
17.02.2015 13:48:30(G) HTTP/1.1 200 OK X-FA-Backend: miloh Vary: Accept-Encoding Content-Type: text/html;charset=utf-8 Content-Length: 0 Accept-Ranges: bytes Date: Tue, 17 Feb 2015 13:48:29 GMT X-Varnish: 752241663 Age: 0 Via: 1.1 varnish Connection: close Server: FlightAware/3.1 X-FA-Cache: MISS cache-control: max-age=5, must-revalidate
17.02.2015 13:48:30(G) Next feeding after 14 sec
17.02.2015 13:48:45(G) Create report (BIN ALL CRC TSgps RTS FEC ACoff)
17.02.2015 13:48:45(G) Sending 290 reports, (129 position less)
17.02.2015 13:48:45(G) posting 51017 bytes
17.02.2015 13:48:46(G) done
17.02.2015 13:48:46(G) HTTP/1.1 200 OK X-FA-Backend: elaan Vary: Accept-Encoding Content-Type: text/html;charset=utf-8 Content-Length: 0 Accept-Ranges: bytes Date: Tue, 17 Feb 2015 13:48:45 GMT X-Varnish: 752246866 Age: 0 Via: 1.1 varnish Connection: close Server: FlightAware/3.1 X-FA-Cache: MISS cache-control: max-age=5, must-revalidate
17.02.2015 13:48:46(G)

C:\ ping 70.42.6.250

Pinging 70.42.6.250 with 32 bytes of data:
Reply from 70.42.6.250: bytes=32 time=135ms TTL=47
Reply from 70.42.6.250: bytes=32 time=132ms TTL=47
Reply from 70.42.6.250: bytes=32 time=135ms TTL=47
Reply from 70.42.6.250: bytes=32 time=133ms TTL=47

Ping statistics for 70.42.6.250:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 132ms, Maximum = 135ms, Average = 133ms


#12

i have a radarcape too however i dont have a problem the flight aware feeder, I have had a problem in the past with the fr24 feeder stats stopping.

I have worked it out to be a DNS issue with the angstrom on the beaglebone. One of the updates to the kernel can break something to do with dns settings in connman (opkh update etc…) doesnt effect everyone, google slow DNS lookup on a beagle bone.

When i had the problem the DNS lookup is very slow but does work and sometimes didn’t work.

I made things a lot better by setting the Ethernet to be manual.

http://derekmolloy.ie/set-ip-address-to-be-static-on-the-beaglebone-black/

something to look at maybe.


#13

Peter, your radarcape shows offline for several hours, is that accurate or part of this problem? Looking at it now and the graph is rather odd.


#14

It does the samething on my Radarcape FA feed since the last radarcape software update.
On the FA user stats page. it will show Online and Offline throughout the day.
Looking at the upload FA page on the radarcape box. It’s uploading every minute.
Not sure where the problem is.

It only does it on the FA feed. The other feeds are fine.


#15

That is part of the problem, Site 5987 - EGLF is on H24. The PP feed to FA (Site 178) originates from the same Radarcape.


#16

Peter, can you confirm if the problem was tied to a software update? When was your last software update installed? Perhaps we can correlate it with the stats.


#17

Started 02.02.15 Site identifier: d0:5f:b8:fc:fc:95 and on 18.02.15 Site identifier: bc:6a:29:85:c3:70 both with new firmware.


#18

Peter, do you know on which days you applied the firmware?


#19

For bc:6a:29:85:c3:70 was definately 18.02.15 and almost certainly 02.02.15 for the other.


#20

Everything appears okay on our side – perhaps we should involve Günter?