Quote:
Originally Posted by CJR238  See what im saying?
These are the things that need to take place to have a problem with TrueLock:
1) Local radar is running in X or K
2) You lock out a location with X or K
3) the location you lock out with X or K happens to be the same 30MHz block the local LEO's are running
4) A LEO is running radar in that same locked out area.
5) His signal is of about the same strength of the false so it doesn’t alert out side the locked out area.
6) and lastly you are speeding in that "High Risk" area.
That’s more variables than what it takes to get a ticket with a RD that has no TrueLock. and at least with the 9500I you have the choice of locking out a source or not. |
I believe that for many people there's much more than a 1% chance that is possible. I do agree that some thought needs to go into how one utilizes the TrueLock feature. It IS a nice idea. The problem is I'm not convinced that it can be implemented to full effectiveness in every situation. In fact I'm convinced that it cannot be. And as I see it, how does the user know?
Example: there's a certain intersection that I drive by regularly. Since a couple of new buildings went up last year, I now count 8 or 9 K band alerts from my V1. Now, you mentioned the signal strength sensitivity of the 9500i's TrueLock. Well, those signals go across the board from 1 LED on the V1 indicator to full alert. As I drive by on the main road or coming up from a side road, the same thing happens. There are 3 stop lights within 200-300 feet of each other, and that makes it likely you will be annoyed with the your RD going berserk problem nearly every time you drive thru there.
On the other hand, in that same spot on both sides of the road you have access lanes - easy spots to setup a speed trap. And the PSL goes from 35 to 40 to 45 and vice versa on this road, with the part I'm talking about I think is 40. However, I'm not sure (I don't doubt the LEO's know either), as since it has built up you can't really figure out what the PSL is supposed to be. I think there's one sign going one direction and none in the other. But point is if you catch the lights right you can easily blow thru this area doing way over PSL (it's 3 lanes either side).
Anyhow... now, before you say, "See the V1 sucks because it's going to drive you crazy with all those K-band alerts," let me tell you that EVERY detector worth a crud goes ballistic here.
With my V1, I could set the K-band mute delay for longer than the factory default 10 seconds, but now instead I am using the GPS Mirror - which is a god-send.... Set the speed indicator to mute below a certain speed an voila! no more annoying K-band alerts in that area I'm talking about. If I'm zipping thru the area at a decent pace, the 10 second timer on the V1 will mute it. If I'm putzing along, the Cheetah Mirror mutes it.
Quote:
These are the things that need to take place to have a problem the V1's Junk feature:
1) LEO running real radar
2) V1 junking it
3) ticket
Hmmm, that looks like V1 didn’t test the "J" feature long enough?
|
Agreed, though that is very rare. I have never had that problem personally, and I've owned/used a V1 for about 5 years now. I did recently turn off the J feature though just in case. I think the J out feature is a bad idea if even 1 in a 1,000,000 times it J's out a real threat. I'd rather get spooked by the Ka bleeding Cobras, etc. on the road versus miss a real threat no matter how low the chance it will J it out. However, that's my choice. I like having all the input around me and letting me decide how to react versus my RD remaining silent because it thought something was bogus.
I think the main problem here are the bad Cobras, etc. setting off everyone else's Ka band alerts around them.