NXDN Update Now Available!

[milcom_chaser]

I surely took that into consideration and ran with a few different rubber ducky antennas, one cut for the UHF band and the other a Radio Shack 800 MHz antenna obviously not cut for 450-470 reception (although it does a pretty good job everywhere).

As far as I can see now the issue appears to be the fact that the control channel was an active part of the programming. With the control channel removed and the system still being scanned as a trunked system, performance is far better and the flashing S is only present when there is a signal present on the system and voice is not being decoded. When voice is being decoded the T flashes. From what I understand from Don's posts, aside that there's no control channel programmed, this is relatively normal for the display.

So that pesky control channel, which one would have thought would be a must for tracking a trunked radio system, appears to be the detriment instead. Who knew?

...

 

[AA6IO]

It's breaking squelch whenever the inverted 'S' icon turns on. You proved that when you turned on global attenuation and saw a reduction in how often the icon is "on".

To really prove it, try this:
* squelch knob fully CW
* global attenuation on ("GA" on LCD)
* antenna disconnected

Unless you have a strong RF source in the room, you should never see the 'S' icon. If you turn the squelch knob fully CCW, it will likely appear.

Then I really have issues. Here in Los Angeles my TRX-2 is getting hammered with outside antenna. Even with PAR FM and 152 MHz filters in line, and squelch at full CW (max), I sometimes still get the inverted S when trying to scan DMR and NXDN. Can run squelch at these frequencies on my Unidens without PARs in line at squelch setting of 2. Attenuation does help, but yikes, at full squelch, the inverted S.

 

[RK3BV]

Why TRX-1 no work NXDN 140-174 Mhz.? Conventional ,step 3,125 For ex.: 172,834375-"Frequency is invalid for this model" write me program. This frequency range need for Europe! Plesase help!

 

[AggieCon]

Try removing the control channel.

 

[sparklehorse]

Then I really have issues. Here in Los Angeles my TRX-2 is getting hammered with outside antenna. Even with PAR FM and 152 MHz filters in line, and squelch at full CW (max), I sometimes still get the inverted S when trying to scan DMR and NXDN. Can run squelch at these frequencies on my Unidens without PARs in line at squelch setting of 2. Attenuation does help, but yikes, at full squelch, the inverted S.

On which band are you having overload problems? If it's VHF-Hi you might try adding a TV filter or two. I live close to a number of broadcast TV and FM radio transmitters, and have had a lot of overload problems, especially on VHF. I found that with a rooftop antenna I needed not only the PAR FM filter, and two pager filters (153 & 158), but also two of the PAR TV filters. TV channels 8 & 10 in my case. With all of those strung together my newer radios work very well on VHF, even the Whistler 1065 which seemed to be the most prone to overload. I'm finding though that the TRX-2 has a surprisingly good front end. I can run it straight off my Comet GP-1, no filtering, and it doesn't seem to suffer much from overload. I have to run the squelch a notch higher, and it'll hang on some intermod occasionally, but unfiltered it's receiving distant VHF signals just about as well as my old BC780XLT, which is well known for its sensitivity and great front end. But every RF situation is different, and it could well be that a TV station is boogering up your reception. There are some good tools online that can show where your local TV towers are located, TV Fool being the most comprehensive I've seen.

.

 

[KC1UA]

I thought it was an overload issue for a while, but clearly it is not. I think we have proven pretty efficiently that it is a control channel issue.

As has now been stated excessively, remove the control channel and try again. I can almost guarantee you'll see a difference, not only in the flashing S but also in the overall performance.

I've put this scanner away at this point and I'm moving on to other things, unless I'm specifically asked to do some testing by Don or anyone at Whistler, or unless a firmware update comes along, or both.

 

[AA6IO]

Thanks for advice everyone. Will try removing CC, and if still problems, will try TV filter.

 

[wbswetnam]

Wendy - Are there any plans to include text ID support in NXDN? As of now, it only shows 'unit number' and not the text ID. Thx

 

[Ubbe]

Why TRX-1 no work NXDN 140-174 Mhz.? Conventional ,step 3,125 For ex.: 172,834375-"Frequency is invalid for this model" write me program. This frequency range need for Europe! Plesase help!

Use "United Kingdom" bandplan and flex step enabled. The frequency will round to the nearest valid value and will be usuable as there is no filter that narrow in the TRX-1 that could degrade the reception.

/Ubbe

 

[kikito]

Wendy - Are there any plans to include text ID support in NXDN? As of now, it only shows 'unit number' and not the text ID. Thx

What do you mean by "text ID"?

 

[W4KRR]

What do you mean by "text ID"?

I think he means radio alias. The NXDN system here sends out the programmed alias of the individual radios, if one has been programmed. You might see something like "Base 2", "Truck 5", "Mobile 3", etc. I see this with the DSD+ program. This info presumably comes from the control channel, but if the TRX radios don't utilize the control channel, then you probably won't ever see it.

 

[kikito]

I think he means radio alias. The NXDN system here sends out the programmed alias of the individual radios, if one has been programmed. You might see something like "Base 2", "Truck 5", "Mobile 3", etc. I see this with the DSD+ program. This info presumably comes from the control channel, but if the TRX radios don't utilize the control channel, then you probably won't ever see it.

That would be a neat feature.

 

[racingfan360]

I think he means radio alias. The NXDN system here sends out the programmed alias of the individual radios, if one has been programmed. You might see something like "Base 2", "Truck 5", "Mobile 3", etc. I see this with the DSD+ program. This info presumably comes from the control channel, but if the TRX radios don't utilize the control channel, then you probably won't ever see it.

The alias is actually programmed into the radio itself and sent as part of the signalling associated with the voice transmission, so its not in the control channel transmission. It's available in all NXDN radios - conventional and trunked - and not specific to a trunked system. Agree it would be a useful feature to add to the TRX series.

 

[Lwolf1313]

Trx-1 firmware version

What firmware version is the NXDN support in?

 

[racingfan360]

What firmware version is the NXDN support in?

I can't comment on which version it was first released in, but it is in the latest (ie DSP Version: 3.0
CPU Version: 5.0)

 

[SCPD]

Latest file CPU : DSP versions for TRX 2

Are these the latest versions for the TRX 2

CPU Boot 1.1
CPU APP U4.1
DSP APP 3.0
DSP VOC 1.6
DSP Build 101
Library 468
Location DB 10

 

[dudekindjack]

How is nxdn on the wster trx-2 compaired to the aor ar-dv1? There is a couple police dept here who have switched to a nxdn mode, and ar-dv1 will not decode the signal at all. I was just wondering how nxdn works on the whistler compared to the ar-dv1.

 

[lehigh4me]

I listen to a nearby police dept. that is on NXDN with my TRX-1. It works great and have not had a problem.

 

[werinshades]

Just found this thread and am new to the NXDN monitoring. Using the TRX-2, I searched and found the frequencies for the Diga-Talk system that was previously mentioned. The frequencies in the Database do not match my findings.

My question is this...I was able to document 24 frequencies on the system, most have a RAN of 6, a few have Ran's of 7, 1 has a RAN of 9, and a few have a RAN of 24. I was told the one of the RAN's has a site closest to me, so I went ahead and programmed in only those three frequencies and I was missing traffic. I went back to the original site and programmed in all the frequencies and it was back to monitoring the radio traffic. What is the best way to program in this system? During search, I was able to confirm Talk group numbers from all the different RAN's so I know they all belong. The FCC database is no help.

When I "hold" on a talk group, the TRX-2 flashes the "S" and the "T" According to what I have read, this would indicate the scanner is receiving a trunking channel? What is it scanning? Does the "known" control channel play any role here? I know the original NXDN upgrade said that the TRX scanners do not "trunk" NXDN nut a later upgrade said it now does. Unfortunately, there's not much information yet, so I'm trying to get a grasp on this...

 

[EricCottrell]

Just found this thread and am new to the NXDN monitoring. Using the TRX-2, I searched and found the frequencies for the Diga-Talk system that was previously mentioned. The frequencies in the Database do not match my findings.

My question is this...I was able to document 24 frequencies on the system, most have a RAN of 6, a few have Ran's of 7, 1 has a RAN of 9, and a few have a RAN of 24. I was told the one of the RAN's has a site closest to me, so I went ahead and programmed in only those three frequencies and I was missing traffic. I went back to the original site and programmed in all the frequencies and it was back to monitoring the radio traffic. What is the best way to program in this system? During search, I was able to confirm Talk group numbers from all the different RAN's so I know they all belong. The FCC database is no help.

When I "hold" on a talk group, the TRX-2 flashes the "S" and the "T" According to what I have read, this would indicate the scanner is receiving a trunking channel? What is it scanning? Does the "known" control channel play any role here? I know the original NXDN upgrade said that the TRX scanners do not "trunk" NXDN nut a later upgrade said it now does. Unfortunately, there's not much information yet, so I'm trying to get a grasp on this...

Hello,

The missed traffic could be due to missing frequencies for a site, or the traffic is only on some of the sites.

The Diga-Talk system is programmed as a NXDN(C) trunked system under the Trunked Radio Systems tab in the PC Application. The RAN value on a NXDN(C) system is the site number modulus 64. This system appears to have site numbers above 64, but for your purposes you can group the frequencies with the same RAN together. Create a site in Site Details for each RAN and put the frequencies with the RAN in the site frequencies.

73 Eric