Linux feeder software for Flightradar24 (Old software)

[Ressy]

In your fr24.sh script, are you specifying where the data stream is?

My fr24.sh looks like:

export FR24AUTHIP=83.140.247.20
/home/pi/fr24feed_x86_242 --fr24key=xxxxxxxxxxx --bs-ip=192.168.0.188 > /tmp/fr24feed.log &

Where 192.168.0.188 is the IP address of the linux box itself, so you should replace that with your box's IP on your local network. I never tried using 127.0.0.1 (which is localhost), but presumably that should also work.

But as RESSI said, also make sure that dump1090 is actually running.

I suspect that is his problem.
Since he's using mint, I dare say he's using a pc/server, so likely everything is on same box, localhost works fine.

Using screen, I find is better, since you can temporarily reattach the session if you suspect there are problems (for simplicity I use -S fr24 -S 1090 etc so screen -r fr24 recalls it rather than the full session id's), for both dump1090 and fr24's stuff (and any others you feed) mines on a slackware pc (media/file server so its always on) but that might not be suitable to an RPi, hrmm, is screen even on it? spose you can install it if not.

[peterhr]

In your fr24.sh script, are you specifying where the data stream is?

My fr24.sh looks like:

export FR24AUTHIP=83.140.247.20
/home/pi/fr24feed_x86_242 --fr24key=xxxxxxxxxxx --bs-ip=192.168.0.188 > /tmp/fr24feed.log &

Where 192.168.0.188 is the IP address of the linux box itself, so you should replace that with your box's IP on your local network. I never tried using 127.0.0.1 (which is localhost), but presumably that should also work.

But as RESSI said, also make sure that dump1090 is actually running.

Hi Herman,

I use 127.0.0.1 since dump1090 and fr24feed are on the same box

[HermanZA]

In your fr24.sh script, are you specifying where the data stream is?

My fr24.sh looks like:

export FR24AUTHIP=83.140.247.20
/home/pi/fr24feed_x86_242 --fr24key=xxxxxxxxxxx --bs-ip=192.168.0.188 > /tmp/fr24feed.log &

Where 192.168.0.188 is the IP address of the linux box itself, so you should replace that with your box's IP on your local network. I never tried using 127.0.0.1 (which is localhost), but presumably that should also work.

But as RESSI said, also make sure that dump1090 is actually running.

[Ressy]

Hi.

I start feeding with a new system base on Linux, (Mint 17) but when I running a program displayed me this:

./fr24feed_x86_242 --fr24key=*************
[i]FR24Feed v242 - built on Apr 23 2014/10:19:07
[i]Downloading configuration...OK
[i]Parsing configuration...OK
[c]Interval: 5s
[c]Latitude: **.********
[c]Longitude: *****.*********
[c]GND: YES
[c]NonADSB: YES
[i]Source defined as Basestation
[b]connecting to localhost:30003
[e]could not connect to BS
[i]waiting 5 seconds
[n]defined 1 server
[n]***@83.140.21.66:8099/UDP
[n]connecting
[i][stats]Stats thread started
[n]connected
[n]switching to UDP
[n]working
[i]Source defined as Basestation
[b]connecting to localhost:30003
[e]could not connect to BS
[i]waiting 5 seconds
[i]Source defined as Basestation
[b]connecting to localhost:30003
[e]could not connect to BS
[i]waiting 5 seconds
[i]Source defined as Basestation
[b]connecting to localhost:30003
[e]could not connect to BS
[i]waiting 5 seconds
[i]Source defined as Basestation
[b]connecting to localhost:30003
[e]could not connect to BS
[i]waiting 5 seconds

where is the problem?

specification:
dongle RTL2832U
OS: Linux Mint 17

Being linux I assume you are using dump1090, is it actually running? if so, how are you running it?

copy of my /etc/rc.d/rc.adsb script that starts everything from rc.M (or your systems equiv startup calls): http://members.ausics.net/noelb/rc.adsb

[RelativeCode]

Hi.

I start feeding with a new system base on Linux, (Mint 17) but when I running a program displayed me this:

./fr24feed_x86_242 --fr24key=*************
[i]FR24Feed v242 - built on Apr 23 2014/10:19:07
[i]Downloading configuration...OK
[i]Parsing configuration...OK
[c]Interval: 5s
[c]Latitude: **.********
[c]Longitude: *****.*********
[c]GND: YES
[c]NonADSB: YES
[i]Source defined as Basestation
[b]connecting to localhost:30003
[e]could not connect to BS
[i]waiting 5 seconds
[n]defined 1 server
[n]***@83.140.21.66:8099/UDP
[n]connecting
[i][stats]Stats thread started
[n]connected
[n]switching to UDP
[n]working
[i]Source defined as Basestation
[b]connecting to localhost:30003
[e]could not connect to BS
[i]waiting 5 seconds
[i]Source defined as Basestation
[b]connecting to localhost:30003
[e]could not connect to BS
[i]waiting 5 seconds
[i]Source defined as Basestation
[b]connecting to localhost:30003
[e]could not connect to BS
[i]waiting 5 seconds
[i]Source defined as Basestation
[b]connecting to localhost:30003
[e]could not connect to BS
[i]waiting 5 seconds

where is the problem?

specification:
dongle RTL2832U
OS: Linux Mint 17

[rubenc]

Hello!

I have a problem. I am feeding with a "Cubieboard" (ARM) and it works great for a week. But then i get the following error message in the Feeder log:


What means errno: 101?
In the first post there's only mentioned errno 111?

Thank you very much.

Regards
Skyscraper

Hi,

Error 101 is "network unreachable". That could be due to firewalling/routing issues.

Rubén.

[Skyscraper]

Hello!

I have a problem. I am feeding with a "Cubieboard" (ARM) and it works great for a week. But then i get the following error message in the Feeder log:

[e]Could not connect to feed.flightradar24.com, errno: 101

What means errno: 101?
In the first post there's only mentioned errno 111?

Thank you very much.

Regards
Skyscraper

[1gwk]

Is there a reason why you don't run the feeder on the Pi - it only uses 5-10% of the Pi resource and someone else with the setup you have has said they got a backlog problem where the Pi couldn't feed data fast enough to the feeder and had a huge backlog of network traffic waiting to go down the pipe. The delay all being due to all Pi network traffic having to go via the USB chipset.

Raspberry is performing other tasks also, so i decided to run feeder at my x86 box to reduce raspberry load. Usb ethernet might be problem, if there is huge amount of planes seen by dump1090, but i haven't seen that on my setup.

#tc -s qdisc ls dev eth0

qdisc pfifo_fast 0: root refcnt 2 bands 3 priomap 1 2 2 2 1 2 0 0 1 1 1 1 1 1 1 1
Sent 73467398 bytes 483161 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0

[tyldum]

Got an issue with fr24 telling me that my feed is inactive, however I do have some observations:

(-35 0.00000000) No handler for message type 24 from 30d879
[n]ping 42
[n]ping 43
[n]ping 44
[n]ping 45
[n]ping 46
(-39 0.00000000) Type 0 (short A-A surveillance) from 5257fa at 47950ft (speed 1200-2400kt)
[i]Removed 0 of 0 AC
[n]pinging the server
[n]ping 1
[n]ping 2
[i][stats]sent 16 bytes
(-39 0.00000000) Type 0 (short A-A surveillance) from 18a62d at 90100ft (speed 75-150kt)
[n]pinging the server
(-38 0.00000000) Type 4 (short surveillance altitude reply) from ed0ddd at -900ft (aircraft is on the ground)
(-39 0.00000000) Type 0 (short A-A surveillance) from fd5b51 at 65300ft (speed 150-300kt)
[n]ping 1
(-39 0.00000000) No handler for message type 24 from bfb3fb
[n]pinging the server
(-37 0.00000000) Type 0 (short A-A surveillance) from 5a4c9f at 52800ft (speed 150-300kt)
(-37 0.00000000) Type 4 (short surveillance altitude reply) from 91728e at 13975ft (GROUND ALERT)

Also, connecting directly to the basestation-data I see:

MSG,6,0,577,3975DC,677,2014/08/05,00:45:01.326,2014/08/05,00:45:01.326,,,,,,,,1644,0,0,0,0
MSG,7,0,583,594D0F,683,2014/08/05,08:40:54.242,2014/08/05,08:40:54.242,,109500,,,,,,,,,,0
MSG,5,0,585,7E3770,685,2014/08/05,08:40:55.554,2014/08/05,08:40:55.554,,41300,,,,,,,1,0,0,1
MSG,7,0,586,90D869,686,2014/08/05,08:40:55.561,2014/08/05,08:40:55.561,,2700,,,,,,,,,,0
MSG,5,0,589,D82139,689,2014/08/05,08:41:24.531,2014/08/05,08:41:24.531,,119700,,,,,,,1,0,0,1
MSG,6,0,590,03DCE6,690,2014/08/05,08:41:24.632,2014/08/05,08:41:24.632,,,,,,,,0276,,,,
MSG,7,0,591,56295B,691,2014/08/05,08:41:24.633,2014/08/05,08:41:24.633,,95400,,,,,,,,,,1
MSG,7,0,592,181B50,692,2014/08/05,08:41:24.637,2014/08/05,08:41:24.637,,2575,,,,,,,,,,1
MSG,5,0,594,0DA86C,694,2014/08/05,08:41:24.738,2014/08/05,08:41:24.738,,18600,,,,,,,1,0,0,0
MSG,5,0,596,B3BB5A,696,2014/08/05,08:41:24.847,2014/08/05,08:41:24.847,,4975,,,,,,,1,0,0,1
MSG,6,0,597,DA3529,697,2014/08/05,08:41:25.148,2014/08/05,08:41:25.148,,,,,,,,0640,1,0,0,1
MSG,7,0,598,39F9AB,698,2014/08/05,08:41:25.149,2014/08/05,08:41:25.149,,28300,,,,,,,,,,1
MSG,6,0,599,89CA3A,699,2014/08/05,08:41:32.062,2014/08/05,08:41:32.062,,,,,,,,7680,,,,
MSG,7,0,600,1C4D63,700,2014/08/05,08:41:43.387,2014/08/05,08:41:43.387,,1700,,,,,,,,,,0
MSG,6,0,601,9174B7,701,2014/08/05,08:41:43.387,2014/08/05,08:41:43.387,,,,,,,,3072,1,0,1,
MSG,7,0,603,5257FA,703,2014/08/05,09:04:47.064,2014/08/05,09:04:47.064,,47950,,,,,,,,,,0
MSG,7,0,605,18A62D,705,2014/08/05,09:06:02.727,2014/08/05,09:06:02.727,,90100,,,,,,,,,,0
MSG,7,0,606,4E0259,706,2014/08/05,09:06:02.728,2014/08/05,09:06:02.728,,6000,,,,,,,,,,0
MSG,5,0,607,ED0DDD,707,2014/08/05,09:06:24.070,2014/08/05,09:06:24.070,,-900,,,,,,,0,0,0,1
MSG,6,0,608,B8E3FC,708,2014/08/05,09:06:24.170,2014/08/05,09:06:24.170,,,,,,,,6200,0,0,0,0
MSG,6,0,609,4CD496,709,2014/08/05,09:06:24.271,2014/08/05,09:06:24.271,,,,,,,,4210,,,,
MSG,7,0,610,FD5B51,710,2014/08/05,09:06:24.973,2014/08/05,09:06:24.973,,65300,,,,,,,,,,0
MSG,7,0,611,F15D0B,711,2014/08/05,09:07:04.658,2014/08/05,09:07:04.658,,34400,,,,,,,,,,0
MSG,7,0,612,5A4C9F,712,2014/08/05,09:07:04.759,2014/08/05,09:07:04.759,,52800,,,,,,,,,,0
MSG,5,0,614,1F7172,714,2014/08/05,09:07:04.759,2014/08/05,09:07:04.759,,43800,,,,,,,,,,
MSG,6,0,616,560644,716,2014/08/05,09:07:04.861,2014/08/05,09:07:04.861,,,,,,,,7444,,,,
MSG,5,0,617,91728E,717,2014/08/05,09:07:04.861,2014/08/05,09:07:04.861,,13975,,,,,,,1,0,0,1
MSG,6,0,618,8AD555,718,2014/08/05,10:40:39.907,2014/08/05,10:40:39.907,,,,,,,,2540,,,,
MSG,6,0,619,3B67CC,719,2014/08/05,10:40:40.007,2014/08/05,10:40:40.007,,,,,,,,1464,,,,
MSG,5,0,620,15FBD3,720,2014/08/05,10:40:40.008,2014/08/05,10:40:40.008,,103900,,,,,,,,,,
MSG,6,0,625,549402,725,2014/08/05,11:06:51.262,2014/08/05,11:06:51.262,,,,,,,,7436,0,0,0,0
MSG,7,0,627,1AE171,727,2014/08/05,11:21:39.130,2014/08/05,11:21:39.130,,83100,,,,,,,,,,0
MSG,6,0,628,1F0F67,728,2014/08/05,11:21:39.335,2014/08/05,11:21:39.335,,,,,,,,5310,1,0,0,0
MSG,5,0,629,B6A2DD,729,2014/08/05,11:21:55.487,2014/08/05,11:21:55.487,,73300,,,,,,,,,,
MSG,5,0,631,5018A8,731,2014/08/05,11:48:37.560,2014/08/05,11:48:37.560,,2875,,,,,,,,,,
MSG,7,0,632,9893C8,732,2014/08/05,12:22:18.092,2014/08/05,12:22:18.092,,48325,,,,,,,,,,0

fr24.png


Used to work before I reinstalled and went with x64. Using fr24feed_x64_242.

[peterhr]

Is there a reason why you don't run the feeder on the Pi - it only uses 5-10% of the Pi resource and someone else with the setup you have has said they got a backlog problem where the Pi couldn't feed data fast enough to the feeder and had a huge backlog of network traffic waiting to go down the pipe. The delay all being due to all Pi network traffic having to go via the USB chipset.

[1gwk]

Hi,

I'm running fr24feed_x86_242 on x86 linux box and dump1090 on raspberry. When dump1090 or raspberry restarts for some reason, fr24feed doesn't recover, it just keeps sending pings.

After i restarts fr24feed, it connects to dump1090 again:

.
.
.
[n]ping 1786
[n]ping 1787
[n]ping 1788
[n]ping 1789

ctrl-z

#> ./fr24feed_x86_242 --fr24key=xxxxxxxxxxxxxx --bs-ip=xx.yyy.0.47
[i]FR24Feed v242 - built on Apr 23 2014/10:19:07
[i]Downloading configuration...OK
[i]Parsing configuration...OK
[c]Interval: 5s
[c]Latitude: 61.xxxx
[c]Longitude: 21.xxxx
[c]GND: YES
[c]NonADSB: YES
[i]Source defined as Basestation
[b]connecting to xx.yyy.0.47:30003
[i][stats]Stats thread started
[n]defined 1 server
[b]connected
[b]working
[n]EFxxx@83.140.21.66:8099/UDP
[n]connecting
[n]connected
[n]switching to UDP
[n]working
[i]Data feed time difference OK abs(19:03:09.153 - 19:03:09.140)=0
[i]sent 4 planes in 1 packets
[i]sent 4 planes in 1 packets
.
.
.

[sergsero]

Supervisord is a nifty daemon for running and monitoring processes.

But I see nothing wrong that System V (SysV) init (/etc/init.d, etc) has survived as long as it has. Looking at its features, it's a pretty plain system, so why is it still here? Maybe because, historically, it has been good enough.

SysV init often forces upon programs common tasks such as PID file management, daemonizing (backgrounding), log management, privilege separation, etc. Most things don't use PID files correctly (nobody locks them), many startup scripts lack a functioning 'status' check, and everyone re-implements the daemonizing and privilege dropping differently and many times incorrectly. Supervisord differs from upstart init.d in that it uses a main background daemon that does the work of starting processes and monitoring their status, along with a UNIX socket file used by the supervisorctl command-line tool to talk to the main controller process.

Sometimes you also need more. What was cool thirty years ago may not be cool today. Supervisord gets you a few more goodies you may find useful.

But you are right in your preferences. And the first phase of this part of topic was: "How to automatically run programs in Linux, each finds his way".

Thanks,
sergsero

[peterhr]

I read this and wonder whay a simple shell scrip wasn't used with a cron @reboot job to start it - all the stuff setting up services is fairly complex for someone new to Linux - and it spreads the startup configuration int more places than may be needed.

[koro]

Hi Sergero,

Thank you very much for all the help...
Wheezy was complete new for me... and i didn't know how to start...
I learned a lot...

Hope to meet you some day...

Hi Ken,




I think that we need to lower case for sbs in options: --outServer sbs10001:10001

Then, in the settings BaseStation.exe, to specify the connection to the IP-address of Raspberry Pi and port 10001.


If everything is configured correctly, RPi will started after power on via microUSB port. The supervisor will automatically start both programs: modesmixer2 and fr24feed with the desired options. Any of your participation will not be required.
What you login to the system via the GUI interface, only adds additional work to the computer and not required for system.

Thanks,
sergsero

[sergsero]

Hi Ken,

Seems to be working fine now... tnx for the effort...

I added also --outServer SBS10001:10001 to see on another pc if i receive something, but i cannot connect via Basestation.

Is there also a way to boot th pi without filling a password and username?
So i can unconnect my keyboard, mouse and screen...

I think that we need to lower case for sbs in options: --outServer sbs10001:10001

Then, in the settings BaseStation.exe, to specify the connection to the IP-address of Raspberry Pi and port 10001.


If everything is configured correctly, RPi will started after power on via microUSB port. The supervisor will automatically start both programs: modesmixer2 and fr24feed with the desired options. Any of your participation will not be required.
What you login to the system via the GUI interface, only adds additional work to the computer and not required for system.

Thanks,
sergsero