[EAS] Ira's Comments

[Tom Spencer]

That's not an insurmountable obstacle, though...  I can think of a 
couple of legacy codes that could be used to implement a GMC 
conversion.  First, and most obvious, would be to convert GMC to EAN, 
with an EAS originator code.  That would have to be authorized in the 
Rules, of course, but it would work.  A GMC converted to legacy might 
carry CIV as originator and CEM as the event code, would be another.  
The legacy endec would have to be programmed to recognize that whatever 
the combination used is A) valid, and B) a must-carry message similar to 
the Presidential access.  But it could be done.  The Rules would have to 
be written to allow the GMC to be translated into a specific legacy 
code, I'd think... especially if the event code were to be EAN.  The 
converter would have to recognize the difference between EAS EAN = GMC 
and PEP EAN = Presidential Message

Just a thought...

ed.czarnecki at monroe-electronics.com wrote:
> 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. 
>   

-- 
Tom Spencer