Alert Lock....Scary testing results for GX-65.

**gpracer1** · 02-10-2009, 12:38 AM

I cut and pasted this from another thread because I think its relevant.

This information is to be used for just that, not bashing a detector.

I just went for a test drive after reading all 20 pages

Highway mode gps on. X off, K and Ka on.
I brought my Kustom Falcon, which according to my GX is shooting 24.145 ..............wait 24.175. No, it changes every few times I shoot. I assume the detector is the one that is not the perfect high dollar "spectrum analyzer".
It even alerted Ka twice 33.7, I think the gun was too close and right behind the RD. After that I had the gun to the side shooting straigh ahead like a dash mount but way off to the side.

I drove by a Pepboys that has a strong false K door opener supposedly at 24.175. I then locked it out and drove away from the area (over 2 miles).

I drove back though the locked out area and the sat symbol was spinning and there was no alert. Perfect.
Then while there I hit it with my gun......NO ALERT. When the sat symbol stopped spinning I waited for 5 seconds and hit it with my gun again I/O.....the sat symbol started to spin again and no alert. This continued for about .5 miles.

So to see the lockout area size, I drove way past, turned around and drove through the area with my gun on C/O even before I got to the area. The sat symbol spun for a total of 1.3 miles with no alert to either the door or the gun while in the area. After leaving the area it starting alerting with the gun still on.

I would have video'd it but I only have 2 hands.
I hope that with some firmware "adjustments" they can fix this or enhance it a bit. After all, we are the RD elite and most informed users (most of us here)

so we are kind of like free beta testers / R&D.

**CJR238** · 02-14-2009, 01:32 PM

Sorry for the late jump in guys, and im not sure all my 9500I testing necessarily correlates to the GX65.

The problem with the TrueLock concept is it has inherent problems not knowing K band from K band, Pretty logical. So Escort put in place certain rules to help prevent a lock out. When we deliberately try to create a lock out the results appear to be catastrophic when in reality it isn't that bad in reality. When something is set up to be 100% its 100%, it would be just as easy to do the opposite but that's not fun.

In order to have a bad lock out in the real world many things have to fall into place.

1- The local LEO's need to use K band (or x).
2- You need to lock out a K false.
3- The LEO needs to sit in that area.
4- The LEO's radar needs to fall into the same 30Mhz block.*
5- The LEO would need to be running a farley weak signal so it falls within the same lock out radius of the false so you are not notified before the lock out.
6- you would need to be speeding, which is usually unlikely where congested traffic and falses are.
7- The LEO needs to be monitoring speed and not eating doughnuts running C/O.

*If the false signal is strong your 30Mhz block may end up 60Mhz or bigger (ghosting). This is also the problem with using a gun as a false.
The lock out radius is in 1/10mi increments, so if the signal is strong you will get 1/2mi lock out. If its a week signal and no additional falses you will get a 1/10mi lock out.

Even though K band from a gun, and K band from a door fall under the same technology they are very different in how they are encountered and there purpose. To test a K gun as a false and as the LEO isn't really accurate to real life, and cannot be equated to a real scenario that will ever be duplicated in reality. Fundamentally its a good example but in reality it would never happen.

I'm not saying a lock out cant happen or that it cant be simulated perfectly to happen every time (GOL did some good ones). The chance of it happening is what Escort relies on, and a list of 7 or even more factors to have a problem is pretty good.

I'm not sure weather i will use Autolock, it adds an additional factor to prevent a LEO lock out but at that same time it adds one. If i manually do it my self i know what to expect. But if its automatically locking out it could lock out an actual LEO & position, however it will also unlock if its not there anymore.

**CJR238** · 02-14-2009, 01:54 PM

Originally Posted by <<JAZZY>>

Does that mean they all fell into the one locked out segment of K band? Each segment is supposed to be about 30 MHz and they are all within 30 MHz of each other. According to the chart, the Decatur Genesis 24.153 was correctly blocked out even though it would have resulted in a ticket. However, the Kustom Signals 24.173 should have alerted if the chart is accurate.

The above blocks are definitely used for the 9500 sires, not sure if its used for the GX65.
You can get ghosting into another 30Mhz block if the signal strength is strong (creating a 60Mhz block). Most false radar is angled down so they are week and don't travel far so a smaller lock out area is created. If a gun is used the signal will almost definitely have a larger lock out radius because of its strength.

**Z1NONLY** · 02-14-2009, 02:38 PM

First, my ix has locked out two LEO's but the LEO and the lockout fq's were right on top of each other. The same ix has alerted to a K-band LEO in a lockout zone. I don't think my ix locks such big chunks of the band like the GX seems to have done here.

Second, and more important, is my solution to the limitations of GPS filtering....

SSO

Strong Signal Overide. This feature needs to be added to Belsorts GPS detectors and be selectable for the end user.

I would set my SSO to overide any and all lockouts when any signal in the lockout band breaks 60% of full strength.

**gpracer1** · 02-14-2009, 02:50 PM

Originally Posted by Z1NONLY

First, my ix has locked out two LEO's but the LEO and the lockout fq's were right on top of each other. The same ix has alerted to a K-band LEO in a lockout zone. I don't think my ix locks such big chunks of the band like the GX seems to have done here.

Second, and more important, is my solution to the limitations of GPS filtering....

SSO

Strong Signal Overide. This feature needs to be added to Belsorts GPS detectors and be selectable for the end user.

I would set my SSO to overide any and all lockouts when any signal in the lockout band breaks 60% of full strength.

Yep, this is what we were talking about a while ago. Almost all falses are 1 bar alerts. Most real LEO encounters are more. They may start out as 1 but usually ramp up quick.