Closed semisynthetic closed 1 year ago
Multi_rx supports two different methods of monitoring simultaneous voice channels. The key thing to remember is that every individual channel has to have access to the full RF spectrum of the P25 system being monitored without affecting any of the other channels. To that end, since most P25 systems occupy more than the ~2Mhz max usable bandwidth available from the cheap RTL dongles, you either need to dedicate one dongle per voice channel and make the devices tunable (tunable=true) or have one or more wideband receivers (e.g. Airspy) set up with sufficient bandwidth to capture the whole P25 system at the same time and designate it non-tunable (tunable=false). What you can't do is share a tunable device between two channels, because re-tuning channel A would implicitly affect channel B.
In addition to the above, multi_rx does not support the system hopping capability that could be achieved in rx.py when multiple lines were entered into trunk.tsv. My reasoning is that RTL devices are inexpensive (~$25) and the advantage of true simultaneous monitoring far outweighs the disadvantages of the small added cost. With rx.py the time-based hopping between systems just caused lots of traffic to be missed.
OK, understood, and I agree. The time it takes for these freqs to monitor in rx.py, a lot is lost. Thanks!
I've been working with multi_rx.py configuration, and I can get things working fine with one P25 trunk and channel configured (for my single rtl-sdr). However, when I try to add a second P25 trunk, it seems it will not allow this. I get
Also, I was assuming I should at least be able to replicate the functionality of rx.py, on some level, and I can't seem to do that.
Here's the config I'm working with (I'm outputting audio to liquidsoap, or at least trying to).
Any idea what I'm doing wrong?