RL360C 1.8 Big 3 Shootout Part 2 K Band, 33.8, 34.7

Rags

Tumbleweed
Advanced User
Joined
Oct 26, 2011
Messages
2,892
Reaction score
4,712
This is part 2 to this thread: https://www.rdforum.org/threads/110405/

I had time to finish up testing of the 33.8 and 34.7, in addition @Brainstorm69 indicated I should have been testing the RL360C with TSR off, so I re-ran K band tests again today with both TSR on and off with the RL360C in addition to running the other detectors again (to eliminate set up to set up variance).


The K source is a Kustom Golden Eagle with a K band antenna measured at 24.144 Ghz

The 33.8 source is a MPH Python II fs with a 33.8 antenna measured at 33.789 Ghz

The 34.7 source is a Stalker Dual with a 34.7 antenna measured at 34.691 Ghz

The settings are as follows:

For Ka:

RL360C and R7: Highway, Ka Narrow 2,4,5,6,8
V1G2: All bogeys mode, no custom frequencies

K Settings:

RL360C:
K wide
K notch On
TSR On
MRCD Off

R7:
K Wide
K Block 1 Weak
K Block 2 Weak
K Filter On
MRCD On
TSF on

V1G2:
K Verifier On


The longest detections were near this pin drop on the map:
Hat 6 Long Range.jpg


The second longest detections were near this pin drop on the map:

Hat 6 V1G2 2nd detection.jpg


The 3rd longest detections were at this pin drop on the map:

Hat 6 V1G2 3rd detection.jpg


Here is the approximate location where constant alerting going towards the source were clustered:

Hat 6 Constant Detection Cluster.jpg


Here are the results that will go with the above maps:

K band:

Hat 6 K Long Range.jpg

As you can see, the Redline 360C was the only detector to alert at the longest distance cluster this go around. It also alerted at the 2nd and 3rd points. It did this with both TSR on and Off. The V1G2 was able to alert at the second location 2 out of 3 times, the R7 never was able to.

They were all silent after the 3rd detection point until nearing the source where they then would alert constantly up to the source. The constant detection location results looked like this:

Hat 6 K Constant 2.jpg



Running the other direction from behind the source (forward facing detection):


Hat 6 K FF 2.jpg


33.8 results:

Longest detections:

Hat 6 33.8 Longest.jpg


All would quickly lose the signal, then pick up the signal at different distances later on, these are averages of 3 runs:

Hat 6 33.8 Multiple.jpg


Again, FF results for 33.8:

Hat 6 33.8 FF.jpg


Finally, here's the 34.7 results:

Longest detections:

Hat 6 34.7 Longest.jpg


Again, all would lose the signal quickly then pick it back up at different distances, these are the average of 3 runs:

Hat 6 34.7 Multiple Detections.jpg


Lastly, Forward Facing 34.7:

Hat 6 34.7 FF.jpg


During testing, I noted some odd behavior:

The RL360C when passing the K band antenna, the arrows would transition, but when flipping from front to back, the sound from the detector would stop, then start again but would take a second or two for the audible sound to match the level meter on the detector. It only did this with K band, on Ka it seemed somewhat normal.

The R7 would report up to 3 bogeys on the 34.7 antenna when getting near it. The RL360C and V1G2 only reported 1 bogey for all tests. The R7 reported 1 bogey on K and 33.8.

It looks like the RL360C is a very strong performer on K band distance, if Escort and Valentine get the K band reaction times fixed, they would both have the top detectors with regards to K performance.

The newest firmware does, indeed, seem to have improved Ka performance a bit, but it still doesn't seem to be as good as the V1G2 overall...but both are really very close in reality. My R7 has great performance as well, but it doesn't seem to be as strong overall as the other 2.

Of course, this is just 1 sampling of these detectors, so your results may vary :)
 

Vortex

Making Videos
Observer
VIP
Lifetime Premium
Corgi Lovers
Advanced User
Joined
Jul 19, 2012
Messages
22,058
Reaction score
60,657
Location
Washington State
Wow, thanks for the testing! Great showing by the RL360c and V1, despite some of the quirks. Interesting to see the R7 lag behind the competition like that...
 

Rags

Tumbleweed
Advanced User
Joined
Oct 26, 2011
Messages
2,892
Reaction score
4,712
Wow, thanks for the testing! Great showing by the RL360c and V1, despite some of the quirks. Interesting to see the R7 lag behind the competition like that...
It may just be the course I run, but the R7 seems to struggle with off axis and forward facing when compared to the other 2. I've been putting on a lot of miles on the RL360C and R7 the last few weeks and these results seem to somewhat reflect what I have seen as well on Ka, but I wasn't expecting this large of a difference.

I should be able to do some extreme distance testing in the next couple of weeks to see if this translates to on axis long range too.
 
Last edited:

westwind77

Lifetime Premium
Advanced User
Joined
Dec 7, 2016
Messages
3,684
Reaction score
8,770
It looks like the RL360C is a very strong performer on K band distance, if Escort and Valentine get the K band reaction times fixed, they would both have the top detectors with regards to K performance.

Thank you for taking your valuable time and testing, and for the thorough write up that goes along with it all!

The RL360c is so close to being the top RD, just crossing my fingers they can turn around the worsening K-band reactivity.

The G2 really is an amazing RD on Ka, noting seems to be able to slip by it!
 

Rags

Tumbleweed
Advanced User
Joined
Oct 26, 2011
Messages
2,892
Reaction score
4,712
I would be very curious to see an r1/3 on 1.53/54 with its better off axis on this course. Thanks for the testing.
Stay tuned. It's coming. There are a couple of surprises for other detectors and tests too.
Post automatically merged:

 
Last edited:

Kennyc56

Ford Lover-I/O hater!
Premium Plus
Lifetime Premium
Advanced User
Joined
Feb 22, 2018
Messages
5,507
Reaction score
21,046
Location
I/O Hell, Aka Eastern N.C.
Great job @Rags ! Great testing just like always from you! I can't wait to see what you come up with next! Like we all keep saying, If VR figures out K band look out! Our testing shows the same results with the R7. Off axis and forward facing Ka alerts are where the V1G2 really pulls ahead.
 
Last edited:

DC Fluid

RDF Addicts Anonymous Member
Corgi Lovers
Advanced User
Joined
Jun 7, 2019
Messages
5,420
Reaction score
18,838
Age
55
Location
Prince George, B.C. Canada
I noticed in my tests of F133 vs F135, the R7 takes a hit on range with TSF on, and again with K Filter on. Filters off the two firmwares were pretty equal.
So the price of quieter BSM filtering was outright range in testing. Even though they made reactivity better.
Strong performance out of the others too.
I'm finding the Redline more chatty than the R7, and MRCD falsing too much.
 

Rags

Tumbleweed
Advanced User
Joined
Oct 26, 2011
Messages
2,892
Reaction score
4,712
I noticed in my tests of F133 vs F135, the R7 takes a hit on range with TSF on, and again with K Filter on. Filters off the two firmwares were pretty equal.
So the price of quieter BSM filtering was outright range in testing. Even though they made reactivity better.
Strong performance out of the others too.
I'm finding the Redline more chatty than the R7, and MRCD falsing too much.
Yeah, I bet it does affect range, but on my R7 I can't run with it off. I would throw the thing out the window.

It's akin to k verifier off adding range on the V1G2, it does but it's not realistic to run with it off.

Do you need MRCD turned on with the RL360C?
 

DC Fluid

RDF Addicts Anonymous Member
Corgi Lovers
Advanced User
Joined
Jun 7, 2019
Messages
5,420
Reaction score
18,838
Age
55
Location
Prince George, B.C. Canada
Yeah, I bet it does affect range, but on my R7 I can't run with it off. I would throw the thing out the window.

It's akin to k verifier off adding range on the V1G2, it does but it's not realistic to run with it off.

Do you need MRCD turned on with the RL360C?
Right now, yes, northern Alberta.
 

Rags

Tumbleweed
Advanced User
Joined
Oct 26, 2011
Messages
2,892
Reaction score
4,712
Right now, yes, northern Alberta.
So you can't run the R7 with 1.35 either, correct? It's my understanding that the R7 doesn't reliably detect it with that firmware. I don't know that the RL360C 1.8 firmware has been tested against it yet either.
 

elantra04

Learning to Fly
Beginner User
Joined
Aug 16, 2012
Messages
646
Reaction score
917
Thank you for taking your valuable time and testing, and for the thorough write up that goes along with it all!

The RL360c is so close to being the top RD, just crossing my fingers they can turn around the worsening K-band reactivity.

The G2 really is an amazing RD on Ka, noting seems to be able to slip by it!
Hopefully by the time escort ever figures out a way to best the G2, Theia will be out and escort won’t matter anymore (in my mind they don’t already).
 

DC Fluid

RDF Addicts Anonymous Member
Corgi Lovers
Advanced User
Joined
Jun 7, 2019
Messages
5,420
Reaction score
18,838
Age
55
Location
Prince George, B.C. Canada
So you can't run the R7 with 1.35 either, correct? It's my understanding that the R7 doesn't reliably detect it with that firmware. I don't know that the RL360C 1.8 firmware has been tested against it yet either.
There was unverified reports of some MRCT cameras not alerting as well, but actual MRCD I believe it to still work well until a head to head test appears.
R7 can run MRCD full time with zero falses for me on 133 and 135.

Just today, Redline falsed MRCD 3 times on two 8 minute commutes, with minimal traffic and no F Series in sight.
Multiple sources cause falses. Even some transport trucks head on MR alerts.
Defender Database is on crack too, warning nearly every intersection here, cameras or not.
To the point of wanting to turn off camera alerts and rely on HR only.
When arriving at lodgings tonight, I put away the RL360, and put up R7.
Time to test out 135 in the new city, and Mithheru database for this week and see who comes out on top.
 

WildOne

PSL +5
Intermediate User
Joined
Oct 16, 2020
Messages
840
Reaction score
2,608
Location
MD
There was unverified reports of some MRCT cameras not alerting as well, but actual MRCD I believe it to still work well until a head to head test appears.
R7 can run MRCD full time with zero falses for me on 133 and 135.
I have some MRCD(T) around here too. I'm still not really sure the visual difference between the two. I have seen one at a traffic light not alert from time to time, but I think they have been turned off due to the stage of the intersection. I would pass it in both directions and it would detect at appropriate ranges. The V1G2 would actually detect K band when very close both times. Then I would go back for a third pass, but I would not have any detections from either detector. Back for a 4th time and it was like the first two.

I have seen a similar on/off at another intersection. I don't think it is the R7, as the V1G2 agrees all the time.

The detection ranges that I have had have all been very good. I have also not had any falses on 135.

I do have the GPS speed camera alert turned off though. It is just toooo annoying when it tells you to slow down when there is no camera there or your 1 MPH over! I just rely on JBV1 to alert me to those.
Post automatically merged:

Oh, but it would be nice to have a signal level to go with the MRCD alert....
 

DC Fluid

RDF Addicts Anonymous Member
Corgi Lovers
Advanced User
Joined
Jun 7, 2019
Messages
5,420
Reaction score
18,838
Age
55
Location
Prince George, B.C. Canada
I have some MRCD(T) around here too. I'm still not really sure the visual difference between the two. I have seen one at a traffic light not alert from time to time, but I think they have been turned off due to the stage of the intersection. I would pass it in both directions and it would detect at appropriate ranges. The V1G2 would actually detect K band when very close both times. Then I would go back for a third pass, but I would not have any detections from either detector. Back for a 4th time and it was like the first two.

I have seen a similar on/off at another intersection. I don't think it is the R7, as the V1G2 agrees all the time.

The detection ranges that I have had have all been very good. I have also not had any falses on 135.

I do have the GPS speed camera alert turned off though. It is just toooo annoying when it tells you to slow down when there is no camera there or your 1 MPH over! I just rely on JBV1 to alert me to those.
Post automatically merged:

Oh, but it would be nice to have a signal level to go with the MRCD alert....
Oh, but it would be nice to have a signal level to go with the MRCD alert

And arrows for MRCD.
 

Discord Server

Latest threads

Forum statistics

Threads
96,507
Messages
1,468,763
Members
24,747
Latest member
ronjhoser
Top