fr24feed not connecting

[Responder]

That's true. Flight Aware do send back the processed data back to your dump1090. Forgot about that. Thanks mate :-)

[Oblivian]

No, mlat uploads mlat data to Fr from dvbt sticks. Flight aware sends mlat processed data to users if enough are around.

You can't do local processing yourself to see them

Sent from my XT1092 using Tapatalk

[Responder]

Hi again Oblivian,

Not sure if I have setup something wrong or it isn't included. I have said "yes" for mlat receiving/processing but I am unable to see any mlat aircraft on the localhost:8080 page. I can see the mlat traffic within the listing on the right of screen (as I know which planes operate mlat in the UK) but it doesn't show the plane on the map section of the screen.

Have I setup something wrong? Am I not synchronised with enough users for mlat? or, doesn't FR24's version of dump1090 display mlat traffic on the :8080 web page?

Thanks again.

[VK4FSRD]

I am having issues with fr24feed, here is a copy of the log.

2016-01-29 05:14:32 | [feed][c]GND: YES
2016-01-29 05:14:32 | [feed][c]NonADSB: YES
2016-01-29 05:14:32 | [feed][c]Timestamps: optional
2016-01-29 05:14:32 | [feed][c]Max range AIR: 350.0nm
2016-01-29 05:14:32 | [feed][c]Max range GND: 100.0nm
2016-01-29 05:14:32 | [feed][i]defined 1 server
2016-01-29 05:14:32 | [feed][n]YTWB4@83.140.21.66:8099/UDP
2016-01-29 05:14:32 | [feed][n]connecting
2016-01-29 05:14:32 | [stats][i]Stats thread started
2016-01-29 05:14:35 | [reader][i][0]Connecting to Generic receiver via (exe://mr-dump1090.exe --raw)
2016-01-29 05:14:35 | [reader][i][0]Connected to the receiver, authenticating
2016-01-29 05:14:35 | [reader][i][0]Authenticated, processing messages
2016-01-29 05:14:37 | [reader][i][0]Connection terminated
2016-01-29 05:14:42 | [reader][i][0]Connecting to Generic receiver via (exe://mr-dump1090.exe --raw)
2016-01-29 05:14:42 | [reader][i][0]Connected to the receiver, authenticating
2016-01-29 05:14:42 | [reader][i][0]Authenticated, processing messages
2016-01-29 05:14:44 | [reader][i][0]Connection terminated
2016-01-29 05:14:49 | [reader][i][0]Connecting to Generic receiver via (exe://mr-dump1090.exe --raw)
2016-01-29 05:14:49 | [reader][i][0]Connected to the receiver, authenticating
2016-01-29 05:14:49 | [reader][i][0]Authenticated, processing messages
2016-01-29 05:14:51 | [reader][i][0]Connection terminated
2016-01-29 05:14:54 | [feed][n]connected via TCP (fd 748)
2016-01-29 05:14:54 | [feed][n]switching to UDP
2016-01-29 05:14:54 | [feed][n]working
2016-01-29 05:14:56 | [reader][i][0]Connecting to Generic receiver via (exe://mr-dump1090.exe --raw)
2016-01-29 05:14:56 | [reader][i][0]Connected to the receiver, authenticating
2016-01-29 05:14:56 | [reader][i][0]Authenticated, processing messages
2016-01-29 05:14:58 | [reader][i][0]Connection terminated
2016-01-29 05:15:03 | [reader][i][0]Connecting to Generic receiver via (exe://mr-dump1090.exe --raw)
2016-01-29 05:15:06 | [reader][i][0]Connected to the receiver, authenticating
2016-01-29 05:15:06 | [reader][i][0]Authenticated, processing messages
2016-01-29 05:15:06 | [reader][i][0]Connection terminated
2016-01-29 05:15:11 | [reader][i][0]Connecting to Generic receiver via (exe://mr-dump1090.exe --raw)
2016-01-29 05:15:11 | [reader][i][0]Connected to the receiver, authenticating
2016-01-29 05:15:11 | [reader][i][0]Authenticated, processing messages
2016-01-29 05:15:13 | [reader][i][0]Connection terminated
2016-01-29 05:15:18 | [reader][i][0]Connecting to Generic receiver via (exe://mr-dump1090.exe --raw)
2016-01-29 05:15:18 | [reader][i][0]Connected to the receiver, authenticating
2016-01-29 05:15:18 | [reader][i][0]Authenticated, processing messages
2016-01-29 05:15:20 | [reader][i][0]Connection terminated
2016-01-29 05:15:24 | [feed][n]ping 1
2016-01-29 05:15:25 | [reader][i][0]Connecting to Generic receiver via (exe://mr-dump1090.exe --raw)
2016-01-29 05:15:25 | [reader][i][0]Connected to the receiver, authenticating
2016-01-29 05:15:25 | [reader][i][0]Authenticated, processing messages
2016-01-29 05:15:27 | [reader][i][0]Connection terminated
2016-01-29 05:15:32 | [reader][i][0]Connecting to Generic receiver via (exe://mr-dump1090.exe --raw)
2016-01-29 05:15:32 | [reader][i][0]Connected to the receiver, authenticating
2016-01-29 05:15:32 | [reader][i][0]Authenticated, processing messages
2016-01-29 05:15:34 | [reader][i][0]Connection terminated
2016-01-29 05:15:39 | [reader][i][0]Connecting to Generic receiver via (exe://mr-dump1090.exe --raw)
2016-01-29 05:15:39 | [reader][i][0]Connected to the receiver, authenticating
2016-01-29 05:15:39 | [reader][i][0]Authenticated, processing messages
2016-01-29 05:15:41 | [reader][i][0]Connection terminated
2016-01-29 05:15:46 | [reader][i][0]Connecting to Generic receiver via (exe://mr-dump1090.exe --raw)
2016-01-29 05:15:46 | [reader][i][0]Connected to the receiver, authenticating
2016-01-29 05:15:46 | [reader][i][0]Authenticated, processing messages
2016-01-29 05:15:48 | [reader][i][0]Connection terminated
2016-01-29 05:15:53 | [reader][i][0]Connecting to Generic receiver via (exe://mr-dump1090.exe --raw)
2016-01-29 05:15:53 | [reader][i][0]Connected to the receiver, authenticating
2016-01-29 05:15:53 | [reader][i][0]Authenticated, processing messages
2016-01-29 05:15:55 | [reader][i][0]Connection terminated
2016-01-29 05:15:55 | [feed][n]ping 2

it is now just scrolling through as follows over and over, it has been working fine for months with out issue

2016-01-29 05:15:53 | [reader][i][0]Connected to the receiver, authenticating
2016-01-29 05:15:53 | [reader][i][0]Authenticated, processing messages
2016-01-29 05:15:55 | [reader][i][0]Connection terminated

Please assist

[Responder]

Config web page on port 8754. Http://yourpisiphere:8754

Sent from my GT-I9300 using Tapatalk

Thanks Oblivian. Working well now on 8080 :-)

[Oblivian]

Config web page on port 8754. Http://yourpisiphere:8754

Sent from my GT-I9300 using Tapatalk

[Responder]

Hi Oblivian,

I decided to finally use the new FR24 Pi Image to feed my data tonight, instead of the image that was created and uploaded by a past member/feeder.

Anyway, I got the feeder working - see below.

FR24 Link: Connected via UDP
FR24 Radar Code: T-EGBB16
Aircraft Tracked (ModeS & ADS-B): 9
Aircraft Uploaded: 7
Receiver: dvbt, Connected
MLAT running: YES

However, I have tried to use my web browser using the dump1090 with my IP:8080 but it isn't connecting. You said above to use the command --net --net-http-port 8080 in the config file.

Please would you kindly advise on how to access the config file. I've looked in /usr/lib/fr24/ in my RPi but unable to see any kind of config file and once found, how do I actually put the command line in?

Many thanks.

[Oblivian]

No if you select avrtcp it uses local network ports. So dump1090 connects to stick. Outputs data on 30002. Frfeeder attaches to 30002. Other software can do the same. Up to 3 clients

Sent from my XT1092 using Tapatalk

[razorseal]

It also means other software can use 30002 as you are now in tcp mode if configured right

Sent from my XT1092 using Tapatalk

I did the localhost:8080 thing you mentioned and I got a webview now. but does that mean I'm in TCP mode? and is 30002 on by default or something?

[razorseal]

No 8754 is the web output only. See post above. It has the answer

Sent from my XT1092 using Tapatalk

Very cool. I have a map that shows me the stuff now on localhost:8080. How do I get adsbscope or VRS to get this feed now? Direct them to localhost:8080?

Either format output from RTL1090 is not in right mode, or the signal is not good enough. FR24 is configured for filtering and will only respond to a constant feed, patchy or not very good signal will be ignored.

If you want a simple web view, reconfigure FR24feed to USB dognle, add <--net --net-http-port 8080> Minus <'s to additional commands and launch FR on its own.

That will enable the Dump1090 web output on http://localhost:8080

RTL does its own data filtering so isn't recommended for a primary receiver

Nice! got a google map view of my SDR's info now.

[Oblivian]

It also means other software can use 30002 as you are now in tcp mode if configured right

Sent from my XT1092 using Tapatalk

[Oblivian]

No 8754 is the web output only. See post above. It has the answer

Sent from my XT1092 using Tapatalk

[razorseal]

Is there a way I can output the info from fr24feed to ADSBScope or planeplotter or VRS??? I like seeing the stuff on my own local side. Since I shut off RTL1090 now, I'm not sure how to pull that info

can I direct it to port 8754?

[Oblivian]

Either format output from RTL1090 is not in right mode, or the signal is not good enough. FR24 is configured for filtering and will only respond to a constant feed, patchy or not very good signal will be ignored.

If you want a simple web view, reconfigure FR24feed to USB dognle, add <--net --net-http-port 8080> Minus <'s to additional commands and launch FR on its own.

That will enable the Dump1090 web output on http://localhost:8080

RTL does its own data filtering so isn't recommended for a primary receiver

[razorseal]

If it receives data it needs, And processes it. It will bundle and send to server, state will change to Online.

F- are supplied boxes from FR24, not software based like you are working on. They are live and able to report connection data

Gotcha...

something doesn't look or feel right about this in TCP mode. as u see in RTL1090, a plane is shown on my map transmitting. it never was sent to fr24feeder. I went back to the default mode and shut RTL1090 off for now. it started tracking correctly now.