- Joined
- May 18, 2018
- Messages
- 4,251
- Reaction score
- 7,369
Recently have observed people talking, complaining about Ka falses on there device.
I have been experiencing this. Where my traditional segmenting (2,4,5,6,8) does not solve the problem.
I have have seen falsing across most of Ka bands.
I observe this behavior growing in past several months. Affects my VR G2s, R7, 360 platform (non RL). I have second hand user report of my Pro M triggering Ka more often then normal, no police observed.
There are reports on RDF of multiple RL 360c doing this (I do not own one yet).
At first I blamed theG2 new Ka falsing (my current heavy use device) new .019 firmware. The new firmware also has messed up the best in class BSM filtering (IMO, more on G2 BSM in another post later). Then, as I moved between devices (and different vehicles), started to notice same issue.
The Ka false problem ratio is rare compared to time. But, the ratio seems to be getting worse.
As a user of CM for 40+ years, I know my way around how to read devices for situational awareness. Here is a sampling of experiences.
I run 4 and 6 segments due to wobbly 34.7 machines being off frequency. On G2 “33.8” freq area cannot be segmented (1,3), so it shows this range. Which is good in northern GA due to actual police running off frequency (outside seg 2). Actually seen be me and others (@benzr is one that comes to mind)
Ka falsing on 2,4,5,6 and lessor extent 8 (Maybe because 7, 9,10 are turned off).
The Ka false I have seen also hits right on 2,5,(Lesser degree 8). Adds to total count of the other frequencies acting up.
I am suggesting that we keep our eyebrows raised, and not assume all Ka alerts we would expect to see are not LEO. And log those that are not.
I have logged JBV1 data to sort through. I have Escort Live observations (need to take screen shots) of miles of Ka reports in a stretch. Sure, once in awhile this can happen due to someone following or being in front of some LEO blasting C/O that goes around bends, and over hills. We have all seen this. However recently when I have used EL, it is worse in busy traveled areas for this to show up.
I experience this both front and rear antenna. With rear antenna, it can go on for long stretches until I change direction. There is no LEO. I have pulled over, turned around to check. These false alerts can be on any segment I have turned on.
I have observed what I ”Guess” are causes of this. I posted pictures of ambulances and trucks on RDF in 2020 that were causing Ka falsing. Rare, but real. This past couple months semis, box trucks, and cars could he causing this. But, there is more to this Ka chaos, IMO.
I observe the Ka alert to shift frequencies. Mostly within (But not always) a segment range, say 34.xxx will show hopping around. On G2 it will show up with many tracked frequencies on JBV1. False many times will also trigger extra “bogie“ counts on the G2 display (Which sometimes kicks in the double beep, and it goes silent. Like a “junk filter” kicks in).
Roughly 80% of the experience is with the VR G2. Because I run it 80%+ of the time being mentioned.
What could this be? At same time multiple brands and devices are all saddled with bad FW, or have gone bad? Do not think so. All of a sudden millions of drivers have bought some new “Batman” like spewing RD that triggers my high end gear? Enough volume sold, I am running into them? Do not think so.
Is there some new tech that is now infiltrating traffic sensors, adaptive cruise controls, or something else? When the rare time this happens it is like the recent past years when we first came upon visual distance of a Pacifica or a Honda that blurted our BSM for half a mile. Only now all this is on Ka?
I have experience while driving multiple vehicles, with Wifi, no wifi, and never had this issue before. Also, in rental vehicles. This past Month or so I have been traveling extensive “pre China virus“ business miles driving. Shows up rare, but routine due to extensive shorter distance +long haul time behind the wheel. This past week, I grew frustrated at this phenomenon, to make this post.
I am posting this thread as a way to see, over time, if others are seeing this trend? Not specific to one brand. Please post your observations. Even if it might appear to be obscure, or someone might suggest you “missed something”. IF this is a real trend, let’s document observations so better testing can be done.
If this post gains any traction, I will go back and get some screen shots of the JBV1 logs.
I have been experiencing this. Where my traditional segmenting (2,4,5,6,8) does not solve the problem.
I have have seen falsing across most of Ka bands.
I observe this behavior growing in past several months. Affects my VR G2s, R7, 360 platform (non RL). I have second hand user report of my Pro M triggering Ka more often then normal, no police observed.
There are reports on RDF of multiple RL 360c doing this (I do not own one yet).
At first I blamed theG2 new Ka falsing (my current heavy use device) new .019 firmware. The new firmware also has messed up the best in class BSM filtering (IMO, more on G2 BSM in another post later). Then, as I moved between devices (and different vehicles), started to notice same issue.
The Ka false problem ratio is rare compared to time. But, the ratio seems to be getting worse.
As a user of CM for 40+ years, I know my way around how to read devices for situational awareness. Here is a sampling of experiences.
I run 4 and 6 segments due to wobbly 34.7 machines being off frequency. On G2 “33.8” freq area cannot be segmented (1,3), so it shows this range. Which is good in northern GA due to actual police running off frequency (outside seg 2). Actually seen be me and others (@benzr is one that comes to mind)
Ka falsing on 2,4,5,6 and lessor extent 8 (Maybe because 7, 9,10 are turned off).
The Ka false I have seen also hits right on 2,5,(Lesser degree 8). Adds to total count of the other frequencies acting up.
I am suggesting that we keep our eyebrows raised, and not assume all Ka alerts we would expect to see are not LEO. And log those that are not.
I have logged JBV1 data to sort through. I have Escort Live observations (need to take screen shots) of miles of Ka reports in a stretch. Sure, once in awhile this can happen due to someone following or being in front of some LEO blasting C/O that goes around bends, and over hills. We have all seen this. However recently when I have used EL, it is worse in busy traveled areas for this to show up.
I experience this both front and rear antenna. With rear antenna, it can go on for long stretches until I change direction. There is no LEO. I have pulled over, turned around to check. These false alerts can be on any segment I have turned on.
I have observed what I ”Guess” are causes of this. I posted pictures of ambulances and trucks on RDF in 2020 that were causing Ka falsing. Rare, but real. This past couple months semis, box trucks, and cars could he causing this. But, there is more to this Ka chaos, IMO.
I observe the Ka alert to shift frequencies. Mostly within (But not always) a segment range, say 34.xxx will show hopping around. On G2 it will show up with many tracked frequencies on JBV1. False many times will also trigger extra “bogie“ counts on the G2 display (Which sometimes kicks in the double beep, and it goes silent. Like a “junk filter” kicks in).
Roughly 80% of the experience is with the VR G2. Because I run it 80%+ of the time being mentioned.
What could this be? At same time multiple brands and devices are all saddled with bad FW, or have gone bad? Do not think so. All of a sudden millions of drivers have bought some new “Batman” like spewing RD that triggers my high end gear? Enough volume sold, I am running into them? Do not think so.
Is there some new tech that is now infiltrating traffic sensors, adaptive cruise controls, or something else? When the rare time this happens it is like the recent past years when we first came upon visual distance of a Pacifica or a Honda that blurted our BSM for half a mile. Only now all this is on Ka?
I have experience while driving multiple vehicles, with Wifi, no wifi, and never had this issue before. Also, in rental vehicles. This past Month or so I have been traveling extensive “pre China virus“ business miles driving. Shows up rare, but routine due to extensive shorter distance +long haul time behind the wheel. This past week, I grew frustrated at this phenomenon, to make this post.
I am posting this thread as a way to see, over time, if others are seeing this trend? Not specific to one brand. Please post your observations. Even if it might appear to be obscure, or someone might suggest you “missed something”. IF this is a real trend, let’s document observations so better testing can be done.
If this post gains any traction, I will go back and get some screen shots of the JBV1 logs.
Last edited:
