If you set the history that long … working as intended.
The HISTORY_SIZE=5400 and INTERVAL=16 is the fault?
I think that was the default, 24 hours.
that is not the default.
really that doesn’t matter, just change it if you want a shorter history.
1 Like
I thought it was browser cache? Those previous tracks go away if you just reload the Tar1090 page in your browser. Reloading also fills in the tracks that are not solid lines for some reason if you left the map loaded in a background browser tab for a long time.
e.g. My always running Tar1090 map, I click on this plane that approached from the east, landed for some hours and then took off again. I can initially see the pre-landing track from the east, and the new track after takeoff.
But if I refresh, I only see the track since take off. It’s behaved like this for as long as I can remember (using Chrome anyway).
All depends on how long the history is set to. (/etc/default/tar1090)
Page in the background isn’t allowed to run, so it can’t get data.
Reloading pulls in the more complete history.
2 Likes
Hi - completely new to this hobby. Hope this is on topic for this thread.
Kit is RPi 4B RaspberryOS 64 running Bullseye and rtl-sdr. Using sdrangel can display ~50 a/c so it basically works with a home made ground plane spider antenna which I plan to work on!
Have installed readsb and tar1090.
Have disabled kernel mods and systemd’s.
Can start readsb with rtl, console shows a/c. Can start 192.168.x.yy/tar1090/ on Firefox which gives blank map and error message.
Cannot get connection from server backend.
Readsb shows a/c in console.
Have looked at readsb.conf and increased gain to 30 and corrected location. Have looked at tar1090.js file and changed default map from Bing.
Have read all I can find to try to clear this error.
So now I’m asking what I’ve missed? A -net or socket connection?
Tks
R
You need to have the readsb systemd service running for all the usual stuff to work.
To then look at the data on the console use viewadsb.
Not sure why you wouldn’t want the systemd service … anyhow start it and check the command line with pgrep if you want to replicate it. You’ll also have to create the /run/readsb directory …
bing is never the default map …
Thanks for the quick response:
I disabled the readsb service so that it does not start on boot. I use the Pi for a number of different purposes.
The readsb command seemed to produce an output with aircraft on it.
I have started the readsb service, created the /run directory and now the map starts in the browser with the correct home location. However, there are no a/c on it.
And viewadsb shows the column headings, but no entries.
However, if I stop the service to release the tuner, then enter
$ readsb --device-type rtlsdr
I get aircraft.
BUT with that command running, viewadsb returns:
“Beast TCP input: Connection to 127.0.0.1 port 30005 failed: 111 (Connection refused)”
So I seem to be able to see aircraft. but not the map, while running the terminal command, and the map, but no aircraft, while running the service.
?
Tks
R
The service will create the /run directory itself.
This page shows how to check the log: Automatic installation for readsb · wiedehopf/adsb-scripts Wiki · GitHub
sudo systemctl disable readsb tar1090
That will prevent start on boot.
Then you will have to systemctl start those services when you want to use it.
The tar1090 service is for history things so it’s not strictly necessary.
You’ve done something wrong, i don’t know what, read the readme … check the journalctl log.
All working now, thanks.
It was the gain - I had set it in readsb.conf but that had not ‘taken’. The log showed that.
The sudo adjust gain command fixed it.
Takeaways I had not spotted from the documentation:
1 readsb is a serviced service, not a command line service. For my needs I had to disable both the kernel modules (to be able to use my pi headless) and the systemd service at boot, then enable them to use the applications.
2 map needs to be initially configured in the tar1090 .js file
3 gain needs to be configured via sudo and not via the readsb.conf file.
Many thanks!
R
It doesn’t need to be configured, you’re mistaken.
You can edit /etc/default/readsb just fine but if you use the wrong syntax it’s not gonna work.
Really if you follow the readme linked here: Automatic installation for readsb · wiedehopf/adsb-scripts Wiki · GitHub
It instructs you to set the location for readsb which is necessary to have the receiver location.
1 Like
Not sure if this is a bug or issue with my device, but after upgrading tar1090 today (changelog upgrade to jquery 3.6.1), the tracking map won’t load as shown in screen shot. This is on Pi4B running PiAware SD card install 7.2. Using Chrome 105 on Android 12 device.
EDIT: never mind! Cleared browser cache all is well
I upgraded tar1090 after today’s update (changelog support updating db features without aircraft going out of view or reloading the page). Ever since the tracking map and aircraft won’t load as shown in the screen shot above.
This time clearing browser cache/data has not resolved the problem. Nor has rebooting the Pi or reinstalling tar1090 via SSH.
Tracked aircraft are still visible as usual through FA’s SkyAware interface.
Does anyone have a suggestion?
not sure if this is the same issue or not. been using TAR1090 (FA) for quite a while (a couple of years). this morning nothing would happen. i reloaded tar 1090, no joy, i deleted tar 1090 and reloaded, still no joy. i cleared the browser, still nothing. 192,168,x,yy/skyaware works fine.
any comments??
all is now well, it took an uninstall, then restart pc, then reinstall…
http://192.168.2.18/tar1090/?showerrors
Let’s see if that shows anyhign (with the correct IP).
In the nearly 3 years I’ve been operating an ADS-B receiver, this is the longest I’ve ever seen tar1090 go between updates (last update Oct 6th). Not that it needs to be updated… it’s running great. Just hope everything is ok with @wiedehopf .
Try updating (if you feel the need)
That date is when you installed tar1090 but last actual update to tar1090 repo was on Oct. 6. That’s why there concern about @wiedehopf.
1 Like