DM42- clock losing time

Post here to share useful tips and tricks, to ask questions about using your DM42 or to report software-related problems
cappy
Posts: 68
Joined: Sun Jul 30, 2017 5:30 pm

Re: DM42- clock losing time

Post by cappy » Thu May 09, 2019 5:22 pm

It's really a shame we can't get a reply from the developers on this issue
DM42 SN: 0612

keithdalby
Posts: 544
Joined: Mon Apr 24, 2017 6:38 pm

Re: DM42- clock losing time

Post by keithdalby » Thu May 09, 2019 9:16 pm

Issue?

rprosperi
Posts: 491
Joined: Mon Apr 24, 2017 5:48 pm
Location: New York

Re: DM42- clock losing time

Post by rprosperi » Fri May 10, 2019 2:30 am

cappy wrote:
Thu May 09, 2019 5:22 pm
It's really a shame we can't get a reply from the developers on this issue
It's not clear that there is an issue, just some vague comments that you think it lost some amount of time over some other amount of time; you noted yourself that you didn't even record it.

I suggest you do this, to help characterize if there is an issue:

1. Update to the latest f/w
2. Set the time precisely and record the time that you set it (using a reliable, objective source)
3. Enjoy life for a couple months
4. Come back and check the time on the DM42 vs. the original source, and record the difference

Then come back here and report it. Either the result is there is not enough difference to matter, OR that you've provided a solid case that something is amiss and a basis for SM to investigate.
--bob p

DM42: β00071 & 00282

cappy
Posts: 68
Joined: Sun Jul 30, 2017 5:30 pm

Re: DM42- clock losing time

Post by cappy » Fri May 10, 2019 3:21 am

keithdalby wrote:
Thu May 09, 2019 9:16 pm
Issue?
The clock losing time, after no use for an extended period.
DM42 SN: 0612

cappy
Posts: 68
Joined: Sun Jul 30, 2017 5:30 pm

Re: DM42- clock losing time

Post by cappy » Fri May 10, 2019 3:23 am

rprosperi wrote:
Fri May 10, 2019 2:30 am
cappy wrote:
Thu May 09, 2019 5:22 pm
It's really a shame we can't get a reply from the developers on this issue
It's not clear that there is an issue, just some vague comments that you think it lost some amount of time over some other amount of time; you noted yourself that you didn't even record it.

I suggest you do this, to help characterize if there is an issue:

1. Update to the latest f/w
2. Set the time precisely and record the time that you set it (using a reliable, objective source)
3. Enjoy life for a couple months
4. Come back and check the time on the DM42 vs. the original source, and record the difference

Then come back here and report it. Either the result is there is not enough difference to matter, OR that you've provided a solid case that something is amiss and a basis for SM to investigate.
Another user just reported the same thing, in this thread.
Given that I had the latest firmware when I reported it, and it’s been months since I posted the original message..
I think there’s enough information there for people with multiple DM-42’s to do the experiment and report.
DM42 SN: 0612

keithdalby
Posts: 544
Joined: Mon Apr 24, 2017 6:38 pm

Re: DM42- clock losing time

Post by keithdalby » Fri May 10, 2019 4:18 am

Are we talking a few seconds different per month? A few minutes? A few hours? A few days?

It's a calculator, not a precision time piece. A little lost time is not an issue.

cappy
Posts: 68
Joined: Sun Jul 30, 2017 5:30 pm

Re: DM42- clock losing time

Post by cappy » Fri May 10, 2019 5:30 am

keithdalby wrote:
Fri May 10, 2019 4:18 am
Are we talking a few seconds different per month? A few minutes? A few hours? A few days?

It's a calculator, not a precision time piece. A little lost time is not an issue.
Many minutes over several months.

There are precision clock sources driving most microcontrollers (some use the cheesy resonators), there’s no excuse for that much loss of time especially in such a short period. I wouldn’t expect that much Lost time until several years have lapsed.
DM42 SN: 0612

User avatar
Walter
Posts: 1060
Joined: Tue May 02, 2017 9:13 am
Location: Close to FRA, Germany

Re: DM42- clock losing time

Post by Walter » Fri May 10, 2019 11:05 am

I can confirm that the DM42 clock has a precision in the order of minutes, not seconds. My DM42 is 11 minutes ahead of true time today - I adjusted it several months ago (sorry I didn't record that date).

I concur it's a calculator, not a clock, even less a precision clock. Nevertheless (and as mentioned in post #2 of this thread already), this precision is not conforming with a quartz-controlled clock which is standard nowadays even at low cost devices.

And it bears the name "SwissMicros" which certainly sets expectations ... ;)
DM42 SN: 00041 --- Follower of Platon.

HP-35, HP-45, ..., HP-50, WP 34S, WP 31S, DM16L

cappy
Posts: 68
Joined: Sun Jul 30, 2017 5:30 pm

Re: DM42- clock losing time

Post by cappy » Fri May 10, 2019 4:31 pm

Walter wrote:
Fri May 10, 2019 11:05 am
I can confirm that the DM42 clock has a precision in the order of minutes, not seconds. My DM42 is 11 minutes ahead of true time today - I adjusted it several months ago (sorry I didn't record that date).

I concur it's a calculator, not a clock, even less a precision clock. Nevertheless (and as mentioned in post #2 of this thread already), this precision is not conforming with a quartz-controlled clock which is standard nowadays even at low cost devices.

And it bears the name "SwissMicros" which certainly sets expectations ... ;)
Thanks for confirming this Walter
DM42 SN: 0612

User avatar
Jebem
Posts: 21
Joined: Sat Jul 22, 2017 10:21 pm
Location: Portugal

Re: DM42- clock losing time

Post by Jebem » Fri May 10, 2019 6:04 pm

Despite using a 32768khz reference device (be it a crystal or a resonator or whatever they are using on it), the time depended on two factors:

1. Hardware oscillator circuitry precision. The hardware design, namely the load components used affect the frequency that will not be exactly 32768khz if the project was not covering this clock "feature". Also the crystal/resonator type will have its own precision tolerances, namely to temperature changes.
So to have a precision clock it requires adequate hardware design to support that "feature" in first place.

2. Software design. As already mentioned, documentation exists to be followed that covers the different processor states in order to maintain good accuracy, as long as the hardware oscillator precision can be trusted.

I don't remember to see any adverts from the manufacturer concerning the precision of the clock but i might be wrong.

Post Reply