Radenso pro M on the way

benzr

Been there done that !! Original V1 user !!
Advanced User
Joined
Apr 23, 2012
Messages
4,855
Reaction score
5,521
Location
FLA

Dr M5 Comp

Learning to Drive
General User
Joined
Feb 21, 2019
Messages
42
Reaction score
33
Turn your Ka filter off.

Ok, thanks. So teach me something. So Ka Narrow filters specific bands associated with BSM's, right? So we want to leave that on. Ka Filter would apply a filter to the whole Ka frequency so not a good idea as we want maximum warning, correct? Thanks.
 

Heywood

Learning Something New, Still Dying Stupid
Advanced User
Lifetime Premium Member
Joined
May 12, 2016
Messages
3,561
Reaction score
6,344
Location
Alberta Canada
Ok, thanks. So teach me something. So Ka Narrow filters specific bands associated with BSM's, right? So we want to leave that on. Ka Filter would apply a filter to the whole Ka frequency so not a good idea as we want maximum warning, correct? Thanks.
Yes and no, but your on the right track.

1. BSM does not drift into the Ka spectrum. Right now it’s only in K band
2. Ka Wide is more for the European or over seas market.
3. Ka segmentation was added in the last couple of Pro-M firmware’s. You didn’t have the ability to turn off specific Ka frequencies like you do now.
If you look at the segmentation options of the Unidens or the Redline Ex, it’ll give you a better idea of how wide the Ka spectrum is. That’s why, in North America, we suggest leaving them all off except segments 2/5/8.
4. The theory is when you’re not looking for frequencies you don’t need to see, the detector would run faster on ones you did.

So your right on your thoughts of why, but off base with the BSM aspect when considering Ka Band.
.
 

Dr M5 Comp

Learning to Drive
General User
Joined
Feb 21, 2019
Messages
42
Reaction score
33
Yes and no, but your on the right track.

1. BSM does not drift into the Ka spectrum. Right now it’s only in K band
2. Ka Wide is more for the European or over seas market.
3. Ka segmentation was added in the last couple of Pro-M firmware’s. You didn’t have the ability to turn off specific Ka frequencies like you do now.
If you look at the segmentation options of the Unidens or the Redline Ex, it’ll give you a better idea of how wide the Ka spectrum is. That’s why, in North America, we suggest leaving them all off except segments 2/5/8.
4. The theory is when you’re not looking for frequencies you don’t need to see, the detector would run faster on ones you did.

So your right on your thoughts of why, but off base with the BSM aspect when considering Ka Band.
.

Ok thanks a lot. You said "in North America, we suggest leaving them all off except segments 2/5/8". How does this statement get implemented on the Pro M? Are these settings correct then or do you recommend cutting them all off? Thanks.
  • *Ka:Narrow
    • Ka 33.8 On
    • Ka 34.3 Off
    • Ka 34.7 On
    • Ka 35.5 On
 

Heywood

Learning Something New, Still Dying Stupid
Advanced User
Lifetime Premium Member
Joined
May 12, 2016
Messages
3,561
Reaction score
6,344
Location
Alberta Canada
Ok thanks a lot. You said "in North America, we suggest leaving them all off except segments 2/5/8". How does this statement get implemented on the Pro M? Are these settings correct then or do you recommend cutting them all off? Thanks.
  • *Ka:Narrow
    • Ka 33.8 On
    • Ka 34.3 Off
    • Ka 34.7 On
    • Ka 35.5 On
That looks good how you have it. The 34.3 is an overseas frequency. Just keep the Ka filter off.

33.8 is hit and miss. Some places still use it, but it’s not as widespread as 34.7 and 35.5.

The problem with 33.8 is that some cheap radar detectors, such as the Cobras, will false most high end detectors right around that frequency. Usually on a 2 lane road when they’re heading at you. It’ll look like I/O (instant on).

Once you get some seat time, you’ll find out in your daily commute what you see. You might find there is no 33.8 and turn it off too if you don’t need it. Maybe turn it back on for road trips.
 
Last edited:

aikidoka

Learning to Drive
General User
Joined
Jun 22, 2017
Messages
12
Reaction score
16
Location
Indiana
I attached a photo of where I plan to mount the Radenso on my motorcycle. I have question about the multa radar settings for Chicago and Northwest Indiana. I have them both set to narrow and the filter on
4F054E71-EE51-4B47-9A76-1FDD7727F0AA.jpeg
high. I’ve gotten some detections in both stated but nothing visibly confirmed. Any suggestions?
 

DrHow

Lifetime RDF Contributor
Advanced User
Lifetime Premium Member
Joined
May 18, 2018
Messages
2,241
Reaction score
3,462
I attached a photo of where I plan to mount the Radenso on my motorcycle. I have question about the multa radar settings for Chicago and Northwest Indiana. I have them both set to narrow and the filter on View attachment 119367high. I’ve gotten some detections in both stated but nothing visibly confirmed. Any suggestions?
Keep 33.8 on. Too much of that running around Indiana. I see this regularly.

In Chicago, MRCT is a danger on main non interstate roads. There are default factory recommendation for MRCT. Suggest sticking with that.
 

aikidoka

Learning to Drive
General User
Joined
Jun 22, 2017
Messages
12
Reaction score
16
Location
Indiana
Ok. I got a MD detection on 294 this morning 8 bars, no ramp up. It then changed to MT at only 1 bar and kept with that. No visual confirmation.
 

TheSkyIsFalling

Learning to Fly
Beginner User
Joined
Feb 7, 2016
Messages
1,215
Reaction score
1,570
Ok thanks a lot. You said "in North America, we suggest leaving them all off except segments 2/5/8". How does this statement get implemented on the Pro M? Are these settings correct then or do you recommend cutting them all off? Thanks.
  • *Ka:Narrow
    • Ka 33.8 On
    • Ka 34.3 Off
    • Ka 34.7 On
    • Ka 35.5 On

That’s how I have it. I get 33.8 falsing but nothing crazy and like heywood stated. With seat time on how the pro M behaves. It’s definitely a false. I personally believe in my area only 34.7 is used. But since the pro M is extremely good a detecting 34.7. I feel any (if there is) loss of performance in 34.7 range is worth it in case I do get a legit 33.8 or 35.5 hit
 

DrHow

Lifetime RDF Contributor
Advanced User
Lifetime Premium Member
Joined
May 18, 2018
Messages
2,241
Reaction score
3,462
Ok. I got a MD detection on 294 this morning 8 bars, no ramp up. It then changed to MT at only 1 bar and kept with that. No visual confirmation.
MRCD? Then you changed to MRCT?

Follow the recommended factory MRTC settings when needed in Chicago area. MRCT is a fix multi lane, multi direction traffic speed ticket machine. I might have some pics of what they look like up there. For the most part, the newer fixed sites are on galvanized looking polls, on their own, about 20ish feet tall. Radar and cams on your traveling side of road will face other way picking you up when you go past. Or when oncoming you would see these on opposite side of street, the radar/cams facing you.

Using the factory default MRCT settings (it is late, I could have this backwards) of MRCT narrow, filter high should help cut down false BSM as MRCT, still have good range (for MRCT). When approaching the fixed site on your side of road, radar facing away until you go past, warnings can be as little as 400 feet. Normally more than that. These are on main roads, not interstates. I think I have had a real MRCT reading from the interstate. It picked up a MRCT fix just past the overpass on the road to the right of the exit lane. That road, forget the name of the exit, has that cam system clocking traffic maybe 500’ or so east of the interchange. This was north west Chicago area on 294. I was going past the exit. I have gotten off there and seen (plus alert) the fixed MRCT speed trap on that cross road.

Hope this helps.
 

Discord Server

Latest threads

Forum statistics

Threads
77,402
Messages
1,179,721
Members
19,819
Latest member
Chazark
Top