Running NXDN on a 536HP and 436HP here in LA on railroad (Los Angeles Metro Line). Good audio quality. Thanks Uniden.
NXDN Upgrade for BCD436HP and BCD536HP Now Available!
- Thread starter UPMan
- Start date
- Status
Correct on the i0.
In fairness, it's not that Whistler's NXDN is bad. It's that they don't trunk NXDN. Within the limitation of what it does, it works.
This is the same as the criticism of previous models not working as well as they could on LSM systems. They weren't designed to decode LSM properly, and never claimed to do that. Likewise, the Whistler was never designed to trunk DMR or NXDN, and they never claimed to do that. They COULD (unlike LSM), but they don't. That was a choice they made to keep the cost down.
The improvement you hear is the result of actually following the trunk system as opposed to scanning it conventionally. Yes, you hear the replies better actually trunking the system since you don't have to hunt for the next active voice frequency.
Fidgety9996
Member
This update is a big disappointment. It does not seem to show IDs on "encrypted" calls. It could easily decode them as AOR DV1 does.
NXDN4800 seems not to work at all when it is on frequency you cannot input into uniden. Uniden has 5 places after the dot for frequency - you need 6 in many cases.
Maybe that is also/or only the problem of the NXDN Very Narrow systems.
Great disappointment for 30 bucks.
I will have access to some kenwood hardware will perform some tests.
NXDN4800 seems not to work at all when it is on frequency you cannot input into uniden. Uniden has 5 places after the dot for frequency - you need 6 in many cases.
Maybe that is also/or only the problem of the NXDN Very Narrow systems.
Great disappointment for 30 bucks.
I will have access to some kenwood hardware will perform some tests.
You lost me there. The ability to receive a whole new digital mode for the price of dinner out and you complain about how you cannot see who you cannot hear? lol
fourthhorseman
Member
good you got it right away then,,rather than wait till sentinel updates and had to pay 60.....u dodged a bullet there.,,whew...
Fidgety9996
Member
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.
Paul,
Thanks for Uniden sending out the new NXDN Firmware Version! Do We need to wait till Monday for the RR database update for NXDN? Or can Uniden push an update so we can use radio reference to update our scanners,
Thanks for Uniden sending out the new NXDN Firmware Version! Do We need to wait till Monday for the RR database update for NXDN? Or can Uniden push an update so we can use radio reference to update our scanners,
You have to program NXDN manually for now. Sentinel support is not available yet. Hence the 30 dollar price. As soon as support for Sentinel is available the price goes to 60 dollars.
There will be (at some still un-released time a new Sentinel release), some changes required to implement NXDN, so NO, not next Monday.
Paraphrasing Paul above, but it's neem mentioned several times.
Paraphrasing Paul above, but it's neem mentioned several times.
So it seems I was right...the release of NXDN from Uniden was because they wanted the scanners to properly trunktrack, and they wanted to get it right. I guess good things truly do come to those who wait. I don't have any real NXDN where I am just yet...but I have a feeling Metro North will be doing some NXDN down the road. 90 bucks to upgrade all three radios was a bargain indeed.
Drumbum
Member
That means the upgrade price,for the SDS-100 will be 60 plus the DMR price over the $699 asking, hmmm
Sent from my VS995 using Tapatalk
I am not seeing OTA aliases on the system I am monitoring. At least not on the 436HP I'm using. On the DSD+ set up a few feet away, I am seeing the aliases. Which I take to mean that the Uniden implementation doesn't process that yet.
Same with me - thanks for the confirmation.
I'd say it's a pretty minor thing to gripe about considering we got "full" (with trunking) support otherwise.
Still, it'd be nice to implement at a later date. I guess we'll see what comes...
I'd say it's a pretty minor thing to gripe about considering we got "full" (with trunking) support otherwise.
Still, it'd be nice to implement at a later date. I guess we'll see what comes...
I'm pretty happy with it so far. The only other odd thing I've seen is that sometimes the scanner will stop on a TG, but there is no audio. Meanwhile, the audio can be heard on DSD+.
I seem to remember that there was something similar with Motorola trunking way back. I forget the details, but the scanner wouldn't process audio if it stopped on a TG midway through a conversation. From watching the display, I also note that when this happens, there is no UID displayed on the scanner, just the TGID.
If I get time later today, I'll manually program in a different NXDN system and see how that one plays.
Definitely worth the money.
I seem to remember that there was something similar with Motorola trunking way back. I forget the details, but the scanner wouldn't process audio if it stopped on a TG midway through a conversation. From watching the display, I also note that when this happens, there is no UID displayed on the scanner, just the TGID.
If I get time later today, I'll manually program in a different NXDN system and see how that one plays.
Definitely worth the money.
I'm glad to manually program a few local NXDN just to have the opportunity to enjoy this new upgrade. Will be glad when Sentinel or ARC536 gets updated as I hate manual labor. Next Monday would be great.
That's known as "late entry". I haven't had enough time to explore if my radio is joining conversations on late entry properly or not.
i have entered the correct key. but its telling me its incorrect? do i have to enter anything else?
- Status
Similar threads
BCD436HP/BCD536HP:
NXDN Upgrade key best price for BCD536HP?
