I was scanning my FL’s, monitoring a statewide system in Ct. (Ct. Land Mobile Radio Network, or CLMRN) when something interesting pops up and I pressed “Channel” on the lower three buttons at the base of the display. This stoped the scanning action and “held” on that particular TG for me, in order to catch any replies on that TG. But I was caught by surprise when the SDS200 left the TG to catch some traffic I had on a few conventional frequencies I had programmed as Priority DND. When the trunked TG became silent, still holding on that TG, the SDS200 jumped to the conventional frequencies when they became active. I have been under the impression the conventional analogue priority features only worked when the scanner was scanning those conventional frequencies, not when the scanner was scanning trunked systems. And since I had the scanner held on a trunked TG I was pleasantly surprised to see this happening. I haven’t as yet reviewed how the priority features work, and what to expect, my first thought was to ask here about it. Was I working under the false impression what I experienced was not possible? Did I get it wrong? Comments?
SDS100/SDS200: Using DND Priority on a conventional analogue frequency and scanning along with trunked systems-using a SDS200.
- Thread starter n1chu
- Start date
Priority DND = Do Not Disturb. Meaning while scanning or held on a tg or any other channel for that matter. You won't hear the blank space in between it checking the Priority channels. Hence the Do No Disturb. If your put it to regular Priority you will hear the space interval as its checking for the Priority channel. Which is annoying. DND is much better. Keep it that way. If you put it to the regular Priority checking mode. You'll hear the difference.
If you turn the priority on within the trunked system it will only check for priority channels within that system only.
Overall, priority DND is the way to go.
If you turn the priority on within the trunked system it will only check for priority channels within that system only.
Overall, priority DND is the way to go.
Yea… not helpful. I know the difference between DND Priority and Simple Priority. I’m under the impression that either will only work when monitoring conventional analogue frequencies. So, if I have the scanner scanning both conventional and trunked, the feature will only revert back to whatever you have either Priority set on if it becomes active while scanning the conventional stuff. Meaning if the scanner is scanning through trunked systems it won’t apply either Priority feature until the scanner gets back to the conventional stuff… just need to wait until it finishes scanning thru the trunked stuff and moves into the conventional stuff. Thanks anyways. I discovered that when I paused scanning when the radio stopped to listen to a trunked system TG the DND Priority feature worked after the trunked transmission completed. This tells me I do not have a proper understanding of how the feature works, or have discovered a setting that allows it when it shouldn’t. I’m just looking for verification of what I happened upon. It just never happened to me previously.
Your trunked radio systems have the capability of having a separate priority setting which is only for that particular trunked radio system it's scanning at the time. You can set priority talkgroups within each trunked system. Turning the feature on/off within the system, only affects that system.
The other priority settings (ie. Priority - DND) pertain to the conventional channels which the radio listens for. When that is turned on, You will be listening for the priority conventional channels regardless if it's a conventional system or a trunked system that you're scanning.
The other priority settings (ie. Priority - DND) pertain to the conventional channels which the radio listens for. When that is turned on, You will be listening for the priority conventional channels regardless if it's a conventional system or a trunked system that you're scanning.
Ubbe
Member
You are absolutely right. What firmware version are you using? It must be a new feature Uniden have programmed as it never have worked like that, as it is technically very difficult to do during monitoring of a trunked system. User manual says it only does DND during conventional channel monitoring and not when monitoring trunked systems.
Priority DND – The scanner checks priority channels, based on the Priority Interval and Max Channels settings, only when not receiving other conventional channels so there is no interruption in scanning with conventional systems
Priority ID Scan – This function is similar to conventional priority although there is no interruption during the transmission. Priority is checked in between transmissions, when the scanner is receiving the control channel, and during the channel delay period. The scanner can only look for priority IDs in the trunked system it is currently scanning.
/Ubbe
Yeah, priority scanning with Uniden is kind of wild.
When there is Priority scanning involving a conventional frequency, the scanner will "jump off" a trunked conversation to check for an active conversation on a conventional channel. But, the scanner will NOT jump off a conventional channel to check for a conversation on a priority trunked channel.
I imagine all of this is due to the differences in how trunked systems are "scanned" versus conventional channels.
The only thing about "DND" is that the scanner is "told" to not leave an active conversation and check for activity on higher priority conventional channels.
When there is Priority scanning involving a conventional frequency, the scanner will "jump off" a trunked conversation to check for an active conversation on a conventional channel. But, the scanner will NOT jump off a conventional channel to check for a conversation on a priority trunked channel.
I imagine all of this is due to the differences in how trunked systems are "scanned" versus conventional channels.
The only thing about "DND" is that the scanner is "told" to not leave an active conversation and check for activity on higher priority conventional channels.
I believe I’m using the latest version of the Butel programming software as I have the automatic update feature turned on. As for the SDS200 firmware I have the following:
Main Ver 1.23.07
Sub Ver 1.03.06
Idlemonitor and Ubbe have answered my question. If I have correctly caught your drift on the way it works; any conventional frequency that’s tagged as either Priority or Priority DND (when there is no activity) will work during scanning BOTH conventional AND trunked systems. But the Priority feature on a trunked system only works when the scanner is scanning that particular trunked system.
This is good to know as I now have the understanding that when I am scanning the numerous trunking systems I have programmed, conventional Priority is active and will work, bringing my scanner back to the conventional priority frequencies I have tagged immediately, or in the case of Priority DND only when there is no activity on the trunked systems. I was working under the assumption that while the scanner was scanning through the trunked systems I was loosing the ability to use the conventional Priority features, where I may be missing a lot on the conventional side… thinking I should have a second scanner such as a BCD996 (I’ve got the older version, not the P2) dedicated to conventional and the SDS200 dedicated to trunking. I still may press the 996 back into service just the same!
Thanks again for all the help.
This is good to know as I now have the understanding that when I am scanning the numerous trunking systems I have programmed, conventional Priority is active and will work, bringing my scanner back to the conventional priority frequencies I have tagged immediately, or in the case of Priority DND only when there is no activity on the trunked systems. I was working under the assumption that while the scanner was scanning through the trunked systems I was loosing the ability to use the conventional Priority features, where I may be missing a lot on the conventional side… thinking I should have a second scanner such as a BCD996 (I’ve got the older version, not the P2) dedicated to conventional and the SDS200 dedicated to trunking. I still may press the 996 back into service just the same!
Thanks again for all the help.
