I had noticed before, but not put a thought into a problem that I have when using Unitrunker to monitor this system. It is a splinter system and automatically recognizes it as so. It also tells me it's not a type I, but sometimes says it is a Type II or Type IIi.
I trained the PRO-96 on it while I was watching the system and discovered that a lot of the TG's that have been ID'd by Unitrunker don't really correspond to a single TG. Instead a number of TG's end up showing up on the same TG with the PRO-96.
For example, TG 3216 on the PRO-96 handles most of the traffic for this TG, but Unitrunker ID's the TG's as 3216, 3217, 3221, and 3222. It is definitely the same entity, as I will switch from trunk mode to listening to each of the individual active frequencies as shown by Unitrunker and can continue to hear the conversation.
So my question is, if this is a combination system, how do I use Unitrunker to identify the fleet map?
Attached is what I've learned from Unitrunker and a log file. The first part of the log file, I got about 85% read on this system. The second part it goes back to 100%.
Thanks for any assistance.
John
SE of Tucson
I trained the PRO-96 on it while I was watching the system and discovered that a lot of the TG's that have been ID'd by Unitrunker don't really correspond to a single TG. Instead a number of TG's end up showing up on the same TG with the PRO-96.
For example, TG 3216 on the PRO-96 handles most of the traffic for this TG, but Unitrunker ID's the TG's as 3216, 3217, 3221, and 3222. It is definitely the same entity, as I will switch from trunk mode to listening to each of the individual active frequencies as shown by Unitrunker and can continue to hear the conversation.
So my question is, if this is a combination system, how do I use Unitrunker to identify the fleet map?
Attached is what I've learned from Unitrunker and a log file. The first part of the log file, I got about 85% read on this system. The second part it goes back to 100%.
Thanks for any assistance.
John
SE of Tucson