Anyone else having issues with the TRX-1 tracking NXDN conversations? I find that I'm missing replies when paused on a talkgroup, and sometimes whole conversations, when compared to the same traffic on the DSD+ program.
I started wondering how the TRX scanners work on NXDN trunked systems. The NXDN control channel sends out data that tells subscriber radios to, for example, switch to channel 217. In order for the DSD+ program to work, you need to tell it what frequency channel 217 is. The actual frequency isn't sent out on the control channel. For the TRX scanners, you just enter the frequencies; there's no provision to enter what channel number goes with which frequency. So can I assume that the TRX scanners work on NXDN trunked systems just like they work on DMR systems, that they just scan all frequencies looking for channel activity?
I will say that the NXDN audio quality on the TRX scanner is superior to that of DSD+, but for trunk tracking and following specific talkgroups, the DSD+ software program beats the TRX-1 easily.
I started wondering how the TRX scanners work on NXDN trunked systems. The NXDN control channel sends out data that tells subscriber radios to, for example, switch to channel 217. In order for the DSD+ program to work, you need to tell it what frequency channel 217 is. The actual frequency isn't sent out on the control channel. For the TRX scanners, you just enter the frequencies; there's no provision to enter what channel number goes with which frequency. So can I assume that the TRX scanners work on NXDN trunked systems just like they work on DMR systems, that they just scan all frequencies looking for channel activity?
I will say that the NXDN audio quality on the TRX scanner is superior to that of DSD+, but for trunk tracking and following specific talkgroups, the DSD+ software program beats the TRX-1 easily.
Last edited: