[EAS] Sorry, the FCC notice and EAS handbook are attached to this email. ##

[Harold Price]

I understand Mike's point of view here, and sometimes you gotta do 
what you gotta do.  But, there are implications, including what Alan 
has led us to, that are important to consider.  More inline below.

At 05:12 AM 8/20/2016, Alan Alsobrook wrote:
>On 8/19/2016 5:56 PM, Mike McCarthy wrote:
> > When I have a market manager and slew of PD's yelling at me to "Get that
> > !@#$%^&*() shut down", the power cord is the FIRST thing that gets pulled.
> >   BTDT....and have the loss of hearing to prove it.....
>
>Humm, guess I need to test and see if powering off the 3644 will allow
>an attached MSRP in the equipment room to resume normal operation.

Alan,

No, cutting power to the ENDEC won't clear devices that use serial 
ports or the LAN to receive switching commands.  Cutting power also 
won't clear any downstream EAS devices if other stations monitor yours.

Attached devices that use contact closures in the closed state to 
switch will clear immediately when power is lost and the relays open.

The MSRP and similar devices use serial port commands.  These will 
only be reset to the pass-through state when the ENDEC comes back up, 
though this will take up to 40 seconds.

The best first choice to abort a bad EAN, NPT, or any event sent in 
error is to use the abort or end buttons on the web interface or the 
front panel.  That will put all connected equipment back in the 
normal post-alert state, and will send the EAS End of Message (EOM) 
code so that downstream stations that monitor yours will also 
terminate normally.

And as regards downstream stations in the daisy chain when an 
incoming alert ends without an EOM: for most alert types, the ENDEC 
will time out after two minutes, though some of those minutes will 
have been spent relaying upstream programming.

For an EAN, however, downstream stations will continue to relay the 
upstream station without time limit.  If you know that your station 
has sent EAN headers, but for whatever reason has not sent the end of 
message, the best thing to do is to send an RWT as soon as 
possible.  The RWT's EOM will terminate the downstream EAN.

If the EAN header did go to air, but the EOM didn't, even for reasons 
that have nothing to do with the ENDEC - say someone/something 
switched the ENDEC out of the air chain before the EOM was sent, 
downstream stations will appreciate it if you get an RWT on the air.

Sage's recommendation:

If your ENDEC is sending an alert that you want to get off the air 
quickly, first try to abort the alert normally by using the end or 
abort buttons on the web interface or the front panel.  This will 
restore your local equipment to its normal state, and will end the 
alert normally for stations that monitor your station.  It may take a 
few seconds to complete the abort, depending on where you are in the 
alert process when you start the abort.  The ENDEC will always send a 
complete header sequence once that sequence has started, and the 
ENDEC will always send all of the end of message data bursts at the end.

Pulling power to the ENDEC may leave your station's switching 
equipment and automation in an indeterminate state.  It may also 
cause extra problems for stations that monitor your station. Powering 
off the ENDEC should be done only if the alert can't be aborted from 
the web page or the front panel.

Harold