SDS100/SDS200: Audio Transmission Cut off

[Jeremy1873]

Hello, I just got my SDS100 scanner and I'm having issues with my transmission being cut off in the beginning. I don't know if that's normal or not, but sometimes the beginning audio cuts off while other times it doesn't. I thought the scanner scans then switches to the frequency or TG that is transmitting so I get everything, but again i don't know if i programed it wrong or something. Any information or help to fix my issues would mean a lot.

 

[tvengr]

A scanner can scan only one system or site at a time. It takes over a second to scan a site in a trunked system, While you are scanning a site, transmissions on another site or system may have already started and you will not hear it until you get back to scanning that site or system. As a result, you lose the beginning of the transmission. You should limit your scanning to a minimum of local sites and systems to avoid missing activity. If you are scanning a single trunked system with a single site, you will hear the first talkgroup active immediately. You will still not hear activity on another talkgroup until the activity on the current talkgroup is completed. The more you scan, the less you will hear. The solution is to use multiple scanners with each monitoring a single system. In my vehicle, I have one scanner monitoring my local fire and another for the local police. Otherwise, if the police are busy, I would miss fire activity, and if fire is busy, I would miss police activity.

 

[Ubbe]

I don't know if that's normal or not, but sometimes the beginning audio cuts off while other times it doesn't.

If it cuts off the start when you hear a dispatcher make a call and then the response from a mobile unit are cut in the beginning, then try increasing the delay for the TG. It's default value are 2 sec and that might be too short ans the scanning will continue if the mobile unit are slow to respond. Try setting all TG's to 5 sec. In Sentinel you can set one TG to 5 sec and copy that value and then mark all TG's in a department, mark first line and hold shift while click on the last and paste, and change delay to 5 sec in one go.

Unfortunately if you scan from the database it is fixed at 2 sec and cannot be changed. We hope a firmware update will make that user adjustable.

/Ubbe

 

[Jeremy1873]

If it cuts off the start when you hear a dispatcher make a call and then the response from a mobile unit are cut in the beginning, then try increasing the delay for the TG. It's default value are 2 sec and that might be too short ans the scanning will continue if the mobile unit are slow to respond. Try setting all TG's to 5 sec. In Sentinel you can set one TG to 5 sec and copy that value and then mark all TG's in a department, mark first line and hold shift while click on the last and paste, and change delay to 5 sec in one go.

Unfortunately if you scan from the database it is fixed at 2 sec and cannot be changed. We hope a firmware update will make that user adjustable.

/Ubbe

Thank you I’ll give this a try

 

[Jeremy1873]

A

A scanner can scan only one system or site at a time. It takes over a second to scan a site in a trunked system, While you are scanning a site, transmissions on another site or system may have already started and you will not hear it until you get back to scanning that site or system. As a result, you lose the beginning of the transmission. You should limit your scanning to a minimum of local sites and systems to avoid missing activity. If you are scanning a single trunked system with a single site, you will hear the first talkgroup active immediately. You will still not hear activity on another talkgroup until the activity on the current talkgroup is completed. The more you scan, the less you will hear. The solution is to use multiple scanners with each monitoring a single system. In my vehicle, I have one scanner monitoring my local fire and another for the local police. Otherwise, if the police are busy, I would miss fire activity, and if fire is busy, I would miss police activity.

I see thanks