[EAS] Listening to EAS over the air

Sean Donelan sean at donelan.com
Wed Aug 22 21:53:35 CDT 2018


As I previously mentioned, I leave some bench test EAS systems idling on 
random Washington DC area stations. This is not about enforcement. Most 
stations are compliant. The EAS box may log everything was ok, but when 
you listen to what is actually on the air, sometimes there are other 
issues.

Based on today's RMT, I pulled some recordings of the on the air 
performance.

For reference, this is the LP-1 origination station source recording for 
August 22, 2018's RMT:

http://www.donelan.com/WTOP_20180822_RMT.mp3

I've trimmed the remaining recordings, so they have a couple of seconds 
before and after the EAS transmission.

Next, an example of a switching glitch cutting off the end of the EAS 
message. WWDC does a good job, but has a slight timing glitch switching 
back to its programming. It cuts off two of three EOMs. Likely just need 
to adjust the timers. The EAS logs won't shows this. You need to listen to the 
on-air transmission.

http://www.donelan.com/WWDC_20180822_RMT.wav

Next is an example of barely understandable audio. WZHF is the Russian 
programming station in Washington DC.  Its 100% compliant, and barely 
understandable. Nevertheless, barely understandable is still 
understandable so I give it a pass.

http://www.donelan.com/WZHF_20180822_RMT.wav

And finally, this is SIRIUSXM.  Unlike Satelite TV providers, Satellite 
Audio Radio (only 1 now) creates its own RMT, and doesn't coordinate 
with any other EAS RMT. SiriusXM tends to use the same schedule as 
Washington DC for its RMTs. Guessing audio levels on the barker channel 
is a bit challenging, I can't tell what level will be representative of 
the FEMA audio levels when it acts as a PEP.

http://www.donelan.com/SIRIUSXM_20180822_RMT.wav

My point is engineers need to use their ears, not just check the EAS log.



More information about the EAS mailing list