NTP time provider and ticksPerSecond

[Michael Westfall <mwestfal@gemini.edu>]

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