SDS-200 Not recognizing trunked system, deaf

[cognetic]

Not sure if the same thing is going on with my SDS200; however, my SDS200 is having trouble with simulcast systems in the two counties I work and live. I have to use a dedicated favorite list specific to a particular simulcast in order to receive any signal. Even if held on the particular SYS/DEPT/CHANNEL being targeted, it will not receive using GPS at zero range when scanning the whole database (LEO & dispatch services only). This has annoyed me for weeks as my 536s, 436, and HP1/2s were receiving the targeted signals just fine. At times the SDS 100 seems to be doing something similar. Fortunately, my G5 is on hand & programmed for the specific geographic locale on either end of my commute where this is happening.

-cognetic

 

[TailGator911]

As many times that this question has been asked, I am almost sure someone is working a write up as we speak.

Again, does anyone know about documentation for the various filters? Where can I find it?

 

[werinshades]

Again, does anyone know about documentation for the various filters? Where can I find it?

As many times that this question has been asked, I am almost sure someone is working a write up as we speak.

I don't know if this suffices your curiosity, but UPMan explained it here:

SDS100FirmwareUpdate < UnidenMan4 < TWiki

Scroll down...your answers are before you.

 

[jjbond]

Again, does anyone know about documentation for the various filters? Where can I find it?

So many have asked, so little has been given... sadly, nothing official.

 

[chief21]

As an update to my initial post, I think I might have finally found the secret sauce for monitoring my local simulcast system. For background, my particular situation seems to involve a strong local signal that is interfering with the CC of a local simulcast system. As a result, I have been unable to get the SDS-200 to lock on that CC. The use of IFX produces no improvement.

After playing around with numerous combinations of antennas and scanner settings, it appears as if the SDS-200 is at last locking on the CC and decoding properly. My antenna (if you could call it that) is a *very* short piece of stripped coax and a BNC connector. For this particular site, the SDS-200 attenuator is ON and the filter is set to AUTO. Although the signal meter now indicates a very weak signal (zero to one bar, but only on the CC), the scanner does stay locked on the CC about 95% of the time. By contrast, all of the related voice channels are full (or nearly full) strength. The moral of this story seems to be that, in simulcast at least, sometimes much less is more!

So... the good news is that I am finally able to monitor this problem system. The bad news is that I am unable to monitor much else due to the severe antenna limitation.

 

[sparklehorse]

As an update to my initial post, I think I might have finally found the secret sauce for monitoring my local simulcast system. For background, my particular situation seems to involve a strong local signal that is interfering with the CC of a local simulcast system. As a result, I have been unable to get the SDS-200 to lock on that CC. The use of IFX produces no improvement. <snip>

I also have a couple of problematic systems that I believe are due to adjacent signal interference. It would be great to have the option of a software notch filter to remedy that situation. A very sharp notch, even if it only attenuated a few dB, should do the trick. I don’t know if that’s something that can be added with firmware. You’d also need to have a waterfall or other means of determining the offending frequency and also be able to ‘tune’ the notch for best effect. Might be a tall order, but then again the SDS are as much a computer as they are a radio, so it might be doable.
.