SDS100/SDS200: SDS200 Could someone explain how the Digital Waiting Time works?
- Thread starter tnbound
- Start date
- Status
doctordialtone
Member
It's the time that the scanner uses to determine whether a signal is Digital or Analog.
SDS100: - SDS 100 Mixed mode reception
If it's set too high, the scanner will "hang" on the channel.
Ubbe
Member
It does nothing for digital or decoding performance. It's just an audio mute function that makes the audio mute for the time set from the point where the squelch detects a carrier. It will not override the Hold time set to a system.
It's use are to only mute the audio while it is syncing to the digital data and starts to decode it and determine it to be a valid data signal. You then don't have to listen to the data noise during the decode process. The function are only active during systems where you have set the audio option to All and not Digital or Analog. Try first with a short time like 100mS and if you still hear a data burst then increase in 50mS steps until you no longer hear the data burst. I prefer to set it to 0mS so that I can hear that it is actually receiving something but some people get annoyed by the data burst.
/Ubbe
Good luck with it on Close Call.
Any time it gets a hit, and the freq is P25, NXDN or DMR, it just sits there making noise, and does not decode. Pretty pathetic.
This is on Close Call only, actual searching will yield results.
Any time it gets a hit, and the freq is P25, NXDN or DMR, it just sits there making noise, and does not decode. Pretty pathetic.
This is on Close Call only, actual searching will yield results.
Ubbe
Member
Search have full sensitivity but CloseCall are much worse and the signal must be both close and strong and pretty much the only signal to let it trigger a hit. In previous scanners it was a specific chip that handled closecall and needed a lot of signal but I do not know if it works any different in SDS scanners, probably not.
To detect a transmission using CloseCall takes something like 1 or 2 seconds but using search could take minutes if you search all frequency bands, and by then the signal could be gone and not found.
/Ubbe
To detect a transmission using CloseCall takes something like 1 or 2 seconds but using search could take minutes if you search all frequency bands, and by then the signal could be gone and not found.
/Ubbe
Great info thanks
Ubbe
Member
The instruction manual says that CloseCall are used to find frequencies and the function settings lack any means of setting decode modes like it does in search. There's probably a reason to why it isn't supposed to decode digital formats, even if it's hard to understand from a technical standpoint. When you find a signal you probably would want to know what it is and not just let you listen to meaningless digital noise.
/Ubbe
But it doesn't decode NXDN, P25, Tetra, etc. either.
So CloseCall is Analog only? I had hoped, somehow, someday, it would catch a Digi freq., thus me leaving it on. I'll turn it off now, and let my 996P2 do the Close Calling.
Sure wish they could get somebody in place to pep these things up. Nothing at all for the SDS series in years. Pitiful.
I'm not sure what you are doing different, but I find that Close Call works quite well. I run Close Call when traveling and have successfully captured P25 Phase 1, NXDN, and DMR signals. TETRA is a non-starter. I switch on the record option to capture the transmissions so I can go back and review (and listen) to my findings.
Last edited:
Here is a picture of a Close Call hit that decoded DMR quite nicely. These guys were talking so much, I ended up pushing the 'Avoid' button so I could capture other close call hits.
There is no luck involved. Close Call works.
Apparently not for everybody.....
- Status
Similar threads
SDS100/SDS200:
sds100/200 and NXDN channel
SDS100/SDS200:
SDS 200 programming question
