Raspberry Pi3, Piaware feeding to FA & FR24 issues.

FlightAware ADS-B Flight Tracking
1

Hi, first post here but been lurking for a while.

I have setup a Raspberry Pi3 with a FA Pro Stick, FA ADS-B filter and the FA 1090Mhz antenna. I installed PIAware and setup my FlightAware feed and then added my FlightRadar24 feed after. The issue I am having is that my feeds keep losing connection, they could be live for 12-18 hours and then drop, I then have to pull the plug and reboot. My Wi-Fi is strong and has no issues.

I also notice that the red power LED goes out once that it has rebooted even though the feeds are live, I thought the red led should remain on?

Anyone have any idea’s or recommendations?

Thanks

2

Sounds like a power supply problem.
Do you have a quality 2.5 amp power supply?

3

Which begs the question; What do the status lights actually mean??

4

The LEDs are software-controllable but in the default configuration the red LED is driven by a voltage monitor that monitors the 5V line.
If the red LED is off (or blinks off), you have power problems - the 5V line has dropped below the monitor’s trigger level (I can’t remember exactly what the trigger level is, 4.something…)

5

And the green LED??

6

Try this:
raspberrypi-spy.co.uk/2013/0 … explained/
assuming the LED use has not changed.

7

The power supply is a PiHut psu but it is only 2amp and not 2.5amps. I have another psu on order that should be delivered tomorrow so I’ll see how that goes.

Thanks

8

New power supply arrived yesterday, the power light remains constantly red but I still have the same issue. The system ran from 5pm yesterday and went offline at 8am this morning :frowning:

9

this issue has been happening to me too and the problem is that the makers of piaware software have a bug in there with the pi 3 that needs to be ironed out.

I went through all the scenarios with power supply not being enough so I got a 5 volt 5 amp supply and same problem

I changed dongles from the pro stick to a regular dongle and same problem

yet i put the pro stick on a pi 2 using the latest software and it runs forever …

it has to be a programming issue…

but others out there will tell you different

problem is there are too many posts like this

10

So you’re saying that you ran identical software on two different bits of hardwre, and only one of them had problems, and therefore the problem must be in the software?
Umm…

That said, if you want to send me a detailed bug report I can certainly take a look, but so far I have nothing concrete to go on. My own Pi 3 has been running for a couple of months with no issues: flightaware.com/adsb/stats/user/obj#stats-20523

11

I’m kinda new to the Pi3, what log files files would you need?

12

If you want to be really complete:

Move /tmp back onto the sdcard if it’s on tmpfs.
Send /var/log/syslog, /tmp/piaware.out, and the output of:

  • dmesg
  • uptime
  • /sbin/ifconfig -a
  • /sbin/route -n
  • pgrep -a piaware
  • pgrep -a fa-mlat-client
  • pgrep -a faup1090
  • pgrep -a dump1090

… immediately after you notice that your feed is having problems (before rebooting)

You can mail that to me at oliver@mutability.co.uk

13

Of course it hasn’t. It wouldn’t dare! :wink: :slight_smile:

14

yes one is a pi 2 the other is a pi 3

others with pi 3 have had this problem

15

I have reinstalled the scripts and so far so good, I’ll monitor it over the next couple of days.

Thanks

16

I have almost exact same symptoms.

syslog:


Jun  4 06:25:18 piaware kernel: [89614.988455] brcmfmac: brcmf_sdio_hdparse: seq 253: sequence number error, expect 252
Jun  4 06:25:18 piaware kernel: [89614.989848] brcmfmac: brcmf_sdio_hdparse: seq 252: sequence number error, expect 254
Jun  4 06:25:18 piaware kernel: [89614.992594] brcmfmac: brcmf_sdio_hdparse: seq 254: sequence number error, expect 253
Jun  4 06:25:35 piaware rsyslogd0: action 'action 17' resumed (module 'builtin:ompipe') [try http://www.rsyslog.com/e/0 ]
Jun  4 06:25:35 piaware rsyslogd-2359: action 'action 17' resumed (module 'builtin:ompipe') [try http://www.rsyslog.com/e/$
Jun  4 06:30:01 piaware CRON[20012]: (root) CMD (bash /home/pi/adsb-receiver/build/portal/graphs/make-collectd-graphs.sh 6$
Jun  4 06:30:01 piaware CRON[20014]: (root) CMD (bash /home/pi/adsb-receiver/build/portal/graphs/make-collectd-graphs.sh 1$
Jun  4 06:30:12 piaware kernel: [89909.111399] brcmfmac: brcmf_sdio_hdparse: seq 145: sequence number error, expect 144
Jun  4 06:30:12 piaware kernel: [89909.117508] brcmfmac: brcmf_sdio_hdparse: seq 144: sequence number error, expect 146
Jun  4 06:30:12 piaware kernel: [89909.118299] brcmfmac: brcmf_sdio_hdparse: seq 146: sequence number error, expect 145
Jun  4 06:32:01 piaware CRON[20094]: (root) CMD (bash /home/pi/adsb-receiver/build/portal/graphs/make-collectd-graphs.sh 2$
Jun  4 06:35:01 piaware CRON[20143]: (root) CMD (bash /home/pi/adsb-receiver/build/portal/graphs/make-collectd-graphs.sh 1$
Jun  4 06:39:01 piaware CRON[20230]: (root) CMD (   -x /usr/lib/php5/sessionclean ] && /usr/lib/php5/sessionclean)
Jun  4 06:40:01 piaware CRON[20294]: (root) CMD (bash /home/pi/adsb-receiver/build/portal/graphs/make-collectd-graphs.sh 6$
Jun  4 06:40:01 piaware CRON[20297]: (root) CMD (bash /home/pi/adsb-receiver/build/portal/graphs/make-collectd-graphs.sh 1$
Jun  4 06:40:17 piaware kernel: [90514.196738] brcmfmac: brcmf_sdio_hdparse: seq 138: sequence number error, expect 137
Jun  4 06:40:17 piaware kernel: [90514.197092] brcmfmac: brcmf_sdio_hdparse: seq 137: sequence number error, expect 139
Jun  4 06:40:17 piaware kernel: [90514.250710] brcmfmac: brcmf_sdio_hdparse: seq 139: sequence number error, expect 138
Jun  4 06:42:01 piaware CRON[20441]: (root) CMD (bash /home/pi/adsb-receiver/build/portal/graphs/make-collectd-graphs.sh 2$
Jun  4 06:44:01 piaware CRON[20563]: (root) CMD (bash /home/pi/adsb-receiver/build/portal/graphs/make-collectd-graphs.sh 7$
Jun  4 06:45:01 piaware CRON[20637]: (root) CMD (bash /home/pi/adsb-receiver/build/portal/graphs/make-collectd-graphs.sh 1$
Jun  4 06:50:01 piaware CRON[20871]: (root) CMD (bash /home/pi/adsb-receiver/build/portal/graphs/make-collectd-graphs.sh 6$
Jun  4 06:50:01 piaware CRON[20873]: (root) CMD (bash /home/pi/adsb-receiver/build/portal/graphs/make-collectd-graphs.sh 1$

Usualy it keeps wifi connection on, but this morning it was all lost and had to do a hard reboot.

17

Fix the power issue first; if the red LED is off after boot your power supply isn’t supplying the required voltage.

Jun 4 06:25:18 piaware kernel: [89614.988455] brcmfmac: brcmf_sdio_hdparse: seq 253: sequence number error, expect 252

That looks like a wifi driver bug: github.com/raspberrypi/linux/issues/1313

18

It should remain on. I bought 2 new Pi3’s and set them both up, neither one had a red light lit but they were still mostly working, so I switched them to a better power source (an Anker phone charger seems to do fairly ok but I don’t plan on this being a long term solution as I still see the red LED go off once in a while)

I decided to put a power meter on it and see how much power it’s pulling.

The entire set up (Pi 3, SD card, ethernet active (bt and wifi not touched from the FA stock image file) with PiAware running is pulling just under 900mA

The RTL-SDR dongle alone is pulling about 500mA

I don’t have one handy (I may be able to borrow one from a friend tomorrow) but I believe the Pi 2 operating current is a decent amount lower.

19

i bought a belkin powered usb hub
solved my problem

i run the pi 3 with its own 2.5 amp supply
I power the prostick withe the powered hub

the pi 3 does not give enough amperage to the prostick

any little blip and you drop connection

still testing but it is still up and running

20

Have you tried adding: max_usb_current=1

To /boot/config.txt ?? That kicks total current available to the USB ports to 1.2A …