[WORKING] New ADSBExchange base image v1.0

The current install using htop shows a user "dump1090" running FA version.

 

Yes, the PiAware SkyView now shows the data correctly. However, Grafana isn't. Images attached.

(thanks for helping with this, btw)

 

This is where you start to lose me, I'm afraid.

So htop says dump1090exporter is located here: /home/pi/.local/bin/

There are two files in that location: "chardetect" and "dump1090exporter".

When I use nano editor to look at dump190exporter it gives the following output:

-----

#!/usr/bin/python3


# -*- coding: utf-8 -*-

import re

import sys


from dump1090exporter.__main__ import main


if __name__ == '__main__':

sys.argv[0] = re.sub(r'(-script\.pyw?|\.exe)?$', '', sys.argv[0])

sys.exit(main())

-----

I've no idea what part of that to update or edit. If there is a start-up file somewhere, I don't know where it is!

I prefer the PiAware version of dump1090 as it uses the coloured icon identifiers which give you info in a nicer way. Sadly, I also like the interface of Grafana....

 

Thanks. I await further info.

FYI. I'm looking at the dump1090-exporter GitHub page and to use that software the readme says it only works under python3. But this image with Grafana is python2.7 so I can't even re-install dump1090-exporter and update any settings. Slightly confused with that.

Standing by.

 

No .. there are 2 versions of python in the wild. 2.7 and 3.5 .. .they are separate installs

If you installed piaware, it installs dump1090-fa and auto force starts it. I have no idea what Flightaware is doing it but it breaks the image. Let me know if you figure it out.

it is not my fault Piaware & Flightware do not play nice.

I repeat it has nothing to do with what you are thinking... it is the Piaware installer installs dump1090-fa and that prevents dump109--mutability from starting via script because dump1090-fa has take over the SDR

figure out how to remove dump1090-fa of prevent it from starting on boot and image works

 

I've just discovered the python thing, James. Thanks for confirming. I ran "python -V" and it stated v2.7. That was part of the ever growing confusion... But I see that python3 is also installed. Baffling.

I installed PiAware alongside the image and it was uploading the data to FlightAware no problem. It just wasn't showing it locally at xx.xx.xx.xx.:8080 and that's what I wanted to use as it's my preferred GUI. The only way to get that to work is to force a re-install of dump1090. That's when it breaks the data getting to Grafana.

I left a message on GitHub about the ADSBx install script to include the Custom Feed port (which is what started this whole thing). I may just go back to my original install, and use the new GitHub script that he's updated to include the option of a Custom Feed port.

I'll keep an eye here to see what happens...

 

You can thank legacy code and developers for that - they have to maintain a Python 2 AND Python 3 because Python 3 broke so many things.

Because FA takes over the image, I can't support FA or FR24 when their forcibly break each other because they are commercial businesses selling your data for $. Feeders get nothing for it but some flashy green lights and images and charts and they sell your data to the highest bidder.

For my own sanity - I'm not beating my head against a wall of code every FA or FR24 update.

They don't even give you access to your own data.

I guess that install script is still being updated.

 

If you are dedicated then look through all the scripts .. remove dump1090 mutability from starting ... then reconfigure all the exporters, to look for wherever dump1090-fa hides the json files

That would probably get it to work.

Or figure out how to start dump1090-fa with the same args as in adsbexchange-dump1090_maint.sh

That will write the json to the correct places .... maybe ...

 

I hear you. I have aspergers, so having data and not feeding it to as many places as possible seems weird to me. That's how my brain works

The GitHub code I was referring to was updated 15hrs ago, to include the Custom Feed inclusion I requested. I'm keeping the Grafana image I've been working on (with the broken Grafana part), and I'm re-imaging another card with my old back-up to get myself back in the position I was yesterday. I'm going to try this new GitHub version he's updated, as to be honest all I was after was a way to have all my other original feeds still working and also uploading to ADSBx too. I stumbled across the Images on the forum and thought I'd give them a try. I've sat here for almost 8hrs now updating and reinstalling and re-imaging. Round and round!

 

Interesting. So someone is working on it.

 

Ugh ... I know how that feels. I'll see if I can reach out to that guy developing that script again.

 

Yes, don't get me wrong. If I roll back to the back-up I took of Grafana before I broke it (!) then everything IS uploading to all the correct places, including ADSBx. The only thing I couldn't get to work was the PiAware map with the coloured icons.

I like the numbers and data that Grafana shows, but I also prefer the dump1090 map with the coloured icons. Seems I can't have both. I'll still dig around with the Grafana version later, and see if I can find anything else that might help solve this.

 

Try taking the dump1090-fa html folder from git
and overwriting the

/usr/share/dump1090-mutability/html/

if all you want is the gaudy FA design


I has nothing to do with grafana or anything like that ... It's because dump1090-fa (the executable) is being launched or doing whatever it is doing without explaination or common sense

I'm pretty sure you can just swap the html from mutability and dump1090-fa f you want the FA interface

Hell if it's just the colored planes you want ... that's just in the config.js

 

in /usr/share/dump1090-mutability/html/config.js

Just un-comment the colored and comment out the monochrome.

Code:

/ -- Marker settings -------------------------------------
// These settings control the coloring of aircraft by altitude.
// All color values are given as Hue (0-359) / Saturation (0-100) / Lightness (0-100)
/*ColorByAlt = {
        // HSL for planes with unknown altitude:
        unknown : { h: 0,   s: 0,   l: 40 },
        // HSL for planes that are on the ground:
        ground  : { h: 120, s: 100, l: 30 },
        air : {
                // These define altitude-to-hue mappings
                // at particular altitudes; the hue
                // for intermediate altitudes that lie
                // between the provided altitudes is linearly
                // interpolated.
                //
                // Mappings must be provided in increasing
                // order of altitude.
                //
                // Altitudes below the first entry use the
                // hue of the first entry; altitudes above
                // the last entry use the hue of the last
                // entry.
                h: [ { alt: 2000,  val: 20 },    // orange
                     { alt: 10000, val: 140 },   // light green
                     { alt: 40000, val: 300 } ], // magenta
                s: 85,
                l: 50,
        },
        // Changes added to the color of the currently selected plane
        selected : { h: 0, s: -10, l: +20 },
        // Changes added to the color of planes that have stale position info
        stale :    { h: 0, s: -10, l: +30 },
        // Changes added to the color of planes that have positions from mlat
        mlat :     { h: 0, s: -10, l: -10 }
};
*/
// For a monochrome display try this:
 ColorByAlt = {
         unknown :  { h: 0, s: 0, l: 40 },
         ground  :  { h: 0, s: 0, l: 30 },
         air :      { h: [ { alt: 0, val: 0 } ], s: 0, l: 50 },
         selected : { h: 0, s: 0, l: +30 },
         stale :    { h: 0, s: 0, l: +30 },
         mlat :     { h: 0, s: 0, l: -10 }
 };

[CODE]

 

See Colors: