BCDx36HP Firmware 1.22.00 Available

[UPMan]

1.22.00 Release Notes (06/01/2018)

Improved false TGID display on DMR systems
Modified LCN finder
Fixed an issue where avoided sites were being scanned

 

[iMONITOR]

And the hits keep on coming! Whistler could never follow in your footsteps. Thank you again Paul for all your work and support for the user community.

I just purchased my third x36 series yesterday. I now have a 436 and two 536's. Your excellent support had a big influence on my decisions.

 

[bravo14]

I updated the fw just 30 mints ago. I noticed the 1.21.00 a p25 UHF System I was getting more better signal and audio. Also no False ID on Cap+ system. 1.22.00 have no issues on Cap+ False IDs and I do notice signal strength on certain Freq's lost some signal.

 

[vocoder]

And the hits keep on coming! Whistler could never follow in your footsteps. Thank you again Paul for all your work and support for the user community.

I just purchased my third x36 series yesterday. I now have a 436 and two 536's. Your excellent support had a big influence on my decisions.

+1 on that! Uniden is rockin!
I am also on the way to purchase another 536, now that i know it has continued support

 

[scan-pa]

Thanks Paul. Keep up the great work. It is very much appreciated...

Sent from my SM-G935V using Tapatalk

 

[AC0RV]

I am curious about the LCN Finder modification. How was it modified ?


Hey thanks for the hard work.

 

[INDY72]

It was again having issues locking onto and rolling through DMR especially Cap+ systems especially with RAS enabled, which had been fixed on a previous FW and had been broken again by tweaks that fixed other things. Its tricky doing firmware tweaking, it can fix fracked things, and yet cause issues with things you ALREADY had fixed.

 

[GTR8000]

Doesn't address the Priority Scan issue on P25 Phase II systems:

https://forums.radioreference.com/u...priority-scanning-p25-phase-2-talkgroups.html

 

[pinballwiz86]

Thanks Uniden and UPMan! The firmware update is working great on my 436HP and 536HP.

 

[mrscanner2008]

UPMAN


Doesn't adress the 2 issues with CAPMAX https://forums.radioreference.com/u...an-logs-lcn-finder-problems-cap-max-tiii.html

 

[Ubbe]

And the hits keep on coming! Whistler could never follow in your footsteps.

They don't need to fix anything that isn't broken. DMR decoding has always been rock solid with no "ghost" TG's on the Whistler.

/Ubbe

 

[jonwienke]

They don't need to fix anything that isn't broken. DMR decoding has always been rock solid with no "ghost" TG's on the Whistler.

Not if RAS is involved.

Speaking of which, .22 not only broke the LCN Finder for CAP+ with RAS, but I'm not getting any reception at all on my local CAP+/RAS system. I have the 436 running LCN Finder, and the 536 holding on that system in ID Search mode, and I'm getting nothing at all.

I'm going to let thing run a few more hours and post a log.

 

[werinshades]

1.22.00 Release Notes (06/01/2018)

Improved false TGID display on DMR systems
Modified LCN finder
Fixed an issue where avoided sites were being scanned

I'm seeing an improvement in the Phase 2 UID's being displayed from version 1.21.00. I know it wasn't mentioned in the release notes and it has been a hectic weak with the release of Sentinel and the SDS100 so maybe it was overlooked? Hoping the debug logs I'm submitting through Houk are landing on the right desk...lol!

 

[Dreamflight767]

Hi:

Just want to make sure this update encompasses all the previous updates as well.

Thanks!

 

[freqseeker]

Yes.

 

[INDY72]

LCN Finder is indeed broken on DMR Cap+ systems. Again. Getting reception, but LCN FInder is just like it was back before FW .17 or .18 I think it was that fixed it? Works fine on Con+ and still doing good for NXDN. So we know it was some change made in FW .21 that popped it off kilter, and has not fixed it again yet. Am going to go back to FW .20 as that worked with no issues that I could find.

 

[melbournefan]

LCN Finder is indeed broken on DMR Cap+ systems. Again. Getting reception, but LCN FInder is just like it was back before FW .17 or .18 I think it was that fixed it? Works fine on Con+ and still doing good for NXDN. So we know it was some change made in FW .21 that popped it off kilter, and has not fixed it again yet. Am going to go back to FW .20 as that worked with no issues that I could find.

Yeah, I tried to search for LCN's on a Cap+ system from around 100 meters away and nothing on FW .21

I don't think there's a RAS system nearby (one did popup for the F1) but i'm just planning for the what if.

 

[Ubbe]

They don't need to fix anything that isn't broken. DMR decoding has always been rock solid with no "ghost" TG's on the Whistler.

Not if RAS is involved.

It works perfect with RAS in search and manual tune, no ghosting, but Whistler broke the RAS capability while in scan in a previous version.

/Ubbe

 

[jonwienke]

It works perfect with RAS in search and manual tune, no ghosting, but Whistler broke the RAS capability while in scan in a previous version.

Sounds like it's not "rock solid" then.

 

[kh6sz]

Maybe a dumb question, but how do you know a CAP system has RAS? Does it show something special either on the scanner or DSD+? Does it behave differently? Sorry if this has been asked and answered before.