SDS100/SDS200: SDS200 requires IFX on trunk cc... now what?

[GTR8000]

ProScan only do favorite list edit so that IFX table are only in Sentinel.

Incorrect.

 

[phask]

No, you don't. Read my post above this. Go into Sentinel, edit Profile, go to Misc tab, edit IFX table, upload, done.

Came to say the same. I've never used the method Trentbob mentioned and did not know it existed Always did it in the profile.

 

[tvengr]

So after a long, arduous debug session, I finally discovered that this one trunk control channel "requires" IFX to work with my SDS200 scanner

Do you have a FM broadcast or TV tower close to you. You may be having image or intermod problems. I assume you tried all of the filters.

 

[dmfalk]

This situation, oddly, is one where the waterfall upgrade actually comes in handy, in order to tell if its either an IF birdie or actual intermodulation interference.

Besides, the OP never did say what the CC's frequency was, or which city he's in and what system he's monitoring.

 

[devicelab]

This situation, oddly, is one where the waterfall upgrade actually comes in handy, in order to tell if its either an IF birdie or actual intermodulation interference.

The SDS100 works fine and there's no indication of any obvious problem with my SDRs.

RF saturation in this area is at 99 on a scale of 1-10.

 

[devicelab]

Besides, the OP never did say what the CC's frequency was, or which city he's in and what system he's monitoring.

Yes I did.

 

[dmfalk]

Your profile says you're in Washington (state), but not where, as that could be anywhere from the Vancouver/Portland area to Spokane to the Walla Walla metro area, because I can't just assume the Seattle/Tacoma/Olympia metro area. Add to this, that your SDS100 may not necessarily be in the same place as your SDS200, so it might not be the IF causing interference directly. (Some devices transmit low-level RFI, and you might be close to one, causing intermodulation with the IF.)

Sorry for the nitpicking, but there are so many factors to consider, to weed out what's actually causing this interference. This is also why it would be nice to know which CC frequency on what system, especially to see if broadcast FM is a cause for interference.

 

[dmfalk]

Yes I did.

You only mentioned 167 MHz. Usually, most operators don't have their operations precisely at 167.000 (or at any MHz, on the nose), particularly because of birdies.

 

[devicelab]

You only mentioned 167 MHz. Usually, most operators don't have their operations precisely at 167.000 (or at any MHz, on the nose), particularly because of birdies.

Gee and what trunk could have sites (and be located in WA state) on 167 Mhz. I'm stumped.

 

[dmfalk]

Don't assume. Even a statewide (or federal) system does not keep its control channels on the same frequencies everywhere.

 

[KevinC]

OP got his issue resolved. Closing as this is getting ridiculous.