Announcement

Collapse
No announcement yet.

Automated Installation of Dump1090-Mutability, Data Feeders, and Performance Graphs

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

  • #91
    Unfortunately the coax ends as SMA male and dongle is female, so it should be perfectly connected.

    Comment


    • #92
      Originally posted by maverick464 View Post
      Unfortunately the coax ends as SMA male and dongle is female, so it should be perfectly connected.
      Even with coax male and dongle female, the center wire connection will be broken if coax male is RP-SMA.

      Please unscrew the adaptor from dongle and carefully inspect the SMA male. Does it have a center pin?

      Comment


      • #93
        Yea it does have a pin in it. So it’s definitely a SMA connector.

        Comment


        • #94
          Try these:
          1. Check if the sma is fully screwed to dongle.
          2. If you have another sma male connector, try it.
          3. Remove dongle from current USB port of Pi and plug into another USB port of Pi.
          4. Check continuity of coax core & shield.
          Last edited by abcd567; 2019-01-03, 22:33.

          Comment


          • #95
            Please also show the output of this command:
            sudo journalctl -u dump1090-mutability -e --no-pager -n20

            You can also check the if the N connector of the antenna is connected properly and the diameter of the pin matches hole.

            But literally receiving nothing is strange.

            You could also as a test plug in a 7cm piece of wire into the dongle sma connector and check if you receive anything. (a very crude antenna but you should receive more than nothing)
            Last edited by wiedehopf; 2019-01-03, 23:37.

            Comment


            • #96
              Originally posted by wiedehopf View Post
              You could also as a test plug in a 7cm piece of wire into the dongle sma connector and check if you receive anything. (a very crude antenna but you should receive more than nothing)
              Something like this, which I used with my portable/mobile ADSB receiver. The dongle I used is Flightaware Pro Stick Plus, and used a 90 deg USB bend to keep dongle vertical. With RPi you dont need this bend, just hold the RPi itself in vertical position to make dongle vertical

              Portable ADSB.png


              WIRES WHICH MAY BE USE FOR MAKING TEMPORARY ANTENNA

              Steel Tie Wire
              Steel Tie Wire.jpg

              Scrap Network Cable
              Scrap Network Cable.jpg
              Last edited by abcd567; 2019-01-04, 03:22.

              Comment


              • #97
                28wiedehopf
                Thanks also for you help.
                N connector from the antenna I'm 99,9% sure that is correctly connected as I check twice when I installed the antenna.

                This is the result of the command line suggested by you:

                Pi receiving nothing at my parents' place (all the star and stop were made by me as I was testing the reception of various frequencies with GQRX app):
                Code:
                pi@Pi24:~ $ sudo journalctl -u dump1090-mutability -e --no-pager -n20
                -- Logs begin at Thu 2016-11-03 18:16:44 CET, end at Fri 2019-01-04 08:20:57 CET. --
                gen 02 18:49:57 Pi24 systemd[1]: Starting LSB: dump1090 daemon (mutability variant)...
                gen 02 18:50:01 Pi24 systemd[1]: Started LSB: dump1090 daemon (mutability variant).
                gen 03 05:29:14 Pi24 systemd[1]: Stopping LSB: dump1090 daemon (mutability variant)...
                gen 03 05:29:15 Pi24 systemd[1]: Stopped LSB: dump1090 daemon (mutability variant).
                gen 03 05:36:40 Pi24 systemd[1]: Starting LSB: dump1090 daemon (mutability variant)...
                gen 03 05:36:42 Pi24 systemd[1]: Started LSB: dump1090 daemon (mutability variant).
                gen 03 05:53:55 Pi24 systemd[1]: Stopping LSB: dump1090 daemon (mutability variant)...
                gen 03 05:53:56 Pi24 systemd[1]: Stopped LSB: dump1090 daemon (mutability variant).
                gen 03 06:41:14 Pi24 systemd[1]: Starting LSB: dump1090 daemon (mutability variant)...
                gen 03 06:41:15 Pi24 systemd[1]: Started LSB: dump1090 daemon (mutability variant).
                gen 03 10:38:01 Pi24 systemd[1]: Stopping LSB: dump1090 daemon (mutability variant)...
                gen 03 10:38:02 Pi24 systemd[1]: Stopped LSB: dump1090 daemon (mutability variant).
                gen 03 11:58:37 Pi24 systemd[1]: Starting LSB: dump1090 daemon (mutability variant)...
                gen 03 11:58:38 Pi24 systemd[1]: Started LSB: dump1090 daemon (mutability variant).
                Pi that's working fine at my home with black DVB-T dongle and internal small TV antenna installed (MCX connector) in my living room (not best place but receives a good amount of a/c):
                Schermata 2019-01-04 alle 08.48.12.png
                Code:
                pi@ads-b:~ $ sudo journalctl -u dump1090-mutability -e --no-pager -n20
                -- Logs begin at Thu 2016-11-03 18:16:44 CET, end at Fri 2019-01-04 08:21:19 CET. --
                gen 02 09:21:02 ads-b systemd[1]: Starting LSB: dump1090 daemon (mutability variant)...
                gen 02 09:21:06 ads-b systemd[1]: Started LSB: dump1090 daemon (mutability variant).
                I left yesterday evening my parents' home and I'll be back probably next month, so I can't test with 7cm wire on dongle as my dad is not very into this kind of things. I will as soon as I'll be there anyway.

                abcd567
                Answering you questions:
                1. I checked several times and everything is correctly connected
                2. Don't have a second SMA connector but I will buy on Amazon the same black dongle with antenna that is working at my home to further troubleshoot
                Schermata 2019-01-04 alle 08.48.12.png
                3. I will as soon as I'm back to my parents' place.
                4. How can I do it? The cable from the antenna is running inside a corrugated pipe from the roof to the attic. Should I remove all the antenna cable and check cm by cm?

                to everyone
                The things I don't understand are:
                1. WHY, when I first tested and configured the Pi in my bedroom with antenna laid on my bed it was receiving a lot of a/c and when I moved it to my attic and passed the antenna cable from the rooftop through the corrugated pipe to the attic and connected everything up, it stopped working;
                2. WHY, when I stop dump1090-mutability service and opening GQRX app, searching for known freq (radio FM and ATC freq), I'm able to listen them. Radio FM very clearly while ATC freq a bit disturbed, but I don't know if it's due to my position or due to settings on squelch.


                Sorry for the long post, but I tried to be the as clear as possible to help you guys.
                Thanks again

                Comment


                • #98
                  While the antenna is not optimized for it FM signals are much stronger than ADSB signals.
                  So if there is simply a bad connection you can still receive FM signals but no ADSB signals.
                  Also the damaged cable could still be good for carrying the relatively low frequency of radio (FM around 100 MHz while ADS-B is 1090 MHz).
                  Different frequencies behave much differently that's why for lower frequency the coax is much cheaper.
                  (You could for example have damaged the coax by bending it too sharply)

                  I'm sorry about the log command i forgot mutability does not emit anything useful to the system log. (i normally work with the flightaware version which is basically the successor which everyone can use no matter if you feed there)

                  Your log is located at /var/log/dump1090-mutability.log
                  So use the command
                  sudo cat /var/log/dump1090-mutability.log
                  and post the output please (I assume you have port forwarded SSH and setup a dyndns?)

                  Anyway there really is no good explanation for it to work before installation and not after except you breaking the coax.
                  Looking at all the logs does not hurt though.
                  Last edited by wiedehopf; 2019-01-04, 08:52.

                  Comment


                  • #99
                    I really hope not to have broken the coax cable as it is new . Bought it right before going to my parents' home
                    Anyway I do have SSH and created a dyndns to access to dump1090 map, fr24feed page remotely but to give seminal commands I really prefer using TeamViewer.

                    Here is the last section of *.log file of Pi not working:
                    Code:
                    Statistics: Fri Jan  4 07:58:38 2019 CET - Fri Jan  4 08:58:38 2019 CET
                    Local receiver:
                      8640004096 samples processed
                      0 samples dropped
                      0 Mode A/C messages received
                      123576216 Mode-S message preambles received
                        80205000 with bad message format or invalid CRC
                        43371021 with unrecognized ICAO address
                        10 accepted with correct CRC
                        185 accepted with 1-bit error repaired
                      -16.3 dBFS noise power
                      -16.3 dBFS mean signal power
                      -15.4 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
                    195 total usable messages
                    22 surface position messages received
                    67 airborne position messages received
                    0 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
                    2 local CPR attempts with valid positions
                      0 aircraft-relative positions
                      0 receiver-relative positions
                    87 local CPR attempts that did not produce useful positions
                      65 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
                    194 unique aircraft tracks
                    191 aircraft tracks where only one message was seen
                    CPU load: 25.1%
                      626078 ms for demodulation
                      258275 ms for reading from USB
                      20475 ms for network input and background tasks
                    
                    
                    Statistics: Fri Jan  4 08:58:38 2019 CET - Fri Jan  4 09:58:38 2019 CET
                    Local receiver:
                      8640004096 samples processed
                      0 samples dropped
                      0 Mode A/C messages received
                      125485302 Mode-S message preambles received
                        81500179 with bad message format or invalid CRC
                        43984919 with unrecognized ICAO address
                        16 accepted with correct CRC
                        188 accepted with 1-bit error repaired
                      -16.5 dBFS noise power
                      -16.6 dBFS mean signal power
                      -15.8 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
                    204 total usable messages
                    27 surface position messages received
                    61 airborne position messages received
                    0 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
                    6 local CPR attempts with valid positions
                      0 aircraft-relative positions
                      0 receiver-relative positions
                    82 local CPR attempts that did not produce useful positions
                      55 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
                    201 unique aircraft tracks
                    198 aircraft tracks where only one message was seen
                    CPU load: 25.1%
                      620823 ms for demodulation
                      260822 ms for reading from USB
                      20522 ms for network input and background tasks
                    Here instead the last section of *.log from Pi working at my home place:
                    Code:
                    Statistics: Wed Jan  2 09:21:06 2019 CET - Fri Jan  4 09:07:28 2019 CET
                    Local receiver:
                      410424836096 samples processed
                      0 samples dropped
                      0 Mode A/C messages received
                      822578287 Mode-S message preambles received
                        406968161 with bad message format or invalid CRC
                        414498578 with unrecognized ICAO address
                        978484 accepted with correct CRC
                        133064 accepted with 1-bit error repaired
                      -40.0 dBFS noise power
                      -26.4 dBFS mean signal power
                      -2.2 dBFS peak signal power
                      61 messages with signal power above -3dBFS
                    Messages from network clients:
                      0 Mode A/C messages received
                      6654 Mode S messages received
                        0 with bad message format or invalid CRC
                        0 with unrecognized ICAO address
                        6654 accepted with correct CRC
                        0 accepted with 1-bit error repaired
                    1118202 total usable messages
                    201 surface position messages received
                    92503 airborne position messages received
                    81125 global CPR attempts with valid positions
                    4 global CPR attempts with bad data
                      0 global CPR attempts that failed the range check
                      3 global CPR attempts that failed the speed check
                    76 global CPR attempts with insufficient data
                    10649 local CPR attempts with valid positions
                      0 aircraft-relative positions
                      0 receiver-relative positions
                    926 local CPR attempts that did not produce useful positions
                      723 local CPR attempts that failed the range check
                      2 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
                    3254 unique aircraft tracks
                    1854 aircraft tracks where only one message was seen
                    CPU load: 14.6%
                      14425663 ms for demodulation
                      9486023 ms for reading from USB
                      1271911 ms for network input and background tasks
                    If it helps, as my ISP has dynamic public IP, I can give you in pvt my actual IP and ports to see what I see (so nothing )
                    Last edited by maverick464; 2019-01-04, 09:22.

                    Comment


                    • Ok so this is interesting.

                      It looks like you have some massive noise that you are receiving.
                      Might be something producing noise where you installed the antenna.
                      Might be noise were the dongle is (less likely in my opinion)

                      You could try the rtl-sdr blog LNA to improve that. (It's very good at filtering noise, though your level of noise is really something else)

                      Tracking down the source of the noise would probably require you to try mounting the setup somewhere else.
                      For example trying it out near a window in your parents house. It could well be that there is some strong mobile tower near your parents house or whatever is producing that horrible noise could be some bad tech in your parents house. It's hard to guess but moving the antenna might give you a hint.

                      You could also try do a spectrum scan following the guide of abcd567
                      (https://discussions.flightaware.com/.../2?u=wiedehopf)
                      (If you are curious i compared several filtering options here: https://discussions.flightaware.com/.../6?u=wiedehopf)
                      (I never recorded a baseline with the rtl-sdr dongle alone, the blue stick already has good filtering built in)

                      This might give us some hint what the type of noise is
                      It's somewhat technical with the installation stuff but you seem capable enough.
                      Last edited by wiedehopf; 2019-01-04, 10:08.

                      Comment


                      • Mmmmhhh could it be caused by the position of the antenna? See post #89 pic 4 the scheme I draw about installation.
                        Could it be caused also by possible broken/bended coax cable? Sorry for newbie question but I AM a newbie in freq field.
                        Why it worked when the antenna was on my bed? Probably the reason of noise has to be looked in one of the above questions?

                        I'll consider in buying a filter after having further troubleshooted with another dongle to narrow the problem down

                        Thanks anyway for the advice and now I'll try to do a spectrum scan if I manage to....

                        And here it is. I divided it in 4 pieces as in first upload the original file was resized and was unreadable.

                        Even if I'm a completely ignorant in frequencies and spectrum I can clearly see that my spectrum is a real mess....isn't it?

                        800-920.jpg

                        920-1000.png

                        1000-1120.jpg

                        1120-1200.png
                        Attached Files
                        Last edited by maverick464; 2019-01-04, 12:49.

                        Comment


                        • No a broken coax would present differently and if you can remember really abusing it like bending it really sharply or squeezing it really hard then i can't see how it would get damaged.

                          Which other dongles do you have? (As i mentioned some have a filter builtin)

                          There is strong mobile band noise at 950 MHz which can be a problem in itself.
                          But the real problem making you unable to receive anything is that smeared out noise that goes basically all the way from 1080 to 1160 MHz
                          Not sure where noise on that frequency comes from really.

                          Also not sure if any filter would help against that noise.
                          Because the filter can't filter noise at 1090MHz.


                          It worked when the antenna was in your room in your parents house?

                          Then mounting somewhere in the attic or at another location on the roof might be the solution.
                          You could also try unplugging the SAT receiver to test if it works then (could be backfeeding noise into the satellite dish, though that would be problematic for TV reception as well i guess)

                          Comment


                          • No, I've been very careful in installing the coax cable, did not abuse it

                            The dongle I have are:

                            This one at my parents' home bought at jetvision DOT de website in bundle with antenna and coax cable
                            Schermata 2019-01-04 alle 14.22.13.png

                            This one at my own place working like a charm even though it's an "old" version compared to the one above.
                            Schermata 2019-01-04 alle 14.22.52.png

                            The black one is the one I'll buy again on Amazon, to further troubleshoot as I have a SMA/MCX adapter at home, next time I go to my parents.

                            I'll then try to move the antenna away from SAT dish (even if it's unused since years, no decoder connected to it) and from TV antenna.

                            For the moment, unfortunately, I can't do much more remotely from my home.

                            I'll report the tests made and hopefully the solution for future users reference, as soon as I go to my parents' place next month.

                            Thanks abcd567 and wiedehopf for your patience and hints, I learned some new coding lines that will be helpful in future, probably.

                            Happy New Year

                            Comment


                            • Don't buy the jetvision dongle, the rtl-sdr blog dongle is better

                              Or get a flightaware blue dongle, it has a builtin amplifier and SAW filter.

                              Don't see the dongle being the problem. You just have unusual noise nothing to do with the dongle

                              Comment


                              • Thought they were the same dongle from jetvision and RTL-SDR website....
                                Do you think this one is better? FlightAware dongle

                                Comment

                                Working...
                                X