BCD536HP Noise on Remote Audio Test

[UPMan]

We aren't able to duplicate the issue, but have isolated possible causes down to 4 areas. To check, we've made 4 test updates. If you are experiencing the issue (noise after the end of digital transmissions when remote monitoring), we'd appreciate it if you would check with each of the test version s and let us know which one(s) fixed the issue.

To test, copy the target update into the scanner's firmware folder, then reboot the scanner.

(One at a time...)

http://info.uniden.com/twiki/pub/PartnerWeb/Firmware/BCD536HP_V1_16_01.bin
http://info.uniden.com/twiki/pub/PartnerWeb/Firmware/BCD536HP_V1_16_02.bin
http://info.uniden.com/twiki/pub/PartnerWeb/Firmware/BCD536HP_V1_16_03.bin
http://info.uniden.com/twiki/pub/PartnerWeb/Firmware/BCD536HP_V1_16_04.bin

 

[mule1075]

Awesome thanks will do when I get home around noon.Thanks

 

[W4ELL]

I will try these ASAP... thank you!

 

[nosoup4u]

I'm running 01 and 02 right now on 2 scanners. Maybe we should split them up so we can figure it out faster.

 

[W4ELL]

I'm running 01 and 02 right now on 2 scanners. Maybe we should split them up so we can figure it out faster.

Great idea... unfortunately, I won't be home until later today.

 

[jonwienke]

I'm going to give each version an hour of runtime and see what happens.

 

[nosoup4u]

I got the noise on #2, I did not get it on 1 so far.

 

[NYRHKY94]

FYI - I just got the buzzing sound (quite loud) testing with #1. Running a stream through Radio Feed via Wifi on the 536. Took about 12 minutes into the test. Switching to #3 shortly.

 

[nosoup4u]

I hear it on 3

 

[NYRHKY94]

Like nosoup4u, I just heard a "very loud" example of the noise after testing with #3 for 9 minutes.

 

[W4ELL]

I came home for lunch and updated both my 536...

I am running FWs 01 and 04... I have already heard buzzing on 01.

Still monitoring 04... no buzzing so far:
http://ellismike.hopto.me:5001/stream.m3u

 

[jonwienke]

I didn't hear any buzz on #1, switching to #4, since no one else has mentioned hearing the buzz on that one.

 

[nosoup4u]

#4 has been good for me for the last hour.

 

[W4ELL]

I think 04 is the winner... so far.

 

[nosoup4u]

I agree, #4 has been good so far for me as well.

 

[W4ELL]

I think I am willing to call version 04 the fix. I would have heard the buzzing by now and haven't heard a peep.

Thanks to Paul and the engineers for the quick turnaround on this.

 

[UPMan]

Engineering wakes up in about 3 hours...so I'd keep it on 4 if you can and let us know if the good luck sustains.

 

[jonwienke]

I'm running 4 with no issues so far.

Over 4 hours with no buzz.

One oddity, and I'm not sure if this is a ProScan problem or a firmware problem:

I have recording turned on in ProScan. It works great, except for Search With Scan / Close Call Hits transmissions. I hear them just fine in ProScan, but a lot of them do not get recorded--maybe 50% or more. Transmissions from every other system and department record just fine, but Search With Scan / Close Call Hits traffic is recorded only intermittently.

AFAIK this started around the time 1.16.00 came out, and the issue is present in 1.16.00, 1.16.01, and 1.16.04.

I connect to ProScan via Wi-Fi.

 

[jonwienke]

Apologies for the crappy video quality, but here is an example:
https://1drv.ms/v/s!ApJIS-l4xqPtgvE7nhBPnt2akXCMVw

The first transmission in the conversation is recorded, but several subsequent ones are not.

 

[Ubbe]

It's all related to the same source of problem, the initial problem with analog channels falsely indicating it had carrier (probably also missed analog conversations and affected digital as well), remote command strings not indicating that conversations start or end. The interupt that detect a state change of a carrier are hard to break but the routines that use it might have.

The introduction of NXDN could have caused a stack overflow and some pointers and values are flushed down the toilet.

/Ubbe