New SDS-100 incorrectly identifying talk groups

[ks4ec]

I just received my spanking new SDS 100 and I love the sound. It is taking me a while to get used to not having to enter EVERYTHING, I have to stop overthinking things.
One thing that is really driving me nuts is that is constantly misidentifies talk groups. One min EMS talks to a hospital on the correct talk group, then the next min they are talking on LECom 1. Buses appear on hospital groups, COP units appear on COP1 like they are supposed to then later show up on a hospital group.

I have paid attention to the displayed talkgroup number and it is correct for what is displayed, but not for what I am hearing.

FYI, This is on the Palm Beach County P25 Phase I and II system and it is a very big, busy, simulcast system. That's why I spent the extra for this radio as I heard it is the best for these systems. I know that many of the PBSO talkgroups are encrypted and I will never hear them, but I would like to have the "In the clear" groups work right.

I cant be sure but it seemed to be working OK before I upgraded the firmware.

Is there something I can look at to help diagnose this problem?
I have an SDRPlay receiver and unitrunker, I was going to look at that this weekend to see if maybe there was something tricky going on with the system.

Thanks for all your help

 

[mharris]

I just received my spanking new SDS 100 and I love the sound. It is taking me a while to get used to not having to enter EVERYTHING, I have to stop overthinking things.
One thing that is really driving me nuts is that is constantly misidentifies talk groups. One min EMS talks to a hospital on the correct talk group, then the next min they are talking on LECom 1. Buses appear on hospital groups, COP units appear on COP1 like they are supposed to then later show up on a hospital group.

I have paid attention to the displayed talkgroup number and it is correct for what is displayed, but not for what I am hearing.

FYI, This is on the Palm Beach County P25 Phase I and II system and it is a very big, busy, simulcast system. That's why I spent the extra for this radio as I heard it is the best for these systems. I know that many of the PBSO talkgroups are encrypted and I will never hear them, but I would like to have the "In the clear" groups work right.

I cant be sure but it seemed to be working OK before I upgraded the firmware.

Is there something I can look at to help diagnose this problem?
I have an SDRPlay receiver and unitrunker, I was going to look at that this weekend to see if maybe there was something tricky going on with the system.

Thanks for all your help

This happened to me, seemingly randomly after a database update. I used the "reset user data" in the menu and that fixed the problem.

 

[harryshute]

I just received my spanking new SDS 100 and I love the sound. It is taking me a while to get used to not having to enter EVERYTHING, I have to stop overthinking things.
One thing that is really driving me nuts is that is constantly misidentifies talk groups. One min EMS talks to a hospital on the correct talk group, then the next min they are talking on LECom 1. Buses appear on hospital groups, COP units appear on COP1 like they are supposed to then later show up on a hospital group.

I have paid attention to the displayed talkgroup number and it is correct for what is displayed, but not for what I am hearing.

FYI, This is on the Palm Beach County P25 Phase I and II system and it is a very big, busy, simulcast system. That's why I spent the extra for this radio as I heard it is the best for these systems. I know that many of the PBSO talkgroups are encrypted and I will never hear them, but I would like to have the "In the clear" groups work right.

I cant be sure but it seemed to be working OK before I upgraded the firmware.

Is there something I can look at to help diagnose this problem?
I have an SDRPlay receiver and unitrunker, I was going to look at that this weekend to see if maybe there was something tricky going on with the system.

Thanks for all your help

Yes it is the new firmware. There is info on the thread about the new firmware that started last Friday. I'm hoping for new firmware today.

 

[ks4ec]

Yes it is the new firmware. There is info on the thread about the new firmware that started last Friday. I'm hoping for new firmware today.

I looked and cant find the thread you mentioned, can you give me more info about the thread you are talking about.

 

[PapaG]

I have also been dealing with firmware malfunction for a week now. Hoping for firmware Friday also.

 

[ks4ec]

Is there a way to downgrade the firmware to the last version???

 

[RRR]

I have also noticed UID's sometimes incorrectly being displayed as well....

 

[harryshute]

This should be the thread.

SDS Firmware Issue

 

[budevans]

Is there a way to downgrade the firmware to the last version???

Yes. Do a Firmware Update using Sentinel. That will take you back to the last released production release.

 

[kruser]

Yes. Do a Firmware Update using Sentinel. That will take you back to the last released production release.

That will only work if Uniden posts a version of the last good FW with a Version higher than the bad 1.09.02 version that is now current.
If you are already running the bad new version, a FW update will do nothing other than tell you that you are already running the latest version.

 

[ks4ec]

Looks like going back a version in the firmware solved the problem... As an IT guy, I should know better then to upgrade to the latest shiny new firmware as soon as it comes out! Rob

 

[RRR]

I would do that, but I believe Uniden will introduce a new FW that will address these issues.

 

[Hit_Factor]

Looks like going back a version in the firmware solved the problem... As an IT guy, I should know better then to upgrade to the latest shiny new firmware as soon as it comes out! Rob

It's a hobby, not a livelihood. Live dangerously.

73, K8HIT
Icom: IC-7300, IC-PW1, ID-5100A, ID-51A Plus 2, IC-R30, Hytera PD782G, Kenwood TH-D74, Uniden SDS100, DVMega, SDRplay RSPduo

 

[budevans]

Looks like going back a version in the firmware solved the problem... As an IT guy, I should know better then to upgrade to the latest shiny new firmware as soon as it comes out! Rob

Rob,
You're not alone. By the way, I'm a retired Director of IT. Can't give up playing with the new tech.