Cr 97 K/KA band BSM confusion (1 Viewer)

yellowtibby

Shifter ZR4's number one fan.
Intermediate User
Joined
Dec 15, 2011
Messages
362
Reaction score
169
Location
Idaho and Connecticut
Does anybody know if there is an actual solution to the CR97's constant confusion of K band BSM being reported as 33.8 Ka Band? My unit has decent BSM filtering with TFSR on but will always alert as Ka Band 33.8 to all Honda and Acura BSMs. The problem is, here in Idaho, the state police all run 33.8 Ka band radar so it's a real pain in the butt when I get a 33.8 alert since I can't tell if it's a BSM or a statie up ahead. It doesn't help that everyone around here seems to own the new CRV. It's driving me nuts! I called whistler's customer service reps and they basically shrug it off. Anyone actually know if Mike B is aware of this problem? I was hoping they would release a firmware update to fix this on the CR97, but the last update was over 6 months ago with version 2.1 and I don't see any other firmware updates that are scheduled. This is pretty frustrating.
 

Kennyc56

Ford Lover, I/O Hater!
Advanced User
Lifetime Premium Member
Joined
Feb 22, 2018
Messages
2,492
Reaction score
6,003
Location
Eastern North Carolina
Does anybody know if there is an actual solution to the CR97's constant confusion of K band BSM being reported as 33.8 Ka Band? My unit has decent BSM filtering with TFSR on but will always alert as Ka Band 33.8 to all Honda and Acura BSMs. The problem is, here in Idaho, the state police all run 33.8 Ka band radar so it's a real pain in the butt when I get a 33.8 alert since I can't tell if it's a BSM or a statie up ahead. It doesn't help that everyone around here seems to own the new CRV. It's driving me nuts! I called whistler's customer service reps and they basically shrug it off. Anyone actually know if Mike B is aware of this problem? I was hoping they would release a firmware update to fix this on the CR97, but the last update was over 6 months ago with version 2.1 and I don't see any other firmware updates that are scheduled. This is pretty frustrating.
If you go back and read the Whistler threads you'll see how hard some of us have tried to get a fix for this problem! We have even got @Bossdad71 to speak directly to Mike Batten, the head engineer for Whistler about this issue, but nothing whatsoever has been done about it. It's a damn shame too because if they could do something to fix these glitches the CR95 and 97 would be great detectors, especially in their price range! I'm going to keep my 95 and 97 just in case the sky falls and a miracle happens and they fix this bs, but I'm not holding my breath!
 

yellowtibby

Shifter ZR4's number one fan.
Intermediate User
Joined
Dec 15, 2011
Messages
362
Reaction score
169
Location
Idaho and Connecticut
I'm glad someone talked to him, there appears to be no solution then. I agree, I love how reactive CR97 is, and it has good range and awesome laser sensitivity, but the band confusion is maddening. The strange thing is my CR 85 never has band confusion and has even better BSM filtering with TFSR on, it never alerts to hondas and acuras, but I heard that the CR 88/93 has band confusion with K/Ka band mix up as well. I wonder if it has to do with the FSDR feature since my CR 85 does not have it but the CR88/93/97 does.
 

radarguy1986

PSL +5
Intermediate User
Joined
Feb 23, 2017
Messages
868
Reaction score
659
Location
IL
I wonder if mike b adds band segmentation feature would it help with the confusion?

Sent from my SM-J727P using Tapatalk
 

Kennyc56

Ford Lover, I/O Hater!
Advanced User
Lifetime Premium Member
Joined
Feb 22, 2018
Messages
2,492
Reaction score
6,003
Location
Eastern North Carolina
I wonder if mike b adds band segmentation feature would it help with the confusion?

Sent from my SM-J727P using Tapatalk
It never hurts to dream I guess! It's not a segmentation related problem, although segging these Whistlers would make killers out of them! If they see more than one K band signal at a time that are just a smidge different somehow it thinks the multiple k band signals are an off the wall Ka signal. I can shoot my CR 95 or 97 all day with 24.150 with my K band gun and it sees only K band. Out on the road however, it will see 2 different BSM K signals and go crazy with Ka falses!
 
Last edited:

NOTKTS

Learning to Fly
Beginner User
Joined
Oct 30, 2018
Messages
75
Reaction score
176
Location
Long Island/NY
I have just put my CR97 back on the windshield. I am back to experimenting. I am now trying xk at 0 and ka at 1 with TFSR on but FDSR off. I am thinking delaying k may be causing the mixup. Interesting about the CR85 vs the FDSR in the later units. Is the CR85 significantly less sensitive than the CR95/97 in the real world?
 

Kennyc56

Ford Lover, I/O Hater!
Advanced User
Lifetime Premium Member
Joined
Feb 22, 2018
Messages
2,492
Reaction score
6,003
Location
Eastern North Carolina
I have just put my CR97 back on the windshield. I am back to experimenting. I am now trying xk at 0 and ka at 1 with TFSR on but FDSR off. I am thinking delaying k may be causing the mixup. Interesting about the CR85 vs the FDSR in the later units. Is the CR85 significantly less sensitive than the CR95/97 in the real world?
Yes! My CR85 gets about half the range that my CR95 and 97 do. It's no contest!
 

NOTKTS

Learning to Fly
Beginner User
Joined
Oct 30, 2018
Messages
75
Reaction score
176
Location
Long Island/NY
Yes! My CR85 gets about half the range that my CR95 and 97 do. It's no contest!
Thanks, the 97 is in a different league than my old XTR538 also. I really hope they can fix this, although its not looking like that's going to happen soon. I will try the 97 tomorrow with xk at 0. I don't think I ever did.
 

RoadDogg

Lifetime RDF Contributor
Intermediate User
Lifetime Premium Member
Joined
May 10, 2018
Messages
438
Reaction score
895
Location
Tennessee
Does anybody know if there is an actual solution to the CR97's constant confusion of K band BSM being reported as 33.8 Ka Band? My unit has decent BSM filtering with TFSR on but will always alert as Ka Band 33.8 to all Honda and Acura BSMs. The problem is, here in Idaho, the state police all run 33.8 Ka band radar so it's a real pain in the butt when I get a 33.8 alert since I can't tell if it's a BSM or a statie up ahead. It doesn't help that everyone around here seems to own the new CRV. It's driving me nuts! I called whistler's customer service reps and they basically shrug it off. Anyone actually know if Mike B is aware of this problem? I was hoping they would release a firmware update to fix this on the CR97, but the last update was over 6 months ago with version 2.1 and I don't see any other firmware updates that are scheduled. This is pretty frustrating.
I agree it is frustrating. I am fortunate that I don’t have any real police 33.8 used in my immediate area because my CR97 frequently gives me a 33.8 Ka warning for Honda and Acura BSMs whether TFSR is on or off. The first time I encountered real 33.8 police radar about two hours away from where I live with my CR97, I started looking around for a Honda or Acura, and then I realized it was the real deal. I was in a 30mph zone, and I am glad I wasn’t speeding through this unfamiliar town, because that K/Ka glitch could have caused me to ignore the CR97 and get a ticket. I know since you see a lot of real 33.8, it has to be challenging to figure out if the 33.8 signal is a LEO or Honda/Acura BSM.

I am hopeful they will introduce a firmware update for the CR97 to address some of the issues that we are experiencing, but I am not expecting any significant firmware updates. There may be a hardware problem with the CR95/CR97 that prevents the K/Ka mix up from being fixed. I have figured that Whistler has abandoned/given up on the CR95/CR97 platform, but I hope I am wrong. The CR97 does have potential.

I still run my CR97 some as I spent $249 on it, and I need to try to feel as if I am getting something for that money spent. I have gotten some saves with my CR97 so all is not lost...lol.

I have been running TFSR off a lot lately, and I have been having a problem (as I have had before with it on) with my CR97 “latching” on to K-band signal, it keeps alerting long after I have passed the signal. I normally have to unplug or power cycle the CR97 to get it quiet again. I haven’t called Whistler in a long time because early on when I called about the K/Ka mixup, they shrugged it off as you said and said that was “normal”.

I have tried so many filtering combinations trying to get that “ideal” balance between radar detection performance with minimal false alarms. I like running it with TFSR on as it helps with the false alarms, but I think TFSR on also impacts radar detection range and performance. I am still trying to figure out my CR97, and I have recently thought about sending it in to Whistler to check it out before my warranty expires, but I don’t think that would make any difference in my CR97’s performance. I think my CR97 is performing in a similar manner as others on the RDF, so I don’t think sending it to Whistler for service will change anything.






Sent from my iPhone using Tapatalk
 
Last edited:

Kennyc56

Ford Lover, I/O Hater!
Advanced User
Lifetime Premium Member
Joined
Feb 22, 2018
Messages
2,492
Reaction score
6,003
Location
Eastern North Carolina
Like we've said before, these detectors are designed for the average customer, not crazy folks like us on the forum! You know, the "hear the beep and hit the brakes crowd!" For them, it's all good, but for those of us who are hard core detector users that have multiple detectors and know how they should act, it will drive you nuts! I've tried every single way on Earth to set my CR97 up and just when I think I've found the magic way to run it BAM! yet another K/Ka mixup! If the range wasn't so damn good and the response to I/O so incredible I'd throw it in the closet and say to hell with it! I tried again this past weekend to drive a stake in it's heart at our 35.5/laser test but once again it nipped at the heels of my R1, Redline , V1 and even a R7! It even matched my V1 on every laser gun we could throw at it kicking all of my other detectors @ss in the process!
 
Last edited:

NOTKTS

Learning to Fly
Beginner User
Joined
Oct 30, 2018
Messages
75
Reaction score
176
Location
Long Island/NY
Some recent low level experimenting leads me to think that lowering the xk filter to 0 seems to reduce the incidence of the k/ka mix up. I had FDSR off and TFSR on with the ka filter at 1. Also kept ka max off. Stuck in traffic and I put the xk filter to 1 and it reported ka at 33.8 for what were BSM's. Lowered xk to 0 and the falsing showed as k. Same cars were around me as I was hardly moving. Driving around this way seems to result in less k/ka mix ups. I will email Whistler and see what they say. Again, this is my gut feel and nothing more, but when I got a false with these setting the 97 showed it as a k and very rarely as a ka from what I recall.
 

RoadDogg

Lifetime RDF Contributor
Intermediate User
Lifetime Premium Member
Joined
May 10, 2018
Messages
438
Reaction score
895
Location
Tennessee
Like we've said before, these detectors are designed for the average customer, not crazy folks like us on the forum! You know, the "hear the beep and hit the brakes crowd!" For them, it's all good, but for those of us who are hard core detector users that have multiple detectors and know how they should act, it will drive you nuts! I've tried every single way on Earth to set my CR97 up and just when I think I've found the magic way to run it BAM! yet another K/Ka mixup! If the range wasn't so damn good and the response to I/O so incredible I'd throw it in the closet and say to hell with it! I tried again this past weekend to drive a stake in it's heart at our 35.5/laser test but once again it nipped at the heels of my R1, Redline , V1 and even a R7! It even matched my V1 on every laser gun we could throw at it kicking all of my other detectors @ss in the process!
You are right that the CR97 is more for the average consumer than us crazy enthusiasts on the RDF. I have been running my CR97 more the last few days back to experimenting with the settings. I still enjoy running the CR97 even though it has some quirks. I, too, am old Whistler guy. I know I oftentimes I say the same things over and over about the CR97, and I sound like a broken record...lol. “It is what it is” until a firmware update is introduced to fix the issues (if it is possible with this hardware platform). If not, hopefully Mike B. and the folks at Whistler can fix some of these issues we have been discussing on their next generation of detectors. Even though my CR97 is not my primary detector, I will continue to “throw it in the mix” and still use it.

I have been running TFSR off quite a bit lately (My FDSR/r stays off all the time now too) bumping up the XK and Ka filters a bit too. TFSR on seems to help with reducing false alarms, but warning range/sensitivity seems to take a reduction too as we have discussed before. I like my CR97 in the city (I don’t use the GPS lockouts on my R3 or Max360c), and I often use it in my wife’s vehicle around the town as it gives me plenty of warning against the C/O on K and Ka (34.7/35.5) that I encounter in my city and the neighboring town.


Sent from my iPhone using Tapatalk
 

Kennyc56

Ford Lover, I/O Hater!
Advanced User
Lifetime Premium Member
Joined
Feb 22, 2018
Messages
2,492
Reaction score
6,003
Location
Eastern North Carolina
I feel the same way! I picked up another R1 yesterday from @johnboy00 that he only ran for 1 hour! I'm going to take my CR95 out of Jane's low mileage 99 Mustang that we just bought a little while ago. I've tried every possible way to "fix" the quirks in it as well! I'm going to put the new R1 on a perm mount off of Ebay, hardwire it and let it eat! I'm running my "ghetto arrows" in my daily driver Mustang, but I'm also going to run the 95 and 97 from time to time. not with the ghetto arrows of course! The R1/Redline setup is the best I've ever run with, and that includes a R7 that I ran for more than a week and tested on the same day we tested the ghetto setup! My ghetto setup won! I'm still hoping Whistler will fix this damn K/Ka mixup because in this day and age, there is really no excuse for it!
 
Last edited:

yellowtibby

Shifter ZR4's number one fan.
Intermediate User
Joined
Dec 15, 2011
Messages
362
Reaction score
169
Location
Idaho and Connecticut
Do you guys think Whistler has given up on the CR97? It is their flagship detector and its less than 1 year old since release. I would be surprised they are giving up on it. I wonder if their sales of the cr97 are dismal since its sold only exclusively through radarbusters?
 

Brainstorm69

TXCTG 2016 MOTY
Advanced User
Premium Member
Joined
May 23, 2015
Messages
8,952
Reaction score
18,717
Location
Lone Star State
Perhaps the exclusive deal with RB only lasts for a set period of time and we'll see the CR97 being sold elsewhere in the future.
 

RoadDogg

Lifetime RDF Contributor
Intermediate User
Lifetime Premium Member
Joined
May 10, 2018
Messages
438
Reaction score
895
Location
Tennessee
Do you guys think Whistler has given up on the CR97? It is their flagship detector and its less than 1 year old since release. I would be surprised they are giving up on it. I wonder if their sales of the cr97 are dismal since its sold only exclusively through radarbusters?
I certainly hope they haven’t give up on the CR97. Hopefully Whistler will surprise us all with a firmware update before the end of the year. I do remember the CR97 was originally was reported that it was going to be released for sale in early 2018, but the release was delayed maybe around 6 plus months. I wonder if Whistler was trying to fix some of the reported issues back then and could not fix them and decided to go ahead and put the CR97 on the market? I know Whistler did some product testing prior to product release, and they had to have known about the K/Ka mix up. I know when I called Whistler (several times) after using the CR97 for a while about the K/Ka mix up, the people at Whistler indicated that was “normal” and no reason to send the CR97 in for service. I now know some of “quirks” I was experiencing with the CR97 are common to the CR97 and others were experiencing them as well. I am using my CR97 mostly in the city now, and I normally run mine with TFSR on in the city with the XK and Ka filters at either 1 or 2 (after trying TFSR off with many different filter adjustments on XK and Ka).

Perhaps the exclusive deal with RB only lasts for a set period of time and we'll see the CR97 being sold elsewhere in the future.
Interesting point. I wonder if the exclusive deal is for 1 year (or longer)? I believe Radar Busters has a presence on both EBay and Amazon so the CR97 is available for sale on those platforms from Radar Busters in addition to their website.



Sent from my iPhone using Tapatalk
 

NOTKTS

Learning to Fly
Beginner User
Joined
Oct 30, 2018
Messages
75
Reaction score
176
Location
Long Island/NY
I emailed Whistler on Saturday asking them if keeping xk at 0 actually can be minimizing those BSM k/ka mix ups. If I get an answer, I'll post it.
 

NOTKTS

Learning to Fly
Beginner User
Joined
Oct 30, 2018
Messages
75
Reaction score
176
Location
Long Island/NY
Sorry for the long post....
I received a reply...
Here's my question:
  • I have a CR97, updated to latest firmware. I notice a mix up with k & ka when it's detecting automotive BSM systems. It defaults to ka. This is a problem as most enforcement here uses ka. I have FDSR off, Ka max off, TFSR on. Experimenting with filters and I notice these mix ups are reduced when the xk filter is at 0 and Ka filter is at 1. It seems if I increase the xk filter these incorrect id's increase. Does this seem to be a solution of sorts or is it due to the randomness of cars around me? Can this be fixed or reduced with a firmware update?

    Here's the reply:
    HI,

    I checked with engineering and they suggest increasing the Ka filter from 1 to 2 or possibly to 3.

    --

    John
    Whistler Customer service representative
    Thank you,
    Whistler Customer Support

    I am afraid of bumping Ka up & unfortunately there is no mention of firmware update. They did answer quickly. I thought I was on to something. I wonder if they are looking at this now behind the scenes. I'll bump up Ka to 2 and see what happens. Again, I never ran xk at 0. If they can fix this without clipping range it would be great.
 

Kennyc56

Ford Lover, I/O Hater!
Advanced User
Lifetime Premium Member
Joined
Feb 22, 2018
Messages
2,492
Reaction score
6,003
Location
Eastern North Carolina
Sorry for the long post....
I received a reply...
Here's my question:
  • I have a CR97, updated to latest firmware. I notice a mix up with k & ka when it's detecting automotive BSM systems. It defaults to ka. This is a problem as most enforcement here uses ka. I have FDSR off, Ka max off, TFSR on. Experimenting with filters and I notice these mix ups are reduced when the xk filter is at 0 and Ka filter is at 1. It seems if I increase the xk filter these incorrect id's increase. Does this seem to be a solution of sorts or is it due to the randomness of cars around me? Can this be fixed or reduced with a firmware update?

    Here's the reply:
    HI,

    I checked with engineering and they suggest increasing the Ka filter from 1 to 2 or possibly to 3.

    --

    John
    Whistler Customer service representative
    Thank you,
    Whistler Customer Support

    I am afraid of bumping Ka up & unfortunately there is no mention of firmware update. They did answer quickly. I thought I was on to something. I wonder if they are looking at this now behind the scenes. I'll bump up Ka to 2 and see what happens. Again, I never ran xk at 0. If they can fix this without clipping range it would be great.
Thanks for your efforts @NOTKTS . I can promise you that all of us with the CR97 are all waiting for the miracle cure. I finally gave up on my CR95 in jane's car. Everytime we would drive her Mustang somewhere, I noticed that she had turned the volume all the way off due to all of the K/Ka mixup BS. That was not going to work! I just happened to be looking in the classifieds when a brand new R1 with only one hour of run time on it popped up for sale. I got a great deal on it, updated it to 1.48 from 1.37, hardwired it and installed it on a perm Ebay mount above her rear view mirror. We also replaced her dash cam as well. She's all set! I'm not going to sell my 95 or 97 and am waiting to see what if anything changes for them. Again, I'm not holding my breath!
 
Last edited:

RoadDogg

Lifetime RDF Contributor
Intermediate User
Lifetime Premium Member
Joined
May 10, 2018
Messages
438
Reaction score
895
Location
Tennessee
Sorry for the long post....
I received a reply...
Here's my question:
  • I have a CR97, updated to latest firmware. I notice a mix up with k & ka when it's detecting automotive BSM systems. It defaults to ka. This is a problem as most enforcement here uses ka. I have FDSR off, Ka max off, TFSR on. Experimenting with filters and I notice these mix ups are reduced when the xk filter is at 0 and Ka filter is at 1. It seems if I increase the xk filter these incorrect id's increase. Does this seem to be a solution of sorts or is it due to the randomness of cars around me? Can this be fixed or reduced with a firmware update?

    Here's the reply:
    HI,

    I checked with engineering and they suggest increasing the Ka filter from 1 to 2 or possibly to 3.

    --

    John
    Whistler Customer service representative
    Thank you,
    Whistler Customer Support

    I am afraid of bumping Ka up & unfortunately there is no mention of firmware update. They did answer quickly. I thought I was on to something. I wonder if they are looking at this now behind the scenes. I'll bump up Ka to 2 and see what happens. Again, I never ran xk at 0. If they can fix this without clipping range it would be great.
Thanks for sharing. I have not noticed any difference bumping the Ka filter higher on the K/Ka mix up. I have been adjusting and trying many different filter combinations and adjusting both XK and Ka filters up and down, and TFSR on vs off, and my experience is the K/Ka mix up is the same on most BSM systems no matter what filter combination or TFSR setting I choose. His response leads me to believe there is no firmware update in the works, but maybe they are working on one and don’t want to discuss it until released. I use Ka Max Id setting for Ka, so when I don’t get a Ka frequency with my warning (a generic Ka warning) I know it is most likely a BSM. Oftentimes a 33.8 Ka warning is a Honda/Acura BSM too. Almost every 34.7 or 35.5 for me has been real police radar.

Let us know what your experience is changing the settings and bumping up the Ka filter. I don’t think bumping the Ka filter to 2 will cause a huge difference in warning range.


Sent from my iPhone using Tapatalk
 

Users Who Are Viewing This Thread (Users: 0, Guests: 1)

Latest threads

Latest posts

Social Group Activity

Forum statistics

Threads
76,613
Messages
1,167,129
Members
19,684
Latest member
lonelydesires
Top