Page 74 of 91 FirstFirst ... 2464727374757684 ... LastLast
Results 731 to 740 of 901

Thread: Archived - Beta test MLAT software for Raspberry Pi

  1. #731
    Passenger
    Join Date
    Apr 2015
    Posts
    4
    Quote Originally Posted by bakerkj View Post
    I have fr24feed running (1.0.18-7).

    I have noticed that my log file /var/log/fr24feed.log is not being rotated (after months of being up). feed.flightradar24.com/fr24feed-manual.pdf seems to suggest that --logmode and --logpath need to be set to get this behavior. However the recent init scripts found in the debs (here feed.flightradar24.com) instead set arguments "--log-base=/var/log/fr24feed" and "--log-rotate=2".

    I am running with the init script. With those parameters set I would expect log-rotate=2 to cause the logs to "rotate at midnight <and> keep for 72 hours".

    Can anyone confirm that log rotation is working for them? In which case I'd guess it is a configuration issue on my side. If not is this a log rotation bug in fr24feed?

    Thanks!

    -- Ken
    Make sure you have logrotate installed

    Code:
    sudo apt-get install logrotate
    Plus in order to prevent SD/Flash memory wear due to repeated writing you should add

    Code:
    tmpfs /var/log tmpfs nodev,nosuid,size=50M 0 0
    to your /etc/fstab

    The above line will create a 50mb tmpfs partition (aka in RAM) mounted in /var/log that won't survive a reboot but won't wear your storage.

  2. #732
    Passenger
    Join Date
    Feb 2014
    Posts
    2
    Help, please! My FR24Feed v. 1.0.18-7 on RaspberryPI doesn't work properly. I do not know where to start, but it is not transmitting data to the flightradar24.com, but in FlightAware dump1090 I see the flights. Tell me what to do. Write me what more data I have provide for full understanding of my problem. Sorry for my english.
    "ac_map_size="3072"
    build_arch="armv7l"
    build_flavour="generic"
    build_os="Linux"
    build_revision="HEAD-91e2757.git"
    build_timetamp="Jul 11 2016 09:24:44"
    build_version="1.0.18-7"
    cfg_baudrate=""
    cfg_bs="yes"
    cfg_host="192.168.1.88:30002"
    cfg_mpx="yes"
    cfg_path=""
    cfg_raw="yes"
    cfg_receiver="dvbt"
    cfg_windowmode="0"
    d11_map_size="0"
    feed_alias="T-UKDD8"
    feed_configured_mode="UDP"
    feed_current_mode="UDP"
    feed_current_server="83.140.21.112"
    feed_last_attempt_time="1478033487"
    feed_last_config_attempt="1478033487"
    feed_last_config_info=""
    feed_last_config_result="success"
    feed_last_connected_time="1478033487"
    feed_status="connected"
    feed_status_message=""
    fr24key="3b***************"
    last_json_utc="1478034928"
    last_rx_connect_status="OK"
    last_rx_connect_time="1478034999"
    last_rx_connect_time_s="2016-11-01 21:16:39"
    mlat-ok="NO"
    mlat-started="YES"
    mlat_problem="no-config"
    msg_ring_full="0"
    msg_ring_length="0"
    offline-mode="no"
    rx_connected="0"
    shutdown="no"
    time_update_utc="1478034945"
    time_update_utc_s="2016-11-01 21:15:45"
    timing_is_valid="1"
    timing_last_drift="+0.0012"
    timing_last_offset="+0.0003"
    timing_last_result="success"
    timing_source="NTP"
    timing_time_last_attempt="1478034697"
    timing_time_last_success="1478034697"
    timing_time_since_last_success="606"

    $ sudo service fr24feed diagnostics
    [ ok ] FR24 Feeder/Decoder Process: running.
    [ ok ] FR24 Stats Timestamp: 2016-11-01 21:39:55.
    [ ok ] FR24 Link: connected [UDP].
    [ ok ] FR24 Radar: T-UKDD8.
    [ ok ] FR24 Tracked AC:.
    [FAIL] Receiver: down ... failed!
    [FAIL] FR24 MLAT: not running ... failed!
    Last edited by valentajn; 2016-11-01 at 21:42.

  3. #733
    Super Moderator
    Join Date
    May 2011
    Location
    T-NZCH1, PP:PH New Zealand
    Posts
    5,008
    Quote Originally Posted by valentajn View Post
    Help, please! My FR24Feed v. 1.0.18-7 on RaspberryPI doesn't work properly. I do not know where to start, but it is not transmitting data to the flightradar24.com, but in FlightAware dump1090 I see the flights. Tell me what to do. Write me what more data I have provide for full understanding of my problem. Sorry for my english.
    "ac_map_size="3072"
    build_arch="armv7l"
    build_flavour="generic"
    build_os="Linux"
    build_revision="HEAD-91e2757.git"
    build_timetamp="Jul 11 2016 09:24:44"
    build_version="1.0.18-7"
    cfg_baudrate=""
    cfg_bs="yes"
    cfg_host="192.168.1.88:30002"
    cfg_mpx="yes"
    cfg_path=""
    cfg_raw="yes"
    cfg_receiver="dvbt"
    cfg_windowmode="0"
    d11_map_size="0"
    feed_alias="T-UKDD8"
    feed_configured_mode="UDP"
    feed_current_mode="UDP"
    feed_current_server="83.140.21.112"
    feed_last_attempt_time="1478033487"
    feed_last_config_attempt="1478033487"
    feed_last_config_info=""
    feed_last_config_result="success"
    feed_last_connected_time="1478033487"
    feed_status="connected"
    feed_status_message=""
    fr24key="3b***************"
    last_json_utc="1478034928"
    last_rx_connect_status="OK"
    last_rx_connect_time="1478034999"
    last_rx_connect_time_s="2016-11-01 21:16:39"
    mlat-ok="NO"
    mlat-started="YES"
    mlat_problem="no-config"
    msg_ring_full="0"
    msg_ring_length="0"
    offline-mode="no"
    rx_connected="0"
    shutdown="no"
    time_update_utc="1478034945"
    time_update_utc_s="2016-11-01 21:15:45"
    timing_is_valid="1"
    timing_last_drift="+0.0012"
    timing_last_offset="+0.0003"
    timing_last_result="success"
    timing_source="NTP"
    timing_time_last_attempt="1478034697"
    timing_time_last_success="1478034697"
    timing_time_since_last_success="606"

    $ sudo service fr24feed diagnostics
    [ ok ] FR24 Feeder/Decoder Process: running.
    [ ok ] FR24 Stats Timestamp: 2016-11-01 21:39:55.
    [ ok ] FR24 Link: connected [UDP].
    [ ok ] FR24 Radar: T-UKDD8.
    [ ok ] FR24 Tracked AC:.
    [FAIL] Receiver: down ... failed!
    [FAIL] FR24 MLAT: not running ... failed!
    If you have flight aware or any other feeders working do NOT configure fr25 for dvbt. You need avrtcp

    Sent from my XT1092 using Tapatalk
    Posts not to be taken as official support representation - Just a helpful uploader who tinkers

  4. #734
    Captain abcd567's Avatar
    Join Date
    Sep 2013
    Location
    Toronto CYYZ
    Posts
    2,768
    Quote Originally Posted by Oblivian View Post
    If you have flight aware or any other feeders working do NOT configure fr25 for dvbt. You need avrtcp
    To change settings, type <IP of PI>:8754/settings.html in your browser address bar.
    Set Receiver AVR(TCP), Host 127.0.0.1:30002
    Click Save button and then Restart button at bottom right corner of settings page.
    FR24 settings.png


    To see status, type <IP of PI>:8754 in your browser address bar.
    FR24 status.png

  5. #735
    Passenger
    Join Date
    Feb 2014
    Posts
    2
    Thank you all for your help, now works as it should.

  6. #736
    Flight attendant Wolli's Avatar
    Join Date
    Dec 2014
    Location
    Germany
    Posts
    82

    [mlat][e]Received MLAT timestamp error: 0 seconds!

    Hi all,

    after bringing my RPi3 to live I am feeding with MLAT enabled for some weeks now.

    Initial problems caused by the MLAT server mlat-1.fr24.com have been solved two weeks ago (obviously wrong MLAT server configuration, see from posting #8 on http://forum.flightradar24.com/threa...ing-Pi24-error).

    Now since 2 days, a new problem occured. I see the line
    -> [mlat][e]Received MLAT timestamp error: 0 seconds!
    in the log, and obviously no more MLAT data is transferred (always line [mlat][i]Stats 6807269/0 in the log), although "sudo service fr24feed diagnostics" states
    -> (example): "[ ok ] FR24 MLAT: ok [UDP]."

    Here an example log of a feed session (started without "service" for "bug mining"):
    pi@raspberrypi:~ $ sudo fr24feed start
    2016-11-22 18:22:11 | [main][i]FR24 Feeder/Decoder
    2016-11-22 18:22:11 | [main][i]Version: 1.0.18-7/generic
    2016-11-22 18:22:11 | [main][i]Built on Jul 11 2016 09:24:44 (HEAD-91e2757.git/Linux/armv7l)
    2016-11-22 18:22:11 | [main][i]Copyright 2012-2016 Flightradar24 AB
    2016-11-22 18:22:11 | [main][i]http://flightradar24.com
    2016-11-22 18:22:12 | [main][i]DNS mode: LIBC
    2016-11-22 18:22:12 | [main][i]Automatic updates are DISABLED
    2016-11-22 18:22:12 | ERROR
    2016-11-22 18:22:12 | [httpd][i]Server started, listening on 0.0.0.0:8754
    2016-11-22 18:22:12 | [main][i]Reader thread started
    2016-11-22 18:22:12 | [main][i]MLAT data feed started
    2016-11-22 18:22:12 | [master][i]Starting processing thread
    2016-11-22 18:22:12 | [reader][i]Initializing reader
    2016-11-22 18:22:12 | [reader][i]Connecting to DVBT receiver via (exe:///usr/lib/fr24/dump1090 --net --fix --raw --mlat)
    2016-11-22 18:22:12 | [reader][i]Connected to the receiver, configuring
    2016-11-22 18:22:12 | [reader][i]Configured, processing messages
    2016-11-22 18:22:12 | [mlat][i]Waiting for MLAT configuration
    Found 1 device(s):
    0: Generic, RTL2832U, SN: 77771111153705700 (currently selected)
    Found Rafael Micro R820T tuner
    Max available gain is: 49.60
    Setting gain to: 49.60
    Exact sample rate is: 2000000.052982 Hz
    Gain reported by device: 49.60
    2016-11-22 18:22:12 | [reader][w]Setting new UTC offset: 0!
    2016-11-22 18:22:13 | [time][i]Synchronizing time via NTP
    2016-11-22 18:22:17 | [time][i]Time synchronized correctly, offset +0.0003 seconds
    2016-11-22 18:22:17 | [main][i]Feed Network client started
    2016-11-22 18:22:17 | [feed][i]Downloading configuration
    2016-11-22 18:22:17 | [feed][c]Interval: 5s
    2016-11-22 18:22:17 | [feed][c]Latitude: 51.xxxxxxxx
    2016-11-22 18:22:17 | [feed][c]Longitude: 6.xxxxxx
    2016-11-22 18:22:17 | [feed][c]GND: YES
    2016-11-22 18:22:17 | [feed][c]NonADSB: YES
    2016-11-22 18:22:17 | [feed][c]Timestamps: optional
    2016-11-22 18:22:17 | [feed][c]Max range AIR: 350.0nm
    2016-11-22 18:22:17 | [feed][c]Max range GND: 100.0nm
    2016-11-22 18:22:17 | [stats][i]Stats thread started
    2016-11-22 18:22:17 | [feed][i]defined 5 servers
    2016-11-22 18:22:17 | [feed][n]EDDL27@83.140.21.68:8099/UDP
    2016-11-22 18:22:17 | [feed][n]connecting
    2016-11-22 18:22:17 | [feed][n]connected via UDP (fd 8)
    2016-11-22 18:22:17 | [feed][n]working
    2016-11-22 18:22:17 | [feed][i]sent 1,0 AC
    2016-11-22 18:22:18 | [mlat][i]MLAT configuration received, service ENABLED
    2016-11-22 18:22:18 | [mlat][i]Starting MLAT with preconfigured position: 51.xx,6.xx,187.0
    2016-11-22 18:22:18 | [mlat][i]MLAT bandwidth reduction active, level 1
    2016-11-22 18:22:18 | [mlat][i]Configuring UDP connection udp://mlat-1.fr24.com:19788
    2016-11-22 18:22:18 | [mlat][i]Registering MLAT station
    2016-11-22 18:22:18 | [mlat][i]Registering MLAT station: SUCCESS
    2016-11-22 18:22:22 | [feed][i]sent 9,0 AC
    2016-11-22 18:22:23 | [mlat][i]Received ADS-B time references AC:
    2016-11-22 18:22:23 | [mlat][i] 343202
    2016-11-22 18:22:23 | [mlat][i] 400DB1
    2016-11-22 18:22:23 | [mlat][i] 4D00D8
    2016-11-22 18:22:23 | [mlat][i] A76DF1
    2016-11-22 18:22:27 | [feed][i]sent 8,0 AC
    2016-11-22 18:22:32 | [mlat][e]Received MLAT timestamp error: 0 seconds!
    2016-11-22 18:22:32 | [mlat][i]Pinging the server
    2016-11-22 18:22:32 | [mlat][i]Stats 6807269/6807269
    2016-11-22 18:22:32 | [feed][i]sent 10,0 AC
    2016-11-22 18:22:38 | [feed][i]sent 11,0 AC
    2016-11-22 18:22:48 | [feed][i]sent 9,0 AC
    2016-11-22 18:22:53 | [mlat][i]Pinging the server
    2016-11-22 18:22:53 | [mlat][i]Stats 6807269/0
    2016-11-22 18:22:53 | [feed][i]sent 9,0 AC
    2016-11-22 18:22:58 | [feed][i]sent 9,0 AC
    2016-11-22 18:23:03 | [feed][i]sent 7,0 AC
    2016-11-22 18:23:08 | [feed][i]sent 10,0 AC
    2016-11-22 18:23:13 | [mlat][i]Pinging the server
    2016-11-22 18:23:13 | [mlat][i]Stats 6807269/0
    2016-11-22 18:23:14 | [feed][i]sent 10,0 AC
    2016-11-22 18:23:19 | [feed][i]sent 11,0 AC
    2016-11-22 18:23:20 | [feed][i]filtering out 13 overlapping AC (saving bandwidth)
    2016-11-22 18:23:24 | [feed][i]sent 0,9 AC
    2016-11-22 18:23:25 | [feed][i]removed 1 of 19 AC
    2016-11-22 18:23:29 | [feed][i]sent 0,8 AC
    2016-11-22 18:23:33 | [mlat][i]Received ADS-B time references AC:
    2016-11-22 18:23:33 | [mlat][i] 343202
    2016-11-22 18:23:33 | [mlat][i] 400DB1
    2016-11-22 18:23:33 | [mlat][i] 4BAAD0
    2016-11-22 18:23:33 | [mlat][i] 4CA223
    2016-11-22 18:23:33 | [mlat][i] 4D00D8
    2016-11-22 18:23:33 | [mlat][i]Pinging the server
    2016-11-22 18:23:33 | [mlat][i]Stats 6807269/0
    2016-11-22 18:23:34 | [feed][i]sent 4,8 AC
    2016-11-22 18:23:37 | [feed][i]removed 2 of 20 AC
    2016-11-22 18:23:39 | [feed][i]sent 0,9 AC
    2016-11-22 18:23:44 | [feed][i]sent 0,9 AC
    2016-11-22 18:23:49 | [feed][i]sent 0,8 AC
    2016-11-22 18:23:49 | [feed][n]syncing stream async: 1
    2016-11-22 18:23:50 | [feed][n]syncing stream result: 1
    2016-11-22 18:23:53 | [mlat][i]Pinging the server
    2016-11-22 18:23:53 | [mlat][i]Stats 6807269/0
    2016-11-22 18:23:54 | [feed][i]sent 0,9 AC
    2016-11-22 18:23:59 | [feed][i]sent 0,7 AC
    2016-11-22 18:24:04 | [feed][i]sent 0,7 AC
    2016-11-22 18:24:09 | [feed][i]sent 0,8 AC
    2016-11-22 18:24:13 | [mlat][i]Pinging the server
    2016-11-22 18:24:13 | [mlat][i]Stats 6807269/0
    2016-11-22 18:24:15 | [feed][i]sent 2,9 AC
    2016-11-22 18:24:17 | [feed][i]removed 2 of 19 AC
    2016-11-22 18:24:20 | [feed][i]sent 4,9 AC
    2016-11-22 18:24:21 | [feed][i]filtering out 11 overlapping AC (saving bandwidth)
    2016-11-22 18:24:25 | [feed][i]sent 7,7 AC
    2016-11-22 18:24:30 | [feed][i]sent 5,6 AC
    ^C2016-11-22 18:24:31 | [main][i]Terminating on user request
    2016-11-22 18:24:31 | [main][i]Terminating worker threads
    2016-11-22 18:24:31 | [reader][i]Connection terminated
    2016-11-22 18:24:31 | [main][i]Terminating child process 10813 with SIGETERM
    2016-11-22 18:24:31 | [reader][i]Terminating on request
    2016-11-22 18:24:35 | [master][i]Terminating on request
    2016-11-22 18:24:35 | [feed][n]busy
    2016-11-22 18:24:35 | [feed][n]disconnected
    2016-11-22 18:24:35 | [feed][x]Feeding thread terminated
    pi@raspberrypi:~ $


    Note especially the log lines
    -> 2016-11-22 18:22:32 | [mlat][e]Received MLAT timestamp error: 0 seconds!
    and the "zero" MLAT data
    -> [mlat][i]Stats 6807269/0

    Questions:
    1) Any ideas?
    2) Do you also observe "[mlat][e]Received MLAT timestamp error: 0 seconds!" in your logs?

    Greetings from Germany, Wolli
    Last edited by Wolli; 2016-11-22 at 18:13.

  7. #737
    Flight attendant Wolli's Avatar
    Join Date
    Dec 2014
    Location
    Germany
    Posts
    82

    Update concerning: [mlat][e]Received MLAT timestamp error: 0 seconds!

    Hi all,

    after several days "living" with that error (I checked that every 2 days or so), today I noticed that the reported
    -> [mlat][e]Received MLAT timestamp error: 0 seconds!
    is no more appearing in my feeder's log. I don't know, why.

    I assume the FR24 guys are - from time to time - changing the behaviour of their MLAT-servers, in a continuously ongoing process of enhancing MLAT quality. However, this is just speculation.

    Greetings, -Wolli-

  8. #738
    Flight attendant Wolli's Avatar
    Join Date
    Dec 2014
    Location
    Germany
    Posts
    82

    2nd Update concerning: [mlat][e]Received MLAT timestamp error: 0 seconds!

    After several days of MLAT "working as it should" (seen with my eyes) the - by me myself - stated "error" ...
    -> [mlat][e]Received MLAT timestamp error: 0 seconds!
    is again back here.

    Though I explicitely appreciate this posting of @WolfInTheAir (many thanks!), my wish is to see an "official FR24 posting" concerning FR24's handling of volunteer MLAT feeders' (like e.g. me) problems.

    Motivation for my request:
    We - the volunteers - are investing time and money to help/assist FR24 being able to spread good/best quality flight data to "the world". We like to do so. However, when problems (seen with our eyes) arise, we would like to have some info, why.

    * Maybe, the data quality of an individual feeder is not so good, as FR24 requires. A suggestion by FR24, what the feeder (person) could do to enhance data quality, would be warmly welcome.

    * Maybe, participation in MLAT feeding generally requires the individual feeder to supply data of many dozens of ACs at the same time to ensure "good quality MLAT data". Maybe, MLAT-feeders seeing just a few dozens of ACs have a "natural" MLAT data quality problem.

    I understand, that FR24 probably won't put all its cards "open on the table", due to business secrets. That's ok.

    However, my current feeling is, that we currently do not receive sufficient information concerning MLAT problems/issues.

    Consequently, it would be nice to see/read some more official FR24 info about MLAT issues.

    So I politely invite FR24 to supply us with some more info concerning MLAT problems. This would be very rewarding. May we have hope? Kind regards, -Wolli-
    Last edited by Wolli; 2016-12-06 at 19:59.

  9. #739
    Flight attendant
    Join Date
    Mar 2012
    Posts
    71
    Do we have to prepare for leap-second event on 1 Jan 2017? Just reboot after midnight and all will be fixed?

  10. #740
    Purser
    Join Date
    Sep 2013
    Location
    T-VHST9
    Posts
    101
    Quote Originally Posted by Kemistry View Post
    Do we have to prepare for leap-second event on 1 Jan 2017? Just reboot after midnight and all will be fixed?
    FR24feed software will synchronize time via NTP server every 10 minutes automatically...
    I think no need to worry about it...
    T-VHST9: http://vhst9.hopto.org/
    (24/7)

Posting Permissions

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