V1G2 - Junk Ka hit ?

westwind77

Advanced User
Lifetime Premium Member
Joined
Dec 7, 2016
Messages
2,669
Reaction score
4,847
Still adjusting to the V1G2. Ha a Ka 34.555 hit today, but the RD quickly displayed what looked to be a 'J' where the bogey counter is and I thought V1driver said 'junk' as well.

The G2 is running 'factory' with nothing special set in the app - curious if the app is calling it junk or the G2 itself? Is it calling it junk because it is out of the typical frequency range of 34.7 or some other reason?
 

IcePick74

Learning to Fly
Beginner User
Lifetime Premium Member
Joined
Oct 20, 2017
Messages
52
Reaction score
55
Page 14 of manual

Valentine One Gen2 is designed to recognize—and ignore—phony POP signals transmitted by poorly-designed detectors. Occasionally an alarm will be initiated before verification is certain. If it’s then determined that 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 briefly in the Bogey Counter.
 

westwind77

Advanced User
Lifetime Premium Member
Joined
Dec 7, 2016
Messages
2,669
Reaction score
4,847
Guess I should have RTFM closer the first time, thanks!
 

LouG

PSL +5
Intermediate User
Joined
Jan 2, 2014
Messages
3,488
Reaction score
4,260
I've only had one 33.xxx J out. While running Gen1 and Gen 2 together, Gen 1 was J'ing out a few times, Gen 2 was silent.
 

jdong

Advanced User
Premium Member
Joined
Jun 5, 2013
Messages
7,123
Reaction score
10,395
Still adjusting to the V1G2. Ha a Ka 34.555 hit today, but the RD quickly displayed what looked to be a 'J' where the bogey counter is and I thought V1driver said 'junk' as well.

The G2 is running 'factory' with nothing special set in the app - curious if the app is calling it junk or the G2 itself? Is it calling it junk because it is out of the typical frequency range of 34.7 or some other reason?
Yeah as others have said, this is a Valentine unique feature.

Their thought process is that for some signals that look like instant-on Ka or Ka POP, they'd rather tell you about it right away. It may take an additional half second or second for the detector to rule out whether or not it's a junk detector, and it would rob you of reaction time if it did turn out to be legit IO Ka.

So, the "J" means "please disregard the last alert you got, we're sure it was junk". That way you don't sit around paranoid about whether or not you got hit with selective IO.

Before, the J-outs were almost exclusively on 33.8 for Ka POP, but now it seems like it can be anywhere on Ka band.
 

westwind77

Advanced User
Lifetime Premium Member
Joined
Dec 7, 2016
Messages
2,669
Reaction score
4,847
It seemed to ID it as 'J' very quickly and the 'graph' on V1driver also stopped being red as well when it was ID'ed as such.

I would rather have it do this than miss a weak/odd I/O shot.
 

jdong

Advanced User
Premium Member
Joined
Jun 5, 2013
Messages
7,123
Reaction score
10,395
It seemed to ID it as 'J' very quickly and the 'graph' on V1driver also stopped being red as well when it was ID'ed as such.

I would rather have it do this than miss a weak/odd I/O shot.
Yep usually it happens quickly. In the past, "J" outs on 33.8 are because Cobra detectors trying to hide from VG-2 RDDs would park on a LO frequency with a 33.8 harmonic once every 2 seconds or so. So in the past, J-outs can be delayed by as much as a second or two.

These days I find that J-outs happen pretty quickly after the alert. I also like this compared to the alternative -- most other detectors are silently suppressing illegitimate Ka alerts that may also be hurting your detection performance silently.
 

Hahns52

Crackheads and Debutantes
Advanced User
Premium Member
Joined
Aug 28, 2012
Messages
2,002
Reaction score
2,495
Age
31
Location
SW WA
I only ever got one J out with my V1G1 (despite getting cobra falses all the time), and that was only about a month ago. I've had a few cobra falses so far with my V1G2, no J outs.
 

westwind77

Advanced User
Lifetime Premium Member
Joined
Dec 7, 2016
Messages
2,669
Reaction score
4,847
so....... :) ..was it a legit hit or a false or do you know?

just asking as I have my custom frequencies set
It was 100% false. My town only runs K-band. There have been a few stray out of town cruisers visiting, but that was not the case today.
 

Deadhead1971

Instant-On Survivor
Advanced User
Joined
Dec 7, 2014
Messages
3,413
Reaction score
5,785
Location
Central NC
It was 100% false. My town only runs K-band. There have been a few stray out of town cruisers visiting, but that was not the case today.
Ok. I will check my Ka custom frequencies to see if this is in or out. Thx
 

samq45

Advanced User
Lifetime Premium Member
Joined
Jul 5, 2011
Messages
1,496
Reaction score
2,137
Location
Saratoga, NY
I have had 2 J outs so far on the G2.

I could see the detectors one was an old Bel (980 or 985), the other was a really flat and thin looking detector. Both of them were right next to me at a stoplight and traffic circle. and the J out dropped the alert quickly, after 1 beep.
 

Brainstorm69

TXCTG - 2016 MOTY
Advanced User
Lifetime Premium Member
Joined
May 23, 2015
Messages
10,298
Reaction score
23,405
Location
Lone Star State
I've had a couple of J-outs with my V1G2. Nothing excessive. Have had some 35.x falses. too.
 

Deadhead1971

Instant-On Survivor
Advanced User
Joined
Dec 7, 2014
Messages
3,413
Reaction score
5,785
Location
Central NC
I haven’t had a J yet. I also run Ka custom frequencies similar to the uniden’s 2, 5, 6, and 8. -primarily to keep out alerts from +/-34.498
 

Discord Server

Latest threads

Latest posts

Forum statistics

Threads
83,441
Messages
1,267,684
Members
21,058
Latest member
norhj
Top