DM 15L two line display

[AnnoyedOne]

(Yesterday 03:57 PM)dm319 Wrote:  Got to admit, coveting it a lot.

Ok, but I think it is already "branded".

Equivalent to "putting a ring on it"

A1

PS: Swissmicros may sell a few more DM15L's in the near future. A shame that their shipping is so slow (based on recent reports). Perhaps not their fault.

[Ross Barnes]

A user Helix reported that he was unable to stop a running program after loading firmware V33 on his DM15L. I had just installed the firmware before I saw the message. I loaded a short program with an infinite loop, started it, and I was only able to stop it using the Reset pinhole on the back. Could someone else confirm this behavior? Thank you.

See message link below:
Update V33

[rprosperi]

(Yesterday 02:39 PM)ctrclckws Wrote:  

(12-21-2024 03:46 PM)Jase Wrote:  Man, that would be cool if the mini-me gets a 2-line option.

It does work on the older credit card size DM15 and DM16

Very sorry, please let me clarify my earlier clarification.

Some of the very earliest DM15 devices cannot have the V33 DM15 f/w installed (IIRC, these had limited ROM size), but this does not affect all earlier DM15 cc-sized models, in fact most of them will work.

Sorry for the poorly worded comments earlier.

[rprosperi]

(Yesterday 08:53 PM)Ross Barnes Wrote:  A user Helix reported that he was unable to stop a running program after loading firmware V33 on his DM15L. I had just installed the firmware before I saw the message. I loaded a short program with an infinite loop, started it, and I was only able to stop it using the Reset pinhole on the back. Could someone else confirm this behavior? Thank you.

See message link below:
Update V33

Please list the program which you are unable to stop, I can't reproduce this problem with another simple looping program, program execution stops properly when I press [R/S] while running, without loss of control.

[Ross Barnes]

It was a simple one:
P/R
LBL A
1
+
GTO A
P/R
GSB A

I tried R/S and every other key and various combos of keys.
Gave up and Reset.
I then ran the program again thinking I might have been in some strange mode
Same result. Reset.

I've already flashed back to V32 since I use the calculator daily.
I am pretty certain that I was running my DM15L with V33 at the slower clock rate because V33 defaulted to the higher clock rate on flashing and I wanted it at the slower clock rate that V32 set by default.

I used the DM15_M1B_xx.hex images.

[Johnp_g]

(Yesterday 10:37 PM)Ross Barnes Wrote:  It was a simple one:
P/R
LBL A
1
+
GTO A
P/R
GSB A

I tried R/S and every other key and various combos of keys.

I used the same infinite loop program and I find it DOES stop with pressing R/S and also by pressing any other key (within limits, I haven't tried them ALL, but any I press halts the running program and shows the current count in X.

I tried with DM15_33.hex and DM15_M1B_33.hex and tried at 12MHz and 48MHz. All work normally, and can be stopped and started with R/S, and stopped with any other keypress.


Cheers,

John

[rprosperi]

It works fine for me too, in both 12 and 48MHz.

@Ross Barnes - please try replacing your battery and trying again. If no change, please try reflashing (with the same version V33 M1B f/w, being sure to download from the website right-clicking the filename and using "Save Link as..." to save the file.

Thanks!

[Ross Barnes]

I went back to SwissMicros web site and download the flash file again. I diffed it again the file use before. No differences.
I reflashed V33 M1B file. I did NOT change the battery.
After reflashing I returned the display to a single line, dropped the clock rate to 12 MHz and I reentered the program. I ran the test program and I had NO problem stopping the program. I went through a few of the gyrations I did the first time I flashed V33, changing options, etc.. I reran the program again and had NO problem stopping the program.

I then flashed my two other DM15L calculators with V33, set them up identically, ran the program and had NO problem stopping the program.

I don't know why the original V33 flash wouldn't stop a running program. The first time around I had to Reset the calculator each time before rerunning the infinite loop program using the keyboard so there must have been a problem with my original flashing of V33.

Thank you for your assistance as well as the software update.

[rprosperi]

Thanks for rechecking, reflashing and retesting to check this issue. Glad to know it's now working properly (in all 3 of your DM15L machines!) and I appreciate your confirming all this so promptly.

Now you can enjoy checking out the new features!

Thanks and Merry Christmas!

[J-F Garnier]

(Yesterday 10:37 PM)Ross Barnes Wrote:  It was a simple one:
P/R
LBL A
1
+
GTO A
P/R
GSB A

I tried R/S and every other key and various combos of keys.
Gave up and Reset.
I then ran the program again thinking I might have been in some strange mode
Same result. Reset.

I CONFIRM that there is a problem there.
I can't reproduce it when running the program with GSB A or R/S, but I reproduce the problem in USER mode and pressing [A]: the program can't be stopped by any keystroke including ON. Reset and memory clear mandatory.
Also, using SOLVE A or INTEG A on this same program leads to the same unstoppable situation.

Tested with DM15_M1B_33 at 12 or 48 MHz.
My batteries may be a bit weak (I didn't change them recently) but I don't believe this is important here.

J-F

[mfleming]

(Today 08:32 AM)J-F Garnier Wrote:  Tested with DM15_M1B_33 at 12 or 48 MHz.
My batteries may be a bit weak (I didn't change them recently) but I don't believe this is important here.

J-F

Try replacing the battery and testing again. Prior to preparing my 41L for update I did my usual battery check "12 ENTER 34 +" and noticed a missed keystroke. An infinite loop would cause a steady current draw and subsequent voltage drop that could affect operation. A weak battery accounted for keystroke problems on the 15C CE.

PS. 41L also unused for a number of months before deciding to update.

[John Casper]

Is it possible to hide the keycodes in programming and show only their names

[AnnoyedOne]

(Yesterday 03:57 PM)dm319 Wrote:  And to add...

Yeah, there are many differences between the HP-15C CE and DM15L (including the ones you mentioned).

IMHO they're minor in practice. I think that the two I posted (previously) are the significant ones.

I have a HP-15C CE. You have (access to) a DM15L. To quote the Black Knight ("Monty Python and the Holy Grail")

Quote:We'll call it a draw then?

A1

[AnnoyedOne]

(Today 01:14 PM)John Casper Wrote:  Is it possible to hide the keycodes in programming and show only their names

Why would you want to? Per dm319's video above (which shows programming in action) the codes and mnemonics are displayed on different lines.

A1

PS: If you really don't want to see the keycodes a small strip of paper/etc may "hide" them

[J-F Garnier]

(Today 12:41 PM)mfleming Wrote:  

(Today 08:32 AM)J-F Garnier Wrote:  Tested with DM15_M1B_33 at 12 or 48 MHz.
My batteries may be a bit weak (I didn't change them recently) but I don't believe this is important here.

Try replacing the battery and testing again.

I definitively confirm that it's not a problem with batteries.
Using the same set of batteries, it happens in DM15_M1B_33 but doesn't in DM15_M1B_32.

Another use case that produces an unstoppable situation requiring a full hardware reset:
Using the same LBL A test program as above, run it indirectly with the sequence, from the keyboard:
20 , STO I , GSB I
The program can't be stopped.

J-F