Flightradar24 decoder/feeder BETA testing (Win/RPi/Linux/OSX)

[YSCB8]

New test build 1.0.10-2 available for RPi and Windows:

I would appreciate some testing, so I can release it on Wednesday.. Will try to address other issues before that too.

I'm running it now and can't see any issues. (Windows Version)

[Wolli]

1.0.10-2 seems OK (as far as I can see)

I'm running it now and can't see any issues.

Yep, I agree.

Dear Piotr, a happy New Year to you and your beloved ones.

I'm running "1.0.10-2" for several hours now. Seems ok (Windows version - config here: Windows Vista, Jetvision dongle). A good idea that you now printout date & time in the console messages. I missed that in previous releases. Kind regards, -Wolli-

[eshabi]

Few issues with the new Windows version configuration (Windows 7, dvbt dongle):

• 1st time configuration process asks twice about enabling the Raw data port (30002) although the 2nd question enables/disables the BS port (30003).

• 1st time configuration process never finished (tried several times). Had to kill the process.

• What is the format to enter when it asks for log path? Windows style path or UNIX style? include the log file name or just the path?

[piopawlu]

Thanks for your prompt feedback. We have a day off today in Sweden, but tomorrow we are back at full speed. I will include fixes to mentioned problems and if there's enough time check the OSX nib problem as well.

[trigger]

New test build 1.0.10-2 available for RPi and Windows:

Changelog:
- Fixed seg-fault and corrupted config file on save


RPi DEB: http://feed.flightradar24.com/raspbe...10-2_armhf.deb


I would appreciate some testing, so I can release it on Wednesday.. Will try to address other issues before that too.

Hi piopawlu,
The segment fault on saving the .ini file is OK now but running fr24feed --reconfigure the prompts seem to have extra data and I have to press return twice on entering some parameters. After entering the last parameter I have to Ctrl C to get back to a prompt.
I've been running 1.0.10-2_armhf.deb all day with no problems.

Thanks

[giacomo892]

Latest version on RPi is feeding great Thanks piopawlu

[piopawlu]

New build 1.0.10-3 is available for all platforms, from the main download site, that includes also OSX fix.

[equi]

What are the changes ?

[piopawlu]

What are the changes ?

Mostly fixes.. reconfiguration,, no more timestamps in signup process, OSX build fixed, etc. If you have a stable ride with 1.0.10-2 you don't need to upgrade.

[equi]

Thank you for your prompt answer, i have a really good ride with 1.0.9-2 atm

[piopawlu]

Tomorrow I will update the manual.. there are a few new parameters as well as a few that were not documented before.

[trigger]

Just loaded 1.0.10-3 and I'm still having problems with the fr24feed.ini file.

--reconfigure works fine and creates the .ini file OK.

But I still get this after doing a "sudo service fr24feed status"

[ok]FR24 feeder/decoder process:running
[ok]FR24 Stats timestamp:2015-01-01 10:42
[ok]FR24 link:connected[UDP]
[ok]FR24 Radar:T-EGUB1
[ok]FR24 Tracked AC: .
[Fail] Receiver: down ... failed!

Looking at the output from command "top" I can see dump1090 trying to start. It keeps popping up at the top of the list, then disappears, then pops up again. FR24feed is running constantly.

If I take out all the parameters in FR24feed.ini except "receiver" and "fr24key", I start to feed, no errors and "top" shows the 2 applications running fine.

I'm not the only one with this problem http://forum.flightradar24.com/threa...ll=1#post61305

We are both beginners so there may well be something obvious we have missed.
Thanks

[YSCB8]

I was having a comfortable ride on 1.0.10-2 too but I upgraded to 1.0.10-3 anyway. So far no turbulence noticed yet (Win32).
Still never seems to show me as a tracker of aircraft in FR24 though it shows in my account page.

[trigger]

Just loaded 1.0.10-3 and I'm still having problems with the fr24feed.ini file.

--reconfigure works fine and creates the .ini file OK.

But I still get this after doing a "sudo service fr24feed status"

[ok]FR24 feeder/decoder process:running
[ok]FR24 Stats timestamp:2015-01-01 10:42
[ok]FR24 link:connected[UDP]
[ok]FR24 Radar:T-EGUB1
[ok]FR24 Tracked AC: .
[Fail] Receiver: down ... failed!

Looking at the output from command "top" I can see dump1090 trying to start. It keeps popping up at the top of the list, then disappears, then pops up again. FR24feed is running constantly.

If I take out all the parameters in FR24feed.ini except "receiver" and "fr24key", I start to feed, no errors and "top" shows the 2 applications running fine.

I'm not the only one with this problem http://forum.flightradar24.com/threa...ll=1#post61305

We are both beginners so there may well be something obvious we have missed.
Thanks

piopawlu has sorted this problem for me via email.
The path in fr24feed.ini has to have the binary name in it, eg path="/usr/lib/fr24/dump1090"
I was missing off the binary name

[eshabi]

I've noticed that for several times the feeder (latest build on Win7) stopped receiving signals or stopped displaying and sending them and started pinging the server(?) for several hours.
I'm terminating the feeder, have to kill the mr-dump1090 process as it did not stopped, run the feeder again and it starts to receive and send signals immediately.

This is the content of the log file when it happened for the last time. It kept pinging for several hours till I noticed it:

2015-01-09 04:25:13 | [feed][i]sent 2 AC in 1 packet
2015-01-09 04:25:18 | [feed][i]sent 2 AC in 1 packet
2015-01-09 04:25:23 | [feed][i]sent 3 AC in 1 packet
2015-01-09 04:25:28 | [feed][i]sent 2 AC in 1 packet
2015-01-09 04:25:33 | [feed][i]sent 1 AC in 1 packet
2015-01-09 04:26:03 | [feed][n]ping 1
2015-01-09 04:26:33 | [feed][n]ping 2
2015-01-09 04:27:03 | [feed][n]ping 3
2015-01-09 04:27:33 | [feed][n]ping 4
2015-01-09 04:28:03 | [feed][n]ping 5
2015-01-09 04:28:33 | [feed][n]ping 6
2015-01-09 04:29:04 | [feed][n]ping 7
2015-01-09 04:29:34 | [feed][n]ping 8
2015-01-09 04:30:04 | [feed][n]ping 9
2015-01-09 04:30:34 | [feed][n]ping 10
2015-01-09 04:31:04 | [feed][n]ping 11
2015-01-09 04:31:34 | [feed][n]ping 12
2015-01-09 04:32:04 | [feed][n]ping 13
2015-01-09 04:32:34 | [feed][n]ping 14
2015-01-09 04:32:48 | [stats][i]sent 95 bytes
2015-01-09 04:33:04 | [feed][n]ping 15
2015-01-09 04:33:35 | [feed][n]ping 16
2015-01-09 04:34:05 | [feed][n]ping 17
2015-01-09 04:34:21 | [time][i]Synchronizing time via NTP
2015-01-09 04:34:25 | [time][i]Time synchronized correctly, offset +1.0223 seconds, drift 0.0028 seconds/minute
2015-01-09 04:34:35 | [feed][n]ping 18
2015-01-09 04:35:05 | [feed][n]ping 19
.
.
2015-01-09 08:24:16 | [main][i]FR24 Feeder/Decoder [0x02107000]
2015-01-09 08:24:16 | [main][i]Version: 1.0.10-3/generic
2015-01-09 08:24:17 | [main][i]Built on Jan 7 2015 16:10:51 (r:284/Windows/i386)
2015-01-09 08:24:17 | [main][i]Copyright 2008-2015 (c) Piotr Pawluczuk
2015-01-09 08:24:17 | [main][i]Flightradar24 AB(http://flightradar24.com)
.
2015-01-09 08:24:20 | [feed][n]connecting
2015-01-09 08:24:20 | [stats][i]Stats thread started
2015-01-09 08:24:21 | [feed][n]connected
2015-01-09 08:24:21 | [feed][n]switching to UDP
2015-01-09 08:24:21 | [feed][n]working
2015-01-09 08:24:27 | [feed][i]sent 2 AC in 1 packet
2015-01-09 08:24:31 | [feed][i]sent 3 AC in 1 packet
2015-01-09 08:24:36 | [feed][i]sent 3 AC in 1 packet