Stalker rear traffic alert leak ?

[siRman20]

there running the stalker duals lil black att. driver rear low corner i pass them all the time on the dallas toll way and george bush pike i get same reading w my 9500i and ix, it goes off real close or nothing..... they got it off most time looking in side mirror and instant on your a** parked on shoulder. at night there sneaky bastards in dark i get a single brap soon enough there ahead waiting then its full blast ka your toast

[Z1NONLY]

No. The LEO was targeting either me directly or the car that passes me, probably both of us actually, at about 0:43 of the video. The gun was definitely pointed in my direction. If you'll notice, there's just us 2 cars on the road at that point. There's no one else the target could have been.

First alert= :07,

Then at :22, you can see a car coming toward you at the intersection. (looks like he's about even with the LEO at that point)

Next alert comes at :31, but the light is still red and you are not moving.

However there is another car coming toward you that comes into view at :39

His position looks like he could shoot both ways if he wanted to and, if your lane was being targeted the whole time, the second I/O burst seems silly since you were parked.

There is also a large crown vic between him and the intersection you were parked at. (taxi sign on top too?)

It doesn't look like he can get line of sight untill after you are through the intersection. Not abnormal usage with a dash mount, but to sit there and hold the gun in your hand and wait for car(s) to come into view???

IDK....

[languy99]

Maybe they are using the same radar antenna as the new handheld Stalker II is using. If they are, even my V1 is having serious problems detecting these bad boys. I'd expect that your less sensitive Pro78 would struggle mightily to detect them. My V1 missed an I/O shot from this gun at less than 4 blocks away. This new low powered antenna is changing the game, I promise you.

YouTube - Stalker Instant On, 9500ci alerts to 1st shot, V1 misses it

All I have to say is your are running pop off on the v1 so I am not surprised that it missed that short I/O encounter.

[djrams80]

All I have to say is your are running pop off on the v1 so I am not surprised that it missed that short I/O encounter.

Why would turning pop on increase detection range for 34.7Ka band? I would argue that it wouldn't. In fact, I would argue that turning pop on would theoretically decrease 34.7Ka band detection range. Logically, if my V1 was busy scanning pop frequency ranges(K band and 33.8Ka band), it would then be spending less time scanning 34.7Ka band, the frequency that the Stalker II uses. Also, since X and K band are turned off on my V1 and since my V1 only has to scan Ka band, this should theoretically increase my V1's Ka band sensitivity.

When GOL tested the V1 with different settings, they showed no appreciable detection range increase with pop on, or pop off for that matter. The average detection range with pop on was 925.5ft, with pop off was 908.5ft.

I personally think the theory of V1 having an appreciable increase in range with pop on is bogus.

Guys of LIDAR - Radar Detector Test - August 2007

[jdong]

(1) Modern detectors based off advanced platforms like the V1 or Escort's M4 do NOT "spend a lot of time" looking for POP. In fact, I'd be willing to bet they see POP whether being asked to scan for it or not, but instead when POP is OFF they suppress the alert in software.


(2) The theory that POP increases detection range is based off the speculation that at a far distance, even a CO signal may fade in and out. With POP off the detector rejects all signals below about 500ms on K-band or 700ms on some of Ka-band, while with POP ON the V1 is more likely to accept a short-blip signal while in POP OFF it's more likely to filter it out. This can cause you to miss a glimpse of an IO burst entirely at a long distance, or a couple hundred (at worst) feet of CO before your detector sees a steady, stable signal.

(3) GOL tests extremely slow speed runs which are probably not able to examine this phenomenon. Mike B's lab tests show a significant difference in whether or not a detector accepts short-duration IO bursts (i.e. from 100-800ms) across the board for common detectors when POP is on vs off. With the exception of the STI, detectors tend to reject short IO bursts in this range when POP is off compared to on.

[languy99]

(1) Modern detectors based off advanced platforms like the V1 or Escort's M4 do NOT "spend a lot of time" looking for POP. In fact, I'd be willing to bet they see POP whether being asked to scan for it or not, but instead when POP is OFF they suppress the alert in software.


(2) The theory that POP increases detection range is based off the speculation that at a far distance, even a CO signal may fade in and out. With POP off the detector rejects all signals below about 500ms on K-band or 700ms on some of Ka-band, while with POP ON the V1 is more likely to accept a short-blip signal while in POP OFF it's more likely to filter it out. This can cause you to miss a glimpse of an IO burst entirely at a long distance, or a couple hundred (at worst) feet of CO before your detector sees a steady, stable signal.

(3) GOL tests extremely slow speed runs which are probably not able to examine this phenomenon. Mike B's lab tests show a significant difference in whether or not a detector accepts short-duration IO bursts (i.e. from 100-800ms) across the board for common detectors when POP is on vs off. With the exception of the STI, detectors tend to reject short IO bursts in this range when POP is off compared to on.

Thanks man, I am just tired of telling people the same thing over and over. This has been discussed many times and to this day I run with pop on and have yet to miss an I/O signal.

[djrams80]

My 9500ci detected the I/O shot with pop off. Why wasn't my 9500ci affected by having pop turned off? Shouldnt this pop theory work for both RDs? My 9500ci alerted for a full 10 seconds for the I/O shot that the V1 missed. I think its quite clear from the video that the signal that the V1 missed was not of a short duration, but rather a weak signal that the V1 was not sensitive enough to detect. Languy99, trying to compare your normal Ka band I/O detections to that of the extremely low powered Stalker II is apples to oranges. There will be tons of missed I/O shots against this gun, I guarantee it.

There is no reason that the V1 should miss a detectable I/O Ka band shot with both X and K bands turned off. This fact should have more to do with Ka band detection sensitivity than any other setting. At that point, it has no other job. The V1 is just not as sensitive as the 9500ci and that's a fact. There is no evidence whatsoever to back up this pop on/off theory. I wasn't hit with pop, I was hit with I/O Stalker 34.7Ka band. I don't think my V1's pop setting has any affect whatsoever and it shouldn't. Trying to make excuses for the V1 by blaming my settings is weak.

[GTO_04]

Maybe they are using the same radar antenna as the new handheld Stalker II is using. If they are, even my V1 is having serious problems detecting these bad boys. I'd expect that your less sensitive Pro78 would struggle mightily to detect them. My V1 missed an I/O shot from this gun at less than 4 blocks away. This new low powered antenna is changing the game, I promise you.

YouTube - Stalker Instant On, 9500ci alerts to 1st shot, V1 misses it

At first I thought maybe the V1 was malfunctioning or maybe dead on Ka, but the V1 alerted first on the 2nd I/O shot. Kind of odd given that it totally missed the first alert. I wouldn't think that the ci would interfere with the V1 given it's almost zero leakage.

Hopefully there will be a Stalker II at the upcoming GOL test. And a 3.872 V1.



GTO_04

[jdong]

My 9500ci detected the I/O shot with pop off. Why wasn't my 9500ci affected by having pop turned off? Shouldnt this pop theory work for both RDs? My 9500ci alerted for a full 10 seconds for the I/O shot that the V1 missed. I think its quite clear from the video that the signal that the V1 missed was not of a short duration, but rather a weak signal that the V1 was not sensitive enough to detect. Languy99, trying to compare your normal Ka band I/O detections to that of the extremely low powered Stalker II is apples to oranges. There will be tons of missed I/O shots against this gun, I guarantee it.

There is no reason that the V1 should miss a detectable I/O Ka band shot with both X and K bands turned off. This fact should have more to do with Ka band detection sensitivity than any other setting. At that point, it has no other job. The V1 is just not as sensitive as the 9500ci and that's a fact. There is no evidence whatsoever to back up this pop on/off theory. I wasn't hit with pop, I was hit with I/O Stalker 34.7Ka band. I don't think my V1's pop setting has any affect whatsoever and it shouldn't. Trying to make excuses for the V1 by blaming my settings is weak.

There is no need to be close-minded and antagonistic about this. Of course the V1 is less sensitive than the 9500ci, nobody is trying to argue against that. But the idea of pulse-guarding duration affecting detection range is not a far-fetched theory but in fact a well-accepted phenomenon that explains, for example, how Whistler units with undoubtedly lower in-lab sensitivity can have real-world detection ranges similar to way more sensitive detectors (Whistler uses some of the lowest filter durations in the industry)

According to Mike B's test of the V1: http://www.radardetector.net/forums/323323-post3.html

POP ON:
K band responds to > 100ms
POP OFF:
K-band responds to > 200ms

POP ON:
33.8 responds 100% 67-300ms; 20-80% 300-700ms, 100% >700ms

POP OFF:
33.8 responds 100% >600ms

POP ON:

34.7 responds 0% <300ms, 50% 300-700ms, 100% above 700ms

POP OFF:

34.7 responds 100% > 400ms

POP ON:
35.5 responds 0% <300ms, 50% 300-800ms, 100% above 800ms.

POP OFF
100% above 400ms



So, for the V1, on 33.8 you get better pulse coverage with POP ON, on 35.5 and 34.7 it's more or less the same. So, in this case, you are correct, the POP setting would probably have not affected your ability to detect a short IO pulse on 34.7



However, the V1 is also an extremely conservative unit for pulse guarding; not as much as the Whistlers but more than its Belscort competitors. With many of the Bel/Escort units they consistently will not respond to ANYTHING less than 800ms with POP OFF, according to Mike B's tests.

[djrams80]

There is no need to be close-minded and antagonistic about this. Of course the V1 is less sensitive than the 9500ci, nobody is trying to argue against that.

Languy99's point seems to be that the reason why my V1 missed this I/O shot is because I had pop off on my V1. I disagree. I think it's the V1's relative lack of sensitivity.

But the idea of pulse-guarding duration affecting detection range is not a far-fetched theory but in fact a well-accepted phenomenon that explains, for example, how Whistler units with undoubtedly lower in-lab sensitivity can have real-world detection ranges similar to way more sensitive detectors (Whistler uses some of the lowest filter durations in the industry)

According to Mike B's test of the V1: http://www.radardetector.net/forums/323323-post3.html

POP ON:
K band responds to > 100ms
POP OFF:
K-band responds to > 200ms

POP ON:
33.8 responds 100% 67-300ms; 20-80% 300-700ms, 100% >700ms

POP OFF:
33.8 responds 100% >600ms

POP ON:

34.7 responds 0% <300ms, 50% 300-700ms, 100% above 700ms

POP OFF:

34.7 responds 100% > 400ms

POP ON:
35.5 responds 0% <300ms, 50% 300-800ms, 100% above 800ms.

POP OFF
100% above 400ms



So, for the V1, on 33.8 you get better pulse coverage with POP ON, on 35.5 and 34.7 it's more or less the same. So, in this case, you are correct, the POP setting would probably have not affected your ability to detect a short IO pulse on 34.7



However, the V1 is also an extremely conservative unit for pulse guarding; not as much as the Whistlers but more than its Belscort competitors. With many of the Bel/Escort units they consistently will not respond to ANYTHING less than 800ms with POP OFF, according to Mike B's tests.

This data basically backs my point, that pop on has nothing to do with 34.7Ka band detection. Any affect that pop setting on would have would be with the pop frequencies, which are 33.8Ka band and K band.