Page 1 of 7 123 ... LastLast
Results 1 to 10 of 61

Thread: PI24: Replace dump1090 v1.14 -> pre-build package of dump1090 v1.15

  1. #1
    Captain abcd567's Avatar
    Join Date
    Sep 2013
    Location
    Toronto CYYZ
    Posts
    2,767

    PI24: Replace dump1090 v1.14 -> pre-build package of dump1090 v1.15

    How to replace PI24's integral dump1090-mutability v1.14 by dump1090-mutability v1.15


    Map of PI24's Default ver 1.14
    At "http://IP-of-PI/dump1090/"
    dump1090-mutability ver 1.14.png


    Map After Replacing by ver 1.15~dev
    At "http://IP-of-PI/dump1090/"
    dump1090-mutability ver 1.15-dev.png

    The replacement can be done by any one of the following two methods (OPTION-1 or OPTION-2).

    OPTION-1: Automated method given below (Very easy).
    The user has only to issue following command, and all is done automatically:

    Code:
    sudo bash -c "$(wget -O - https://raw.githubusercontent.com/abcd567a/dump1090/master/PI24_replace_dump1090_v1.14_by_v1.15.sh)"
    The script will take some time to finish.
    After script finishes, following message will be displayed:

    Code:
    ---------------
    ALL DONE !
    ---------------
    REBOOT RPi
    
    After reboot, go to your browser and check map on following address
    http://IP-of-Pi/dump1090/
    
    If new map does not show:
    Clear browser cache (Ctrl+Shift+Delete) and Reload Browser (Ctrl+F5)
    
    Check fr24feed status by following command:
    fr24feed-status
    .


    OPTION-2: Manually by method given in Post # 3 (Good for learning).
    "If you want to help someone, dont give him fish, teach him how to catch the fish"
    Last edited by abcd567; 2019-07-14 at 15:42.

  2. #2
    Passenger
    Join Date
    Apr 2019
    Posts
    1
    Thanks.
    So easy to use, and works perfectly.

  3. #3
    Captain abcd567's Avatar
    Join Date
    Sep 2013
    Location
    Toronto CYYZ
    Posts
    2,767
    MANUAL METHOD: (Good for Learning)
    "If you want to help someone, dont give him fish, teach him how to catch the fish"

    dump1090-mutability ver 1.15-dev-2.png

    INTRODUCTION
    I have compiled the installation package of dump1090-mutability ver 1.15 from source code, uploaded the package to Github, and made this installation package publicly downloadble. Now anyone can replace the PI24's dump1090-mutability ver 1.14 by ver 1.15~dev installation package I have uploaded to Github.


    STEP-1:
    Opened file install_dump1090.sh to modify
    Code:
    sudo nano /usr/lib/fr24/install_dump1090.sh
    Commented-out three lines (red) for ver 1.14, and added 3 lines (green) for ver 1.15, as shown below.

    NOTE: To comment-out a line of code, you have to add # at start of the line, as I have done in the red lines below.

    Code:
        # Download and install dump1090-mutability
    #    wget -O /tmp/dump1090-mutability_1.14_armhf.deb https://github.com/mutability/dump1090/releases/download/v1.14/dump1090-mutability_1.14_armhf.deb
    #    dpkg -i /tmp/dump1090-mutability_1.14_armhf.deb
    #    rm -f /tmp/dump1090-mutability_1.14_armhf.deb
    
    
        wget -O /tmp/dump1090-mutability_1.15_dev_armhf.deb https://github.com/abcd567a/dump1090/releases/download/v1/dump1090-mutability_1.15_dev_armhf.deb
        dpkg -i /tmp/dump1090-mutability_1.15_dev_armhf.deb
        rm -f /tmp/dump1090-mutability_1.15_dev_armhf.deb

    STEP-2:
    Purged ver 1.14
    Code:
    sudo dpkg --purge dump1090-mutability

    STEP-3:
    Run modified file install_dump1090.sh to install ver 1.15
    Code:
    cd /usr/lib/fr24/
    
    sudo ./install_dump1090.sh
    
    sudo service lighttpd force-reload
    
    sudo systemctl restart fr24feed

    STEP-4:

    Reboot RPi

    Code:
    sudo reboot

    STEP-5:
    Check
    Code:
    apt-cache policy dump1090-mutability
    dump1090-mutability:
      Installed: 1.15~dev
      Candidate: 1.15~dev
      Version table:
     *** 1.15~dev 100
            100 /var/lib/dpkg/status
    Code:
    fr24feed-status
    [ ok ] FR24 Feeder/Decoder Process: running.
    [ ok ] FR24 Stats Timestamp: 2019-06-05 17:57:04.
    [ ok ] FR24 Link: connected [UDP].
    [ ok ] FR24 Radar: T-CYYZ50.
    [ ok ] FR24 Tracked AC: 23.
    [ ok ] Receiver: connected (7183 MSGS/0 SYNC).
    [ ok ] FR24 MLAT: ok [UDP].
    [ ok ] FR24 MLAT AC seen: 22.
    Last edited by abcd567; 2019-07-14 at 15:45.

  4. #4
    Captain abcd567's Avatar
    Join Date
    Sep 2013
    Location
    Toronto CYYZ
    Posts
    2,767
    Last edited by abcd567; 2019-07-13 at 23:12.

  5. #5
    Passenger
    Join Date
    Jul 2017
    Location
    D:\Aachen
    Posts
    3
    Just worked perfect with my fresh install of the PI24 Image and your script.

    Thank you sir!

  6. #6
    Captain abcd567's Avatar
    Join Date
    Sep 2013
    Location
    Toronto CYYZ
    Posts
    2,767
    Skipper-Kolding:
    ua459:
    DarkBlue:


    Thanks to all of you for your feedbacks.
    Positive Feedbacks encourage.
    Negetive feedbacks or posting issues helps to solve problem and improve.
    No feedback is discouraging.

  7. #7
    First officer LN-MOW's Avatar
    Join Date
    Mar 2010
    Location
    Coal Mountain GA
    Posts
    278
    I overwrote the old fr24image on my 2nd feed with your script and it worked like a charm. Changed to beast tcp and it came right up.

    Great job!

    But Im puzzled why FR24 themselves are so passive in this matter. You would have thought it was in their interest to have all this lined up when they shut down the windows feed ..


    Sent from my iPad using Tapatalk Pro

  8. #8
    Passenger
    Join Date
    Feb 2013
    Location
    London, UK
    Posts
    43
    Thank you for this!
    I used your script (I was in a hurry!), and it seems to have done the trick, but although the OSM map is displayed, and there are planes displayed, they are not being updated, and after a few seconds a box displays

    "Problem fetching data from dump1090.
    The data from dump1090 hasn't been updated in a while. Maybe dump1090 is no longer running?
    The displayed map data will be out of date. "

    The UTC clock shows the current time and is updating itself, the Last Update clock has the wrong time, and is not ticking.

    Clearing the browser's cache has not helped.

    I can see the raw data at http://frpi:30003/

    Code:
    pi@frrpi:~ $  fr24feed-status 
    [ ok ] FR24 Feeder/Decoder Process: running.
    [ ok ] FR24 Stats Timestamp: 2019-06-26 15:13:19.
    [ ok ] FR24 Link: connected [UDP].
    [ ok ] FR24 Radar: T-EGLC11.
    [ ok ] FR24 Tracked AC: 51.
    [ ok ] Receiver: connected (421391 MSGS/0 SYNC).
    [ ok ] FR24 MLAT: ok [UDP].
    [ ok ] FR24 MLAT AC seen: 48.
    pi@frrpi:~ $  apt-cache policy dump1090-mutability
    dump1090-mutability:
      Installed: 1.15~dev
      Candidate: 1.15~dev
      Version table:
     *** 1.15~dev 100
            100 /var/lib/dpkg/status
    pi@frrpi:~ $
    Any suggestions?

  9. #9
    Captain
    Join Date
    Apr 2018
    Posts
    750
    Most likely an insufficient power supply.

    dump1090-mutability 1.14 uses a lower sample rate, so the dongle is more likely to be affected by a not so good power supply.

    Let's check the output of this:
    Code:
    sudo bash -c "$(wget -q -O - https://raw.githubusercontent.com/wiedehopf/adsb-wiki/master/rtl_test.sh)"
    It checks the dongle for lost samples and for undervoltage.

  10. #10
    Passenger
    Join Date
    Feb 2013
    Location
    London, UK
    Posts
    43
    Thanks, but the dongle is fine, and I can see the raw ADSB data on port 30003 in real time, and this is being correctly fed to fr24.

    But, I ran your script anyway:
    Code:
    Found 1 device(s):
      0:  Realtek, RTL2838UHIDIR, SN: 00000031
    
    Using device 0: Generic RTL2832U OEM
    Found Elonics E4000 tuner
    Supported gain values (14): -1.0 1.5 4.0 6.5 9.0 11.5 14.0 16.5 19.0 21.5 24.0 29.0 34.0 42.0 
    Sampling at 2400000 S/s.
    
    Info: This tool will continuously read from the device, and report if
    samples get lost. If you observe no further output, everything is fine.
    
    Reading samples in async mode...
    Signal caught, exiting!
    
    User cancel, exiting...
    Samples per million lost (minimum): 0
    -------
    Test finished!
    More than 2 lost samples per million or other errors probably mean the receiver isn't working correctly.
    Try another power supply before condemning the receiver though!
    -------
    -------
    No undervoltage detected, looking fine!
    If the dongle is not directly plugged into the Raspberry Pi, lack of power/voltage could still be an issue.
    Even without detected undervoltage a better power supply can often improve reception!
    For optimum performance i would recommend the Official Raspberry Pi power supply.
    -------
    It is an original RPi PSU.

Posting Permissions

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