[EAS] Ira's Comments

[ed.czarnecki at monroe-electronics.com]

I would have to respectfully disagree with the statement made that "replacing the complete system with a new box will require a lot more in the way of configuration to even get it working like the old EAS decoder." 

Both products mentioned by Clay (DAS DASDEC and Sage) natively support the legacy EAS.  No more configuration needed here than one would usually expect.

Both products also natively support CAP next-gen EAS - which as stated is a matter to "get it talking to the internet to be able to go fetch (or receive, BTW) CAP alerts."

Also stated "that's the same problem with the all-in-one boxes--they may be set up to relay EAN's and RMT's but simply dump to memory everything else."  Not sure I follow the point here.  So long as EAS is a volunteer activity, broadcasters of course have the option of not airing selected event codes (except for EAN, which is locked in the unit, and RMT, which you should not ignore.

However, things become less-than-voluntary with the forthcoming Governors Must Carry capability.  There is a specific CAP parameter that triggers the GMC function (as adopted by FEMA, see www.eas-cap.org).  With converter boxes, generically speaking, that required CAP parameter won't translate to FSK a legacy EAS encoder decoder can understand and act on. 

Just in the spirit of trying to clarify a few points...

Edward Czarnecki, Ph.D.
Senior Director - Strategy, Development and Regulatory Affairs
Monroe Electronics, Inc. / Digital Alert Systems
ed.czarnecki at monroe-electronics.com

www.monroe-electronics.com
www.digitalalertsystems.com