Help me help you

[werinshades]

I can make it do it on both sds100 and 436hp. and there are numerous other posts that replicate the issue, look at the one just above here by Ubbe. Hit F then you can either press release Dept or hold Dept, either will make the message Site Hold off appear. then it either immediately come back on, or as soon as you turn the scroll knob it comes back. Then at some point with the exact same key sequence, sometimes the first time, sometimes the 5th time, it will clear and allow scrolling once again. I get you can't duplicate it, that's fine. But I can and I know how to use the scanners.. But thanks for trying

I've also tried to duplicate this for awhile now without success. I press the Function knob, press Site...Site Hold active, I then press Function again, press Site, Site Hold Off and scanner resumes scanning. What am I missing?

 

[epersson]

You are telling it to site hold. I am not. I am simply trying to scroll through the systems.

 

[werinshades]

You are telling it to site hold. I am not. I am simply trying to scroll through the systems.

Can you explain the steps you're using to do this?

 

[epersson]

Can you explain the steps you're using to do this?

Not again, look back. thanks everyone for the suggestions, but I have listed steps revs firmware, issues, over and over again. there are other records of this happening, look there as well.

 

[werinshades]

Not again, look back. thanks everyone for the suggestions, but I have listed steps revs firmware, issues, over and over again. there are other records of this happening, look there as well.

Possible this is user error and not firmware related?

 

[epersson]

Possible this is user error and not firmware related?

Nope.

 

[werinshades]

When holding on a channel, it defaults to scrolling CHANNELS. You have to press a key (System/Dept/Site) to scroll those. Now, it could be changed to default to scroll DEPARTMENTS, but then you would have to press CHAN to scroll channels. I believe the current scheme is more intuitive (as it works the same with other modes) and would be more commonly used vs scrolling departments. There is another possibility (scroll the last type pressed) but then you would never really know what you might scroll at any given time.

As was mentioned - just press the DEPT softkey if you want to hold or scroll departments.

P.S. When you are holding on a channel, you are not still scanning. When you are holding on a Department, you are still scanning - that is why the scroll knob changes direction as it does any other time you are scanning.

I think it was explained pretty well, unless you're doing something different?

 

[epersson]

I think it was explained pretty well, unless you're doing something different?

As I've said, I know how to use the scanners. ... OK one more time... if @JoeBearcat doesn't have any input this is a dead issue at this point.

There are pics a little earlier in this thread. Both sds100 and BCD436hp latest firmware. combination of conventional and trunked systems. when hold then try to scroll manually between systems (yes, I know I had to hit system button here), just scrolling it will lock on a trunked system with "site hold" displayed now it goes no further, just scrolls through that site. I hit Function and hit or hold dept/site button, get the message site unlocked, but it either locks up again right away, or as soon as I turn the knob it locks up again. Latest firmware. This seems like a firmware bug in these systems. any way to get it to stop locking?

 

[werinshades]

@JoeBearcat doesn't have any input this is a dead issue at this point.

I thought he did..I posted the previous responses? I've been working on this again and I'm not able to duplicate it still. I have trunking and coventional systems programmed and if I turn the function knob without pressing System, mine does not go into Site Hold. As I previously posted, I can put the scanner in Site Hold when following the current programming method. I went back a few pages and yes I see others have reported it so you're not alone. A firmware bug would be/should be happening in all the scanners following your instruction. It appears I'm not alone either in being unable to duplicate the issue. Could this be a symptom of another issue that's not firmware related? But...until it's addressed, you're right it's a dead issue and I would find a different way of scanning through systems.

 

[JoeBearcat]

46 pages later.....what actual requests have been addressed since this thread started in Jan 2021?

Hardware issues were address save one that will be ongoing. Currently software issues are being researched. Bugs will be in an upcoming stage and that is where the vast majority of issues reside, but bugs can be solved through firmware updates so they are not as sensitive as say a hardware issue that can only be solved through production. (most users can update their own firmware - most cannot perform repairs)

 

[JoeBearcat]

JB I know your swamped on tracing back all the past issues. For that we all thank you.

As one engineer to another I think your time would be best spent on getting the firmware updated on the SDS and 436/536 units. I am pretty sure many of the issues your tripping over will be fixed by updated firmware. If your guys are reading the code in the firmware properly I think they will find a couple of checks that are not executed or the command buffer gets full from user input. This last would be correctable by placing a one command completed at a time check. Possibly a on screen "be patient" or input overloaded remove last key sequence y/n option.

Technically I'm not a Uniden engineer, but I work with them. That said I'm sure you can appreciate the higher priority to fix hardware before firmware.

Most lag issues are caused by failing or corrupted SD cards.

 

[gary123]

LOL sorry about that jb . Either way your working in resolving these long time issues is welcome. I agree that hardware issues are a priority or at lease properly isolating the issue to a specific hardware fault is imperative all the firmware updates wont fix a bad switching transistor or bad capacitor.

I find myself in agreement on the SD card issue as well. Many different manufacturers have different read/write, latency and life cycle specifications. We both agree that it is not fair to expect the end user to have to understand or implement such technical details . All of these variations are dynamic and beyond the highly desired plug and play target Uniden is aiming for. There are several excellent threads here about SD related issues. I think in many of the cases it is not reasonable to expect Uniden or any manufacturer to be able to cover all possible cases.

I have thought about some of the recurring issues that seem to be possible hardware related. I was thinking of a series of simple yes/no questions based on each model that the membership can reply to similar to a pole. With that as a data base specific questions or tests can be performed by the user to help isolate the specifics of a failure.

 

[JoeBearcat]

I think we have a handle on all hardware issues except one which seems to be pretty rare. HQ is still working on that one.

I would like to see a report that the requested production change for the hum issue actually made it into the field.
(specifically not using masking on the screw vias so they properly conduct to ground)

Oh, and no need to be sorry. I appreciate the candor.

 

[oracavon]

I would like to see a report that the requested production change for the hum issue actually made it into the field.
(specifically not using masking on the screw vias so they properly conduct to ground)

Thanks for all your involvement and dedication to customer support. I will be buying an SDS200 as soon as that hum fix is confirmed on shipping units - that's the only thing holding me back. Please let us know as soon as you can verify that it made it into the field.

Thanks again.

 

[MStep]

I think we have a handle on all hardware issues except one which seems to be pretty rare. HQ is still working on that one.

I would like to see a report that the requested production change for the hum issue actually made it into the field.
(specifically not using masking on the screw vias so they properly conduct to ground)

Oh, and no need to be sorry. I appreciate the candor.

Why not just ask your company for a copy of the report?

 

[StaticDischarge]

If "My SDS200 HUM fix" is what they use (not using masking under the screws) it would be a grand compliment to issue a SDS100 and an SDS200 to the guy that came up with that fix for a very big "thank you for saving our A$$"...
Don't you think?
I'm not holding my breath though...

 

[Ubbe]

If "My SDS200 HUM fix" is what they use (not using masking under the screws)

Uniden probably ordered many thousands of those isolating film PCB boards when SDS200 production started that are in storage in the Vietnamese factory. It would be easier to just use that washer with a soldering tag to it, that they use to connect a wire from the main chassi to the front panel, and stick under a screw that holds the PCB and solder that wire to the nearest component leg that are grounded to the PCB.

Uniden might have designed the front panel to use separate grounds for analog and digital signals and making alterations to the grounding points might screw up the digital data and could make the read and writes to the SD card unreliable. Uniden needs the scanners designer to take a look at the issues to come to a solution that will not cause any future problems.

/Ubbe

 

[StaticDischarge]

Uniden might have designed the front panel to use separate grounds for analog and digital signals and making alterations to the grounding points might screw up the digital data and could make the read and writes to the SD card unreliable. Uniden needs the scanners designer to take a look at the issues to come to a solution that will not cause any future problems.

I've been running this same scanner since I came up with My Hum Fix and it is still using the original SD card. Absolutely no issues besides the firmware issues everybody else has.
Also, I have yet to read anything pertaining to corrupt data of any kind from those that have applied my fix and if they have it mainly came down to OE (operator error) or simply a bad card.
Now you must take into consideration that "My Hum Fix" was posted to the forum on Oct 28, 2019 and I had it applied to my scanner roughly two months prior to that posting due to extensive testing to make sure my fix would not cause any issues, and I found none.
So if they did use separate grounds as you state, they made a huge mistake.
No, as I've stated before I think that this was a simple oversight that no one at Uniden looked at or considered.

 

[drdeputy]

I've been running this same scanner since I came up with My Hum Fix and it is still using the original SD card. Absolutely no issues besides the firmware issues everybody else has.
Also, I have yet to read anything pertaining to corrupt data of any kind from those that have applied my fix and if they have it mainly came down to OE (operator error) or simply a bad card.
Now you must take into consideration that "My Hum Fix" was posted to the forum on Oct 28, 2019 and I had it applied to my scanner roughly two months prior to that posting due to extensive testing to make sure my fix would not cause any issues, and I found none.
So if they did use separate grounds as you state, they made a huge mistake.
No, as I've stated before I think that this was a simple oversight that no one at Uniden looked at or considered.

I used this post/method just over a year ago and still have the pre and post audio to show the difference in processor sound/hum. No issues whatsoever. I certainly wouldn't recommend my adaptation to a beginner, but I used a very light touch with a Dremel wire brush tool to remove the lacquer. It gave me a better and more consistent result than scraping. Again, no issues whatsoever with reception or anything else.

 

[bravo14]

Not sure if this was brought up on Fire Tone Out. I was wondering if a L/O can be added? Say if if you're doing a search and tone goes out for a station you already have comes up but hear other tones after that 1st tone alerted if they are paging out more than 1 station for major call.