FlightAware Pro Stick Plus loses USB connection


#1

FlightAware Pro Stick Plus loses USB connection – any ideas?

changes made around the same time 1) move to a hotter location 2) added feed to FR24 and Planefinder.

ul 24 08:17:01 raspberrypi CRON[7714]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Jul 24 09:17:01 raspberrypi CRON[8071]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Jul 24 10:17:01 raspberrypi CRON[8426]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Jul 24 11:17:01 raspberrypi CRON[8778]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Jul 24 12:17:01 raspberrypi CRON[9099]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Jul 24 13:17:01 raspberrypi CRON[9453]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Jul 24 14:17:01 raspberrypi CRON[9805]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Jul 24 15:17:01 raspberrypi CRON[10122]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Jul 24 15:37:50 raspberrypi systemd[1]: Starting Daily apt download activities…
Jul 24 15:37:53 raspberrypi systemd[1]: Started Daily apt download activities.
Jul 24 15:37:53 raspberrypi systemd[1]: apt-daily.timer: Adding 8h 19min 42.860705s random time.
Jul 24 15:37:53 raspberrypi systemd[1]: apt-daily.timer: Adding 8h 30min 25.543423s random time.
Jul 24 16:17:01 raspberrypi CRON[10521]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Jul 24 17:14:35 raspberrypi kernel: [87084.524834] usb 1-1.1.2: usbfs: usb_submit_urb returned -121
Jul 24 17:14:35 raspberrypi kernel: [87084.525119] usb 1-1.1.2: usbfs: usb_submit_urb returned -121
Jul 24 17:14:35 raspberrypi kernel: [87084.525366] usb 1-1.1.2: usbfs: usb_submit_urb returned -121
.
.
.
Jul 24 17:14:35 raspberrypi kernel: [87084.528857] usb 1-1.1.2: usbfs: usb_submit_urb returned -121
Jul 24 17:14:35 raspberrypi kernel: [87084.529205] usb 1-1.1.2: usbfs: usb_submit_urb returned -121
Jul 24 17:14:35 raspberrypi dump1090-fa[4758]: cb transfer status: 1, canceling…
Jul 24 17:14:35 raspberrypi kernel: [87084.529548] usb 1-1.1.2: usbfs: usb_submit_urb returned -121
Jul 24 17:14:35 raspberrypi kernel: [87084.529787] usb 1-1.1.2: usbfs: usb_submit_urb returned -121
Jul 24 17:14:35 raspberrypi kernel: [87084.530041] usb 1-1.1.2: usbfs: usb_submit_urb returned -121
.
.
.
Jul 24 17:14:35 raspberrypi kernel: [87084.560607] usb 1-1.1.2: usbfs: usb_submit_urb returned -121
Jul 24 17:14:35 raspberrypi kernel: [87084.560860] usb 1-1.1.2: usbfs: usb_submit_urb returned -121
Jul 24 17:14:35 raspberrypi kernel: [87084.561106] usb 1-1.1.2: usbfs: usb_submit_urb returned -121
Jul 24 17:14:35 raspberrypi kernel: [87084.561317] usb 1-1.1.2: USB disconnect, device number 8
Jul 24 17:14:35 raspberrypi dump1090-fa[4758]: weirdness: rtlsdr gave us a block with an unusual size (got 0 bytes, expected 262144 bytes)
Jul 24 17:14:35 raspberrypi dump1090-fa[4758]: weirdness: rtlsdr gave us a block with an unusual size (got 0 bytes, expected 262144 bytes)
Jul 24 17:14:35 raspberrypi dump1090-fa[4758]: weirdness: rtlsdr gave us a block with an unusual size (got 0 bytes, expected 262144 bytes)
.
.
.
Jul 24 17:14:35 raspberrypi dump1090-fa[4758]: weirdness: rtlsdr gave us a block with an unusual size (got 0 bytes, expected 262144 bytes)
Jul 24 17:14:35 raspberrypi dump1090-fa[4758]: weirdness: rtlsdr gave us a block with an unusual size (got 0 bytes, expected 262144 bytes)
Jul 24 17:14:35 raspberrypi kernel: [87084.869202] usb 1-1.1.2: new high-speed USB device number 9 using dwc_otg
Jul 24 17:14:35 raspberrypi kernel: [87085.020711] usb 1-1.1.2: New USB device found, idVendor=0bda, idProduct=2832
Jul 24 17:14:35 raspberrypi kernel: [87085.020727] usb 1-1.1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jul 24 17:14:35 raspberrypi kernel: [87085.020736] usb 1-1.1.2: Product: RTL2832U
Jul 24 17:14:35 raspberrypi kernel: [87085.020744] usb 1-1.1.2: Manufacturer: Realtek
Jul 24 17:14:35 raspberrypi kernel: [87085.020752] usb 1-1.1.2: SerialNumber: 00001000
Jul 24 17:14:35 raspberrypi kernel: [87085.028128] usb 1-1.1.2: dvb_usb_v2: found a ‘Realtek RTL2832U reference design’ in warm state
Jul 24 17:14:35 raspberrypi kernel: [87085.081583] usb 1-1.1.2: dvb_usb_v2: will pass the complete MPEG2 transport stream to the software demuxer
Jul 24 17:14:35 raspberrypi kernel: [87085.081645] dvbdev: DVB: registering new adapter (Realtek RTL2832U reference design)
Jul 24 17:14:35 raspberrypi kernel: [87085.088142] i2c i2c-3: Added multiplexed i2c bus 4
Jul 24 17:14:35 raspberrypi kernel: [87085.088156] rtl2832 3-0010: Realtek RTL2832 successfully attached
Jul 24 17:14:35 raspberrypi kernel: [87085.088218] usb 1-1.1.2: DVB: registering adapter 0 frontend 0 (Realtek RTL2832 (DVB-T))…
Jul 24 17:14:35 raspberrypi kernel: [87085.088443] r820t 4-001a: creating new instance
Jul 24 17:14:35 raspberrypi kernel: [87085.095304] r820t 4-001a: Rafael Micro r820t successfully identified
Jul 24 17:14:35 raspberrypi kernel: [87085.106769] Registered IR keymap rc-empty
Jul 24 17:14:35 raspberrypi kernel: [87085.106899] rc rc0: Realtek RTL2832U reference design as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.2/rc/rc0
Jul 24 17:14:35 raspberrypi kernel: [87085.107103] input: Realtek RTL2832U reference design as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.2/rc/rc0/input8
Jul 24 17:14:35 raspberrypi kernel: [87085.108862] input: MCE IR Keyboard/Mouse (dvb_usb_rtl28xxu) as /devices/virtual/input/input9
Jul 24 17:14:35 raspberrypi kernel: [87085.109883] rc rc0: lirc_dev: driver ir-lirc-codec (dvb_usb_rtl28xxu) registered at minor = 0
Jul 24 17:14:35 raspberrypi kernel: [87085.109901] usb 1-1.1.2: dvb_usb_v2: schedule remote query interval to 200 msecs
Jul 24 17:14:35 raspberrypi kernel: [87085.122312] usb 1-1.1.2: dvb_usb_v2: ‘Realtek RTL2832U reference design’ successfully initialized and connected
Jul 24 17:14:35 raspberrypi mtp-probe: checking bus 1, device 9: “/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.2”
Jul 24 17:14:35 raspberrypi mtp-probe: bus: 1, device: 9 was not an MTP device
Jul 24 17:14:36 raspberrypi systemd-udevd[10891]: Process ‘/usr/sbin/th-cmd --socket /var/run/thd.socket --passfd --udev’ failed with exit code 1.
Jul 24 17:14:36 raspberrypi systemd-udevd[10893]: Process ‘/usr/sbin/th-cmd --socket /var/run/thd.socket --passfd --udev’ failed with exit code 1.
Jul 24 17:14:36 raspberrypi systemd-udevd[10899]: Process ‘/usr/sbin/th-cmd --socket /var/run/thd.socket --passfd --udev’ failed with exit code 1.
Jul 24 17:14:36 raspberrypi dump1090-fa[4758]: Tue Jul 24 17:14:36 2018 CDT No data received from the SDR for a long time, it may have wedged
Jul 24 17:15:36 raspberrypi dump1090-fa[4758]: Tue Jul 24 17:15:36 2018 CDT No data received from the SDR for a long time, it may have wedged
Jul 24 17:16:37 raspberrypi dump1090-fa[4758]: Tue Jul 24 17:16:37 2018 CDT No data received from the SDR for a long time, it may have wedged
Jul 24 17:17:01 raspberrypi CRON[10917]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Jul 24 17:17:37 raspberrypi dump1090-fa[4758]: Tue Jul 24 17:17:37 2018 CDT No data received from the SDR for a long time, it may have wedged
Jul 24 17:18:37 raspberrypi dump1090-fa[4758]: Tue Jul 24 17:18:37 2018 CDT No data received from the SDR for a long time, it may have wedged
Jul 24 17:18:37 raspberrypi systemd[1]: Starting Cleanup of Temporary Directories…
Jul 24 17:18:37 raspberrypi systemd[1]: Started Cleanup of Temporary Directories.
Jul 24 17:19:37 raspberrypi dump1090-fa[4758]: Tue Jul 24 17:19:37 2018 CDT No data received from the SDR for a long time, it may have wedged
Jul 24 17:20:38 raspberrypi dump1090-fa[4758]: Tue Jul 24 17:20:38 2018 CDT No data received from the SDR for a long time, it may have wedged
Jul 24 17:21:38 raspberrypi dump1090-fa[4758]: Tue Jul 24 17:21:38 2018 CDT No data received from the SDR for a long time, it may have wedged
.
.
.
Jul 24 17:31:40 raspberrypi dump1090-fa[4758]: Tue Jul 24 17:31:40 2018 CDT No data received from the SDR for a long time, it may have wedged
Jul 24 17:32:40 raspberrypi dump1090-fa[4758]: Tue Jul 24 17:32:40 2018 CDT No data received from the SDR for a long time, it may have wedged
Jul 24 17:33:10 raspberrypi dump1090-fa[4758]: Tue Jul 24 17:33:10 2018 CDT Caught SIGTERM, shutting down…
Jul 24 17:33:10 raspberrypi systemd[1]: Stopping dump1090 ADS-B receiver (FlightAware customization)…
Jul 24 17:33:10 raspberrypi dump1090-fa[4758]: Tue Jul 24 17:33:10 2018 CDT Waiting for receive thread termination
Jul 24 17:34:40 raspberrypi systemd[1]: dump1090-fa.service: State ‘stop-sigterm’ timed out. Killing.
Jul 24 17:34:40 raspberrypi systemd[1]: dump1090-fa.service: Killing process 4758 (dump1090-fa) with signal SIGKILL.
Jul 24 17:34:40 raspberrypi systemd[1]: dump1090-fa.service: Main process exited, code=killed, status=9/KILL
Jul 24 17:34:40 raspberrypi systemd[1]: Stopped dump1090 ADS-B receiver (FlightAware customization).
Jul 24 17:34:40 raspberrypi systemd[1]: dump1090-fa.service: Unit entered failed state.
Jul 24 17:34:40 raspberrypi systemd[1]: dump1090-fa.service: Failed with result ‘timeout’.
Jul 24 17:34:40 raspberrypi systemd[1]: Started dump1090 ADS-B receiver (FlightAware customization).
Jul 24 17:34:40 raspberrypi dump1090-fa[11061]: Tue Jul 24 17:34:40 2018 CDT dump1090-fa 3.5.3 starting up.
Jul 24 17:34:40 raspberrypi dump1090-fa[11061]: rtlsdr: using device #0: Generic RTL2832U (Realtek, RTL2832U, SN 00001000)
Jul 24 17:34:40 raspberrypi dump1090-fa[11061]: Detached kernel driver
Jul 24 17:34:40 raspberrypi kernel: [88289.811741] r820t 4-001a: destroying instance
Jul 24 17:34:40 raspberrypi kernel: [88289.812716] dvb_usb_v2: ‘Realtek RTL2832U reference design:1-1.1.2’ successfully deinitialized and disconnected
Jul 24 17:34:40 raspberrypi dump1090-fa[11061]: Found Rafael Micro R820T tuner
Jul 24 17:34:41 raspberrypi dump1090-fa[11061]: rtlsdr: enabling tuner AGC
Jul 24 17:34:55 raspberrypi systemd[1]: Stopping FlightAware ADS-B uploader…
Jul 24 17:34:56 raspberrypi systemd[1]: Stopped FlightAware ADS-B uploader.
Jul 24 17:34:56 raspberrypi systemd[1]: Started FlightAware ADS-B uploader.
Jul 24 17:41:25 raspberrypi systemd[1]: Started Session c5 of user pi.


#2

most likely culprits: low voltage or a loose usb connection.


#3

Bad power supplies are the biggest cause of problems with piaware.
From crashes to USB problems.
Make sure you have a quality 2.5 amp usb power supply.


#4

Thanks that fixes it - power supply fixed