Can someone please tell me the penalty for owning non ISO 80000-2 compliant calculators?
I have several and I want to do the right thing. Can I get amnesty if I voluntarily turn them in?
I had no idea... please go easy on me... I have a family to support!
WP43 News
Re: 43S News
You can give them to me. I won't press any charges.
I believe in free will. Just can't help it.
Re: 43S News
Final.
I did love H2X's reference to Asterus and Obelus!
11. Changed U-> to CONV (HP42S Style)
12. Changed L-> to DRG
For years I knew of the WP34S project, but only made one this year after I found the WP34C branch solves the complex number entry reversal. Now I have a WP34C on my work desk, home desk, in my laptop bag and even an extra WP34S floating around. The point of my story is that user participation (i.e. the compile time options, my overlays and the WP34C branch) opened up the WP34S project for me. I expect that the WP43S project would reach more people once there are more user contributions to allow more to get what they want. My attempt proves that this is feasible. For clarity, I do not at all imply that the development team should either consider these options or bear this responsibility; this should be user energy, not a burden to development.
Your comments:
1, 2, 4 & 9: I realise it may be archaic, but your pressures make the calculator "right" in terms of new (ISO) standards and I respect that, and my pressures make it useful for me by trying to keep to familiar bits. As TwoWeims implied today, its no crime not to fully comply with the ISO. The world at large is also only partially complying bit by bit in certain areas
5: Yes, I know: CPX and an underlined CPX, sufficiently differentiated in colours, causing no confusion.
10: I did move the shifted labels with the key front (operator) labels and it does seem to make sense. The more labels I shift though, the more maintenance it is for me in your future source updates.
Walter, I don't expect you to spend time on my unsupported layout, but were there traps that you saw in my layout causing you to mention (10) above?
It figures as I'm no native English speaker ... I could have referred to the "division slash" or the "division sign", or as in Walter's comment, type the actual letter / or ÷.toml_12953 wrote: ↑Mon Jun 17, 2019 12:13 pm
P.S. Who the hell actually uses the word "obelus" when they talk about a division symbol?
No native English speakers I've ever heard!
I did love H2X's reference to Asterus and Obelus!
I forgot 2 points:Walter wrote: ↑Mon Jun 17, 2019 9:24 amThanks for your kind words. Some comments:Jaymos wrote: ↑Mon Jun 17, 2019 2:05 amI fiddled further and the total changes I made up to now are listed and visible on the side by side emulator pics below:
1. Changed "/" with obelus. (HP42S style).
2. Increased the font size of the 4 operators on the emulator.
3. Removed the top key "ˆ" labels. (DM42 style).
4. Change lg to log. (HP42S style).
5. Changed CC to CPX. (WP34S style).
6. Changed +/- to CHS. (HP28C style).
7. Changed P/R to PRGM. (HP42S style).
8. Swapped operators left/right, keeping the sequence. (HP42S style).
9. Changed to eRPN. (HP28C style).
10. Shifted the alpha letters and greek letters around due to the left right swap.
For now I decided not to change all the second row keys to match the DM42 hardware keys.
1. / (or maybe even : ). Cf. ISO 80000-2: "The symbol ÷ should not be used."
2. Cosmetics.
3. We could call "^" HP27S style FWIW.
4. True, but pursuing an error: LOG is the general logarithm, lg is the decadic. Cf. ISO 80000-2: "log x shall not be used in place of ln x, lg x ..."
5. Did you notice there's another CPX present already?
6. +/- (Pioneer style).
7. P/R (Voyager style).
8. See many earlier posts.
9. We stick to HP's traditional RPN.
10. You should shift some shifted labels as well.
Layouting is more fun than you might expect.
11. Changed U-> to CONV (HP42S Style)
12. Changed L-> to DRG
For years I knew of the WP34S project, but only made one this year after I found the WP34C branch solves the complex number entry reversal. Now I have a WP34C on my work desk, home desk, in my laptop bag and even an extra WP34S floating around. The point of my story is that user participation (i.e. the compile time options, my overlays and the WP34C branch) opened up the WP34S project for me. I expect that the WP43S project would reach more people once there are more user contributions to allow more to get what they want. My attempt proves that this is feasible. For clarity, I do not at all imply that the development team should either consider these options or bear this responsibility; this should be user energy, not a burden to development.
Your comments:
1, 2, 4 & 9: I realise it may be archaic, but your pressures make the calculator "right" in terms of new (ISO) standards and I respect that, and my pressures make it useful for me by trying to keep to familiar bits. As TwoWeims implied today, its no crime not to fully comply with the ISO. The world at large is also only partially complying bit by bit in certain areas
5: Yes, I know: CPX and an underlined CPX, sufficiently differentiated in colours, causing no confusion.
10: I did move the shifted labels with the key front (operator) labels and it does seem to make sense. The more labels I shift though, the more maintenance it is for me in your future source updates.
Walter, I don't expect you to spend time on my unsupported layout, but were there traps that you saw in my layout causing you to mention (10) above?
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.
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.
Re: 43S News
Hi Jaco,
Do you really need stickers on the keys themselves?
On the DM42 (and hence the WP43S), can't the device be physically opened up and keys moved around to match whatever your proposed branch provides in its firmware? Obviously, you still need a sticker to re-label shifted functionality, but that's not so bad if the keys themselves could be sticker-free.
I guess your renaming of "/" → " ÷ " and other such niceties would be missing, but at least it would let one put the operand keys in one's preferred column and order. That is the bigger deal for me...
Re: 43S News
Burkhard,
There's so much information in this thread. The challenge seems to be reading and remembering:
There's so much information in this thread. The challenge seems to be reading and remembering:
Walter wrote: ↑Wed May 29, 2019 4:36 pmFor sake of preventing creation of legends, please note: As with the Pioneers, all buttons of the DM42 are one sprue; and all are printed at once. I guess this processing will not change significantly for the 43S. So while changing shifted labels will be easy, modifying individual physical keys will be difficult.
WP43 SN00000, 34S, and 31S for obvious reasons; HP-35, 45, ..., 35S, 15CE, DM16L S/N# 00093, DM42β SN:00041
Re: 43S News
I haven’t opened my DM42 yet but many on this forum confirmed it is one plastic piece with all the buttons and not possible to change them out. A quick google renders this vid, at 2:50 there is a good view of the connected buttons.
https://youtu.be/ZDxVxw6_SKU
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.
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.
Re: 43S News
Hi Walter & Jaco,
Thanks both for the nice (and speedy!) replies.
Yes, once I saw it in print (and confirmed in the video), that did seem familiar again.
Sigh...This "memory getting old stuff" is for the birds.
Oh well, I should have known the clever guys here would have thought of that already.
Stickers it is then—they have proven OK for me on the 34S.
This single thread on the 43S is getting pretty long...
Thanks both for the nice (and speedy!) replies.
Yes, once I saw it in print (and confirmed in the video), that did seem familiar again.
Sigh...This "memory getting old stuff" is for the birds.
Oh well, I should have known the clever guys here would have thought of that already.
Stickers it is then—they have proven OK for me on the 34S.
This single thread on the 43S is getting pretty long...
Re: 43S News
... but it's still easier to read and scan than multiple threads, isn't it?
WP43 SN00000, 34S, and 31S for obvious reasons; HP-35, 45, ..., 35S, 15CE, DM16L S/N# 00093, DM42β SN:00041
Re: 43S News
Jaco,
You pursue your personal JM43S, we pursue a public WP43S. Different targets.
Though it's perfectly legal to branch an open source project. Since you publish your mods, I just took the freedom to comment from my point of view. You don't have to follow - nor will we follow your modifications. The following just documents different opinions, maybe triggering some thoughts. That's all a discussion is good for, isn't it?
Now to the individual points:
1.-4.: All said.
5.: I just think names shall be unique. YMMV
6.-9.: All said.
10.: IIRC, there was a post of Gene in this thread covering grouping of shifted labels. I can't find it right now (i.e. I'm too lazy for reading the full thread again). Please search, read, and decide.
11., 12.: Up to you.
You pursue your personal JM43S, we pursue a public WP43S. Different targets.
Though it's perfectly legal to branch an open source project. Since you publish your mods, I just took the freedom to comment from my point of view. You don't have to follow - nor will we follow your modifications. The following just documents different opinions, maybe triggering some thoughts. That's all a discussion is good for, isn't it?
Don't be afraid if a standard tells something should be done. But think deeply if it tells something shall be done. Since you are creating your very own JM43S, however, you're free as a bird and responsible yourself for the consequences as well.Jaymos wrote: ↑Mon Jun 17, 2019 10:42 pmI forgot 2 points:Walter wrote: ↑Mon Jun 17, 2019 9:24 am1. / (or maybe even : ). Cf. ISO 80000-2: "The symbol ÷ should not be used."Jaymos wrote: ↑Mon Jun 17, 2019 2:05 am1. Changed "/" with obelus. (HP42S style).
2. Increased the font size of the 4 operators on the emulator.
3. Removed the top key "ˆ" labels. (DM42 style).
4. Change lg to log. (HP42S style).
5. Changed CC to CPX. (WP34S style).
6. Changed +/- to CHS. (HP28C style).
7. Changed P/R to PRGM. (HP42S style).
8. Swapped operators left/right, keeping the sequence. (HP42S style).
9. Changed to eRPN. (HP28C style).
10. Shifted the alpha letters and greek letters around due to the left right swap.
2. Cosmetics.
3. We could call "^" HP27S style FWIW.
4. True, but pursuing an error: LOG is the general logarithm, lg is the decadic. Cf. ISO 80000-2: "log x shall not be used in place of ln x, lg x ..."
5. Did you notice there's another CPX present already?
6. +/- (Pioneer style).
7. P/R (Voyager style).
8. See many earlier posts.
9. We stick to HP's traditional RPN.
10. You should shift some shifted labels as well.
11. Changed U-> to CONV (HP42S Style)
12. Changed L-> to DRG
...
Your comments:
1, 2, 4 & 9: I realise it may be archaic, but your pressures make the calculator "right" in terms of new (ISO) standards and I respect that, and my pressures make it useful for me by trying to keep to familiar bits. As TwoWeims implied today, its no crime not to fully comply with the ISO. The world at large is also only partially complying bit by bit in certain areas
5: Yes, I know: CPX and an underlined CPX, sufficiently differentiated in colours, causing no confusion.
10: I did move the shifted labels with the key front (operator) labels and it does seem to make sense. The more labels I shift though, the more maintenance it is for me in your future source updates.
Walter, I don't expect you to spend time on my unsupported layout, but were there traps that you saw in my layout causing you to mention (10) above?
Now to the individual points:
1.-4.: All said.
5.: I just think names shall be unique. YMMV
6.-9.: All said.
10.: IIRC, there was a post of Gene in this thread covering grouping of shifted labels. I can't find it right now (i.e. I'm too lazy for reading the full thread again). Please search, read, and decide.
11., 12.: Up to you.
WP43 SN00000, 34S, and 31S for obvious reasons; HP-35, 45, ..., 35S, 15CE, DM16L S/N# 00093, DM42β SN:00041
Re: 43S News
Error in administration: CPX sign and CPX UNITV are actually identical (see the ReM). And |x| is on the keyboard already, so having (angle) and UNITV unshifted and |x| shifted in CPX makes some sense. Sorry for the confusion.
WP43 SN00000, 34S, and 31S for obvious reasons; HP-35, 45, ..., 35S, 15CE, DM16L S/N# 00093, DM42β SN:00041