STI R and Redline

[aa2033]

Okay, since i'm loosing my arrows from my V1 and bogey counter, i was wondering how i should run both detectors.

right now my STI R is 2 5 8, RDR on, laser off, x off in spec mode.
The redline has "multiple threats detected" alert in.. expert mode?

I've encountered 2 Ka bands and 1 K band at the same time before, and i usually encounter 2 K bands or 2 Ka bands, i'm looking for something, not to replace, but to help compensate for the loss of bogey counter.

also, will two M3 antennas interfere with each other? (redline and sti r)

[jmccam]

also, will two M3 antennas interfere with each other? (redline and sti r)

From everything I read, seen (I have run them together) and heard from Escort and others....the answer would appear to be no.

I believe CJR238 and NINE_C1 are conducting some test on this this to verify.

[nine_c1]

also, will two M3 antennas interfere with each other? (redline and sti r)

From everything I read, seen (I have run them together) and heard from Escort and others....the answer would appear to be no.

I believe CJR238 and NINE_C1 are conducting some test on this this to verify.

If I remember correctly, Riptide did run my RedLine with his STi-R during some of our tests. The numbers we achieved with the RedLine during that test were very consistent with my home bench testing of the RedLine.

Riptide........correct me if I'm wrong but I'm pretty sure we went through several strings with those two running together.

[Swamp]

If you run the Redline pointing to the rear, and the STI R forwards, you'll be able to tell where the signal is a lot better than if they both face forwards.

[nine_c1]

Okay, since i'm loosing my arrows from my V1 and bogey counter, i was wondering how i should run both detectors.

right now my STI R is 2 5 8, RDR on, laser off, x off in spec mode.
The redline has "multiple threats detected" alert in.. expert mode?

I've encountered 2 Ka bands and 1 K band at the same time before, and i usually encounter 2 K bands or 2 Ka bands, i'm looking for something, not to replace, but to help compensate for the loss of bogey counter.

also, will two M3 antennas interfere with each other? (redline and sti r)

I would certainly switch RDR off as that seemed to have the biggest impact on reducing the STi-R's reaction time. We failed to test RDR by itself but my belief is that it's the combination of Band Seg with RDR off that makes the STi-R the best performer against Quick Triggers.

I believe RDR (Radar Detector Rejection) requires a signal to be present for a minimum amount of time..........or possibly on multiple sweeps. So, even though band seg 2/5/8 cuts down the bandwidth swept by 75%, we did not see that improvement until RDR was switched off. Turning off RDR on the STi-R should not be anything like turning Ka Guard off on the V1 since your are cutting out segment 1 where most Ka falses show up.

[Riptide]

If I remember correctly, Riptide did run my RedLine with his STi-R during some of our tests. The numbers we achieved with the RedLine during that test were very consistent with my home bench testing of the RedLine.

Riptide........correct me if I'm wrong but I'm pretty sure we went through several strings with those two running together.

Yeah I remember having some issues with its oddly placed buttons and wondering why it was so godamn heavy quirks aside its an awsome detector.

If you run the Redline pointing to the rear, and the STI R forwards, you'll be able to tell where the signal is a lot better than if they both face forwards.

If you do that you'll drive yourself insane with how long false alerts last.

I would certainly switch RDR off as that seemed to have the biggest impact on reducing the STi-R's reaction time. We failed to test RDR by itself but my belief is that it's the combination of Band Seg with RDR off that makes the STi-R the best performer against Quick Triggers.

I believe RDR (Radar Detector Rejection) requires a signal to be present for a minimum amount of time..........or possibly on multiple sweeps. So, even though band seg 2/5/8 cuts down the bandwidth swept by 75%, we did not see that improvement until RDR was switched off. Turning off RDR on the STi-R should not be anything like turning Ka Guard off on the V1 since your are cutting out segment 1 where most Ka falses show up.[replacer_img]

I drove 3 hrs from VA to MD to get to the lidar meet and had about 3-4 Ka falses. All of these I knew were falses immediately due to their frequency on the spec display being ~33.7. If I had made that same trip with the V1 Ka-guard off.... well... yeah... you get the idea

[nine_c1]

If I remember correctly, Riptide did run my RedLine with his STi-R during some of our tests. The numbers we achieved with the RedLine during that test were very consistent with my home bench testing of the RedLine.

Riptide........correct me if I'm wrong but I'm pretty sure we went through several strings with those two running together.

Yeah I remember having some issues with its oddly placed buttons and wondering why it was so godamn heavy quirks aside its an awsome detector.

If you run the Redline pointing to the rear, and the STI R forwards, you'll be able to tell where the signal is a lot better than if they both face forwards.

If you do that you'll drive yourself insane with how long false alerts last.

I would certainly switch RDR off as that seemed to have the biggest impact on reducing the STi-R's reaction time. We failed to test RDR by itself but my belief is that it's the combination of Band Seg with RDR off that makes the STi-R the best performer against Quick Triggers.

I believe RDR (Radar Detector Rejection) requires a signal to be present for a minimum amount of time..........or possibly on multiple sweeps. So, even though band seg 2/5/8 cuts down the bandwidth swept by 75%, we did not see that improvement until RDR was switched off. Turning off RDR on the STi-R should not be anything like turning Ka Guard off on the V1 since your are cutting out segment 1 where most Ka falses show up.[replacer_img]

I drove 3 hrs from VA to MD to get to the lidar meet and had about 3-4 Ka falses. All of these I knew were falses immediately due to their frequency on the spec display being ~33.7. If I had made that same trip with the V1 Ka-guard off.... well... yeah... you get the idea

Ahhh........thats the beauty of Band Segmentation. Knowing this I would kill Segment 2 as well in my area since nobody in this part of New York runs MPH units. For my trips down to Jersey, it would be switched back on due to the popularity of 33.8 down there.

Drive Smarter..........I would if I could.

[kappaz]

If I remember correctly, Riptide did run my RedLine with his STi-R during some of our tests. The numbers we achieved with the RedLine during that test were very consistent with my home bench testing of the RedLine.

Riptide........correct me if I'm wrong but I'm pretty sure we went through several strings with those two running together.

Yeah I remember having some issues with its oddly placed buttons and wondering why it was so godamn heavy quirks aside its an awsome detector.

If you run the Redline pointing to the rear, and the STI R forwards, you'll be able to tell where the signal is a lot better than if they both face forwards.

If you do that you'll drive yourself insane with how long false alerts last.

I would certainly switch RDR off as that seemed to have the biggest impact on reducing the STi-R's reaction time. We failed to test RDR by itself but my belief is that it's the combination of Band Seg with RDR off that makes the STi-R the best performer against Quick Triggers.

I believe RDR (Radar Detector Rejection) requires a signal to be present for a minimum amount of time..........or possibly on multiple sweeps. So, even though band seg 2/5/8 cuts down the bandwidth swept by 75%, we did not see that improvement until RDR was switched off. Turning off RDR on the STi-R should not be anything like turning Ka Guard off on the V1 since your are cutting out segment 1 where most Ka falses show up.[replacer_img]

I drove 3 hrs from VA to MD to get to the lidar meet and had about 3-4 Ka falses. All of these I knew were falses immediately due to their frequency on the spec display being ~33.7. If I had made that same trip with the V1 Ka-guard off.... well... yeah... you get the idea

Ahhh........thats the beauty of Band Segmentation. Knowing this I would kill Segment 2 as well in my area since nobody in this part of New York runs MPH units. For my trips down to Jersey, it would be switched back on due to the popularity of 33.8 down there.

Drive Smarter..........I would if I could.

Any reason why escort doesn't incorporate band segmentation in the redline?

[nine_c1]

Any reason why escort doesn't incorporate band segmentation in the redline?

I can only assume that the brass at Escort do not see adding these options as a means of generating significant revenue. That would mean that the majority of Belscort customers (and potential customers) in the US are generally ignorant to the various aspects of how we measure a Radar Detectors performance. The few quips from SML and RadarTest in the major publications (think Car&Driver) is the #1 advertising mechanism that sells RD's. Ever notice that every add for every Belscort advertises it as "The most technically advanced" RD on the planet with the longest range.

Apparently consumers in Canada and Europe are smarter and it takes features like this to convince them to buy.

Ahhh.........I digress.........short answer, I don't have a friggin clue!

[GTO_04]

Any reason why escort doesn't incorporate band segmentation in the redline?

Ah, you beat me to it!

That would be a great set of features to add to the Redline. Knowing Escort, they would probably charge another $80 for adding them.

GTO_04