NXDN... maybe never?

[SOFA_KING]

Me too...money waiting to be spent if they would get off their butts. I'd also like to see System Fusion and D-STAR. Basically, I would like an all-mode scanner. Isn't that what we all want? Plug a frequency in, and hear whatever mode is transmitted with full information displayed. And of course the ability to limit transmissions to specific parameters you may only want to hear, when being selective matters.

So, what's the hold up? Not enough talent at Uniden to do this, and do it in short order?

Phil

 

[RRR]

Really? I suspect the query/point the OP was making is that the only way you can manually 'tune' to a specific frequency is by adding it into the scanner as a [manually] stored channel. You can't directly enter a frequency in VFO mode (via the keypad, or via a search/pause). The closest you'll get is to run a search and try hit on the frequency, but even then you have to increment up/down with the keypad to reach the right frequency: I can tell you it's pretty tedious as the step size can't be changed. As stated earlier in this thread, I too find it a joke to pay good money for a scanner in 2017 when it doesn't even have the basic features of a scanner I had back in the 1980's - and even then, that was a fraction of the price. The TRX really is only useful for scanning known channels - not searching.

Sighhh..... ok:

Page 27 of the TRX-1 handbook states; Manual programming; Enter conventional frequency

1- Press MENU to access main menu

2- Scroll to and select "PROGRAM MENU" then "ADD CONV FREQ"

3- Simply write over an existing frequency or hit "Skip" to clear. Using the alphanumeric keypad or the /\ or \/ buttons, enter the desired frequency. Press SEL when finished.

4- Scroll to "SAVE CHANGES" then press "SEL"

5- Press "MENU" to return to the main menu.

I just did it on mine, and I programmed a variety of Analog, NXDN and DMR freqs on the fly by hand. Sorry you are having such problems with it.

 

[racingfan360]

So nothing new to learn from your post then....as I've already acknowledged, the only way to tune to a specific frequency is to add it manually as a stored memory channel. It takes at least 5 steps to do it. And you have to hope the step size in the bandplan is right for the frequency you want to monitor.

I'll let others judge whether directly tuning to a specific frequency with their other brand scanners is as complicated as that for a Whistler TRX: the equivalent on a Uniden BCDx36HP is as simple as CHAN/MOD, type in the frequency, then CHAN/MOD.

Anyway, perhaps we can get back on thread, see if Uniden will add NXDN to a more flexible scanner....

 

[n2pqq]

And then we have the forgotten HP-2 > still waiting for DMR

 

[SOFA_KING]

Not me. I said before that the HP-2 had a better chance of getting DMR and PV before the x36 got any additional digital modes.

Phil

 

[goodmore]

NXDN is very quiet in my area. A few rail systems are listed in the data base for using it as well as few private businesses. Most of it I assume happens during the morning shift when I am working myself. I have the Whistlers and to be honest I just don't have the interest in listening to it.

 

[mrscanner2008]

After 3 months that the NXDN has been released at Whistler,
I have no hope of seeing Uniden come out also with the NXDN,
I am very disappointed that uniden leave us in the ignorance
And I'll have to turn to Whistler to listen to the NXDN.

 

[werinshades]

I'm starting to wonder if Uniden simply has no intention of offering an NXDN upgrade, and are happy to let us speculate about the future when in fact they have no intention of offering it.

I follow the trials and tribulations on the Whistler Forums in regards to NXDN and trunking. AggieCon's reports seem to lean towards Whistler doesn't seem to trunk track NXDN systems, while others report they are trunking. Then of course encryption is always a possibility and all this could be for nothing. Like you, I'd enjoy the challenge like we did with MotoTRBO and DMR systems. I'm really not sure what Uniden is going to do here. We speculate on this issue, but based upon what Whistler users are experiencing, monitoring a NXDN trunking system in trunking mode seems to be a sticking point. Could this be the issue with the delay, or are the Uniden folks trying to obtain licensing rights similar to what they had to do to perfect MotoTRBO systems? I'm by no means disappointed with the x36p series of scanners, but I admit the challenge finding new systems intrigues me during "quiet" times on the scanner...when not too much is going on. Hopefully, we'll have an answer in the near future.

 

[racingfan360]

Whistler have now added a Tune Mode as part of their latest firmware release (and I think that's been 3 releases since the last time Uniden offered any updates). This now plugs a significant gap in the TRX range's capabilities, and I know the lack of it was putting many people off purchasing a Whistler.

I guess that means another chunk of folks who want NXDN will simply give up waiting for Uniden to do anything, and sink their $$$'s into the 'other' scanner now (?)

 

[werinshades]

Whistler have now added a Tune Mode as part of their latest firmware release (and I think that's been 3 releases since the last time Uniden offered any updates). This now plugs a significant gap in the TRX range's capabilities, and I know the lack of it was putting many people off purchasing a Whistler.

I guess that means another chunk of folks who want NXDN will simply give up waiting for Uniden to do anything, and sink their $$$'s into the 'other' scanner now (?)

For me personally, MotoTRBO has been more beneficial for my listening needs. I'm aware I have a few NXDN systems close by, and not sure if they are encrypted so making the jump and purchasing another $500 scanner doesn't make sense. I know others have different needs and if NXDN is what you need more, by all means make the jump. I find it hard to believe that the Uniden engineers aren't working on something or another Update Day like they've had in the past. P25 simulcast can always be improved, tweaking the MotoTRBO a bit as well as offering a pay-as-you-go NXDN add on would not surprise me. I would gladly pay an additional $50 for a NXDN upgrade then purchasing another scanner. Meanwhile...the scanner is working well, and don't have any complaints. Actually...just started playing with the record feature a little more and trying to figure out how to convert my saved Windows Media Player files so I can play them back and save them on my computer. Always learning more here.

 

[garys]

The x36HP scanners have a lot of features the Whistlers don't, so I'd never trade one for the other. I might trade a 996P2 for a Whistler, but frankly the lack of third party software weighs heavily against that too. I like OOS system that Whistler uses, but again, not enough to put up with EZScan.

For the record, I don't like Sentinel all that much either, but ARC536 works great for 90% of my programming needs.

Like some other people have commented, I'm pretty confident that Uniden is working on a NXDN upgrade. Maybe they're just more interested in getting it right than getting it fast.

Of course every time there is a "Uniden doesn't offer a feature, wah, wah, wah" thread, Uniden comes out with it. Just like every time there is a "Uniden has abandoned the x36HP line because they won't fix X, wah, wah, wah" thread Uniden comes up with a fix for the problem.

See people just aren't happy unless they can be unhappy.

 

[buddrousa]

I have 8 Uniden scanners running on PROSCAN recording audio, logging TG's Logging UID's and logging frequencies and and 2 tone page outs. Show me where and I own TRX-1 TRX-2 PRO668 and a PRO18 where I can do the same setup plus control them remotely like I can my Unidens.

 

[werinshades]

The x36HP scanners have a lot of features the Whistlers don't, so I'd never trade one for the other. I might trade a 996P2 for a Whistler, but frankly the lack of third party software weighs heavily against that too. I like OOS system that Whistler uses, but again, not enough to put up with EZScan.

For the record, I don't like Sentinel all that much either, but ARC536 works great for 90% of my programming needs.

Like some other people have commented, I'm pretty confident that Uniden is working on a NXDN upgrade. Maybe they're just more interested in getting it right than getting it fast.

Of course every time there is a "Uniden doesn't offer a feature, wah, wah, wah" thread, Uniden comes out with it. Just like every time there is a "Uniden has abandoned the x36HP line because they won't fix X, wah, wah, wah" thread Uniden comes up with a fix for the problem.

See people just aren't happy unless they can be unhappy.

I agree Gary and many of us here contributed our findings on different types of MotoTRBO systems which were later modified. I look forward to doing the same with some NXDN systems when it's released.

 

[SOFA_KING]

Never!

(nothing happening)

Phil

 

[mharris]

This actually surprises me. I thought for sure Uniden would follow up with NXDN for an additional $50.

 

[jonwienke]

I would be surprised if it never happened. I believe that it will eventually be released, but not necessarily soon. As a practical matter, I suspect that Uniden's firmware engineers are currently busy ironing out the current bugs in DMR and Provoice, and will turn their focus to NXDN once the bugs in DMR and Provoice are satisfactorily resolved.

I would rather wait until Uniden has a robust, functional implementation of NXDN and all trunked variants of NXDN, rather than getting a half-baked product with significant bugs.

 

[garys]

Other than the ongoing blather of a couple of the usual anti Uniden suspects, there is nothing to indicate that Uniden isn't going to offer NXDN.

I would think that the only reason that they might not offer it is that demand for DMR has not met expectations and they don't think that demand for NXDN will have a sufficient ROI to justify the money spent.

This actually surprises me. I thought for sure Uniden would follow up with NXDN for an additional $50.

 

[wa8pyr]

I follow the trials and tribulations on the Whistler Forums in regards to NXDN and trunking. AggieCon's reports seem to lean towards Whistler doesn't seem to trunk track NXDN systems, while others report they are trunking.

I just acquired a TRX-1 and it's trunk tracking the local NXDN system just fine. The kicker is that, like DMR and EDACS, all of the system frequencies have to be present for it to work right or transmissions will be missed.

Figuring that out was a bit tricky as the system is using frequencies licensed to two different sites, and it took me an hour or two on a Sunday to figure out what was going on and then log enough transmissions using DSD+ to identify all the channels. Once I got those and updated the radio it works fine. I updated the database too. . .

As far as the actual topic of this thread, I have no doubt Uniden is working on NXDN for the 436/536, and I'd love to have it in my 436. However, from past experience I can say that they're not going to say much/anything about it until it's ready for release, for the reasons stated by others earlier in this thread. On top of that, UPMan has stated before that Uniden corporate policy is not to release info on impending upgrades.

I'll just wait patiently and enjoy my TRX-1, which in a lot of ways I like better than the 436 (V-Folders and scan list layout especially).

 

[garys]

I've had a similar experience with a NXDN UHF trunk network in my area. Licenses are all over the place, with multiple entities holding licenses and apparently sharing them to make a system. It's very confusing.

If Uniden uses a NXDN scheme similar to what they use for DMR, we're going to need the channel number in addition to the frequencies, and maybe even the RAN.

One of the best features of the GRE/RS/Whistler scanners is the use of Lists where you can mix and match conventional and trunked information. It makes scanning a system that uses a mix of trunking and conventional frequencies quite easy. I wish Uniden could develop something similar.

I just acquired a TRX-1 and it's trunk tracking the local NXDN system just fine. The kicker is that, like DMR and EDACS, all of the system frequencies have to be present for it to work right or transmissions will be missed.

Figuring that out was a bit tricky as the system is using frequencies licensed to two different sites, and it took me an hour or two on a Sunday to figure out what was going on and then log enough transmissions using DSD+ to identify all the channels. Once I got those and updated the radio it works fine. I updated the database too. . .

As far as the actual topic of this thread, I have no doubt Uniden is working on NXDN for the 436/536, and I'd love to have it in my 436. However, from past experience I can say that they're not going to say much/anything about it until it's ready for release, for the reasons stated by others earlier in this thread. On top of that, UPMan has stated before that Uniden corporate policy is not to release info on impending upgrades.

I'll just wait patiently and enjoy my TRX-1, which in a lot of ways I like better than the 436 (V-Folders and scan list layout especially).

 

[jonwienke]

IMO separating discrete conventional/analog frequencies and an actual trunked system into two separate Systems makes better sense conceptually and logically--put the analog freqs in the analog System and trunked stuff in the trunked System.

You can put any mixture of trunked and conventional Systems in a Favorite List.