Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!ucsd!ucbvax!udel.edu!Mills
From: Mills@udel.edu
Newsgroups: comp.protocols.time.ntp
Subject: Re:  Heath clock timing, and building a WWV clock
Message-ID: <9010311350.aa02306@huey.udel.edu>
Date: 31 Oct 90 18:50:27 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: inet
Organization: The Internet
Lines: 11

Rich,

I had an early Heath WWV model, too. The only defect I found 
obviously due to firmware was an incorrect rollover at the end
of the month to day 0, not day 1. Heath replaced the CPU at
no cost. I have also noticed the same thing as you - locking
to a timewarp, but this happens (less frequently) to WWVB
clocks, too. That's why we need multiple redundant, diverse
peers.

Dave