No MEM-TEK this is not a hypothesis, this is 100% FACT.
Unlike some people on this forum, I do my best not to represent my personal therories or hypothesis as fact, and I didn't do that in this case.
I feel stupid for having to say this, but have you ever considered the idea that that people who run this board just might periodically have some information which isn't available to the general public? Wink (hint hint) That's all the further I can go with it! If you're waiting for Beltronics
to make an official announcement/admission regarding this, it isn't likely to happen.
I'll recap by quoting the following FACTS that I've posted previously, for the
benefit of anyone who might be reading this.
This is exactly what causes the problem:
The 33.8 problem is caused by Ka filtering to prevent false alerts from other detectors. The STi looks for a brief "blip" of radar on 33.8 of a certain time duration, which is indicative of the sweeping oscillator from a leaky detector. When it sees this "blip", it raises the threshold or ignores a section of the Ka band for a certain duration in order to prevent a Ka false alert from the leaky detector. The problem is that when you're barely "on the edge" of detecting CW radar (like in our test), the signal will fade in and out of the noise, and can produce the same kind of "blip" that might be seen from another detector, causing the STi to filter out that section of the Ka band. How Beltronics might have "fixed" this, I don't know. Perhaps they decided to use a different method, or they tightened their time constraints a bit.