Printable View
As a data point, I didn't receive a single J on a busy 500 mile holiday weekend trip with all default settings (POP on, etc.), the day I got my updated V1 back. It did alert Ka to one possible crapra going opposite direction, but I would have expected more.
Ah, forgot to mention, I had POP off before this encounter.
J' outs are fine, but were they real threats? http://i6.photobucket.com/albums/y22...ht/1shifty.gifQuote:
i used to get 3-5 J' outs per week with pop on...with it off i have gotten maybe 5-6 in the last 16 months
well i was in NJ most of the time so no its all X....but i have J'd out 1x on a real leo the whole time i have had my v1
Quote:
Originally Posted by hockey005
Funny I have only received 4 "J" outs in my many many hours of V1 use, and ironically 3 of my "J" outs were in NJ :lol:. Must be something in the air there because I only drive thru a small portion NJ and spend very little time there and had 75% of my "J" outs there:eek:.
i have pop off tho...and u should turns urs off as well!
mine actually J'd out just like it should, I got a slight 3 dot Ka hit and then a J. I took a look around and driving towards me was a firebird with some kind of detector pointing towards the sky.
yes but i bet it would ot have picked up ne Ka if pop was off....pop off = less j'outs....like A LOT less
No way Jose :) Mr. Valentine spent alot of time and investment in detecting POP. Since I don't know the exact radar units in my area (and since I’m not going to stop an ask:eek:) I'll leave it on, I don't wana end up creating a thread that I received radar ticket and my detector didn't go off:angry:.Quote:
Originally Posted by hockey005
:lol: ok well have ur j'outs but since pop cannot be even used to issue a ticket (even says this in the user manuals the radar units and the valentine 1 manual) then there is no need for it on....esp when its not even used...at all...i/o is the biggest threat if u have jammers and if not that laser and i/o
A: POP is *not supposed* to be used to issue a ticket, which means that you should be able to beat it in court. But, if you don't even know that a LEO used POP incorrectly, it's hard to argue that in court. Thus, for POP detection to be really useful, it needs to alert the RD user to the fact that POP was the last signal used (and this should remain in the display just to be sure). Personally, I think that any signal received for less than about 1 second should be timed, and the duration reported to the RD user. This would include the K and Ka POP and any other frequency signal that might be from a short-triggered radar unit.Quote:
Originally Posted by hockey005
B: Even if POP is used correctly, which means just using it to estimate speed before correctly measuring speed with an I/O blast, that means that a detector with POP off would not detect the POP blasts from traffic ahead unless the LEO decided that that target was worth the full I/O blast, which basically means he's already got a customer. If he doesn't use the I/O and already have a customer, guess who the next POP target will be, and if it looks good so he keeps the trigger pulled for the full I/O, guess who's detector's first alert will basically be to pull over?
The only reason I have POP off is because the greatest threat I face is short-triggering of non-POP guns on other Ka frequencies, and Michael B.'s test results have shown that the V1 actually detects these more reliably with POP off. I don't actually know whether the STi behaves similarly.
Conclusion: Yes, we do need better POP/Short-trigger detection, and preferably a notice that displays at least until the next non-POP (i.e., legally admissible) signal is received on the same frequency.