I just received my brand new Pro Stick Plus. I removed the Pro Stick (Orange) and filter and replaced it with the Pro Stick Plus (Blue). I did this on a Raspberry Pi 3 B and I am running PiAware 3.5 on it. I of course removed power during the swap. Now nothing is working. No planes appear on the dump1090 map and according to FlighAware my MLAT is off. So, I put everything back the way it was and all is good again. I want to be able to use the Pro Stick Plus. What am I doing wrong?
Thanks
What you did should work fine. Check your power supply. Is the red power LED on the Pi 3 solidly on?
Yes it is a steady red. And there is an ongoing error on my My ADS-B page with the gear on it:
[2017-07-12 15:05 CDT] no ADS-B data program seen listening on port 30005 for 131 seconds, next check in 60s
[2017-07-12 15:06 CDT] no ADS-B data program is serving on port 30005, not starting multilateration client yet
Ok, so it’s not obviously bad power.
Those log entries mean dump1090 is not starting correctly for some reason. You can try a few commands from the command line to try to diagnose it further:
sudo systemctl status dump1090-fa -l
sudo journalctl -u dump1090-fa
lsusb
dmesg | grep usb
Results:
sudo systemctl status dump1090-fa -l
pi@piaware:~$ sudo systemctl status dump1090-fa -l
● dump1090-fa.service - dump1090 ADS-B receiver (FlightAware customization)
Loaded: loaded (/lib/systemd/system/dump1090-fa.service; enabled)
Active: activating (auto-restart) (Result: exit-code) since Wed 2017-07-12 15:50:55 CDT; 4s ago
Docs: flightaware.com/adsb/piaware/
Process: 1121 ExecStart=/usr/bin/dump1090-fa $RECEIVER_OPTIONS $DECODER_OPTIONS $NET_OPTIONS $JSON_OPTIONS $PIAWARE_DUMP1090_LOCATION_OPTIONS --write-json /run/dump1090-fa --quiet (code=exited, status=1/FAILURE)
Main PID: 1121 (code=exited, status=1/FAILURE)
Jul 12 15:50:55 piaware systemd[1]: Unit dump1090-fa.service entered failed state.
sudo journalctl -u dump1090-fa
pi@piaware:~$ sudo journalctl -u dump1090-fa
– Logs begin at Wed 2017-07-12 15:17:01 CDT, end at Wed 2017-07-
Jul 12 15:17:09 piaware systemd[1]: Starting dump1090 ADS-B recei
Jul 12 15:17:09 piaware systemd[1]: Started dump1090 ADS-B receiv
Jul 12 15:17:09 piaware dump1090-fa[538]: Wed Jul 12 15:17:09 201
Jul 12 15:17:09 piaware dump1090-fa[538]: rtlsdr: no supported de
Jul 12 15:17:09 piaware systemd[1]: dump1090-fa.service: main pro
Jul 12 15:17:09 piaware systemd[1]: Unit dump1090-fa.service ente
Jul 12 15:48:50 piaware systemd[1]: Stopping dump1090 ADS-B recei
Jul 12 15:48:50 piaware systemd[1]: Starting dump1090 ADS-B recei
Jul 12 15:48:50 piaware systemd[1]: Started dump1090 ADS-B receiv
Jul 12 15:48:50 piaware dump1090-fa[832]: Wed Jul 12 15:48:50 201
Jul 12 15:48:50 piaware dump1090-fa[832]: rtlsdr: no supported de
Jul 12 15:48:50 piaware systemd[1]: dump1090-fa.service: main pro
Jul 12 15:48:50 piaware systemd[1]: Unit dump1090-fa.service ente
Jul 12 15:49:20 piaware systemd[1]: dump1090-fa.service holdoff t
Jul 12 15:49:20 piaware systemd[1]: Stopping dump1090 ADS-B recei
Jul 12 15:49:23 piaware systemd[1]: Starting dump1090 ADS-B recei
Jul 12 15:49:23 piaware systemd[1]: Started dump1090 ADS-B receiv
Jul 12 15:49:23 piaware dump1090-fa[897]: Wed Jul 12 15:49:23 201
Jul 12 15:49:23 piaware dump1090-fa[897]: rtlsdr: no supported de
Jul 12 15:49:23 piaware systemd[1]: dump1090-fa.service: main pro
Jul 12 15:49:23 piaware systemd[1]: Unit dump1090-fa.service ente
Jul 12 15:49:53 piaware systemd[1]: dump1090-fa.service holdoff t
lsusb
pi@piaware:~$ lsusb
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
dmesg | grep usb
0.155610] usbcore: registered new interface driver usbfs
0.155691] usbcore: registered new interface driver hub
0.155780] usbcore: registered new device driver usb
1.106891] usbcore: registered new interface driver smsc95xx
1.535903] dwc_otg 3f980000.usb: DWC OTG Controller
1.535937] dwc_otg 3f980000.usb: new USB bus registered, assigned bus number 1
1.535970] dwc_otg 3f980000.usb: irq 62, io mem 0x00000000
1.536215] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
1.536225] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
1.536233] usb usb1: Product: DWC OTG Controller
1.536241] usb usb1: Manufacturer: Linux 4.9.35-v7+ dwc_otg_hcd
1.536249] usb usb1: SerialNumber: 3f980000.usb
1.538040] usbcore: registered new interface driver usb-storage
1.545444] usbcore: registered new interface driver usbhid
1.545448] usbhid: USB HID core driver
1.954298] usb 1-1: new high-speed USB device number 2 using dwc_otg
2.184507] usb 1-1: New USB device found, idVendor=0424, idProduct=9514
2.184518] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
2.504299] usb 1-1.1: new high-speed USB device number 3 using dwc_otg
2.634561] usb 1-1.1: New USB device found, idVendor=0424, idProduct=ec00
2.634575] usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
2.728236] smsc95xx 1-1.1:1.0 eth0: register 'smsc95xx' at usb-3f980000.usb-1.1, smsc95xx USB 2.0 Ethernet, b8:27:eb:a8:f9:4e
2.824261] usb 1-1.5: new full-speed USB device number 4 using dwc_otg
2.924275] usb 1-1.5: device descriptor read/64, error -32
3.144274] usb 1-1.5: device descriptor read/64, error -32
3.364324] usb 1-1.5: new full-speed USB device number 5 using dwc_otg
3.464260] usb 1-1.5: device descriptor read/64, error -32
3.684262] usb 1-1.5: device descriptor read/64, error -32
3.904237] usb 1-1.5: new full-speed USB device number 6 using dwc_otg
4.344232] usb 1-1.5: device not accepting address 6, error -32
4.444234] usb 1-1.5: new full-speed USB device number 7 using dwc_otg
4.884234] usb 1-1.5: device not accepting address 7, error -32
4.884472] usb 1-1-port5: unable to enumerate USB device
17.898277] usbcore: registered new interface driver brcmfmac
pi@piaware:~$
Ok, that is most likely either a bad USB connection (try a different USB port on the Pi?) or a faulty dongle.
It might still be bad power, so you might want to try a different power supply if you have a spare, but usually marginal power would manifest in other ways.
Ok, I will move it to a different port in the morning and let you know. Meanwhile can you get me of off the Antenna in the attic issue. I don’t need to do that one, lol. I just got another email for it…
I guess you mean the forum emails? You can manage them in the user control panel here: ucp.php?i=main&mode=subscribed
Actually, I am using the same port that the Orange Pro Stick works in, so it isn’t the port on the Raspberry Pi or I would have issues with it, too. How do I get a replacement that does work?
If it is a mechanical issue this is not necessarily true, the connectors may be slightly different. Try a different port anyway?
How do I get a replacement that does work?
Organize this with whereever you bought it through. There should be no problem returning a faulty item.
Ok I moved it and as I expected, it isn’t the port. The results are the same. Also, Amazon has a bad batch of these. Reading the reviews NSY 3 17 do not work. I really don’t want a 3rd one from them! They are inexpensive so rather than messing with a return, I just bought another one. Both are from the same batch and neither work! I need a better solution from you.
If you don’t return it as faulty then we can’t tell
a) whether it is a fault with the dongle or something specific to your setup (we need the faulty prostick back to be able to test it);
b) whether there is any pattern to faults (generally we get very few faulty returns)
So the better solution is “return the faulty dongle”, not “buy another one”.
I have a 3/17 too and two DOAs is very unlikely. A -32 is not as clear as a -110 USB read error but is very likely to be power related. Do you have a USB cable between the dongle and the Raspberry PI (suspect #1)? Have you tried a different power supply - can be anything, even a 12W Apple power supply + micro USB cable or an high amp power bank (suspect #2)?
Last resort, but often a permanent solution: power off the Pi, disconnect everything and let it cool down for 5 minutes. After that: plug everything back in and start the Pi again.
Thanks, I’ll give those ideas a try.
The 5 minute idea made no difference. I don’t have a cable between the dongle and the Pi. I have no 2.5 A power supplies with a micro USB cable end on it. I can get a 2.5 A power supply with the correct connector on it but I don’t like the idea of spending $23.00 to make a $16.00 device work.
My Pro Stick Plus v1.0.0 appears to have failed. 
In fact, it failed back in May of this year but I was too busy to notice (no alert from FlightAware!). It had stopped communicating with FlightAware and showed no dump1090 messages per second on the Skyview local web page. So the question is: how do I get a refund? Although I bought it from Amazon, it’s a FlightAware product.
You are probably outside the Amazon return window now.
I’d check your power first though - most of the “failed” dongles seen on the forums were fixed by swapping out the power supply.
This has happened with me also. Couple of months after I started using ProStick with my Pi, the setup failed, giving all symptoms of “dongle” failure. Swaping USB port will not make a difference.
Luckily on my Windows desktop, I had RTL1090 and dvb-t driver (zadig) already installed since the time when I did not have a Pi, and using desktop instead. I removed the ProStick from Pi and plugged it into Windows Desktop, and the ProStick worked perfectly well.
Once established that ProStick is not faulty, I replaced the other prime suspect: Pi’s existing 2.5 Amps power supply by a new 3 Amps power supply, and my system started working normal.
My original Pi power supply was a 2.0 amp. I did find a reasonably priced 2.5 amp and bought it. I plugged in the Pro Stick Plus and still failed to work. I was within Amazon’s window so both of them went back for credit. I give up on the blue one and am still using the orange one without issues. Since I am hardly the only one with this issue, I might try a Plus again at some future date. I want it to work on the Pi so I don’t have to leave a PC running all the time. These clearly have some power issues.
I successfully use:
ProStick(orange)+Pi
AND
ProStickPlus(blue)+Pi
Both Pis have power supplies switching type, rated 3 Amps
Dongle plugged directly into Pi (no usb cable), Power supply cable 1 meter only, No PoE