SDS100/SDS200: CTCSS question

[bearcatrp]

Have my SDS200 using proscan logging. Am getting allot of interop frequencies with ctcss recordings but listening to the recording, nothing but a hiss. Isn't the 200 supposed to automatically lock in on the ctcss and decode the transmission so i can listen to the transmission? Been looking in the manual and the easy to read 200 but not finding anything about this. thanks

 

[buddrousa]

Is there a chance that you are seeing some type of DATA STREAM or CO-CHANNELING?
I do not remember if you are in a high RF Enviromint

 

[n1chu]

CTCSS (or PL/DPL) does not decode, as when dealing with encryption. It merely ignores those transmissions that don’t have the proper CTCSS programmed with the frequency you want to monitor. So if and unless you don’t have the scanner set to “Search” for the CTCSS/DCS, the scanner won’t record anything on that frequency. In your case, when using the proper CTCSS, and not having the scanner set to Search, what you hear is what’s being transmitted on that frequency, in your case just a transmission without any audio. It may appear as a quiet channel with a bit of background hissing… or, possibly an encrypted channel, as some encryption techniques which may produce this mild hissing. My bet is what you are hearing is to be expected in some cases. I’d just ignore them as they may be caused by what others have posted here.

 

[dave3825]

Am getting allot of interop frequencies with ctcss recordings but listening to the recording, nothing but a hiss. Isn't the 200 supposed to automatically lock in on the ctcss and decode the transmission so i can listen to the transmission?

The scanner locks on the active carrier on a freq. If set up for search, it will display the tones if found. If programmed, it will stop on the freq that are broadcasting the tone. If the tone is found in the transmission, it will stay there. If a different tone is detected, it resumes scanning.

 

[Whiskey3JMC]

Have my SDS200 using proscan logging. Am getting allot of interop frequencies with ctcss recordings but listening to the recording, nothing but a hiss

Not sure if I'm understanding your inquiry correctly but...are you using Proscan for recording too? If yes, you'll need to stop the recorder then click the Audio Control tab, then the Recorder tab, make sure your input sound device is set to whatever you are using to feed your SDS200's audio. If input device is set to anything else you'll hear dead air or a "hiss" when the recorder kicks in depending on which incorrect input this is set to. Pages 7 & 8 of the Proscan manual describe this more in depth

 

[bearcatrp]

All my other recording play correctly. Just checked. Just these interop frequencies with the ctcss is just a hiss. I'll fire up my R8600 and go to that frequency and use the ctcss code to see if I can listen to the transmissions. Usually those interop frequencies are just 2 to 3 seconds recorded but lately they are becoming long recordings. Just have the 200 scanning my selected service types with a 5 mile radius.

 

[Randyk4661]

Can you tell us what system you are listening to?
It might help us figure what's going on.

 

[bearcatrp]

Can you tell us what system you are listening to?
It might help us figure what's going on.

453.4625 C 156.7 UTAC41- tacticle

 

[Colin9690]

453.4625 C 156.7 UTAC41- tacticle

@Randyk4661 meant something more descriptive, such as FCC callsign, state, city, county, agency, etc. The posted information tells us nothing unfortunately.

 

[bearcatrp]

System site: National Interoperability-USA , Department: NIFOG-UHF National Interoperability , System Type: Conventional , Tone: NFM .
This is what proscan shows besides what I already posted. The recording times were 27 seconds and 18 seconds for the last hour that got logged.

 

[JoeBearcat]

Have my SDS200 using proscan logging. Am getting allot of interop frequencies with ctcss recordings but listening to the recording, nothing but a hiss. Isn't the 200 supposed to automatically lock in on the ctcss and decode the transmission so i can listen to the transmission? Been looking in the manual and the easy to read 200 but not finding anything about this. thanks

Could it simply be a repeater that was keyed up or some other dead carrier? (dead aside from the CTCSS tone)

 

[bearcatrp]

If it was logging only a few, could consider that. But am getting many interop recordings, more than I normally see and longer transmissions. Usually see 2 to 5 seconds. Now, usually exceed 25 seconds.
Am hoping proscan gets updated with a better search feature so I could tell you exactly how many interop recordings I am getting and the frequencies.

 

[ecps92]

All my other recording play correctly. Just checked. Just these interop frequencies with the ctcss is just a hiss. I'll fire up my R8600 and go to that frequency and use the ctcss code to see if I can listen to the transmissions. Usually those interop frequencies are just 2 to 3 seconds recorded but lately they are becoming long recordings. Just have the 200 scanning my selected service types with a 5 mile radius.

odd thought, are you running any other scanners at the same time ??
It could be the other Scanner is throwing a carrier and causing those channels to lock-up, for the short period it is on that One interfering channel....?

 

[ProScan]

Am hoping proscan gets updated with a better search feature so I could tell you exactly how many interop recordings I am getting and the frequencies.

In what way? What type of search? I take it you want to search the Recordings grid. Is that correct?
How are interop recordings distinguished from regular recordings?

 

[bearcatrp]

I mentioned to you before in this thread about a search feature that will print to word pad thats on every pc. Can select anything that will go through my entire log and print it in word pad. Will print the entire line so say I chose to select service type, then select interop. It will go through my entire log and print out every instance of a interop logged to a word pad doc. I just match up date and time and seconds recorded to find the recording.

 

[ProScan]

I mentioned to you before in this thread about a search feature that will print to word pad thats on every pc. Can select anything that will go through my entire log and print it in word pad. Will print the entire line so say I chose to select service type, then select interop. It will go through my entire log and print out every instance of a interop logged to a word pad doc. I just match up date and time and seconds recorded to find the recording.

I think what you want is an export function that exports data from ProScan into a text document. Then using a text editor (WordPad) to search for words in the document. You mentioned "recording" so I take it you want to export from the recording grid.

Click this button. The recording grid data will appear in a file named "Recorder Grid Log.txt" then it can be edited with a text editor.
If you want the service type to appear in the recording grid, then use the %ST1 custom formatter in the Custom Filename box.

 

[ProScan]

@bearcatrp, I should have refered you to this thread ProScan: - Official Software Thread as it has nothing to do with this thread.