time on ostc

[lamentin]

hello,

my ostc (n°11-150 v1.29) have always 1 minute late per 36 hours on the time.

what is possible to do for this little problem ?

thank you for your answer.

Martial

[heinrichsweikamp]

Hello,

Is this a one-time offset or is the difference increasing?

Regards,
Matthias

[lamentin]

hi

the difference is increasing : every 36 hours, the time have 1 min late
after 3 days, i have 2 min late
......
after 1 month, it's about 18 min later
cheers
Martial

[lamentin]

and so ....What ?

nice to have an answer.

Thanks

Martial

[heinrichsweikamp]

Hello,

Sorry, we do not have a solution why this happen at your unit. What is the displayed air pressure at your place? I ask, because if the oscillator is wrong that much the air pressure reading should not be accurate as promised, as well.

Regards,
Matthias

[lamentin]

Patm= 1033 to 1036 mb

[heinrichsweikamp]

Hello,

I don't know where you are located but this is too much. The oscillator seems to be out of range. I'd recommend that we replace that part in your unit - please contact us at info@heinrichsweikamp.com

Thanks and best regards,
Matthias

[PeterT]

What is a more normal reading than? Mine shows 1022 to 1023mb at the moment, last week I had readings up to 1049mb! Everything seems to work fine, no time-issues. Last week I upgraded to 1.30, did 1 checkdive without any problems. Dephtreadings seemed OK compared to my Suunto!

grtz
Peter

[Hiasl]

PeterT Wrote:
-------------------------------------------------------
> last week I had
> readings up to 1049mb!

Did You do the dive in the Dead Sea?

[tacks16]

Same with my OSTC (#76) time difference from 21.02.09 till today is 15min.

andreas

[lamentin]

Difficult to resolve

[lamentin]

But it remains a great computer;)

[heinrichsweikamp]

Hello,

We're on it. I'll post a beta with a corrected clock soon. With some help from other users we'll find out if this is a hardware problem.

regards,
Matthias

[heinrichsweikamp]

Hello,

Maybe some other users can test this attached firmware? It has a bug fix that should correct the time on the OSTC, which seems to be a bit too slow in the prior versions.

It also shows the seconds of the actual time in surfacemode. Difference to the real time should be less then 5seconds/day.

regards,
Matthias

[Bech]

It is loaded, I will let you know in a few days if I come back ...

Raph

[lamentin]

Hello,
with the new version 1.32 I always have the same delay:
In 4 days the hour posts(shows) a delay of 2 minutes 40 seconds.
my hour of reference is double: watch and computer.
thank you very much

[Bradipo]

Hello,
I have been checking my computer's time for about 10 days (firmware v. 1.30), and it has not diverged significantly from the PC's clock, which is periodically synchronised with a time server. I would say that after 10 days the two clocks have diverged by 5 seconds at most.
I think that this result should rule out a firmware problem.

Regards,
Giovanni

[Olivier]

Hello,

Same problem as lamentin (with 1.32) : almost 1mn per day.


Regards

[tacks16]

same with my ostc 1min/day offset also with 1.32

[pem]

Yes,same with mine,its about 5 mins slow

[heinrichsweikamp]

Thanks for all the input - we'll rewrite this part of the firmware. The used oscillators are intend for clock use, so I think we should get more accuracy at all. Both, JDiveLog and Divinglog, allow auto-set time of the OSTC. I'd recommend to use this feature additionally.

regards,
Matthias