NXDN Upgrade for BCD436HP and BCD536HP Now Available!

Status
Not open for further replies.

Jake68111

Member
Joined
Feb 19, 2010
Messages
408
Location
Morris, IL. (Grundy County)
I

ilken

Guest
Not Working

Not working here I'm still not sure if it's something I've done wrong see the photograph I tried to program these frequencies in every way I could think of still I don't hear any voice or any control Town noise at all when programming the site manually
 

Attachments

  • Screenshot_20180327-143111.jpg
    Screenshot_20180327-143111.jpg
    33.5 KB · Views: 587

Sanscanman

N5WRF
Premium Subscriber
Joined
Oct 5, 2001
Messages
319
Location
Acworth, GA
when you programmed the site in.. did you do an LCN Find on the site to determine the Correct Number and order? I had this issue with a VHF site, all programmed up, but not a lick of traffic even tho it locked on to the control channel. once I searched for the LCN order and let the scanner update it in the radio everything came in fine.
 

bearcat

Member
Joined
Dec 24, 2002
Messages
737
Not working here I'm still not sure if it's something I've done wrong see the photograph I tried to program these frequencies in every way I could think of still I don't hear any voice or any control Town noise at all when programming the site manually
That picture shows your are doing a custom search. I think you are just locked on an NXDN control channel. It is showing the data coming over the control channel. You need to program all of the frequencies with the correct LCNs as an NXDN trunked system. You could press AVOID on that control channel frequency and see if you hear the voice conventionally on other channels on that system.
 
I

ilken

Guest
That picture shows your are doing a custom search. I think you are just locked on an NXDN control channel. It is showing the data coming over the control channel. You need to program all of the frequencies with the correct LCNs as an NXDN trunked system. You could press AVOID on that control channel frequency and see if you hear the voice conventionally on other channels on that system.

Right its a custom search and I did program and all the frequencies on the radio reference page including the sites that are too far away from me it still does not stop on any channels and I do not hear any voice it does stop on the control Channel when I do custom search but no voice still not sure what's going on
Although I do not remember seeing anything for LCN when I program the site and departments I will look again
 

bearcat

Member
Joined
Dec 24, 2002
Messages
737
Right its a custom search and I did program and all the frequencies on the radio reference page including the sites that are too far away from me it still does not stop on any channels and I do not hear any voice it does stop on the control Channel when I do custom search but no voice still not sure what's going on
Although I do not remember seeing anything for LCN when I program the site and departments I will look again
I did notice that another post reported that NX4 will not decode voice in Custom Search. So that is possibly the issue.
 

jonwienke

More Info Coming Soon!
Joined
Jul 18, 2014
Messages
13,409
Location
VA
That individual was locked on a control channel, not a voice channel.
 

Voyager

Member
Joined
Nov 12, 2002
Messages
12,059
I was wrong. I did not have LCN roperly assigned. After running LCN Finder and finally finding all LCNs the scanner shows the ID's but only for a split second.

Did you HOLD on that TG? If so, it should show the UID. Of course you still won't hear any audio.

But, the scanner will not stop on encrypted channels since you cannot hear them. It continues looking for TGs you CAN hear.
 

Voyager

Member
Joined
Nov 12, 2002
Messages
12,059
One thing I have seen is that audio processing is faster on the 436HP than on the computer running DSD+.

Of course a scanner is a scanner and a computer running DSD+ with two dongles is NOT a scanner. Both have their advantages.

Any time you have an SDR involved, you are adding delay for the frequency processing. The 436 has no such delay since it's using a discriminator.

The audio decoding delay is likely about the same for both units.
 

Voyager

Member
Joined
Nov 12, 2002
Messages
12,059
I'm in agreement about NXDN "LCN" being replaced with "Channel Number"

Hmmmm....

...debating "LOGICAL Channel Number" vs "Channel Number".

Is it really necessary to replace LCN with CN or are people smart enough to understand they are the same thing?
 

bearcat

Member
Joined
Dec 24, 2002
Messages
737
That individual was locked on a control channel, not a voice channel.
No it was post #85 on the FW Thread. He is not getting decode on quick search on conventional freq NX4. I have not had any hits on my NX4 freqs since that post so I cannot verify. NX9 is working fine in quick search and that it what he reported also.
 

kc5igh

Member
Premium Subscriber
Joined
Feb 22, 2014
Messages
726
Location
Velarde, New Mexico
"Incorrect key" message?

I've purchased the key and entered it in the scanner (dashes and all), and I'm getting a message that says "Incorrect key entered. Press any key." I've re-entered the key three times and received this message each time.

It's been a while since I've upgraded my '436 (DMR was the last one), but I can't think of anything I'm doing wrong. We're not supposed to enter the "Checksum" info, are we?
 

bearcat

Member
Joined
Dec 24, 2002
Messages
737
I've purchased the key and entered it in the scanner (dashes and all), and I'm getting a message that says "Incorrect key entered. Press any key." I've re-entered the key three times and received this message each time.

It's been a while since I've upgraded my '436 (DMR was the last one), but I can't think of anything I'm doing wrong. We're not supposed to enter the "Checksum" info, are we?
You should only need the checksum to buy the update. It is not needed for the key entry. Just a guess. Is there any chance you ordered the using the wrong serial #. I do not think that is possible due to the checksum verification.
 

hiegtx

Mentor
Premium Subscriber
Joined
May 8, 2004
Messages
11,393
Location
Dallas, TX
You should only need the checksum to buy the update. It is not needed for the key entry. Just a guess. Is there any chance you ordered the using the wrong serial #. I do not think that is possible due to the checksum verification.
If the scanner you are trying to add NXDN to already has the DMR key (presuming you added that), you should be able to log into MYUNIDEN, and click on the "All My Scanners" link. If the scanner is in your list, just click on the link for 'Purchase NXDN Key". I have two 436HPs, so I have to make sure to choose the one I update.

As bearcat noted, if the scanner is already registered for you, you don't need to re-enter the serial #, ESN, or checksum.

Take a close look at groups on the keys. I typo'd one of mine the first try when I misread a character.
 

kc5igh

Member
Premium Subscriber
Joined
Feb 22, 2014
Messages
726
Location
Velarde, New Mexico
You should only need the checksum to buy the update. It is not needed for the key entry. Just a guess. Is there any chance you ordered the using the wrong serial #. I do not think that is possible due to the checksum verification.

I received an email notice from Uniden that said I'd successfully generated a key for my scanner, and the key was included in the email, as usual.

I checked the "myUniden" account again, and it's still giving me the option to "Purchase NXDN Key," so that may mean something. I'm afraid to launch the whole purchase process again, because I don't want to be charged for two keys.

Something's missing. Most likely pilot error on my part, but I can't think what I could have done wrong.

Any other ideas?
 

bearcat

Member
Joined
Dec 24, 2002
Messages
737
If the scanner you are trying to add NXDN to already has the DMR key (presuming you added that), you should be able to log into MYUNIDEN, and click on the "All My Scanners" link. If the scanner is in your list, just click on the link for 'Purchase NXDN Key". I have two 436HPs, so I have to make sure to choose the one I update.

As bearcat noted, if the scanner is already registered for you, you don't need to re-enter the serial #, ESN, or checksum.

Take a close look at groups on the keys. I typo'd one of mine the first try when I misread a character.
You are exactly right! I forgot all about the scanner already being registered. Excellent Point!
 
Status
Not open for further replies.
Top