[EAS] : Fallout Over False Alert Continues

[Harold Price]

Phil,

It depends on your definition of "much".

My PC's time is set via WIN7's NTP process.  It seems to update every 
8 hours.  Right now, my PC time is 23 seconds slow.  PC clocks aren't 
very accurate.  It could just as well be 23 seconds ahead, and I know 
that I've seen it a minute off between win7 updates.  I might just 
have an outlier that is really bad.

That could result in my issuing a CAP alert a minute ahead, which 
would be plenty of time for it to get out to field devices and still 
be a bit in the future.  Unless you get the NTP time hack as you 
issue every alert (and mystate might, I'm just talking about my PC as 
it sits here) the time isn't going to be exact.

The time in the ENDEC is much better than my PC, as it maintains a 
clock drift calculation that adjusts for temp and xtal offsets.

Harold

At 02:23 PM 10/29/2014, Phil Johnson wrote:
>I believe that information is
>attached automatically when you hit "SUBMIT," apparently from the PC's
>real-time clock -- which should get its "hack" from the Internet.  So
>correct me, but the data and time data shouldn't be off by much when a test
>or alert is originated using this method.
>
>Phil Johnson
>