STI 33.8 issue never existed or already is fixed? PART 2
Quote:
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:
jimbonzzz wrote:
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.
To the Professor,
Ok so if the 33.8 issue is caused by Ka filtering to prevent false alerts from other detectors and raises the threshold or ignores a section of KA band for a CERTAIN DURATION, then why the HEL where there other Radar Detectors on or other interference around which causes the STI to go into this high threshold mode during the GOL test?
If this is true on the STi shouldn't the test be redone without the STi going into the "high threshold filtering." Why test the STi when the filtering was activated. Why call it an issue? The STi was doing what its design to do??
Im puzzled now on this...
Re: STI 33.8 issue never existed or already is fixed? PART 2
Quote:
Originally Posted by Buford T. Justice
To the Professor,
Ok so if the 33.8 issue is caused by Ka filtering to prevent false alerts from other detectors and raises the threshold or ignores a section of KA band for a CERTAIN DURATION, then why the HEL where there other Radar Detectors on or other interference around which causes the STI to go into this high threshold mode during the GOL test?
There was NOT any other detectors powered on, nor other interference in the proximity.
"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."
Quote:
Originally Posted by Buford T. Justice
If this is true on the STi shouldn't the test be redone without the STi going into the "high threshold filtering." Why test the STi when the filtering was activated. Why call it an issue? The STi was doing what its design to do??
Im puzzled now on this...
The problem is that it went into this mode during normal exposure to actual police radar. It was designed to do this in the presence of other detectors, NOT in regular encounters with real police radar.
Hope this answers your question!
Re: STI 33.8 issue never existed or already is fixed? PART 2
Quote:
Originally Posted by jimbonzzz
Quote:
Originally Posted by Buford T. Justice
To the Professor,
Ok so if the 33.8 issue is caused by Ka filtering to prevent false alerts from other detectors and raises the threshold or ignores a section of KA band for a CERTAIN DURATION, then why the HEL where there other Radar Detectors on or other interference around which causes the STI to go into this high threshold mode during the GOL test?
There was
NOT any other detectors powered on, nor other interference in the proximity.
"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."
Quote:
Originally Posted by Buford T. Justice
If this is true on the STi shouldn't the test be redone without the STi going into the "high threshold filtering." Why test the STi when the filtering was activated. Why call it an issue? The STi was doing what its design to do??
Im puzzled now on this...
The problem is that it went into this mode during normal exposure to actual police radar. It was designed to do this in the presence of other detectors,
NOT in regular encounters with real police radar.
Hope this answers your question!
So maybe the newer firmware raises this threshold up a bit to prevent the STi from going into high band filter mode?
Re: STI 33.8 issue never existed or already is fixed? PART 2
Quote:
Originally Posted by Buford T. Justice
So maybe the newer firmware raises this threshold up a bit to prevent the STi from going into high band filter mode?
I don't know for sure what they might have done. But, here are some possibilities:
-They could have tightened their timing constraints for the "blip". So for example IF the "problem code" was looking for a blip that lasts from 100-200ms, then the "new code" might look for one that lasts for say 130-160ms (numbers made up of course :) ) .
-They could look for the "blip" to occur a certain number of times, or at certain intervals, or before "locking out" the 33.8 area.
-Or they could have switched to a different scheme altogether.
