(Background: I've been involved with Radios for a long time - my first scanner was a wonderful 8 crystal unit with a neat Night Rider LED display, but since then I've used many scanners - most recently, a RS Pro-106; I understand the basics of Trunked radio systems and scanners generally)
I just purchased a BCD996XT for mobile monitoring. I'm seeing plenty of differences between the Pro-106 and the BCD996XT, specifically the strange (coming from GRE) limitation on how many trunk groups per "system" can be loaded while also having a scanner with tons more memory. I like much of the Uniden, specifically the GPS capability and the capability to easily turn on and off monitoring of specific sites - will be very useful mobile! (so far, having used both the GRE-ish and Uniden modern models, they both seem to work well for decoding DTRS and the Arvada system; The Uniden seems to pull Denver in better from my home, the GRE seems a bit faster at scanning multiple systems)
I'm using Arc XT and FreeScan (both have different advantages it seems) to program the radio.
So, my main question:
How do most people here set up DTRS on these rigs, particularly while mobile and traveling through Colorado (I don't have a GPS hooked up yet, but will later)? What tips could you give someone just starting to program it that might save me some grief? I'll also likely be listening (at times) to some of the municipal (Lakewood, Denver) trunked systems. I won't be listening to much conventional.
Some other questions:
What I did on the Pro-106 was to set it up to listen to Lookout (good signal at home) and add all the talkgroups that would commonly be heard on Lookout. I then locked out anything I wasn't interested in, but set the radio up with a wildcard talk group. This let me hear new TGs that might not be listed in any public database - something I found interesting. When the call came through on a new TG, I'd hit F3, save it, and then revisit it later (typically looking here for information). Is there some similar feature on the Uniden?
I've noticed scanning multiple systems feels "slow" (for instance, I might want to monitor an incident that involves Jeffco SO and Arvada PD). I've set the system/site hold times to "0". Is there anything else I should be doing?
Basically, I'm looking for "tips and tricks" to this scanner with a Colorado slant.
I just purchased a BCD996XT for mobile monitoring. I'm seeing plenty of differences between the Pro-106 and the BCD996XT, specifically the strange (coming from GRE) limitation on how many trunk groups per "system" can be loaded while also having a scanner with tons more memory. I like much of the Uniden, specifically the GPS capability and the capability to easily turn on and off monitoring of specific sites - will be very useful mobile! (so far, having used both the GRE-ish and Uniden modern models, they both seem to work well for decoding DTRS and the Arvada system; The Uniden seems to pull Denver in better from my home, the GRE seems a bit faster at scanning multiple systems)
I'm using Arc XT and FreeScan (both have different advantages it seems) to program the radio.
So, my main question:
How do most people here set up DTRS on these rigs, particularly while mobile and traveling through Colorado (I don't have a GPS hooked up yet, but will later)? What tips could you give someone just starting to program it that might save me some grief? I'll also likely be listening (at times) to some of the municipal (Lakewood, Denver) trunked systems. I won't be listening to much conventional.
Some other questions:
What I did on the Pro-106 was to set it up to listen to Lookout (good signal at home) and add all the talkgroups that would commonly be heard on Lookout. I then locked out anything I wasn't interested in, but set the radio up with a wildcard talk group. This let me hear new TGs that might not be listed in any public database - something I found interesting. When the call came through on a new TG, I'd hit F3, save it, and then revisit it later (typically looking here for information). Is there some similar feature on the Uniden?
I've noticed scanning multiple systems feels "slow" (for instance, I might want to monitor an incident that involves Jeffco SO and Arvada PD). I've set the system/site hold times to "0". Is there anything else I should be doing?
Basically, I'm looking for "tips and tricks" to this scanner with a Colorado slant.