Page 23 of 91 FirstFirst ... 1321222324253373 ... LastLast
Results 221 to 230 of 901

Thread: Archived - Beta test MLAT software for Raspberry Pi

  1. #221
    Passenger
    Join Date
    Nov 2014
    Posts
    31
    Quote Originally Posted by vinnyspb View Post
    Hi bhaal,

    Thanks for the constructive criticism, but you described exactly the algorithm we've implemented here. There is no rely on NTP-only timestamps. We sync those timestamps across ADS-B traffic server-side, simultaneously visible between 3 Raspberry Pi receivers and 1 FR24 receiver that has exact precise GPS time aligned with Mode-S signal. Positions uncertainty is of course a problem, and we will definitely work on improving the quality. I understand your frustration about vendor-lock for dump1090 - that might be improved in future.
    You asked for a link to sources: https://github.com/flightradar24/dump1090
    If you're using ADS-B as a reference beacon anyway, why do you need to modify the 12MHz timestamp into Radarcape-style seconds-since-midnight format? You don't care about the absolute time of arrival.
    By doing this conversion using the system clock, you're introducting potentially large errors because you have no guarantee that buffers of samples arrive at regular intervals as measured by the system clock.

    (This is why mlat-server and FA's implementation which is built on it are unlikely to ever support this type of converted timestamp)

  2. #222
    Passenger
    Join Date
    Aug 2015
    Posts
    4

    Unhappy

    Quote Originally Posted by oroblraM View Post
    Hi vinnyspb

    I'm new to FR24feed, but "listening" here since a long time...

    A little suggestion: Is it possible to show version informations like shown below
    (or anyhow you think)

    pi@raspberrypi ~ $ sudo service fr24feed status
    [ INFO ] running Version: 1.0.14 Build: 5 ____ newest Version: 1.0.14 Build: 7
    [AutoUpdate] disabled
    [ UpTime ] 7h 5m 12s

    [ ok ] FR24 Feeder/Decoder Process: running.
    [ ok ] FR24 Stats Timestamp: 2015-08-01 19:48:46.
    [ ok ] FR24 Link: connected [UDP].
    [ ok ] FR24 Radar: T-EDMS6
    [ ok ] FR24 Tracked AC: 70.
    [ ok ] Receiver: connected (55402 MSGS/0 SYNC).
    [ ok ] FR24 MLAT: ok [UDP].
    [ ok ] FR24 MLAT AC seen: 69.
    pi@raspberrypi ~ $

    Greets out of Bavaria

    Stefan

    btw: What's trying to tell me: " 0 SYNC" ?????

    no reply to my suggestion or my btw-question??? surprises even me.......

  3. #223
    Passenger
    Join Date
    Mar 2015
    Location
    Germany
    Posts
    3
    Hi,

    I have a RPi2 running since March 2015 and everything was fine. 3 days ago I started the installation for beta testing phase of MLAT. Since then I have a problem. I started the installation as vinnyspb stated on page 1 of this thread. After installation I signed up with my sharing key and restarted the RPI2. The result was as below.

    $ sudo service fr24feed status
    [ ok ] FR24 Feeder/Decoder Process: running.
    [ ok ] FR24 Stats Timestamp: 2015-08-05 08:47:30.
    [ ok ] FR24 Link: connected [UDP].
    [ ok ] FR24 Radar: T-EDWI8.
    [ ok ] FR24 Tracked AC:.
    [FAIL] Receiver: down ... failed!
    [ ok ] FR24 MLAT: ok [UDP].
    [ ok ] FR24 MLAT AC seen: 0.

    The logfile says this:

    2015-08-05 08:34:46 | [main][i]FR24 Feeder/Decoder [0x02117000]
    2015-08-05 08:34:46 | [main][i]Version: 1.0.14-7/generic
    2015-08-05 08:34:46 | [main][i]Built on 20150731-1055 (r:master-5e970cb.git/Linux/armv7l)
    2015-08-05 08:34:46 | [main][i]Copyright 2008-2015 (c) Piotr Pawluczuk
    2015-08-05 08:34:46 | [main][i]Flightradar24 AB
    2015-08-05 08:34:46 | [main][i]DNS mode: LIBC
    2015-08-05 08:34:46 | ERROR
    2015-08-05 08:34:46 | [httpd][i]Server started, listening on 0.0.0.0:8754
    2015-08-05 08:34:46 | [main][i]Reader 0 started
    2015-08-05 08:34:46 | [reader][i][0]Initializing reader
    2015-08-05 08:34:46 | [main][i]MLAT data feed started
    2015-08-05 08:34:46 | [reader][i][0]Connecting to Generic receiver via (exe:///usr/lib/fr24/dump1090 --raw --mlat)
    2015-08-05 08:34:46 | [master][i]Starting processing thread
    2015-08-05 08:34:46 | [reader][i][0]Connected to the receiver, authenticating
    2015-08-05 08:34:46 | [mlat][i]Waiting for MLAT configuration
    2015-08-05 08:34:46 | [reader][i][0]Authenticated, processing messages
    2015-08-05 08:34:46 | [reader][i][0]Connection terminated
    2015-08-05 08:34:46 | [main][i]Terminating child process 19522 with SIGETERM
    2015-08-05 08:34:47 | [time][i]Synchronizing time via NTP
    2015-08-05 08:34:50 | [time][i]Time synchronized correctly, offset +0.0001 seconds
    2015-08-05 08:34:50 | [main][i]Feed Network client started
    2015-08-05 08:34:50 | [feed][i]Downloading configuration
    2015-08-05 08:34:50 | [main][i]RAW data server started
    2015-08-05 08:34:50 | [raw][i]Initializing server
    2015-08-05 08:34:50 | [raw][i]Starting server on 0.0.0.0:30002
    2015-08-05 08:34:50 | [raw][e]Could not bind socket to *:30002, errno=98
    2015-08-05 08:34:51 | [feed][c]Interval: 5s
    2015-08-05 08:34:51 | [feed][c]Latitude: 53.5073
    2015-08-05 08:34:51 | [feed][c]Longitude: 8.0524
    2015-08-05 08:34:51 | [feed][c]GND: YES
    2015-08-05 08:34:51 | [feed][c]NonADSB: YES
    2015-08-05 08:34:51 | [feed][c]Timestamps: optional
    2015-08-05 08:34:51 | [feed][c]Max range AIR: 350.0nm
    2015-08-05 08:34:51 | [feed][c]Max range GND: 100.0nm
    2015-08-05 08:34:51 | [feed][i]defined 1 server
    2015-08-05 08:34:51 | [stats][i]Stats thread started
    2015-08-05 08:34:51 | [feed][n]EDWI8@83.140.21.66:8099/UDP
    2015-08-05 08:34:51 | [feed][n]connecting
    2015-08-05 08:34:51 | [mlat][i]MLAT configuration received, service ENABLED
    2015-08-05 08:34:51 | [mlat][i]Starting MLAT with preconfigured position: 53.51,8.05,72.0
    2015-08-05 08:34:51 | [mlat][i]MLAT bandwidth reduction active, level 1
    2015-08-05 08:34:51 | [mlat][i]Configuring UDP connection udp://mlat-1.fr24.com:19788
    2015-08-05 08:34:51 | [mlat][i]Registering MLAT station
    2015-08-05 08:34:51 | [mlat][i]Registering MLAT station: SUCCESS
    2015-08-05 08:34:52 | [reader][i][0]Connecting to Generic receiver via (exe:///usr/lib/fr24/dump1090 --raw --mlat)
    2015-08-05 08:34:52 | [reader][i][0]Connected to the receiver, authenticating
    2015-08-05 08:34:52 | [reader][i][0]Authenticated, processing messages
    2015-08-05 08:34:52 | [reader][i][0]Connection terminated
    2015-08-05 08:34:52 | [main][i]Terminating child process 19526 with SIGETERM
    2015-08-05 08:34:57 | [reader][i][0]Connecting to Generic receiver via (exe:///usr/lib/fr24/dump1090 --raw --mlat)
    2015-08-05 08:34:57 | [reader][i][0]Connected to the receiver, authenticating
    2015-08-05 08:34:57 | [reader][i][0]Authenticated, processing messages
    2015-08-05 08:34:57 | [reader][i][0]Connection terminated
    2015-08-05 08:34:57 | [main][i]Terminating child process 19527 with SIGETERM
    2015-08-05 08:35:03 | [reader][i][0]Connecting to Generic receiver via (exe:///usr/lib/fr24/dump1090 --raw --mlat)
    2015-08-05 08:35:03 | [reader][i][0]Connected to the receiver, authenticating
    2015-08-05 08:35:03 | [reader][i][0]Authenticated, processing messages
    2015-08-05 08:35:03 | [reader][i][0]Connection terminated
    2015-08-05 08:35:03 | [main][i]Terminating child process 19528 with SIGETERM
    2015-08-05 08:35:07 | [mlat][i]Pinging the server
    2015-08-05 08:35:07 | [mlat][i]Stats 15675087/2339
    2015-08-05 08:35:08 | [reader][i][0]Connecting to Generic receiver via (exe:///usr/lib/fr24/dump1090 --raw --mlat)
    2015-08-05 08:35:08 | [reader][i][0]Connected to the receiver, authenticating
    2015-08-05 08:35:08 | [reader][i][0]Authenticated, processing messages
    2015-08-05 08:35:09 | [reader][i][0]Connection terminated
    2015-08-05 08:35:09 | [main][i]Terminating child process 19529 with SIGETERM
    2015-08-05 08:35:11 | [feed][n]connected via TCP
    2015-08-05 08:35:11 | [feed][n]switching to UDP
    2015-08-05 08:35:11 | [feed][n]working
    2015-08-05 08:35:14 | [reader][i][0]Connecting to Generic receiver via (exe:///usr/lib/fr24/dump1090 --raw --mlat)
    As a result, I did not get the RPI running. I have signed up at least 5 times with automatic / individual configuration, editing the fr24.ini file etc. Nothing changed.
    The dump1090 Webinterface shows all adsb and non adsb aircraft as usuall. It seems to be a failure of connecting to fr24 server.

    Can anybody help me to find a solution for the problem?

    Thank you

    problem has been solved !!
    Last edited by terra; 2015-08-08 at 15:23. Reason: problem has been solved
    F-EDWI3 - FR24-Box | T-EDWI8 - Raspberry Pi 2

  4. #224
    Purser
    Join Date
    Jan 2015
    Location
    Kallangur, Brisbane
    Posts
    168
    Quote Originally Posted by vinnyspb View Post
    Hi bhaal,

    Thanks for the constructive criticism, but you described exactly the algorithm we've implemented here. There is no rely on NTP-only timestamps. We sync those timestamps across ADS-B traffic server-side, simultaneously visible between 3 Raspberry Pi receivers and 1 FR24 receiver that has exact precise GPS time aligned with Mode-S signal. Positions uncertainty is of course a problem, and we will definitely work on improving the quality. I understand your frustration about vendor-lock for dump1090 - that might be improved in future.
    You asked for a link to sources: https://github.com/flightradar24/dump1090
    Alright, I guess the whole NTP sync thing is what put me on the wrong track with the way the FR MLAT system worked, and as with what obj has asked.. Why modifying timestamps? As I have said before, if you want to modify timestamps do it at the server end rather than trying to reinvent the wheel, also the knock-on effect of doing it client side is as you have seen others mention: it increases cpu load dramatically.. I think the only way you are going to get more accurate MLAT data is to bring the future forward faster and move to non-vendor locked dump1090.. This will bring more ADS-B feeders into your MLAT circle..
    T-YBBN50 - Kallangur, QLD, Australia

  5. #225
    Passenger
    Join Date
    Apr 2015
    Posts
    8
    If it is any help here is the start of my log

    2015-07-30 18:50:05 | [main][i]FR24 Feeder/Decoder [0x02117000]
    2015-07-30 18:50:05 | [main][i]Version: 1.0.14-5/generic
    2015-07-30 18:50:05 | [main][i]Built on 20150717-1545 (r:master-e0237e1.git/Linux/armv7l)
    2015-07-30 18:50:05 | [main][i]Copyright 2008-2015 (c) Piotr Pawluczuk
    2015-07-30 18:50:05 | [main][i]Flightradar24 AB(http://flightradar24.com)
    2015-07-30 18:50:05 | [main][i]DNS mode: LIBC
    2015-07-30 18:50:06 | ERROR
    2015-07-30 18:50:06 | [w]Detected --net argument for dump1090, disabling internal RAW feed!
    2015-07-30 18:50:06 | [w]Detected --net argument for dump1090, disabling internal BS feed!
    2015-07-30 18:50:06 | [httpd][i]Server started, listening on 0.0.0.0:8754
    2015-07-30 18:50:06 | [main][i]Reader 0 started
    2015-07-30 18:50:06 | [master][i]Starting processing thread
    2015-07-30 18:50:06 | [main][i]MLAT data feed started
    2015-07-30 18:50:06 | [reader][i][0]Initializing reader
    2015-07-30 18:50:06 | [mlat][i]Waiting for MLAT configuration
    2015-07-30 18:50:06 | [reader][i][0]Connecting to Generic receiver via (exe:///usr/lib/fr24/dump1090 --net --gain -10 --net-http-port 8081 --ppm 12 --raw --mlat)
    2015-07-30 18:50:06 | [reader][i][0]Connected to the receiver, authenticating
    2015-07-30 18:50:06 | [reader][i][0]Authenticated, processing messages
    2015-07-30 18:50:06 | [reader][w][0]Setting new UTC offset: 0!
    2015-07-30 18:50:07 | [time][i]Synchronizing time via NTP
    2015-07-30 18:50:15 | [time][i]Time synchronized correctly, offset -0.0001 seconds
    2015-07-30 18:50:15 | [main][i]Feed Network client started
    2015-07-30 18:50:15 | [feed][i]Downloading configuration
    What parameters are you passing to dump1090. Maybe that is your issue (note I dont use the standard port hence the 8081).

    But my parameters (in etc\fr24feed.ini) are
    receiver="dvbt"
    fr24key="your own sharing key goes here"
    path="/usr/lib/fr24/dump1090"
    bs="yes"
    raw="yes"
    logmode="2"
    procargs="--net --gain -10 --net-http-port 8081 --ppm 12"
    mlat="yes"
    mlat-without-gps="yes"
    lcs

  6. #226
    Flight attendant malavanehsan's Avatar
    Join Date
    Mar 2013
    Posts
    69
    Hi
    in this part
    Code:
    $ gpg --keyserver pgp.mit.edu --recv-keys 40C430F5
    $ gpg --armor --export 40C430F5 | sudo apt-key add -
    $ sudo nano /etc/apt/sources.list

    i can't Type ' | ' in Raspberry
    what should i do?

  7. #227
    Purser
    Join Date
    Jan 2015
    Location
    Kallangur, Brisbane
    Posts
    168
    Quote Originally Posted by malavanehsan View Post
    Hi
    in this part
    Code:
    $ gpg --keyserver pgp.mit.edu --recv-keys 40C430F5
    $ gpg --armor --export 40C430F5 | sudo apt-key add -
    $ sudo nano /etc/apt/sources.list

    i can't Type ' | ' in Raspberry
    what should i do?
    copy'n'paste ...
    T-YBBN50 - Kallangur, QLD, Australia

  8. #228
    Flight attendant malavanehsan's Avatar
    Join Date
    Mar 2013
    Posts
    69
    Quote Originally Posted by bhaal View Post
    copy'n'paste ...
    Can you Explain It You mean I Write 'n' Alternative '|' ?

  9. #229
    Purser
    Join Date
    Jan 2015
    Location
    Kallangur, Brisbane
    Posts
    168
    Quote Originally Posted by malavanehsan View Post
    Can you Explain It You mean I Write 'n' Alternative '|' ?
    Well firstly I am not quite sure why you wouldn't be able to press the pipe key ... shift + backslash..

    But failing that, select the text with your mouse, ctrl-c to copy it to the clipboard, and then in your ssh terminal paste it, you might need to access the paste command via the edit menu..? I have no idea what OS you are using to access the Pi, or what keyboard layout you are using for that matter.. Sorry..
    T-YBBN50 - Kallangur, QLD, Australia

  10. #230
    Flight attendant malavanehsan's Avatar
    Join Date
    Mar 2013
    Posts
    69
    Quote Originally Posted by bhaal View Post
    Well firstly I am not quite sure why you wouldn't be able to press the pipe key ... shift + backslash..

    But failing that, select the text with your mouse, ctrl-c to copy it to the clipboard, and then in your ssh terminal paste it, you might need to access the paste command via the edit menu..? I have no idea what OS you are using to access the Pi, or what keyboard layout you are using for that matter.. Sorry..
    i use From Raspian i can't use Mouse

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •