Nope.
Just run the script with a 2nd parameter in meters.
https://github.com/wiedehopf/tar1090#2-integrate-theoretical-range-outline-into-your-local-tar1090-display
I put it in the readme. (some time ago)
1 Like
Hm… why didn’t i see that? Another reason for cleaning the glasses 
I was looking at that, didn’t understand what that 3048 means.
I assume it’s that section:
# load two outlines, 10000 ft and 40000 ft
sudo /usr/local/share/tar1090/getupintheair.sh XXXXX 3048,12192
where XXXXX the map id is
Something needs to be restarted to “take” that. I tried to restart tar1090 and I still have the old contours.
Changed to readsb this morning and that was the first thing I noticed. I know my station pretty well, I can usually tell how many aircrafts that are in range by looking at the message rate.
The settings I used when changing to readsb had been in use for the last 36 hours.
Anyway, it’s working now (increased -w to 7 seemed to have helped remove most of them anyway) so I’m happy.
Will start looking into why I produce so many unknown icaos, there must be some reason that is happening.
Military radar near-by? Did you ever did a scan?
I live by a commercial airport, sweeping 1030MHz SSR, and needed some filtering.
Has nothing to do with the service and more to do with reloading the browser.
But my suspicion is you’re either using the wrong command line or the service isn’t working.
Well, I live inside a restricted fly zone (not permanently restricted for other aircrafts than military, just during exercises and such). I have a cavity filter before the tripple-filtered LNA (1m high-quality coax (LMR400 Ultraflex) between the antenna and cavity filter, then 15 cm patch cable (RG316) between the filter and the LNA) and then 10 meters of a lower quality cable (CFL200) from the outside box to the computer inside.
It’s been a couple of years since I did the last scan. Perhaps the military have set up something new around here to keep track of the constantly increasing Russian non-civilian air activity over the Baltic sea.
At times there are massive interference on the C-band weather radars around the Baltic Sea, now, when Zapad 21 is running it may be that the russians are using more heavy jamming equipment and other tecniques to pollute the spectrum. They have for years messed with the GPS signals in northern Sweden, Finland and Norway (around the Murmansk area) that have caused some problems for commercial aircrafts (https://aerospace.csis.org/data/gps-jamming-in-the-arctic-circle/)
1 Like
For the longest time, when I was trying to use “tar1090/?pTracks” my browsers would just bog down to a crawl, not responsive at all.
I did have selected “Use WebGL” in the web interface but that didn’t help at all.
Until today I got into this internet rabbit hole and I found out that by default WebGL hardware acceleration is NOT enabled in Edge or Chrome.
I did enable it per those instructions (it was indeed “Disabled” in both those browsers):
Oh, what difference it made!
Zooming and panning now is smooth and uses about 20-25% of my GPU (that’s an RTX3080Ti).
LE: Firefox, on my system, had it enabled by default.
@wiedehopf, I am very embarrassed to admit that I’ve made a complete mess of changing from dump1090-fa to readsb. I’ve got readsb running - graphs 1090 is working and I’m still feeding data to Flightaware. However, tar1090 isn’t working
I’ve tried uninstalling and reinstalling tar1090 without success - I think the problem is that the installer still thinks dump1090-fa is running.
This is what the service file looks like after my latest attempt to install tar1090. I had previously edited the ExecStart line to replace/run/dump1090-fa with /run/readsb but that got over written when I ran the update script.
# tar1090 systemd unit file
[Unit]
Description=tar1090 - compress dump1090 json data
Wants=network.target
After=network.target
After=readsb.service
After=dump1090-fa.service
[Service]
User=tar1090
SyslogIdentifier=tar1090
RuntimeDirectory=tar1090
RuntimeDirectoryMode=0755
EnvironmentFile=/usr/local/share/tar1090/example_config_dont_edit
EnvironmentFile=/etc/default/tar1090
ExecStart=/usr/local/share/tar1090/tar1090.sh /run/tar1090 /run/dump1090-fa
Type=simple
Restart=always
RestartSec=30
Nice=19
[Install]
WantedBy=default.target
Here is the log from the time I edited the service file:
jrg@raspi4-1:~ $ ls -la /run/readsb
total 24
drwxr-xr-x 2 readsb nogroup 140 Sep 16 08:03 .
drwxr-xr-x 34 root root 980 Sep 16 07:58 ..
-rw-r--r-- 1 readsb nogroup 506 Sep 16 08:03 aircraft.binCraft
-rw-r--r-- 1 readsb nogroup 3399 Sep 16 08:03 aircraft.json
-rw-r--r-- 1 readsb nogroup 1586 Sep 16 08:03 outline.json
-rw-r--r-- 1 readsb nogroup 221 Sep 16 07:58 receiver.json
-rw-r--r-- 1 readsb nogroup 4198 Sep 16 08:03 stats.json
jrg@raspi4-1:~ $ sudo nano /lib/systemd/system/tar1090.service
jrg@raspi4-1:~ $ systemctl daemon-reload
==== AUTHENTICATING FOR org.freedesktop.systemd1.reload-daemon ===
Authentication is required to reload the systemd state.
Multiple identities can be used for authentication:
1. ,,, (pi)
2. XXXX,, (jrg)
Choose identity to authenticate as (1-2): 2
Password:
==== AUTHENTICATION COMPLETE ===
jrg@raspi4-1:~ $ sudo restart tar1090
sudo: restart: command not found
jrg@raspi4-1:~ $ sudo systemctl restart tar1090
jrg@raspi4-1:~ $ sudo systemctl status tar1090
● tar1090.service - tar1090 - compress dump1090 json data
Loaded: loaded (/lib/systemd/system/tar1090.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2021-09-16 08:16:25 AEST; 11s ago
Main PID: 9072 (tar1090.sh)
Tasks: 3 (limit: 4165)
CGroup: /system.slice/tar1090.service
├─9072 /bin/bash /usr/local/share/tar1090/tar1090.sh /run/tar1090 /run/readsb
├─9090 /bin/bash /usr/local/share/tar1090/tar1090.sh /run/tar1090 /run/readsb
└─9117 sleep 8
Sep 16 08:16:25 raspi4-1 systemd[1]: Started tar1090 - compress dump1090 json data.
jrg@raspi4-1:~ $ sudo bash -c "$(wget -nv -O - https://github.com/wiedehopf/tar1090/raw/master/install.sh)"
2021-09-16 08:17:17 URL:https://raw.githubusercontent.com/wiedehopf/tar1090/master/install.sh [18301/18301] -> "-" [1]
9444 (process ID) old priority 0, new priority 10
/home/jrg /home/jrg
remote: Total 0 (delta 0), reused 0 (delta 0), pack-reused 0
From https://github.com/wiedehopf/tar1090-db
* branch master -> FETCH_HEAD
HEAD is now at ee21c99 database update (to keep the repository small, this commit is replaced regularly)
/home/jrg
/home/jrg /home/jrg
remote: Total 0 (delta 0), reused 0 (delta 0), pack-reused 0
From https://github.com/wiedehopf/tar1090
* branch master -> FETCH_HEAD
HEAD is now at d5b5e24 localstorage stuff
/home/jrg
Restarting tar1090 ...
Restarting lighttpd ...
--------------
To configure nginx for tar1090, please add the following line(s) in the server {} section:
include /usr/local/share/tar1090/nginx-tar1090.conf;
include /usr/local/share/tar1090/nginx-tar1090-persist.conf;
--------------
All done! Webinterface available at http://192.168.124.104/tar1090
All done! Webinterface available at http://192.168.124.104/persist
jrg@raspi4-1:~ $ journalctl -u tar1090
-- Logs begin at Thu 2019-02-14 21:11:59 AEDT, end at Thu 2021-09-16 08:20:46 AEST. --
Sep 16 07:58:30 raspi4-1 systemd[1]: Started tar1090 - compress dump1090 json data.
Sep 16 08:16:25 raspi4-1 systemd[1]: Stopping tar1090 - compress dump1090 json data...
Sep 16 08:16:25 raspi4-1 systemd[1]: tar1090.service: Main process exited, code=killed, status=15/TERM
Sep 16 08:16:25 raspi4-1 systemd[1]: tar1090.service: Succeeded.
Sep 16 08:16:25 raspi4-1 systemd[1]: Stopped tar1090 - compress dump1090 json data.
Sep 16 08:16:25 raspi4-1 systemd[1]: Started tar1090 - compress dump1090 json data.
Sep 16 08:17:22 raspi4-1 systemd[1]: tar1090.service: Current command vanished from the unit file, execution of the command list won't be resumed.
Sep 16 08:17:23 raspi4-1 systemd[1]: Stopping tar1090 - compress dump1090 json data...
Sep 16 08:17:23 raspi4-1 systemd[1]: tar1090.service: Main process exited, code=killed, status=15/TERM
Sep 16 08:17:23 raspi4-1 systemd[1]: tar1090.service: Succeeded.
Sep 16 08:17:23 raspi4-1 systemd[1]: Stopped tar1090 - compress dump1090 json data.
Sep 16 08:17:23 raspi4-1 systemd[1]: Started tar1090 - compress dump1090 json data.
Sep 16 08:17:23 raspi4-1 tar1090[9570]: /usr/local/share/tar1090/tar1090.sh: line 104: /run/dump1090-fa/aircraft.json: No such file or directory
Sep 16 08:17:23 raspi4-1 tar1090[9570]: No aircraft.json found in /run/dump1090-fa! Try restarting dump1090 or reinstalling tar1090 if you switched dump1090 to readsb!
Sep 16 08:18:23 raspi4-1 tar1090[9570]: /usr/local/share/tar1090/tar1090.sh: line 104: /run/dump1090-fa/aircraft.json: No such file or directory
Sep 16 08:18:23 raspi4-1 tar1090[9570]: No aircraft.json found in /run/dump1090-fa! Try restarting dump1090 or reinstalling tar1090 if you switched dump1090 to readsb!
Sep 16 08:19:23 raspi4-1 tar1090[9570]: /usr/local/share/tar1090/tar1090.sh: line 104: /run/dump1090-fa/aircraft.json: No such file or directory
Sep 16 08:19:23 raspi4-1 tar1090[9570]: No aircraft.json found in /run/dump1090-fa! Try restarting dump1090 or reinstalling tar1090 if you switched dump1090 to readsb!
Sep 16 08:20:23 raspi4-1 tar1090[9570]: /usr/local/share/tar1090/tar1090.sh: line 104: /run/dump1090-fa/aircraft.json: No such file or directory
Sep 16 08:20:23 raspi4-1 tar1090[9570]: No aircraft.json found in /run/dump1090-fa! Try restarting dump1090 or reinstalling tar1090 if you switched dump1090 to readsb!
I’ve tried deleting dump1090-fa:
apt purge dump1090-fa
systemctl disable dump1090-fa
rm -r /run/dump1090-fa
I think my problems started when I tried to install nginx prior to readsb without removing lighttpd first. That didn’t work, so I removed nginx again - but may have hosed something in the process
Is this recoverable or should I start from scratch? - while preserving the graphs 1090 data (and the data use for the cause scripts if it is still there)
Have you by chance put something in this file:
/etc/default/tar1090_instances
?
jrg@raspi4-1** : ~ $ cat /etc/default/tar1090_instances
/run/dump1090-fa tar1090
/run/dump1090-fa persist
Don’t remember putting these lines there - delete them?
If you don’t use /persist then just delete the entire file.
Then rerun the tar1090 install.
Thanks for your help…
I do have a /persist instance and also timelapse1090 (both also affected) - does that change the advice?
Well fix the file then.
Should be rather obvious what to change.
timelapse you need to change the config as described in the readme.
Running the install script will likely also fix timelapse up.
1 Like
Thanks again for your patience and prompt responses.
Replacing dump1090-fa with readsb in the file and then updating tar1090 worked on the two instances. I had to do the same edit in /etc/default/timelapse1090
to get timelapse running. 
I would still like to replace lighttpd with nginx.
When you have time, could you expand on the tar1090 readme to cover whether lighttpd needs to be deleted/disabled prior to installing nginx, or if it and nginx can coexist with appropriate port assignments?
Just change the port?
You’ll see.
1 Like
I just installed this. It’s great! I like the ability to select font and icon sizes, the fact that more page area is devoted to the map and that the infoblock also shows a picture of the aircraft. The only thing it’s missing vs. the original SkyAware page is the ability to configure the range rings.
it can be changed.
sudo nano /usr/local/share/tar1090/html/config.js
Roughly half way there is a section labeled Range Rings. Look for SiteCirclesDistances, can be searched using Ctrl-W, and type rings
the ranges can be set there, including distance, color and line type.
Then do a restart
sudo systemctl restart tar1090