- RaspberryPi Model 2 B+
- Pro Stick Plus dongle (PSP)
- 1090Mhz Antenna MCX
- Powered USB2.0 Hub for the PSP
- Edimax Wifi dongle plugged into the pi’s onboard USB
- 2.5a PSU on the pi
- Piaware via the Debian package add-on
- No other devices, attached, no other apps or programs in use besides SSH
Setup went smoothly, and the system reported steadily for a few days: https://flightaware.com/adsb/stats/user/digittante
Now, it seems, the PSP is non-responsive, and knocks out the wifi dongle as well. The system will boot and connect to flightaware.com w/o the PSP attached, but not with. Same results whether I (1) plug the PSP directly into the pi USB and the wifi into the 2nd hub, (2) plug both the PSP and wifi into the pi USB, (3) use a 3a PSU on the pi, (4) set max_usb_current=1 in the pi’s /boot/config.txt, (5) boot w/ latest Piaware OS build, (6) replace the wifi dongle with another.
W/o the PSP attached, Piaware status yields:
PiAware master process (piaware) is running with pid 472.
PiAware ADS-B client (faup1090) is not running.
PiAware mlat client (fa-mlat-client) is not running.
Local ADS-B receiver (dump1090) is not running.
no program appears to be listening for connections on port 30005.
faup1090 is NOT connected to the ADS-B receiver.
piaware is connected to FlightAware.
got 'couldn’t open socket: connection refused’
dump1090 is NOT producing data on localhost:30005.