Well, post the ticket in the beat the ticket section if you want. It would prove that the ticket is legit. (not that I'm saying you're lying or anything)
Contact Escort about this ASAP.
So guys, is this the first TL ticket ever reported here?
Well, post the ticket in the beat the ticket section if you want. It would prove that the ticket is legit. (not that I'm saying you're lying or anything)
Contact Escort about this ASAP.
So guys, is this the first TL ticket ever reported here?
This indeed can happen -- especially with door openers which are located really close to the road. DJ, while testing your V1 I was stopped at a traffic light fairly close to the hospital in my dad's town. A LEO approached the intersection, your V1 of course alerted to his approach and passing, while my 9500ci merrily spun its GPS icon. I followed the LEO for about 2/10 of a mile and then my 9500ci began to alert to his K band CO radar. The hosiptal has several door openers which are located very close to the road. I had manually locked out these door opener locations from a distance so that my 9500ci wouldn't automatically set a really huge lockout radius.
one of the reasons why i got a V1. Like to think for myself.
Its also one of the reasons why I really like my STi (with its latest firmware which makes it quieter around town) and why I really like Bel's GX65. I feel that the driver should intelligently make the decision about what false alert locations to lock out and from what distance to lock them out too. On my 9500ci, I carefully watched what AutoLearn locked out, then I turned off AutoLearn, and then I manually decided how to handle false alert locations which had door openers located right next to the road. Most of them I decided to handle manually, and a few of them I decided to leave unlocked. A good example is the CVS which is on the route to the video store since many times I will run to the video store later in the evening to either rent or return videos before midnight. In other words, on routes where I frequently make "quick trips" later at night, I generally leave false alert locations unlocked and instead run my 9500ci in Auto Sensitivity mode. That is a much safer alternative for my late night routes.
My guess is that, by the time you got to your local CVS that was already lock out, radar source from LEO may be reaching that location since he was using CO. As you left that lockout CVS store, it was receiving the K band source from LEO along your route back that was locking out the signal from the very start you left that lockout CVS store. The frequencies were too close that the ix could not separate the signals. I have tried this one time where I had the radar onboard with me turned on while leaving a lockout location and the the spinning sat icon continues even after a few miles until you turn off radar.
From the very start, I really did not like the auto learn feature whether it be ix or ci. I think is just a marketing thing IMO and a risk on the other hand. However, I don't think this is an auto learn issue. I think it so happened that you were receiving radar signals from that lockout CVS store all the way along your route back. The only time a spinning icon stops is when the radar source stops or out of range from a radar source.
Last edited by KnightHawk; 05-10-2009 at 11:28 PM.
That makes sense.
Sorry to here about that blackbeltrk. AutoLearn does seem to have its own issues that makes me not trust it, but not for the reasons you got a ticket. I hope to get a reply from Escort about my concerns with AutoLearn soon.
The 9500 sires uses 30MHz blocks and the more blocks you lock out the higher the risk. The frequencies (LEO & false) were too close that the ix could not separate the signals from each other. Most likely AutoLearn didn't lock the LEO the 1st time it was the amount and frequency of the falses that encompassed the LEO's radar. Basically the LEO was running the same frequency as the false locked out blocks.
It sounds like you fall into a "High Risk" scenario:
“The Scenarios”
1) In areas where police X band isn't used, lock out X band falses the first time you encounter them. (No Risk )
2) In areas where police K band isn't used, lock out K band falses the first time you encounter them. (No Risk )
3) In areas where police do use K/X band but never sit in that area it would be a Low Risk lock out point. You will most likely lock this point out.
4) In areas where police K/X band is used and they do sit in that area it would be considered a High Risk lock out point (You may not want to lock this point out).
If you decide to lockout a false in a High Risk area to mute the alert you should still drive through the area with caution if you suspect any chance it could have locked out police radar. The same rules would apply if you were using any non GPS capable detector and instead pressed your mute button in false area. Simply treat the spinning satellite icon in your display as a silent alert and proceed with your own discretion and best judgment.
(There is all ways the option of turning off GPS when speeding in a "High Risk" locked out area)
Now who told you that bad peace of information JAZZY.
Very funny snoopyc4.
X2.
Yes this is the first time a TL ticket has ever reported here. Its been discussed in nauseating detail with obvious ways to make it work for some and not for outhers.
Last edited by CJR238; 05-11-2009 at 10:35 AM.
^ I don't think that this is that simple, CJR.
The problem in this particular scenario is that the end-user had no choice - to me, it sounds like the detector chose to pursue its own lock-out, via AutoLearn, despite the fact that it was in a "High Risk" location.
Unfortunately, the detector itself has no way of knowing that it's in a "High Risk" location.
The technology is the problem - it's immature.
But honestly, even without AutoLearn - for example, if the OP had used manual TrueLock in those areas, for the same signals, I think that the fact that there were pre-existing lock-outs in that area would still have exposed him to a large risk, in this instance/circumstance.
Bookmarks