Page 1 of 4

UPDATE: DMCP-3.11 / DM42-3.11

Posted: Thu Oct 11, 2018 12:43 pm
by grsbanks
Image

This latest update to both the DMCP and DM42/Free42 parts of the DM42's firmware brings the following improvements:
  • DMCP-3.11
    • Clock switching bug when connecting to USB
  • DM42-3.11
    • Revert to Intel® Decimal Floating Point Library V2.0 Update 1
    • Fix for Alpha input/display when first character is '÷'
Clock switching bug

There's a bug in the STM firmware that makes the clock switch when the calculator is plugged into a USB port unreliable. A fix has been put in place to improve reliability.

Intel® Decimal Floating Point Library

In version 3.10 we updated from V2.0 Update 1 to V2.0 Update 2 of this library. However, one of the changes in the library is to the bid128_pow() function that is invoked by Free42's 'Y^X' command. In some instances, Y^X would make the DM42 hang. The hanging problems do not occur with the previous version of the Floating Point library so pending investigation of the root cause of the problem, we've reverted to Version 2.0 Update 1.

'÷' as first character in alpha register

A bug in the handling of the alpha register would cause input to be impossible if the first character typed was the '÷' division symbol or if the register was cleared using the backspace key. Fixed.



The method for updating your DM42 is covered in the manual.

The latest firmware binaries are available here.

SHA1 checksums:
  • a4f7e9be32475e96f2d2e0a353c0c5bd8e3a4e34 DM42-3.11.pgm
  • 53cd2ff2a6829718c1f67bb4d7b4c9d944b1f99a DMCP_flash_3.11.bin
  • 0020b7fd2c591be386528eb9e997f8b017714c1c DMCP_flash_3.11_DM42-3.11.bin

Re: UPDATE: DMCP-3.11 / DM42-3.11

Posted: Thu Oct 11, 2018 1:44 pm
by StreakyCobra
The update went flawlessly. I can confirm the bugs with y^x and ÷ are fixed. I can not relate about the battery consumption though as I didn't had the problem.

Re: UPDATE: DMCP-3.11 / DM42-3.11

Posted: Thu Oct 11, 2018 2:12 pm
by akaTB
StreakyCobra wrote:
Thu Oct 11, 2018 1:44 pm
The update went flawlessly. I can confirm the bugs with y^x and ÷ are fixed. I can not relate about the battery consumption though as I didn't had the problem.
I will take care of that, once at home.
I won't hold my breath though since I don't see anything about power drain issues.

Re: UPDATE: DMCP-3.11 / DM42-3.11

Posted: Thu Oct 11, 2018 7:26 pm
by mcc
Dear SwissMicros,

unfortunately you support your customers way too fast.
I am beginning to loose the bug reports and only get aware
of the fixes...damn!
How on earth one should keep in pace with you?

:)
^^^very big smiley...

Thank you very much D&M for this ober-fast fix! Great!
I cannot confirm the reported two bugs any longer, hehehehe! :)

Cheers!
Meino

...may I ask for a fix for this issue:
viewtopic.php?f=19&t=446&p=5302&hilit=m ... 0431#p5302

Re: UPDATE: DMCP-3.11 / DM42-3.11

Posted: Thu Oct 11, 2018 8:38 pm
by akaTB
akaTB wrote:
Thu Oct 11, 2018 2:12 pm
StreakyCobra wrote:
Thu Oct 11, 2018 1:44 pm
The update went flawlessly. I can confirm the bugs with y^x and ÷ are fixed. I can not relate about the battery consumption though as I didn't had the problem.
I will take care of that, once at home.
I won't hold my breath though since I don't see anything about power drain issues.
As anticipated nothing changed about power drain. From 2.92V to 2.83V in a matter of minutes.
Slowly recovering (now 2.85V) after downgrading to 3.8 + 3.9.1

Re: UPDATE: DMCP-3.11 / DM42-3.11

Posted: Thu Oct 11, 2018 8:53 pm
by budmur
akaTB wrote:
Thu Oct 11, 2018 8:38 pm
akaTB wrote:
Thu Oct 11, 2018 2:12 pm
StreakyCobra wrote:
Thu Oct 11, 2018 1:44 pm
The update went flawlessly. I can confirm the bugs with y^x and ÷ are fixed. I can not relate about the battery consumption though as I didn't had the problem.
I will take care of that, once at home.
I won't hold my breath though since I don't see anything about power drain issues.
As anticipated nothing changed about power drain. From 2.92V to 2.83V in a matter of minutes.
Slowly recovering (now 2.85V) after downgrading to 3.8 + 3.9.1
Bummer - i haven't installed the update for that reason. Please let us know if you hear from Michael on a resolution.

Re: UPDATE: DMCP-3.11 / DM42-3.11

Posted: Thu Oct 11, 2018 11:32 pm
by rprosperi
I just installed DM42 V3.11 on DMCP v3.10 via load-program-from-flash, on production unit 00282.

No hiccups or problems to report.

I usually leave the Voltage display set to OFF, but I enabled it due to the bug that seems to affect some units using DMCP 3.10. My voltage was initially at 2.97V, and then after using the DM42 for a few minutes, it dropped to 2.95V, but then after letting sit a while (interrupted by phone call) and turning it back on, voltage was back up to 2.97V, so it appears the battery drain issue is NOT affecting my machine. Just another data point.

Re: UPDATE: DMCP-3.11 / DM42-3.11

Posted: Thu Oct 11, 2018 11:41 pm
by DA74254
akaTB wrote:
Thu Oct 11, 2018 8:38 pm
akaTB wrote:
Thu Oct 11, 2018 2:12 pm
StreakyCobra wrote:
Thu Oct 11, 2018 1:44 pm
The update went flawlessly. I can confirm the bugs with y^x and ÷ are fixed. I can not relate about the battery consumption though as I didn't had the problem.
I will take care of that, once at home.
I won't hold my breath though since I don't see anything about power drain issues.
As anticipated nothing changed about power drain. From 2.92V to 2.83V in a matter of minutes.
Slowly recovering (now 2.85V) after downgrading to 3.8 + 3.9.1
Is it draining and stays low?
I noticed on mine that the voltage dropped from 2,92 to 2,88 during the Bench test at 10.000. It then recovered to 2,90. Now, after a few hours "off" when switching on, it says 2,92 again.

Re: UPDATE: DMCP-3.11 / DM42-3.11

Posted: Fri Oct 12, 2018 4:03 am
by Walter
Did anyone ever determine the precision of the voltage measurement? Just crossed my mind...

Re: UPDATE: DMCP-3.11 / DM42-3.11

Posted: Fri Oct 12, 2018 7:05 am
by groenewe
Well. If I take out the battery and measure it on various DMMs then it's within approx 0.05v correct. and of course the battery recuperates a little bit when you leave it unconnected. I need to start measuring the current when switched off I guess. Mine is going rapidly down again (3rd battery soon to come).