Finished: Instant On Testing w/ 13 RD's on K Band

Lars36

Banned
Banned User
Joined
Apr 15, 2021
Messages
1,157
Reaction score
3,423
Location
Ocala Fl
"Maybe I just need to buy new suction cups in bulk and throw out old ones periodically, haha"

That's what I would suggest for you to do.
When I used the suction cup mount for my V1 and always left it up on the windshield, after awhile the heat and the sun made them yucky.
 

DC Fluid

RDF Addicts Anonymous Member
Corgi Lovers
Advanced User
Joined
Jun 7, 2019
Messages
5,441
Reaction score
18,936
Age
55
Location
Prince George, B.C. Canada
For testing I only need each detector mounted for a few minutes before I swap things out. Would it be good for temporary installs like that? I'm always trying to make things as efficient as possible for testing and would prefer having to clean the WS off after each RD.

Oddly enough I've tried that too with limited success. Maybe I just need to buy new suction cups in bulk and throw out old ones periodically, haha. I guess they're great for more permanent installs, but not ideally suited to constantly mounting and dismounting.
Yes, when trying to mount for longer periods of time, some fixes can do the job.
Constant on and off, especially when making photos and videos at a artistic level of wanting clean uncluttered appearances of factory accessories, really defeats the temporary fix methods, and leaves you in the market for new high quality cups.
I noticed a big sticky cup taking a beating with my limited installs for video testing, requiring a few baths in hot soapy water to bring back the "sticky" to them.
 

daviper

Learning to Fly
Beginner User
Joined
Dec 11, 2015
Messages
55
Reaction score
43
Thank you for doing all this testing! I hope Escort addresses the responsiveness for Instant On with the RL360c in a future firmware update. I'm happy with the detector but the results you've shown do make me worried for running it.
 

Vortex

Making Videos
Observer
VIP
Lifetime Premium
Corgi Lovers
Advanced User
Joined
Jul 19, 2012
Messages
22,071
Reaction score
60,744
Location
Washington State
So quick update, still working on the final video. I’m admittedly kind of regretting taking this on, given how incredibly time consuming it is to create a video on something that I don’t think is critically important in the first place, lol.

Oh well, hopefully I’ll have the whole thing done in the next day or two and I can move on… :p

Written content is SO much faster… :)
 

Rags

Tumbleweed
Advanced User
Joined
Oct 26, 2011
Messages
2,900
Reaction score
4,740
So quick update, still working on the final video. I’m admittedly kind of regretting taking this on, given how incredibly time consuming it is to create a video on something that I don’t think is critically important in the first place, lol.

Oh well, hopefully I’ll have the whole thing done in the next day or two and I can move on… :p

Written content is SO much faster… :)
But it's hard to monetize written content shared freely on a forum.
 

westwind77

Lifetime Premium
Advanced User
Joined
Dec 7, 2016
Messages
3,690
Reaction score
8,792
something that I don’t think is critically important in the first place, lol.
I greatly appreciate your testing! Can I ask why you do not think it is critically important? Where I live we have difficult terrain and face a fair amount of K-band QT / IO - having every possible advantage over that is critical for anyone in my area (IMO).
 

Vortex

Making Videos
Observer
VIP
Lifetime Premium
Corgi Lovers
Advanced User
Joined
Jul 19, 2012
Messages
22,071
Reaction score
60,744
Location
Washington State
But it's hard to monetize written content shared freely on a forum.
That honestly never crossed my mind. I mean I could just as easily post the same testing on my website, right? I’ve just seen myself as “a YouTuber” for a while so that’s my go-to place to post. I’ve been doing some written reviews lately due to time constraints (and feeling kinda miserable lately with how long editing videos takes) and believe it or not, the written info often makes more $$ than the videos. I really love making videos though. :)
I greatly appreciate your testing! Can I ask why you do not think it is critically important? Where I live we have difficult terrain and face a fair amount of K-band QT / IO - having every possible advantage over that is critical for anyone in my area (IMO).
Outbraking IO is tough. Possible, yes, but tough.

Ideally we want every advantage possible, sure, but I’d personally rank things like sensitivity and BSM filtering higher than IO responsiveness, no?

I may be wrong though, especially since I see almost all CO here. What are your thoughts?
 
Last edited:

Rags

Tumbleweed
Advanced User
Joined
Oct 26, 2011
Messages
2,900
Reaction score
4,740
That honestly never crossed my mind. I mean I could just as easily post the same testing on my website, right? I’ve just seen myself as “a YouTuber” for a while so that’s my go-to place to post. I’ve been doing some written reviews lately due to time constraints (and feeling kinda miserable lately with how long editing videos takes lately) and believe it or not, the written info often makes more $$ than the videos. I really love making videos though. :)

Outbraking IO is tough. Possible, yes, but tough.

Ideally we want every advantage possible, but I’d personally rank things like sensitivity and BSM filtering higher than IO responsiveness.
You have a little one, your time is at an ultra premium right now. Make that premium count!
 

westwind77

Lifetime Premium
Advanced User
Joined
Dec 7, 2016
Messages
3,690
Reaction score
8,792
Outbraking IO is tough. Possible, yes, but tough.

Ideally we want every advantage possible, sure, but I’d personally rank things like sensitivity and BSM filtering higher than IO responsiveness, no?

I may be wrong though, especially since I see almost all CO here. What are your thoughts?
I 100% agree with trying to out-brake I/O. There are just too many factors involved with that situation such as LEO distance when you are hit, driving a large SUV vs small sports car, driver reaction time, etc.

My reasoning for wanting great K-band reactivity is to catch the I/O Q/T shots up ahead (around a corner, through trees, etc) where the RD might only catch say .75s or even 1s of a remaining signal from a vehicle that was targeted ahead out of my sight.

My R3 and M360 have both saved me in the above situation. Driving, not seeing a vehicle in front of me, just staring into a corner and then getting a very brief K-band alert then rounding the corner to the top of a hill where MR LEO then gives me a full shot. Looking ahead I see the other vehicle he hit prior on the straight.

These alerts that have saved me are indeed brief whiffs of what was most likely a bit longer signal but due to terrain limitations only getting a fraction, but just enough.

Given the RL360c K-band reactivity I highly doubt it would have provided saves in my prior situations.

Where I live there was only one town near me that used I/O K-band and they are brutal with it, however, now a number of other towns, including mine, are switching their methods toward I/O more these days. Having great K-band reactivity to 'see' the LEO before they see me is highly desired.
 

Vortex

Making Videos
Observer
VIP
Lifetime Premium
Corgi Lovers
Advanced User
Joined
Jul 19, 2012
Messages
22,071
Reaction score
60,744
Location
Washington State
Finally finished the full video. That took WAY longer than I anticipated, lol.

 

New Yorker

Learning to Drive
General User
Joined
Jan 18, 2021
Messages
22
Reaction score
47
Wow Vortex, no doubt everyone sure appreciates your efforts. Thanks! You bring up a good point in your summary, though; this is just one of many possible tests. Which begs the question: in real world driving, which tests are most important? Perhaps, at some point, you can discuss weighing the importance of the various tests. Where does "instant on/Ka performance" fall in the grand scheme of things? Is it as important as other measures of performance? More important? Less?? I'm a novice, and I'm not obsessive about radar and RDs; I just like to know, generally, which RDs are best, all things considered, when tests are weighted appropriately? (Or lol, maybe you've already discussed that!)
 
Last edited:

Lars36

Banned
Banned User
Joined
Apr 15, 2021
Messages
1,157
Reaction score
3,423
Location
Ocala Fl
Thanks once again for taking the time for the rest of us to make informed decisions 👍
 

OBeerWANKenobi

This is not the car you're looking for......
ModSec
VIP
Premium Plus
Lifetime Premium
Corgi Lovers
Advanced User
Joined
Mar 20, 2018
Messages
8,192
Reaction score
25,738
Location
Outer Rim - Hiding from 35.5 I/O
I 100% agree with trying to out-brake I/O. There are just too many factors involved with that situation such as LEO distance when you are hit, driving a large SUV vs small sports car, driver reaction time, etc.

My reasoning for wanting great K-band reactivity is to catch the I/O Q/T shots up ahead (around a corner, through trees, etc) where the RD might only catch say .75s or even 1s of a remaining signal from a vehicle that was targeted ahead out of my sight.

My R3 and M360 have both saved me in the above situation. Driving, not seeing a vehicle in front of me, just staring into a corner and then getting a very brief K-band alert then rounding the corner to the top of a hill where MR LEO then gives me a full shot. Looking ahead I see the other vehicle he hit prior on the straight.

These alerts that have saved me are indeed brief whiffs of what was most likely a bit longer signal but due to terrain limitations only getting a fraction, but just enough.

Given the RL360c K-band reactivity I highly doubt it would have provided saves in my prior situations.

Where I live there was only one town near me that used I/O K-band and they are brutal with it, however, now a number of other towns, including mine, are switching their methods toward I/O more these days. Having great K-band reactivity to 'see' the LEO before they see me is highly desired.
X1000
It's not about trying to outbrake I/O, it's about completely missing I/O shots up ahead of you by the vast majority of LEO that aren't going by the book. AKA, not holding down the trigger for the full 5 seconds. Though, if you ARE the target, braking at first alert against those that are getting a tracking history could help reduce the speed on your ticket or confuse them as to which car they are picking up when there's more than one around.

I have at least two videos where I'm sure that dropping anchor at first alert, along with other mitigating circumstances (traffic, terrain, obstructions, cosine error), saved me a ticket. Obviously no one can outbrake a HR on a lonely straight stretch of road with only you and the LEO on it......but I digress.

I think those that feel reactivity's not really that important probably don't face a lot of I/O. C/O, not I/O is the unicorn around me. One town is Falcon HR I/O. County is selective I/O 35.5 rolling and stationary. WSP, rolling and stationary 34.7 I/O, etc. Only two cities near me use C/O regularly and they switch it up with some I/O mixed in as well.

Conversely, I spent some time in Green Bay over Memorial day and they were all driving around with their 35.5 C/O. Somtimes I had 3 legit bogeys at once and I must admit that it actually got annoying. LOL
 

DC Fluid

RDF Addicts Anonymous Member
Corgi Lovers
Advanced User
Joined
Jun 7, 2019
Messages
5,441
Reaction score
18,936
Age
55
Location
Prince George, B.C. Canada
Wow Vortex, no doubt everyone sure appreciates your efforts. Thanks! You bring up a good point in your summary, though; this is just one of many possible tests. Which begs the question: in real world driving, which tests are most important? Perhaps, at some point, you can discuss weighing the importance of the various tests. Where does "instant on/Ka performance" fall in the grand scheme of things? Is it as important as other measures of performance? More important? Less?? I'm a novice, and I'm not obsessive about radar and RDs; I just like to know, generally, which RDs are best, all things considered, when tests are weighted appropriately? (Or lol, maybe you've already discussed that!)
IMO absolute range is king however, it must be combined with good false rejection or you lose the advantage of early warning reliability.
So regardless of any feature, false rejection must be part of the equation.
So keeping equal levels of false rejection as a baseline, range is king, I/O & reactivity/reaction times are second.
However I/O performance is an incredibly important feature too, as there are multiple scenarios that it comes into play and makes a save. Less scenarios than absolute range, but it does happen.
So if range and BSM is equal, then the faster I/O responding detector is a no brainer.
However, if one detector is slower (RL360c) than another (R7) but has say 10% more range?
Depends then on how much I/O brownstreak encounters you get in your area.
All the other features of a detector come into play when everything is not equal.

In other words, run the detector you are most comfortable with or trust the most to prevent a ticket in your driving environments.
It will be an endless debate with out a winner yet again.
But a good problem to have, deciding between several worthy detectors.
 

if6ws9

Learning to Fly
Premium Plus
Beginner User
Joined
May 30, 2013
Messages
193
Reaction score
264
Location
Florida
So quick update, still working on the final video. I’m admittedly kind of regretting taking this on, given how incredibly time consuming it is to create a video on something that I don’t think is critically important in the first place, lol.

Oh well, hopefully I’ll have the whole thing done in the next day or two and I can move on… :p

Written content is SO much faster… :)
The effort is greatly appreciated!
 

ICULookin

Road Terror- ICU watching
Premium Plus
Beginner User
Joined
Jul 31, 2018
Messages
876
Reaction score
979
Location
ATL OTP GA
Thanks Vortex for your hard work....
 

Lars36

Banned
Banned User
Joined
Apr 15, 2021
Messages
1,157
Reaction score
3,423
Location
Ocala Fl
IMO absolute range is king however, it must be combined with good false rejection or you lose the advantage of early warning reliability.
So regardless of any feature, false rejection must be part of the equation.
So keeping equal levels of false rejection as a baseline, range is king, I/O & reactivity/reaction times are second.
However I/O performance is an incredibly important feature too, as there are multiple scenarios that it comes into play and makes a save. Less scenarios than absolute range, but it does happen.
So if range and BSM is equal, then the faster I/O responding detector is a no brainer.
However, if one detector is slower (RL360c) than another (R7) but has say 10% more range?
Depends then on how much I/O brownstreak encounters you get in your area.
All the other features of a detector come into play when everything is not equal.

In other words, run the detector you are most comfortable with or trust the most to prevent a ticket in your driving environments.
It will be an endless debate with out a winner yet again.
But a good problem to have, deciding between several worthy detectors.

A great observation of the debate over the best RD.
Only one thing for me to add, I don't always just rely on my RD, basic instincts of my current situation, what road, cars around me, etc.
A lot of times it just doesn't feel right.
 
Last edited:

WildOne

PSL +5
Intermediate User
Joined
Oct 16, 2020
Messages
844
Reaction score
2,622
Location
MD
It's not about trying to outbrake I/O, it's about completely missing I/O shots up ahead of you by the vast majority of LEO that aren't going by the book. AKA, not holding down the trigger for the full 5 seconds. Though, if you ARE the target, braking at first alert against those that are getting a tracking history could help reduce the speed on your ticket or confuse them as to which car they are picking up when there's more than one around.

I have at least two videos where I'm sure that dropping anchor at first alert, along with other mitigating circumstances (traffic, terrain, obstructions, cosine error), saved me a ticket. Obviously no one can outbrake a HR on a lonely straight stretch of road with only you and the LEO on it......but I digress.

I think those that feel reactivity's not really that important probably don't face a lot of I/O. C/O, not I/O is the unicorn around me. One town is Falcon HR I/O. County is selective I/O 35.5 rolling and stationary. WSP, rolling and stationary 34.7 I/O, etc. Only two cities near me use C/O regularly and they switch it up with some I/O mixed in as well.
Exactly! If you don't experience a lot of IO from smart LEOs, then you just don't understand what IO response from the RD really buys you.
 

Noddy

Learning to Drive
General User
Joined
May 21, 2021
Messages
315
Reaction score
944
Location
Ireland
X1000
It's not about trying to outbrake I/O, it's about completely missing I/O shots up ahead of you by the vast majority of LEO that aren't going by the book. AKA, not holding down the trigger for the full 5 seconds. Though, if you ARE the target, braking at first alert against those that are getting a tracking history could help reduce the speed on your ticket or confuse them as to which car they are picking up when there's more than one around.

I have at least two videos where I'm sure that dropping anchor at first alert, along with other mitigating circumstances (traffic, terrain, obstructions, cosine error), saved me a ticket. Obviously no one can outbrake a HR on a lonely straight stretch of road with only you and the LEO on it......but I digress.

I think those that feel reactivity's not really that important probably don't face a lot of I/O. C/O, not I/O is the unicorn around me. One town is Falcon HR I/O. County is selective I/O 35.5 rolling and stationary. WSP, rolling and stationary 34.7 I/O, etc. Only two cities near me use C/O regularly and they switch it up with some I/O mixed in as well.

Conversely, I spent some time in Green Bay over Memorial day and they were all driving around with their 35.5 C/O. Somtimes I had 3 legit bogeys at once and I must admit that it actually got annoying. LOL
🤣Just looking at your name!! Put another twist on Star Wars!!
 

Discord Server

Latest threads

Forum statistics

Threads
96,578
Messages
1,469,649
Members
24,773
Latest member
downhiller2010
Top