[EAS] EAN Natioanl Always ?

Ira Wilner bdcst at vermontel.net
Thu Sep 22 12:47:50 CDT 2011


And in my case in New Hampshire the EAN might prove interesting as I am 
monitoring both the PEP station, WBZ (AM) and NPR via NHPR on FM.  Both 
stations are running IBOC, so there are inherent delays of 8 or more seconds 
plus satellite system and STL delays.  NHPR uses satellite fed STL's.  And 
to add to the confusion NHOEM is also monitoring the PEP station and will 
relay it across their UHF radio link to our LP-1.  Three ways to receive the 
EAN the timing of which is unknown.

Whichever source reaches my Sage Endecs first will grab my stations' air. 
My only fear is, if it is the AM PEP station and it fades into noise before 
the EOM we'll have to manually end the latched EAN.  Space weather and time 
of day can really mess up ground wave reception with out of phase sky-wave.

Only my LP-1 is monitoring the PEP. The rest of the stations in my cluster 
are monitoring the LP-1, also with an 8 second IBOC delay and they also 
monitor the NPR EAS feed from NHPR.  So they may end up broadcasting the 
better FM audio from NPR.   Either way the EAN should make it onto the 
airwaves here.

--Ira

*******************************************************************************

----- Original Message ----- 
From: "Harold Price" <hprice at sagealertingsystems.com>
<eas at radiolists.net>

> If things are running
> well, the EAN would come down the national feed, but would still be
> finding its way down the pep/state/lp chain.  At the local affiliate,
> you'd get the start of the alert on the national feed (if it got it
> first), then your local device would start it up - causing
> confusing/partial messages to the public. 



More information about the EAS mailing list