johnboy00, Can we Creat Custom Sweeps for K Band?

mralsiyabi

Learning to Drive
General User
Joined
Jun 1, 2019
Messages
25
Reaction score
28
Hello @johnboy00 and everyone..

I'm totally new with V1 and JBV1, therefore you guys should expect any stupid question like this.

Most of the radar source in our country operates in Laser and K band, and very limited and few of Ka band. My understanding that we can create a custom sweeps for Ka band in order to get better performance and longer detection range. But, because Ka band radar is very limited and rare over here this feature doesn't really help me out.

And, because K band radar is widely use over here, can we creat a mechanism to specify a range of K band frequencies that V1 will scan and detect?

For example, in my country the K band frequency uses for speed radar is 24.200, so i want V1 to scan and detect this range 24.100 - 24.300 only, and ignore the rest of frequencies.

Is that make sense guys?!
 
Last edited:

BlueV1

"(Don't) Give Hate a Chance" -Jamiroquai
Advanced User
Lifetime Premium Member
Joined
Feb 8, 2016
Messages
3,377
Reaction score
6,315
Location
Western NC
The existing K-band runs 24.050 to 24.250 so you are getting the same 200 MHz spread but 50 MHz lower than what you are requesting.
The only frequencies that you don't want are below 24.100. You can use a frequency box to mute those frequencies below 24.100. :)

Question for clarification: Do you receive frequencies above 24.250?
 

Mushin

Two More Weeks! ಠ_ಠ
Advanced User
Lifetime Premium Member
Joined
Jan 2, 2012
Messages
1,215
Reaction score
3,039
F’ers ^^^ both beat me. My 3 words a minute typing on my phone just can’t compete. Lol.
 

BlueV1

"(Don't) Give Hate a Chance" -Jamiroquai
Advanced User
Lifetime Premium Member
Joined
Feb 8, 2016
Messages
3,377
Reaction score
6,315
Location
Western NC
Here's an example of setting up a box filter. I'm using Box 5 for this demo because it's blank. (Example video deleted)

Note that according to the original design of boxes by Valentine, signals in-the-box are supposed to be valid. If that's what you want, create a box for 24.100-24.250 and then choose the mute out of the box option instead. Note that this way, you can use up to 6 box divided sections to further customize your reception needs.
 
Last edited:

mralsiyabi

Learning to Drive
General User
Joined
Jun 1, 2019
Messages
25
Reaction score
28
The existing K-band runs 24.050 to 24.250 so you are getting the same 200 MHz spread but 50 MHz lower than what you are requesting.
The only frequencies that you don't want are below 24.100. You can use a frequency box to mute those frequencies below 24.100. :)

Question for clarification: Do you receive frequencies above 24.250?
Thank you for your answer, the frequency that i mentioned in my post just for example to express the meaning of my question and not the one that is uses in reality.

And, answering your question: No, i don't receive above this amount for sure. And as i said earlier the frequencies range that i did gice you just to explain the idea, and here is another example:

The K Band radar frequency is 24.222, and I want v1 scans and detects this range 24.212 - 24.232 only and ignore all other frequencies in order to get better performance and longer detection.
 

BlueV1

"(Don't) Give Hate a Chance" -Jamiroquai
Advanced User
Lifetime Premium Member
Joined
Feb 8, 2016
Messages
3,377
Reaction score
6,315
Location
Western NC
. (Sorry, video issues)
 
Last edited:

mralsiyabi

Learning to Drive
General User
Joined
Jun 1, 2019
Messages
25
Reaction score
28
Can't do custom sweeps for K band. You'll have to use box muting to limit K band alerts by frequency.
Just assume that I'm very beginner in this and explain more for our knowledge and study, why we can't do custom sweeps for K band?! Is it a scientific or technical issues, or something else?
-- Double Post Merged: --
Here's an example of setting up a box filter. I'm using Box 5 for this demo because it's blank. (Example video deleted)

Note that according to the original design of boxes by Valentine, signals in-the-box are supposed to be valid. If that's what you want, create a box for 24.100-24.250 and then choose the mute out of the box option instead. Note that this way, you can use up to 6 box divided sections to further customize your reception needs.
This is good option and i knew it, but your explanation helped me a lot to configure. But, this will not help increasing the detection range or give better performance. Isn't it?
 
Last edited:

Mushin

Two More Weeks! ಠ_ಠ
Advanced User
Lifetime Premium Member
Joined
Jan 2, 2012
Messages
1,215
Reaction score
3,039
The V1 detector doesn’t support K band sweeps. It doesn’t take much time to sweep the entire 200 MHz range. It’s much easier to filter after the fact. That’s why it is implemented as a in and out of box filtering.

Thanks @BlueV1 and @johnboy00 for letting me answer this. Lol.
 
Last edited:

BlueV1

"(Don't) Give Hate a Chance" -Jamiroquai
Advanced User
Lifetime Premium Member
Joined
Feb 8, 2016
Messages
3,377
Reaction score
6,315
Location
Western NC
Not to jump ahead of JohnBoy00 again, (I do want to hear his opinion from a developer standpoint);

Ka segmenting is intended to break up 2,600 MHz of the spectrum into 10 pieces (Or any custom subset as Valentine allows!) and each one is roughly 260 MHz.
All of K-band is typically 200 MHz. Segmenting of K-band into only 10 segments would provide 20 MHz segments. A smaller amount of segments would provide more usable segments possibly. Maybe 4 segments, etc.

But, the main thing that precludes any detector from having K-band segments is that it's not built in to the firmware of the detector. JBV1 doesn't create the ability to segment a V1, it utilizes a feature that the V1 already has for Ka. There's no mechanism to limit the V1 to a specific K-band range. (Boxes do nearly the same thing in a safer way.) :)

[Edited to add]
@imaitguy has a chart that shows the amount of scan time in the Ka band and even there with 2,600 MHz to scan, the differences are minimal. I doubt that any mechanism to reduce the amount of K-band that would be scanned is worth bothering with for the sake of speed. @InsipidMonkey might also have some good information in this vein.

Noting that you have specific detection needs that we don't in the US., maybe I'm not thinking of this correctly and someone else might chime in with a better idea. :)
 
Last edited:

Brainstorm69

TXCTG 2016 MOTY
Advanced User
Premium Member
Joined
May 23, 2015
Messages
9,160
Reaction score
19,369
Location
Lone Star State
The K Band radar frequency is 24.222, and I want v1 scans and detects this range 24.212 - 24.232 only and ignore all other frequencies in order to get better performance and longer detection.
The entire K-band spectrum is so small (relatively speaking) that segmenting it, even if it were possible, is not likely to do much at all to increase performance (i.e., segmenting K-band and turning off segments is not likely to get you any increased detection distances on the segments left on).
 
Last edited:

johnboy00

Geaux Tigers!
Advanced User
Lifetime Premium Member
Joined
Sep 6, 2016
Messages
3,850
Reaction score
7,266
Location
Raleigh, NC
I don't have anything to add that hasn't already been said.
 

Deacon

TXCTG
Advanced User
Premium Member
Joined
Nov 13, 2016
Messages
10,052
Reaction score
12,255
Location
Hill Country, TX
It’s much easier to filter after the fact.
Well, no. It’s just that VR doesn’t provide a mechanism (at least through the API) to set K-band limits or sweeps. It would be awesome if they did. Neither JB nor anyone else can add something to modify the behavior of the detector itself that’s unsupported by the detector. Thankfully we can apply an after-the-fact mute box to at least shut it up since we can’t keep it from alerting at all in the first place.
 

Mushin

Two More Weeks! ಠ_ಠ
Advanced User
Lifetime Premium Member
Joined
Jan 2, 2012
Messages
1,215
Reaction score
3,039
.

Reminds me of an old joke. Fun. Period. Fun. Period. Fun. No Period, Worry, Worry, Worry!
 
Last edited:

Discord Server

Latest threads

Forum statistics

Threads
77,524
Messages
1,181,299
Members
19,831
Latest member
imran161
Top