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.
What mode are you running in? And are you experiencing excessive K / BSM falses?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
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)What mode are you running in? And are you experiencing excessive K / BSM falses?
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.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.
Left it alone at the defaultWhat did you set for K-band?
OMG! Can you get that 35.5 sweep any wider!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=)
- 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.
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.Left it alone at the default
23.910-24.250
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.33.690-33.910 (to cover 33.8 MPH)
I always wonder about such a high ceiling. They only thing I’ve gotten up anywhere near 24.250 is a single stationary false.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 covering the "in-spec" K band range (24.150±0.100).I always wonder about such a high ceiling. They only thing I’ve gotten up anywhere near 24.250 is a single stationary false.
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!Just giving you shit bro! 35.5 is always tight! My locals run it and it's dead nuts close to 35.500.