Can anyone comment on how the SDS200 sounds on an analog EDACS system? My town still uses this type of system with no plans for a system upgrade to my knowledge (at least not in the foreseeable future). I currently have an HP-2 and there is a horrible buzzing/grinding noise at the beginning of almost every transmission on this system. I don't know if it's a problem with how the HP-2 handles EDACS or if there is a problem with the radio system itself. It has become very annoying to listen to. I might upgrade to the SDS200 if it would solve this problem.
SDS 200 - EDACS
- Thread starter ansky
- Start date
- Status
DataSquid
Member
You'll love the SDS200. It'll solve that problem by missing the first parts of the transmission by about 2/3rds of a second. At least in the current firmware. I have hope this bug will get sorted out, but given EDACS isn't top-of-mind nowdays, it's likely it'll get passed over.
My 800MHz EDACS system sounds about the same on my SDS200 and my HP436. My coverage is prone to continual short bursts of noise/static crashes, and the filters in the SDS200 help with that I find. But the antenna is the biggest X-factor for this system.
My 800MHz EDACS system sounds about the same on my SDS200 and my HP436. My coverage is prone to continual short bursts of noise/static crashes, and the filters in the SDS200 help with that I find. But the antenna is the biggest X-factor for this system.
Does this bug occur on all analog transmissions or just on EDACS? I listen to a ton of analog so that would be a deal breaker for me.
DataSquid
Member
If it does it's not noticeable. I don't park on other analog systems that often like I do our single site EDACS one, and so it's more evident that it's missing the start of the comm during back-and-forths.
My hunch is that because EDACS isn't pure-analog (our system also has ProVoice traffic but I'm not buying the license as it's all encrypted) it's doing that 400ms or so "decide if its digital" hold-off at the start. However, for these system types, there seems to be no way in Sentinel to lower that threshold as it thinks they're pure analog. Why that doesn't happen with my 436 is a mystery (though it does have the ProVoice key).
I'd also note that the hugely annoying "bonk" of grindy almost alarm-like sound (I hear when 2 units walk over each other on the same TG) is something that was happening often when a new group came online with our EDACS system last year. Like,"often" meaning just about every time they keyed up. It's as if the system wasn't configured right, and instead of getting an immediate grant they were held-off for a little bit and bonking out during. But the operators didn't seem to notice or care. So it might be a system configuration issue (or design feature to annoy scanner users) that might never resolve.
This thread may shed some light...
https://forums.radioreference.com/threads/edacs-anti-scanner-tones.114348/
https://forums.radioreference.com/threads/edacs-anti-scanner-tones.114348/
EDACS is always a Analog trunk system period.. no matter if it using analog FM or Digital FM (ProVoice) audio modes....
Sent from my SM-G935V using Tapatalk
Sent from my SM-G935V using Tapatalk
Your in WO if I remember correctly. The SDS200 receives EDACS just fine. I hear the same noises you’re talking about, I think it’s a WO system thing.
I am surprised that they are staying with EDACS, especially since parts and support are end of life. I know the PD and FD have complained of poor coverage for years. I also read somewhere awhile back, that they were going to go P25 using the same frequencies.
Sent from my iPad using Tapatalk
- Status
Similar threads
SDS100/SDS200:
SDS-200 "Service Type" question
