SDS100/SDS200: SDS100 Firmware 1.05.00M/1.01.05S Open Beta

[Jake68111]

Don't know if I'm the only one seeing this but listening side-by-side with my 536, I'm seeing audio break squelch about 1/2 to 1 second late on the 100 vs the 536 on the same TX's, monitoring a single site on Starcom in Illinois. Not EVERY TX but I'd be willing to say I've experienced it 90% of the time. I normally apply the betas that are put out but don't normally report findings because I don't consider myself well versed in diagnosing intermittent issues that occasionally arise but thought I'd throw this one out there, should it be deemed worthy of looking into and if others are experiencing the same as I.

 

[werinshades]

Don't know if I'm the only one seeing this but listening side-by-side with my 536, I'm seeing audio break squelch about 1/2 to 1 second late on the 100 vs the 536 on the same TX's, monitoring a single site on Starcom in Illinois. Not EVERY TX but I'd be willing to say I've experienced it 90% of the time. I normally apply the betas that are put out but don't normally report findings because I don't consider myself well versed in diagnosing intermittent issues that occasionally arise but thought I'd throw this one out there, should it be deemed worthy of looking into and if others are experiencing the same as I.

We might have a similar issue with Starcom (Site 1-002) and I submitted debug files and a video in an attempt to capture the issue. I noticed short replies were not being heard, and with this version I had some transmissions dropping which has not occurred with previous firmware versions. Per the release notes, there was some changes in Phase 1 P25 decoding which I'll assume is what we are seeing. Ohio MARCS system has similarities to Starcom, and with your findings also confirming it, the change didn't help us. For the time being, I went back to 1.04.01 until the next firmware comes out.

In addition to this issue, UID's are not being captured during recording which has been posted and debug files submitted by another SDS owner. On the same note, Record is supposed to shut off when unit is powered off, which it isn't.

I'm sure these issues will be reviewed and fixed as previous problems discovered were.

 

[K9JLR]

With this firmware update, I'm noticing less noise with VHF and UHF analog transmissions that are more distant (e.g., RSSI values AOB -95 to -100 dBm) than I had previously, making the audio more clear.

 

[Kevinbb]

With this firmware update, I'm noticing less noise with VHF and UHF analog transmissions that are more distant (e.g., RSSI values AOB -95 to -100 dBm) than I had previously, making the audio more clear.

I'll agree with this to an extent. It's getting better with less white noise but my other brand scanner is still pulling VHF/UHF better. The SDS hands down is better on digital than all of them. I wish somehow they could make the VHF/UHF as good as the 780/996P2/325. Not asking for too much

 

[K9JLR]

I'll agree with this to an extent. It's getting better with less white noise but my other brand scanner is still pulling VHF/UHF better. The SDS hands down is better on digital than all of them. I wish somehow they could make the VHF/UHF as good as the 780/996P2/325. Not asking for too much

Oh yes, definitely notice much better performance on digital than otherwise. I just noticed after the last firmware update that a lot of that white noise was gone on analog.

Sent from my Pixel XL using Tapatalk

 

[policefreak]

Oh yes, definitely notice much better performance on digital than otherwise. I just noticed after the last firmware update that a lot of that white noise was gone on analog.

Sent from my Pixel XL using Tapatalk

I really believe these two are related. I noticed in my area a drop in sensitivity with this firnware, but less image artifacts on otherwise empty frequencies and less bleedover interference on active frequencies. This was noticed just doing a custom search of the active bands here which is highband VHF, TBand UHF, and 700/800mhz. The biggest difference was on UHF. VHF performance actually increased as if there was a rise in sensitivity. 700/800 signals still very noisy with 2 powerful transmitters both 2 miles from my location in different directions. Yet P25 Phase 2 performance on my county's local 700/800 system has seen slight improvement with less choppiness on the 800mhz frequencies due I believe to bleedover from those stronger transmitters. Due to unsettled weather the atmosphere hasn't really been conducive to getting an accurate test on sensitivies, noise, and
the effect on distant signals.

 

[jasonhouk]

While in Delaware, OH I was experiencing much higher noise (1000-5000)on COIRS Simulcast than on MARCS non simulcast (50-500). I'm wondering if this noise level is not normal as my decode was stellar?

The only issue I'm having now is with the Analyze feature being hit & miss on decode of site ID, sys ID , activity and quality even though I'm not getting those issues during normal scanning. I've submitted logs through the Beta Group UJE.

Houk

Very good explanation of what we're also seeing. I have been working to confirm that since my noise level is pretty high, but decode is very good that I wasn't having some sort of interference with this firmware, which I did not. I applied IFX to the control channel, and wasn't able to receive a strong enough signal to decode the control channel data. As soon as I turned it off, everything returned to normal.

Sent from my Moto G (4) using Tapatalk

 

[Badboy536]

Sitting the sds100 next to my 436 using the same antenna on each Both with the same programming.listing to LAPD .The 436 stops on a lot more divisions. Theres some divisions the 436 stops on that the sds100 has never stopped on or received. I remember when the 436 first cane out it did the same thing. But after a few firmware updates or a year or two it now receives the way it should. I feel like the sds100 is in that spot that the 436 was.hope you figure out the Tweaking so it will receive as good as the 436 does.

 

[del1964]

SDS-100 locking up on a DMR frequency.....

I'm currently running this Beta Firmware on my SDS-100

I've been running my SDS100 on a couple of DMR systems in south Indianapolis area and I'm noticing a "bug". The scanner locks up on the CC channel (which is also used for voice) frequency with no audio coming out. It's showing the Con+ system. It's showing a slot number. It's showing the color code 6. But just sits there locked up on that channel and no voice traffic. Do DMR systems have a control channel that's also voice and is that why the scanner is locking up on it?

Two systems that it seems to be doing this on when I'm close to their towers:

Perry Township Metropolitan School District (TRBO)

Eskanazi Health Operations


I suppose it's possible I've programmed something in incorrectly and my explanation I know sounds clear as mud probably but maybe someone reading knows possibly what the issue is??

I do know that if I program the Perry Township frequency 462.500 as a conventional frequency DMR, that it definitely locks up on it and won't continue scanning. I'll attach a screenshot of what RRDB shows as Indiana/Marion County/Various Businesses/Shopping Malls/Castleton Square Mall where I had it programmed in as "Digital Only" and "FM" and "Digital Code Search"


I tried to attach an pic of my scanner while it was on the channel but for some reason I keep getting invalid attachment errors no matter what format/size/type???

 

[SCPD]

Just trying my new sds100 out.. weak signals come in on this beta firmware and on the official latest firmware but when i set charge while on to enabled i receive nothing at all..
Dont know if this has been replicated but first impressions of this sds100 are its awesome receive... Then i discovered under battery options "Set Charge While On" and enabled it... lost all reception except super strong channels... went back in and set Charge While on to DISABLEreception back to normal.... also in search mode p25 conventional always starts out as a digital buzzing and then after about 2 seconds the p25 nac displays and audio is crystal clear and the first 1/2 of the transmission is missed all the time only in earch mode holding on a known p25 conventional frequency....

 

[jonwienke]

I'm currently running this Beta Firmware on my SDS-100

I've been running my SDS100 on a couple of DMR systems in south Indianapolis area and I'm noticing a "bug". The scanner locks up on the CC channel (which is also used for voice) frequency with no audio coming out. It's showing the Con+ system. It's showing a slot number. It's showing the color code 6. But just sits there locked up on that channel and no voice traffic.

That's not a bug, that's bad programming. If you have a control channel frequency programmed conventional, that is what will happen. You have to program the frequency as part of a MotoTRBO Trunk system.

 

[SCPD]

That's normal. If the channel is not specifically programmed as P25 digital, then when a transmission starts, the scanner has to detect that the signal is digital and not analog, figure out what kind of digital (P25 vs NXDN, DMR, etc), and then start decoding. That can take up to a second or two, depending on signal strength (better signal takes less time). If you know a frequency is P25, program it as P25 and hold on the programmed frequency, and the problem will go away.

Thanks a bunch jonwienke... programmed as a p25 1frq trunk and boy its picking up everything and even running circles around my BCD996p2 and analog is better then my bct15x...

 

[kc5igh]

If you are referring to the digital threshold settings, these no longer exist (even hidden in firmware) using the I/Q receiver design. If and as we determine that there might be some useful user adjustments to expose, we'll consider doing so.

Thanks, Paul.

Some user adjustments might be very useful, and perhaps even make your life a little easier. On the other hand, user adjustments will give many of us an opportunity to get much deeper into that radio and really screw things up! I, for one, plan to blame Uniden for whatever I do to mess up my SDS100 . . . LOL!!!

Have a good day, and I hope your health is holding up.

-Johnnie

 

[SCPD]

What is one to do when monitoring 159.3675 dmr and 159.435 keys through closecall on bcd996p2 and knocks the complete signal away from 159.3675 on the sds100?
Also 162.4mhz weather is ghosting onto 162.35mhz
and thats a week noaa channel
Will try to get video of both side bye side...

Wondering if instead of a set antenuator if there could be a user adjustable gain for the recieve implimented and would fix issues of desense...

 

[W2GLD]

I have a similar issue as well that affects the entire 144-165 MHz spectrum in the SDS100. Here in Livingston County, Michigan, they have a simulcast VHF Fire/EMS Dispatch/Two-Tone Paging channel on 154.010 MHz; with the stock rubber duck, it bleeds over everything from 144-165 MHz no matter where I am in the county; this doesn't happen on ANY other receiver I have. And those are the Airspy 1, Arispy 2, Whistler TRX-1, ICOM IC-F50V, IC-F3161, IC-F5061, IC-F3400 and IC-F5400, Yaesu FT70DR, Kenwood TH-D74A, TH-F6A, TH-D72A, TS-2000, and TMD-710GA, Uniden BC125AT, and two AnyTon D868 radios; also, prior to me selling my BCD436/536 radios; it never happened there either so it's unique to this SDS100...

I've been tested every single beta firmware that has come along expecting a fix, but still happens as of today as well; otherwise this is an excellent scanner overall aside from battery life and not being able to use AA's I have on hand.

What is one to do when monitoring 159.3675 dmr and 159.435 keys through closecall on bcd996p2 and knocks the complete signal away from 159.3675 on the sds100?
Also 162.4mhz weather is ghosting onto 162.35mhz
and thats a week noaa channel
Will try to get video of both side bye side...

Wondering if instead of a set antenuator if there could be a user adjustable gain for the recieve implimented and would fix issues of desense...

 

[SCPD]

ok So i'm not the only one noticing a complete band whipe on VHF Hi band
I think if the gain for receive were user adjustable to say 1 or 2 to say -6db increments we would be able to fine tune in these situations...
Almost like the Receive is too HOT... I would be willing to test on my own sds100 if Uniden would be willing to offer a solution similar to what I mentioned or send if possible send me a test firmware say 4db less sensitivity.....Attenuater is not an option as even with it on global its still whipes out the VHF Hi band altogether I would not have noticed this but 2 hikers were missing about 5 miles from here and NYSDEC powered up their Johns Brook emergency repeater for back woods rescue which is about 1/8 mile away...

 

[SCPD]

ok So i'm not the only one noticing a complete band whipe on VHF Hi band
I think if the gain for receive were user adjustable to say 1 or 2 to say -6db increments we would be able to fine tune in these situations...
Almost like the Receive is too HOT... I would be willing to test on my own sds100 if Uniden would be willing to offer a solution similar to what I mentioned or send if possible send me a test firmware say 4db less sensitivity.....Attenuater is not an option as even with it on global its still whipes out the VHF Hi band altogether I would not have noticed this but 2 hikers were missing about 5 miles from here and NYSDEC powered up their Johns Brook emergency repeater for back woods rescue which is about 1/8 mile away...

So heres an example... 157.74mhz picks up on bcd996p2 and completely misses it on the sds100 several times.. then the sds100 loses the signal completely after it stops on the same frequency in search mode even more so with 1.05.01m and 1.01.05s and same happens with 1.03.01m paul any explanations its like its desensing and the signal is too weak for antenuator... sorry you cant hear me in the videos but that 1 frequency whipes the whole vhf hi band.... from 150-160mhz and causes p25 to have full signal then lose it when the pager kicks in... only happenes with 157.74 mhz... when active it loses all signal to the sds100 vhf hi band...

https://www.youtube.com/watch?v=Rnw0YjKBoQQ

 

[letarotor]

Is the modulation in NFM? I had accidentally, through some keystrokes, changed a modulation on a frequency to WFM and didn't realize it until I started getting traffic on the frequency and wondering what was going on with the sound. This may not be the issue at all but I thought I'd mention it just in case it does help anyone...

What is one to do when monitoring 159.3675 dmr and 159.435 keys through closecall on bcd996p2 and knocks the complete signal away from 159.3675 on the sds100?
Also 162.4mhz weather is ghosting onto 162.35mhz
and thats a week noaa channel
Will try to get video of both side bye side...

Wondering if instead of a set antenuator if there could be a user adjustable gain for the recieve implimented and would fix issues of desense...

Sent from my SAMSUNG-SM-G930A using Tapatalk

 

[WX4JCW]

Scanner reviews are great.

Review A: "VHF and UHF now come in 10x better!"
Review B: "VHF and UHF now having issues"
Review C: "VHF and UHF noise now gone"
Review D: "VHF and UHF now with strange noises"

I cannot wrap my head around the idea that a huge number of people lie for no apparent reason other than "fanboyism", and therefore I can only conclude that most are honest, and that some devices perform in a wildly different manner for different folks in different situations, while other devices work pretty much exactly the same no matter who is using them or where they are being used. Go figure. Only in the world of radio.

It could be a combination of things, I still can't wrap my head around people that constantly need to take a crap on the radio SMH


Sent from my iPhone 8 using Tapatalk Pro
Jason WX4JCW
XPR7550 - SDS100

 

[SCPD]

Is the modulation in NFM? I had accidentally, through some keystrokes, changed a modulation on a frequency to WFM and didn't realize it until I started getting traffic on the frequency and wondering what was going on with the sound. This may not be the issue at all but I thought I'd mention it just in case it does help anyone...

Sent from my SAMSUNG-SM-G930A using Tapatalk

No actually programming is NFM verified and no antenuator on

If I use the antenuator everything is dead silent all the time..................