is there a possibility to have more than one USB DVB-T receiver on a piaware device and to collect all these information with one instance of dump1090? It would be nice to cover different sides of a house with different receivers.
Yes, that’s how I have mine set up. The only thing to watch out for is that piaware will feed from whatever is providing data on local port 30005 (or 10001 if you have a version with FATSV support) - so make sure it’s the hub instance that’s on that port.
Yes. The hub dump1090 does basically everything a regular dump1090 does - it can generate the webmap or feed to other sources - it just gets its data indirectly from the receivers rather than directly from a RTLSDR dongle.
I’ve run a Wi-Fi dongle and an SDR on the B+ with no issues. More than two SDRs is going to push it – you want to go to a powered USB hub, which can introduce noise issues, but overcomes the power limitations.
Raspberry Pi 2 B with 6 times more CPU oomph and twice as much memory has gone on sale (at the same price as the old) - that should be able to supply the compute resource for four dongles, but you might need to run at least some of the dongles via a powered USB hub - just for the power requirement.
Okay, I’m still stupid with the command interface of the raspberry pi. (I used to be pretty handy with DOS though!)
I have raspbian running dump1090 and piaware with 1 rtl-sdr dongle to a CI-105 1/4 wave transponder antenna (perks of being an avionics installer).
I want to use my other rtl-sdr dongle to expand my coverage directionally with a home brew biquad.
What do I do?
I figure I need to install another instance of dump1090, configure it to use the new dongle specifically, and send it’s data to the original instance of dump1090. The original dump1090 then needs to be setup to receive the data from the new dump1090. Or am I completely off?
I should really get a Raspbian for Dummies book or something.
You don’t need to install a new copy of dump1090, you can reuse the existing install. You do need to configure it to run it a second time, though. Here’s an approximate outline:
Arrange to run a second copy with different command-line arguments. This will usually involve taking a copy of the existing init.d script and modifying it. The different arguments you will need are:
–device-index to specify which of the two dongles to use (it’s best to put this on both copies and identify them by serial number; you can set the serial number with rtl_eeprom)
One of the copies will need a bunch of extra arguments to change/disable the network ports it uses, so they don’t conflict with the other copy, something like: --net-bo-port 31005 --net-bi-port 0 --net-ro-port 0 --net-ri-port 0 --net-sbs-port 0 --net-http-port 0 (this moves the Beast output port to port 31005, and disables the other ports)
Arrange for a netcat tunnel between the two instances. I use a script like this. You are sending from “–net-bo-port” of one instance to the “–net-bi-port” on the other:
nc -d localhost 31005 | nc -q1 localhost 30004
Arrange for everything to be started on boot (not enough space in this margin to explain)