TRX-2: Whistler TRX2 NXDN Problem

[theTastyCat]

Let me clarify my issues a little bit.

Whether I monitor my local NXDN as trunked or conventional, the same thing happens. Bear in mind I've confirmed all the frequencies with DSD+.

Many transmissions are missed entirely, and most others are missing the first second or two, which makes traffic very hard to correctly understand. Often long transmissions will simply drop out for a few seconds in the middle and sometimes come back, sometimes not.

 

[racingfan360]

Let me clarify my issues a little bit.
Whether I monitor my local NXDN as trunked or conventional, the same thing happens. Bear in mind I've confirmed all the frequencies with DSD+..

Just to confirm, if you run the TRX alongside DSD+ on the same frequency, are you hearing voice traffic on DSD+ that you're not hearing on the Whistler?

 

[theTastyCat]

Yes. I've sent Whistler tech support several examples. About 10% of the transmissions get through in full, 50% are missed and the rest are missing typically the first two seconds if not more later on.

Here's an example I uploaded to YouTube:

https://www.youtube.com/watch?v=KEsRQdV4QCk

Really hope this gets sorted out as this is the whole reason I bought a TRX-2 and it's almost worthless scanning my local NXDN, which is 100% of public safety in my area.

 

[Wackyracer]

Yes. I've sent Whistler tech support several examples. About 10% of the transmissions get through in full, 50% are missed and the rest are missing typically the first two seconds if not more later on.

Here's an example I uploaded to YouTube:

https://www.youtube.com/watch?v=KEsRQdV4QCk

Really hope this gets sorted out as this is the whole reason I bought a TRX-2 and it's almost worthless scanning my local NXDN, which is 100% of public safety in my area.

Have you tried attenuating it?

 

[theTastyCat]

No - I'm not sure how that would improve performance. Also, the signal drops off within about ten miles of the site, so I'm afraid if I attenuated it would be even worse.

 

[Wackyracer]

How many bars? Too weak a signal or too strong act the same way...so you either boost it or attenuate it,

 

[BrianG61UK]

How many bars? Too weak a signal or too strong act the same way...so you either boost it or attenuate it,

Other strong signals on nearby frequencies is the main thing attenuating can fix.

 

[theTastyCat]

OK, thanks for the info - good to know. I did try attenuating and nothing made it through the squelch :/ btw it's the TRX-2 and being used mobile, so I've tried it in a lot of different locations and distances from the site and nothing seems to change.

 

[BrianG61UK]

Yes. I've sent Whistler tech support several examples. About 10% of the transmissions get through in full, 50% are missed and the rest are missing typically the first two seconds if not more later on.

Here's an example I uploaded to YouTube:

https://www.youtube.com/watch?v=KEsRQdV4QCk

Really hope this gets sorted out as this is the whole reason I bought a TRX-2 and it's almost worthless scanning my local NXDN, which is 100% of public safety in my area.

In the video it looks like the scanner is scanning while, presumably anyway, the input to DSD+ is from a receiver of some kind that is permanently tuned to one frequency.

 

[kd7kdc]

Could be the actual channel center is 3.125 kHz above or below the FCC published frequency.


Sent from my iPhone using Tapatalk

 

[theTastyCat]

I have confirmed all the frequencies with DSD+. On DSD, it does jump from channel to channel but is tracked perfectly by the software. As you can see, it's not the same deal with the TRX-2.

 

[BrianG61UK]

I have confirmed all the frequencies with DSD+. On DSD, it does jump from channel to channel but is tracked perfectly by the software. As you can see, it's not the same deal with the TRX-2.

What receiver are you using with DSD+ that allows you to change frequency?

Sent from my SM-N9005 using Tapatalk

 

[W2GLD]

Okay, I am curious if anyone else has experienced this issue. I am trying to program an NXDN trunked system with the following frequencies that I have confirmed directly from a subscriber radio on the system:

422.63125 422.74375 422.75625 422.76875 422.78125

However, each time I enter these frequencies, the TRX-1 and TRX-2 scanners both round these to another frequency. For example, the first channel "422.63125" always rounds to "422.630"; what gives?

I am running the latest CPU/DSP from 06/30/2017 as well and just retested and the same issue is occurring. Am I doing something incorrectly?

 

[jdolina]

Have you enabled flex step?

 

[W2GLD]

Have you enabled flex step?

I have and it makes no difference, I just tried it again with Flexstep enabled and it still rounds "422.63125" to "422.63000"

I think this is a firmware flaw that's been here for sometime; I've been trying to enter this system for the last three firmware releases.

The center channel is: 422.63125 MHz, which splits the 6.25 kHz bandwidth into two 3.125 MHz segments, this makes the above and below as follows:

Upper: 422.66250 MHz.
Center: 422.63125 MHz.
Lower: 422.60000 MHz.

For NXDN, you need to be able to have finite control of the frequencies like this. I just opened up the ICOM cloning software for the iDAS radios, and all the frequencies can be entered in this fashion and most sample cloning files I have are centered on channels like this and are licensed as such through the FCC. So I think Whistler needs to address this issue.

 

[werinshades]

I submitted the request for 3.125 khz frequency entry as well as NXDN control channel decoding for future firmware updates if possible.

 

[Wackyracer]

Okay, I am curious if anyone else has experienced this issue. I am trying to program an NXDN trunked system with the following frequencies that I have confirmed directly from a subscriber radio on the system:

422.63125 422.74375 422.75625 422.76875 422.78125

However, each time I enter these frequencies, the TRX-1 and TRX-2 scanners both round these to another frequency. For example, the first channel "422.63125" always rounds to "422.630"; what gives?

I am running the latest CPU/DSP from 06/30/2017 as well and just retested and the same issue is occurring. Am I doing something incorrectly?

In ezscan, Under advanced tab, flexible frequency, make sure Flex step is enabled

 

[werinshades]

In ezscan, Under advanced tab, flexible frequency, make sure Flex step is enabled

I know I have it enabled and it doesn't take the actual frequency either but rounds it off:

471.31563 (Rounded to 471.31875)
472.25938 (Rounded to 472.25625)
472.31563 (Rounded to 472.31875)

 

[Wackyracer]

I submitted the request for 3.125 khz frequency entry as well as NXDN control channel decoding for future firmware updates if possible.

I thought I read they added this in the 6/30 update. I think it was listed under the release notes when you downloaded it....can any one confirm?

 

[werinshades]

No change. You can lock out the control channel and NXDN system and makes no difference and still can not enter the frequencies I posted. They are active on a NXDN system I monitor.