SDS100/SDS200: Uniden's Official SDS100/200 1.24.00 Main (12/20/2025) discussion

[Whiskey3JMC]

Shows this is the latest but sentinel not letting me update to it, Just comes up sayings I already have the latest ... Strange

You've confirmed via [Menu > Settings > See Scanner Information > Firmware Version] that the scanner's showing an older version?

Nevermind you answered this in post #59

 

[jasonhouk]

It will be available in the European version of Sentinel.

The European versions if requested by our customer (Avera), they will be officially released after their evaluation and approval.

 

[Ubbe]

Updated my SDS100. ...... I was hoping since this firmware mentioned control channel acquisition that maybe would have fixed the issue, but alas not yet

Set the scanner to debug mode and set it to off and then on again maybe each hour or so to split up the log in smaller parts.
Then if the issue appears note the time and copy the file from the SD card to your PC and edit to keep maybe 5 minutes before the issue and 1 minute after and zip, that will create a very small file and attach to a post in this thread and let Jason know about it so he can forward it to Uniden.

/Ubbe

 

[jasonhouk]

Updated my SDS100. So it's interesting that it mentioned an issue with control channel reception. Mine now takes an extra second to lock onto control channel after update to 1.24.00. But no other issues once control channel is acquired. I still have to test it on a fringe system where it may lose control channel at times.
My main issue with the SDS100s (and it's been consistent on both I have) is on P25 Phase 2, even on a very strong system, a random transmission will come in very garbled or totally lost. If I am scanning a P25 system or two with a System Hold Time of 2 it happens on average about 1 in 25 transmissions. If I set the System Hold Time to 255 it seems to happens less if at all. It seems to happen in the split second between when a transmission ends and if another transmission comes in right at that second. The D error rate goes way up to like 30 or 40, the voice is garbled or not copy able, and sometimes it sounds like encrypted noise coming through. If there's a response transmission right after, the scanner will not track it, it will stay hung up on the original voice frequency for 3 seconds before resuming scanning, or I'll hear that encrypted noise for a few seconds before resuming scanning. This has been consistent with the SDS100s regardless of location, filter, FM vs NFM, Antenna, squelch, you name it. I kinda suspect it might be something with the processor unsure of the time slot on the TDMA voice frequency when it reacquires the control channel after going through that split second "housekeeping" function.

It's very frustrating, always happens at the most inopportune times, and no firmware has fixed it. I could just listen to one system and set System Hold Time for 255 seconds, but that's what I have a Unication pager and a BK radio for and they sound way better on P25 anyway. I want to be able to scan multiple systems with one device.

I also suspect this may have been an issue on my BCD436HP and 536 too. I couldn't see the voice frequencies or D Error rates, but both those devices would randomly garble or lose transmissions on my local P25 Phase 2 with encrypted noise coming through at times. I attributed it to simulcast distortion. But since my SDS100s exhibit the very same behavior, I now doubt that.

Sorry for the lengthy description, I hope I'm describing the probem accurately. I really wish I could get video of my SDS100 doing this. I have tried several times and it never happens when I record but the minute I stop recording, it loses a transmission. I was hoping since this firmware mentioned control channel acquisition that maybe would have fixed the issue, but alas not yet

Has anyone else noticed this?

@policefreak I'm sending you a private conversation.

 

[tglendye]

If your talking about a flash of the signal bar after a transmission is done, I see that...
Both my 100 and 200 do that... Other than that the signal bar is on solid...

I’ve only had my 100 for about 6 months and it has done this with each firmware version released. I took it as “normal” for the scanner, but It does seem to drop the CC for a bit and misses parts of voice traffic. I’d like to see this resolved. My Unication doesn’t miss a beat with the traffic.

But I’m super glad that Uniden is continually releasing updates to improve the operation.

 

[jasonhouk]

I’ve only had my 100 for about 6 months and it has done this with each firmware version released. I took it as “normal” for the scanner, but It does seem to drop the CC for a bit and misses parts of voice traffic. I’d like to see this resolved. My Unication doesn’t miss a beat with the traffic.

But I’m super glad that Uniden is continually releasing updates to improve the operation.

Check your "set hold time" under Edit Sys Option:

Set Hold Time This sets (in seconds) the amount of time the scanner will scan the System before moving on to the next system. All (Unavoided) channels will be scanned at least once regardless of this setting. The scanner moves to the next system after the hold time expires, any current transmission ends, and the channel delay time expires. The default (and recommended) setting is 0 seconds.

Enter the hold time 0-255 (sec.) and press E/yes to save.

 

[jtwalker]

I’ve only had my 100 for about 6 months and it has done this with each firmware version released. I took it as “normal” for the scanner, but It does seem to drop the CC for a bit and misses parts of voice traffic. I’d like to see this resolved. My Unication doesn’t miss a beat with the traffic.

But I’m super glad that Uniden is continually releasing updates to improve the operation.

Your Unication doesn’t scan sites, it stays on one site. Try site hold on your SDS100 and see how it behaves.

 

[Chris0516]

Check your "set hold time" under Edit Sys Option:

Set Hold Time This sets (in seconds) the amount of time the scanner will scan the System before moving on to the next system. All (Unavoided) channels will be scanned at least once regardless of this setting. The scanner moves to the next system after the hold time expires, any current transmission ends, and the channel delay time expires. The default (and recommended) setting is 0 seconds.

Enter the hold time 0-255 (sec.) and press E/yes to save.

@tglendye If you have Proscan, highlight the 'System', and. You will be able to set the Hold Time easily.

 

[tglendye]

I will take a look at the Hold time, but I don’t think it’s related. I should have also mentioned that I have a 436hp that doesn’t behave this way. It keeps track of the CC and doesn’t drop any voice traffic on the same system, same site, same programming, same location, etc.

Thanks

 

[tglendye]

Your Unication doesn’t scan sites, it stays on one site. Try site hold on your SDS100 and see how it behaves.

I’m only scanning a single site but I tried both Site Hold and System Hold, which didn’t make any difference.

The other thing I should have mentioned (instead of bringing the Unication into it) was that my 436hp tracks the system perfectly and doesn’t miss the beginning of any traffic. That’s what’s a little frustrating about it. I figured the 100 would behave the same or better.

 

[I_Am_Infinite]

I had just a few minutes ago on a p25 phase 1 system, Indiana project Hoosier safety site, that the VC was stuck after transmission and was on and off giving static like noise, alternating between static and silence while stuck on it, eventually resumed scanning again.

 

[Ubbe]

I had just a few minutes ago on a p25 phase 1 system, Indiana project Hoosier safety site, that the VC was stuck after transmission and was on and off giving static like noise, alternating between static and silence while stuck on it, eventually resumed scanning again.

A scanner needs to decode the datasignal almost perfectly to be able to tell that it is a control channel in idle mode, or no ongoing conversations at TG's that you have selected to monitor. If the signal are too weak or distorted it will stay on the data signal and try to decode it until it is either too weak to decode at all for a certain amount of time or strong enough to decode the part that says what status it has.

Even if you set the systems hold time to 0 it will still stay at least 1,5 sec as that are the lowest possible time, unless the squelch doesn't detect any signal as it then use normal scan rate of 80ch/s. Those in between signal levels are always difficult to handle for a firmware in a scanner.

/Ubbe

 

[I_Am_Infinite]

A scanner needs to decode the datasignal almost perfectly to be able to tell that it is a control channel in idle mode, or no ongoing conversations at TG's that you have selected to monitor. If the signal are too weak or distorted it will stay on the data signal and try to decode it until it is either too weak to decode at all for a certain amount of time or strong enough to decode the part that says what status it has.

Even if you set the systems hold time to 0 it will still stay at least 1,5 sec as that are the lowest possible time, unless the squelch doesn't detect any signal as it then use normal scan rate of 80ch/s. Those in between signal levels are always difficult to handle for a firmware in a scanner.

/Ubbe

That system is essentially full bars peaked out so signal strength isn't the issue. I've never heard it ever do this before, I don't know what the problem was as I never heard it before, but figured I'd note it

 

[Ubbe]

was on and off giving static like noise, alternating between static and silence while stuck on it, eventually resumed scanning again.

That system is essentially full bars peaked out so signal strength isn't the issue. I've never heard it ever do this before

I agree with you. It seems like when that voice channel ended the call it didn't make the scanner go back to the control channel and it instead where stuck on the frequency in analog mode and the signal level where briefly opening squelch.

For some reason I have a similar problem with my SDS200E but in NXDN mode, that sometimes after a call ends the scanner stays on the channel in analog mode with squelch open and I can turn up the squelch to max but will still stay open. That never happens with my SDS100E using the same older E firmware and filter settings.

/Ubbe

 

[I_Am_Infinite]

I agree with you. It seems like when that voice channel ended the call it didn't make the scanner go back to the control channel and it instead where stuck on the frequency in analog mode and the signal level where briefly opening squelch.

For some reason I have a similar problem with my SDS200E but in NXDN mode, that sometimes after a call ends the scanner stays on the channel in analog mode with squelch open and I can turn up the squelch to max but will still stay open. That never happens with my SDS100E using the same older E firmware and filter settings.

/Ubbe

Ya it's weird, cause why wud it do that on digital modes, and have an analog static noise, just don't make sense. Just so odd that happens on one of urs but not the other. I've had my SDS 200 for years now and have never heard it do that before, with the static noise

I've had other things which happen occasionally, that I've posted about but with this, it's a first for me.

 

[IdleMonitor]

Yeah, I'm not liking this latest update. I've noticed some degredation of signals on a system I listen to.

Seems it's not wanting to pull in the signal needed to decode on the control channel. When I do a conventional search of the frequencies. most of the digital/analog voice frequencies will show up and I can hear the audio. When I scan the system and the sites needed, it will not pick up anything off this system at all.

Now recently, I've added access to my outside antenna with my SDS200 so my signals should be getting better. Not worse. I'm pretty certain that this system is the only one affected. It is the only P25 system active in my area at the moment.

If I put my 436HP up against the SDS200 at the moment with the exact same programming, the 436 hands down will do better and completely pull in the needed system. As well as some other stuff that I wasn't able to get before since gaining access to the outside antenna.

Not sure what else to look at, at this moment.

 

[KevinC]

Now recently, I've added access to my outside antenna with my SDS200 so my signals should be getting better. Not worse. I'm pretty certain that this system is the only one affected. It is the only P25 system active in my area at the moment.

That isn't a "P25" system, it's a Motorola 3600 with mixed-mode audio. The external antenna is probably causing the SDS200 to get overloaded by strong in-band signals.

Nothing in this update should have affected sensitivity that I can see.

 

[IdleMonitor]

That isn't a "P25" system, it's a Motorola 3600 with mixed-mode audio. The external antenna is probably causing the SDS200 to get overloaded by strong in-band signals.

Nothing in this update should have affected sensitivity that I can see.

That should not happen. I had less of an antenna setup a few weeks ago and was still able to pull in the system. I've set the filters to both Off/Normal with no changes. 436HP no issues. All systems go. SDS200 not so much. Same programming. Same antenna, same location. Thought Fleetnet was APCO25 Phase 1. What flavour of digital is it?

The outside antenna is not experiencing any overloading of any signals into either radio.

The P25 fix that had been done. I didn't really noticed the issue until after that update then I thought to myself, actually, yeah I did see the system hang on a frequency in the past. I can't tell now, if this has been fixed, because now I can't even pull in the system needed to listen to.

 

[KevinC]

I had less of an antenna setup a few weeks ago and was still able to pull in the system.

So with the update and the "less" antenna it worked fine?

The P25 fix that had been done. I didn't really noticed the issue until after that update then I thought to myself, actually, yeah I did see the system hang on a frequency in the past.

The update affected 9600 P25 control channels, not 3600 analog like the system you linked, That system is not a "P25" system. As I posted earlier it's a Motorola 3600 system with mixed-mode audio.

Put the 200 back on the "less: antenna and see how it performs.

 

[IdleMonitor]

So with the update and the "less" antenna it worked fine?

The update affected 9600 P25 control channels, not 3600 analog like the system you linked, That system is not a "P25" system. As I posted earlier it's a Motorola 3600 system with mixed-mode audio.

Put the 200 back on the "less: antenna and see how it performs.

I did. Was able to pull it in. Still barely pulls in what I need though compared to before.