Slowing the clock (time) down

[Gizmo]

Is it possible to adjust the time on the OSTC2?

Currently mine is gaining just under 1 minute per day.
I am running V1.60.

[heinrichsweikamp]

This will be available in the coming 1.63 (This week).

regards,
Matthias

[Gizmo]

Thanks Matthias for the quick reply!

[Gizmo]

I am now running V1.70, can you tell me where i can find the settings so can slow the time down so it does not keep gaining 1 minute per day.

[Olivier]

See CF 48

[Gizmo]

Olivier Wrote:
-------------------------------------------------------
> See CF 48


Ah thanks, i only checked the wiki (not in there yet)

So with the default being 42, what would you guestimate the setting to be to loose a minute every 24 hours?

[heinrichsweikamp]

Hello,

- Set this value to zero
- Set time at 12:00
- Wait 24h
- Check offset (Internal clock may be slower then actual clock)
- enter this offset into CF42

regards,
Matthias

[David Tobin]

The value entered in CF48 represents 1 sec offset
So if you time is say 90 sec fast, you enter 90
Can I assume the time is never too slow

[Gizmo]

heinrichsweikamp Wrote:
-------------------------------------------------------
> Hello,
>
> - Set this value to zero
> - Set time at 12:00
> - Wait 24h
> - Check offset (Internal clock may be slower then
> actual clock)
> - enter this offset into CF42
>
> regards,
> Matthias

OK i am struggling here a bit! Should this offset be in CF42 (Blink Gas) or CF48 (Time offset)?

(CF48 default is 42,8B)
I set CF48 to 0, set the clock, waited 24 hrs and entered the offset (which was 77 seconds) so i set CF48 to 77
24 hrs later the clock still gained (approx) 1 min,

So as an experiment i set CF48 to 7 (default = 42, minus the 35 I had increased it = 7) yet it STILL gains 60 seconds every 24hrs!!

Where am i going wrong??

[Mike Coull]

I am also finding that my unit is gaining time, any pointers on how to fix this, I am running V1.70

[heinrichsweikamp]

> > - Set this value to zero
> > - Set time at 12:00
> > - Wait 24h
> > - Check offset (Internal clock may be slower
> then
> > actual clock)
> > - enter this offset into CF42

CF48, of course....

The algorithm is really simple, the amount of seconds in CF48 is added at midnight. That means the really exact time is only available at 12 o'clock. Before and after that a small error of some seconds is (unwanted but) normal.

Just follow the above procedure exactly if the offset is too big and/or sync with the PC time at least once/month (It's just one click in Divinglog or JDiveLog).

regards,
Matthias