Announcement

Collapse
No announcement yet.

Windows Setup/Feed Migration (virtualVM) Assistance

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Oblivian
    replied
    Oh dear.

    For future reference, editing posts after posting them can have adverse effects.

    I approved it and removed the 2 duplicates.

    You edited it again after I did. That is exactly what link spammers do.

    So it re triggered and moderated it again.

    New users attempting to post links, common script/web code (FR24 logs included), or other key characters (attempting to tag users with @'s will trigger this - so don't!) may find their posts automatically moderated and will not show until approved. Do NOT post-boost or re-post to avoid, Edit code and links to broken/text only format to fix this, or separately request approval.
    Patience is a virtue. And I'm on quite a different timezone.

    Sent from my EML-L09 using Tapatalk

    Leave a comment:


  • wiedehopf
    replied
    Use this command:

    sudo systemctl restart fr24feed

    And check if it works then, because right now dump1090 is running but when it tried to start before it couldn't start because a port was occupied.

    Also let's see the output of this command

    ls -l /etc/fr24feed.ini

    Maybe the rights are incorrect and it's not using the settings and fighting with dump1090-mutability over the dongle.

    Leave a comment:


  • wetter-rimbach
    replied
    No, unfortunately not. I rebooted and repeated the forum post's instructions. I even cleaned my Raspberry and re-installed the OS. and then did it on a fresh device again. Always same issue.

    I also tried it without the second one and only as DVB-T stick which forces dump to Version 1.14 as far as I understood, also here a failure. When I switch back to my Windows feeder, no problem, I submit data and it is recognized and valid datastream to FR24

    Leave a comment:


  • wiedehopf
    replied
    Does a reboot fix it?

    Because it looks like it's working.

    Leave a comment:


  • wetter-rimbach
    replied
    So here again ....

    Code:
     $ cat /etc/fr24feed.ini
    receiver="beast-tcp"
    fr24key="10dxxxxxxxxxx removed for privacy"
    host="127.0.0.1:30005"
    bs="no"
    raw="no"
    logmode="0"
    logpath="/var/log"
    mlat="yes"
    mlat-without-gps="yes"
    Code:
    $ cat /var/log/dump1090-mutability.log
    Wed Apr 17 12:43:13 2019 CEST  dump1090-mutability v1.15~dev starting up.
    Using sample converter: UC8, integer/table path
    Found 1 device(s):
    0: Generic, RTL2832U, SN: 77771111153705700 (currently selected)
    Detached kernel driver
    Found Rafael Micro R820T tuner
    Max available gain is: 49.60 dB
    Setting gain to: 49.60 dB
    Gain reported by device: 49.60 dB
    Error opening the listening port 30002 (Raw TCP output): bind: Address already in use
    Wed Apr 17 12:48:30 2019 CEST  dump1090-mutability v1.15~dev starting up.
    Using sample converter: UC8, integer/table path
    Found 1 device(s):
    0: Generic, RTL2832U, SN: 77771111153705700 (currently selected)
    Found Rafael Micro R820T tuner
    Max available gain is: 49.60 dB
    Setting gain to: 49.60 dB
    Gain reported by device: 49.60 dB
    
    
    Statistics: Wed Apr 17 12:48:31 2019 CEST - Wed Apr 17 14:02:49 2019 CEST
    Local receiver:
      61341696 samples processed
      0 samples dropped
      0 Mode A/C messages received
      170613 Mode-S message preambles received
        93488 with bad message format or invalid CRC
        74410 with unrecognized ICAO address
        2519 accepted with correct CRC
        196 accepted with 1-bit error repaired
      -37.1 dBFS noise power
      -24.4 dBFS mean signal power
      -16.6 dBFS peak signal power
      0 messages with signal power above -3dBFS
    Messages from network clients:
      0 Mode A/C messages received
      0 Mode S messages received
        0 with bad message format or invalid CRC
        0 with unrecognized ICAO address
        0 accepted with correct CRC
        0 accepted with 1-bit error repaired
    2715 total usable messages
    0 surface position messages received
    130 airborne position messages received
    115 global CPR attempts with valid positions
    0 global CPR attempts with bad data
      0 global CPR attempts that failed the range check
      0 global CPR attempts that failed the speed check
    0 global CPR attempts with insufficient data
    15 local CPR attempts with valid positions
      0 aircraft-relative positions
      0 receiver-relative positions
    0 local CPR attempts that did not produce useful positions
      0 local CPR attempts that failed the range check
      0 local CPR attempts that failed the speed check
    0 CPR messages that look like transponder failures filtered
    0 non-ES altitude messages from ES-equipped aircraft ignored
    14 unique aircraft tracks
    1 aircraft tracks where only one message was seen
    CPU load: 0.1%
      2610 ms for demodulation
      1557 ms for reading from USB
      102 ms for network input and background tasks
    Code:
    $ pgrep -fa dump1090
    561 /usr/bin/dump1090-mutability --net --ppm 0 --fix --lat 49.618066 --lon 8.760589 --max-range 300 --net-ri-port 30001 --net-ro-port 30002 --net-bi-port 30004 --net-bo-port 30005 --net-sbs-port 30003 --net-heartbeat 60 --net-ro-size 500 --net-ro-interval 1 --net-buffer 2 --net-bind-address 127.0.0.1 --stats-every 3600 --write-json /run/dump1090-mutability --write-json-every 1 --json-location-accuracy 1 --quiet

    Leave a comment:


  • wetter-rimbach
    replied
    They disappeared again after reload. This is not good ! They were there and I took a screenshot.

    I post them again ! Hoping they get released by a moderator rather soon

    Leave a comment:


  • wiedehopf
    replied
    Try posting the output of these commands and be sure not to include the line with the command you put in.

    Code:
    cat /etc/fr24feed.ini | tr '/@.' '|A,'
    
    cat /var/log/dump1090-mutability.log | tr '/@.' '|A,'
    
    pgrep -fa dump1090 | tr '/@.' '|A,'
    Without / or @ or . let's hope that the forum isn't quite as annoying.
    (The second part of these commands above replace / with |, @ with A and . with ,)
    Last edited by wiedehopf; 2019-04-17, 13:35.

    Leave a comment:


  • wiedehopf
    replied
    I can't see any logs if you posted any.

    Leave a comment:


  • wetter-rimbach
    replied
    Hi both,

    my post just came through, wiedehopf, any idea about my reply to your request for logs ?

    Thanks

    Best regards
    Rudolf

    Leave a comment:


  • wiedehopf
    replied
    So using @ is the problem? Or is it the slashes as well?

    Leave a comment:


  • Oblivian
    replied
    Originally posted by wiedehopf View Post
    It's aggravating that even when there are no actual links the slashes in unix pathes are triggering the auto moderation?
    Anyway makes it really hard to help people who just registered on the forum.

    Oblivian do you know what go the post auto-moderated?

    I can probably include some character replacement trickery in those commands to get rid of all the slashes or whatever else is triggering the automoderation.
    Because people continue to use @s like its twitter.

    And they're included in standard linux console output

    Leave a comment:


  • wiedehopf
    replied
    It's aggravating that even when there are no actual links the slashes in unix pathes are triggering the auto moderation?
    Anyway makes it really hard to help people who just registered on the forum.

    Oblivian do you know what go the post auto-moderated?

    I can probably include some character replacement trickery in those commands to get rid of all the slashes or whatever else is triggering the automoderation.
    Last edited by wiedehopf; 2019-04-17, 12:39.

    Leave a comment:


  • Oblivian
    replied
    (I'm hoping he realises and replies. Moved from it's own moderated thread to here)

    Leave a comment:


  • wiedehopf
    replied
    Please show the output of following commands:

    cat /etc/fr24feed.ini

    cat /var/log/dump1090-mutability.log

    pgrep -fa dump1090
    Last edited by wiedehopf; 2019-04-17, 11:14.

    Leave a comment:


  • wetter-rimbach
    replied
    Former Windows user - switch to Raspberry fails massively despite all my searches

    Hi all,

    I hope you can help me. I am a current "Windows-Feeder", My system runs since 2 years very well. Now I am forced to switch, which I am very ok with.

    I have a Raspberry Pi3+, I have my DVB-T Stick (SDR USB Dongle, which fulfills the requirement specs (I checked it a few times).

    I followed this instructions: (Can't submit links yet)
    /threads/8908-New-Flightradar24-feeding-software-for-Raspberry-Pie?p=66479#post66479
    and
    /threads/10232-How-to-Install-dump1090-mutability_1-15-dev-on-RPi

    Both ran through without error.

    But when I start the feeder and check the status I get ALWAYS this, even following the second link ....
    Code:
    pi@raspberrypi:~ $ fr24feed-status
    [ ok ] FR24 Feeder/Decoder Process: running.
    [ ok ] FR24 Stats Timestamp: 2019-04-17 10:49:00.
    [ ok ] FR24 Link: connected [UDP].
    [ ok ] FR24 Radar: T-EDFM52.
    [ ok ] FR24 Tracked AC:.
    [FAIL] Receiver: down ... failed!
    [FAIL] FR24 MLAT: not running ... failed!
    I need definitely help, because I am lost. I searched last 3 days the forum and there is no solution I have found but I might have overread it.

    Thanks a lot to you all !

    Best regards
    Rudolf

    Leave a comment:

Working...
X