Could The RL360c Be Too Good For It's Own Good?

[Darkmann]

I've logged near 4 miles range but that was sketchy. Last week, I recorded, for sure 2.5 miles to LEO on a straightaway on RT. 13, in DE. In city, I get some random Ka but when I search, I find the source as true LEO, but usually well away from where the Ka announcement initiated. The RL360c range is probably too much for city (and even highway) driving - so much, I think, that it picks up "unnecessarily true" Ka. I don't run with the frequency bands displayed, but in my area, Ka = LEO, period. I pick them all,..., maybe too many for my comfort. I wish the display would also tell distance to signal along with the direction. What's your experience.

 

[sdrawkcaB]

In the city I prefer AutoLoK for the detector so that the sensitivity will automatically adjust based on travel speed.

I don't mind having the long distance alerts as I'd rather have it be overly sensitive to Ka than not sensitive enough. Other detectors have weak off axis detection, and you won't be alerted to one on a side street you're about to meet until you are only just a few hundred feet away from meeting at an intersection.

I will also take advantage of the Low Speed Muting (Cruise Alert / Quiet Ride). This will help keep it quiet when you're below your speed threshold that you define. I usually set mine to 15mph to help have it quiet when I'm stopped at stop lights. Others use it set to higher speeds such as 25mph or even 40mph, with the understanding that they won't be speeding if they're at those speeds in the city or residential areas. It's a personal preference and risk assessment. I opt for 15mph because I don't want to out-accelerate the GPS's ability to realize I'm now at 35mph and it needs to begin alerting me at 25mph but lagged behind...

Estimating distance likely won't happen any time soon due to the inability to account for things like signal reflection and signal attenuation.

 

[infiniti]

I've logged near 4 miles range but that was sketchy. Last week, I recorded, for sure 2.5 miles to LEO on a straightaway on RT. 13, in DE. In city, I get some random Ka but when I search, I find the source as true LEO, but usually well away from where the Ka announcement initiated. The RL360c range is probably too much for city (and even highway) driving - so much, I think, that it picks up "unnecessarily true" Ka. I don't run with the frequency bands displayed, but in my area, Ka = LEO, period. I pick them all,..., maybe too many for my comfort. I wish the display would also tell distance to signal along with the direction. What's your experience.

Where are you using this?

 

[Boozehound]

Maybe the current top 3- R360c, R7, and V1G2 are capable of nuisance alerts that are real police Ka. My G2 regularly knocks off real cops that are a mile off the expressway on side roads. That kind of range means I don't just drop anchor at the first whiff. I check the frequency for the band of bacon and an idea of distance. The R360 testing I've seen shows excellent sensitivity.

 

[DC Fluid]

This is a subject of interest for when Theia comes out.
Even more Ka range than the top 3?
My whole city bowl area could become constant alert zone. Radenso has said sensitivities will be adjustable for this.
I have played with the idea of reducing Ka on the R7 down to a "City" friendly % setting.
What I don't know and would have to research it, if Ka is reduced like done on K, is it only for "Advanced Mode"?
Or is City reduced too? Highway unaffected?
Arrows definetely help determine threat level with this problem.
I believe Escort Auto modes have NO effect on Ka sensitivity.
I love max sensitivity Ka but can see it being annoying in some areas. I work 2 blocks from the RCMP station and every day I leave there is a few kms of driving with Ka alerts because one of them parked with radar on.

 

[RoadDogg]

When you have a detector that is very sensitive and has great off axis performance, I definitely think it is great to have arrows to help pinpoint the source or sources.

When I was running my R3 as primary, I had many times I had crazy long detections that took a while to figure out where the LEO was.

As far as a detector like a RL360c or even a V1G2 or R7, I like to have crazy sensitivity and crazy off-axis detections and those WOW moments that go with them because sometimes that sensitivity with come in handy in challenging terrain or I/O situations.


Sent from my iPhone using Tapatalk

 

[Chrismx]

don’t overlook the advantage long range detection provides. If you have a LEO miles ahead (or in challenging terrain) and possibly light traffic that “nuisance” alert may be telling you there is a LEO ahead shooting IO..... just my 2¢

 

[westwind77]

I've logged near 4 miles range but that was sketchy. Last week, I recorded, for sure 2.5 miles to LEO on a straightaway on RT. 13, in DE. In city, I get some random Ka but when I search, I find the source as true LEO, but usually well away from where the Ka announcement initiated. The RL360c range is probably too much for city (and even highway) driving - so much, I think, that it picks up "unnecessarily true" Ka. I don't run with the frequency bands displayed, but in my area, Ka = LEO, period. I pick them all,..., maybe too many for my comfort. I wish the display would also tell distance to signal along with the direction. What's your experience.

'Too good for its own good'....maybe...maybe against C/O.....but that is about it. When you move up the ranks a bit more you will see what I mean. Long distance sensitivity is not everything in a RD, there are many other important factors to consider as well.