What changes that causes issues between models?
SDS100 Trunking Reception
- Thread starter pjbracing
- Start date
- Status
If you look at trunked System and Site settings when Target Model is set to x36, they are not the same as when Target Model is set to SDS100. I had a long conversation on Facebook with a guy who was about ready to return his SDS100 for a refund because it wasn't receiving any trunked systems, and it turned out he had his profile set to x36 when he did Write To Scanner. He changed the profile setting to SDS100, did Write To Scanner again, and it worked fine after that.
Ok I think I have this issue after accidentally writing the wrong profile setting and I'm trying to find the differences.
Make 2 profiles, set one with Target Model x36, and the other with Target Model SDS100. Look at the Favorite List settings for trunked Systems and Sites with each profile active--there are significant differences. A random sampling:
1. No AGC system settings for the SDS100.
2. x36 sets P25 NAC at the system level.
3. SDS100 sets P25 NAC separately for each Site. There is no P25 NAC setting at the system level.
4. No Digital Threshold mode or value setting options for the SDS100.
I'm sure there are others. Best practice is to have separate profiles for each model, with the correct Target Model set for each.
1. No AGC system settings for the SDS100.
2. x36 sets P25 NAC at the system level.
3. SDS100 sets P25 NAC separately for each Site. There is no P25 NAC setting at the system level.
4. No Digital Threshold mode or value setting options for the SDS100.
I'm sure there are others. Best practice is to have separate profiles for each model, with the correct Target Model set for each.
I've given up. I added a 700-800 mhz antenna and the reception was poorer than the standard rubber duck type that came with the scanner. The reception of the SDS100 is not sufficient no matter the location in or around my home while my 396XT receives the trunked transmissions without any problem. I am returning the scanner with great disappointment. It did a great job on the simulcast system when I was in Flint but that doesn't do me any good at home.
Make sure the attenuator is Off...if that doesn't work, send it back. Possibly bad antenna connection, not normal behavior.
The new firmware makes a big difference when receiving weak signals. Have you tried that?
troymail
Silent Key
I just checked firmware. It says i have latest downloaded on scanner
Main and Sub: (Version 1.02.03)
The attenuator is off on all sites.
RSSI: 98 - 105+ dBm
2-3 bars on signal strength.
conventional turned off and squelch at zero
= No Hits
I'm really trying to find a solution so I can keep this scanner!!!
https://forums.radioreference.com/uniden-tech-support/372091-sds100-firmware-1-02-05a-open-beta.html
Follow the instructions in the first post.
Follow the instructions in the first post.
Thanks - Updated firmware but unfortunately I get nothing. Pretty expensive scanner to have to do so much trial and error debugging. Kinda disappointed for my Father's Day present. I'll keep an eye on the forums and when it looks like I can buy one that works, I'll order one. In the meantime, I'll just continue to use my 396XT.
Thanks for all of your help and the help from so many others.
stantorres
Member
Had a similar problem. My Home Patrol-2 was receiving much more traffic than the SDS100 when side by side. Went through the programming thoroughly. Auburn Hills area. It's got to be something with MPSCS simulcast in this area. Returned my SDS100 until it can be sorted out.
I walked a guy through that exact problem on MPSCS. The SDS100 can program separate NACs for each site. Some of the NACs are wrong in the RR database, and so the SDS100 wasn't receiving traffic from the sites where the wrong NAC was listed. Correcting the NAC fixed the problem. The issue was not the scanner, but bad programming data.
pjbracing, your issue is probably the same thing.
stantorres
Member
I didn't think to look at the NAC. That would explain the behavior I was seeing. Wish I had thought of that before I returned the unit. Nice detective work.
Thanks but I not think it was the NAC's as I was able to receive MPSCS very well without any programming changes when I left my house and drove only a short distance away, still connected to the Holly tower.
I agree, a wrong NAC blocks site reception regardless of your location. If you can ever receive a site, your NAC setting for that site is OK.
Your case sounds like some type of RFI issue. Have you tried looking for the source?
If you have a SDR dongle, a USB extension cord, and a laptop with SDR#, it's easy to trace the source of interference. Connect an antenna to the dongle (any small whip will do). Tune to one of the middle site frequencies so all of the site frequencies are visible on the band scope. Turn the RTL AGC on, and the tuner AGC off, and set the RF gain so that the noise floor is around -40. Walk around and try to find where the noise floor goes the highest. As you get closer to the noise source, you may need to turn down the RF gain.
- Status
Similar threads
