NXDN Update Now Available!
- Thread starter WhistlerWendy
- Start date
- Status
No CPU update for the TRX-1? I can sit on an NXDN control channel and hear nothing while DSD+ is hearing voice! BTW, TRX-2 after new update still deaf to same control channel.
Last edited:
deleted
what setting did you use for NXDN - Type C or D? Did you try the other flavor to see if it works?
Tried C and D. No dice so far programmed as conventional either. Have to keep working at it.
well TRX-1 is not saving RAN correctly. I programmed 26 in EZ Scan but it showed 1A in the scanner.
DonS
Member
Damn, I thought maybe I had a reason for no NXDN.
DonS
Member
Unless you're really sure about the RAN used, set it to "ANY".
That confused me too. The software shows the RAN's as decimal, but on the scanner they're in HEX.
Just because the db may say a particular RAN, don't trust that if you aren't receiving traffic...set it to any and see what happens. You can always change it back later.
EDIT: Oops, DonS beat me to it...
EDIT: Oops, DonS beat me to it...
I'm using the RAN I'm getting from DSD+
Audio quality is as usual exceptional. Trunktracking performance is completely the opposite. Two $20 RTL dongles and DSD+ software croak it. I know it's free but I'd expect a better start, with all due respect.
I am trying to follow two NXDN4800 systems. One has four frequencies, the other six. Both are well within range of my reception area. Both are programmed to "NXDN Auto" and "Any" for NXDN RAN. Each has just a wildcard programmed at this point under talkgroup details for anticipated simplicity's sake.
Transmissions disappear in midstream, get picked up in midstream, and replies within the perceived delay period as programmed are often not received. Many transmissions are outright missed as if the scanner is going off into lala land and forgetting what it's doing.
There is nothing else programmed into the test TRX-1 right now but these two systems. Earlier in the day I was scanning just one system and testing it against a DSD+ setup. The latter won hands down with the exception of the audio quality.
I am trying to follow two NXDN4800 systems. One has four frequencies, the other six. Both are well within range of my reception area. Both are programmed to "NXDN Auto" and "Any" for NXDN RAN. Each has just a wildcard programmed at this point under talkgroup details for anticipated simplicity's sake.
Transmissions disappear in midstream, get picked up in midstream, and replies within the perceived delay period as programmed are often not received. Many transmissions are outright missed as if the scanner is going off into lala land and forgetting what it's doing.
There is nothing else programmed into the test TRX-1 right now but these two systems. Earlier in the day I was scanning just one system and testing it against a DSD+ setup. The latter won hands down with the exception of the audio quality.
milcom_chaser
Member
- Joined
- Jul 4, 2010
- Messages
- 982
My Cat RAN when I read this post...
I have had much success by playing around with the squelch. Normally listening to a digital system, I would turn the squelch all the way counter clockwise (off) for maximum reception. With the NXDN this setting inhibited the scan/search. By opening it up the signal strength meter stayed in the strong position and many talk groups were picked up from more than one site. I could actually hear both parts of the conversation. This was done in both the "C" and "D" mode and listening to the wildcard only. When in scan mode with a wildcard and some TGs, it was quite quiet. Next I'll programm all the TGIDs I have heard into the system and run it in scan mode and see it things improve. For now, listening to the wildcard "object" seems to work best.
CPU 4.1 is working very well Wendy!
No problems found and mostly, no card corruption!
I don't currently have DSD setup so I cannot comment on it doing a better job or not but I'm very happy with what my TRX-2 is copying right now!
Thanks to you and the Whistler team for addressing these problems in such a timely matter for both the TRX and the 1095/98 model users.
NXDN channels that I'd already loaded are working well.
I still need to setup an actual trunked site at a hospital just a mile or two away as I'm still scanning NXDN conventionally for now using the Quick Import site that AggieCon put together for us all. That alone was very nice of him to put that site together for everyone.
It sure helps me find things in range for both DMR and NXDN modes.
Have a great weekend!
oz1jua
Member
Thanks now it seems to work much better. CPU Update 4.1 works fine again.
The only feature i miss now is to set the Basic Encrypt code to a DMR channel.
"Playing around with the squelch" is not the answer in the real world of using these scanners. If I minimize the squelch under normal circumstances to improve reception on a NXDN system I'm opening (literally) the door for problems elsewhere. What if I have several conventional frequencies that I monitor that do not use tone squelch, such as maritime channels?
I should not have to play with the squelch. The two systems I mention are roughly 5 and 10 miles distant from me and have ample signal for what should render excellent performance for a trunked radio system.
All of that said, for experimental purposes I am exclusively scanning NXDN UHF trunked radio systems, and regardless of the squelch position (which should be irrelevant given signal strength) there is no performance difference in my case.
I should not have to play with the squelch. The two systems I mention are roughly 5 and 10 miles distant from me and have ample signal for what should render excellent performance for a trunked radio system.
All of that said, for experimental purposes I am exclusively scanning NXDN UHF trunked radio systems, and regardless of the squelch position (which should be irrelevant given signal strength) there is no performance difference in my case.
I think I figured out my problem with the system I'm trying to monitor. See image. It would have helped to have been watching the DSD+ screen the entire time last night. I think the system has some type of radio registration acceptance. I don't know if this is why I get nothing. Anyone?
I did get 5 2 second recordings on this system with no voice. The TGID's were different than DSD+, but I did change the RAN to any so maybe they were from another system.
All in all, I have to say that whatever Whistler did on this update for DMR, it made my receive even better than it was. There were a few systems that I only ever had 2-3 bars that now have 4-5. Better decode on those same systems too.
I did get 5 2 second recordings on this system with no voice. The TGID's were different than DSD+, but I did change the RAN to any so maybe they were from another system.
All in all, I have to say that whatever Whistler did on this update for DMR, it made my receive even better than it was. There were a few systems that I only ever had 2-3 bars that now have 4-5. Better decode on those same systems too.
Attachments
Conventional NXDN channels sound good on my updated TRX-1 and 2 here in Los Angeles. But still hope Uniden gets NXDN out, because frankly, their search features are plain superior to what the Whistlers have.
- Status
Similar threads
