Changing ADS-B receivers

I’ve been using the DVB ADS-B Recceiver with the MCX Female. I’m looking at replacing it with the Flightaware Prostick with the filter. Has anyone tried this?

Yes, it is simple. Unplug DVB-T from Pi or computer. and plug-in ProStick. The filter preferably directly connected to ProStic.

I had 2 Pis with DVB-T, and on one of these I replaced DVB-T by ProStick+Filter. You will need a pigtail or adaptor with SMA-male connector to connect the antenna to filter.

Please see photos of my setup. From antenna to receiver, I use RG6 coax with F adaptor, hence I use F to SMA pigtail. You will require pigtail/adaptor according to your coax cable.

F-female to SMA-male Pigtail RG316 20cm from eBay.ca
Be careful. Dont purchase RP-SMA male. It looks like SMA male, but if you look carefully, you will find it does not have a center pin.
Dont purchase any pigtail which says “wifi” or “wlan”, as these use the RP-SMA.

This is the best value for money setup I have come across.
Search the forums for optimising the dongle gain. I had to reduce mine to get the best results. Every system is unique and requires testing.

As abcd567 has stated, be careful with the SMA connectors. Don’t confuse them with SMA-RP or F connectors.

RPI2 and 3s require good quality 2.0-2.5Amp Power supplies(or POEs).
If you use USB pigtails, you may consider adding inexpensive RF chokes.

Awesome info. I’ve ordered the parts. I’m hoping I’ll get a boost. Thanks guys.

@eprn1n2

The FA Antenna+FA Filter+ProStic is the best option I have used up to now.

I have 2 setups. Please see the photo of my setup, which I have posted in my post above.

My stats show the FA combo gives much better performance: Message rate 182%, Plane count 114%

Pi-1: Cantenna + 12 ft RG6 Coax + 12 inch RG316 pigtail + Black DVB-T (No Amplifier) >> plugged directly into OPi PC
Pi-2: FA Antenna + 4 ft RG6 Coax + 4 inch RG316 pigtail + FA Filter + ProStick >> plugged directly into RPi Model2

Note:
(1) Both antennas are at same location in same vertical line. Horizontal distance = 0, Vertical distance = 1 m / 3 ft
(2) There is NO AMPLIFIER with Cantenna + Generic DVB-T, while ProStick has a built-in RF amplifier.

Nice to have the data! I have an antenna on my roof so I should get the same increase. Thanks.

I too have changed the USB Stick/Receiver to a FlightAware Stick but no joy 8-(

In my log:

[2016-07-29 15:11 BST] autoUpdate is not set in adept config, looking further…
[2016-07-29 15:11 BST] autoUpdate in /etc/piaware is enabled, allowing update
[2016-07-29 15:11 BST] manualUpdate is not set in adept config, looking further…
[2016-07-29 15:11 BST] manualUpdate in /etc/piaware is enabled, allowing update
[2016-07-29 15:11 BST] multilateration support enabled (use piaware-config to disable)
[2016-07-29 15:11 BST] multilateration support enabled (use piaware-config to disable)
[2016-07-29 15:11 BST] multilateration data requested, enabling mlat client
[2016-07-29 15:11 BST] Starting multilateration client: /usr/lib/piaware/helpers/fa-mlat-client --input-connect localhost:30005 --results beast,connect,localhost:30104 --udp-transport 70.42.6.191:9455:3823725717
[2016-07-29 15:11 BST] mlat(926): fa-mlat-client 0.2.4 starting up
[2016-07-29 15:11 BST] mlat(926): Using UDP transport to 7*.4*.6.19*:9455 (My asterix)
[2016-07-29 15:11 BST] mlat(926): Input connected to localhost:30005
[2016-07-29 15:11 BST] mlat(926): Beast-format results connection with localhost:30104: connection established
[2016-07-29 15:11 BST] 0 msgs recv’d from dump1090 (0 in last 1m); 0 msgs sent to FlightAware
[2016-07-29 15:13 BST] mlat(926): Disconnecting from localhost:30005: No data (not even keepalives) received for 150 seconds
[2016-07-29 15:13 BST] mlat(926): Input connected to localhost:30005
[2016-07-29 15:16 BST] mlat(926): Disconnecting from localhost:30005: No data (not even keepalives) received for 150 seconds
[2016-07-29 15:16 BST] mlat(926): Input connected to localhost:30005
[2016-07-29 15:16 BST] 0 msgs recv’d from dump1090 (0 in last 5m); 0 msgs sent to FlightAware

I cannot hook up to port:8080 - it just hangs. It’s as if the wifi is not connecting?

Change back to the NooElec.com stick and everything is fine.

Mystified … no doubt I’ve missed a trick. Any thoughts?

Kind Regards

Hugh

Which nooelec dongle? Most use the MCX connector (except the latest).

Make sure your pigtail is SMA not SMA-RP.
See this post for the difference.
post196305.html?hilit=SMA#p196305

It looks like you are getting no traffic from dump1090

I’ve made this mistake before - but it’s a direct replacement for the Nooelec which works perfectly.

The connector on both sticks is identical.

I really appreciate your help and I will double check.

Kind Regards

Hugh

Could it be a power issue I wonder? I’m using a direct micro USB connection from an iMac …

Hugh

Theoretically, USB ports will only supply 500mA so yes, quite possibly a power issue.

Most USB ports only put out less than an amp.
RPIs need 2-2.5Amps. The FA dongle does use more power than others. I think it reserves 500ma and the others request 250ma.

check lsusb and dmesg

I’m convinced it’s a power issue: I’ve always had trouble ‘firing’ the system up. It often takes many attempts before everything works. I’m powering from a USB port on my iMac …

The FlightAware stick takes more power than the Nooelec so I’m told. So: new beefy PSU on order.

Kind Regards

Hugh

Still foxed!

Beefy PSU in place. Raspberry pi fired, connection established but zero messages. Cannot connect via port :8080 - it just hangs

mlat(925): fa-mlat-client 0.2.4 starting up
[2016-07-31 09:39 BST] mlat(925): Using UDP transport to 70.42.6.197:8463
[2016-07-31 09:39 BST] mlat(925): Input connected to localhost:30005
[2016-07-31 09:39 BST] mlat(925): Beast-format results connection with localhost:30104: connection established
[2016-07-31 09:40 BST] 0 msgs recv’d from dump1090 (0 in last 1m); 0 msgs sent to FlightAware
[2016-07-31 09:42 BST] mlat(925): Disconnecting from localhost:30005: No data (not even keepalives) received for 150 seconds
[2016-07-31 09:42 BST] mlat(925): Input connected to localhost:30005

Mystified! If it was purely an antenna issue I’d still be able to access port :8080 I think

Hugh

You are using a browser to connect to port 8080, right? If you just try to connect there with netcat/telnet etc, it will sit there waiting for a HTTP request from you.

If you run dump1090 from the commandline (e.g. “dump1090 --gain -10 --net”) after stopping the currently running copy, what does it tell you?

My apologies if I haven’t quite understood … and really most grateful for your help!

One DVB-T stick works fine, the other doesn’t …

Kind Regards

Hugh

The orange plastic, depending on your Pi case, sometimes stops the usb stick seating properly - can you temporarily remove the pi case?

Right - I will!

Many thanks

Hugh

UPDATE No change 8-(

UPDATE 2 Just read this: flightaware.com/adsb/prostick/setup/

Filter on order

him

Update**

Filter fitted. No change: 0 msgs received and still unable to access :8080

Could the FA USB stick be duff?

Nooelec still runs well.

Kind Regards

Hugh

No joy. Both Pro Stick and Band pass Filter are now up for sale on eBay (soon).

**Official PSU from Pi and all is running: Pi3/3.5" touch screen display/ProStick. No filter needed so far …

Thank you for all your help and advice.

Hugh