Captain Kirk
New member
Cody,
I do not know that much about the details of the Explorer design. I just ask myself the question about the purpose of the null. To me it makes sense that the null is just the detectors means of letting the user know that a rejected target has been detected. The opposite approach would be to not inform the user at all by leaving the threshold tone undisturbed. But, it seems that it is useful to inform the user that there are targets there that are being rejected.
The next issue is what should determine the length of the null. In looking for an answer to this question we must make a determination as to how long the target ID should last. Supose that you are sweeping at 5 feet per second (I know that is very fast for the Explorer). That suggests that the center strip is over the target for only about 1/60 of a second or 16.7mS. That is clearly not enought time to sound the target ID tone. Therefore, the tone must be stretched out to some degree. Also consider that the detector electronics would like to be able to look at multiple cycles of the received signal in order to make a more accurate target ID. All of these factors are probably what determines the length of the null time. When we switch to FAST on, then the Explorer probably shortens the process down to some degree at the expense of accuracy.
If the only purpose of the null is to inform the user of a rejected target, then I see no reason why the null should not last as long as the target ID falls into the rejected target region or at least some minimum time. As soon as the detector determines that the target no longer falls into the null region, then the null should terminate essentially immediately. I see no reason why the null duration should be effected by the strength of the signal as long as the combined signal (of a good target in close proximity to a rejected target) is greater than the threshold setting.
But, of course I may be out in left field in all of this.
HH,
Glenn
I do not know that much about the details of the Explorer design. I just ask myself the question about the purpose of the null. To me it makes sense that the null is just the detectors means of letting the user know that a rejected target has been detected. The opposite approach would be to not inform the user at all by leaving the threshold tone undisturbed. But, it seems that it is useful to inform the user that there are targets there that are being rejected.
The next issue is what should determine the length of the null. In looking for an answer to this question we must make a determination as to how long the target ID should last. Supose that you are sweeping at 5 feet per second (I know that is very fast for the Explorer). That suggests that the center strip is over the target for only about 1/60 of a second or 16.7mS. That is clearly not enought time to sound the target ID tone. Therefore, the tone must be stretched out to some degree. Also consider that the detector electronics would like to be able to look at multiple cycles of the received signal in order to make a more accurate target ID. All of these factors are probably what determines the length of the null time. When we switch to FAST on, then the Explorer probably shortens the process down to some degree at the expense of accuracy.
If the only purpose of the null is to inform the user of a rejected target, then I see no reason why the null should not last as long as the target ID falls into the rejected target region or at least some minimum time. As soon as the detector determines that the target no longer falls into the null region, then the null should terminate essentially immediately. I see no reason why the null duration should be effected by the strength of the signal as long as the combined signal (of a good target in close proximity to a rejected target) is greater than the threshold setting.
But, of course I may be out in left field in all of this.
HH,
Glenn