SDS100/SDS200: New SDS Firmware is here!

[werinshades]

There are several new firmware versions out this week. The Uniden website is currently up to date on the changes and latest firmware.

The SDS100 firmware was delayed by a few hours due to a typo.

Scannermanuals < unidenman4 < TWiki

info.uniden.com

Phase 2 is decoding better...well, at least for me, no change with Phase 2 UID capture issue.

 

[Ronnierozier2]

Phase 2 is decoding better...well, at least for me, no change with Phase 2 UID capture issue.

what do you mean by the Phase 2 UID capture issue?

mom currently trying to capture all the UID’s in my area

 

[pro106import]

I noticed no change at all with the decode quality. Mine is still the same even on very weak systems in the -120db range. Sadly, the squelch is still the same with being too tight at level 2. I was hoping that fix would be in the update. I still have to leave the squelch set at zero or 1 (open) to hear anything worse than -110db. It will just scan right by them if I don't.

 

[werinshades]

what do you mean by the Phase 2 UID capture issue?

mom currently trying to capture all the UID’s in my area

Since the 436/536 releases, when the scanner(s) encounter a conversation on a Phase 2 talkgroup, the scanner doesn't consistently display the UID (Radio ID's), during the initial transmission. During a reply it will though. On Phase 1 systems, MotoTRBO, NXDN Trunking, this isn't the case.

 

[KevinC]

I noticed no change at all with the decode quality. Mine is still the same even on very weak systems in the -120db range. Sadly, the squelch is still the same with being too tight at level 2. I was hoping that fix would be in the update. I still have to leave the squelch set at zero or 1 (open) to hear anything worse than -110db. It will just scan right by them if I don't.

Expecting reliable decode at -110 dBm or lower from a consumer grade receiver is asking for a lot in my opinion.

 

[werinshades]

I noticed no change at all with the decode quality. Mine is still the same even on very weak systems in the -120db range. Sadly, the squelch is still the same with being too tight at level 2. I was hoping that fix would be in the update. I still have to leave the squelch set at zero or 1 (open) to hear anything worse than -110db. It will just scan right by them if I don't.

I'm looking at -60db range, so that's pretty tough for any scanner to lock on to.

 

[pro106import]

I'm looking at -60db range, so that's pretty tough for any scanner to lock on to.

Even right now a system hovering around -100db will not lock on with the squelch at 2. But it receives the system 100% with the squelch open. But I don't mean to get off topic. Just wish after 18 months without any updates, that this one fixed something besides a minor thing and a little housekeeping. Maybe there are more updates to come.....

 

[werinshades]

Even right now a system hovering around -100db will not lock on with the squelch at 2. But it receives the system 100% with the squelch open. But I don't mean to get off topic. Just wish after 18 months without any updates, that this one fixed something besides a minor thing and a little housekeeping.
View attachment 124340

As it was said, you're expecting alot for any scanner with that poor of a decode. I'd focus on improving the reception if the system is important to you, instead of expecting some miracle firmware release.

 

[pro106import]

As it was said, you're expecting alot for any scanner with that poor of a decode. I'd focus on improving the reception if the system is important to you, instead of expecting some miracle firmware release.

Like I said above, the reception is perfect , 100%, even at -115 to -120db. But it won't lock on the CC with the squelch at 2. Simple. I am 75 miles away and I get the system 99% of the time. Again, with the squelch at 0. The scanner does great. Just needs a minor fix to make it better.

 

[Ronnierozier2]

Since the 436/536 releases, when the scanner(s) encounter a conversation on a Phase 2 talkgroup, the scanner doesn't consistently display the UID (Radio ID's), during the initial transmission. During a reply it will though. On Phase 1 systems, MotoTRBO, NXDN Trunking, this isn't the case.

Im having this exact problem on my sds100!! I was about to post in the forums but I guess you gave me the answer. At times the alpha tag won’t show but at times it will.

 

[werinshades]

Like I said above, the reception is perfect , 100%, even at -115 to -120db. But it won't lock on the CC with the squelch at 2. Simple. I am 75 miles away and I get the system 99% of the time. Again, with the squelch at 0. The scanner does great. Just needs a minor fix to make it better.

Right...understand, but you're turning off the squelch with a setting at 0. If you have any analog systems, it wouldn't scan because the squelch is too low. In your case, I wouldn't expect to see any improvements as you're lucky to lock onto a control channel. In my situation where I can receive the system set at 19 (the highest), the system can still decode. I don't know what you'd like to see a scanner firmware release do to improve your situation if you have to turn the squelch off to receive it?

 

[werinshades]

Im having this exact problem on my sds100!! I was about to post in the forums but I guess you gave me the answer. At times the alpha tag won’t show but at times it will.

Yes, it's been a known and documented issue since the 436/536 releases. Might go further back that that with 325P2/996P2 releases, but didn't run those scanners like that. Over the years others have mentioned it being a "timing issue" in the firmware(s). I've submitted debug files over the years in an attempt to help resolve it.

 

[pro106import]

Right...understand, but you're turning off the squelch with a setting at 0. If you have any analog systems, it wouldn't scan because the squelch is too low. In your case, I wouldn't expect to see any improvements as you're lucky to lock onto a control channel. In my situation where I can receive the system set at 19 (the highest), the system can still decode. I don't know what you'd like to see a scanner firmware release do to improve your situation if you have to turn the squelch off to receive it?

Its a simple fix that you can do with all radios that use a digital number for the squelch settings ( in the programming code). Just have to make the numbers more linear. If you ever owned a commercial radio (professional grade), you would know what I mean if you went into the "Tune mode" where you can change anything with the radio settings. Very simple code change for any programmer. And yes that is the problem with leaving it open. Any Analog channels without a CTCSS set will stay open. It would make a huge improvement, trust me. My whistlers have an analog squelch control which is much better.

 

[donc13]

Even right now a system hovering around -100db will not lock on with the squelch at 2. But it receives the system 100% with the squelch open. But I don't mean to get off topic. Just wish after 18 months without any updates, that this one fixed something besides a minor thing and a little housekeeping. Maybe there are more updates to come.....
View attachment 124340

According to @JoeBearcat more updates are in the "soon" that are bug and feature updates. No idea how soon, but my impression is with the next month or so.

 

[sonm10]

Even right now a system hovering around -100db will not lock on with the squelch at 2. But it receives the system 100% with the squelch open. But I don't mean to get off topic. Just wish after 18 months without any updates, that this one fixed something besides a minor thing and a little housekeeping. Maybe there are more updates to come.....
View attachment 124340

Try using a different filter. Wide-Auto works best for me.

 

[pro106import]

Try using a different filter. Wide-Auto works best for me.

Yes I have had the best filter setting with all of my systems at Wide-Normal at my location. Thanks.

 

[NoahWL]

Right...understand, but you're turning off the squelch with a setting at 0. If you have any analog systems, it wouldn't scan because the squelch is too low. In your case, I wouldn't expect to see any improvements as you're lucky to lock onto a control channel. In my situation where I can receive the system set at 19 (the highest), the system can still decode. I don't know what you'd like to see a scanner firmware release do to improve your situation if you have to turn the squelch off to receive it?

I have this issue too. The scanner will jump between the control channel and a slightly weaker voice channel until the transmission ends. Setting the squelch to 1 resolves this problem. There is no issue with reception. There simply is not a squelch setting available that will open on weak enough digital trunked systems. We shouldn't have to turn the squelch off to receive systems the scanner has no problem receiving otherwise.

The lazy fix would be to separate conventional and trunked squelch settings. The proper fix would be to add more granularity.

For example, if the threshold is dependent on RSSI, and the current thresholds are as follows:
0: -170dB
1: -130db
2: -90dB
3: -50dB
...

Then the new thresholds should be something along the lines of:
0: -170dB
1: -130dB
2: -120dB
3: -110dB
4: -100dB
5: -90dB
...

Make sense? We're not trying to receive signals the scanner is incapable of receiving; they decode just fine. The problem is if we configure the scanner so it will receive the digital trunked systems we want (by opening the squelch), then the scanner obviously won't scan conventional channels (because the squelch is open). We shouldn't have to choose between open squelch and too tight of a squelch.

 

[captainmax1]

Not only were the SDS and x36 updates out this week, but I also found a new update for my BC125AT (5-10-22) and a recent update for my BCT15X (10-8-21). Thanks, Bearcat, for keeping Uniden's present and previous scanners updated and operating at their best.

 

[pro106import]

I have this issue too. The scanner will jump between the control channel and a slightly weaker voice channel until the transmission ends. Setting the squelch to 1 resolves this problem. There is no issue with reception. There simply is not a squelch setting available that will open on weak enough digital trunked systems. We shouldn't have to turn the squelch off to receive systems the scanner has no problem receiving otherwise.

The lazy fix would be to separate conventional and trunked squelch settings. The proper fix would be to add more granularity.

For example, if the threshold is dependent on RSSI, and the current thresholds are as follows:
0: -170dB
1: -130db
2: -90dB
3: -50dB
...

Then the new thresholds should be something along the lines of:
0: -170dB
1: -130dB
2: -120dB
3: -110dB
4: -100dB
5: -90dB
...

Make sense? We're not trying to receive signals the scanner is incapable of receiving; they decode just fine. The problem is if we configure the scanner so it will receive the digital trunked systems we want (by opening the squelch), then the scanner obviously won't scan conventional channels (because the squelch is open). We shouldn't have to choose between open squelch and too tight of a squelch.

THANK YOU! Finally someone else sees the same problem I have been having for years. I hope @JoeBearcat has it as a priority with the fixes. Most people don't even realize why they are having problems with P25 systems. The signal is there. Plenty of it. Either their squelch isn't at zero or their filters are not set for the best results.
I agree that the current threshold at setting 2 is -90db. I put my radio on a service monitor and that is about where the squelch opens at #2.

 

[werinshades]

Phase 2 is decoding better...well, at least for me, no change with Phase 2 UID capture issue.

I have this issue too. The scanner will jump between the control channel and a slightly weaker voice channel until the transmission ends. Setting the squelch to 1 resolves this problem. There is no issue with reception. There simply is not a squelch setting available that will open on weak enough digital trunked systems. We shouldn't have to turn the squelch off to receive systems the scanner has no problem receiving otherwise.

The lazy fix would be to separate conventional and trunked squelch settings. The proper fix would be to add more granularity.

For example, if the threshold is dependent on RSSI, and the current thresholds are as follows:
0: -170dB
1: -130db
2: -90dB
3: -50dB
...

Then the new thresholds should be something along the lines of:
0: -170dB
1: -130dB
2: -120dB
3: -110dB
4: -100dB
5: -90dB
...

Make sense? We're not trying to receive signals the scanner is incapable of receiving; they decode just fine. The problem is if we configure the scanner so it will receive the digital trunked systems we want (by opening the squelch), then the scanner obviously won't scan conventional channels (because the squelch is open). We shouldn't have to choose between open squelch and too tight of a squelch.

I got all that, but my original statement is I'm seeing better decode on a Phase 2 system, while he's not with a 110-120db receive. If this has been asked about before, I missed it or didn't pay attention to it. I think you're asking alot of a scanner with that poor of a decode, and these are not commercial grade radios, so don't expect it to behave as one.