[EAS] EAS Digest, Vol 8, Issue 18

[Steven C Johnson]

>Message: 2
>From: "Bowen, Jonathan" <jBowen at rejoice.org>
>       <eas at radiolists.net>
>       <6836BE7D4557294F88D4A80528DF367549D12E489B at EXCHANGE01.pcci.int>
>Content-Type: text/plain; charset="iso-8859-1"

>Maybe I am mistake but doesn't the EAN,EAT and maybe even the NPT ignore the FIPS code anyway? If the box sees those event codes it retransmits them regardless of what FIPS are programmed into the machine.

>Quote from the forum post: "EAS Location Code will be Washington, DC. [Equipment manufacturers have said this will not be an issue, and no EAS unit re-programming is necessary.]"

>The test should just work without fiddling with any settings.

>Thank you

>Jonathan Bowen
>RBN/WPCS Field Engineer
> 

Jonathan,

It depends on the manufacturer.  Some ignore the FIPS code on an EAN.  Others check for a valid code before relaying.  Seems strange that these type accepted products react differently to an EAN.

Darryl, I agree that a national FIPS code of all zeros seems to be the way to go.  It's confusing to use the DC code for EAN and one more potential point of failure.  Using both, initially, might be the solution until everyone can gear up for the new code.

Steve
--
Steven C Johnson
Johnson Telecom, LLC
www.JohnsonTelecom.com
Steve at JohnsonTelecom.com
704 968 7031
AIM  SteveJNC
 
Join_My_Mailing_List_for_newsletters

EAS_Newsletter