Re: NTP time provider and ticksPerSecond

[Michael Westfall <mwestfal@gemini.edu>]

Thanks.

Yes, we're using base-3.14.12.4

I had already fixed it here by adding the following to osiNTPTime.c:

/********************************************************
 * This function added my MDW 2016-005-17 to notify
 * NTP time provider that the system tick rate has been
 * updated.
 */
void NTPTimeUpdateTickRate(void)
{
    NTPTimePvt.ticksPerSecond = osdTickRateGet();
    NTPTimePvt.nsecsPerTick   = NSEC_PER_SEC / NTPTimePvt.ticksPerSecond;
}

Our custom clock tick provider driver calls this after changing the system tick frequency.

I do like the idea of the NTP time provider updating it's tick frequency automatically like in the patch you attached.   That's a more elegant solution.

On Tue, May 17, 2016 at 12:24 PM, Andrew Johnson <anj@aps.anl.gov> wrote:

Hi Mike,

On 05/17/2016 11:05 AM, Michael Westfall wrote:
> 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?

There was a change committed to the 3.15 branch of Base before 3.15.1 to
make the NTP time provider adjust automatically to changes in the system
clock tick rate. Changing the tick rate after iocInit is not advisable,
but in your case this change may be all you need. Since you're evidently
using a 3.14.12 release of Base you should be able to apply the attached
patch file to your copy.

HTH,

- Andrew

--
Arguing for surveillance because you have nothing to hide is no
different than making the claim, "I don't care about freedom of
speech because I have nothing to say." -- Edward Snowdon

--

Mike Westfall

Control Systems Software Engineer