That's why I always prefer two dongle setup
In addition to that, setting up has much more sense and is much more faster in switching to a call with higher priority
Undocumented NEXEDGE Trunk System... Except it's really strange
- Thread starter Facsimile
- Start date
That's why I always prefer two dongle setup
In addition to that, setting up has much more sense and is much more faster in switching to a call with higher priority
Is there a solution to capturing everything on a NXDN system? Maybe as many virtual machines as frequencies * 2 dongles? I could see that being a ton of dongs. 16 in this case.
Do you really want to hear everything on the system? Or are you just trying to get all TGs, Radio IDs, aliases? If the latter, then there is no reason to actually listen -- but there is a need to monitor the voice channels. And in that case set something up to capture all CC data, and then individual copies of something (DSDPlus or something else) + dongle for each of those copies just to monitor each voice freq 24/7.
Are you sure there are really 16 freqs to monitor? I know there are quitea few licenses, many with duplicate freqs. I'd really be surprised if they had 15 talkpaths set up for that system.
Not sure it's worth the effort for that type of system, unless you really REALLY want to listen to the whole thing. Otherwise, if you ran DSDPlus with two dongles, you would eventually get every radio ID, every alias, every talkgroup over a little bit of time. Once you get a radio ID and it's alias, lock it out. That's what I'd do.
I've monitored a helluva lot of large sites with DSDPlus and can comfortably say that on many very large sites I've gathered just about everythging I could with a single copy and a little bit of time.
Anyway, sounds like you want to go to extremes to monitor what would otherwise be a fairly boring system (other than getting radio IDs / talker aliases). YYou'll spend more time coming up with a solution than you would just putting a two-dongle setup together and letting it monitor 24/7.
Are you sure there are really 16 freqs to monitor? I know there are quitea few licenses, many with duplicate freqs. I'd really be surprised if they had 15 talkpaths set up for that system.
Not sure it's worth the effort for that type of system, unless you really REALLY want to listen to the whole thing. Otherwise, if you ran DSDPlus with two dongles, you would eventually get every radio ID, every alias, every talkgroup over a little bit of time. Once you get a radio ID and it's alias, lock it out. That's what I'd do.
I've monitored a helluva lot of large sites with DSDPlus and can comfortably say that on many very large sites I've gathered just about everythging I could with a single copy and a little bit of time.
Anyway, sounds like you want to go to extremes to monitor what would otherwise be a fairly boring system (other than getting radio IDs / talker aliases). YYou'll spend more time coming up with a solution than you would just putting a two-dongle setup together and letting it monitor 24/7.
No not at all, I'm just trying to see what it would take to monitor every voice channel at any given moment. This is more of a learning thing for me as I'm not fully making the connection. Earlier I thought you said that DSDPlus was only capable of using two RTL-SDRs (in my case). My hope was maybe DSDPlus was capable of using one dongle for the CC, and then multiple other dongles for the remaining VCs all in one instance. Since that doesn't appear to be the case, I was trying to come up with a scenario that would work - this is how I came up with 16 RTL-SDR dongles. Eight instances (for eight frequencies) of DSDPlus, each instance covering the same CC frequency but with a different VC frequency for each of the 2nd dongles.
Only eight. It's just extremely busy.
I really don't. I just want the knowledge of how or where my thought process is going wrong. One day a system might come along that I really do want to cover everything and I'd just like to be ready.
Chances are that if one day you find a system wher eyou really want to monitor everything, it'll probably be something like a P25 system where you can use something like SDRTrunk to monitor everything with one instance of SDRTrunk and some dongles. Heck, Denny has stated he is working on adding NXDN support. So it is likely going to happen one day.
But for any flavor of trunked system that doesn't provide any trunking info over the voice channel, you'd be in the same situation you are now.
Yes, DSDPlus supports two dongles at most (in a trunk-tracking fashion). I've never done it, but apparently you can run multiple copies from the same directory and use a particular command line switch to allow sharing of certain files . Somebody else would have to tell you how to do that, or you'd have to read the documentation in the TXT files.
To it just seems like you are way too concerned about monitoring every possible simultaneous conversation, on a system that likely is not that interesting. It's a system where, if you ran two dongles and two copies of DSDPlus in the fashion described in the TXT files you'd get 100% of control channel information and would be able eto track one conversation at a time. Eventually, during all of that you would get pretty much every radio ID and talker alias on the system. You would not have gotten every voice transmission that ever occurred though. For me, that is almost always enough for systems like that.
For things like statewide systems, they are usually P25, so you can just monitor the sites that you can receive with SDRTRunk and handful of dongles and copy 100% of the voice/CC traffic, record it, whatever.
I don't think I have anything more to add. Id just encourage you to go with the two-dongle, two FMP*, two DSPLUs copies as outlined in the TXT help files and capture data that way. You won't get every voice comm. But eventually you'll get pretty much all other relevant info (TGs, radio IDs, Aliases).
mike
But for any flavor of trunked system that doesn't provide any trunking info over the voice channel, you'd be in the same situation you are now.
Yes, DSDPlus supports two dongles at most (in a trunk-tracking fashion). I've never done it, but apparently you can run multiple copies from the same directory and use a particular command line switch to allow sharing of certain files . Somebody else would have to tell you how to do that, or you'd have to read the documentation in the TXT files.
To it just seems like you are way too concerned about monitoring every possible simultaneous conversation, on a system that likely is not that interesting. It's a system where, if you ran two dongles and two copies of DSDPlus in the fashion described in the TXT files you'd get 100% of control channel information and would be able eto track one conversation at a time. Eventually, during all of that you would get pretty much every radio ID and talker alias on the system. You would not have gotten every voice transmission that ever occurred though. For me, that is almost always enough for systems like that.
For things like statewide systems, they are usually P25, so you can just monitor the sites that you can receive with SDRTRunk and handful of dongles and copy 100% of the voice/CC traffic, record it, whatever.
I don't think I have anything more to add. Id just encourage you to go with the two-dongle, two FMP*, two DSPLUs copies as outlined in the TXT help files and capture data that way. You won't get every voice comm. But eventually you'll get pretty much all other relevant info (TGs, radio IDs, Aliases).
mike
To monitor "every voice channel" you need individual receivers for each voice channel. You would also need to be monitoring them in conventional mode.
Similar threads
