- Nov 13, 2016
- Reaction score
- Hill Country, TX
Yes, they’re different.And Vortex said it used to be Custom sweeps which acted differently to the new custom frequency setting I thought.
Think of it like the radio in your car. You can tell it to scan, and it will sweep the commercial broadcast radio frequencies until it hits something strong enough to stop. If you remove your antenna, it can’t receive anything worth stopping on, so it will keep sweeping until it hits the end of its frequency range and start over again at the bottom. It takes a few seconds at least for it to sweep that whole range and start over again, right?
What if you could tell the radio to only do that within, say, 90.1 to 94.5, and then 101.3 to 104.7? It would skip the rest, so you’d never hit on 88.9 or 97.6 or whatever was outside of those frequency ranges, and it would get through those narrower ranges much faster. That’s like what Custom Sweeps were for the Gen1. Whatever you set limited then detector’s range of frequencies it looked at, what frequencies it swept across. Of course, it was way faster than your car radio, so it didn’t make a huge difference, but it allowed you to turn off filtering on Ka (“Ka Guard”) which substantially increased range, and you could keep it from looking in areas that might turn up a false Ka alert (which otherwise would’ve been suppressed by Ka Guard).
Now what if your car’s radio was super fast at scanning (aka sweeping through) the whole spectrum, but it let you say don’t worry about stopping on any stations outside of those ranges we specified earlier? It would still sweep through the entire range of frequencies, but even if it found a station on 88.9 or 97.6, it wouldn’t stop on it since it knows you don’t want to listen to those stations. That’s what the Custom Frequencies are like on the Gen2. Unlike the old sweeps, it doesn’t change what frequencies the detector looks at. It sweeps through all of them super fast anyway. Instead, with Custom Frequencies enabled, when it sees something outside the windows you’ve specified, it simply doesn’t alert to it. It’s a little deeper than just superficial muting, apparently, as it fully ignores it, not surfacing an alert at all, at mute volume or otherwise.
I hope that helps.
Post automatically merged:
Those settings could use some work. For example the 33.8 range will alert no matter what you say. Hopefully they fix that in a future firmware update. But more importantly you have two separate frequency ranges defined that overlap slightly and go all the way from 34.592 to 35.166. That’s fine if you want to alert so high outside the 34.7 range, but why have two overlapping ranges? Why not just 34.592-35.166?Yeah that’s what I have. Just sounded like it didn’t really matter to have these, but from what you’re saying, it means anything outside of the ranges won’t alert? Yeah I always run segmented on my other detectors.
On K, which is a new option for the Gen2, I’ve never seen a threat higher than 24.194 (just one oddball cruiser), but I’ve seen some stationary falses up past 24.200, even up near 24.250. If you want to narrow things down, I’d probably suggest modifying the K range to top out at 24.200 or so. Your call, though.