TIMER ALARM bug

[Geoff Quickfall]

This occurs on both the last operating system and the newest March 30th update. The following test was run with the March 30th updated operating system.

1). Comparison between 41CX / 41CL & DM41X

2). Flag 44 is the continuous on flag. It is set when the XEQ ON function is invoked. It is not set by the TIMER ALARM condition

Condition:

I have a routine running that among other things sets the stopwatch with a countdown timer (-ve value). When the timer reaches zero the TIMER ALARM message displays and the alarm beeps for a prescribed amount of time.

However, the DM41X remains on causing battery depletion. This has occurred twice. The display fades with the message TIMER ALARM. Then it becomes a brick until the battery is changed.

The reason I do not acknowledge the TIMER ALARM and select the calculator off is this usually occurs near landing or if we are early, in the flight bag which is not checked until the next day.

So the questions are:

1). does the TIMER ALARM cause a continuous on state? It does, but not by altering flag 44 to a set condition.

2). Is this a bug or normal HP 41 behaviour? Yes it is a bug and not normal for the 41CX or 41CL. When running the same routine on the 41CX and CL both turn off in 10 minutes.

You can test this by entering in X; -0.0020 and XEQ SETSW. This sets a 20 second countdown. Now XEQ RUNSW then turn off the calculator be it a 41CX, 41CL or DM41X. The calculators will all turn on in 20 seconds displaying TIMER ALARM and beeping. After 10 minutes the 41CX and 41CL turn off and the DM41X remains on until battery depletion.

Cheers, Geoff

Stay safe everyone.

Edited to include the March 30th operating update.

[rprosperi]

Geoff,

Thanks for the bug report and the detailed notes.

A new version of f/w for the 41X was released earlier today, that includes some bug fixes that affect StopWatch mode. Though these fixes were not aimed at this particular problem, it is possible the fix has corrected this problem as well, could you please check?

The SW problem addressed in this release was errant behavior where the SW would, at unpredictable times when running, suddenly add 30 hours to the time. This could even happen very shortly after the SW started so it feasibly was the cause, though I'd guess not.

If the problem is not corrected in the new release, let know and we'll take a look, it sure sounds like a bug that should be corrected.

Thanks!

[Geoff Quickfall]

Hi Bob!

Yes, tested it on the new operating system. Then I posted

Cheers, Geoff

[rprosperi]

Thanks for confirming Geoff, we're on it and will get back to you with confirmation, more questions if needed, etc.

Thanks!

[rprosperi]

Problem identified and fixed and will be in the next update.

Thanks for the detailed report and your help tracking it down Geoff!.

[Geoff Quickfall]

Glad it was tracked down and more then happy to help, that’s why we like beta testing here!

Also, looking forward to saving batteries