I'm running 5 dongles and using sdrtrunk. I am having an issue with one of the dongles activity. I have the channels tied to specific dongles. My issue is that I have two dongles for a p25 trunked system but can only use the preference for one. Most of the voice channels are close enough to the control channel it doesn't need the second dongle. Sometimes the second dongle will go over and handle voice traffic for the 217 mhz mpt-1327 system. One dongle can easily handle the traffic on the mpt-1327 system. Herein lies the issue, I have yagis for everything but the 800 mhz p25 system. I live in a valley, in sight of 4 simulcast sites, so i have the gain turned all the way to zero and still have a great signal. So when the last dongle drifts to the mpt-1327 system it sounds terrible. What's the best way to "lock" the second dongle into the p25 800 mhz system?
SDRtrunk multiple dongles, multiple trunk systems
- Thread starter flatfoot859
- Start date
That solved my problem. I was way overthinking this. Thank you very much!
Post a link to the system(s) and site(s) your interested in.
Not sure what links you're looking for. I just want to understand how to set up a second dongle to handle P25 system decoding. Is there a way to set one dongle for the command channel and the other for voice? What is the right way to do this?
Post a link to the system in the database, and tell us what site(s) your looking to monitor. You may or may not need more than one dongle. Number of required dongles is based on the sites frequency span.
There is no setup. SDR trunk will use whats available when its loaded. Just plug in second third dongle restart SDR trunk.
There most certainly *IS* some setup required. I ran into problems trying to get 3 of the metal RTL-SDR dongles running on the Broward County, FLA trunked system. I could only get 2 of the 3 to do anything, but SDRtrunk goes out of its way to shield the user from metrics and diagnostics as to what's going on under the hood.
Finally, with no clear instructions anywhere I gave up and slapped an AirSpy R2 on there because it can cover the entire frequency range of their repeaters, now it runs fine. Now I see that the min and max frequency range might do the trick.
It's a warning sign that a newbie asks for help and instead of help he gets a demand for which system he wants to monitor. Teach a man to fish...
Knowing the system he wants to monitor is a fundamental question, and drives the troubleshooting process forward. I would agree that SDRTrunk is not plug and play for anything more complicated than a system/site that has a frequency spread of more than 2 MHz or so.
If you teach him how to figure it out, he can do it himself from that point forward without having to return to the Almighty Oracle of Knowledge every time he encounters a new system.
Similar threads
