Because it seems you didn’t find what i was talking about:
I was just starting. The multiple instances on tar is my next challenge
Finally i got it working with TAR as combo following the instructions of @wiedehopf
the combined map on top, below the two single instances.
Maybe someone could help me with this. I’m trying to combine 2 feeders together. One on my network and another one offsite (let’s call it 111.111.111.111) with port 54321 open in the firewall pointing to the pi. I’m able to map to that IP and port to bring up the remote pi’s dump1090-fa page and see the live traffic no problem.
I’d like to run the combining feature on my local pi. I’ve tried a bunch of different options but nothing seems to have worked, I only see my local pi when I view the combined page. Below is what my source/ports/custom settings are. I think these are the only lines I need to change. Could someone tell me what settings I should be using or if I’m missing something? Thank you!
SOURCES= 127.0.0.1 111.111.111.111
PORTS= 30005 30105 54321
CUSTOM=111.111.111.111:54321
The map is on port 80 or/and 8080, the data you want are on 30005 and 30105 so you need to forward those ports as well.
To keep it easy just make the external port the same as the internal port.
Then the config becomes:
SOURCES= 127.0.0.1 111.111.111.111
PORTS= 30005 30105
That’s it no CUSTOM required.
AlternativelY:
If you use other ports, let’s say 55123 (forwarded to 30005) and 55124 (forwarded to 30105), then this would be the config:
SOURCES= 127.0.0.1
PORTS= 30005 30105
CUSTOM= 111.111.111.111:55123 111.111.111.111:55124
As you don’t use the same ports for all sources, you can put the ports in the ports list or it would try to connect to 55123 and 55124 on all sources, which would just result in a lot of error messages in the system log.
This did the trick, thanks so much for your help!
Can combine1090 also import positions from dump978-fa?
Can someone help me
I have two receivers + two pi
Want to combine data
Send A-data aggregation data to Flightradar24
Can someone tell me what settings should I use?
IP
A: peter6101.myftp.biz
B: peter6101.myftp.org
Port
A: 30005
B: 30005
How to send data from B to A
If you aggregate the data you need to disable MLAT.
Have you installed combine1090 and found the configuration file?
You will need it on the A receiver.
SOURCES= 127.0.0.1 peter6101.myftp.org
PORTS=30005
This should do the trick, but that is for display not for feeding as i said.
You should do the feeding from each receiver individually.
Hi Wiedehopf,
Thank you for this great tool!
I have a couple of questions:
I have three reicevers that I merge with combine1090.
- A via my local network picking up the the beast feed from port 30005 on 192.168.0.X
- B via the internet using a ddns service
- C via the internet by piping the beast output directly to port 29004 of the combine1090 instance
Option A works without any problems
Option B stalls usually overnight and combine1090 does not pick up the signals again so I would have to restart the service.
Option C works fine. Does it make a difference whether I pipe the signal direct to 29004 or whether I configure combine1090 to pick up the signals?
As my receivers are quite far apart from each other (one in Germany two in the UK) I initially struggled with the combined display as most of the traffic was displayed as Mode-S only. I got around this by setting “–max-range 1360”. Is that intended? Are there alternatives as some position reports are wrong?
Is there a way to see what position was provided by which receiver?
Thank you
Dennis
No.
I would expect this to be a dyndns problem with the IP not being updated, combine1090 should automatically reconnect.
I’m only making it easier to use socat and create a 2nd dump1090-fa instance, the rest is up to the user.
Some positions will be wrong, i suppose you can try my readsb dev branch to get around this issue, but that’s much more complicated and i wouldn’t really recommend it.
You shouldn’t need 1300 nmi though, just put the combine1090 location somewhere half-way?
@wiedehopf I have a FlightFeeder 978 (UAT) device.
I have added it’s IP on the combine list but I can’t see the planes from SkyAware 978 in the remote tar1090 window.
Do you have any ideas? I don’t have an instance of dump978 running on my tar1090 machine, I don’t think is needed…
PS: I want to avoid another spliter on the 978MHz antenna, that would mean adding a LNA, plus a receiver and a dump978 instance running.
Different formats.
Configure the skyaware978 URL directly in the tar1090 settings.
You mean like: [IP]/skyaware978/
Have you checked the config file yet?
It’s plenty obvious.
Note i wrote tar1090 settings, not combine1090 settings.
Just to avoid further confusion, i’ll quote the section:
# Change to yes to enable UAT/978 display in tar1090
ENABLE_978=no
# If running dump978-fa on another computer, modify the IP-address as appropriate.
# The URL needs to point at where you would normally find the skyview978 webinterface
URL_978="http://127.0.0.1/skyaware978"
Oh, now it makes sense. I was trying to use combine for this…
You could also transfer the 30978 data to a local skyaware via the skyaware settings
NET_OPTIONS="--connect localhost:30978 --reconnect-interval 30"
HISTORY_OPTIONS="--history-count 120 --history-interval 30"
But that would be kinda redundant.
And tar1090 gets the 978 data via http anyhow.
It’s not beast data … so dump1090 doesn’t know what to do with the data.
That’s a FlightFeeder 978, so I don’t have access to it’s settings.
I don’t see too many planes on UAT, most of the GA here switched to ADS-B 1090, I guess it become cheap enough…
Well you can install skyaware978 on the Pi and the --connect
option will connect to the feeder to get the data.
But as i wrote, doesn’t really make sense.