Posting this out of frustration.
I hate the BCD396XT's "Systems". If you put trunked systems into the scanner then when you browse those "systems" using Func+Encoder you're actually browsing sites, not systems. If any system has lots of sites that long list of sites pollutes the system navigation, you have to scroll through all of them. I used ArcXT to pull the trunked systems down from radioreference, and I named all of the systems. But those names don't even show up when you're scrolling through the systems menu. The site names do, and sometimes they're obscure or the same as site names in other systems, and you have no idea at a glance what you're looking at. I've had to manually rename lots of site names pulled down from RR to work around this. Then comes trying to enable/disable trunked systems with multiple sites. It seems like you can't lockout such a system, only individual sites? And to do that you have to set startup keys for every single one of them? Ugh!
For systems with many sites, this has lead me to simply leave them off the scanner altogether, even though I'd like to have them programmed in so I can listen to them occasionally, simply because the trunked systems management seems so poor.
A firmware upgrade that at least showed the system name + site when you were scrolling through systems and let you easily lockout entire systems would be huge IMO. Then I could leave all the local systems programmed in.
Am I doing something completely wrong? I feel like I must be...
I hate the BCD396XT's "Systems". If you put trunked systems into the scanner then when you browse those "systems" using Func+Encoder you're actually browsing sites, not systems. If any system has lots of sites that long list of sites pollutes the system navigation, you have to scroll through all of them. I used ArcXT to pull the trunked systems down from radioreference, and I named all of the systems. But those names don't even show up when you're scrolling through the systems menu. The site names do, and sometimes they're obscure or the same as site names in other systems, and you have no idea at a glance what you're looking at. I've had to manually rename lots of site names pulled down from RR to work around this. Then comes trying to enable/disable trunked systems with multiple sites. It seems like you can't lockout such a system, only individual sites? And to do that you have to set startup keys for every single one of them? Ugh!
For systems with many sites, this has lead me to simply leave them off the scanner altogether, even though I'd like to have them programmed in so I can listen to them occasionally, simply because the trunked systems management seems so poor.
A firmware upgrade that at least showed the system name + site when you were scrolling through systems and let you easily lockout entire systems would be huge IMO. Then I could leave all the local systems programmed in.
Am I doing something completely wrong? I feel like I must be...