# Piaware not working **URL:** \ **Category:** ADS-B Flight Tracking\ **Created:** [June 27, 2017, 3:51am UTC](https://discussions.flightaware.com/t/piaware-not-working/20196 "2017-06-27T03:51:52Z")\ **Posts on this page:** 14\ **Page:** 1
**Author:** ![MarcusMartinez](https://avatars.discourse-cdn.com/v4/letter/m/9fc348/32.png) [@MarcusMartinez](https://discussions.flightaware.com/u/MarcusMartinez)\ **Post date:** [June 27, 2017, 3:51am UTC](https://discussions.flightaware.com/t/piaware-not-working/20196/1 "2017-06-27T03:51:52Z")
Dont know what happened but for whatever reason it seems to just not feed anymore but for a few minutes, made a new one from scratch took it to work and it fine bring it home after a few minutes it stops again… I dont get it. Marcus ---
**Author:** ![abcd567](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/abcd567/32/113769_2.png) [@abcd567](https://discussions.flightaware.com/u/abcd567)\ **Post date:** [June 27, 2017, 4:51am UTC](https://discussions.flightaware.com/t/piaware-not-working/20196/2 "2017-06-27T04:51:55Z")
Test Piaware: ```auto sudo systemctl status piaware -l ``` Test dump1090-fa: ```auto sudo systemctl status dump1090-fa -l ``` Test the DVB-T: ```auto lsusb sudo systemctl stop dump1090-fa rtl_test ``` ---
**Author:** ![tdrane](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/tdrane/32/10967_2.png) [@tdrane](https://discussions.flightaware.com/u/tdrane)\ **Post date:** [June 27, 2017, 12:45pm UTC](https://discussions.flightaware.com/t/piaware-not-working/20196/3 "2017-06-27T12:45:04Z")
> [@MarcusMartinez](#): > > took it to work and it fine bring it home after a few minutes it stops again… I dont get it. > Marcus Are you using a different power supply at work? ---
**Author:** ![triggers](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/triggers/32/117248_2.png) [@triggers](https://discussions.flightaware.com/u/triggers)\ **Post date:** [December 3, 2019, 6:31pm UTC](https://discussions.flightaware.com/t/piaware-not-working/20196/4 "2019-12-03T18:31:28Z")
Digging out an old post. My brother’s system [https://uk.flightaware.com/adsb/stats/user/triggers#stats-15612](https://uk.flightaware.com/adsb/stats/user/triggers#stats-15612) went down on 22 November so I asked him to run some tests. Not sure what he did but managed to chop off the ends of some of the error messages. If you can help, I’d appreciate it. I’ve got him to change the orange dongle and check all connections. Software hasn’t changed since the 3.7.2 upgrade. It looks as though the feeder was checking in to the Flightaware servers but not reporting any planes. The system is currently disconnected as he is bringing it over to me tomorrow for a complete rebuild. ```auto pi@piaware:~ $ sudo systemctl stop dump1090-fa pi@piaware:~ $ rtl_test -t No supported devices found. pi@piaware:~ $ pi@piaware:~ $ sudo systemctl status piaware -l ● piaware.service - FlightAware ADS-B uploader Loaded: loaded (/lib/systemd/system/piaware.service; enabled; vendor preset: Active: active (running) since Sat 2019-11-23 12:17:09 UTC; 2h 36min ago Docs: https://flightaware.com/adsb/piaware/ Main PID: 355 (piaware) CGroup: /system.slice/piaware.service └─355 /usr/bin/piaware -p /run/piaware/piaware.pid -plainlog -statusf Nov 23 14:51:58 piaware piaware[355]: no ADS-B data program seen listening on po Nov 23 14:52:00 piaware piaware[355]: 0 msgs recv'd from dump1090 (0 in last 5m) Nov 23 14:52:56 piaware sudo[31303]: piaware : TTY=unknown ; PWD=/ ; USER=root Nov 23 14:52:56 piaware sudo[31303]: pam_unix(sudo:session): session opened for Nov 23 14:52:56 piaware sudo[31303]: pam_unix(sudo:session): session closed for Nov 23 14:52:56 piaware piaware[355]: no ADS-B data program is serving on port 3 Nov 23 14:52:58 piaware sudo[31311]: piaware : TTY=unknown ; PWD=/ ; USER=root Nov 23 14:52:58 piaware sudo[31311]: pam_unix(sudo:session): session opened for Nov 23 14:52:58 piaware sudo[31311]: pam_unix(sudo:session): session closed for Nov 23 14:52:58 piaware piaware[355]: no ADS-B data program seen listening on po 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; vendor pres Active: activating (auto-restart) (Result: exit-code) since Sat 2019-11-23 14 Docs: https://flightaware.com/adsb/piaware/ Process: 31481 ExecStart=/usr/share/dump1090-fa/start-dump1090-fa --write-json Main PID: 31481 (code=exited, status=1/FAILURE) Nov 23 14:53:25 piaware systemd[1]: dump1090-fa.service: Unit entered failed sta Nov 23 14:53:25 piaware systemd[1]: dump1090-fa.service: Failed with result 'exi Unit \xe2\x80\x93l.service could not be found. pi@piaware:~ $ ``` ---
**Author:** ![wiedehopf](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/wiedehopf/32/114045_2.png) [@wiedehopf](https://discussions.flightaware.com/u/wiedehopf)\ **Post date:** [December 3, 2019, 6:37pm UTC](https://discussions.flightaware.com/t/piaware-not-working/20196/5 "2019-12-03T18:37:29Z")
> [@triggers](#): > > The system is currently disconnected as he is bringing it over to me tomorrow for a complete rebuild. Really nothing useful in there. dump1090-fa isn’t running, but not enough of the logs shown to even make a guess why not. This is really strange: ```auto Unit \xe2\x80\x93l.service could not be found. ``` Maybe the sd-card is bad? ---
**Author:** ![triggers](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/triggers/32/117248_2.png) [@triggers](https://discussions.flightaware.com/u/triggers)\ **Post date:** [December 3, 2019, 6:53pm UTC](https://discussions.flightaware.com/t/piaware-not-working/20196/6 "2019-12-03T18:53:01Z")
Many thanks. I also think the card has gone bad. The 3 status buttons on the web page were all green and as I said the feeder seemed to be checking in. Very strange. Once I get the system back tomorrow I’ll report back. ---
**Author:** ![obj](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/obj/32/118984_2.png) [@obj](https://discussions.flightaware.com/u/obj)\ **Post date:** [December 3, 2019, 8:18pm UTC](https://discussions.flightaware.com/t/piaware-not-working/20196/7 "2019-12-03T20:18:11Z")
> [@wiedehopf](#): > > ```auto > Unit \xe2\x80\x93l.service could not be found. > > ``` That is a cut & paste problem. E2 80 93 is a UTF-8 en-dash; someone’s cut&pasted a non-ascii command line (that “-l” on the command line is not actually a “-l” …) ```auto $ echo '–l' | hexdump -C 00000000 e2 80 93 6c 0a |...l.| ``` ---
**Author:** ![triggers](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/triggers/32/117248_2.png) [@triggers](https://discussions.flightaware.com/u/triggers)\ **Post date:** [December 3, 2019, 10:32pm UTC](https://discussions.flightaware.com/t/piaware-not-working/20196/8 "2019-12-03T22:32:51Z")
> [@obj](#): > > That is a cut & paste problem Being a bit dense here but are you saying that there is a dodgy cut & paste in the piaware code or in the cut & paste of the error messages? ---
**Author:** ![wiedehopf](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/wiedehopf/32/114045_2.png) [@wiedehopf](https://discussions.flightaware.com/u/wiedehopf)\ **Post date:** [December 3, 2019, 10:42pm UTC](https://discussions.flightaware.com/t/piaware-not-working/20196/9 "2019-12-03T22:42:48Z")
> [@triggers](#): > > cut & paste of the error messages? this. so it’s not an identification of log corruption. rather copy paste by your brother artifact. ---
**Author:** ![obj](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/obj/32/118984_2.png) [@obj](https://discussions.flightaware.com/u/obj)\ **Post date:** [December 4, 2019, 4:52am UTC](https://discussions.flightaware.com/t/piaware-not-working/20196/10 "2019-12-04T04:52:59Z")
> [@triggers](#): > > Being a bit dense here but are you saying that there is a dodgy cut & paste in the piaware code or in the cut & paste of the error messages? A dodgy cut and paste of the _command which was run_ (i.e. the input, not the resulting output). The “-” in the command pasted is not the character you get if you hit the “-” key on your keyboard, but a Unicode character that looks very similar; systemctl sees them as different characters. ---
**Author:** ![triggers](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/triggers/32/117248_2.png) [@triggers](https://discussions.flightaware.com/u/triggers)\ **Post date:** [December 4, 2019, 9:06am UTC](https://discussions.flightaware.com/t/piaware-not-working/20196/11 "2019-12-04T09:06:58Z")
> [@obj](#): > > A dodgy cut and paste of the _command which was run_ Ah, he is using a Mac to SSH 😊 ---
**Author:** ![triggers](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/triggers/32/117248_2.png) [@triggers](https://discussions.flightaware.com/u/triggers)\ **Post date:** [December 11, 2019, 7:56pm UTC](https://discussions.flightaware.com/t/piaware-not-working/20196/12 "2019-12-11T19:56:41Z")
Looks like the USB has failed. This is with nothing plugged in to any USB port, new SD card and Buster lite. Can I continue to use the Pi for other things but never plug anything into the USB ports? ```auto pi@raspberrypi:~ $ dmesg | grep usb [0.092324] usbcore: registered new interface driver usbfs [0.092427] usbcore: registered new interface driver hub [0.092610] usbcore: registered new device driver usb [0.369872] usbcore: registered new interface driver lan78xx [0.372766] usbcore: registered new interface driver smsc95xx [0.406092] dwc_otg 3f980000.usb: base=(ptrval) [0.857314] dwc_otg 3f980000.usb: DWC OTG Controller [0.859900] dwc_otg 3f980000.usb: new USB bus registered, assigned bus number 1 [0.862596] dwc_otg 3f980000.usb: irq 56, io mem 0x00000000 [0.870585] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 4.19 [0.875736] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [0.878477] usb usb1: Product: DWC OTG Controller [0.881161] usb usb1: Manufacturer: Linux 4.19.75-v7+ dwc_otg_hcd [0.883941] usb usb1: SerialNumber: 3f980000.usb [0.893855] usbcore: registered new interface driver usb-storage [0.925798] usbcore: registered new interface driver usbhid [0.928676] usbhid: USB HID core driver [2.322418] usb 1-1: new high-speed USB device number 2 using dwc_otg [2.572851] usb 1-1: New USB device found, idVendor=0424, idProduct=9514, bcdDevice= 2.00 [2.587044] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [2.932478] usb 1-1.1: new high-speed USB device number 3 using dwc_otg [3.072860] usb 1-1.1: New USB device found, idVendor=0424, idProduct=ec00, bcdDevice= 2.00 [3.087525] usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [3.207196] smsc95xx 1-1.1:1.0 eth0: register 'smsc95xx' at usb-3f980000.usb-1.1, smsc95xx USB 2.0 Ethernet, b8:27:eb:69:bd:b1 [3.226015] usb 1-1-port2: over-current change #1 [3.602749] usb 1-1-port2: over-current change #2 [3.858665] usb 1-1-port2: over-current change #3 [4.114659] usb 1-1-port2: over-current change #4 [4.370656] usb 1-1-port2: over-current change #5 [4.626670] usb 1-1-port2: over-current change #6 ``` ---
**Author:** ![Nitr0](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/nitr0/32/128824_2.png) [@Nitr0](https://discussions.flightaware.com/u/Nitr0)\ **Post date:** [December 11, 2019, 10:46pm UTC](https://discussions.flightaware.com/t/piaware-not-working/20196/13 "2019-12-11T22:46:11Z")
> [@triggers](#): > > usb 1-1-port2: over-current change I’ve read about this happening to several people in the past and haven’t seen a true resolve. First thing I’d do is check the board for physical damage and/or shorted pins, especially the POE pins and inside each USB port. Perhaps a pin in one of the USB ports folded back and is shorting out. Secondly, try booting the thing using a different power supply. If neither of those yield nothing, you’d be down to checking voltages across the board - there are several threads about this on the Raspberry forums still I think. EDIT/ADD: Are you using a POE hat by chance? Some “official” hats were fatally flawed: [https://www.martinrowan.co.uk/2018/09/raspberry-pi-official-poe-hat-fail-if-you-want-to-use-the-usb-ports/](https://www.martinrowan.co.uk/2018/09/raspberry-pi-official-poe-hat-fail-if-you-want-to-use-the-usb-ports/) ---
**Author:** ![triggers](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/triggers/32/117248_2.png) [@triggers](https://discussions.flightaware.com/u/triggers)\ **Post date:** [December 12, 2019, 8:21am UTC](https://discussions.flightaware.com/t/piaware-not-working/20196/14 "2019-12-12T08:21:42Z")
Thanks for the reply Nitr0 > [@Nitr0](#): > > EDIT/ADD: Are you using a POE hat by chance? Some “official” hats were fatally flawed: Just a bare bones Pi, no hats. I’ve tried different power supplies too. The fixes on the Pi forums seem to require removing components or reflowing components. Too much hassle for me. I will take a look at the USB pins