SDS100/SDS200 Tax Day Update (1.10.00)

[mule1075]

AFAIK, there is no such thing as a three finger reset on the x36HP or SDS models.

Correct

 

[policefreak]

I tried reverting back to 1.07.02/1.02.00 and had worse performance so I updated back to the 1.10.00/1.02.00 firmware. Since updating back I have been experiencing erratic behavior on my SDS100. My local P25P2 system is missing transmissions and showing a poor RSSI compared to before I tried the experiment. The scanner shows 1.10.00/1.02.00 as the installed firmware, but it is not behaving as such. What's stranger is that I let the scanner sit overnight, and upon initial start up it was performing like normal until I entered the menu, then the erratic behavior started again.

To fix, I have tried reverting back and forth through multiple firmwares with no success. I also tried formatting a new SD card and using that, and the erratic behavior is continuing. I thought a filter setting changed, but I am showing the same filter (W-INV) as was successful before the experiment. It seams like a hardware issue, though I don't know it this is possible just by switching firmwares. Could the sub have failed during one of the firmware changes?

Has anyone experienced anything like this, or have any suggestions? Thank you.

So before you reverted the firmware, did you possibly have a different filter set on your P25P2 system that is now behaving erratically? Because maybe all you need to do is upgrade to the new 1.10.00/1.02.00 firmware again, and play with the filters on your system. They could reset when you downgraded and then upgraded again.

 

[Ubbe]

What do you mean by "three finger reset"?

Holding down buttons 2-9-DEPT while turning on the scanner, the display will show "All memory clear" if you manage to do it successfully, will restore to factory mode and will also clear the SD card of any user settings and favorite lists, so remember to first make a scanner read and then save using Sentinel. Do this reset as a precaution after a firmware change. Upgrading are probably handled correctly, or everyone would get into problems, but downgrading could have issues if memory are not cleared out and restored to scratch.

/Ubbe

 

[Jeff19]

Ubbe - 2-9-DEPT does nothing upon start-up.

I was working with 1.10.00/1.01.05 which was going ok. I was trying to receive aircraft when I discovered that the screen was showing a transmission received, but there was nothing audible. I put the sub back at fw 1.02.01 and the aircraft were audible (having changed no other settings). I'm guessing I corrupted my sub somehow.

policefreak - I wish filters was my problems, but I've confirmed that I'm using the same filters before the experiment. My only hope at this point is that a new fw comes out that overrides all of this, or Uniden can give some insight.

Thanks

 

[seth21w]

Jeff go into settings on scanner and make sure you are on the latest firmware update through sentinel then go into settings and reset the scanner and then write to scanner and see if this resolves everything also I am running filter off on everything now.

 

[StaticDischarge]

My two pennies..
I just moved from on side of Michigan to the other and without a computer handy. I saw the 2-9-DEPT reset on this thread and tried it.. Wouldn't you know... It worked on my SDS200..
In my business we call that "OE" (Operator Error) if the technician can get it to work and the operator cannot...

 

[MisterLongwire]

2-9-DEPT probably works on the "old" firmware. IT IS HOWEVER RECOMMENDED TO UPGRADE TO THE LATEST AND GREATEST. As for Ubbe, he seems to think it works the same as the 536, which from my experience isn't so

 

[StaticDischarge]

2-9-DEPT probably works on the "old" firmware. IT IS HOWEVER RECOMMENDED TO UPGRADE TO THE LATEST AND GREATEST. As for Ubbe, he seems to think it works the same as the 536, which from my experience isn't so

OK so it seems I have to drop one more penny...
I have the latest firmware installed..

 

[KN6SD]

Happy Tax Day!

Apply the update using Sentinel, as usual (for public releases).

1.10.00 Main (4/15/2019)
This firmware applies the following enhancements and bug fixes:

• Fixed the issue of false TGID displaying during site hold.
• Modified the valid condition of EDACS system ID.
• Improved DMR OFT reception.
• Improved NXDN48 (OFT) reception.
• Slightly improved the clarity of analog and digital voice

Any new updates on the way??? I own both the SDS100 and the SDS200, Great radios..

Great job Uniden...

 

[buddrousa]

We have not seen an update while UPMan has been sick and I do not see one coming until he is back here and at work.

 

[radio3353]

We have not seen an update while UPMan has been sick and I do not see one coming until he is back here and at work.

I am a little confused by this. Unless Upman comes back to work we will never see another update?

 

[KN6SD]

We have not seen an update while UPMan has been sick and I do not see one coming until he is back here and at work.

UPMan has been down for awhile, I hope he makes a comeback both professionally and personally...

 

[trentbob]

UPMan has been down for awhile, I hope he makes a comeback both professionally and personally...

Yep, there is a thread in the Uniden Tavern regarding his blog and updates on his status called Any updates for Paul (UPMan)?

 

[seth21w]

I've got a couple bug reports for sds200 on 1.10.00 if I set audio amp off time more than 100ms the audio isnt cutting off after it resumes scanning it works fine on 100ms and sometimes on 500ms but 1 second on up it doesnt stop the amp. I want 2 sec as it doesnt effect key beeps. Also dmr cap+ and conventional dmr is not decoding with anything less than the strongest of systems 70rssi or lower. Please help someone!

 

[sklpl]

SDS100E (European version) just got the update to 1.10.06 (sub 1.02.01) today.

 

[trentbob]

SDS100E (European version) just got the update to 1.10.06 (sub 1.02.01) today.

Could you tell us how long you have been using the radio with the previous firmware?

Would you mind sharing with everyone your opinion about the update after you've run it through its paces.

Thanks.

 

[sklpl]

The latest available firmware for "E" version was 1.07.04 (1.02.00) - until yesterday. I was having it installed since early March. I'm using the scanner mainly for tracking DMR one-frequency and EDACS systems. The only issues I am having with SDS100E is lack of audio AGC, quite poor sensitivity and audio quality on analog and on EDACS sometimes UID is not dispalyed at all. No noticeable changes on new software as for now.

I also wonder what is added/fixed in 1.10.06 when comparing to 1.10.00.

 

[safmig]

indeed since the last update for Europe, the sds100e always has a bad and metallic sound it is not very sensitive compare to the 3600 xlt short nothing new and we still wait tétra !!!

 

[Jeff19]

I tried reverting back to 1.07.02/1.02.00 and had worse performance so I updated back to the 1.10.00/1.02.00 firmware. Since updating back I have been experiencing erratic behavior on my SDS100. My local P25P2 system is missing transmissions and showing a poor RSSI compared to before I tried the experiment. The scanner shows 1.10.00/1.02.00 as the installed firmware, but it is not behaving as such. What's stranger is that I let the scanner sit overnight, and upon initial start up it was performing like normal until I entered the menu, then the erratic behavior started again.

To fix, I have tried reverting back and forth through multiple firmwares with no success. I also tried formatting a new SD card and using that, and the erratic behavior is continuing. I thought a filter setting changed, but I am showing the same filter (W-INV) as was successful before the experiment. It seams like a hardware issue, though I don't know it this is possible just by switching firmwares. Could the sub have failed during one of the firmware changes?

Has anyone experienced anything like this, or have any suggestions? Thank you.

My scanner is on its way back from repair after the firmware roll-back issues I was seeking help on. The work order indicated Q1/Q2 were replaced. I am hopeful because the scanner was exhibiting some symptoms others have described with the Q1/Q2 issues, but I am skeptical because others also have had to send their scanners in several times to get it working. I'm not sure how a firmware roll-back could have blown Q1/Q2, but that may explain why everyone's suggestions on reformatting, etc.were not successful. It arrives tomorrow and I'll post another update.

 

[Jeff19]

My scanner is on its way back from repair after the firmware roll-back issues I was seeking help on. The work order indicated Q1/Q2 were replaced. I am hopeful because the scanner was exhibiting some symptoms others have described with the Q1/Q2 issues, but I am skeptical because others also have had to send their scanners in several times to get it working. I'm not sure how a firmware roll-back could have blown Q1/Q2, but that may explain why everyone's suggestions on reformatting, etc.were not successful. It arrives tomorrow and I'll post another update.

My scanner has been working flawlessly since receiving it back from repair.