Adding Plane tracker and filter to list

[leforet]

Hi,
Similar to the satellite tracking widget that is on the images (#1156). Would it be possible to use an ADSB feed(example https://www.adsbexchange.com) to identify trails that are possibly aircraft in the captured image.
In the example below we have a Delta flight going overhead. In this picture North is roughly at the bottom.

From ads exchange (https://globe.adsbexchange.com/?icao=ab3c61&lat=45.281&lon=-80.202&zoom=9.7&showTrace=2024-10-01 for illustration)

You can either have a ADSB receiver as part of the setup (https://www.adsbexchange.com/ways-to-join-the-exchange/build-your-own/ ) and/or subscribe services that will gather the information. The data on the right hand side of the adsb image would be displayed on the Indi-allsky image.

Any plane that is detected within XX distance and at XX flight it would be tagged as aircraft in the image filter. https://192.168.XxX.xXx/indi-allsky/gallery

[aaronwmorris]

This is an interesting idea. I will try to do some investigation.

[leforet]

If you have any questions, please ask away. Right now, I have a second PI with the ads receiver in it. I was planning on adding to the all sky, but I need to print a slightly larger case to fit all the equipment in there and make sure I have enough power on the PoE. Also to make sure the software plays nice.

[aaronwmorris]

@leforet If you have one of these ADSB devices, does it have its own API you can query to get information on planes?

[leforet]

Yes, once it is running. It will put up a local webpage that has the local environment showing the traffic in the air. typically the ip address of the raspberry pi (you can specify the port). example is http://192.168.XxX.XxX/tar1090/ It might be easier to scrape the page then to debug the feed.

Some details on the feed client I'm using
https://github.com/ADSBexchange/feedclient

looking at the html

then looking at the backend

I'm assuming that one of these scripts, css, html generates the table and you could use that.

[aaronwmorris]

I dug up an RTL SDR adapter I had in storage. I was able to setup dump1090-mutability and see the local airplanes on a map.

The nice thing about dump1090-mutability is it creates a JSON file on the file system which the web site loads, but this would be easily parsed by indi-allsky.

$ cat /var/run/dump1090-mutability/aircraft.json
{ "now" : 1727977835.8,
  "messages" : 4276,
  "aircraft" : [
    {"hex":"abc0c1","squawk":"7424","flight":"SWA2196 ","lat":32.770401,"lon":-85.501379,"nucp":7,"seen_pos":13.4,"altitude":37000,"vert_rate":0,"track":51,"speed":489,"category":"A3","mlat":[],"tisb":[],"messages":71,"seen":11.1,"rssi":-33.5},
    {"hex":"a50329","mlat":[],"tisb":[],"messages":6,"seen":79.1,"rssi":-35.8},
    {"hex":"ac5bb0","mlat":[],"tisb":[],"messages":162,"seen":67.9,"rssi":-33.4},
    {"hex":"a35e5b","mlat":[],"tisb":[],"messages":531,"seen":143.4,"rssi":-33.9},
    {"hex":"a33ca9","mlat":[],"tisb":[],"messages":170,"seen":298.7,"rssi":-33.7}
  ]
}

[leforet]

excellent news, I'm guessing there would have to be a distance/height filter that would take the site location and calculate if the aircraft could be seen from the lens.

[aaronwmorris]

I have made a first past with #1560 to support tracking aircraft. For the time being, I have added the ability to label the images with the aircraft information. A search function might come in the future, but that would take a lot more database work in order to make the the SQL queries perform well enough to work. The images are tagged in the database with the aircraft info, but trying to query that information will probably be very slow.

https://github.com/aaronwmorris/indi-allsky/wiki/ADS%E2%80%90B-Aircraft-Tracking

Attached are some images with labeled aircraft.

This one passed almost directly overhead.

[leforet]

if I do a TOP command, I can see both services running.

[aaronwmorris]

Make sure you setup the Aliases in the HTTPS virtual host. The URL when using Apache needs to start with https://

[leforet]

Sorry,
Apache is new to me. When you saw alias in the HTTPS virtual host. I'm assuming you are referring to the file /etc/apache2/sites-enabled/indi-allsky.conf

If so, then yes those have been unHashed in both locations.

ADSB Aircraft tracking

Alias /dump1090/data /run/dump1090-mutability
Alias /dump1090 /usr/share/dump1090-mutability/html

here is that file
Listen *:80
Listen *:443

<VirtualHost *:80>
RewriteEngine On

### Comment this section to permit HTTP access to indi-allsky
###  SESSION_COOKIE_SECURE will have to be set to "false" in flash config
RewriteCond "%{HTTPS}" off
RewriteRule "^/(.*)" "https://%{SERVER_NAME}:443/$1" [R,L]
###

RewriteRule "^/$" "/indi-allsky/" [R]

TimeOut 180
LimitRequestBody 1073741824

ProxyPreserveHost On
ProxyPass /indi-allsky/static !
ProxyPass /indi-allsky/images !
ProxyPass /indi-allsky unix:/var/lib/indi-allsky/gunicorn-indi-allsky.sock|http://localhost/indi-allsky
ProxyPassReverse /indi-allsky unix:/var/lib/indi-allsky/gunicorn-indi-allsky.sock|http://localhost/indi-allsky
ProxyTimeout 180


ExpiresActive On
ExpiresByType application/javascript "access plus 1 days"
ExpiresByType text/css "access plus 1 days"
ExpiresByType image/x-icon "access plus 1 days"
ExpiresByType image/jpg "access plus 90 days"
ExpiresByType image/jpeg "access plus 90 days"
ExpiresByType image/png "access plus 90 days"
ExpiresByType image/tiff "access plus 90 days"
ExpiresByType image/webp "access plus 90 days"
ExpiresByType image/x-jp2 "access plus 90 days"
ExpiresByType video/mp4 "access plus 90 days"
ExpiresByType video/webm "access plus 90 days"


<Directory /home/pi/indi-allsky>
    Require all granted
    Options -Indexes
</Directory>

<Directory /var/www/html/allsky/images>
    Require all granted
    Options -Indexes
</Directory>


Alias /indi-allsky/images /var/www/html/allsky/images
Alias /indi-allsky/static /home/pi/indi-allsky/indi_allsky/flask/static

### ADSB Aircraft tracking
Alias /dump1090/data /run/dump1090-mutability
Alias /dump1090 /usr/share/dump1090-mutability/html

<VirtualHost *:443>
RewriteEngine On
RewriteRule "^/$" "/indi-allsky/" [R]

TimeOut 180
LimitRequestBody 1073741824

ProxyPreserveHost On
ProxyPass /indi-allsky/static !
ProxyPass /indi-allsky/images !
ProxyPass /indi-allsky unix:/var/lib/indi-allsky/gunicorn-indi-allsky.sock|http://localhost/indi-allsky
ProxyPassReverse /indi-allsky unix:/var/lib/indi-allsky/gunicorn-indi-allsky.sock|http://localhost/indi-allsky
ProxyTimeout 180

RequestHeader set X-Forwarded-Proto expr=%{REQUEST_SCHEME}
RequestHeader set X-Forwarded-SSL expr=%{HTTPS}


ExpiresActive On
ExpiresByType application/javascript "access plus 1 days"
ExpiresByType text/css "access plus 1 days"
ExpiresByType image/x-icon "access plus 1 days"
ExpiresByType image/jpg "access plus 90 days"
ExpiresByType image/jpeg "access plus 90 days"
ExpiresByType image/png "access plus 90 days"
ExpiresByType image/tiff "access plus 90 days"
ExpiresByType image/webp "access plus 90 days"
ExpiresByType image/x-jp2 "access plus 90 days"
ExpiresByType video/mp4 "access plus 90 days"
ExpiresByType video/webm "access plus 90 days"


<Directory /home/pi/indi-allsky>
    Require all granted
    Options -Indexes
</Directory>

<Directory /var/www/html/allsky/images>
    Require all granted
    Options -Indexes
</Directory>


Alias /indi-allsky/images /var/www/html/allsky/images
Alias /indi-allsky/static /home/pi/indi-allsky/indi_allsky/flask/static


Protocols h2 http/1.1


SSLEngine on
SSLCertificateFile /etc/apache2/ssl/indi-allsky_apache.pem
SSLCertificateKeyFile /etc/apache2/ssl/indi-allsky_apache.key

SSLProtocol all -SSLv3 -TLSv1 -TLSv1.1
SSLHonorCipherOrder     off
SSLSessionTickets       off

# 1 week HSTS header
Header always set Strict-Transport-Security "max-age=604800; includeSubDomains"

### ADSB Aircraft tracking
Alias /dump1090/data /run/dump1090-mutability
Alias /dump1090 /usr/share/dump1090-mutability/html

pi@piCOMET:/etc/apache2/sites-available $

I've checked that there is ads-b data being created in /run/dump1090-mutability and /usr/share/dump1090-mutability/htm

[aaronwmorris]

Okay, just make sure you restart the apache2 service.

sudo systemctl restart apache2

What URL do you have configured?

[leforet]

Hi,
I restarted the apache as instructed.

for the URL, I'm using whatever the guidelines/wiki have stated ;). Not sure where to check.

It does seem to be working now

Just waiting for a plane to fly over head.

[ph03nix42]

I'm running an adsb server on another pi also, would this be easier to run local on the indi-allsky unit or keep maintained on a separate unit.

indi is on a Pi5 8gb with 512gb sd and a zwo676mc for reference

[aaronwmorris]

It is probably easier to run it on a separate unit, but ultimately, either will work. It is only really easier because dump1090 sets up its own lighttpd web server to serve the aircraft.json file. You can run it on the same device, you just have to perform some customizations to the indi-allsky Apache web server config to have indi-allsky and adsb operational at the same time.

dump1090-mutabiity is not particularly heavy, both softwares can easily run on the same device.

[czimm74]

Trying to install and get this running.

(indi-allsky) pi@allsky-pi5:~/indi-allsky $ ./misc/adsb_test.py
[ERROR]: URL returned 404
[INFO]: # xy:15,900 (Left)
[INFO]: # anchor:la (Left Justified)
[INFO]: # color:200,200,200
[INFO]: Aircraft

Do I need a ads receiver for this to actually work? Or did I just miss doing something in the steps?

[aaronwmorris]

Yes, a software defined radio device is necessary to receive the ADS-B broadcasts. I can see from the wiki instructions that is not clear so I have added a section on the hardware requirements. A RTL2832U USB dongle can cost anywhere from $20-$50 from the regular marketplaces.

[czimm74]

Okay, makes sense now. I sort of guessed that from reading this thread.

[Dentonknifeworks]

Its amazing that no airplanes are around when you want them for testing.
Having said that I am not able to get mine working.
My ADS is running on a different pi on my network. I created a script that monitors the aircraft.json and have it copy to /var/www/html every time it is updated.
So from my allsky I have http://192.168.254.167/aircraft.json in the ADS tab
I can use that address from the allsky in the web browser and get the json file and when I do a refresh it changes.
I have ran the adsb_test.py I get
pi@120NoIR:~/indi-allsky/misc $ python3 adsb_test.py
[INFO]: # xy:20,200 (Left)
[INFO]: # anchor:la (Left Justified)
[INFO]: # color:200,200,200
[INFO]: Aircraft
What am I missing? I am somewhat confused about what I need on the remote ADS pi but I figured it just needed the json file and by putting a live copy in the /var/www/html would do the trick.

[Dentonknifeworks]

I’m finding that the current setup is mostly working, as I can see some aircraft being identified. However, there are a few issues where certain aircraft aren't being identified, and in some cases, aircraft are being identified even though they don’t appear in the image.

I suspect this issue might be caused by network delay. Here's how my process currently works:

A remote Raspberry Pi generates the aircraft.json file with ADS-B data.
A script then copies this aircraft.json file to the HTML directory. (The script was sleeping 5 sec now changed to 1 will test more tonight.)
The AllSky software fetches the aircraft.json file via HTTP over the network.
I believe that the network delay introduced during this process might be causing the inaccuracies. A possible solution to improve this would be to run the ADS-B receiver directly on the same Raspberry Pi that’s running the AllSky software. This would eliminate the need to transfer the aircraft.json file over the network, making the system faster and, in turn, more accurate.

It’s something to consider if you plan on integrating ADS-B tracking into your AllSky setup.

Note: the script running at 1 sec now has helped.
What do you think? And thanks for your help I swear you never sleep like me LOL.

[ph03nix42]

I’m finding that the current setup is mostly working, as I can see some aircraft being identified. However, there are a few issues where certain aircraft aren't being identified, and in some cases, aircraft are being identified even though they don’t appear in the image.

I suspect this issue might be caused by network delay. Here's how my process currently works:

A remote Raspberry Pi generates the aircraft.json file with ADS-B data. A script then copies this aircraft.json file to the HTML directory. (The script was sleeping 5 sec now changed to 1 will test more tonight.) The AllSky software fetches the aircraft.json file via HTTP over the network. I believe that the network delay introduced during this process might be causing the inaccuracies. A possible solution to improve this would be to run the ADS-B receiver directly on the same Raspberry Pi that’s running the AllSky software. This would eliminate the need to transfer the aircraft.json file over the network, making the system faster and, in turn, more accurate.

It’s something to consider if you plan on integrating ADS-B tracking into your AllSky setup.

Note: the script running at 1 sec now has helped. What do you think? And thanks for your help I swear you never sleep like me LOL.

I'd be curious how you handle this setup. I'm running a setup identical to yours and found that my 676MC was hanging due to overheating in my enclosure, even with 2 40mm fans running to remove the excess heat. The adsb does run effectively when attached directly to the pi, but the usb stick gets really hot. I believe I was seeing temps around 60-65c with outside ambient temps up to 90-95f

[Dentonknifeworks]

Thats a good point them SDR's do run hot and if there in the same box as the camera that would not be good. Id run a USB extension cable outside the camera box and put the SDR in its own ventilated box.

[aaronwmorris]

Most aircraft are only visible overhead for an average of 60s. The exposure period (the time between exposures) probably has a greater effect on "visibility" in the images. If you take exposures every 60s, you only get one chance to see an aircraft and the aircraft might have moved out of view by the time aircraft.json is queried. The aircraft.json file is queried after the exposure is completed. The ideal exposure period for tracking aircraft is probably 15-20 seconds.

indi-allsky also sorts the display of the aircraft by the angular altitude. This is not to be confused with the "altitude" in common aircraft vernacular to express the elevation of the aircraft. I try to treat "altitude" as the angular expression, ie altitude and azimuth.

indi-allsky calculates the visual angular altitude to determine if the aircraft is visible to the observer. The elevation and distance to the aircraft are used to calculate the visual angle of the aircraft. I was using basic trig to calculate this, so it kind of assumes the earth is flat, but the values returned should be good enough for local calculations.

This motivated me to include the dropoff in Earth's curvature in my calculations, so as of #1593 , the dropoff is taken into account to determine the angular altitude.

[ph03nix42]

Thats a good point them SDR's do run hot and if there in the same box as the camera that would not be good. Id run a USB extension cable outside the camera box and put the SDR in its own ventilated box.

Still finding that the camera is hanging with SDR outside the unit in another protected enclosure, wonder now if it's something else. Going to try removing it from the system and patching to it from another RPi.

@aaronwmorris would a log be helpful in determining what might be causing the camera hang?

[czimm74]

If you still have issues with getting dump1090 installed. I found this page and followed it, helped a lot in getting things running.

https://forum.flightradar24.com/forum/radar-forums/flightradar24-feeding-data-to-flightradar24/9949-how-to-install-dump1090-mutability-on-rpi

This rabbit hole may be the death of me... ;)