How to remove this line?
Do I need to reload 1090-fa?
I upgraded to version 5.0, and when I open IP/combine of my feeder that links all of my local feeders, I see this narrative across the Flightaware display page. Any ideas?
I’ve changed combine1090 over to use tar1090 as an interface.
Reinstall combine1090 please, the settings file will stay intact and the interface continue to be at /combine1090.
3 Likes
Curious if there is an option to compile for openwrt 19. (TL-WDR3500 Atheros AR9344)
I am looking for a way to transfer data from a remote receiver to a Virtualradar server through a router.
You should just use socat?
That’s what combine1090 uses for the data redirection.
At some point i will probably change it to just use readsb and the --net-connector functionality.
But maybe i’ll just leave it with socat.
So … if you want to use the script … see the readme there is a “redirect-only” option.
If socat is available and bash and systemd services … then i would expect combine1090 to work.
99.9% certain you’ll get socat for OpenWRT.
Yes. I use socat in script:
while true
do
socat addr1 addr2
sleep 1
done
but I have no idea how redirecting multiple ports with socat.
Multiple socat processes.
Have you checked the shell script combine1090 uses?
GitHub - wiedehopf/combine1090: Combine data from multiple ADS-B receivers into one readsb decoder / tar1090 webinterface
Really just use that script together with the service and config file 
I did the update as you directed, but it did not remove the warning banner from the IP/combine1090 screen view. If I go to IP/skyaware URL, I still get the warning banner, and no combined feeder input. Just the output of the one feeder that I use to show the combined feed of all on my local network. Any ideas how to remove the banner overlay? Thanks, KB4ERT…
I’m sorry it seems i forgot to push / publish my changes to github.
Try again with the update please
/skyaware should never have the warning … only /dump1090-fa should have it.
But really that’s not a combine1090 problem 
With the actual update now /combine1090 will be independent of the skyaware/dump1090 interface.
I started with fresh image and was reinstalling Tar1090-combine so i could see both of my receivers on one instance of tar1090. It wasn’t working for me (user error i would suspect), so i wanted to just uninstall and start over. I removed the instance and then used the command as shown on the github page. It threw some errors. What was strange was it was trying to stop tar1090-tar1090-combo service. So i issued the command without the tar1090-combo and just combo. It seemed to work. Was wondering if there was something in the updated install that may be an issue? Anyway, wanted you to know.
pi@piaware:/usr/local/share/tar1090 $ sudo bash /usr/local/share/tar1090/uninstall.sh tar1090-combo
--------------
Removing tar1090, instance name tar1090-tar1090-combo!
--------------
Failed to stop tar1090-tar1090-combo.service: Unit tar1090-tar1090-combo.service not loaded.
Failed to disable unit: Unit file tar1090-tar1090-combo.service does not exist.
Configuration is left to be removed manually, you can use this command:
sudo rm /etc/default/tar1090-tar1090-combo
--------------
tar1090 is now gone! Shoo shoo!
and without tar1090-combo and just combo
pi@piaware:/usr/local/share/tar1090 $ sudo bash /usr/local/share/tar1090/uninstall.sh combo
--------------
Removing tar1090, instance name tar1090-combo!
--------------
Removed /etc/systemd/system/default.target.wants/tar1090-combo.service.
Configuration is left to be removed manually, you can use this command:
sudo rm /etc/default/tar1090-combo
--------------
tar1090 is now gone! Shoo shoo!
Maybe an old tar1090 version or something …
I can’t reproduce the issue.
1 Like
Fresh install, i’ll keep playing with it. Was confused when the uninstall put the extra tar1090 in the argument. Frustrated i can’t get it working again, was working fine before!!! User errors are so hard to diagnose!!!
Thanks, much appreciated!
Huh oh that’s intended behaviour.
I thought you were using the combine1090 uninstall.
So the URL is /combine1090 and that is the instance name.
To make it clear that the service is a tar1090 service it’s called tar1090-instance while the URL is at /instance.
As such the uninstall wants the instance not tar1090-instance.
1 Like
Doh! User error. Thanks!
I installed combine1090 but it doesn’t seem to work for me. Tried to load 192.168.1.151/combine1090
I get this message: Problem fetching data from the server: Seems the decoder/receiver/backend isn’t working correctly!
So, being an amateur, i was looking at /lib/systemd/system/tar1090-combine1090.service specifically this line:
ExecStart=/usr/local/share/tar1090/tar1090.sh /run/tar1090-combine1090 /run/combine1090
The directory combine1090 doesn’t seem to exist in the directory /run/
tar1090-combine1090 does exist. Does this have anything to do with my issue?
What did I do wrong? This is a fresh install of PiAware 5.0. Thanks for any hints and I apologize for messing up something simple!
It’s just a consequence.
The service you need to check is combine1090-dump … not sure why it wouldn’t work.
How exactly did you install?
Followed the instructions on your page: GitHub - wiedehopf/combine1090: Combine data from multiple ADS-B receivers into one readsb decoder / tar1090 webinterface
sudo bash -c “$(wget -q -O - https://raw.githubusercontent.com/wiedehopf/combine1090/master/install.sh)”
pi@piaware:~ $ sudo find / -name combine1090-dump*
/usr/lib/systemd/system/combine1090-dump.service
find: ‘/proc/24003’: No such file or directory
find: ‘/proc/24012’: No such file or directory
find: ‘/proc/24031’: No such file or directory
find: ‘/proc/24120’: No such file or directory
/tmp/combine1090-master/combine1090-dump.service
/etc/systemd/system/default.target.wants/combine1090-dump.service
Not sure if this means anything…
pi@piaware:~ $ sudo systemctl start /usr/lib/systemd/system/combine1090-dump.service
Failed to start usr-lib-systemd-system-combine1090\x2ddump.service.mount: Unit usr-lib-systemd-system-combine1090\x2ddump.service.mount not found.
pi@piaware:~ $
You check the log, haven’t you seen the page? Debug commands · wiedehopf/adsb-wiki Wiki · GitHub
Just kidding
It’s
sudo journalctl -u combine1090-dump | tail -n30
Also you don’t specify the complete path to start a service.
You’d just do this:
sudo systemctl restart combine1090-dump
The .service at the end is optional.
Thank you for being patient with me, learning!!
pi@piaware:~ $ sudo systemctl restart combine1090-dump
pi@piaware:~ $ sudo journalctl -u combine1090-dump | tail -n30
Mar 17 15:28:49 piaware systemd[1]: combine1090-dump.service: Service RestartSec=30s expired, scheduling restart.
Mar 17 15:28:49 piaware systemd[1]: combine1090-dump.service: Scheduled restart job, restart counter is at 236.
Mar 17 15:28:49 piaware systemd[1]: Stopped combine1090-dump - combine1090 dump1090-fa/readsb instance.
Mar 17 15:28:49 piaware systemd[1]: Started combine1090-dump - combine1090 dump1090-fa/readsb instance.
Mar 17 15:28:49 piaware systemd[5113]: combine1090-dump.service: Failed to execute command: No such file or directory
Mar 17 15:28:49 piaware systemd[5113]: combine1090-dump.service: Failed at step EXEC spawning /usr/bin/readsb: No such file or directory
Mar 17 15:28:49 piaware systemd[1]: combine1090-dump.service: Main process exited, code=exited, status=203/EXEC
Mar 17 15:28:49 piaware systemd[1]: combine1090-dump.service: Failed with result ‘exit-code’.
Mar 17 15:29:19 piaware systemd[1]: combine1090-dump.service: Service RestartSec=30s expired, scheduling restart.
Mar 17 15:29:19 piaware systemd[1]: combine1090-dump.service: Scheduled restart job, restart counter is at 237.
Mar 17 15:29:19 piaware systemd[1]: Stopped combine1090-dump - combine1090 dump1090-fa/readsb instance.
Mar 17 15:29:19 piaware systemd[1]: Started combine1090-dump - combine1090 dump1090-fa/readsb instance.
Mar 17 15:29:19 piaware systemd[5667]: combine1090-dump.service: Failed to execute command: No such file or directory
Mar 17 15:29:19 piaware systemd[5667]: combine1090-dump.service: Failed at step EXEC spawning /usr/bin/readsb: No such file or directory
Mar 17 15:29:19 piaware systemd[1]: combine1090-dump.service: Main process exited, code=exited, status=203/EXEC
Mar 17 15:29:19 piaware systemd[1]: combine1090-dump.service: Failed with result ‘exit-code’.
Mar 17 15:29:49 piaware systemd[1]: combine1090-dump.service: Service RestartSec=30s expired, scheduling restart.
Mar 17 15:29:49 piaware systemd[1]: combine1090-dump.service: Scheduled restart job, restart counter is at 238.
Mar 17 15:29:49 piaware systemd[1]: Stopped combine1090-dump - combine1090 dump1090-fa/readsb instance.
Mar 17 15:29:49 piaware systemd[1]: Started combine1090-dump - combine1090 dump1090-fa/readsb instance.
Mar 17 15:29:49 piaware systemd[6371]: combine1090-dump.service: Failed to execute command: No such file or directory
Mar 17 15:29:49 piaware systemd[6371]: combine1090-dump.service: Failed at step EXEC spawning /usr/bin/readsb: No such file or directory
Mar 17 15:29:49 piaware systemd[1]: combine1090-dump.service: Main process exited, code=exited, status=203/EXEC
Mar 17 15:29:49 piaware systemd[1]: combine1090-dump.service: Failed with result ‘exit-code’.
Mar 17 15:29:53 piaware systemd[1]: Stopped combine1090-dump - combine1090 dump1090-fa/readsb instance.
Mar 17 15:29:53 piaware systemd[1]: Started combine1090-dump - combine1090 dump1090-fa/readsb instance.
Mar 17 15:29:53 piaware systemd[6494]: combine1090-dump.service: Failed to execute command: No such file or directory
Mar 17 15:29:53 piaware systemd[6494]: combine1090-dump.service: Failed at step EXEC spawning /usr/bin/readsb: No such file or directory
Mar 17 15:29:53 piaware systemd[1]: combine1090-dump.service: Main process exited, code=exited, status=203/EXEC
Mar 17 15:29:53 piaware systemd[1]: combine1090-dump.service: Failed with result ‘exit-code’.
pi@piaware:~ $
Seems … i accidentally broke the install in certain cases.
Try try try again
(the install script)
Success!!! Thank you so much for your patience and rapid response! Have a wonderful rest of your day!