WP43 News

This area is for discussion about these families of custom high-end Scientific Calculator applications for SwissMicros devices.
redglyph
Posts: 177
Joined: Sat Dec 22, 2018 11:45 am

Re: 43S News

Post by redglyph »

I tried and after playing with it a little, sometimes it does nothing for me too when selecting PROG then G, but it's hard to reproduce. When I had this, pressing EXIT a few times to clear the menus seemed to fix it.

I can't seem to find the solution though, 'Out of range' is all I get when I press on F1 ('K'), with or without initial guess value(s). The expected result is −0.7781 and 1.1347 (for real roots).

I tried to enter the polynomial with EQN, NEW, 0 = X^6-X-1.
Then I select Solver.
Then I enter two values, for example -2 F1 2 F1.
Then I press Draw, I get an empty plot (the curve is not visible)

I accidentally pressed the up arrow key and got a "This is most likely a bug in the firmware [...]". I can reproduce it every time, maybe it's not a problem since we may not be supposed to press that key, but I'm reporting it in case it's interesting.
Clipboard01.png
Clipboard01.png (4.23 KiB) Viewed 1652 times
If I press on F1, I get the same 'Out of range' message.

Maybe I misunderstood the procedure, I'll check that again later.
User avatar
Jaymos
Posts: 1635
Joined: Sun Nov 04, 2018 7:03 pm
Location: Cape Town

Re: 43S News

Post by Jaymos »

Try using lower case x, or another variable name such as XX.
Do not use a register name.

Draw gives:
Screenshot 2022-08-14 at 22.36.38.png
Screenshot 2022-08-14 at 22.36.38.png (10.01 KiB) Viewed 1645 times
-2 F1 2 F1 F1 gives -0.778089598678601097880682309659297

-2 F1 2 F1 cpxSlv gives 1.134724138401519492605446054506473

These are two different algorithms and in this case the one goes the left root, and the other happens to give the right hand side root.

-0.85 F1 1.2 F1 Draw gives a better picture.
Screenshot 2022-08-14 at 22.36.38 copy.png
Screenshot 2022-08-14 at 22.36.38 copy.png (10.47 KiB) Viewed 1645 times
Jaco Mostert
Elec Eng, South Africa
https://47calc.com C47 (s/n 03818 & 06199), WP43 (0015). In box: HP42S, HP32Sii, WP34S&C, HP28C, HP35s, EL-506P, EL-W506, PB700; ex: FX702P, 11C, HP67 & HP85; iOS: 42s Byron, Free42+, WP31S/34S, HCalc.
User avatar
Jaymos
Posts: 1635
Joined: Sun Nov 04, 2018 7:03 pm
Location: Cape Town

Re: 43S News

Post by Jaymos »

redglyph wrote:
Sun Aug 14, 2022 10:10 pm

I accidentally pressed the up arrow key and got a "This is most likely a bug in the firmware [...]". I can reproduce it every time, maybe it's not a problem since we may not be supposed to press that key, but I'm reporting it in case it's interesting.

It is a bug.
A wrong or irrelevant key must not cause a crash.
I will look into that bug. Thank you for reporting.
Jaco Mostert
Elec Eng, South Africa
https://47calc.com C47 (s/n 03818 & 06199), WP43 (0015). In box: HP42S, HP32Sii, WP34S&C, HP28C, HP35s, EL-506P, EL-W506, PB700; ex: FX702P, 11C, HP67 & HP85; iOS: 42s Byron, Free42+, WP31S/34S, HCalc.
User avatar
Walter
Posts: 3070
Joined: Tue May 02, 2017 11:13 am
Location: On a mission close to DRS, Germany

Re: 43S News

Post by Walter »

Jaymos wrote:
Sun Aug 14, 2022 10:48 pm
redglyph wrote:
Sun Aug 14, 2022 10:10 pm
I accidentally pressed the up arrow key and got a "This is most likely a bug in the firmware [...]". I can reproduce it every time, maybe it's not a problem since we may not be supposed to press that key, but I'm reporting it in case it's interesting.
It is a bug.
A wrong or irrelevant key must not cause a crash.
I will look into that bug. Thank you for reporting.
I concur. Thanks, redglyph! Obviously I don't know our Solver by heart. :?
WP43 SN00000, 34S, and 31S for obvious reasons; HP-35, 45, ..., 35S, 15CE, DM16L S/N# 00093, DM42β SN:00041
User avatar
Jaymos
Posts: 1635
Joined: Sun Nov 04, 2018 7:03 pm
Location: Cape Town

Re: 43S News

Post by Jaymos »

Jaymos wrote:
Sun Aug 14, 2022 10:48 pm
redglyph wrote:
Sun Aug 14, 2022 10:10 pm

I accidentally pressed the up arrow key and got a "This is most likely a bug in the firmware [...]". I can reproduce it every time, maybe it's not a problem since we may not be supposed to press that key, but I'm reporting it in case it's interesting.
It is a bug.
A wrong or irrelevant key must not cause a crash.
I will look into that bug. Thank you for reporting.
Bug fixed and will be rolled out in the next release.
Jaco Mostert
Elec Eng, South Africa
https://47calc.com C47 (s/n 03818 & 06199), WP43 (0015). In box: HP42S, HP32Sii, WP34S&C, HP28C, HP35s, EL-506P, EL-W506, PB700; ex: FX702P, 11C, HP67 & HP85; iOS: 42s Byron, Free42+, WP31S/34S, HCalc.
User avatar
Jaymos
Posts: 1635
Joined: Sun Nov 04, 2018 7:03 pm
Location: Cape Town

Re: 43S News

Post by Jaymos »

Jaymos wrote:
Sun Aug 14, 2022 10:46 pm
Try using lower case x, or another variable name such as XX.
Do not use a register name.
Quoting p255 of the OM: "...You must not, however, reuse any name of such a constant for any of your variables – your WP 43S may misunderstand your intentions."

@Walter, maybe an additional note on p255 regarding the use of especially "X" and "x" in equations could be warranted.
Jaco Mostert
Elec Eng, South Africa
https://47calc.com C47 (s/n 03818 & 06199), WP43 (0015). In box: HP42S, HP32Sii, WP34S&C, HP28C, HP35s, EL-506P, EL-W506, PB700; ex: FX702P, 11C, HP67 & HP85; iOS: 42s Byron, Free42+, WP31S/34S, HCalc.
redglyph
Posts: 177
Joined: Sat Dec 22, 2018 11:45 am

Re: 43S News

Post by redglyph »

Jaymos wrote:
Sun Aug 14, 2022 10:46 pm
Try using lower case x, or another variable name such as XX.
Do not use a register name.
Thanks for the tip!

A few observations,

- When I edited the equation this time, the left & right arrows on F1/F6 were not working, the cursor was stuck at the end of the line and wouldn't move. I had to insert something first before I could use the arrows.
- The editor starts in uppercase; if we cannot use uppercase variables, wouldn't it be better to start in lowercase?
- 'X' is often used too, that's what users take by default on HP-48 and later models, so it's an easy mistake. Maybe a warning by the calculator?
- The uppercase/lowercase mode is reset each time the user edits the equation or enters alpha when editing a program. For the latter it's good since alpha is used for labels, strings and other purposes too. But isn't it better to remember the uppercase/lowercase mode when editing functions?
- I confirm it works for me with lowercase 'x' in interactive mode (EQN/Solver) and Draw shows the expected result.
- 'K' is used in other examples, for instance pp. 59. If it's reserved, maybe another variable should be used, or a warning be printed (maybe I missed it).
- After I edited the program to replace 'K' with lowercase 'w' and tried SOLVE/PROG/G, it went back to the P.FN menu instead of launching the solver (as reported by @BINUBALL above).
- I exited all the menus and tried again, this time it showed the variable in F1 as expected.
- I confirm it works for me in program mode with 'w' (ADV/SOLVE).

- I see pp. 57, "K is also the alpha register for some special operations (see pp. 242f)", so I see the usage with K pp. 243 but it seems to be related to alpha operations. Still 'K' is obviously an issue with SOLVE, it's unexpected. Once again I think you will get fewer fake bug reports if the calculator issues an error or a warning with those variables. Or if there was a warning in the manual I missed it, maybe because I jumped to the section about equations as someone would to brush up on a topic after a while.

By the way, I'm not familiar with that notation, what do the 'f's stand for after a page number? EDIT: found it, 'f' for following section, 'ff' for following sections. Perhaps worth mentioning? It's the first time I see it and it's not as if I were never reading manuals and books. ;)
Last edited by redglyph on Tue Aug 16, 2022 9:56 am, edited 1 time in total.
User avatar
Walter
Posts: 3070
Joined: Tue May 02, 2017 11:13 am
Location: On a mission close to DRS, Germany

Re: 43S News

Post by Walter »

Since some users fell in pits while naming user variables, I refined p. 59 of the Owner's Manual. It may read as follows now:
.
Variables.png
Variables.png (64.12 KiB) Viewed 1510 times
WP43 SN00000, 34S, and 31S for obvious reasons; HP-35, 45, ..., 35S, 15CE, DM16L S/N# 00093, DM42β SN:00041
User avatar
Jaymos
Posts: 1635
Joined: Sun Nov 04, 2018 7:03 pm
Location: Cape Town

Re: 43S News

Post by Jaymos »

Walter wrote:
Tue Aug 16, 2022 12:37 am
Since some users fell in pits while naming user variables, I refined p. 59 of the Owner's Manual. It may read as follows now:
.
Variables.png
Sufficient guidance imo.
Jaco Mostert
Elec Eng, South Africa
https://47calc.com C47 (s/n 03818 & 06199), WP43 (0015). In box: HP42S, HP32Sii, WP34S&C, HP28C, HP35s, EL-506P, EL-W506, PB700; ex: FX702P, 11C, HP67 & HP85; iOS: 42s Byron, Free42+, WP31S/34S, HCalc.
rprosperi
Posts: 1703
Joined: Mon Apr 24, 2017 7:48 pm
Location: New York

Re: 43S News

Post by rprosperi »

Walter wrote:
Tue Aug 16, 2022 12:37 am
Since some users fell in pits while naming user variables, I refined p. 59 of the Owner's Manual. It may read as follows now:
.
Variables.png
I think this is pretty clear in general, but could be made more so if items is also defined (which perhaps it is somewhere). While defining Variables, the explanation suddenly jumps to items, whose scope is not explained.

It is clear Variables are a subset of items, same for Registers, but what else is included in the domain of items? Of course one could go look at ReM, App. I and review the full list, but since the point of this note is to clarify, I suggest you also define the scope of items, or add a reference to where that is defined, if done so previously. This lets the reader know which other things to compare a proposed name to, in order to know it is acceptable.
--bob p

DM42: β00071 & 00282, DM41X: β00071 & 00656, DM10L: 071/100
Post Reply