You would have to miss some traffic at some point. During housekeeping the control channel could issue a channel grant, and by the time you're scanner returns to listening to the control channel, decodes it, tunes the voice channel, the conversation which could just be a quick one second reply (like someone replying "affirmative" or "negative") would already be over.My SDS100 does the same thing and my 436 did too. I thought it was supposed to do it. Neither unit ever missed any traffic though.
You would have to miss some traffic at some point. During housekeeping the control channel could issue a channel grant, and by the time you're scanner returns to listening to the control channel, decodes it, tunes the voice channel, the conversation which could just be a quick one second reply (like someone replying "affirmative" or "negative") would already be over.
My suggestion for this problem would be to have the scanner think the hold time is the max when the user is holding on a trunked system/site. That would at least push the housekeeping to once every 4.5 minutes which equates to losing the control channel 13 times per hour for a grand total of about 8 seconds. Not having the control channel for 8 out of every 3600 seconds instead of 8 out of every 17 seconds would greatly reduce the odds of a missed transmission. There must be a downside to doing this which is why it hasn't been implemented this way already.
I would also change the default behavior of holding on a channel within a trunked system in two ways. First if you are holding on a system, I would have the scanner keep track of the last site on which talkgroups are seen in the control data (i.e. keep a simple lookup table for as long as you are held on that system) and maybe even age out some of the entries if you hold on the system for a long time. Then when trying to hold on a talkgroup, the scanner can look up and hold on the last known site automatically instead of constantly scanning all control channels until you force a site hold where you know the talkgroup is active. Also, if a talkgroup is active and you quickly press the channel hold button, the site should also hold with it. As talkgroups tend to cover specific geographic areas like towers/sites, I think this is a better default if you immediately hold on an active talkgroup (i.e. the odds are low that all sides of the conversation are suddenly going to affiliate to another site).
Stop making sense. LOL, Those are good suggestions.
I'd just like for it to lock on and receive as well as it should and as well as I know it can with some firmware fixes.
It doesn't make sense to me that there are 5 bars present in the signal meter, hold time set to 250, Site NAC enabled, and with the squelch at 2, and even 0, it won't receive consistently.
The SDS100 does a little better when the filter is set on Auto.
What is the difference between NORMAL, AUTO, INVERTED, AND OFF ?
Mark
SDS100&200/536/436/WS1095/996p2/996xt/325p2/396xt/psr800/396t/HP-1/HP-2 & others
I noticed in your video the VC was 853.0875, have you noticed if it's this same frequency every time that causes your issue?
No, can't say I've noticed what frequencies. I'll try and keep an eye on that, but my point remains, it's not decoding like it should.
You would have to miss some traffic at some point. During housekeeping the control channel could issue a channel grant, and by the time you're scanner returns to listening to the control channel, decodes it, tunes the voice channel, the conversation which could just be a quick one second reply (like someone replying "affirmative" or "negative") would already be over.
My suggestion for this problem would be to have the scanner think the hold time is the max when the user is holding on a trunked system/site. That would at least push the housekeeping to once every 4.5 minutes which equates to losing the control channel 13 times per hour for a grand total of about 8 seconds. Not having the control channel for 8 out of every 3600 seconds instead of 8 out of every 17 seconds would greatly reduce the odds of a missed transmission. There must be a downside to doing this which is why it hasn't been implemented this way already.
I would also change the default behavior of holding on a channel within a trunked system in two ways. First if you are holding on a system, I would have the scanner keep track of the last site on which talkgroups are seen in the control data (i.e. keep a simple lookup table for as long as you are held on that system) and maybe even age out some of the entries if you hold on the system for a long time. Then when trying to hold on a talkgroup, the scanner can look up and hold on the last known site automatically instead of constantly scanning all control channels until you force a site hold where you know the talkgroup is active. Also, if a talkgroup is active and you quickly press the channel hold button, the site should also hold with it. As talkgroups tend to cover specific geographic areas like towers/sites, I think this is a better default if you immediately hold on an active talkgroup (i.e. the odds are low that all sides of the conversation are suddenly going to affiliate to another site).
So if i only monitor 1 digital trunking system it would be better if i change my hold time to 255 seconds??
Most of the functionality are aimed at mobile use, when you drive and the coverage from one site comes and goes and the scanner needs to switch to another site to be able to get the reply in a conversation. The same goes for the GPS check that needs to be done, but not as often as now. Maybe once each 3 minutes as you even at highway speed doesn't move that far that the scanner needs to switch scanlists back and forth.My suggestion for this problem would be to have the scanner.....
Most of the functionality are aimed at mobile use, when you drive and the coverage from one site comes and goes and the scanner needs to switch to another site to be able to get the reply in a conversation. The same goes for the GPS check that needs to be done, but not as often as now. Maybe once each 3 minutes as you even at highway speed doesn't move that far that the scanner needs to switch scanlists back and forth.
I wish there where a base mode where all anoying mobile related things where disabled like "house keeping".
/Ubbe
I have an observation, my sds200 with the Mansfield site programmed and all other systems avoided permanently from the fw regional system except the mansfield tx site shows scanning and signal bars but the signal bars disappear every second or so then come back again.
...snip...
Actually this is not true. They also do housekeeping, but there was less housekeeping to do back then. Try using either of them with GPS and you will find that it nearly kills the operating system trying to keep up. With no location control, and any of the new options, they are less effected. So if you don't use the higher options they seem to work without housekeeping because there is less to do.The 996/396 models don't do this that I can see/hear...
So if you don't use the higher options they seem to work without housekeeping because there is less to do.
The bcd325p2 does not do this either and gets all the transmissions, maybe they could add a switch in the settings favorites systems list which would check a favorites list system check box for on/off/auto for housekeeping with the default being auto.The 996/396 models don't do this that I can see/hear...
The bcd325p2 does not do this either and gets all the transmissions,