detection cr97

InsipidMonkey

Premium Monkey
Advanced User
Premium Member
Joined
Mar 22, 2017
Messages
6,129
Reaction score
12,902
Location
New England
For a straight, flat, open road like that I would've hoped for a little better, especially on 34.7.

Where was the cop in the second detection?
 

gbriggs82

PSL +5
Intermediate User
Joined
Aug 24, 2015
Messages
278
Reaction score
229
Not sure
For a straight, flat, open road like that I would've hoped for a little better, especially on 34.7.

Where was the cop in the second detection?
not sure now that one I believe that detection was farther because the cop I believe was on the other side of the highway @Brainstorm69 knows that area pretty well also I was Hesitant hesitant to keep driving to see but I was heading to work
 

Brainstorm69

TXCTG 2016 MOTY
Advanced User
Lifetime Premium Member
Joined
May 23, 2015
Messages
9,616
Reaction score
20,751
Location
Lone Star State
I'd estimate it at a little over half a mile, but he was pretty far off axis before that.

111350
 
Last edited:

Marty K

Always Driving Vigilantly
Intermediate User
Premium Member
Joined
Nov 27, 2018
Messages
485
Reaction score
1,072
Location
Missouri
@gbriggs82,
What are your settings? Do you have TFSR ON or OFF. If it's ON, it really impacts the CR97's performance (range and sensitivity). It should not affect Ka band, but it does. Also, what is your Ka setting? norm, norm ID, max, or maxID? Filter level of Ka band?

The second detection in my opinion was a false - misidentified BSM, most likely from that BMW or Honda on the traffic signal. Many CR97 users (including myself) have experienced this bug, where the K band BSM is displayed as Ka band alert with no frequency. You had full signal most of that alert, but never got a frequency ID. I have also had a case twice already where a strong signal from BSM will overdrive my detector, and will start alerting to Ka with no ID full signal for as long as you let it go. I had to power-cycle it to stop the alert. In both cases, there were no LEOs around.

There are also times where a BSM alert will be displayed as Ka 33.8 or 33.5. In such cases, if you are close enough to the source (an long enough around it), it will eventually switch to K band alert.
 

gbriggs82

PSL +5
Intermediate User
Joined
Aug 24, 2015
Messages
278
Reaction score
229
@gbriggs82,
What are your settings? Do you have TFSR ON or OFF. If it's ON, it really impacts the CR97's performance (range and sensitivity). It should not affect Ka band, but it does. Also, what is your Ka setting? norm, norm ID, max, or maxID? Filter level of Ka band?

The second detection in my opinion was a false - misidentified BSM, most likely from that BMW or Honda on the traffic signal. Many CR97 users (including myself) have experienced this bug, where the K band BSM is displayed as Ka band alert with no frequency. You had full signal most of that alert, but never got a frequency ID. I have also had a case twice already where a strong signal from BSM will overdrive my detector, and will start alerting to Ka with no ID full signal for as long as you let it go. I had to power-cycle it to stop the alert. In both cases, there were no LEOs around.

There are also times where a BSM alert will be displayed as Ka 33.8 or 33.5. In such cases, if you are close enough to the source (an long enough around it), it will eventually switch to K band alert.
Maxid tfsr off k band filter 2 Ka filter 1
 

Marty K

Always Driving Vigilantly
Intermediate User
Premium Member
Joined
Nov 27, 2018
Messages
485
Reaction score
1,072
Location
Missouri
Maxid tfsr off k band filter 2 Ka filter 1
Almost same as mine (I just have XK filter 3, and FDSr ON).
I watched your video few more times. Initially I was more agree with @InsipidMonkey in regards to the "short" range (I thought maybe TFSR is to blame). But now I would say that this was a pretty good detection, and definitely a safe if you were over the PSL. At the initial alert, there were no oncoming headlights as far as I could see ahead. So the LEO was then still behind that slight bend, and maybe lower (I saw that dip at the curve later on). The terrain did not help much either - no big buildings aside you to reflect; and the trees in the median were a disadvantage too. So definitely a good encounter. I still think the 2nd alert was a false, as I described earlier.

Yesterday, I had a good 34.7 detection around a curve and a dip, range was about 0.3 miles (see here: CR95/CR97 - Configuration Settings Discussion, post #245) - but the buildings to the right made it possible.
 
Last edited:

gbriggs82

PSL +5
Intermediate User
Joined
Aug 24, 2015
Messages
278
Reaction score
229
Corr
Almost same as mine (I just have XK filter 3, and FDSr ON).
I watched your video few more times. Initially I was more agree with @InsipidMonkey in regards to the "short" range (I thought maybe TFSR is to blame). But now I would say that this was a pretty good detection, and definitely a safe if you were over the PSL. At the initial alert, there were no oncoming headlights as far as I could see ahead. So the LEO was then still behind that slight bend, and maybe lower (I saw that dip at the curve later on). The terrain did not help much either - no big buildings aside you to reflect; and the trees in the median were a disadvantage too. So definitely a good encounter. I still think the 2nd alert was a false, as I described earlier.

Yesterday, I had a good 34.7 detection around a curve and a dip, range was about 0.3 miles (see here: CR95/CR97 - Configuration Settings Discussion, post #245) - but the buildings to the right made it possible.
[/QUOTE correction tfsr was on I swore I turned it off I just seen it powering it on go figured
 

Kennyc56

Ford Lover-I/O hater!
Advanced User
Lifetime Premium Member
Joined
Feb 22, 2018
Messages
2,987
Reaction score
7,669
Location
I/O Hell, Aka Eastern N.C.
No matter what, I always end up with TFSR off, Ka filter at 0 or 1, K filter at 1 or 2 and yes, FDSr### on as well! I can't help myself!
 
Last edited:

RoadDogg

PSL +5
Intermediate User
Lifetime Premium Member
Joined
May 10, 2018
Messages
550
Reaction score
1,211
Location
Tennessee
No matter what, I always end up with TFSR off, Ka filter at 0 or 1, K filter at 1 or 2 and yes, FDSr### on as well! I can't help myself!
You going back to running FDSr on? I thought you were having false alarm issues with FDSr on? I cannot run FDSr on in my CR97. It changes the “personality” of my CR97 from pleasant to just down right annoying...lol.


Sent from my iPhone using Tapatalk
 

Bossdad71

Advanced User
Premium Member
Joined
Jul 11, 2016
Messages
7,208
Reaction score
10,262
Location
Kansas running with the pack
You going back to running FDSr on? I thought you were having false alarm issues with FDSr on? I cannot run FDSr on in my CR97. It changes the “personality” of my CR97 from pleasant to just down right annoying...lol.


Sent from my iPhone using Tapatalk
Mike b told me the FRSR is more about information than range
 

Kennyc56

Ford Lover-I/O hater!
Advanced User
Lifetime Premium Member
Joined
Feb 22, 2018
Messages
2,987
Reaction score
7,669
Location
I/O Hell, Aka Eastern N.C.
You going back to running FDSr on? I thought you were having false alarm issues with FDSr on? I cannot run FDSr on in my CR97. It changes the “personality” of my CR97 from pleasant to just down right annoying...lol.


Sent from my iPhone using Tapatalk
It changes all kinds of things, all in ways I don't like! It cuts Ka range and quickness as soon as you turn it off. I can't deal with either one! TFSR does the same thing by turning it on, even though it's not supposed too. If it comes down to it, I'll always deal with the false alerts before I'll give up even one inch of range, especially on ANY Ka band!
 

NOTKTS

Learning to Fly
Beginner User
Joined
Oct 30, 2018
Messages
98
Reaction score
218
Location
Long Island/NY
Me too! After experimenting every which way for a few weeks it's TFSR off, filters at 1 or 2 each, and FDSr on. (Maybe we should call it "Kennyc56mode"?) I run in city so it just double beeps. If that starts bothering me, it's volume level to zero time. I feel safe this way. No guessing if I numbed it down with filtering. The FDSr seems to 'push' the bsm ka's back to k. I'm not sure but I recall reading that FDSr may prevent the 97's (and 95's) from from locking onto an alert in the presence of another.
 

RoadDogg

PSL +5
Intermediate User
Lifetime Premium Member
Joined
May 10, 2018
Messages
550
Reaction score
1,211
Location
Tennessee
Mike b told me the FRSR is more about information than range
I am ok with the FDSr as long as I can keep it off...lol. It probably does give a lot of information, but when I have it on, My CR97 is going off all of the time with false alarms, I just ignore it. In the real world on the interstate (in my experience), I have no idea how FDSr on or off affects range as when I have encountered real police radar with my CR97 with FDSr on, it falses so much, I don’t know when the false alarm stops and the real police radar detection begins. My CR97 is a very pleasant radar detector to use when FDSr is off. I really thought that FDSr would be a useful feature for me when I bought the CR97, but I don’t like it. That is the beauty of a programmable detector like the CR97. Choose to use, disable, or modify the settings to customize what works for you. I have gotten to the point where I enjoy using my CR97 with my “normal” settings of both X/K and Ka filters on 1, FDSr/FDSR off, and TFSR on. Sometimes I try TFSR off, but I seem to get a few more false alarms with TFSR off. I have figured out the CR97’s quirks, and I am ok with them, but I certainly wouldn’t be opposed to a firmware fix to the K / Ka issue.


Sent from my iPhone using Tapatalk
 

Marty K

Always Driving Vigilantly
Intermediate User
Premium Member
Joined
Nov 27, 2018
Messages
485
Reaction score
1,072
Location
Missouri
No matter what, I always end up with TFSR off, Ka filter at 0 or 1, K filter at 1 or 2 and yes, FDSr### on as well! I can't help myself!
@Kennyc56, that's how I run mine as well. It's the only way to get the best out of it, just comes with a "price" to pay (the darn falses and the darn band mis-identifications)...
Post automatically merged:
Mike b told me the FRSR is more about information than range
@Bossdad71, I run FDSr ON exactly for that reason - as a confirmation that the eventual Ka false is indeed a false. A brief Ka alert with no ID could very well be a distant I/O. So If I don't get a K #### alert within few seconds, then I know the generic Ka was a real source. With FDSr OFF, I can't confirm this. Ad it's only because of the K/Ka mis-identification bug.
Post automatically merged:
You going back to running FDSr on? I thought you were having false alarm issues with FDSr on? I cannot run FDSr on in my CR97. It changes the “personality” of my CR97 from pleasant to just down right annoying...lol.


Sent from my iPhone using Tapatalk
@RoadDogg, I understand your problem when running FDSr ON. It all depends on the environment you drive in. With heavy traffic on major interstates and many semi trucks, this feature being ON will just be absolutely annoying. But when driving mostly in rural areas with totally different kind of traffic (almost no semi trucks), then FDSr ON is acceptable...
 
Last edited:

Kennyc56

Ford Lover-I/O hater!
Advanced User
Lifetime Premium Member
Joined
Feb 22, 2018
Messages
2,987
Reaction score
7,669
Location
I/O Hell, Aka Eastern N.C.
I am ok with the FDSr as long as I can keep it off...lol. It probably does give a lot of information, but when I have it on, My CR97 is going off all of the time with false alarms, I just ignore it. In the real world on the interstate (in my experience), I have no idea how FDSr on or off affects range as when I have encountered real police radar with my CR97 with FDSr on, it falses so much, I don’t know when the false alarm stops and the real police radar detection begins. My CR97 is a very pleasant radar detector to use when FDSr is off. I really thought that FDSr would be a useful feature for me when I bought the CR97, but I don’t like it. That is the beauty of a programmable detector like the CR97. Choose to use, disable, or modify the settings to customize what works for you. I have gotten to the point where I enjoy using my CR97 with my “normal” settings of both X/K and Ka filters on 1, FDSr/FDSR off, and TFSR on. Sometimes I try TFSR off, but I seem to get a few more false alarms with TFSR off. I have figured out the CR97’s quirks, and I am ok with them, but I certainly wouldn’t be opposed to a firmware fix to the K / Ka issue.


Sent from my iPhone using Tapatalk
I agree with you! Problem is I'm not "normal'! I can't stand to run a detector. ANY detector for more than a few minutes knowing It's not running wide open! FDSr really is supposed to be for info only, but as all of us who have tried to turn it off know, it does more than that! It cut a mile of distance off of my CR95 when @VariableWave and I tested it awhile back with it turned off. It also slows it's reflexes against Q/T and I/O shots . I'd rather deal with the falses than get popped with I/O and not have the best protection! When it gets to be too much, I just flip my 3-way toggle switch and turn the CR97 off and fire my R1 up!
 
Last edited:

Marty K

Always Driving Vigilantly
Intermediate User
Premium Member
Joined
Nov 27, 2018
Messages
485
Reaction score
1,072
Location
Missouri
K/Ka mix up is the only real issue here. If that is to be fixed, we are golden. Most likely though, it is not possible to fix with via firmware update. I suspect the nature of the design is at fault. In order to have such a quick reactivity the hard-coded approach is to scan for X/K/Ka in one round (except 34.7), which is the case here. So there is the design limit of fixing that.
If I am wrong, then the "cost" of fixing it (scan the bands independently) will be slower reactivity, as it will take longer to scan and positively confirm the source frequency. The real question is how much of a delay (reduction in range) will that cause, and it if is practical to do so???
 

Kennyc56

Ford Lover-I/O hater!
Advanced User
Lifetime Premium Member
Joined
Feb 22, 2018
Messages
2,987
Reaction score
7,669
Location
I/O Hell, Aka Eastern N.C.
K/Ka mix up is the only real issue here. If that is to be fixed, we are golden. Most likely though, it is not possible to fix with via firmware update. I suspect the nature of the design is at fault. In order to have such a quick reactivity the hard-coded approach is to scan for X/K/Ka in one round (except 34.7), which is the case here. So there is the design limit of fixing that.
If I am wrong, then the "cost" of fixing it (scan the bands independently) will be slower reactivity, as it will take longer to scan and positively confirm the source frequency. The real question is how much of a delay (reduction in range) will that cause, and it if is practical to do so???
All damn good questions! All I know is this, I own the best detectors that have ever been built. 2 R1's, a Redline, V1, a RX65. and several older whistlers. If they would just fix this damn Ka /K band mixup BS, the CR97 would be my favorite one of the bunch! Throw in a little more off axis and this thing would be a full on monster!
 

Discord Server

Latest threads

Forum statistics

Threads
79,965
Messages
1,216,689
Members
20,243
Latest member
abseis
Top