Any word on the status of NXDN support?

[jonwienke]

Most rail traffic in my area is NFM analog.

 

[troymail]

Seriously - How much of Columbus rail traffic is NXDN? From what I understand, none. I thought they were only using it in selected areas with no interconnections or yard work.

Most rail traffic in my area is NFM analog.

Then perhaps Uniden is of the same mind and really has no plan to release a NXDN solution...

 

[ThomasMcKean]

Seriously - How much of Columbus rail traffic is NXDN? From what I understand, none. I thought they were only using it in selected areas with no interconnections or yard work.

That's a good question? I had thought none as well, and yet the Digital Frequency Search site says there is a whole bunch of it on NXDN. I suppose just because it says so doesn't make it true, but from what I have heard that site is kept up to date. Or at least it was? Maybe that has changed...?

 

[troymail]

That's a good question? I had thought none as well, and yet the Digital Frequency Search site says there is a whole bunch of it on NXDN. I suppose just because it says so doesn't make it true, but from what I have heard that site is kept up to date. Or at least it was? Maybe that has changed...?

Yeah.... unfortunately, you can't trust that. It's just what they are licensed for not what they are actually doing.... But you can find out even without a NXDN capability ... just tune to the frequencies and see if you hear the NXDN digital stream....

 

[jonwienke]

Then perhaps Uniden is of the same mind and really has no plan to release a NXDN solution...

Not necessarily. NXDN is used by entities other than railroads. And I make no representation that traffic in my area is representative of traffic nationwide.

Just because someone has a license that allows NXDN doesn't mean they are using NXDN. There's a bunch of NXDN rail licenses in my area, but I still mostly hear analog FM.

 

[troymail]

Not necessarily. NXDN is used by entities other than railroads. And I make no representation that traffic in my area is representative of traffic nationwide.

Just because someone has a license that allows NXDN doesn't mean they are using NXDN. There's a bunch of NXDN rail licenses in my area, but I still mostly hear analog FM.

Ah, playing both sides of the argument. Ok. That's fine.

I'm well aware of NXDN licenses vs. actual users since I have a Whistler radio that Whistler announced would be able to do NXDN in advance - and delivered.

 

[Nasby]

Seriously - How much of Columbus rail traffic is NXDN? From what I understand, none. I thought they were only using it in selected areas with no interconnections or yard work.

All of the mainline rail traffic in Columbus is still analog and can easily be monitored with the cheapest, programmable scanner that money can buy.

Many Class 1 railroads have have the ability to use NXDN (hence the FCC licensing) but there has not been any widespread use in Ohio.

If there's one thing that's true about the railroads is that they are very slow to embrace change and even slower to implement change.

Heck, it took them years just to decide on NXDN as their digital protocol.

So to the OP, you won't be hearing NXDN on the mainline trains in C-Bus anytime soon.

 

[wbswetnam]

All of the Union Pacific rail road traffic that I've heard here in Arkansas is still NFM. However, there are are some agencies in Arkansas (mostly volunteer fire departments but some sheriffs departments, too) that have switched to NXDN, enough so that it's worth having here.

 

[ThomasMcKean]

I plugged in all the local railroad frequencies and they are all active. So apparently it is true we are still NFM here in the area. However, as others have pointed out, there is far more than just railroads on NXDN these days, and us nosey people want to hear them.

 

[icomuser]

NXDN ?

I am a railfan and recently visited the Great Smoky Mountain Railroad in North Carolina. I had the frequencies programmed into my unit; I asked a crew member which was the road channel and was told.:" You can't monitor us, we are using narrow-band. I assured them I could monitor narrow-band. But what I received was just static on the channels when they transmitted. A check of their license showed that they are licensed for FM narrow and NXDN, which apparently they are now using. It is a shame that this wonderful radio will not yet monitor this mode, which all railroads will be switching to in the future. Does anyone have an idea to correct this issue, other than drilling into my radio or purchasing a Whistler unit? Both "solutions" are equally undesirable to me at the present. We railfans would at least like some encouragement on this issue. The 436 is a great radio, but we need this upgrade ASAP. We will gladly pay for it!

 

[mmckenna]

Get yourself a used Kenwood (NXDN/NexEdge) or Icom (IDAS) VHF radio and program it up.

Won't be cheap, but would probably be cheaper than a new high end scanner.

As long as they are not using encryption or trunking, you'd be able to listen to them.

 

[AggieCon]

I agree, once Uniden can do NXDN, it will have the next edge of commercial scanners by far. :wink:

 

[kevino]

NXDN

Of course we know that the latest models of Whistler scanners can handle conventional NXDN, but it seems that making a scanner that can properly track trunked NXDN might be be giving scanner developers and engineers a bit of difficulty. Unlike with Motorola and other systems that use a standardized channel map for trunking, NXDN allows trunked system operators the ability to develop their own channel map. And therein lies the rub. In order to track those systems, you'd need to know exactly which frequency has been assigned which channel number. There is a large NXDN trunked system operator in the midwest that has a channel map consisting of over 1000(!) channels. There is no rhyme or reason to the layout of these channels, and they are not in frequency order. On top of this, selectivity might also be an issue due to how narrow these signals are. The system operator mentioned above uses many 3.125 kHz splits. And to add to the mix, they often use frequencies that are 3.125 kHz off of the licensed frequency. If you're not looking at the signal on a service monitor or with a dongle and a program like SDR#, you may not realize this.

Bottom line is that it isn't as simple as one might think for even the major players to come up with a scanner that will track trunked NXDN.

 

[troymail]

Of course we know that the latest models of Whistler scanners can handle conventional NXDN, but it seems that making a scanner that can properly track trunked NXDN might be be giving scanner developers and engineers a bit of difficulty. Unlike with Motorola and other systems that use a standardized channel map for trunking, NXDN allows trunked system operators the ability to develop their own channel map. And therein lies the rub. In order to track those systems, you'd need to know exactly which frequency has been assigned which channel number. There is a large NXDN trunked system operator in the midwest that has a channel map consisting of over 1000(!) channels. There is no rhyme or reason to the layout of these channels, and they are not in frequency order. On top of this, selectivity might also be an issue due to how narrow these signals are. The system operator mentioned above uses many 3.125 kHz splits. And to add to the mix, they often use frequencies that are 3.125 kHz off of the licensed frequency. If you're not looking at the signal on a service monitor or with a dongle and a program like SDR#, you may not realize this.

Bottom line is that it isn't as simple as one might think for even the major players to come up with a scanner that will track trunked NXDN.

This is no different than older LTR and even DMR systems that require knowing the frequencies and their order....

I suspect Uniden is holding NXDN for a new piece of hardware they want to sell.... the hardware just ain't ready yet....

Paul even seems to have hinted at something in a recent post...

http://forums.radioreference.com/uniden-tavern/359019-upman-away-while.html#post2818238

We have several things that are very close to fruition and something on the further horizon that I think you'll go ape over. But, I should be back by then and really shouldn't tease you like this.

Of course, being the master of tease, this could mean anything - even a firmware release he wants to sell you.

 

[UPMan]

Or, one could even be a free firmware release.

https://forums.radioreference.com/uniden-tech-support/359561-bcd325p2-bcd996p2-update-1-07-09-a.html

 

[troymail]

Or, one could even be a free firmware release.

https://forums.radioreference.com/uniden-tech-support/359561-bcd325p2-bcd996p2-update-1-07-09-a.html

That probably covers the "things that are very close to fruition". It's the "further horizon" ... "go ape over" I'm talking about.

 

[UPMan]

That is not all that is on my plate. That is just what I have for today.

 

[garys]

Given your track record on predictions, I'm now very sure that there is no new hardware on the horizon.

That probably covers the "things that are very close to fruition". It's the "further horizon" ... "go ape over" I'm talking about.

 

[troymail]

Given your track record on predictions, I'm now very sure that there is no new hardware on the horizon.

I have to be right at some point, eh?

 

[garys]

You haven't even beat the point spread yet.

I have to be right at some point, eh?