BAT indicator stuck on

[cdmackay]

thanks very much Bob. Excited that mine is unique

I'd already emailed Michael on Thursday… will await reply.

[cdmackay]

update, for those following along at home…

I've just updated to:

DMCP v3.18t02 (IFC 03.13)
DM41X v1.11t01

and was quite surprised to find that my BAT indicator is no longer stuck on. It was on before I performed the firmware update, but is not on now, including after a reset.

However, I tried the selftest-diags again, and it is still reading:

Vdd:1221,cal:1666

the same as it did before, when the BAT indicator was on.

Has there been some fix in the firmware to ignore values of Vdd as low as 1221?

Or has some other change "broken" the BAT indicator, so that it now doesn't come on?

[I've reported the above to Michael]

[rprosperi]

The new version has no intended change in this area, so that's curious indeed. Of course something odd could have happened by mistake, however since it appears that unit is not working 100% right anyhow, it's probably safer to conclude the problem, whatever it is, simply manifests differently with the new DMCP version that is part of the new build.

The BAT indicator you are referring to is the 41C BAT annunciator on the bottom line, and not the battery strength indicator on the top header line, right?

[cdmackay]

The new version has no intended change in this area, so that's curious indeed. Of course something odd could have happened by mistake, however since it appears that unit is not working 100% right anyhow, it's probably safer to conclude the problem, whatever it is, simply manifests differently with the new DMCP version that is part of the new build.

The BAT indicator you are referring to is the 41C BAT annunciator on the bottom line, and not the battery strength indicator on the top header line, right?

Yes, that's right. The 41C annunc. disappeared, but the "compressed battery" icon in the top right, stayed, which is odd.

However, after a couple of hours of use, BAT has come back on!

So perhaps it was just a coincidence that it went off for a few hours immediately on updating the firmware. It's been otherwise on constantly since I received the calc, and I've updated the firmware before.

Ah well.

Michael will be sending me a new PCB, which is great.

thanks again, sorry for the time wasted.

[rprosperi]

No need to apologize, all issues should be reported, its the only way to find the real bugs...

Keep reporting please, and thanks for clarifying.

[Geoff Quickfall]

Very interesting thread.

Could it possibly have been a corruption of the previous OS. Would you have time to reload the older OS that you just replaced and see if the BAT fault returns?

Or reload a new download of the older OS and reinstall it.

Geoff

[akaTB]

Very interesting thread.

Could it possibly have been a corruption of the previous OS. Would you have time to reload the older OS that you just replaced and see if the BAT fault returns?

Or reload a new download of the older OS and reinstall it.

Geoff

Well, this is not needed, I think...

However, after a couple of hours of use, BAT has come back on!

[Geoff Quickfall]

Yes, I missed the “after a few hours sentence”.

RTWP. (Read the whole posting).

[cdmackay]

I get caught by that all the time, too

[cdmackay]

update: Michael kindly sent me a new board, and that's cured the issue (of course).

thanks for all the suggestions/help.


@mods: perhaps move this thread to "hardware"?