1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 <2007> 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 2025 | Index | 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 <2007> 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 2025 |
<== Date ==> | <== Thread ==> |
---|
Subject: | RE: Setting an IOC clock from the vxWorks shell |
From: | "Thompson, David H." <[email protected]> |
To: | [email protected], tech-talk <[email protected]> |
Date: | Tue, 27 Feb 2007 14:30:52 -0500 |
Timo, Sheng Peng, and I have been
collaborating on a package that loads onto an IOC that may help you. It
replaces the NTP client in iocClock with a system that provides for multiple
time providers on an IOC, one of which is the vxWorks clock. The vxWorks
clock is set periodically when NTP or a better time provider is
available. It supports hardware timing systems as well. One
of the things it does is fall back to internal timekeeping if the NTP server
fails, all transparently. You can get it at http://ics-web1.sns.ornl.gov/share/generalTime.tar.gz. There were presentations on it at the APS
and SLAC EPICS meetings. From: J. Frederick Bartlett [mailto:[email protected]] Recently we have been having problems with IOC
timestamp synchronization on our EPICS network. The timing master is
unable to obtain timing information from our ntp server -- see Geoff Savage's
techtalk note on 15 Feb 2007. While we are finding the solution to that
problem, I would like to make one of our IOC's a timing master and set its clock
to approximately the correct time. Does anyone know of a method of setting the
IOC's clock from the vxWorks shell?
-- J. Frederick Bartlett Fermi National Accelerator Laboratory D0 Experiment/Online Systems and Controls
[email protected] 630-840-4058
|