Archived - Beta test MLAT software for Raspberry Pi

[yuvadm]

I'm trying to run the new fr24feed software with the following configuration: feeding server is pulling SBS1 data over TCP from port 30003 on a remote device that is running antirez's original dump1090 (i.e. https://github.com/antirez/dump1090#port-30003)

Up until now I was running the legacy client using fr24feed_x64_241 --fr24key=abcd --bs-ip=example.com --bs-port=30003 (where example.com is the IP of the device running dump1090)

What is the equivalent of this on the new client? I can't seem to find any configuration that works, and the lack of docs isn't helping :/

[giacomo892]

RPI MLAT aided positions. This also work for MLAT6

[malavanehsan]

What's Meanning Of T_MLAT7?

[DerMarienfelder]

Look at the First Page :-)

[mbirth]

Could you explain to me how I add the repository certificate please?

sudo apt-key adv --keyserver pgp.mit.edu --recv-keys 40c430f5

[m0bob]

Could you explain to me how I add the repository certificate please?

Thanks.

Bob.

[DerMarienfelder]

Probably not added the repository certificate first. It won't know where to find it

Sent from my XT1092 using Tapatalk

Thx now it works

[Oblivian]

After i do the first steps i try to install fr24
$ sudo apt-get update
$ sudo apt-get install fr24feed
E: Unable to locate package fr24feed
Please help me i use raspbian jessy

Probably not added the repository certificate first. It won't know where to find it

Sent from my XT1092 using Tapatalk

[DerMarienfelder]

After i do the first steps i try to install fr24
$ sudo apt-get update
$ sudo apt-get install fr24feed
E: Unable to locate package fr24feed
Please help me i use raspbian jessy

[valentajn]

What is this?
pi@pi ~ $ sudo service fr24feed status
Б≈▐ fr24feed.service - LSB: Flightradar24 Decoder & Feeder
Loaded: loaded (/etc/init.d/fr24feed)
Active: active (running) since Fri 2015-10-30 20:27:19 EET; 3min 57s ago
Process: 480 ExecStart=/etc/init.d/fr24feed start (code=exited, status=0/SUCCE
CGroup: /system.slice/fr24feed.service
Б■°Б■─559 /usr/bin/fr24feed -- --monitor-file=/dev/shm/fr24feed.txt -
Б■■Б■─593 /usr/lib/fr24/dump1090 --raw --mlat

Oct 30 20:27:19 pi fr24feed[480]: Starting FR24 feeder: fr24feed.
Oct 30 20:27:19 pi systemd[1]: Started LSB: Flightradar24 Decoder & Feeder.

[lcsneil]

Bob

Are you trying to use any other feeders on the Raspberry pi to other sites?

Are you getting raw data out on <your pi IP address>ort

Where port is 3002,3003 or 3005?

I had the same issue and it was a mis configuration of the FR24 feeder. (Caused after a Wifi dongle failure of all things which somehow broke the config!!)

lcs

m0bob,

Do you have anything exciting about your dongle in 'dmesg' output?
Also try connecting it directly without a power hub.

[m0bob]

Hi again,

I did what you suggested and this is what was displayed. There is obviously an error, but I am not sure what and how to deal with it.

Thanks,

Bob.

rtlsdr_demod_write_reg failed with -4
rtlsdr_demod_read_reg failed with -4
rtlsdr_demod_write_reg failed with -4
rtlsdr_demod_read_reg failed with -4
rtlsdr_demod_write_reg failed with -4
rtlsdr_demod_read_reg failed with -4
rtlsdr_demod_write_reg failed with -4
rtlsdr_demod_read_reg failed with -4
rtlsdr_demod_write_reg failed with -4
rtlsdr_demod_read_reg failed with -4
Exact sample rate is: 2000000.052982 Hz
rtlsdr_demod_write_reg failed with -4
rtlsdr_demod_read_reg failed with -4
rtlsdr_demod_write_reg failed with -4
rtlsdr_demod_read_reg failed with -4
rtlsdr_demod_write_reg failed with -4
rtlsdr_demod_read_reg failed with -4
rtlsdr_demod_write_reg failed with -4
rtlsdr_demod_read_reg failed with -4
rtlsdr_demod_write_reg failed with -4
rtlsdr_demod_read_reg failed with -4
rtlsdr_demod_write_reg failed with -4
rtlsdr_demod_read_reg failed with -4
rtlsdr_write_reg failed with -4
rtlsdr_write_reg failed with -4
Gain reported by device: 0.00
Failed to submit transfer 0!
2015-10-28 21:58:47 | [time][i]Synchronizing time via NTP
2015-10-28 21:58:52 | [time][i]Time synchronized correctly, offset +0.0006 seconds
2015-10-28 21:58:52 | [main][i]Feed Network client started
2015-10-28 21:58:52 | [main][i]RAW data server started
2015-10-28 21:58:52 | [raw][i]Initializing server
2015-10-28 21:58:52 | [raw][i]Starting server on 0.0.0.0:30002
2015-10-28 21:58:52 | [raw][e]Could not bind socket to *:30002, errno=98
2015-10-28 21:58:52 | [feed][i]Downloading configuration
2015-10-28 21:58:52 | [feed][c]Interval: 5s
2015-10-28 21:58:52 | [feed][c]Latitude: 51.5943
2015-10-28 21:58:52 | [feed][c]Longitude: 0.2230
2015-10-28 21:58:52 | [feed][c]GND: YES
2015-10-28 21:58:52 | [feed][c]NonADSB: YES
2015-10-28 21:58:52 | [feed][c]Timestamps: optional
2015-10-28 21:58:52 | [feed][c]Max range AIR: 350.0nm
2015-10-28 21:58:52 | [feed][c]Max range GND: 100.0nm
2015-10-28 21:58:52 | [feed][i]defined 1 server
2015-10-28 21:58:52 | [feed][n]EGLC51@83.140.21.66:8099/UDP
2015-10-28 21:58:52 | [feed][n]connecting
2015-10-28 21:58:52 | [stats][i]Stats thread started
2015-10-28 21:58:52 | [mlat][i]MLAT configuration received, service ENABLED
2015-10-28 21:58:52 | [mlat][i]Starting MLAT with preconfigured position: 51.59,0.22,40.0
2015-10-28 21:58:52 | [mlat][i]MLAT bandwidth reduction active, level 1
2015-10-28 21:58:52 | [mlat][i]Configuring UDP connection udp://mlat-1.fr24.com:19788
2015-10-28 21:58:52 | [mlat][i]Registering MLAT station
-10-28 21:59:07 | [mlat][i]Pinging the server
2015-10-28 21:59:07 | [mlat][i]Stats 0/0
2015-10-28 21:59:12 | [feed][n]connected via TCP
2015-10-28 21:59:12 | [feed][n]switching to UDP
2015-10-28 21:59:12 | [feed][n]working
2015-10-28 21:59:27 | [mlat][i]Pinging the server
2015-10-28 21:59:27 | [mlat][i]Stats 0/0
2015-10-28 21:59:42 | [feed][n]ping 1
2015-10-28 21:59:47 | [mlat][i]Pinging the server
2015-10-28 21:59:47 | [mlat][i]Stats 0/0
^[[A2015-10-28 22:00:07 | [mlat][i]Pinging the server
2015-10-28 22:00:07 | [mlat][i]Stats 0/0
2015-10-28 22:00:12 | [feed][n]ping 2
2015-10-28 22:00:27 | [mlat][i]Pinging the server
2015-10-28 22:00:27 | [mlat][i]Stats 0/0
2015-10-28 22:00:42 | [feed][n]ping 3

[Oblivian]

If you drop the service you will get more output to diagnose from

sudo service fr24feed stop
sudo fr24feed start

That will let you see the startup procedure and any errors/issues contacting the USB stick. Does the version have the right frequency range?

[m0bob]

Raspberry Pi problem with RTL2838UH Dongle - Not receiving any aircraft to upload

Hi there,

I have been using Windows 10 to share flight data without problems.

I decided to use my Raspberry Pi to share data with Flightradar24 and followed the online installation instructions so that I could use my RTL2838UH Dongle. I am not sure why, but I am not receiving any aircraft to upload and I'm uncertain what to do next.

My set-up is as follows:
Raspberry Pi type B
a powered hub
a loft antenna fed with a short length of RG213

I used the following command "service fr24feed status" and this is the result.

pi@raspberrypi ~ $ service fr24feed status
[ ok ] FR24 Feeder/Decoder Process: running.
[ ok ] FR24 Stats Timestamp: 2015-10-28 13:45:11.
[ ok ] FR24 Link: connected [UDP].
[ ok ] FR24 Radar: T-EGLC51.
[ ok ] FR24 Tracked AC:.
[ ok ] Receiver: connected (0 MSGS/0 SYNC).
[ ok ] FR24 MLAT: ok [UDP].
[ ok ] FR24 MLAT AC seen: 0.

My home location is London, so there are plenty of aircraft nearby.

I have checked my antenna and it is connected.

Could it be a driver issue?

I am new to Raspberry Pi, so any help would be gratefully received.

Many thanks,

Bob.