RL360c 1st Impressions

[F15]

@westwind77 I am driving 300 miles today through OK and MO. What settings would you used based on these tests?

 

[westwind77]

@westwind77 I am driving 300 miles today through OK and MO. What settings would you used based on these tests?

I do not know the exact threats you face in OK or MO. Personally I run K on all segments and Ka 2,4,5,6,8 just to C.M.A. The RL360c has shown to be a very sensitive RD in real world testing. My 'tests' were more about reactivity comparison than anything else.

 

[KASHER1979]

If this detector is digital and really very fast then I can't see that it would have any issues scanning quickly.

I am still not convinced that there isn't some kind of filtering happening.... Either that or it just isn't as fast as they think, but even the old Redline O with RDR off would catch super fast I/O shots. So I dunno.............

 

[searay]

@westwind77 I am driving 300 miles today through OK and MO. What settings would you used based on these tests?

Not sure about OK but here in MO I run my RL with all K bands on and with K notch on as well as Ka bands 2/3/4/5/6/7/8 also to C.M.A. Not sure if all of these Ka bands are truly necessary but I have found a few guns that have drifted both low and high so it's always better to play it safe especially with Ka.
That said, the RL360c has been my quietest detector yet (I came from the Max 360) and the range is incredible. Safe travels.

 

[westwind77]

That said, the RL360c has been my quietest detector yet (I came from the Max 360)

That is very surprising. I have a very short commute to work and the last two days I have recieved a few BSM alerts both directions each time, where I can go multiple days without a BSM alert from the M360. I will admit more time is needed with the RL360c but so far I find the M360 filtering superior.

 

[SoulPatch]

That is very surprising. I have a very short commute to work and the last two days I have recieved a few BSM alerts both directions each time, where I can go multiple days without a BSM alert from the M360. I will admit more time is needed with the RL360c but so far I find the M360 filtering superior.

Comparing my M360c to my R360c, I have the opposite experience.

 

[samq45]

Here is a video from my basic reactivity testing. When the new firmware came out I shot the RL 360c and V1G2 many times. The delays were all over the board on the RL360 and the V1 was lightning fast Sometimes the delay for the RL360 would be about 1 sec, other times as much as 4-5 sec delay. I dont have anything scientific to measure this, just the time in the videos.

Here is a is a video of one of the longer ones (but not the longest), I have a few more. I am showing the ATR so you can see when I trigger it and the only detector on is the RL360 and I have it pointed away from the detector, but I am still pretty close. I had K enabled and segments 2,4,5,6,7,8 on (NY)

I reloaded the firmware after this video using DT and the delay seemed to improve and was closer to Vortex's testing, However my 2nd test was from a further distance away - maybe 30 feet?

Do you think its possible that even when we are pointing away from the vehicle the detector is being slightly overdriven because it has so much sensitivity? Why are we seeing perhaps some shorter delays for Vortex's test?

I am heading on vacation shortly to the woods and have my battery pack and ATR, I also have a number of other detectors packed up.

Let me know what you would like me to do and Ill give it my best shot.

 

[BagNDrag]

That is very surprising. I have a very short commute to work and the last two days I have recieved a few BSM alerts both directions each time, where I can go multiple days without a BSM alert from the M360. I will admit more time is needed with the RL360c but so far I find the M360 filtering superior.

Hi Westwind,

Do you have K Notch enabled? My experience with K Notch enabled, it is WAY more quiet than my M360.

-Mark

 

[samq45]

That is very surprising. I have a very short commute to work and the last two days I have recieved a few BSM alerts both directions each time, where I can go multiple days without a BSM alert from the M360. I will admit more time is needed with the RL360c but so far I find the M360 filtering superior.

The RL360c is very quiet, especially with K Notch enabled. It is very close to the V1 from my experience.

I also had a lot of the BSMs go off when I updated to 1.3 using my phone. Once I updated the detector with DT, it seemed to make the BSMs a lot less.

It might not work at all, but I think its worth reloading the full firmware with DT and see if that helps any.

 

[westwind77]

Hi Westwind,

Do you have K Notch enabled? My experience with K Notch enabled, it is WAY more quiet than my M360.

-Mark

The RL360c is very quiet, especially with K Notch enabled. It is very close to the V1 from my experience.

I also had a lot of the BSMs go off when I updated to 1.3 using my phone. Once I updated the detector with DT, it seemed to make the BSMs a lot less.

It might not work at all, but I think its worth reloading the full firmware with DT and see if that helps any.

Good point...I do not have K-Notch enabled.....but I also have a local who runs K-band right in that range along with a MASP unit that runs there too....I know it is designed to still punch through when stronger but when you live in an area with a lot of tight turns, hills, foliage having ever bit of warning is really helpful.

I wish I had more time on my hands as I would tune the Bushnell up further into that range and make a few runs with in on and off to see if it made a difference.

 

[samq45]

I wish I had more time on my hands as I would tune the Bushnell up further into that range and make a few runs with in on and off to see if it made a difference.

That would be a nice test if we can find someone who can do it. It would be interesting to see what kind of additional risk you are taking with the notch on. I "loaned" my bushnell to the local race track and I have not seen it since.

 

[DownEaster]

Received my second RedLine 360C yesterday. Came with 1.3 already installed. The experience has been totally different than my first experience over a month ago. My original unit had a severe rattle inside, would not display frequencies, and had all of the other reported issues that firmware 1.2 provided.

The new unit appears flawless. Running in Highway mode I was getting a lot of K-band hits from various electronic signs running around town, but once I set the sensitivity to AutoLoK, that issue disappeared.

No rattles BTW.

Very quiet thus far.

My settings:

AutoLoK
K Notch ON
X-band OFF
Laser ON
Ka-band ON
K-band ON
TSR ON

I presume that with K and Ka ON, the various segmentation settings that the RedLine defaults to, are ignored.

Unit connects to my iPhone hotspot, although I have not been witness to any database updates.

One gripe is that the Auto brightness should work better. It dims OK at night, but does not brighten to MAX the way I would like during the day.

 

[ICULookin]

thanks for your observations and setting preferences. Keep us posted as to the on road performance.

 

[BagNDrag]

Good point...I do not have K-Notch enabled.....but I also have a local who runs K-band right in that range along with a MASP unit that runs there too....I know it is designed to still punch through when stronger but when you live in an area with a lot of tight turns, hills, foliage having ever bit of warning is really helpful.

I wish I had more time on my hands as I would tune the Bushnell up further into that range and make a few runs with in on and off to see if it made a difference.

Escort's implementation of K-Notch seems to be a solid approach. It would be great to get some actual testing on it, but it seems to let signals punch through at an appropriate threshold that should still give you a save if it was a real threat.

-Mark

 

[timark251]

I will say they def tweaked the BSM filtering on the Redline360C. Came across a newer Honda Odyssey this afternoon on my way home from work, was right in front of me. A quick alert to K-band maybe 3 bars for about 2 seconds, then dead silent the rest of the time I was in view of it. So their "AI" technically is working. Frequency was 24.202.

 

[BagNDrag]

I presume that with K and Ka ON, the various segmentation settings that the RedLine defaults to, are ignored.

You are correct, having those on ignores the segmentation settings.

-Mark

 

[DownEaster]

Thanks for the confirmation.

You are correct, having those on ignores the segmentation settings.

-Mark