From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,4cf2bf48a13f1d9 X-Google-Attributes: gid103376,public From: "Stanley R. Allen" Subject: Re: Clock Synchronization Date: 2000/07/14 Message-ID: <396F71EE.A1351E44@raytheon.com>#1/1 X-Deja-AN: 646457529 Content-Transfer-Encoding: 7bit References: <396ED195.8DED1C1A@ib-paus.com> X-Accept-Language: en Content-Type: text/plain; charset=us-ascii Organization: NASA, Kennedy Space Center Mime-Version: 1.0 Newsgroups: comp.lang.ada Date: 2000-07-14T00:00:00+00:00 List-Id: "Dr. Michael Paus" wrote: > > > We are running a distributed application on three PowerPC boards > which are connected via VME-Bus. The application is written in > Ada 95 (GNAT) and we use LynxOS as our RTOS. The problem we are > facing is that we need highly synchronized (~1ms) clocks on > each board. We are sending messages with time-stamps back and forth > and so it is important that each part of the application has the > same understanding of the time. Does anybody have an idea of how > to accomplish this without putting too much extra load on the > system? Does anybody know of a hardware solution for this problem > (a common clock which can be read from all CPU-boards)? > http://www.truetime.com http://www.datum.com These companies provide time cards that can be synchronized using an external signal. You'll need to have a central source for the time to distribute to each machine, probably a GPS receiver that can produce output in IRIG B format. The cost can be fairly high for a complete solution. Your applications will have to use the time card's clock instead of the motherboard clock. Another technique is to use the Network Time Protocol (NTP), which requires that a daemon be running on each machine (ntpd). One node is designated the 'server'; its daemon sends it's concept of time to the 'clients'. The daemons in the client will adjust the local CPU clocks, so you can use the local clock. The NTP daemons talk over an ordinary LAN, so there's no need for extra IRIG B wires. NTP is said to be good for applications needing about 1 millisecond resolution. For approx. 1 microsecond resolution, use the time cards. -- Stanley Allen mailto:Stanley_R_Allen-NR@raytheon.com