Here's a visual example to go along with thatYou might look at this thread. (Just for the basic concepts.)
Custom Frequencies Hi all, In a few recent threads we have seen people complaining about false Ka signals and not realizing what it's about or how to eliminate those signals. While many of us know this stuff like the back of our hands, there are people that don't yet know. In today's vehicles...www.rdforum.org
Without seeing it directly, I can't say this is what's happening, but the Gen1 did this:
With my Gen1 over a year ago (as I recall) I showed that with TMF2 off, the sweeping range of my BSMs would appear as multiple signals and load up my screen with slightly different frequencies. (Even though I was only detecting two BSM emitters.) I could replicate 7-10 alerts this way frequently.
It's sort of like how CRT screens work, or movies work. The persistence of a user-facing alert that beeps and shows light is much longer than a horn-facing signal has to be to generate the alert. You could have a radar signal that appears at 24.195 for a fraction of a second and that will generate an alert that you will see for a few seconds.
With many BSM signals the frequency cycles repeatedly. For example:
Once it gets to it's upper limit, it goes back to 24.195 and does it all again. This can happen many times a second so what you get is strobe-light type of snapshots of what that signal was doing at that sample moment. The next sample will show something a little different, etc.
Lots of samples are displayed for a few seconds each even though they only lasted a fraction of those seconds. Each sample that is different than the existing alerts will generate a new alert.
Taking that a step further into territory where the frequencies are not variable; Getting a signal where the frequency varies a little (or many samples of frequencies) from two nearby emitters might be demonstrating the constructive and destructive interference that occurs from slightly different set frequencies and all of the multipath reflections that might occur.
In any case, VR is aware of what is called SHBC (Suspiciously High Bogey Counts) and has been working on it. Firmware v4.1019 is better than v4.1018 was and v4.1020 should be along fairly soon.
I have no idea why, but for the last few weeks my V1G2 is doing much better with this. My problem with multiple bogeys was almost always during 34.7 alerts. It happened more when I got shot in the rear antenna. It was nothing to get 12 or more on my JBV1! Lately however, It's a lot better and most alerts I'm getting only one or two. I don't know why but I'll take it!Ok,
These are a couple examples of false Ka band reading that went nuts like some kind of FM Ka. I do not get this Chaos with any other brand I run. NONE. This is one sample of many over past weeks.
I also have pages of JBV1 logs of showing FM shifting variable K band popping up for eternal amounts of time.
Especially when real Ka band alert hits, and then “Mikey preference“ kicks in and defeats any K verifier actions, and all the cars surrounding me FM multi freq BSMs Show up. Mikey preference has been reported he wants to have “all alerts” show up once a real one burns through. If this is true, a total mess.
whatever they did to my G2 with FW .019, and new board, make this stuff unbearable when it shows up. VR will be getting a call next week. They should be happy to accept my JBV1 logs and figure out what is causing this. They can my G2s back for complete autopsy. Oh, and BSM “verifier” performance in general is not as good as .018 (and prior) FW.
“Houston Mike, we have a problem“. It needs to be solved. And not in VR “two weeks” reverse dog years.
otherwise G2 is the best out there.
below, notice segments of 2 (mandatory on G2), 4-5-6, 8. No other detector brand gets falses like this on same Ka segments.
View attachment 160327 View attachment 160329