Yeah if you don't mind, run my dump1090-fa install script, it will fix you FR24 configuration and clean up what fr24feed has effed up! (I've speculated on the problem of selecting dvb-t in fr24feed and elaborated some in my earlier post) https://github.com/wiedehopf/adsb-wiki/wiki/Automatic-installation-for-dump1090-fa
Phew, it didn't work [email protected]:~ $ https://github.com/wiedehopf/adsb-wiki/wiki/Automatic-installation-for-dump1090-fa -bash: https://github.com/wiedehopf/adsb-wiki/wiki/Automatic-installation-for-dump1090-fa: No such file or directory Yes I know, I'll check it out this weekend!
Quick update. Without the help of any wine today I started again from scratch and it all went well. Now feeding FA, FR24 and ADSBx. Thanks, @wiedehopf for the info about changing the FR24 setup from dvb-t to Beast which was mucking things up. (attached a screenshot in case it helps anyone else). I'd also not helped things by putting altitude in metres instead of feet (doh). The other idiot move I did when installing ADSBx was to paste all the commands into Kitty SSH at once, "sudo apt install git socat" asks a question at the end so the next line which was pasted answered it wrong (if that makes sense). I should know better than that (25 years using telnet in my day job). Next on the list is to move the Aerial outside, but the Lake District weather hasn't made that look easy today. Still getting up to 100 Mile range propped up against the window though. Many thanks to all for putting up with a (rather tipsy) newbie last night, really appreciated all the replies.
It seemed like a funny thing to do at the time (after a drink) but now looks stupid. I did know it was a link, sorry.
"Enter your recievers altitude in meters > 0m (optional suffix m for meters or ft for feet)." If you don't put any units behind it, it will assume meters. That is altitude above sea level by the way. What kind of antenna are you using?
The FR24 setup wanted it in feet (I think, or was that FA) I've had a few goes to set it all up since the aerial arrived on Tuesday and I started with the FR24 image but struggled to combine it with ADSBx and FA. it's an SCO-1090-MCX from Jetvision. All good now.
I thought it was all working as .../my_ip shows , but I don't see myself listed on the feeder statistics page. I've done some digging and tried running the contents of adsbexchange-mlat_maint.sh and got the following: Code: [email protected]:~/adsb-exchange $ /usr/bin/mlat-client --input-type dump1090 --input-connect localhost:30005 --lat 54.67536 --lon -3.20212 --alt 90 --user MikeD --server feed.adsbexchange.com:31090 --no-udp --results beast,connect,localhost:30104 Mon Aug 12 16:12:37 2019 mlat-client 0.2.6 starting up Mon Aug 12 16:12:37 2019 Connected to multilateration server at feed.adsbexchange.com:31090, handshaking Mon Aug 12 16:12:38 2019 Beast-format results connection with ::1:30104: connection established Mon Aug 12 16:12:58 2019 Lost connection to feed.adsbexchange.com:31090 Mon Aug 12 16:12:58 2019 Reconnecting in 30.0 seconds Mon Aug 12 16:13:28 2019 Connected to multilateration server at feed.adsbexchange.com:31090, handshaking Mon Aug 12 16:13:48 2019 Lost connection to feed.adsbexchange.com:31090 Mon Aug 12 16:13:48 2019 Reconnecting in 30.0 seconds FlightAware and FR24 tell me I'm feeding them fine. I'd like to feed ADSBx as the coverage map shows a bit of a hole where I am (UK, North Cumbria) unless there are others feeding with privacy set. I'm quite sure It's something I've done wrong but still need a bit of help figuring it out. My day job involves working with OS-9 (really old real-time OS, nothing to do with Apple) and although it's similar to unix everything is just a bit different.
It's UK mlat slice, you can't do anything more. Feed to 30005 looks stable, mlat client is disconnecting and reconnecting. Keep feeding, don't change anything.
