Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!watmath!clyde!bonnie!akgua!sdcsvax!dcdwest!ittvax!decvax!mcnc!ncsu!ikonas!joels@tektronix.UUCP (Joel Swank) From: joels@tektronix.UUCP Newsgroups: net.micro.cbm Subject: Re: time inaccurate on VIC Message-ID: <3718@tektroni.UUCP> Date: Thu, 27-Sep-84 12:12:30 EDT Article-I.D.: tektroni.3718 Posted: Thu Sep 27 12:12:30 1984 Date-Received: Sun, 30-Sep-84 04:22:46 EDT Lines: 19 References: <1401@emory.UUCP> Relay-Version:version B 2.10.1 6/24/83; site ncsu.UUCP Posting-Version:version B 2.10.1 (Tek) 9/26/83; site tektronix.UUCP Path:ncsu!mcnc!decvax!tektronix!joels Message-ID:<3718@tektronix.UUCP> Date:Thu, 27-Sep-84 12:12:30 EDT Organization:Tektronix, Beaverton OR () I also have used VICs for dedicated control applications. I found that they all have inaccurate clocks. Some run fast and some run slow. Each one is different. I wrote some automatic corrrection code into my program. I found that even the ammount of error varied over time on the same machine. I have to set the time at least once a week to maintain accuracy to within a couple of minutes. I'm afraid that if you need extreme accuracy over a long period of time, the only answer will be a hardware clock. Joel Swank Tektronix, Beaverton OR