[EAS] EAS Digest, Vol 8, Issue 17

[Dave Kline]

On the other hand...
What if... and I realize it is a big what if.
But what if, there were to be a real EAN before the test came down.
Do we program our equipment (maybe at the last minute if at all) to be  
able to handle a scheduled test?
Or do we program to handle the real thing if it occurs?
If you can honestly say you feel comfortable that your box is set up  
properly for an EAN then OK. If it still fails the test then you've  
got more work to do.
But if you knew there were possible issues and did nothing because you  
wanted to wait for the test to see what would happen and missed a real  
EAN...
Well you see where this could go.

Just another though on the subject.
Dave

************************************************
Dave Kline   UNO-TV / KVNO
University of Nebraska at Omaha
6001 Dodge St. Omaha, NE  68182  CPACS 200
************************************************

On Jun 24, 2011, at 12:05 PM, Lowell Kiesow wrote:

> It is just a test.  A test is for learning where the problems
> occur.  If there is an issue with FIPS addresses, then let the test
> fail on any equipment that doesn't recognize it.  In my opinion, we
> should not take special measures to make the test work. That
> invalidates the test and the very reason for doing it.  If we cover
> up a problem by making adjustments to EAS boxes, how else will they
> find out the extent of the problem?  There are no negative
> consequences for broadcasters if the test goes down in flames.  The
> best way for FEMA to learn is by failure.