Mildly interesting - K-band

[westwind77]

Given the BSM issues with the latest firmware I went out and put the G2 on 'little L' to see how it would react - wanted to see if the low volume would still catch my attention and to see at what point the unit would go to full volume and consider it a threat)

After playing around and feeling comfortable with the info I gathered I powered on the M360 which sits about 16" inches away. I then triggered a few short burst of K-band for fun and out of no where the G2 came to life, alerting to them - weakly though - 1 or 2 bars, much like it reacted to Ka I/O on the prior firmware. The trigger pulls were right on the edge of where the M360 picks them up, which is pretty quick.

Now....prior to powering on the M360 the G2 was its typical 'lazy' self alerting to K-band, taking its sweet time. However, I'm guessing somehow the interference created by the M360 is also causing the G2 to sniff out the K-band quicker. I powered down both units and fired up the G2 and tested a bit.....slow reacation as usual....then fired up the M360 again and sure enough the G2 caught every shot the M360 did, which with it off there is NO way that would happen. Again, when the G2 does pick it up, it is weak, even though the signal is strong.

Like the title says, I find it mildly interesting. I would never run these two together (or any two), but interesting to see that this is repeatable and that is somehow has an affect on how the G2 alerts to K-band.

 

[VariableWave]

I have heard similar with others detectors doing the same with other Frequencies and situations. If I recall, @Kennyc56 and I did a test with R7 vs V1G2, and the R7 seemed to come to life alittle more when together, but ran independently, it was shorter.

 

[cihkal]

Given the BSM issues with the latest firmware I went out and put the G2 on 'little L' to see how it would react - wanted to see if the low volume would still catch my attention and to see at what point the unit would go to full volume and consider it a threat)

After playing around and feeling comfortable with the info I gathered I powered on the M360 which sits about 16" inches away. I then triggered a few short burst of K-band for fun and out of no where the G2 came to life, alerting to them - weakly though - 1 or 2 bars, much like it reacted to Ka I/O on the prior firmware. The trigger pulls were right on the edge of where the M360 picks them up, which is pretty quick.

Now....prior to powering on the M360 the G2 was its typical 'lazy' self alerting to K-band, taking its sweet time. However, I'm guessing somehow the interference created by the M360 is also causing the G2 to sniff out the K-band quicker. I powered down both units and fired up the G2 and tested a bit.....slow reacation as usual....then fired up the M360 again and sure enough the G2 caught every shot the M360 did, which with it off there is NO way that would happen. Again, when the G2 does pick it up, it is weak, even though the signal is strong.

Like the title says, I find it mildly interesting. I would never run these two together (or any two), but interesting to see that this is repeatable and that is somehow has an affect on how the G2 alerts to K-band.

These type of things further my thoughts that real world conditions are key when people conduct serious I/O or range testing with the more complicated RDs, especially the G2.

I'm glad you tested this and shared your interesting findings!!!

 

[Deadhead1971]

@westwind77 K verifier on? Any filtering on the escort?

 

[westwind77]

@westwind77 K verifier on? Any filtering on the escort?

KV active with the G2

M360 in Highway / TSR Off

 

[WildOne]

I have heard similar with others detectors doing the same with other Frequencies and situations. If I recall, @Kennyc56 and I did a test with R7 vs V1G2, and the R7 seemed to come to life alittle more when together, but ran independently, it was shorter.

Mildly interesting is a good description..... On the surface, it would seem that it could help V1 pass a certain energy received level, but that doesn't make any sense for weak signals that it does well with, just not quickly, without the escort on.

I have also seen in my testing that it responds quicker to IO at lower levels(1 to 2 bars) than higher levels. By higher, I'm talking 4-6 bars, no where near full power, so it isn't a saturation issue.

Maybe the leakage out of the escort keeps the filter occupied and rather than not alarm to the IO, it just passes the signal through without the delay of filtering. Just a wild ass guess...

I'll try putting two or more signals into my bench setup to see if it makes a difference on IO speed.

 

[Brainstorm69]

I have also seen in my testing that it responds quicker to IO at lower levels(1 to 2 bars) than higher levels. By higher, I'm talking 4-6 bars, no where near full power, so it isn't a saturation issue.

How much of a difference have you seen? .1 sec? .2 sec? Any more?

 

[WildOne]

How much of a difference have you seen? .1 sec? .2 sec? Any more?

.25 at best. This makes the total delay somewhere around .5 sec for low level, to .75 to 1 sec for higher level. This is the latest build. I didn't see this variability in 4.1019.

Post automatically merged: Nov 19, 2020

.25 at best. This makes the total delay somewhere around .5 sec for low level, to .75 to 1 sec for higher level. This is the latest build. I didn't see this variability in 4.1019.

X band is a solid 2 sec delay though. No changes with intensity. It wasn't there in 4.1019

 

[samq45]

These 2 detectors certainly interfere, and the parking of the V1 on K and Ka with the RL360c present can cause some delay in alerts for both detectors from stationary ka band signs.

I wont run them together, but its not quite as bad as introducing and R3 or R7 into the mix.

My V1 will alert Ka band to my Rl360c, once it starts it alerts in a repeating pattern.

 

[Brainstorm69]

.25 at best. This makes the total delay somewhere around .5 sec for low level, to .75 to 1 sec for higher level. This is the latest build. I didn't see this variability in 4.1019.

X band is a solid 2 sec delay though. No changes with intensity. It wasn't there in 4.1019

Thanks. It's very interesting to hear this, since it is consistent with some K-band bench testing I did (only available to intermediate and above members) on the original fw (4.1018) where there was about a .2 sec difference between a strong signal (radar in same room) and weaker signal (radar across the house and pointed away from the detector).

Another very interesting thing you said in another thread (https://www.rdforum.org/threads/100802/post-1529234) was that the stability of the signal makes a difference. We have seen (from various testing) that the V1G2 does have a some K-band reactivity variance depending on the radar gun being used. Maybe that is what is causing it.

I haven't tested X-band reactivity on the bench. I'll try some when I get the chance.

 

[LouG]

The next update might be a free Cobra for those facing mobile K.