forgot an important point. I have had one likely Ka false over a week ago at 34.5. These were the main reasons I wanted to run custom frequencies to screen these out. So far, I haven’t gotten more than 1.
V1 Gen2 Custom Sweeps/Frequencies: Negative impact on falsing?
- Thread starter InsipidMonkey
- Start date
- Tagged users None
I haven't run custom frequencies (CF) yet. But below are some of the falses I've gotten that have made me think about it. I haven't had a ton of them, but enough to make me consider CF. Although the reports of CF perhaps causing more BSM falses have also made me think about whether I really want to run CF. So I am interested in this thread and people's thoughts.
35.0xx
35.1xx
35.3xx
34.0xx
34.1xx
34.5xx
33.6xx
I also have had some falses in 33.7xx-33.8xx and 35.4xx-35.5xx, but using CF would not have helped with those.
35.0xx
35.1xx
35.3xx
34.0xx
34.1xx
34.5xx
33.6xx
I also have had some falses in 33.7xx-33.8xx and 35.4xx-35.5xx, but using CF would not have helped with those.
Last edited:
- Joined
- Sep 16, 2016
- Messages
- 7,454
- Reaction score
- 10,633
The first few days I had run the V1G2, I had quite a few "off" frequency falses. I decided to run Custom Frequencies to stop those.
Since I've run custom frequencies 0 Ka Falses. Running the same ones I had for V1.1
Since I've run custom frequencies 0 Ka Falses. Running the same ones I had for V1.1
What mode are you running in? And are you experiencing excessive K / BSM falses?
Update:
Having gone back and forth with Custom Frequencies and Default (both with X off a majority of the time and Laser off all the time) and then using Advanced Logic below PSL and Logic above PSL,
I'm tempted to stay with the Default setup unless VR changes how Custom Frequencies work. I've only encountered a few Ka falses in the last week or two it seems.
Having gone back and forth with Custom Frequencies and Default (both with X off a majority of the time and Laser off all the time) and then using Advanced Logic below PSL and Logic above PSL,
I'm tempted to stay with the Default setup unless VR changes how Custom Frequencies work. I've only encountered a few Ka falses in the last week or two it seems.
- Joined
- Sep 16, 2016
- Messages
- 7,454
- Reaction score
- 10,633
Currently in "l" Logic mode with CFs. Nice quiet ride. I don't hear any impact on K filtering at all (yes, using standard K sweep)
- Joined
- Feb 22, 2012
- Messages
- 832
- Reaction score
- 2,962
Brainstorm - I've been running CF for this very reason and I have been VERY pleased with the results. I still want Valentine to fix the issue in firmware, but until then my CF have helped keep the Boggie Counter down to where it should be.
-Mark
The temptation was too great (guilty pleasures 
) so I created a “custom frequencies” profile again to let her rip- I think I have a good sense of what happens running logic w / no CFs for my area.
covering the bases + a drifting gun with no more 34.5 falses (34.5 falses=
)
so I’ll be running logic w/ CFs...again to see. When I was running CFs before, I did get some high K signal strength meter bars (3 and above) for some BSM falses. I did not get any really above 2 up until today; I think I had a 3 bar today briefly. It was enough to generate an audible alert.
) so I created a “custom frequencies” profile again to let her rip- I think I have a good sense of what happens running logic w / no CFs for my area.covering the bases + a drifting gun with no more 34.5 falses (34.5 falses=
)- 33.690-33.910 (to cover 33.8 MPH)
- 34.600-34.870 (to cover 34.7 Stalker)
- 35.400-35.675 (to cover 35.5 Kustom Signals and Decatur)
so I’ll be running logic w/ CFs...again to see. When I was running CFs before, I did get some high K signal strength meter bars (3 and above) for some BSM falses. I did not get any really above 2 up until today; I think I had a 3 bar today briefly. It was enough to generate an audible alert.
Last edited:
What did you set for K-band?
Left it alone at the default
23.910-24.250
OMG! Can you get that 35.5 sweep any wider!The temptation was too great (guilty pleasures
covering the bases + a drifting gun with no more 34.5 falses (34.5 falses=
- 33.690-33.910 (to cover 33.8 MPH)
- 34.600-34.870 (to cover 34.7 Stalker)
- 35.400-35.675 (to cover 35.5 Kustom Signals and Decatur)
so I’ll be running logic w/ CFs...again to see. When I was running CFs before, I did get some high K signal strength meter bars (3 and above) for some BSM falses. I did not get any really above 2 up until today; I think I had a 3 bar today briefly. It was enough to generate an audible alert.
Just giving you shit bro! 35.5 is always tight! My locals run it and it's dead nuts close to 35.500.
Last edited:
- Thread starter
- Admin
- #72
If things are still working well after a week, I wonder if narrowing this down further to 24.000-24.250 will have any effect.
Just for reference, 33.8 is covered no matter what you do, whether you want it or not. No need to add a CF window for it.
I always wonder about such a high ceiling. They only thing I’ve gotten up anywhere near 24.250 is a single stationary false.
- Thread starter
- Admin
- #74
Just covering the "in-spec" K band range (24.150±0.100).
I’ve had 35.4xx but those might be falses. It’s tighter than seg 8 on the uniden I think. Will have to checkOMG! Can you get that 35.5 sweep any wider!
Last edited:
I bet they're falses! Unless you verify the cop!
I was running looser Ka sweeps on my Gen1 and JBV1 was boxed for a tighter range.
I might try a tighter K-band CF today on my Gen2.
I might try a tighter K-band CF today on my Gen2.
Was Ka guard discussed with Mike in the interview? I can’t remember. That option obviously has gone away to turn on/off. I don’t know if they just got rid of it or if some new Ka filtering is built in now. I can’t imagine with the range this thing has or with the ka falses being reported that there is any type of ka filtering.
We still get J-outs on Ka. There's at least that. I'm not sure how much Ka Guard helped with sat dishes.
I ran 4 years with Ka guard off.
I ran 4 years with Ka guard off.
Similar threads
