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

[kis]

New version has been released 1.0.5-1

Thank you. Great job!

Just found one bug: If settings are saved via settings.html, due to GET-URL-encoding every space in the input-fields is replaced with "+" and leads to invalid parameters like e.g. --net+--modeac etc.

BTW: Are there any default parameters of dump1090 set (--quiet, --net or anything)?

BTW2: Which dataformat uses fr24feed from dump1090 (RAW, Beast, Basestation)? Are there any advantages to use dump1090's --modeac or --net-beast with fr24feed?

Maybe another bug:
In /etc/fr24feed.ini I wrote

procargs="--net --net-http-port 63280 --modeac --lat 52.xxxxxx--lon 9.xxxxxx --aggressive --enable-agc --ppm  44 --net-beast --fix"

The file /var/log/fr24feed.log shows

[reader][i][0]Connecting to Generic receiver via (exe:///usr/lib/fr24/mr-dump1090 --net --net-http-port 63280 --modeac --lat 52.xxxxxx--lon 9.xxxxxx --aggressive --enable-agc )

Is it just a cut off in the logfile or a parameter-cut off at starting dump1090?

[ptl]

Hi,

I installed new version fr24feed_1.0.5-1_armhf.deb and started to use Malcolm Robb dump1090, mainly to get the localhost:8080.

But I cannot get anything from localhost:8080, any ideas?

Here are some details of my set-up

# cat /etc/fr24feed.ini
receiver="dvbt-mr"
fr24key="xxxcensoredxxx"
path="/usr/lib/fr24/mr-dump1090"
bs="no"
raw="no"
logmode="2"
procargs="--net --fix --aggressive --stats-every 3600 --modeac --enable-agc --net-beast"

What are proper parameters for dump1090 (procargs)?

# netstat -l --inet -v -p -n | grep -e dump1090 -e fr24feed
tcp 0 0 0.0.0.0:8080 0.0.0.0:* LISTEN 18731/mr-dump1090
tcp 0 0 0.0.0.0:30001 0.0.0.0:* LISTEN 18731/mr-dump1090
tcp 0 0 0.0.0.0:30002 0.0.0.0:* LISTEN 18731/mr-dump1090
tcp 0 0 0.0.0.0:8754 0.0.0.0:* LISTEN 18714/fr24feed
tcp 0 0 0.0.0.0:30003 0.0.0.0:* LISTEN 18731/mr-dump1090
tcp 0 0 0.0.0.0:30004 0.0.0.0:* LISTEN 18731/mr-dump1090
tcp 0 0 0.0.0.0:30005 0.0.0.0:* LISTEN 18731/mr-dump1090
udp 0 0 0.0.0.0:33694 0.0.0.0:* 18714/fr24feed

BTW, I tried to select logmode 3 during the installation, but was not able to, so I choose 2.

[kis]

I started to test Malcolm Robb dump1090

path="/usr/lib/fr24/dump1090"

The problem I have is that localhost:8080 does not show anything.

The actuall package contains two dump1090 builds:
- antirez's: at "/usr/lib/fr24/dump1090" and
- Malcolm's: at "/usr/lib/fr24/mr-dump1090"

Your fr24feed.ini points to antirez's build without http-support. Just change path-entry to "/usr/lib/fr24/mr-dump1090", restart and see the results in your browser. Also, you don't need your previous dump-installation anymore.

[ptl]

kis, looks like you replied to my message, that I completely changed after installing fr24feed_1.0.5-1_armhf.deb. I did not want
the old message to be left around, since my set-up was changed considerably, and for the better (more fr24-standard) i think.

Before that I used separately built Malcolm's dump1090, but the problem was identical, cannot get anything from localhost:8080

But now I'm using just what came with fr24feed_1.0.5-1_armhf.deb, and I do use mr-dump1090, see the .ini in my previous post.

-Paavo

[ptl]

Question: where do the mr-dump1090 logs go? These would be quite useful for me since I need to start tuning the antennas.

Example rom my other receiver which has dump1090 from https://github.com/MalcolmRobb/dump1090 and fr24feed_x64_242, just 600 secs in this:

Statistics as at Sat Nov 8 20:20:10 2014
9170 sample blocks processed
0 sample blocks dropped
0 ModeA/C detected
589126 valid Mode-S preambles
3 DF-?? fields corrected for length
4 DF-?? fields corrected for type
243 demodulated with 0 errors
41 demodulated with 1 error
8 demodulated with 2 errors
3 demodulated with > 2 errors
241 with good crc
54 with bad crc
54 errors corrected
33 with 1 bit error
21 with 2 bit errors
295 total usable messages

and

*8d461f6258c90336e78582556a79;
CRC: 000000 (ok)
DF 17: ADS-B message.
Capability : 5 (Level 2+3+4 (DF0,4,5,11,20,21,24,code7 - is airborne))
ICAO Address : 461f62
Extended Squitter Type: 11
Extended Squitter Sub : 0
Extended Squitter Name: Airborne Position (Baro Altitude)
F flag : even
T flag : non-UTC
Altitude : 39000 feet
Latitude : 64.821671
Longitude: 25.354907

*8d461f62994017b828048f26f1c9;
CRC: 4e7c9b (wrong)
No. of bit errors fixed: 2
DF 17: ADS-B message.
Capability : 5 (Level 2+3+4 (DF0,4,5,11,20,21,24,code7 - is airborne))
ICAO Address : 461f62
Extended Squitter Type: 19
Extended Squitter Sub : 1
Extended Squitter Name: Airborne Velocity
EW status : Valid
EW velocity : 22
NS status : Valid
NS velocity : -448
Vertical status : Valid
Vertical rate src : 0
Vertical rate : 0

[papasven]

Before that I used separately built Malcolm's dump1090, but the problem was identical, cannot get anything from localhost:8080

I compile dump1090 always with fixed web-dir path. (usr/share/dump1090)

1. Option change a line in dump1090.h

from

#define HTMLPATH   "./public_html"      // default path for gmap.html etc

in

#define HTMLPATH   "/usr/share/dump1090"      // default path for gmap.html etc

2. Option add line in Makefile

PREFIX=/usr

edit: and of course then run make

and then copy the public_html folder to usr/share an rename to dump1090

[ptl]

Looks like mr-dump1090 that came with fr24feed_1.0.5-1_armhf.deb uses the default:

# strings /usr/lib/fr24/mr-dump1090 | grep public
./public_html

Would /usr/lib/fr24/public_html work better?

# ls -axl /usr/lib/fr24/public_html/
total 68
drwxr-xr-x 3 1000 1000 4096 Nov 8 13:24 .
drwxr-xr-x 3 root root 4096 Nov 8 13:24 ..
-rw-r--r-- 1 1000 1000 1157 Nov 7 09:33 config.js
drwxr-xr-x 2 1000 1000 4096 Nov 8 13:24 coolclock
-rw-r--r-- 1 1000 1000 627 Nov 7 09:33 extension.js
-rw-r--r-- 1 1000 1000 2603 Nov 7 09:33 gmap.html
-rw-r--r-- 1 1000 1000 433 Nov 7 09:33 options.js
-rw-r--r-- 1 1000 1000 8894 Nov 7 09:33 planeObject.js
-rw-r--r-- 1 1000 1000 20936 Nov 7 09:33 script.js
-rw-r--r-- 1 1000 1000 1444 Nov 7 09:33 style.css

-Paavo

[papasven]

Mhh

I have tested with this fr24feed.ini and it's work http://raspberrypi:8080/

receiver="dvbt-mr"
fr24key="blablakey"
path="/usr/lib/fr24/mr-dump1090"
bs="no"
raw="no"
logmode="2"
procargs="--net"

Do you have an error message (Error opening HTML file: No such file or directory) or no planes.

Normally I use Mode-S Beast running on another pc, does not work so well with raspberrypi probably need a stronger power supply.

[ptl]

I have absolutely nothing from localhost:8080.

# curl localhost:8080
curl: (56) Recv failure: Connection reset by peer
# netstat -l --inet -v -p -n | grep 8080
tcp 0 0 0.0.0.0:8080 0.0.0.0:* LISTEN 23030/mr-dump1090

This is what I'm using now:

receiver="dvbt-mr"
fr24key="something"
path="/usr/lib/fr24/mr-dump1090"
bs="no"
raw="no"
logmode="2"
procargs="--net --fix --aggressive --quiet"

I'll try just --net next.

[ptl]

I'll try just --net next.

Still nothing from 8080... :-(

[ptl]

Hi,

I switched to dump1090 from https://github.com/MalcolmRobb/dump1090, and now running fr24feed_arm-rpi_242 on top of that.
I'm sure I could have used /usr/lib/fr24/mr-dump1090 but now both my receivers (this Raspi and a Fedora 20 box) have very similar set-up
and I can use same start-up and monitoring tools (scripts).

I got nothing from 8080 before I rebooted the Raspi, but now everything works OK.
Weird, rebooting very rarely helps with Linux, but in this case I did not know what else I could have tried.

Now I also get --stats-every 600 info. See this for more details of what I did:

http://forum.flightradar24.com/threads/4270-Linux-feeder-software-for-Flightradar24?p=58975&viewfull=1#post58975

I'll stick to this set-up until I have the antenna done, and then I'll return to fr24deed service.

-Paavo

[piopawlu]

The "fr24feed_arm-rpi_242" will soon be phased out.. the point of doing all this is to have the same decoder everywhere so we can trust the data and fix bugs quickly if we find some.

The included Malcolm Robb's version should work out of the box,, tested it multiple times and it should read public_html from /usr/lib/fr24. This is the command line as used on one of our test RPis:

/usr/lib/fr24/mr-dump1090 --net --net-http-port 8080 --raw

with working directory set to /usr/lib/fr24/.

The URL encoding bug (changing spaces to "+") will be fixed today as well as the command line truncation problem.

[ptl]

Sounds good to me.

My wish list:
- Package dump1090 separately (or has someone done this already?)
- Run dump1090 in a separate daemon like service dump1090 start|stop|restart|status (and systemctl ...)
- Separate config for dump1090 e.g. /etc/dump1090.conf to allow easy use of custom params like with/without --net
- Improve dump1090 configuration so that the HTMLPATH can also be configured normally (and not only build-time)
- Allow fr24feed to use dump1090 running in a different host, use hostCOLONport style config to connect to dump1090
- And perhaps, allow fr24feed to use more than one dump1090? Assuming those are same enough location

-Paavo

[kis]

Package dump1090 separately (or has someone done this already?)

Just start dump1090, configure fr24feed to use a receiver something with TCP and points to localhost:<your prefered dump1090-Port>.

Run dump1090 in a separate daemon like service dump1090 start|stop|restart|status (and systemctl ...)

See : http://www.satsignal.eu/raspberry-pi/dump1090.html (search for: "Starting the dump1090 program automatically")

Separate config for dump1090 e.g. /etc/dump1090.conf to allow easy use of custom params like with/without --net

Set the PROG_ARGS in the above refered script

Improve dump1090 configuration so that the HTMLPATH can also be configured normally (and not only build-time)

I think this should be a request to Malcolm (https://github.com/MalcolmRobb/dump1090)

Allow fr24feed to use dump1090 running in a different host, use hostCOLONport style config to connect to dump1090

This is already possible. I think you should run "service fr24feed start" and browse to localhost:8754/settings.html

And perhaps, allow fr24feed to use more than one dump1090? Assuming those are same enough location

http://www.satsignal.eu/raspberry-pi/dump1090.html (search for: "Running two Raspberry Pi cards on different sides of the house")

[kis]

The URL encoding bug (changing spaces to "+") will be fixed today as well as the command line truncation problem.

Works good. My cosmetic-wishlist for settings.html: longer input-field for "Process arguments". Also another font-type (e.g. courier) for the input fields. Because two dahses look like one long dash, which may leads to typos in the "Process arguments"-field.

In case of upgrading to a new version, a backup of /usr/lib/fr24/public_html/ should be provided, at least for config.js.