BCD436HP/BCD536HP Firmware Upgrade Wish List

[unpltd]

I would like Close Call hits to get rid of the stupid first screen that inform you of a close call hit, and go directly to the screen that shows frequency, CTCSS/DCS. I would also like the scanner to look up the hit info in the database and display the geographically nearest match. So if I get a CC hit on 160.2300MHz (the CSX road channel in my area), the hit screen will be nearly identical to the normal scan screen, except "Close Call Detected" is displayed, or perhaps the Close Call icon could flash:


Close Call Detected
Railroads

CSX

CSX - Road - all lines
160.2300 MHz NFM
CTCSS/DPL Info (if applicable)


If there is no nearby match for the frequency in the database, then it should have the save prompt at the bottom of the screen:

Close Call Detected

160.2300 MHz NFM
CTCSS/DPL Info (if applicable)

Save Frequency?

Close Call would be a lot more useful if it used the database to tell you what your Close Call hit was.

"BCD536HP v1.05.01 Revision Notes
This firmware version includes the following updates, enhancements, and bug fixes:
Supports Remote-Control over Wi-Fi
Allows updating of the Wi-Fi unit firmware directly through the scanner.
When Close Call hit is found, no longer prompts to press any key.
Fixed the issue that the SD-Card file system is broken when connected to a Macintosh computer"

Note: this is only for the BCD536HP at this time.


BCD536HPFirmwareUpdate < UnidenMan4 < TWiki

 

[rtuchmayer]

Wish list for BCD536HP

Two things would be helpful:
1) WPA2 Enterprise option for WiFi
2) A wired ethernet connectivity option

 

[XTS3000]

I would like Close Call hits to get rid of the stupid first screen that inform you of a close call hit, and go directly to the screen that shows frequency, CTCSS/DCS. I would also like the scanner to look up the hit info in the database and display the geographically nearest match. So if I get a CC hit on 160.2300MHz (the CSX road channel in my area), the hit screen will be nearly identical to the normal scan screen, except "Close Call Detected" is displayed, or perhaps the Close Call icon could flash:





Close Call Detected

Railroads



CSX



CSX - Road - all lines

160.2300 MHz NFM

CTCSS/DPL Info (if applicable)





If there is no nearby match for the frequency in the database, then it should have the save prompt at the bottom of the screen:



Close Call Detected



160.2300 MHz NFM

CTCSS/DPL Info (if applicable)



Save Frequency?



Close Call would be a lot more useful if it used the database to tell you what your Close Call hit was.

It will never happen because Optoelectronics has the patent on this "technology". The only way for Uniden to avoid patent infringements is to have the user press a button to view the CC Hit.

Not sure how long Optoelectronics patent is valid through.

 

[Gilligan]

It will never happen because Optoelectronics has the patent on this "technology". The only way for Uniden to avoid patent infringements is to have the user press a button to view the CC Hit. Not sure how long Optoelectronics patent is valid through.

Thanks for answering this question. I have always wondered if this was the case and who actually owned the patent.

 

[XTS3000]

Two things would be helpful:

1) WPA2 Enterprise option for WiFi

2) A wired ethernet connectivity option

In hind sight, I'm sure Uniden wished they had added or included a wired option.

However, they wanted the scanner to be available to be used in wireless Ad-hoc mode, and that can't happen with a wired setup.

So are you saying the 536 doesn't support basic WPA2 connections?

 

[unpltd]

I'm pretty sure it does, or did anyway. My home wifi is all WPA2 and I had mine connected before the update.

 

[UPMan]

It will never happen because Optoelectronics has the patent on this "technology".

Their patent expired. As we issue updates, this will be included.

 

[XTS3000]

Their patent expired. As we issue updates, this will be included.

I knew it would expire, but didn't know it had already expired. Great news to hear!

How about throwing the XT owners an update for CC in the future. That shouldn't be hard at all, remove a few lines of firmware code and done.

 

[UPMan]

This will probably happen eventually, but I would imagine that my priorities and your's would align in terms of where to apply engineering resources, right now.

 

[henrygb]

I miss the quiet days on the forum ...

When playing the recorded audio, the time was recorded should appear in the screen. I see that neither the escanner or the remote control software this is possible

 

[fourthhorseman]

When enabling/disabling QK's ,,instead of only displaying QK 1 ON or OFF...maybe add a line to display the tagged name of the list..
Would make,for me things easier..Especially since these radios have such expansive storage set ups.

 

[UPMan]

With the exception of FLQK's, the same QK can be assigned to multiple lists (SQK, DQK, CQK). In that case, which name should be displayed?

 

[fourthhorseman]

Hmm....Didnt take that into consideration,
I was thinking FLQK at a minimum.

 

[Minus1]

Date &amp; Time format of recordings

Can we please have the date and time shown with the correct format for recordings?

ISO8601 defines the international date time format as yyyy-mm-dd hh:mm:ss

Nothing that am aware of defines a format as yyyy-mm-dd_hh-mm-ss which is illogical and inconsistent.

Using an underscore in the middle is just bizarre and iiritating.

 

[SCPD]

Can we please have the date and time shown with the correct format for recordings?

ISO8601 defines the international date time format as yyyy-mm-dd hh:mm:ss

Nothing that am aware of defines a format as yyyy-mm-dd_hh-mm-ss which is illogical and inconsistent.

Using an underscore in the middle is just bizarre and iiritating.

You do realize the American date format is .. mm/dd/yyyy .. so be thankful.

 

[Minus1]

You do realize the American date format is .. mm/dd/yyyy .. so be thankful.

At least the rest of the world is spared that! But it shouldn't be that difficult to let users choose whatever format they want.

 

[jonwienke]

Can we please have the date and time shown with the correct format for recordings?

ISO8601 defines the international date time format as yyyy-mm-dd hh:mm:ss

Not going to happen because colons are illegal characters in filenames. Spaces are also illegal filename characters in some OSs. Dashes and underscores are the only universally usable delimiter characters usable in filenames in all operating systems.

 

[mancow]

Ooh the close call update plan is great news. I've tended not to use it due to that annoyance.

 

[Gilligan]

I'm SO happy about the Close Call updates pending Definitely looking forward to having that fixed and I'd like to see it not only applied to the XT versions but going back to all of the scanners. I still have a 246T that I'd love to have that fixed on.

 

[Minus1]

Not going to happen because colons are illegal characters in filenames. Spaces are also illegal filename characters in some OSs. Dashes and underscores are the only universally usable delimiter characters usable in filenames in all operating systems.

What is shown to the user does not have to be the filename, the firmware could quite easily convert it to a more user-friendly format.