Custom Notch Filters?

BestRadarDetectors

Premium Member
Premium Member
Advanced User
Intermediate User
Beginner User
General User
MFG/Vendor
Newly Registered
Joined
Oct 17, 2011
Messages
11,827
Reaction score
26,428
Rating - 0%
0   0   0
Our plan was to have the Net Radar DSP automatically learn to ignore certain frequencies of LCC equipped that the Net Radar DSP has installed on but its not feasible to do this at this time on the existing ALP hardware and still existing auto learn patents.
What I was thinking is that we can add some selectable notch filters to make life much better for some customers that are willing to risk locking out a very small section instead of a large segment.

If we could add lets say 5 small notches what would you all prefer?
 

TurboDriver

PSL + 50, every now and then
Premium Member
Advanced User
Intermediate User
Beginner User
General User
Newly Registered
Joined
Sep 14, 2012
Messages
1,657
Reaction score
1,712
Location
Michigan
Rating - 0%
0   0   0
...
24.197-24.201 would be helpful.

Also on the App side - being able to switch profiles once an alert has started would be great. Once you get stuck behind a Pacifica you literally have to drop back over a quarter mile to stop the alert so that you can switch to a different profile.

Posted from my moto x4 using the RDF Mobile App!
 
Last edited:

BestRadarDetectors

Premium Member
Premium Member
Advanced User
Intermediate User
Beginner User
General User
MFG/Vendor
Newly Registered
Joined
Oct 17, 2011
Messages
11,827
Reaction score
26,428
Rating - 0%
0   0   0
Hopefully we can narrow it down to maybe 5 notch filters that we can cover most customers.
 

TurboDriver

PSL + 50, every now and then
Premium Member
Advanced User
Intermediate User
Beginner User
General User
Newly Registered
Joined
Sep 14, 2012
Messages
1,657
Reaction score
1,712
Location
Michigan
Rating - 0%
0   0   0
...
24.197-24.201 would be helpful.

Also on the App side - being able to switch profiles once an alert has started would be great. Once you get stuck behind a Pacifica you literally have to drop back over a quarter mile to stop the alert so that you can switch to a different profile.

Posted from my moto x4 using the RDF Mobile App!
---edit add---

Not to derail things but the current DSP firmware is just like the Uniden 1.46 with long Traffic Filter delay. If we could go back to older firmware which had the equivalent of 1.37 of Uniden so we could run Traffic Filter (with no delay) along with K Filter it would help also with falses.

Posted from my moto x4 using the RDF Mobile App!
 

BestRadarDetectors

Premium Member
Premium Member
Advanced User
Intermediate User
Beginner User
General User
MFG/Vendor
Newly Registered
Joined
Oct 17, 2011
Messages
11,827
Reaction score
26,428
Rating - 0%
0   0   0
---edit add---

Not to derail things but the current DSP firmware is just like the Uniden 1.46 with long Traffic Filter delay. If we could go back to older firmware which had the equivalent of 1.37 of Uniden so we could run Traffic Filter (with no delay) along with K Filter it would help also with falses.

Posted from my moto x4 using the RDF Mobile App!
When Uniden works out all the issues we can make the adjustment at that time. Its easier at this point since they have much more users to work out the issue on a larger scale. We can adapt to what works best when they are done.

--- DOUBLEPOST MERGED ---

...
24.197-24.201 would be helpful.

Also on the App side - being able to switch profiles once an alert has started would be great. Once you get stuck behind a Pacifica you literally have to drop back over a quarter mile to stop the alert so that you can switch to a different profile.

Posted from my moto x4 using the RDF Mobile App!
What vehicles do you see in that range?
 

Up All Night

Premium Member
Premium Member
Advanced User
Intermediate User
Beginner User
General User
Newly Registered
Joined
Nov 27, 2015
Messages
2,789
Reaction score
2,649
Location
Cleveland, OH
Rating - 0%
0   0   0
What I don’t understand is, if (Name Brand) can filter out 85% of the cars, what makes two or three mfg’s so different that the algorithm that works on the others can’t be adjusted ? Is it the case where only one person knew how to do it and they left?? Or do some mfg’s mimic real radar guns and the detectors just can’t tell the difference?
Posted from my iPhone using the RDF Mobile App!
 

BestRadarDetectors

Premium Member
Premium Member
Advanced User
Intermediate User
Beginner User
General User
MFG/Vendor
Newly Registered
Joined
Oct 17, 2011
Messages
11,827
Reaction score
26,428
Rating - 0%
0   0   0
What I don’t understand is, if (Name Brand) can filter out 85% of the cars, what makes two or three mfg’s so different that the algorithm that works on the others can’t be adjusted ? Is it the case where only one person knew how to do it and they left?? Or do some mfg’s mimic real radar guns and the detectors just can’t tell the difference?
Posted from my iPhone using the RDF Mobile App!
Some are too close that its risky to try to ignore. GM is probably the biggest culprit. I don't think anyone has found a way to ignore all GM systems without too much of a risk. Some of the earlier systems have been easy but many of the latest ones are more difficult. I know Uniden is arranging for the engineers to come out to the US next year to really spend a lot of time around these systems to figure something out.
 

TurboDriver

PSL + 50, every now and then
Premium Member
Advanced User
Intermediate User
Beginner User
General User
Newly Registered
Joined
Sep 14, 2012
Messages
1,657
Reaction score
1,712
Location
Michigan
Rating - 0%
0   0   0
Acura/Honda is mostly what I see in that range.
Yes, those too.. but here in Michigan is is the Chrysler, Dodge, Jeeps that are rampant!

BRD --- For .197-.201 it's Pacifica's and Jeep Cherokee mostly.

GM's have always been a problem but they aren't as distinct of a frequency. Some newer are around 24.135, others from .165-.180, older ones were .078 ish and .248 ish. I see real radar in all but the lows and higher ranges so I wouldn't want to notch any mid ranges. The .100-.195 range for me has been a threat in recent year.

Posted from my moto x4 using the RDF Mobile App!
 

TurboDriver

PSL + 50, every now and then
Premium Member
Advanced User
Intermediate User
Beginner User
General User
Newly Registered
Joined
Sep 14, 2012
Messages
1,657
Reaction score
1,712
Location
Michigan
Rating - 0%
0   0   0
---edit--. I tried adding to my other post but it didn't work for me, sorry...

If anything, I would like to see high and low of K Narrow be adjustable, it might be the easiest fix for now.

I'm not sure if possible to do in single increments but I personally would run .090-.197, or something like that.

Posted from my moto x4 using the RDF Mobile App!
 
Last edited:

BestRadarDetectors

Premium Member
Premium Member
Advanced User
Intermediate User
Beginner User
General User
MFG/Vendor
Newly Registered
Joined
Oct 17, 2011
Messages
11,827
Reaction score
26,428
Rating - 0%
0   0   0
---edit--. I tried adding to my other post but it didn't work for me, sorry...

If anything, I would like to see high and low of K Narrow be adjustable, it might be the easiest fix for now.

I'm not sure if possible to do in single increments but I personally would run .090-.197, or something like that.

Posted from my moto x4 using the RDF Mobile App!
With NR we don't have a wide or narrow.. We offer Band Segmentation and only these 4 segments affect the US:

K3 24.050 - 24.100
K4 24.100 - 24.150
K5 24.150 – 24.200
K6 24.200 – 24.250

I am trying to add a few extra slices to make the segments more narrow since they are currently in 50 blocks so I would maybe drop them to 25 blocks and also add some specific slices geared towards BSM nuisances.
 

mikedotd

Arrow enthusiast
Premium Member
Advanced User
Intermediate User
Beginner User
General User
Newly Registered
Joined
May 6, 2012
Messages
2,889
Reaction score
4,088
Location
New England
Rating - 100%
1   0   0
As @TurboDriver mentioned, being able to notch out 24.197+ would go along way towards pacifying Acura/Honda's. That's really the only range I'd feel comfortable disabling outside of say 24.100 - 24.196.
 

TurboDriver

PSL + 50, every now and then
Premium Member
Advanced User
Intermediate User
Beginner User
General User
Newly Registered
Joined
Sep 14, 2012
Messages
1,657
Reaction score
1,712
Location
Michigan
Rating - 0%
0   0   0
With NR we don't have a wide or narrow.. We offer Band Segmentation and only these 4 segments affect the US:

K3 24.050 - 24.100
K4 24.100 - 24.150
K5 24.150 – 24.200
K6 24.200 – 24.250

I am trying to add a few extra slices to make the segments more narrow since they are currently in 50 blocks so I would maybe drop them to 25 blocks and also add some specific slices geared towards BSM nuisances.
Yes, I kinda miss spoke with the narrow, I knew what I meant .

I do use Seg 4 & 5 on rear setup and as a front Profile option, it does cut down on the falses but being able to to tweak the edges of those 2 Segs would be awesome!

Posted from my moto x4 using the RDF Mobile App!
 

Blizzard

Premium Member
Premium Member
Advanced User
Intermediate User
Beginner User
General User
Newly Registered
Joined
Nov 21, 2015
Messages
1,144
Reaction score
1,457
Location
Northeast
Rating - 0%
0   0   0
Agreed on 24.197-.24.201. Acuras and tons Honda CRV’s. Also get 24.168 GM falses but I too would be worried about cutting that range out. In my particular area .197-.201 are probably 90% of my falses. Can’t stand CRV’s and there are so many by me
 

Flonase

Course X
Premium Member
Intermediate User
Beginner User
General User
Newly Registered
Joined
Sep 10, 2017
Messages
270
Reaction score
346
Rating - 0%
0   0   0
One more vote for that .197-.201 slice. When I ran stand-alone DSP in a windshield mount last winter, those were my only BSM falses. I think I remember both GMC Arcadias and new Chrysler Pacificas triggering that on occasion.

Since moving to a lower mounting point at the front of the TT, updating firmware, and having a crop of new cars hit the road, I have way way more BSM falses at different frequencies, but couldn’t really tell other common frequencies. Maybe I can look at my stats.

Edit: I have to look more, but can definitely say that I see up to 24.203 for falses on the high end...
 
Last edited:

BlueV1

10th gear
Premium Member
Advanced User
Intermediate User
Beginner User
General User
Newly Registered
Joined
Feb 8, 2016
Messages
1,683
Reaction score
2,427
Location
Western NC
Rating - 0%
0   0   0
I have a few K-band box mutes in JBV1 to deal with BSMs that I encounter. Hopefully these will help.
These might seem excessively wide, but I get notified at a lower volume and can still see the alert on my phone (marked as a muted signal) plus it will alert me full volume should the signal be sufficiently strong.

24.120-24.130 for Chrysler Pacificas
24.195-24.215 for Honda/Acura
I should probably add 24.175± for Mazda as well. I haven't muted those yet.

Many new Hondas are running 24.204 and 24.207. I have an Accord and Wife has a CR-V. (Looking for BSM modification ideas for both ;-)) Acuras tend to be 24.197 in my experience.

--- DOUBLEPOST MERGED ---

These screenshots might help as well. I wish I had a way to weed out only BSMs for you.
The screen that is showing the specific frequencies and dates, etc. Might be pretty helpful. Those are in my top 100 signals and shows in this case that I drove in the proximity of these signals for very long time. Ignore the 3 Ka signals at the bottom. I was either following or being followed by an LEO. :)
 

Attachments

TurboDriver

PSL + 50, every now and then
Premium Member
Advanced User
Intermediate User
Beginner User
General User
Newly Registered
Joined
Sep 14, 2012
Messages
1,657
Reaction score
1,712
Location
Michigan
Rating - 0%
0   0   0
The range might be close but I have found that certain brands of detectors report slightly different frequencies. My R3 and DSP are almost always exactly the same, and both of my Redline are usually within a .003 of the DSP. My NR-O is always about .010-.015 off from everything else and not consistent. I am not sure how V1's are but is seems a little higher than what I see.

The information is helpful but when implementing the actual filter I think it is important that we use the frequencies found on the detector the filter will be applied.

Posted from my moto x4 using the RDF Mobile App!
 
Last edited:

ThreePedals6.2

Motor Head
Moderator
Premium Member
Advanced User
Intermediate User
Beginner User
General User
Newly Registered
Joined
Dec 23, 2015
Messages
1,864
Reaction score
2,942
Rating - 100%
1   0   0
As @TurboDriver mentioned, being able to notch out 24.197+ would go along way towards pacifying Acura/Honda's. That's really the only range I'd feel comfortable disabling outside of say 24.100 - 24.196.
+1
This is really the only annoying range IMHO. There are so many new Honda's out there that is has really become an annoyance, so much so I shut off K band on my DSP for now. (Luckily there is barely any K band here).
@BestRadarDetectors also the mute,alert,mute, alert issue still seems to be a problem when these vehicles are in front of me.
Are they still working on this at all? Possibly a longer mute latch needs to be implemented still?. It seemed to be better at one point but i guess it was because i wasn't seeing many of these problem children on the road.
 

64pvolvo1800

Snail Pace
Premium Member
Advanced User
Intermediate User
Beginner User
General User
Newly Registered
Joined
May 1, 2012
Messages
1,282
Reaction score
486
Location
Atlanta
Rating - 100%
1   0   0
My Benz broadcasts 24.200 and drives me nuts!


Sent from my iPhone using Tapatalk
 

Flonase

Course X
Premium Member
Intermediate User
Beginner User
General User
Newly Registered
Joined
Sep 10, 2017
Messages
270
Reaction score
346
Rating - 0%
0   0   0
I went back and looked at the distribution of K-band alerts I had saved on the ALPConnect app. This is for a dual-DSP setup. I had 77 stored alerts from 9/14/2018 through 10/11/2018. This is primarily from driving between the Twin Cities metro and southwest Minnesota / northwest Iowa. I do not believe these alerts include a single legitimate LEO K-band signal. I had most of the stationary falses locked out on my standard drives, but I'm sure they include a not-insignificant number of door openers etc.

First, it isn't my imagination - the 24.200 issue is by far the most important one for me. It's 33 of my 77 total recorded K-band alerts:

Overall Distribution.png


For that set of alerts, I'd need to ignore 24.1955 to 24.2045 to be completely quiet:

Distribution 24200.png


The other one that popped up enough to look at is the one around 24.170. Here I'd need 24.1655 to 27.1745. I wasn't really looking at this one enough to say these were all BSMs, though. The stuff around 24.200 was always, always a BSM system in my driving this fall. Anyway here's the distribution of alerts around 24.170:

Distribution 24170.png


So, after actually looking at my alerts, my vote would be for the notch filter around 24.200 to extend from 24.1955 to 24.2045. I ignore those alerts anyway. If I choose to activate a notch filter in this range, I'd like to filter ALL of the alerts.

THANKS AGAIN for pushing this up in the priority list! Really can't wait to get this. Well, I can wait until spring, when I start driving the TT again, but my sentiment stands. This will be a really great addition to the NetRadar DSP package.

Edit: updated axis labels on detailed histograms and notch ranges.
 
Last edited:

Donation drives

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

This donation drive covers the server and licensing fees for RDF for the month of March 2019...
Goal
$334.00
Earned
$450.00
This donation drive ends in

Latest threads

Social Group Activity

Forum statistics

Threads
79,117
Messages
1,178,814
Members
18,146
Latest member
Zlazarus
Top