Valentine One Custom Sweeps - Tabular Listing (Redone) (1 Viewer)

djg21

Learning to Fly
Beginner User
Joined
Apr 25, 2012
Messages
87
Reaction score
31
Awards
0
3.8952 is the latest version. However, I remember reading post on here where some were unable to push a single sweep even with that version. I believe I recall someone mentioning it was maybe because of a different version of the ESP library from V1. Maybe someone a little more up to speed on this will chime in. Also, if you are using an Android phone, try pushing your sweep through using the JBV1 app.
Using iPhone X. I’ll check my firmware version in the morning. It’s too bad Valentine can’t allow firmware updates via BT, so V1s could be more easily kept up to date.


Sent from my iPhone using Tapatalk
 

BlueV1

You won't be saved by alerts you don't get.
Advanced User
Lifetime Premium Member
Joined
Feb 8, 2016
Messages
3,062
Reaction score
5,623
Awards
0
Location
Western NC
Even though my V1 is 2.5 years old and is v3.8945 (and I have to split at 34.770 to 34.774) my V1 does not show as being upgradable either. :)
 

BaileyAB

Whats PSL? Autobahn bro, A.U.T.O.B.A.H.N.!!!!!
Advanced User
Premium Member
Joined
May 31, 2014
Messages
1,613
Reaction score
3,029
Awards
0
Location
Alberta, Canada
Best user friendly detector out there. Love it with JBV1.
 

djg21

Learning to Fly
Beginner User
Joined
Apr 25, 2012
Messages
87
Reaction score
31
Awards
0
Even though my V1 is 2.5 years old and is v3.8945 (and I have to split at 34.770 to 34.774) my V1 does not show as being upgradable either. :)
Mine is v3.8945 as well. So I guess I need to split up the sweeps until the next time I upgrade.


Sent from my iPad using Tapatalk Pro
 

CJR238

-CMS Article Admin-
Administrator
Advanced User
Lifetime Premium Member
The Pen Is My Sword
Joined
Oct 30, 2010
Messages
27,239
Reaction score
17,339
Awards
0
Location
CT- 4Runner - ALP - V1/RedLine/Waze
Made sticky, unstuck the old one.

Thank you for all your time on this!
 

hiddencam

Premium RDF Member
Advanced User
Premium Member
Joined
Oct 29, 2010
Messages
11,468
Reaction score
24,694
Awards
0
Nice work redoing the tabular listing of the previously shared work.

For those less advanced users new to all this, the increased efficiency referred to in the original post (by scanning less bandwidth) without doubt increase a V1's reactivity to Ka band, which in turn adds a little bit of extra range.

How much obviously depends on terrain, obstacles, and all the other variables that come into play in the real world. My own testing, and that of other testing groups and individuals, has shown that to be very true.

And sometimes every yard matters, particularly when you're up against a foe who employs advanced levels of IO and patient selectivity of targets.

Obviously the majority of the range / reactivity improvement over default V1 settings comes due to the absence of Ka Guard - forced off in C-mode aka Euro mode.

For those beginner users who don't already know, that Ka guard feature adds time to an alert because the detector waits for verification of the first detected signal. And while that is awesome at filtering out Ka falses (and assuring a user that any Ka alert meant with high percentage accuracy that you were facing a real LEO threat), Ka guard can and will give headaches (and dissatisfaction) to people in tough terrain who expect and need more range from less filtering.

Another nice benefit is that custom sweeping a smaller segment of the entire bandwidth results in fewer Ka false alerts.

Additionally, and possibly less known by General users, is that custom sweeping Ka band actually increases K band range as well. I posted at least one K band test several years ago showing this to be true. The reason is that with less Ka band swept comes faster K band sweeping too. And more scans per second means more chance of catching very brief K signals that would otherwise be missed by slower default V1 settings, particularly if default setting users happen to turn POP off while in A-mode.

And although I personally no longer use a V1, I would still emphatically encourage all new V1 owners to take advantage of the increased efficiency and range that C-mode, forced guard off, and Ka sweeping provides.

With the choice of YaV1, V1Driver, and JBV1 we are surely very spoilt these days!
 

Brainstorm69

TXCTG 2016 MOTY
Advanced User
Premium Member
Joined
May 23, 2015
Messages
8,946
Reaction score
18,699
Awards
0
Location
Lone Star State
Last edited:

Sn95king

Learning to Drive
General User
Joined
Mar 2, 2016
Messages
31
Reaction score
26
Awards
0
Nice work redoing the tabular listing of the previously shared work.

For those less advanced users new to all this, the increased efficiency referred to in the original post (by scanning less bandwidth) without doubt increase a V1's reactivity to Ka band, which in turn adds a little bit of extra range.

How much obviously depends on terrain, obstacles, and all the other variables that come into play in the real world. My own testing, and that of other testing groups and individuals, has shown that to be very true.

And sometimes every yard matters, particularly when you're up against a foe who employs advanced levels of IO and patient selectivity of targets.

Obviously the majority of the range / reactivity improvement over default V1 settings comes due to the absence of Ka Guard - forced off in C-mode aka Euro mode.

For those beginner users who don't already know, that Ka guard feature adds time to an alert because the detector waits for verification of the first detected signal. And while that is awesome at filtering out Ka falses (and assuring a user that any Ka alert meant with high percentage accuracy that you were facing a real LEO threat), Ka guard can and will give headaches (and dissatisfaction) to people in tough terrain who expect and need more range from less filtering.

Another nice benefit is that custom sweeping a smaller segment of the entire bandwidth results in fewer Ka false alerts.

Additionally, and possibly less known by General users, is that custom sweeping Ka band actually increases K band range as well. I posted at least one K band test several years ago showing this to be true. The reason is that with less Ka band swept comes faster K band sweeping too. And more scans per second means more chance of catching very brief K signals that would otherwise be missed by slower default V1 settings, particularly if default setting users happen to turn POP off while in A-mode.

And although I personally no longer use a V1, I would still emphatically encourage all new V1 owners to take advantage of the increased efficiency and range that C-mode, forced guard off, and Ka sweeping provides.

With the choice of YaV1, V1Driver, and JBV1 we are surely very spoilt these days!
All this is the reason why I will never look away from the v1c , ever it's just so technical that I love it to much. Would you have a picture of your own sweeps you would run ? I like to compare my own

Sent from my SM-N960U using Tapatalk
 

RadarSammich

Selective listening expert
Advanced User
Joined
May 1, 2017
Messages
1,176
Reaction score
1,519
Awards
0
Location
Arizona
Arizona is getting more 35.5 oriented, so a 35.5 weighted would be good for that region.
 

Sn95king

Learning to Drive
General User
Joined
Mar 2, 2016
Messages
31
Reaction score
26
Awards
0
Alright so quick discussion when having custom sweeps on jbv1 how do you know which one is actually programmed into the radar ? Also it will say new sweep unknown like its putting in its own sweeps and not mine. I dont have override on for it's not needed or does anyone recommend it?

Sent from my SM-N960U using Tapatalk
 

dchemist

Lifetime RDF Contributor
Advanced User
Lifetime Premium Member
Joined
Jul 26, 2017
Messages
2,973
Reaction score
5,394
Awards
0
Location
Benton, AR
Nice work redoing the tabular listing of the previously shared work.

For those less advanced users new to all this, the increased efficiency referred to in the original post (by scanning less bandwidth) without doubt increase a V1's reactivity to Ka band, which in turn adds a little bit of extra range.

How much obviously depends on terrain, obstacles, and all the other variables that come into play in the real world. My own testing, and that of other testing groups and individuals, has shown that to be very true.

And sometimes every yard matters, particularly when you're up against a foe who employs advanced levels of IO and patient selectivity of targets.

Obviously the majority of the range / reactivity improvement over default V1 settings comes due to the absence of Ka Guard - forced off in C-mode aka Euro mode.

For those beginner users who don't already know, that Ka guard feature adds time to an alert because the detector waits for verification of the first detected signal. And while that is awesome at filtering out Ka falses (and assuring a user that any Ka alert meant with high percentage accuracy that you were facing a real LEO threat), Ka guard can and will give headaches (and dissatisfaction) to people in tough terrain who expect and need more range from less filtering.

Another nice benefit is that custom sweeping a smaller segment of the entire bandwidth results in fewer Ka false alerts.

Additionally, and possibly less known by General users, is that custom sweeping Ka band actually increases K band range as well. I posted at least one K band test several years ago showing this to be true. The reason is that with less Ka band swept comes faster K band sweeping too. And more scans per second means more chance of catching very brief K signals that would otherwise be missed by slower default V1 settings, particularly if default setting users happen to turn POP off while in A-mode.

And although I personally no longer use a V1, I would still emphatically encourage all new V1 owners to take advantage of the increased efficiency and range that C-mode, forced guard off, and Ka sweeping provides.

With the choice of YaV1, V1Driver, and JBV1 we are surely very spoilt these days!
Based on your driving habits, it's understandable why you would have had balanced sweeps. Right now I'm rethinking my "Only Sarge" profile and want to adjust my sweeps to become a "commute" profile. Based on my last couple of years experience, I'm facing Stalkers for Ka and Decatur K band. I'm really thinking I'd like to run a 34.7 weighted sweep or possibly @Insipid Monkey ultra fast. You know the terrain and threat as well as I do. Any suggestions? Also @InsipidMonkey and @Nine_C1 I'd love suggestions.

Posted from my Pixel 2 using the RDF Mobile App!
 

2FastNot2Furious

Learning to Drive
General User
Joined
May 29, 2014
Messages
49
Reaction score
7
Awards
0
Location
DFW
I drive alot in the dallas/ft worth area, and make many trips from dallas to houston on interstate 45 and also the country roads going from madisonville, college station and navasota.
can anyone suggest which is the best setup for me on the V1 for all bands. i want the v1 to be quite as possible (no false alerts, bands to be turned off that are not required) and provide the best range with great accuracy.
 

Users Who Are Viewing This Thread (Users: 0, Guests: 0)

Unregistered User Ad


ATTENTION: Want ads to disappear? Register for an account by clicking here - it's free and NO ADS ARE DISPLAYED TO REGISTERED MEMBERS! Thanks!

Donation drives

RDF Server & License Fees (AUGUST 2019) (ACTIVE)

This donation drive covers the server and licensing fees for RDF for the month of August 2019...
Goal
$541.00
Earned
$180.00
This donation drive ends in

Latest threads

Latest posts

Social Group Activity

Forum statistics

Threads
76,505
Messages
1,165,990
Members
19,642
Latest member
SR45
Top