SDS100/SDS200: Firmware 1.05.01M Public Beta

[maus92]

Ohio MARCS, various Northern KY Police and Fire, such as Campbell County and Boone County, Airports such as KCVG, KLUK, KHAO, I67.

So on MARCS, you are saying your 436 and SDS are equivalent? Are you within the service footprint of MARCS? Most other reports claim a marked improvement on this particular P25P1 simulcast system.

Boone public safety is not P25 nor a 700/800 simulcast system, so it makes sense the 436 and SDS are equivalent.

Campbell public safety is EDACS and conventional, so again, 436 and SDS performance would be more or less equivalent.

The point is that both the 436 and SDS perform comparably on conventional or non-simulcast systems. Where the SDS makes a difference is on digital P25 simulcast systems, particularly when within their service footprints where simulcast distortion and co-channel interference is a major issue. Making blanket statements without context doesn't help people decide what will work for them in their particular situation.

 

[belvdr]

So on MARCS, you are saying your 436 and SDS are equivalent? Are you within the service footprint of MARCS? Most other reports claim a marked improvement on this particular P25P1 simulcast system.

Boone public safety is not P25 nor a 700/800 simulcast system, so it makes sense the 436 and SDS are equivalent.

Campbell public safety is EDACS and conventional, so again, 436 and SDS performance would be more or less equivalent.

The point is that both the 436 and SDS perform comparably on conventional or non-simulcast systems. Where the SDS makes a difference is on digital P25 simulcast systems, particularly when within their service footprints where simulcast distortion and co-channel interference is a major issue. Making blanket statements without context doesn't help people decide what will work for them in their particular situation.

You're confused about what I'm trying to say. I was making a comment to W2GLD regarding his bleedover on VHF.

Besides MARCS, the other systems I listen to are simply conventional analog VHF (no EDACS). I don't notice any issue with the analog performance of the SDS100, whereas W2GLD said he is having issues.

 

[maus92]

You're confused about what I'm trying to say. I was making a comment to W2GLD regarding his bleedover on VHF.

Besides MARCS, the other systems I listen to are simply conventional analog VHF (no EDACS). I don't notice any issue with the analog performance of the SDS100, whereas W2GLD said he is having issues.

You're right. I only saw what you wrote in the message I replied to. I didn't see his message quoted or replied to, so I took your message as a standalone statement. sry.

 

[belvdr]

You're right. I only saw what you wrote in the message I replied to. I didn't see his message quoted or replied to, so I took your message as a standalone statement. sry.

No worries. To be honest, I should have quoted the person I was replying to. Had I done that, there would be no confusion.

 

[werinshades]

Wearinshades, how do I get the debug files from the scanner? Pm me if you don't wanna put it here. please,thanks.

1) Power off
2) Hold the Avoid key, and keep holding it, while powering back on ... keep holding Avoid until your favorite lists load, and you hear three beeps
3) Menu -> Settings -> Set Debug Log Mode -> SD Card (File)

Then reproduce the issue you're experiencing. When done, return to the menu and turn debug logging off.

You'll then the log file(s) in the "debug" folder on the SD card (when connected to your PC via USB in Mass Storage mode).

 

[slylingus]

Noticeable difference n The Victoria RMR In Aus

http://info.uniden.com/twiki/pub/PartnerWeb/SDS100-Beta/SDS-100_V1_05_01M_V1_01_05S.zip

Release Notes:
1. Modified the voice channel termination method for P25 Phase 1 systems
2. Modified the TGID check method on voice channel grants for DMR systems

Hi I just updated my SDS100 firmware to the public betta
A noticeable difference on reception on the new Vic RMR network here in Australia. Thanks UpMan
OF Topic sorry there are many avid uniden scanner users here how about letting
us updating our units to DMR currently geocached on payment options.
Loving the SDS

 

[W2GLD]

You're confused about what I'm trying to say. I was making a comment to W2GLD regarding his bleedover on VHF.

Besides MARCS, the other systems I listen to are simply conventional analog VHF (no EDACS). I don't notice any issue with the analog performance of the SDS100, whereas W2GLD said he is having issues.

I would direct you to my posting with videos I shot highlighting the issues with VHF bleedover, etc but as I search RadioReference.com; I see my post was yet again deleted. Anyway, here are the videos again; seems that the post showing receive issues keeps getting deleted by Uniden fanboys. For the record, simulcast performance is excellent, we're talking in terms of conventional VHF and UHF as well as DMR conventional issues and continuous SD-Card write errors even after replacing the SD-Card, formatting, etc. I've thrown my hands up because reporting issues here is a huge waste of time when your posts keep getting deleted when you highlight an issue; it was the same B.S. when people reported issues with the BCD436HP when it first launched. Lesson learned, NEVER BUY UNIDEN FIRST RELEASE PRODUCTS EVER AGAIN; I wish I had listened to my own advice with this product, oh well, it sits on the shelf and perhaps one day Uniden will make it right; in the meantime I use the ICOM IC-R30 and IC-R8600 for conventional monitoring and leave the SDS100 to collect dust unless I'm listening to the MPSCS system. The ICOM's scan at 200-channels per second anyway and actually stops on D-Star, NXDN, and P25 conventional traffic; if it only did DMR, but I have a Whistler TRX-1 that works flawlessly for that anyway. Okay here are the video links; sorry don't have the time or the effort to embed them here as they'll just get deleted shortly after posting anyway.

https://www.dropbox.com/s/dqiffo1no7kly2y/IMG_0682.MOV?dl=0
https://www.dropbox.com/s/6ld2i1mbftf46mz/IMG_0685.MOV?dl=0
https://www.dropbox.com/s/b0z59gd2tjkze11/IMG_0686.MOV?dl=0

The actual fire dispatch is coming from 154.010 MHz with a DPL of 047, you will note that traffic is coming through on 146.520 MHz with the inverse DPL of 023 and also on 155.475 MHz with no CTCSS or DPL and the distortion is awful. This happens on the stock antenna as well as any other antenna tested; also, we're in the sticks, no near by transmitters, etc and no other radio I own has this issue, including the BCD436HP or a cheap RTL SDR dongle; this is isolated to the SDS100 and all firmware versions since its release. Also, some UHF conventional channels are bleed over with an EDACS trunking system that's over 13 miles away; you can regularly hear the control channel mixing in the receiver. Another issue is I have a DMR One Frequency System programmed with several local repeaters and hotspots in it; each site has a color code assigned (yes the correct one), cannot scan this group as it will never stop on traffic; if I manually hold the channel it will eventually decode but if I just manually punch in the frequency in search mode without a color code, the SDS100 decodes immediately and shows the correct color code (yes the same one I programmed). These are just a few of the problems we've identified.

 

[kc5igh]

Rubbish if you use a different antenna so you can receive said systems it is indeed a fair test. Some people only use outdoor antennas on their scanners so to say using a different antenna is not fair is ridiculous.

I think the important point is to use the same antenna to gauge performance differences between firmware versions (the "variable" in this equation), which I'm pretty sure you and everyone else here are already doing.

Eliminating as many variables as possible when making performance comparisons is always a good idea.

 

[KevinC]

I would direct you to my posting with videos I shot highlighting the issues with VHF bleedover, etc but as I search RadioReference.com; I see my post was yet again deleted. Anyway, here are the videos again; seems that the post showing receive issues keeps getting deleted by Uniden fanboys. For the record, simulcast performance is excellent, we're talking in terms of conventional VHF and UHF as well as DMR conventional issues and continuous SD-Card write errors even after replacing the SD-Card, formatting, etc. I've thrown my hands up because reporting issues here is a huge waste of time when your posts keep getting deleted when you highlight an issue; it was the same B.S. when people reported issues with the BCD436HP when it first launched. Lesson learned, NEVER BUY UNIDEN FIRST RELEASE PRODUCTS EVER AGAIN; I wish I had listened to my own advice with this product, oh well, it sits on the shelf and perhaps one day Uniden will make it right; in the meantime I use the ICOM IC-R30 and IC-R8600 for conventional monitoring and leave the SDS100 to collect dust unless I'm listening to the MPSCS system. The ICOM's scan at 200-channels per second anyway and actually stops on D-Star, NXDN, and P25 conventional traffic; if it only did DMR, but I have a Whistler TRX-1 that works flawlessly for that anyway. Okay here are the video links; sorry don't have the time or the effort to embed them here as they'll just get deleted shortly after posting anyway.

https://www.dropbox.com/s/dqiffo1no7kly2y/IMG_0682.MOV?dl=0
https://www.dropbox.com/s/6ld2i1mbftf46mz/IMG_0685.MOV?dl=0
https://www.dropbox.com/s/b0z59gd2tjkze11/IMG_0686.MOV?dl=0

The actual fire dispatch is coming from 154.010 MHz with a DPL of 047, you will note that traffic is coming through on 146.520 MHz with the inverse DPL of 023 and also on 155.475 MHz with no CTCSS or DPL and the distortion is awful. This happens on the stock antenna as well as any other antenna tested; also, we're in the sticks, no near by transmitters, etc and no other radio I own has this issue, including the BCD436HP or a cheap RTL SDR dongle; this is isolated to the SDS100 and all firmware versions since its release. Also, some UHF conventional channels are bleed over with an EDACS trunking system that's over 13 miles away; you can regularly hear the control channel mixing in the receiver. Another issue is I have a DMR One Frequency System programmed with several local repeaters and hotspots in it; each site has a color code assigned (yes the correct one), cannot scan this group as it will never stop on traffic; if I manually hold the channel it will eventually decode but if I just manually punch in the frequency in search mode without a color code, the SDS100 decodes immediately and shows the correct color code (yes the same one I programmed). These are just a few of the problems we've identified.

Hmm...I find no posts of yours deleted in at least the last 6 months.

Are you possibly referring to this post of yours...???

https://forums.radioreference.com/u...-05-00m-1-01-05s-open-beta-6.html#post2982732

 

[W2GLD]

Hmm...I find no posts of yours deleted in at least the last 6 months.

Are you possibly referring to this post of yours...???

https://forums.radioreference.com/u...-05-00m-1-01-05s-open-beta-6.html#post2982732

Yes sir, that is the one I was looking for and for some reason this and several other posts do not return in my search results or my profile as even existing so thanks for locating and highlighting this one for the group; however, this still doesn't explain other posts which have been deleted with regards to the SDS100 and I know I'm not the only one who has been subject to this either, there's a Facebook group running seperate from RadioReference.com where this has been discussed at length. Anyway, I'm not trying to start anything; I just want Uniden to make it right and deliver on their promises, how they messed up conventional operation I have no idea and what's more concerning is it seems everyone is just focusing on simulcast operation and calling it good when it's not a good receiver at all presently.

 

[mule1075]

Yes sir, that is the one I was looking for and for some reason this and several other posts do not return in my search results or my profile as even existing so thanks for locating and highlighting this one for the group; however, this still doesn't explain other posts which have been deleted with regards to the SDS100 and I know I'm not the only one who has been subject to this either, there's a Facebook group running seperate from RadioReference.com where this has been discussed at length. Anyway, I'm not trying to start anything; I just want Uniden to make it right and deliver on their promises, how they messed up conventional operation I have no idea and what's more concerning is it seems everyone is just focusing on simulcast operation and calling it good when it's not a good receiver at all presently.

Since the sds100 was released in June and Kevin says he none of you're posts have been deleted in the past 6 months. Either you are looking in the wrong place or something else is happening.

 

[mikewazowski]

No posts that are on-topic concerning the SDS100 have been deleted.


I would venture a guess that if the member has difficulty finding his own posts regarding the topic, he might be having the same difficulties finding the "deleted" posts. Could just be a quirk in the search function.


End of discussion.


Back to discussing the firmware update. Thanks.

 

[seth21w]

I figured we would have got a new beta to try today. Guess not 436 got one

 

[werinshades]

I figured we would have got a new beta to try today. Guess not 436 got one

436/536 beta release is 1.24...released on same say as 1.05M for SDS100.

 

[seth21w]

436/536 beta release is 1.24...released on same say as 1.05M for SDS100.

We've been on 1.05.01M for 2 weeks now I think. But I've had to roll back to 1.05.00 due to reception issue.

 

[werinshades]

We've been on 1.05.01M for 2 weeks now I think. But I've had to roll back to 1.05.00 due to reception issue.

Ok, you mentioned 436 received a new beta firmware today. Submit debug files if you're having issues. For me, this firmware has been the best. No hurry to change anything. I was out all day...analog, P25, CAP+ for the 3 primary systems I was listening to without issue. Stock antenna, no GPS modification, CTCSS, Color Codes, NAC codes all programmed in correctly. Not doubting your findings, but debug files are reviewed. 1.04 was better than 1.05S for me. Debug files submitted for both firmware updates, 3 weeks later all is good in my world. It goes a long way to try and help.

 

[seth21w]

Ok, you mentioned 436 received a new beta firmware today. Submit debug files if you're having issues. For me, this firmware has been the best. No hurry to change anything. I was out all day...analog, P25, CAP+ for the 3 primary systems I was listening to without issue. Stock antenna, no GPS modification, CTCSS, Color Codes, NAC codes all programmed in correctly. Not doubting your findings, but debug files are reviewed. 1.04 was better than 1.05S for me. Debug files submitted for both firmware updates, 3 weeks later all is good in my world. It goes a long way to try and help.

I will reload the beta and try and catch my problem but overall the 1.05.00 public is stable for me.

 

[Pat]

I apologize as I haven't had a chance to install this beta release myself, but has anyone running this release had issues with the display backlight not turning off during trunking discovery mode? I'm currently running the 1.05 release and I've noticed that the backlight does not turn off while in trunking discovery mode after a hit is received with the backlight mode set to open squelch.

 

[vocoder]

dmr error correction selection

Upman,

In a future firmware release, could we please have an option to select or not select error correction?
I think this would help with dmr ras and other funky radio system oddities
When the scanner shuts down error correct, it makes it harder to rx dmr and others
Thanks and as always thanks for the continued firmware improvements!

73, john

 

[vocoder]

Upman,

In a future firmware release, could we please have an option to select or not select error correction?
I think this would help with dmr ras and other funky radio system oddities
When the scanner shuts down error correct, it makes it harder to rx dmr and others
Thanks and as always thanks for the continued firmware improvements!

73, john

We are missing quite a bit of comms on cap+ systems