Results 1 to 8 of 8
  1. #1
    Lead Foot
    Join Date
    Jan 2008
    Posts
    469

    Default Detecting other RDs

    Interesting experience yesterday. I was sitting in a parking lot waiting for my wife to come back from Starbucks. Some guy was parked directly across from me in a minivan with some POS detector on the windshield. I decided to turn on the V1 to see if I could pick him up. I have Ka guard on and POP on.

    A few seconds after turning on the V1, I picked up Ka ahead very strong. The bogey counter fluctuated between 1 and 2 sources. Finally, after about 15 seconds, I got the J alert.

    Turned off the V1 and turned it back on. It took about a minute before sounding Ka alerts this time. Held the signal for about 5 seconds, then junked it.

    Restarted a third time. Detected the signal after what seemed less than 30 seconds. Held for almost 2 minutes, then junked it. Again, bogey counter was fluctuating between 1 and 2 sources.

    Any idea why there seems to be such a gap between signal detection times, and hold times before issuing a "J"?

  2. #2
    Speed Demon
    Join Date
    Oct 2007
    Location
    MA,NH
    Posts
    791

    Default Re: Detecting other RDs

    Quote Originally Posted by justin81 View Post
    Interesting experience yesterday. I was sitting in a parking lot waiting for my wife to come back from Starbucks. Some guy was parked directly across from me in a minivan with some POS detector on the windshield. I decided to turn on the V1 to see if I could pick him up. I have Ka guard on and POP on.

    A few seconds after turning on the V1, I picked up Ka ahead very strong. The bogey counter fluctuated between 1 and 2 sources. Finally, after about 15 seconds, I got the J alert.

    Turned off the V1 and turned it back on. It took about a minute before sounding Ka alerts this time. Held the signal for about 5 seconds, then junked it.

    Restarted a third time. Detected the signal after what seemed less than 30 seconds. Held for almost 2 minutes, then junked it. Again, bogey counter was fluctuating between 1 and 2 sources.

    Any idea why there seems to be such a gap between signal detection times, and hold times before issuing a "J"?
    Maybe because the signal level didn't reduce by driving by it.

    J out is more like "Remember that Alert I gave you back there, well forget about it".

    Bogey counter always seems to bounce between N and N+1.

  3. #3
    Newcomer
    Join Date
    Mar 2008
    Location
    Houston, TX
    Posts
    44

    Default Re: Detecting other RDs

    All the cobra's that have leaked on my 3.872 only show up as 1 bogey and they are junked out fairly quickly. The fact it may have been seeing 1-2 could indicate it was leaking on multiple frequencies and the V1 wasn't sure if they were both Junk or a cop was in the area.

  4. #4
    Old Timer
    Join Date
    Jun 2005
    Location
    New Hampshire
    Posts
    6,806

    Default Re: Detecting other RDs

    Cobras are cheap pieces of junk, no doubt the signal they're emitting isn't a nice clean continuous fixed frequency like a radar gun. This makes Cobra falsing, and junking-out inconsistent for the most part.

    Plus, the V1 is programmed (quite well I might add) to do its best at filtering out Cobra crap. Since you were so close to the offending RD, it might have exceeded the signal strength threshold where the V1 "assumes" it's a Cobra and goes to a real alert, but then it associated harmonic emissions from the Cobra with the signal and junked it out.

    If you turn Ka guard off, or POP on you would get even more consistent alerts from the POS.

    (I tried to post this earlier in the day but then the server got "too busy")... The emissions from cheap Cobras are very POP-like in nature, which is why you get a lot more Cobra falses with POP turned on. I have to wonder if MPH used Cobra emissions as a point of reference when developing POP, to make it harder to detect with anti-Crapra filtering in RDs.

    Just a side note... your thread title says "Detecting other RDs." Does a $30 piece-of-Crapra qualify as an "RD"? It's more of a noisy radar drone that warns you when a cruiser running radar is about to crash head-on in to you.
    Last edited by kpatz; 10-27-2009 at 02:11 PM.
    If I'm passing you on the right, YOU are in the wrong lane!

    If speed kills, how come I'm still alive?

    Active Countermeasures: V1 3.858, Escort Redline, Beltronics STi-R+, LI Dual 7.1x CPU/8.7 Heads (front)
    Other/Backup Countermeasures: V1 3.813 (loaned to friend), Beltronics Pro RX65 M4 6.3
    Vehicle: 2002 Audi A4 1.8T Quattro
    LEO Toys: Kustom Pro Laser II & III
    Encounters/Saves August 2011: Radar 3/1, Laser 0/0


  5. #5
    Professional
    Join Date
    Mar 2008
    Location
    Pensacola, Florida, United States
    Posts
    1,283

    Default Re: Detecting other RDs

    Quote Originally Posted by kpatz View Post
    It's more of a noisy radar drone that warns you when a cruiser running radar is about to crash head-on in to you.
    It's a safety feature.

  6. #6
    Power User
    Join Date
    Apr 2008
    Posts
    4,054

    Default Re: Detecting other RDs

    It's interesting that it took a while for the J-out to come up, normally it takes my V1 about 3-5 seconds before it junks it

  7. #7
    Newcomer
    Join Date
    Mar 2008
    Posts
    17

    Default Re: Detecting other RDs

    does the J really stand for junk? One of my past v1's kept on flashing the J and I thought it was broken..

  8. #8
    Old Timer
    Join Date
    Jun 2005
    Location
    New Hampshire
    Posts
    6,806

    Default Re: Detecting other RDs

    Quote Originally Posted by C4SXM5 View Post
    does the J really stand for junk? One of my past v1's kept on flashing the J and I thought it was broken..
    The V1 owner's manual says (on page 16):

    What the “Dee-Dah-Doo” Tone means
    Valentine One is designed to recognize — and ignore — phony radar signals from poorly-designed detectors. Occasionally a false alarm will be started before verification is certain. If it then determines the source is a junk detector, it will notify you it is retracting that alert with a “Dee-Dah-Doo” sound. A flashing J indicating “junk” will appear in the Bogey Counter.
    So yes, "J" stands for "junk". I guess that's clearer than using "C" for Crap. I suppose they could have flashed "P...o...S" for.. well, you know, but then that would be confused for POP.
    If I'm passing you on the right, YOU are in the wrong lane!

    If speed kills, how come I'm still alive?

    Active Countermeasures: V1 3.858, Escort Redline, Beltronics STi-R+, LI Dual 7.1x CPU/8.7 Heads (front)
    Other/Backup Countermeasures: V1 3.813 (loaned to friend), Beltronics Pro RX65 M4 6.3
    Vehicle: 2002 Audi A4 1.8T Quattro
    LEO Toys: Kustom Pro Laser II & III
    Encounters/Saves August 2011: Radar 3/1, Laser 0/0


 

 

Similar Threads

  1. V1 detecting it's self
    By ghz1 in forum Valentine One
    Replies: 27
    Last Post: 10-08-2011, 07:32 PM
  2. Sti detecting the V-1 as Ka
    By Eloi in forum Radar Detectors - General
    Replies: 7
    Last Post: 11-16-2010, 03:01 PM
  3. Always Detecting X Band
    By three_sixteen in forum Radar Detectors - General
    Replies: 4
    Last Post: 06-01-2007, 04:24 PM
  4. V1 not detecting?
    By cloud_171 in forum Valentine One
    Replies: 21
    Last Post: 06-01-2007, 12:06 AM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •