Immediacy of Response

**ghz1** · 04-07-2006, 03:57 PM

I was thinking the V1's Immediacy of Response time is 1.01 sec which for some people is not fast enough. I have been told that when the V1 alert's to a ka threat the second time round eg insant on.. it's lightening fast. From what i understand from this forum it's the Ka guard that is filtering for false Ka alert's so this take's time to scan the signal, it's not because the V1 has a slow computer. So what im thinking is if you turn the Ka guard off how fast is the V1 at alerting to a Ka?. (I would not recommend you to drive around with Ka guard turned off due to the never ending Ka false's.) So has anybody got some time info on the V1 alert with Ka guard turned off?
Also if you read the bell forum they seem to get ALOT more Ka falses on there bells... rx65,Sti my 990 int had alot too but they seem to be a bit faster at alerting to Ka would this mean that bell have Sacrificed the filtering for speed? :shock:

Immediacy of Response
Detector Immediacy of Response Time

Cobra 9700 1.24 seconds

Cobra 9400 1.24 seconds

Bel 895 .77 seconds

Bel RX65 .67 seconds

Bel V995 .60 seconds

Escort 8500 X50 .96 seconds

Valentine 1 1.01 seconds (Ka guard on) :wink:

Whistler 1788 .73 seconds

Whistler 1776 .73 seconds

Whistler 1778 .73 seconds

PNI RW 3000 1.48 seconds

Radio Shack 3000 2.34 seconds

**Rottman** · 04-07-2006, 04:09 PM

IF you turn the KA guard off it will altert you faster alright, to everything under the sun.

**jimbonzzz** · 04-07-2006, 06:54 PM

I don't know that 1.01 seconds is accurate, especially if a stopwatch is used. Here's what Michael B got:

33.8 -112 80% at 67ms, 100% from 100 to 200ms, 20 to 80% from 300ms to 600ms, 100% above 700ms
34.3 -115 0% below 500ms, 50% from 500 to 600ms, 100% above 700ms.
34.7 -115 0% below 300ms, 50% from 300 to 600ms, 100% above 700ms
35.5 -113 0% below 300ms, 50% from 300 to 700ms, 100% above 800ms.

**AirMoore** · 04-07-2006, 07:17 PM

Originally Posted by jimbonzzz

Here's what Michael B got:

33.8 -112 80% at 67ms, 100% from 100 to 200ms, 20 to 80% from 300ms to 600ms, 100% above 700ms
34.3 -115 0% below 500ms, 50% from 500 to 600ms, 100% above 700ms.
34.7 -115 0% below 300ms, 50% from 300 to 600ms, 100% above 700ms
35.5 -113 0% below 300ms, 50% from 300 to 700ms, 100% above 800ms.

I am not disagreeing with you here Jim... but arent those the times/lengths (of signal present) that the RD picked up?

Not how fast it picked up the signal during its sweep, recognized the signal as X/K/Ka, displayed the information to the user.

(Meaning it may sweep (quick enough)to pick up the above [ms bursts] from Michael, but in fact its total processing time of that signal is 1.01seconds.)

That is the way I see the numbers being so drastically different... maybe I am seeing differently though.. what do you think Jim?

**jimbonzzz** · 04-07-2006, 07:44 PM

Originally Posted by AirMoore

Originally Posted by jimbonzzz

Here's what Michael B got:

33.8 -112 80% at 67ms, 100% from 100 to 200ms, 20 to 80% from 300ms to 600ms, 100% above 700ms
34.3 -115 0% below 500ms, 50% from 500 to 600ms, 100% above 700ms.
34.7 -115 0% below 300ms, 50% from 300 to 600ms, 100% above 700ms
35.5 -113 0% below 300ms, 50% from 300 to 700ms, 100% above 800ms.

I am not disagreeing with you here Jim... but arent those the times/lengths (of signal present) that the RD picked up?

Not how fast it picked up the signal during its sweep, recognized the signal as X/K/Ka, displayed the information to the user.

(Meaning it may sweep (quick enough)to pick up the above [ms bursts] from Michael, but in fact its total processing time of that signal is 1.01seconds.)

That is the way I see the numbers being so drastically different... maybe I am seeing differently though.. what do you think Jim?

Yes, those are the lengths of time a signal must be present to trigger an alert, so I do see what you are saying...

But I don't believe it to be the case: why would V1 delay an extra amount of time on purpose, once the radar was present long enough to trigger an alert? I know I can hit my V1 with Ka, and it definitely alerts in less than a second after I hit the transmit button.

Maybe Michael B can clarify if V1 alerted immediately in his tests, once the burst was over the time threshold.

Jim

**AirMoore** · 04-07-2006, 07:54 PM

I actually think I have the awnser (if M.B. confirms it may have a slight delay), I thinks its starring us all in the face guys...

It probably has to do with the arrows... the V1 has Top-of-the-line electronics (and henceforth probably Top-of-the-Line processing speed)

HOWEVER... (talking to a technical electronics [engineer] friend of mine), he said that for the arrows to work, the V1 probably process wether the signal is coming from the front/sides/rear (the only Top 3 detector that needs to do this), and that in-fact to make them(the arrows) more accurate (especially when trying to identify the biggest threat via blinking arrow) the V1 probably has a few sets of simple algorithms it goes through if you will... henceforth chewing up some time... my tech. friend said its very possible this could add: (nothing at all), to essentially 1/8th or so second on response time.

(This would probably change between every model/rev... so each could be different depending on what one was tested.)

THAT folks... could be it... Jim what say you on that (again)?

**Veil Guy** · 04-07-2006, 08:09 PM

I tend to agree with Jim on this one.

I have lived with all of the top contenders and I have always found the V1 to be lightning fast on all alerts and especially laser.

If its detectable, the V1 will report it quickly...

Veil Guy 8)

**AirMoore** · 04-07-2006, 08:16 PM

/\ /\ /\ /\

Yeah maybe as Jim (first said) the times may be off on response...

But also (a side note) to remember on Laser the V1 can drop/bypass any algorithms for the arrows (making it that much faster)... because there shouldnt be much (if) any reflected signal at all to the rear laser antenna... whereas radar it would need the process the stuff thats being reflected from behind (off signs/walls etc etc) so the rear arrow doesnt (incorrectly) show, when normally it would.

BTW: Haven't seen you on here in forever TVGuy!!!

**jimbonzzz** · 04-07-2006, 08:23 PM

I would be very surprised if it took that long to run the code to determine the direction.

Watch shooter2jim's video and tell me what you think:
http://www.radardetector.net/viewtopic.php?t=865

I could do my own video too with the other radar freqs, maybe when I have some time...

Jim

**AirMoore** · 04-07-2006, 08:33 PM

Originally Posted by jimbonzzz

I would be very surprised if it took that long to run the code to determine the direction.

Watch shooter2jim's video and tell me what you think:
http://www.radardetector.net/viewtopic.php?t=865

I could do my own video too with the other radar freqs, maybe when I have some time...

Jim

Jim I am not really (avid on) disagreeing with you, just giving reasons why the numbers may be so odd... I guess they probably just are that far off... (Cant see the Video... darn dial up).

Another point to add... the detectors immediacy of reponse is (probably) a mear fraction of the human and cars total reaction time to get to (a)the designated speed after recieving an alert.