V1 w/V1C Custom sweep programming (Android).

ahl395

PSL?
Advanced User
Premium Member
Joined
Jun 20, 2013
Messages
1,502
Reaction score
887
Location
New Jersey, USA
IMO it would make sense that it would scan for 34.7 then 35.5 then 34.7 and so on in an "interleaved" sweep. This way it would be more likely to catch either one of the signals since it would be scanning for each one every few milliseconds.

In a standard "sequential" sweep set that say scans for 34.7 three times then 35.5 three times, in those few ms that its consecutively scanning for one frequency only, it's more likely to miss the other frequency that's still another two sweeps away.

But then with throwing calibration and whatnot into the mix, my way of thinking may be wrong.
 

Windstrings

Premium RDF Member
Advanced User
Premium Member
Joined
Jun 18, 2013
Messages
8,401
Reaction score
4,050
Location
Central Texas
IMO it would make sense that it would scan for 34.7 then 35.5 then 34.7 and so on in an "interleaved" sweep. This way it would be more likely to catch either one of the signals since it would be scanning for each one every few milliseconds.

In a standard "sequential" sweep set that say scans for 34.7 three times then 35.5 three times, in those few ms that its consecutively scanning for one frequency only, it's more likely to miss the other frequency that's still another two sweeps away.

But then with throwing calibration and whatnot into the mix, my way of thinking may be wrong.
Well if there is calibration happening after a sweep, interleaving should help since the V1 can work immediately on the next band /sweep while calibrating the last ran sweep.

Again, only noticeable at great distances or situations where increased reactivity makes a difference.

Like a guard looking at a foxhole to the right, then left, then right, then left (interleaving) vs looking right, looking right again, looking right again, then looking left, left, left, then back to right and so on. (consecutive or redundant)
 

ahl395

PSL?
Advanced User
Premium Member
Joined
Jun 20, 2013
Messages
1,502
Reaction score
887
Location
New Jersey, USA
I guess we may never really know for sure. The only way to be 100% would be to probably ask Mike Valentine himself.
 
Last edited:

CJR238

Retired PR
Advanced User
Lifetime Premium Member
Joined
Oct 30, 2010
Messages
27,274
Reaction score
15,235
Location
CT- 4Runner - ALP - V1/RedLine/Waze
I guess we may never really know for sure. The only way to be 100% would be to probably ask Mike Valentine himself.
Yup, i wish they would at least give us a Q & A section/thread where we could ask questions. Even if it was there choice to answer or not with no flaming or need for additional interaction.

---------- Post added at 10:58 AM ---------- Previous post was at 10:52 AM ----------

Well if there is calibration happening after a sweep, interleaving should help since the V1 can work immediately on the next band /sweep while calibrating the last ran sweep.

Again, only noticeable at great distances or situations where increased reactivity makes a difference.

Like a guard looking at a foxhole to the right, then left, then right, then left (interleaving) vs looking right, looking right again, looking right again, then looking left, left, left, then back to right and so on. (consecutive or redundant)
Even if there is calibration happening after a sweep, i doubt interleaving does much of anything. At best you would be getting a fraction of a millisecond of speed with an interleaved sweep.
 

Windstrings

Premium RDF Member
Advanced User
Premium Member
Joined
Jun 18, 2013
Messages
8,401
Reaction score
4,050
Location
Central Texas
Yep, it's easy to strain at a knat and swallow a camel!
 

valentine

Learning to Drive
General User
Joined
Jul 5, 2015
Messages
1
Reaction score
0
Re: V1 w/V1C Custom sweep programing.

I think sometimes people are making their sweep to tight and missing some alerts trying to make their radar detector faster. I live in the Atlanta GA area. I received the alert in Duluth, GA. 34.851 between 2 and 3 miles from the Leo.
 

Attachments

Windstrings

Premium RDF Member
Advanced User
Premium Member
Joined
Jun 18, 2013
Messages
8,401
Reaction score
4,050
Location
Central Texas
Entirely possible, once your in the ballpark, not a lot more measurable performance is gained, but you can rid false alerts...
But that should never be at the expense of real alerts with the exception of once in a year rare out of band flukes.
 

NVR2FST

Lifetime RDF Contributor
Advanced User
Lifetime Premium Member
Joined
Aug 1, 2011
Messages
1,244
Reaction score
812
Location
Somewhere in cyberspace.
Which would help explain why my own personal sweep for that segment is 34.774 - 34.892. I know some here go even higher.

Free men are not equal. Equal men are not free.
 

CJR238

Retired PR
Advanced User
Lifetime Premium Member
Joined
Oct 30, 2010
Messages
27,274
Reaction score
15,235
Location
CT- 4Runner - ALP - V1/RedLine/Waze
I have been using YaV1 for so long now. I anyone using VR's V1C app anymore?

I may give it a try again to see whats changed.

Anyone have any other creatve ideas for mounting the dongle besides mine:

IMG_20130607_100637_963_zps98e0a0e8.jpg
 

Windstrings

Premium RDF Member
Advanced User
Premium Member
Joined
Jun 18, 2013
Messages
8,401
Reaction score
4,050
Location
Central Texas
That's slick! I saw one mounted same way but stuck on the V1 instead.
 

CJR238

Retired PR
Advanced User
Lifetime Premium Member
Joined
Oct 30, 2010
Messages
27,274
Reaction score
15,235
Location
CT- 4Runner - ALP - V1/RedLine/Waze

Windstrings

Premium RDF Member
Advanced User
Premium Member
Joined
Jun 18, 2013
Messages
8,401
Reaction score
4,050
Location
Central Texas
It's on this forum somewhere. Tapatalks search options are limited
 

Tallyho

Premium RDF Member
Advanced User
Premium Member
Joined
Mar 21, 2013
Messages
2,953
Reaction score
5,266
I have been using YaV1 for so long now. I anyone using VR's V1C app anymore?
Yes, although mainly for testing purposes. I wanted to see if sweeps pushed from YaV1 or those pushed from V1 Connection were somehow impacting detection results. I haven't seen any difference.

I will also occasionally run both apps because I can't find some features like the heightened Ka ramp up on one and can find it on the other. Other than that I do like the V1 Connection for it's simplicity and YaV1 for its customization.
 

Windstrings

Premium RDF Member
Advanced User
Premium Member
Joined
Jun 18, 2013
Messages
8,401
Reaction score
4,050
Location
Central Texas
Yes, although mainly for testing purposes. I wanted to see if sweeps pushed from YaV1 or those pushed from V1 Connection were somehow impacting detection results. I haven't seen any difference.

I will also occasionally run both apps because I can't find some features like the heightened Ka ramp up on one and can find it on the other. Other than that I do like the V1 Connection for it's simplicity and YaV1 for its customization.
I thought Ka ramp was on both I don't think YaV1 did anything to change that
uploadfromtaptalk1446237449330.png
 
Last edited:

SpeedyValentine1

Learning to Fly
Beginner User
Joined
Sep 24, 2014
Messages
98
Reaction score
13
what is the safest boundaries left to right for Ka band 33.8 frequency, for a custom sweep enabling in-box option. Sorry if this has been posted before or in a wrong thread
 

Windstrings

Premium RDF Member
Advanced User
Premium Member
Joined
Jun 18, 2013
Messages
8,401
Reaction score
4,050
Location
Central Texas
what is the safest boundaries left to right for Ka band 33.8 frequency, for a custom sweep enabling in-box option. Sorry if this has been posted before or in a wrong thread
Basic rule of thumb is to scan 100.mhz above and below where leo normally goes to allow for out of tune guns.

* USA Ka-Band Frequencies +/- 100 MHz =
33.8 Ka.... (33.7 - 33.9) Ghz

With the V1 you cannot remove 33.8 scanning, it's fixed and built in.
But you can use YaV1 to use on the box muting and color code the part leo uses and a different color for the other.

Mine is set up this way.
This is box 2 where leo lives uploadfromtaptalk1447212595527.png

Here is above and below (box 1 & 3)
 
Last edited:

SpeedyValentine1

Learning to Fly
Beginner User
Joined
Sep 24, 2014
Messages
98
Reaction score
13
Thanks windstrings, so im using the VR app currently at the moment. So it looks like the 33.8 frequency you have runs at 33.400-33.920. Is this correct or is that to much of a band sweep? I know enabling the euro mode makes the 33.8 automatic. I just wanted a good boundary to set to keep it a legit ka with a little drift of possible out of tune
 
Last edited:

Windstrings

Premium RDF Member
Advanced User
Premium Member
Joined
Jun 18, 2013
Messages
8,401
Reaction score
4,050
Location
Central Texas
Thanks windstrings, so im using the VR app currently at the moment. So it looks like the 33.8 frequency you have runs at 33.400-33.920. Is this correct or is that to much of a band sweep? I know enabling the euro mode makes the 33.8 automatic. I just wanted a good boundary to set to keep it a legit ka with a little drift of possible out of tune
A little confusion.

Remember I said you can't remove scanning in 33.8 (only can in the rest of Ka "34.7, & 35.5)

Sweeping by definition defines what the detection is literally scanning for.. If a freq area is swept away, the detector doesn't even look for it.

Concerning 33.8 it's force swept...

With the stock app you can mute it with box muting. With YaV1 you can also assign colors & /or voice to those boxes.

By creating 3 boxes I can assign different colors so at a glance I know when I'm seeing leos area, vs above or below.... But it's ALL muted.. All 3 boxes!




I'm basically muting all that the V1 scans in 33.8 starting at 33.4 on the low (shown in box 1) thru the high end of box 3 "34.563".

The reason I stop there is because that's where my sweeps start (no reason to mute what your not sweeping)


Basically since I can't sweep anything, I'll mute it all instead (you may not choose to do so)

I rarely get legit 33.8 so why listen to its falses all the time?
 
Last edited:

SpeedyValentine1

Learning to Fly
Beginner User
Joined
Sep 24, 2014
Messages
98
Reaction score
13
thanks windstring, It looks like i found the thread forced range from 11-02-2015 posted as pop bottom an pop top 33.8 running at 33.675-33.925.
 

Windstrings

Premium RDF Member
Advanced User
Premium Member
Joined
Jun 18, 2013
Messages
8,401
Reaction score
4,050
Location
Central Texas
thanks windstring, It looks like i found the thread forced range from 11-02-2015 posted as pop bottom an pop top 33.8 running at 33.675-33.925.
Not to confuse more but the "pop" portion is the part that gets swept 5 times (33.675 - 33.925) and that too is forced as well as the part that is not pop (33.350 - 33.675) in 33.8 that is also forced and only gets its normal one sweep. uploadfromtaptalk1447227715400.png

If I got any of that wrong, someone pls correct me!
 
Last edited:

Discord Server

Latest threads

Forum statistics

Threads
77,578
Messages
1,182,271
Members
19,839
Latest member
Fitipaldi1
Top