Hello, I am running flightradar24 software on raspbian stretch (not flightradar image). I posted here since I’d like all the help I can get. My USB dongle seems to disconnect. What I also find is that it only tracks flight for the first few seconds on boot up. Here is when i plug in the dongle + errors:
`[12006.577233] usb 1-1.3: new high-speed USB device number 80 using dwc_otg
[12006.718840] usb 1-1.3: New USB device found, idVendor=0bda, idProduct=2838
[12006.718856] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[12006.718865] usb 1-1.3: Product: RTL2838UHIDIR [12006.718874] usb 1-1.3: Manufacturer: Realtek [12006.718883] usb 1-1.3: SerialNumber: 00000001 [12006.726248] usb 1-1.3: dvb_usb_v2: found a ‘Realtek RTL2832U reference design’ in warm state
[12006.785622] usb 1-1.3: dvb_usb_v2: will pass the complete MPEG2 transport stream to the software demuxer [12006.785686] dvbdev: DVB: registering new adapter (Realtek RTL2832U reference design)
[12006.793717] i2c i2c-3: Added multiplexed i2c bus 4
[12006.794020] r820t 4-001a: creating new instance
[12006.800889] r820t 4-001a: Rafael Micro r820t successfully identified
[12006.812495] Registered IR keymap rc-empty
[12006.812663] rc rc0: Realtek RTL2832U reference design as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3/rc/rc0
[12006.812855] input: Realtek RTL2832U reference design as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3/rc/rc0/input28 [12006.813435] input: MCE IR Keyboard/Mouse (dvb_usb_rtl28xxu) as /devices/virtual/input/input29 [12006.813865] rc rc0: lirc_dev: driver ir-lirc-codec (dvb_usb_rtl28xxu) registered at minor = 0 [12006.813882] usb 1-1.3: dvb_usb_v2: schedule remote query interval to 200 msecs
[12006.827854] usb 1-1.3: dvb_usb_v2: ‘Realtek RTL2832U reference design’ successfully initialized and connected [12007.037974] usb 1-1.3: dvb_usb_v2: rc.query() failed=-71 [12007.049471] usb 1-1.3: USB disconnect, device number 80 [12007.448711] r820t 4-001a: destroying instance [12007.449453] dvb_usb_v2: ‘Realtek RTL2832U reference design:1-1.3’ successfully deinitialized and disconnected [12007.747250] usb 1-1.3: new high-speed USB device number 81 using dwc_otg
[12008.027321] Under-voltage detected! (0x00050005) [12012.187329] Voltage normalised (0x00000000) [12012.927287] usb 1-1.3: device descriptor read/64, error -110 [12028.287390] usb 1-1.3: device descriptor read/64, error -110 [12028.507381] usb 1-1.3: new high-speed USB device number 82 using dwc_otg
[12033.647405] usb 1-1.3: device descriptor read/64, error -110`
Again: `[ 697.209386] usb 1-1.3: reset high-speed USB device number 4 using dwc_otg
[ 697.329354] usb 1-1.3: device descriptor read/64, error -71
[ 697.569350] usb 1-1.3: device descriptor read/64, error -71
[ 697.789354] usb 1-1.3: reset high-speed USB device number 4 using dwc_otg
[ 697.889386] usb 1-1.3: device descriptor read/64, error -71
[ 698.139367] usb 1-1.3: device descriptor read/64, error -71
[ 698.359370] usb 1-1.3: reset high-speed USB device number 4 using dwc_otg
[ 698.809373] usb 1-1.3: device not accepting address 4, error -71
[ 698.909388] usb 1-1.3: reset high-speed USB device number 4 using dwc_otg
[ 699.349370] usb 1-1.3: device not accepting address 4, error -71
[ 699.349631] usb 1-1.3: USB disconnect, device number 4
[ 699.449367] usb 1-1.3: new high-speed USB device number 5 using dwc_otg
[ 699.559369] usb 1-1.3: device descriptor read/64, error -71
[ 699.799363] usb 1-1.3: device descriptor read/64, error -71
[ 700.019387] usb 1-1.3: new high-speed USB device number 6 using dwc_otg
[ 700.129371] usb 1-1.3: device descriptor read/64, error -71
[ 700.359373] usb 1-1.3: device descriptor read/64, error -71
[ 700.479473] usb 1-1-port3: attempt power cycle
[ 701.139375] usb 1-1.3: new high-speed USB device number 7 using dwc_otg
[ 701.609387] usb 1-1.3: device not accepting address 7, error -71
[ 701.709373] usb 1-1.3: new high-speed USB device number 8 using dwc_otg
[ 702.159379] usb 1-1.3: device not accepting address 8, error -71
[ 702.159472] usb 1-1-port3: unable to enumerate USB device
`
It looks like you could have a power problem.
Make sure that you use a quality 2.5 Amp power supply.
The new RPI 3B+ is more susceptible to power issues. I have POE adapters that work fine the RPI3 but not with the RPI 3B+.
I bought a Raspbian Dongle first and had so much trouble with it and few answers I sold it on eBay and just ordered the flight tracker from flight aware. I even tried to use it as a portable one in my car and could not track much of anything. Get an antenna and set it up on the roof in a clear view of the sky no trees or try for the highest point you can get. It may be location, location location is your issue not sure as I do not know the whole story but as I said the Raspbian one I had sucked.
The flight aware one was free and they delivered it with lots of extra cable so I could put it on my chimney. It came super fast with everything you need to operate it.
I dont think so as the previous power supply I had undervoltaged during bootup and normal use several use, this power supply only had 1 undervoltage in over 1000seconds.
Then check again.
But yes it might well be a problem with the power.
Just because your previous dongle did work doesn’t mean much as the new dongle might be using more power.
Are you using an usb extension?
Also try another usb port.
Nothing wrong with my OS, its the USB dongle. My Raspberry Pi receives enough power, i showed the dmesg output above, it recognizes it at first, but then it drops off after 600+ secs
There are a bunch or already posted answers on here for Dongle issues but if it is not a power issue then most likely it is an SD card issue. If you get some packets but not a lot of them then that’s probably an antenna issue but if your not getting anything then it is most likely power or SD card. If it is a RF issue you will still get some packets thru.It is
Definitely not a SD card issue, I can access the the OS fine. I receive a link at the start of boot, I don’t know why it after that no aircraft are found.
Ok then that leaves only about one thing and that’s the WIFI connection. If it fires up sends a good signal and then the signal drops my best guess is the WIFI is dropping out of it for some reason…