Defective 536's

[N7CAS]

I am dead certain that my 536 is among that group that was defectively manufactured. I was one of the first recipients shortly after the product was available late '14.

It has NEVER functioned properly. I've been fighting this thing for more than a year now. Now it's 2016. Should have sent it back while it was still under warranty but I wanted to make sure it wasn't "operator error." Such a good Boy Scout.

I am thoroughly familiar with its operations; it just doesn't work. The audio is awful (highly, highly unreliable, unstable and sporadic). Other times it stops receiving entirely while some redundant scanners are fine (demonstrating that, no, the PD frequencies are not suddenly tombstone quiet for long periods of time).

And just for icing, the time/date on the display is always lost every time it's turned off, usually after being fed up by the horrible audio reliability.

Updates make no difference. I've been extremely patient. I hate this thing — especially for the money, especially for a product from a once great scanner manufacturer. Customer from Day One for decades, that's how dated/loyal I am. Or was.

UPMan says in a post on radioreference.com that Uniden is aware that there definitely were some defective units and is offering a flat-out exchange program. But the post is dated 2015. The unit itself was registered first thing out of the box, but I received NO communication from Uniden about any of this. I didn't see the UPMan post on radioref until now. This is not my life. It's a hobby. Yet an important one. Now what?

 

[fxdscon]

I
And just for icing, the time/date on the display is always lost every time it's turned off, usually after being fed up by the horrible audio reliability.

Now what?

https://www.uniden.com/product-information/bcdx36hp-repair-campaign

.

 

[darunimal]

Are the last 4 of the S/N below 2601, are you using or have you used an external speaker, was it amplified or not and back ext spkr or front headphone jack, have you reformatted the card yet. And then Clear User Data, how many sites for systems do you use at once and how long are their respective delay time(s). You do realize one click of the noob is one line in the menu when you scroll, there is no update to allow 2 or 3 clicks to equal one line. Uniden is offering to fix Real Time Clock (RTC) batteries and LED's to help rectify loss of clock and fading LEDs, they are not implementing a "Flat-Out Exchange Program," or at least not how I interpret that phase to mean (return old and get a new one). If you haven't tweaked your local P25 threshold settings to manual and adjusted it up or down, it maybe be difficult for the scanner in Auto-Mode to constantly switch and decode properly with multiple sites, and systems and conventional channels, lockout/disable all quick keys except 1 site and Manually adjust P25 settings. But only after you have reformatted with Fat32 and 32 kilobytes.

If you send me a copy of your SD Card I can put it in my scanner and see what's going on more clearly! Even better there seem to be a couple guys in your area that might be able to help with sites and system specifics.

 

[ofd8001]

Two Repair Campaigns were/are applicable.

One was to deal with an issue with the headphone jack affecting some units. This was where the owner registered for the repair with Uniden and was provided a shipping label. When Uniden got confirmation that the scanner was in the shipping pipeline, another scanner was sent to the owner so as to minimize downtime. Plus the warranty was extended to 3 years. The only communications from Uniden were posts on various websites like this.

The most recent one, still on-going, deals with the Real Time Clock battery. See https://www.uniden.com/product-information/bcdx36hp-repair-campaign

If it was me, I send the unit back in for the Real Time Clock battery issue and include a note about the other issues. Perhaps Uniden will take care of any issues while they are dealing with the Real Time Clock battery issue - I can see them doing so.

 

[garys]

In the clock repair campaign thread UPMan has said that if there are other issues, include a note and they will be addressed after the RTC issue is corrected. The reason for that is that the RTC repair line is separate from the regular repair line.

 

[sparklehorse]

It sounds to me like there are four possibilities here:

1. The radio is truly defective.

2. There is an issue with the SD card.

3. There is some issue with the programming causing problems.

4. The system you are having trouble with is simulcast P25, or some other type that is notoriously difficult to decode properly.

What system is it exactly, and what are the "redundant scanners" models that are receiving it just fine? With a little more information about the problem we might just be able to help you troubleshoot It.

As for the clock issue, did you have the scanner on continuously for 50 hours when you first got the scanner to properly charge the RTC battery? Also, if the RTC battery is truly toast, the current firmware allows you to just hit the Enter button when queried on re-boot, thereby bypassing the annoying clock reset procedure.

Are you still using the original SD card that was supplied with the radio? These seem to be common culprits for many 536/436 problems. A new, properly formatted, Class 10 SanDisk has fixed more than a few of these radios.

I understand your frustrations, and it is entirely possible the unit you have is just a lemon. Whatever the issue, hopefully we can help you resolve it, or Uniden will repair or replace it for you. A properly working 536 unit is actually is a very fine scanner, arguably the best one on the market at present. I think you will truly enjoy it once you have one that is working properly.

.

 

[sparklehorse]

The audio is awful (highly, highly unreliable, unstable and sporadic). Other times it stops receiving entirely while some redundant scanners are fine (demonstrating that, no, the PD frequencies are not suddenly tombstone quiet for long periods of time).

I should have asked about this as well. This sounds like the squelch threshold is set too high. Of course there could be many other causes, but this one is worth asking about, so please take no offense. If you have the squelch set higher than 3, or maybe 4, it can certainly cause the symptoms you describe. I always run my 436 and 536 at squelch setting of 2.
.

 

[N7CAS]

I can always count on this group to provide great insight and suggestions. I'll respond to individuals as soon as I have some time off (next week). Thanks again!!! Very cool!

 

[N7CAS]

In answer to the replies and questions in this thread, the date and time failure is indeed just the tip of the iceberg.

The 536 (S/N 375Z48000364) falls silent for long periods when my other scanners are receiving fine.

Most annoying is the 536's audio sporadically covered by a very loud "Chinese firecracker" sound where that last time it landed on the same Talk Group or channel it was fine.

Other times a low, rhythmic drumming sound, no less annoying but rather than being substantially louder than the "scanner traffic," it's at the same volume.

Further: No matter where I set the volume when the 536 lands back on the "channel" (doesn't matter whether it's conventional frequency or a Talk Group) that was at a good level before, it is often substantially disruptively louder or significantly lower in volume to the point of being unintelligible.

Moreover — and here's the really interesting part — that annoyance likes to switch between dispatch and units: dispatch (on the SAME channel or Talk Group) will be blasting and mobiles will be barely audible, or mobiles (on this SAME channel or Talk Group) will be loud and dispatch is inaudible.

And finally, any time I hold on the local Reno Police with the 536 — and this appears specific only to holding on RPD (other "holds" hold where they're supposed to) rather than hold there, it clears the RPD display and goes off to Elko County Sheriff, which is 230 miles from here. Needless to say, the scanner radius is set for my ZIP Code.

Other times, the 536 works just fine. Maybe it's bipolar.

The thing is this: This is not supposed to be a cheap POS.

A repeat customer, I bought a Uniden for a reason! Indeed, the comms are ALWAYS fine on my other scanners: A Radio Shack PRO-2006 for conventional, a Radio Shack PRO-2052 for conventional, another Radio Shack PRO-2052 for EDACS (since they can't do both at the same time), a Uniden BCD396T for conventional and EDACS, and a Uniden BCD436HP for conventional and EDACS. It's not the system. It's the scanner. You can see why I am disappointed in this scanner. It's just a source of grief.

I'm sending this thing in Monday after being directed by helpful folks here to Uniden's Repair Center. The BCD396T, BCD436HP and BCD536HP are all registered with Uniden and associated with my e-mail address.

Since I can't find my telepathy hat anywhere, one would expect that Uniden would have sent out an auto notification, an e-mail informing their product users below a certain serial number regarding the repair program rather than discovering it accidentally on radioreference.com. Again totally thanks to you folks — for which I am grateful! I need to check back here much more often.

Sorry for the length of the post.

 

[Voyager]

I suspect you have duplicate systems - perhaps some programmed as FM and others as NFM.

 

[AuntEnvy]

Aww man, I better get my recently purchased unit hooked up soon and hope this isn't one of the supposed defective series.

I did run it briefly when I got it and didn't notice anything but this is starting to sound like a "warmed-up" unit issue...

 

[N7CAS]

I suspect you have duplicate systems - perhaps some programmed as FM and others as NFM.

Good suggestion, Voyager! My area uses both FM and NFM, and if I manually programmed like I did decades ago that would be a possibility — indeed, I had made a mistake here and there back in those days.

But... both the 536's and 436's programs are downloads, and those downloads are the identical most recent database updates. The point being, the 436 has absolutely none of the infuriating problems that my 536 is a poster child for.

Hopefully Uniden will look at it (I'm including a note regarding the problems above) and not just send it back with the time-and-date fixed.

 

[sparklehorse]

For the volume issue, have you tried experimenting with the AGC setting, on vs off? Are you still using the factory supplied SD card, or have you replaced it with a new, properly formatted card? Are you using custom Favorites Lists, or scanning the full database using Zip code or some other location method? If you're scanning the database, try setting up a small, targeted Favorite List for RPD instead, see how well that works, or doesn't. If you download that exact same Favorites List and profile to both the 436 and the 536 you should get very similar results from each. This assumes using the same antenna, having the most recent firmware installed in each, and same squelch setting. If when set up identically like this, and using good SD cards, you still find the 536 to be inferior to the 436, then I'd say it's very likely you just have a bad 536.

Basically, everything you listed could potentially be caused by a bad SD card, or programming problems, or improper settings somewhere. Those are far more likely than a hardware issue. Using the 436 as a diagnostic tool should help you figure it out. But their setup must be as close to identical as possible, otherwise it's apples vs oranges.

.

 

[garys]

This is all conjecture on the part of N7CAS. I wouldn't put too much credence into it until more people crop up and say that they have similar problems. I've experienced nothing like it in my 436 or two 536s.

The only problem I have right now is that the large "VFO" knob on one of the 536s seems to be going flaky on me. I wouldn't start a thread on that declaring this an issue that UNIDEN HAS TO FIX just because one of my units has a problem.

Of course others would.

Aww man, I better get my recently purchased unit hooked up soon and hope this isn't one of the supposed defective series.

I did run it briefly when I got it and didn't notice anything but this is starting to sound like a "warmed-up" unit issue...

 

[RoninJoliet]

I have had my 996xt for three years and the big knob when turned sometimes does not turn the channels or the text as it skips like its wearing out, is that what you are referring too.....TY

 

[garys]

Pretty much. I'm hoping that the RTC fails in this scanner before the scroll knob fails completely.

I have had my 996xt for three years and the big knob when turned sometimes does not turn the channels or the text as it skips like its wearing out, is that what you are referring too.....TY

 

[AuntEnvy]

Yes garys

This is all conjecture on the part of N7CAS. I wouldn't put too much credence into it until more people crop up and say that they have similar problems. I've experienced nothing like it in my 436 or two 536s.

The only problem I have right now is that the large "VFO" knob on one of the 536s seems to be going flaky on me. I wouldn't start a thread on that declaring this an issue that UNIDEN HAS TO FIX just because one of my units has a problem.

Of course others would.

I'm trying not to get too worked up about it.

The good thing is I noticed, the serial# given, not sure if that's correct or not but both of mine are well below that number. The one I've been running at home (0700's) for the last few months is even further below the one I just got for mobile use (0900's) and I haven't had any problem with it.

 

[horizonscanner]

i agree..but i never hesitated to get 1 myself two weeks ago. That week was an experienced for my 1st scanner. I had 3 new 536 for the week. All had different problems..LCD, Firmware and the muffled audio on provoice. Amazon was helpful enough with my prime returns. So far the last unit is working fine though has muffled audio on digitals.. but other modes are fine. hope this scanner last for years.. Uniden refunded me for the provoice i purchased on defective units. So if you have a new unit bought, don't stop playing ... who knows ..

 

[N7CAS]

This is all conjecture on the part of N7CAS..

Sir! I am factually describing this unit's performance. I posted that description in hopes of attaining some suggestions and this forum never lets me down. And it's true I have no IDEA why its performance ever since I jumped at getting one back in March 2014, an early production, is so subpar.

As I stated before initially I thought it was "operator error." But indeed, I have a 436 as well, the same animal but in handheld mode, and I have has NO SUCH problems with the 436! Both are programmed identically, same download, same firmware/software. I was not trying to denigrate the brand, if that is how it appears. I'm sure the majority of the 536's are peachy. This one is not.

And now it's on its way back to Uniden.

 

[N7CAS]

Basically, everything you listed could potentially be caused by a bad SD card, or programming problems, or improper settings somewhere. Those are far more likely than a hardware issue. Using the 436 as a diagnostic tool should help you figure it out. But their setup must be as close to identical as possible, otherwise it's apples vs oranges.

.

Yes, sir, that's why everything is IDENTICAL between the 536 and my 436. Yet the 436 is stellar. Not a single problem with it ever! It would be ironic if it were just a faulty SD card in the 536. (That's why I love this forum: two or 40 heads are better than mine!). Then again the 536 is the first scanner I've had that had an SD card. I'm a bit behind the times, methinks, and I appreciate the helpful input of everyone.