Thanks. I have this info so far: lines out output: 13 Data incoming from: 94.174.***.** Route: beast_front Port: 30005 Backend: beast_back Connected: merge-3-0 Age: 20m50s
OK guys, and sorry to have taken up lots of time today:-( I had Flight Aware and ADSBExchange running fine earlier on the RPi I take with me to airshows as a feed and named it gm4nsz_portable. I then loaded the software onto the RPi I run 24/7 at home and I can't see it! I did run them both at the same time on the same wifi network and both on 30005 so thought that may be the problem and took the portable RPi off and rebooted the home system named gm4nsz_home. That didn't work so reinstalled the ADSBExchange add-on and tried again. I still can't see myself on the sync 3a page. I have this on myip which is similar for Beast but with a much different connected address: Data incoming from: 94.174.***.** Route: beast_front Port: 30005 Backend: beast_back Connected: cons-10-51051 Age: 1h19m Data incoming from: 94.174.***.** Route: MLAT_front Port: 31090 Backend: MLAT_back_3 Connected: mlat-c Age: 8m28s Data incoming from: 94.174.***.** Route: MLAT_front Port: 31090 Backend: MLAT_back_3 Connected: mlat-c Age: 7m28s I'm guessing that the other MLAT feed is for the FR24 RPi I'm also running independently. Any thoughts or am I just not looking in the correct place for my feed data? Thanks
If you are using a Buster instead of a Stretch image, the mlat-client won't compile. The setup script would need to change the MLAT_CLIENTVERSION and tag to 0.2.10 Code: MLATCLIENTVERSION="0.2.6" MLATCLIENTTAG="v0.2.6" So it needs to look like this to work on Buster. (new Raspbian version) Code: MLATCLIENTVERSION="0.2.10" MLATCLIENTTAG="v0.2.10" Didn't quite get around to making a pull request, James would you mind changing that so it works with Buster?
Ok, thanks. However, to the best of my knowledge, both of the Flight Aware drivers and RPis were using the same setup so not sure why it works on one and not the other?
Well let's see then. What does this command return: mlat-client You can also check the script and post here what this command returns: Code: cat ~/adsb-exchange/adsbexchange-mlat_maint.sh Also interesting, what does this command return: pgrep -a adsbexchange
Sorry for not responding. Got called away last evening. Interestingly, the data seems to have appeared now: Does this look sensible?
Looks normal. Is that the UK MLAT server? According to James that's always unstable because it has so many people contributing. So not seeing a connection for a long time after you reboot your Pi or something, is normal.
Yes, it's from the 3A page. I'm also now showing on the map . I wasn't expecting it to take that long to show; I'll just sit on my hands if I change anything in the future!
Hi all, Just a quick note to say the steps appear to be working fine for me (after I enabled keepalives in PuTTY!) - my Pi is now doing Flightaware, FlightRadar24 and this one lines out output: 13 Data incoming from: 87.81.x.x Route: MLAT_front Port: 31090 Backend: MLAT_back_3A2 Connected: mlat-c2 Age: 8m48s Data incoming from: 87.81.x.x Route: beast_front Port: 30005 Backend: beast_back Connected: cons-1-51033 Age: 2m58s I am on the MLAT stats page all OK, but should I now appear on the coverage map? Cheers, Steve
Good afternoon All, I have been feeding for some time now and it all appears stable. I also have a RPi system which I use at various airfield locations when I am there running airshows, one of which is RAF Cosford. It is fairly easy to change the feeder location on the Flight Aware interface by dragging the point to the new location which allows MLAT to synchronise. How easy is it to change the location in this software and how? I can't remember how I set it at first and don't want to b*@@%r up the SD card . Thanks.
