My Redline 360c Experience

brettzo

PSL +5
Intermediate User
Joined
Oct 22, 2012
Messages
255
Reaction score
417
Location
Alberta, Canada
I have now finally been using the Redline 360c for a couple of weeks and have had enough seat time to put it through its paces and I thought that I would share my experience so far. Overall, I’m liking it despite some concerns that I had about reactivity after doing some quick testing at home. Since then, I was able to get out and do some more practical radar and laser testing and gave me a bit more peace of mind.

The detector definitely has impressive range and the overall package is really nice. Coming from the R7 as my primary detector the Redline is sure quieter, though I still have a soft spot for the R7. It’s a great option and value at the price point. The overall quietness, filtering and auto lockouts was the reason that I wanted to try the Redline for my regular commutes. It’s already almost silent driving on my regular routes, though the detector still certainly needs some reactivity improvements and ramp up presentation. It can be pretty bad at times.

General Settings

V 1.9
Highway
K band: On
Ka band: 2/4/5/6/8
X band: Off
Laser: On
TSR: Off
K notch: Off
MRCD: On
MRCT: Off
Cruise alert: 30 KPH

Pros

Excellent range.

Great BSM filtering.

Nice design and construction. Feels solid and looks nice up on the windshield.

Escort mag mounts are really nice and helpful when transferring the detector to other vehicles.

Crisp screen and arrow presentation/visibility is very nice. Everything is easy to see during all times of the day, even with sunglasses.

Easy updates/connectivity. I don’t have WiFi in the car though when pulling into my garage or starting my vehicle I’m within close enough proximity of my home WLAN to be notified of updates and update the detector and update easily. Not having to bring it inside has been nice.

Escort Live app is nice for customizing settings on the fly.

Cons

Auto brightness doesn’t work very well as a lot of others have reported. I run the detector in the “Max” setting all of the time. Not a big deal to me, as I think that this brightness level works well for me during the day/night and in various weather environments but would be nice to see that working better.

Screen could be a bit larger, but just me pulling at straws. It’s adequate and I think that coming from the R7 is the reason it looks a bit small. It does what’s needed.

Slow reactivity in comparison to other detectors. K band can be extremely slow as I already knew going into this. Ka band segmented is borderline acceptable to me, but still pretty slow in comparison to say the R7 and many other detectors out there. I do find though that strong K band signals come through as needed & with adequate alerting time. I just wish that reactivity and ramp up was improved on and hoping that future firmware can address to put this detector on another level and be near perfect for me.

Cruise alert logic is a bit odd to me. When receiving an initial alert over the specified cruise alert limit (20MPH) and then slowing down below that threshold, any alerts previously detected while over the threshold will still alert at normal volume vs. automatically muting when falling below the cruise alert limit. Receiving these alerts above the threshold works as expected, but why not mute them automatically when falling below and then make them audible again once the limit has been exceeded? This is how I’m accustomed to using low speed muting and works much better in my opinion when driving in unfamiliar urban territory with several new false signals. I originally thought that I had an issue of some kind but found a post by Escort confirming this software logic. Not the end of the world but requires a push of the mute button in these cases.

Lifetime defender updates should be included with the R360c IMO. It’s a pretty nominal fee but feels a bit like nickel and diming given the price point of this detector.

Price is steep, especially up in Canada. $1,360 CAD retail after taxes. Add additional dollars for a blend mount, hardware, etc.

BSM’s

Coming from an R7, this detector sure is quiet. Eerily quiet at times. It’s a night and day difference for me so far vs. the R7’s K block 1 & 2 filtering on the “weak” setting. K band reactivity on the R360c is definitely very still slow in comparison so it’s kind of an apples to oranges thing for me right now, but the range should be adequate in most scenarios. Time will tell.

Auto Lockouts

Reliable and effective in most cases. Yes, Escort’s lockout algorithms tend to lean toward a quieter experience vs. extremely tight lockouts, but I find the Escort lockouts to work consistently as expected at locking out falses. My regular commute is already pretty much silent since using the detector. Lockouts can be concerning though with how wide they are. The detector automatically locked out a known signal and in testing yesterday with my Bushnell in that area, the signal from the Bushnell was being locked out, despite being pretty far off from the original locked out signal (40MHz+). I did a little test and unlocked the signal and then manually locked it out right after. The manual lockout seemed to cover a far wider range past the automatic lockout. To the point where I was locking the Bushnell out 2+ KM down the road. A bit concerning, though I don’t tend to use manual lockouts at all in where K band is in use anyway. It is nice to have though when operating the detector in areas that K band isn’t in use.

Though the R7 is a bit chattier, the lockouts are tighter and I’m on the fence as to which I prefer, as the Redline could certainly get me into trouble in town at some point if I’m not careful. The same is true with the R7, but the tighter lockouts can help though they’re far from perfect. The lockouts on the Redline overall are more consistent and I find that I get less falsing/lockouts needed with he RL with the filtering preventing a lot of them in the first place.

Ka Band

Impressive range on 34.7 testing. We took the cars out to a back road that extended 6KM+ (3.7M) and I was receiving alerts in the 6KM range with I/O shots. Not reliable on each shot, but adequate for a lengthy save. Ramp up was pretty decent to each of these alerts. This was a quick test but after wrapping up, I was rest assured that range was pretty impressive and that I/O and C/O threats on 34.7 on this test weren’t an issue an on the highway at distance.

I did encounter two legitimate I/O encounters since then. The first one was on the highway. The detector went full tilt to LEO operating 34.7 on the first one. Drove half a KM or so and there was a police car waiting at a light shooting I/O to oncoming traffic in the other direction. Must have been one of those situations where the LEO had just turned on to the highway or had just activated radar as I did not receive a peep of IO/CO while driving 10+ KM in that direction. The second encounter was right in town. Another close I/O shot, where the officer was visible to me. Full tilt on the detector as expected. No signals detected from the rear after he passed me.

K Band

Again, pretty slow here but given the impressive range, I’m still confident that the detector would perform when needed in most scenarios. I was seeing up to 3+ seconds to alert in some instances which is plain bad, though the average being quicker. In doing the same back road testing, I was alerting to trigger pulls well advance on my Bushnell and C/O was no worry so far as providing a save. I’m pretty confident that it would perform as needed against legitimate K band threats, both in town where I live and on the highway in most cases, though I sure miss the R7 reactivity at times.

I have noticed a few instances of initial threat detection to known speed signs showing full tilt ramp on the initial alert when I get close enough to the sign and when pushing through the lengthy filtering. It’s quite loud and makes me jump a bit. More time will tell as I encounter some legitimate K band threats.

MRCD

MRCD falsing is very common on the detector, to the point where I might even just turn it off and hope for a fix in future. Detection range seems to be quite good against legitimate MRCD and I hope that Escort is working to further refine the falsing that we’re seeing. It falses far more to MRCD than my R7 comparatively by a long shot. Ford trucks are an issue as others have reported. It’s my biggest complaint so far given we have legitimate MRCD here and it’s pretty annoying and borderline unusable.

Laser Detection

I couldn’t find a lot of information on laser responsiveness when looking in to the R360c and though laser scatter saves are rare and jammers are required for protection, I still like knowing when I’m being targeted by lidar in order to slow down and not continue accelerating. I’ll be installing ALP’s on this car come spring, but thought that some could find this information valuable to some.

I’m happy to report that based on my testing with a Dragon Eye and an Ultralyte, laser responsiveness on the detector is VERY good. Not only did the detector alert instantly each time from 3,000 ft (1KM) to the front to both guns, the alert held for as long as I was targeted and dropped off within a few seconds afterwards. When shooting my Ultralyte to the left and right of my vehicle while stationary from the front, I was still alerting most of the time. Rear detection was also very good. Not quite as good as the front, but pretty impressive overall even against the DE.

Here's a quick video of laser detection (DragonEye) on our last run for demonstration purposes. Shooter blurred for privacy.

Redline 360c Vs. DragonEye

Arrows

They work pretty good, though strong signals can confuse them. Both of the above mentioned Ka encounters resulted in the detector becoming pretty confused with which way the signal was coming from. Front arrows, side arrows and rear arrows all transitioned during these encounters and eventually held in the signal direction.

Anomalies

When turning off Over Speed & Over Speed Limit alerts I was still getting over speed alerts while connected to the Escort Live app. When disconnected, Over Speed would not alert when set to off, but for whatever reason the OSL would. I tried to turn on and off several times and would still receive the OSL alerts any time that I was connected to the EL app. For some reason after turning them on/off both on the detector and within the app itself a few times I was able to get them to go away, but I don’t know why or how specifically and was more of a fluke. I’ve driven for a week now without the alerts presenting while connected to EL, so for now I’m thinking that it’s sorted.

When operating the detector in KPH in the main menu on EL, the cruise alert speed still indicated MPH as the selection. I figured that I’d have to do some converting, so I set it at 20MPH (32KMH) and the detector was still alerting between 20 and 30KPH so I put two and two together and realized that when KPH is set in the main menu, the cruise alert setting is actually in KMH and not MPH, even though MPH is present in the menu. Changed my setting to 30 MPH and it works as expected to alerts slower than 30KPH. It could be helpful to update this in the menu when a user selects KPH as the desired setting.

Overall I’m pretty happy so far, mostly with the quiet experience and hoping that with future firmware updates the detector just keeps getting better from here. The reactivity is a problem for me for sure though, given we have both K & Ka band I/O in use here. If that's sorted, this detector would be my all time favorite.
 
Last edited:

Vortex

Making Videos
Observer
VIP
Lifetime Premium
Corgi Lovers
Advanced User
Joined
Jul 19, 2012
Messages
22,738
Reaction score
66,145
Location
Washington State
Great writeup! Your experience match mine as well. Thanks for taking the time to test it out a bunch and share your feedback with it. :)
 

brettzo

PSL +5
Intermediate User
Joined
Oct 22, 2012
Messages
255
Reaction score
417
Location
Alberta, Canada
Great writeup! Your experience match mine as well. Thanks for taking the time to test it out a bunch and share your feedback with it. :)
Small contribution compared to your efforts, thank you sir.
 

Vortex

Making Videos
Observer
VIP
Lifetime Premium
Corgi Lovers
Advanced User
Joined
Jul 19, 2012
Messages
22,738
Reaction score
66,145
Location
Washington State
Small contribution compared to your efforts, thank you sir.
That's how all this works. Lots of little contributions that collectively add up to a lot. The more people like you sharing their perspectives, the better! :thumbsup:
 

brettzo

PSL +5
Intermediate User
Joined
Oct 22, 2012
Messages
255
Reaction score
417
Location
Alberta, Canada
Since I did a reactivity test between the past and present FW’s on the R360C…. K band reactivity has drastically improved.

First video is FW 1.7 from April.


This is FW 1.9 from 6 days ago.

Yours seems consistently faster than mine when testing with Bushnell in highway mode with TSR and K notch off on 1.9. I saw some 1ish second alerts like yours, but was inconsistent at best. Some of my pulls were 3-4 seconds. And not just one or two, but several. The detector is sensitive to overdrive in my testing too, so I try to give it some space.
 

Rags

Tumbleweed
Advanced User
Joined
Oct 26, 2011
Messages
3,737
Reaction score
8,315
Yours seems consistently faster than mine when testing with Bushnell in highway mode with TSR and K notch off on 1.9. I saw some 1ish second alerts like yours, but was inconsistent at best. Some of my pulls were 3-4 seconds. And not just one or two, but several. The detector is sensitive to overdrive in my testing too, so I try to give it some space.
Yep, 2-3 seconds isn't uncommon with my KGE as well.

The Ka reactivity is also bottom of the barrel when compared to other detectors in its class.
 

brettzo

PSL +5
Intermediate User
Joined
Oct 22, 2012
Messages
255
Reaction score
417
Location
Alberta, Canada
Since I did a reactivity test between the past and present FW’s on the R360C…. K band reactivity has drastically improved.

First video is FW 1.7 from April.


This is FW 1.9 from 6 days ago.

Here’s an example of how slow mine can be. Most are around the 2-3 second range (or faster), but some can really lag spontaneously. Every once in a while I’ll see a 5+ second.

K Reactivity

I’ve tried to move further away from the detector to avoid overdrive and does help, but still see this random extended delay quite a bit.
 
Last edited:

BagNDrag

Lifetime Premium
Advanced User
Joined
Feb 22, 2012
Messages
887
Reaction score
3,356
I have now finally been using the Redline 360c for a couple of weeks and have had enough seat time to put it through its paces and I thought that I would share my experience so far. Overall, I’m liking it despite some concerns that I had about reactivity after doing some quick testing at home. Since then, I was able to get out and do some more practical radar and laser testing and gave me a bit more peace of mind.

The detector definitely has impressive range and the overall package is really nice. Coming from the R7 as my primary detector the Redline is sure quieter, though I still have a soft spot for the R7. It’s a great option and value at the price point. The overall quietness, filtering and auto lockouts was the reason that I wanted to try the Redline for my regular commutes. It’s already almost silent driving on my regular routes, though the detector still certainly needs some reactivity improvements and ramp up presentation. It can be pretty bad at times.

General Settings

V 1.9
Highway
K band: On
Ka band: 2/4/5/6/8
X band: Off
Laser: On
TSR: Off
K notch: Off
MRCD: On
MRCT: Off
Cruise alert: 30 KPH

Pros

Excellent range.

Great BSM filtering.

Nice design and construction. Feels solid and looks nice up on the windshield.

Escort mag mounts are really nice and helpful when transferring the detector to other vehicles.

Crisp screen and arrow presentation/visibility is very nice. Everything is easy to see during all times of the day, even with sunglasses.

Easy updates/connectivity. I don’t have WiFi in the car though when pulling into my garage or starting my vehicle I’m within close enough proximity of my home WLAN to be notified of updates and update the detector and update easily. Not having to bring it inside has been nice.

Escort Live app is nice for customizing settings on the fly.

Cons

Auto brightness doesn’t work very well as a lot of others have reported. I run the detector in the “Max” setting all of the time. Not a big deal to me, as I think that this brightness level works well for me during the day/night and in various weather environments but would be nice to see that working better.

Screen could be a bit larger, but just me pulling at straws. It’s adequate and I think that coming from the R7 is the reason it looks a bit small. It does what’s needed.

Slow reactivity in comparison to other detectors. K band can be extremely slow as I already knew going into this. Ka band segmented is borderline acceptable to me, but still pretty slow in comparison to say the R7 and many other detectors out there. I do find though that strong K band signals come through as needed & with adequate alerting time. I just wish that reactivity and ramp up was improved on and hoping that future firmware can address to put this detector on another level and be near perfect for me.

Cruise alert logic is a bit odd to me. When receiving an initial alert over the specified cruise alert limit (20MPH) and then slowing down below that threshold, any alerts previously detected while over the threshold will still alert at normal volume vs. automatically muting when falling below the cruise alert limit. Receiving these alerts above the threshold works as expected, but why not mute them automatically when falling below and then make them audible again once the limit has been exceeded? This is how I’m accustomed to using low speed muting and works much better in my opinion when driving in unfamiliar urban territory with several new false signals. I originally thought that I had an issue of some kind but found a post by Escort confirming this software logic. Not the end of the world but requires a push of the mute button in these cases.

Lifetime defender updates should be included with the R360c IMO. It’s a pretty nominal fee but feels a bit like nickel and diming given the price point of this detector.

Price is steep, especially up in Canada. $1,360 CAD retail after taxes. Add additional dollars for a blend mount, hardware, etc.

BSM’s

Coming from an R7, this detector sure is quiet. Eerily quiet at times. It’s a night and day difference for me so far vs. the R7’s K block 1 & 2 filtering on the “weak” setting. K band reactivity on the R360c is definitely very still slow in comparison so it’s kind of an apples to oranges thing for me right now, but the range should be adequate in most scenarios. Time will tell.

Auto Lockouts

Reliable and effective in most cases. Yes, Escort’s lockout algorithms tend to lean toward a quieter experience vs. extremely tight lockouts, but I find the Escort lockouts to work consistently as expected at locking out falses. My regular commute is already pretty much silent since using the detector. Lockouts can be concerning though with how wide they are. The detector automatically locked out a known signal and in testing yesterday with my Bushnell in that area, the signal from the Bushnell was being locked out, despite being pretty far off from the original locked out signal (40MHz+). I did a little test and unlocked the signal and then manually locked it out right after. The manual lockout seemed to cover a far wider range past the automatic lockout. To the point where I was locking the Bushnell out 2+ KM down the road. A bit concerning, though I don’t tend to use manual lockouts at all in where K band is in use anyway. It is nice to have though when operating the detector in areas that K band isn’t in use.

Though the R7 is a bit chattier, the lockouts are tighter and I’m on the fence as to which I prefer, as the Redline could certainly get me into trouble in town at some point if I’m not careful. The same is true with the R7, but the tighter lockouts can help though they’re far from perfect. The lockouts on the Redline overall are more consistent and I find that I get less falsing/lockouts needed with he RL with the filtering preventing a lot of them in the first place.

Ka Band

Impressive range on 34.7 testing. We took the cars out to a back road that extended 6KM+ (3.7M) and I was receiving alerts in the 6KM range with I/O shots. Not reliable on each shot, but adequate for a lengthy save. Ramp up was pretty decent to each of these alerts. This was a quick test but after wrapping up, I was rest assured that range was pretty impressive and that I/O and C/O threats on 34.7 on this test weren’t an issue an on the highway at distance.

I did encounter two legitimate I/O encounters since then. The first one was on the highway. The detector went full tilt to LEO operating 34.7 on the first one. Drove half a KM or so and there was a police car waiting at a light shooting I/O to oncoming traffic in the other direction. Must have been one of those situations where the LEO had just turned on to the highway or had just activated radar as I did not receive a peep of IO/CO while driving 10+ KM in that direction. The second encounter was right in town. Another close I/O shot, where the officer was visible to me. Full tilt on the detector as expected. No signals detected from the rear after he passed me.

K Band

Again, pretty slow here but given the impressive range, I’m still confident that the detector would perform when needed in most scenarios. I was seeing up to 3+ seconds to alert in some instances which is plain bad, though the average being quicker. In doing the same back road testing, I was alerting to trigger pulls well advance on my Bushnell and C/O was no worry so far as providing a save. I’m pretty confident that it would perform as needed against legitimate K band threats, both in town where I live and on the highway in most cases, though I sure miss the R7 reactivity at times.

I have noticed a few instances of initial threat detection to known speed signs showing full tilt ramp on the initial alert when I get close enough to the sign and when pushing through the lengthy filtering. It’s quite loud and makes me jump a bit. More time will tell as I encounter some legitimate K band threats.

MRCD

MRCD falsing is very common on the detector, to the point where I might even just turn it off and hope for a fix in future. Detection range seems to be quite good against legitimate MRCD and I hope that Escort is working to further refine the falsing that we’re seeing. It falses far more to MRCD than my R7 comparatively by a long shot. Ford trucks are an issue as others have reported. It’s my biggest complaint so far given we have legitimate MRCD here and it’s pretty annoying and borderline unusable.

Laser Detection

I couldn’t find a lot of information on laser responsiveness when looking in to the R360c and though laser scatter saves are rare and jammers are required for protection, I still like knowing when I’m being targeted by lidar in order to slow down and not continue accelerating. I’ll be installing ALP’s on this car come spring, but thought that some could find this information valuable to some.

I’m happy to report that based on my testing with a Dragon Eye and an Ultralyte, laser responsiveness on the detector is VERY good. Not only did the detector alert instantly each time from 3,000 ft (1KM) to the front to both guns, the alert held for as long as I was targeted and dropped off within a few seconds afterwards. When shooting my Ultralyte to the left and right of my vehicle while stationary from the front, I was still alerting most of the time. Rear detection was also very good. Not quite as good as the front, but pretty impressive overall even against the DE.

Here's a quick video of laser detection (DragonEye) on our last run for demonstration purposes. Shooter blurred for privacy.

Redline 360c Vs. DragonEye

Arrows

They work pretty good, though strong signals can confuse them. Both of the above mentioned Ka encounters resulted in the detector becoming pretty confused with which way the signal was coming from. Front arrows, side arrows and rear arrows all transitioned during these encounters and eventually held in the signal direction.

Anomalies

When turning off Over Speed & Over Speed Limit alerts I was still getting over speed alerts while connected to the Escort Live app. When disconnected, Over Speed would not alert when set to off, but for whatever reason the OSL would. I tried to turn on and off several times and would still receive the OSL alerts any time that I was connected to the EL app. For some reason after turning them on/off both on the detector and within the app itself a few times I was able to get them to go away, but I don’t know why or how specifically and was more of a fluke. I’ve driven for a week now without the alerts presenting while connected to EL, so for now I’m thinking that it’s sorted.

When operating the detector in KPH in the main menu on EL, the cruise alert speed still indicated MPH as the selection. I figured that I’d have to do some converting, so I set it at 20MPH (32KMH) and the detector was still alerting between 20 and 30KPH so I put two and two together and realized that when KPH is set in the main menu, the cruise alert setting is actually in KMH and not MPH, even though MPH is present in the menu. Changed my setting to 30 MPH and it works as expected to alerts slower than 30KPH. It could be helpful to update this in the menu when a user selects KPH as the desired setting.

Overall I’m pretty happy so far, mostly with the quiet experience and hoping that with future firmware updates the detector just keeps getting better from here. The reactivity is a problem for me for sure though, given we have both K & Ka band I/O in use here. If that's sorted, this detector would be my all time favorite.
Thanks for the info! Greatly appreciated.
 

Discord Server

Latest threads

Forum statistics

Threads
99,783
Messages
1,514,769
Members
25,367
Latest member
cjmackay
Top