[EAS] TFT Equipment Support

[Sean Donelan]

On Fri, 17 Jun 2016, Mike McCarthy wrote:
> I have no dispute with the operational realities you ascribe below. Few
> NWS EAS messages outside of TOR and FFW's are relayed.
>
> Never the less, the adoption of of new message codes would be an issue.
> Even more so if the FCC mandates all endec's contain all FIPS codes going
> forward. This is a real possibility which the new rules might require.

Of course, no one outside knows for certain what the FCC is going
to do at the next commission meeting on EAS.  Sometimes, I don't think
anyone inside the FCC knows either.

I'm just pointing out that in the past, the FCC tried to grandfather 
existing EAS equipment in rule changes.  The 2002 Event Codes were only 
required for "new" equipment, participants were not required to update
existing EAS boxes. The FCC included the option for a CAP intermediary 
device connected to existing EAS boxes, and didn't require replacing 
existing EAS boxes.

If the FCC adds new EAS event codes (which is likely), I expect the FCC 
would grandfather existing EAS boxes just like the 2002 order.  So I 
wouldn't panic about some new EAS event codes.

The "000000" change was probably difficult for FCC because the 2015 EAS 
order was essentially the first time the FCC is requiring software/firmware
changes in some (not all) old EAS equipment.  Every vendor has
interpreted/implemented it differently for 20 years.  As I keep pointing 
out, that doesn't mean any vendor was right or wrong; just different.
If you are still using a Hollyanne EAS box, it may be time to replace it.

Other old EAS boxes may pass "000000" without problem.  As far as I 
know, the FCC has not revoked the type acceptance of any old EAS boxes.
If the vendor still supports old EAS boxes, you should ask them for a
definitive answer. If the EAS box no longer has support, you are on your
own.