MT1000 scan & priority useage, sensitivity: Q & A ?
Posted: Fri Oct 15, 2004 4:27 am
Have a 99-ch VHF MT1000 'C' model fully programmed and with a scan list with 1 channel as a priority. Everything works perfectly as intended, and the 'beep' option when the priority channel receives a carrier is quite handy when not in view of the channel LCD display.
One curiosity is, when scanning, when the receiving a signal on a normal scan channel, by ear I can detect a single momentary cyclic 'flutter' , as if it would be sampling the priority channel? It's not a drop in the received signal, it's more likely the synthesizer's sampling back to the Priority channel in a regular, timed cycle (i.e. maybe about once every 1/2 second)? When listening to the audio on the regular scan channel in receive in scan, the cycling anomoly doesn't affect the actual audio or intelligibility on that particular channel, I'm just wondering if this is typical when a Priority is programmed, or if I may actually have some sort of problem with this unit? Again, everything works as intended otherwise and I may not really have any problem at all.
For knowlegeable Genesis series individuals, this unit is programmed pretty much as follows: all 99 channels simplex, carrier squelch, no PL's, TX/RX on all, user-pgmmable scanlist (6 w/1 as priority with hangtime after carrier drop maybe 1-sec.- (Question: is it possible to pgm a channel IN the scanlist AND as a priority at the same time?), also has most sensitive sensitivity setting, user cloneable, battery saver option, MVA display flip. Are there any other pgmmed options that may produce this flutter cycle (possible the battery saver option?). Maybe I'm getting concerned about nothing?
Re. Priority, when Priority is set in RSS, on the 99-chan does Priority automatically follow the channel the unit was set to prior to toggling scan on? Or, is it possible to set a Priority channel permanantly without the possibility of it changing in accordance with what the channel was set on prior to scanning?
Also, user manual states that with use of the battery saver option, the PL attack times are degraded 500 milliseconds, and squelch sensitivity is degraded by 2dB. I'm not concerned about PL attack on this particular unit, however I have the sensitivity level adjusted to 'most sensitive' and wonder if the squelch sensitivity degradation by 2dB would make any difference in the real world? I do indeed want the absolute weakest carriers to break squelch - should I delete the Battery Saver?
Also, of course the Priority option samples the priority channel routinely when scanning, but does the Priority option sample the priority channel constantly when NOT in scan? Haven't checked this out yet.
One final question: Have I asked too many questions?
Thanks!
One curiosity is, when scanning, when the receiving a signal on a normal scan channel, by ear I can detect a single momentary cyclic 'flutter' , as if it would be sampling the priority channel? It's not a drop in the received signal, it's more likely the synthesizer's sampling back to the Priority channel in a regular, timed cycle (i.e. maybe about once every 1/2 second)? When listening to the audio on the regular scan channel in receive in scan, the cycling anomoly doesn't affect the actual audio or intelligibility on that particular channel, I'm just wondering if this is typical when a Priority is programmed, or if I may actually have some sort of problem with this unit? Again, everything works as intended otherwise and I may not really have any problem at all.
For knowlegeable Genesis series individuals, this unit is programmed pretty much as follows: all 99 channels simplex, carrier squelch, no PL's, TX/RX on all, user-pgmmable scanlist (6 w/1 as priority with hangtime after carrier drop maybe 1-sec.- (Question: is it possible to pgm a channel IN the scanlist AND as a priority at the same time?), also has most sensitive sensitivity setting, user cloneable, battery saver option, MVA display flip. Are there any other pgmmed options that may produce this flutter cycle (possible the battery saver option?). Maybe I'm getting concerned about nothing?
Re. Priority, when Priority is set in RSS, on the 99-chan does Priority automatically follow the channel the unit was set to prior to toggling scan on? Or, is it possible to set a Priority channel permanantly without the possibility of it changing in accordance with what the channel was set on prior to scanning?
Also, user manual states that with use of the battery saver option, the PL attack times are degraded 500 milliseconds, and squelch sensitivity is degraded by 2dB. I'm not concerned about PL attack on this particular unit, however I have the sensitivity level adjusted to 'most sensitive' and wonder if the squelch sensitivity degradation by 2dB would make any difference in the real world? I do indeed want the absolute weakest carriers to break squelch - should I delete the Battery Saver?
Also, of course the Priority option samples the priority channel routinely when scanning, but does the Priority option sample the priority channel constantly when NOT in scan? Haven't checked this out yet.
One final question: Have I asked too many questions?
Thanks!