Page 1 of 2

Change Auto-Power-Off Time?

Posted: Tue Feb 25, 2020 4:30 pm
by J Peters
Is the auto-power-off time fixed on the DM42, or can it be changed somewhere? Thanks.

Re: Change Auto-Power-Off Time?

Posted: Tue Feb 25, 2020 5:34 pm
by Walter
I think it can be changed by David only so far.

Re: Change Auto-Power-Off Time?

Posted: Sun May 17, 2020 11:47 am
by Walter
Hmmh, looking at it again, I came across the following observations:
  • In the Free42 manual linked at SwissMicros DM42 site is stated in chapter 12 about flag #44:
    Always on. If true the calculator does not turn off after about 10 minutes.
    .
  • In chapter 14 of the same manual you find the function ON. It reads:
    ON Continuous on. Prevent the calculator from automatically turning off after ten minutes of inactivity.
    .
  • The DM42 automatically powers off after 10 minutes of inactivity regardless of the ON function executed or not. But I don't find anymore where this behaviour is documented or even justified.
What did I miss? Thanks in advance for your response.

(Addendum: Inactivity := no user interaction & no program running. But how does the DM42 know there's something running?)

Re: Change Auto-Power-Off Time?

Posted: Sun May 17, 2020 4:27 pm
by rprosperi
Walter wrote:
Sun May 17, 2020 11:47 am
[*]The DM42 automatically powers off after 10 minutes of inactivity regardless of the ON function executed or not. But I don't find anymore where this behaviour is documented or even justified.[/list]
The ON function (disabling the auto-power-off after 10 mins) is described on p. 323 of the 42S OM. (not sure if you were asking about this?)

The DM42 does correctly set fag 44 when executing ON, however you're right that it doesn't honor that setting and remain on indefinitely, so it needs to be explored.

Thanks Walter.

Re: Change Auto-Power-Off Time?

Posted: Tue May 19, 2020 8:21 am
by jonmoore
rprosperi wrote:
Sun May 17, 2020 4:27 pm
The ON function (disabling the auto-power-off after 10 mins) is described on p. 323 of the 42S OM. (not sure if you were asking about this?)

The DM42 does correctly set fag 44 when executing ON, however you're right that it doesn't honor that setting and remain on indefinitely, so it needs to be explored.

Thanks Walter.
[/quote]

Bob, linking this inquiry through to the DM41x. I tend to use my hardware permanently connected to a USB power source, and wondered if the power off setting could be changed (and honoured). Ideally I'd like both the ability to change the time setting and to disable power off altogether.

Re: Change Auto-Power-Off Time?

Posted: Tue May 19, 2020 2:46 pm
by rprosperi
The time setting can be changed in the 41 interactively using SETIME, or in a program via T+X.

[ON] suspends auto-power-off (same as the DM42/Free42 but does work on the 41X).

These are all normal 41 OS features.

Re: Change Auto-Power-Off Time?

Posted: Tue May 19, 2020 3:04 pm
by Walter
rprosperi wrote:
Tue May 19, 2020 2:46 pm
[ON] suspends auto-power-off (same as the DM42/Free42 but does work on the 41X).
Hmmh, do you mean this works on the 41X but doesn't on the 42? Please confirm or deny.

Re: Change Auto-Power-Off Time?

Posted: Tue May 19, 2020 3:21 pm
by rprosperi
Walter wrote:
Tue May 19, 2020 3:04 pm
rprosperi wrote:
Tue May 19, 2020 2:46 pm
[ON] suspends auto-power-off (same as the DM42/Free42 but does work on the 41X).
Hmmh, do you mean this works on the 41X but doesn't on the 42? Please confirm or deny.
Yes, works on the 41X (last time I tested it, months ago), but seems to not work on the DM42, which should be corrected in the future.

Re: Change Auto-Power-Off Time?

Posted: Tue May 19, 2020 6:12 pm
by dlachieze
Just tested on my DM41X (DM41X V1.12a / DMCP 3.19): [ON] doesn't prevent the calculator to power-off after 10 minutes of inactivity.

Re: Change Auto-Power-Off Time?

Posted: Tue May 19, 2020 6:32 pm
by jonmoore
dlachieze wrote:
Tue May 19, 2020 6:12 pm
Just tested on my DM41X (DM41X V1.12a / DMCP 3.19): [ON] doesn't prevent the calculator to power-off after 10 minutes of inactivity.
Beat me to it. Got the same results here.

Maybe something in the underlying system firmware has changed since Bob last tested.