Experimental Physics and
Industrial Control System

Is there a way to delay initializing the NTP time provider until after my custom clock tick provider has set the system clock tick rate?

The problem seems to be that NTPTime during it's InitOnce routine fills in it's private data structure with the system ticks per second by calling osdTickRateGet(). But this happens before my custom clock tick provider is initialized and changes the clock tick rate.

There doesn't seem to be a way of informing the NTP Time provider of an updated clock tick rate.

Perhaps there is a way to unregister the NTP Time provider, then re-register it again so that it'll reinitialize with the updated tick rate?

--

Mike Westfall

Control Systems Software Engineer

Replies:

Re: NTP time provider and ticksPerSecond Andrew Johnson

Navigate by Date:

Prev: error when make base3.15.3 梁雅翔

Next: Re: NTP time provider and ticksPerSecond Andrew Johnson

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 

Navigate by Thread:

Prev: Re: error when make base3.15.3 Henrique Almeida

Next: Re: NTP time provider and ticksPerSecond Andrew Johnson

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