BCDx36HP v1.18.00 Update

[KevinC]

As noted by others, NXDN alias decode rate is 99.999-100% now.

 

[03msc]

I think 99-100% alias rate is probably as good as it's going to get - I have a Kenwood NX-700 that I used to monitor a local NXDN repeater (until they encrypted) and it would show the alias (i.e. "caller ID") about 99% of the time. Sometimes if the signal was poor (i.e. the transmitting radio was on the fringes) or it was a real quick transmission it would miss the alias but most of the time it got it. All that to say...that's how a radio performed so if the scanner is getting 99% then I'd say that's great.

 

[k3fs]

Alias ID over the air works fine. The unit ID number flashes, and then the alias is displayed. Unfortunately, on the recordings the unit ID number displays most of the time. Meaning that the alias ID is not being shown on the recordings most of the time.

 

[Dreamflight767]

Howdy:

My scanner has been in the shop. When I get it back, do I need to install each update, or will the most recent updates incorporate the ones prior?

Thanks!

 

[wbswetnam]

Howdy:

My scanner has been in the shop. When I get it back, do I need to install each update, or will the most recent updates incorporate the ones prior?

The most recent will incorporate all previous updates, too, I believe.

 

[Voyager]

The most recent will incorporate all previous updates, too, I believe.

It does. You only need apply the latest one. In fact, Sentinel will only let you install the latest one.

As for the UID in replay of recordings, I've seen the same thing with other fields. If a user with a different CTCSS starts talking, only the first one decoded is shown (even if that were a false decode for a CSQ user). It would be nice if the replay were 'active' - showing the data in 'real' (delayed) time as well as the time and date received.

Reportedly, that info is in the recordings.

But, if that doesn't happen I'm not going to have a meltdown about it.

 

[ur20v]

But, if that doesn't happen I'm not going to have a meltdown about it.

You are in a distinct minority, it seems 😂

 

[UPMan]

Channel info (TGID, Alias, etc.) is the first thing recorded into the audio file. If the information is missing or incomplete at the time the info is written, it can't be added. Also, if two users run together (i.e. no carrier drop) the scanner sees it as still being a single transmission, thus it is all in one file, so the changed info can't be updated.

 

[garys]

This probably explains what I am seeing. I'll do more testing when I get home.

Channel info (TGID, Alias, etc.) is the first thing recorded into the audio file. If the information is missing or incomplete at the time the info is written, it can't be added. Also, if two users run together (i.e. no carrier drop) the scanner sees it as still being a single transmission, thus it is all in one file, so the changed info can't be updated.

 

[pinballwiz86]

This probably explains what I am seeing. I'll do more testing when I get home.

Try not to scan the entire kitchen sink while trying to record a NXDN system. Perhaps you are missing the beginning of transmissions.

 

[mcjones2013]

I mentioned this in the 1.17.00 thread, but it's still occuring on the 1.18.00 firmware.

When I hold on a Connect Plus system that has multiple sites programmed in my favorite list, it will scan through all the sites for that system, but after it has scanned through all the programmed sites, it will move on to the first system programmed in the favorite list, instead of holding on the system it was told to.

VIDEO that shows the problem: https://www.youtube.com/watch?v=tnx5wdrksxg

The programming for the favorite list I am using is included in this attachment (which I posted in the previous thread): https://forums.radioreference.com/a...043082-bcdx36hp-update-1-17-00-businesses.zip

Quote from the previous thread that better explains what I'm trying to from Jay911:

Everybody who's replied to you so far has apparently missed the bolded part of your quote above.

This is indeed a bug - once you hold on a system, as you depicted in your video, the scanner should not move off that system in any way.

I remember this bug from years back - it was in one of the HomePatrol models, but I can't recall if it was the HP series or the x36 series. I was reasonably sure it was quashed, though.

For those who are following this sub-thread:

User has multiple systems in his FL. Let's call them systems 1, 2, 3, and 4 for the sake of argument.

User holds on system 3 by pressing SYSTEM twice while it is on-screen during the scan process.

Scanner holds on system 3 and makes one pass through scanning each site that is in range.

Scanner then moves to system 1, still in system hold mode.

This is a problem with the logic in the "have I scanned all the sites in this system, if yes, then move on to the next system" part of the scanner's code. If system hold is on, it should return to this system, not move to another system.

 

[u2brent]

I downloaded your file and gave it a go.

It does not exhibit the same behavior your experiencing, seems fine on my 436.

Have you tried downloading your file and trying it in a new fl?

Just a thought..

 

[Voyager]

I suspect it might have something to do with reception inclusive, so anyone not in his area might not see the issue unless they have a Con+ system on the same frequency(-ies).

 

[k3fs]

Alias ID information displaying on the recordings is not an issue of another user keying up in most cases. When the radio first stops on a transmission it shows the unit ID for a split second and then shows the alias information. The recordings only show the unit ID number when this happens as Bearcat had mentioned.

 

[Voyager]

You must have missed the answer.

https://forums.radioreference.com/2926998-post68.html

 

[kevino]

FW 1.18 Update: I monitored two NXDN4800 Trunked systems today for several hours. The hanging TG with no audio is gone. The Alias tags are appearing about 100% of the time on one system and about 99% of the time on the other. I also ran the LCN finder on one system with 7 freqs. It found 6/7 with two minutes. I determined which freq it did not find and started monitoring it conventionally on another radio. There was no voice activity on that freq for over an hour or more. So that being said LCN finder would never find that one anyway. So I would say the LCN finder is working very well also.

I have not seen any other adverse effects with 1.18 (so far)

1.18 for me is working great.

Updated firmware in my 436 to 1.18, still hanging up on random(?) TGs w/no audio or RIDs when in ID Search mode on trunked N48 system.

 

[u2brent]

Idea

Updated firmware in my 436 to 1.18, still hanging up on random(?) TGs w/no audio or RIDs when in ID Search mode on trunked N48 system.

Create a new department named "False TG's".
Add the offending TG's to that department.
Then avoid each offending TG or avoid the whole department.
Add new "false tg's" as they appear..

Resume Scanning....

There may never be a 100% fix.

 

[jonwienke]

Create a log and post it so that the issue can be investigated. Otherwise getting it fixed is gouing to be nearly impossible.

 

[werinshades]

Create a log and post it so that the issue can be investigated. Otherwise getting it fixed is gouing to be nearly impossible.

Creating one now for the same system. Where do I send it?

 

[jasonhouk]

Creating one now for the same system. Where do I send it?

Zip and upload here if size allows. If not message me and I'll make sure to get it the proper Uniden personnel.

Houk

Sent from my Moto G (4) using Tapatalk