My minor 35s modifications

[Hugh Evans]

Considering there is probably time left to make a few changes before mass production, I figure it's worth a shot to put together a slight change in the keyboard layout to make the stack manipulation keys more accessible. In addition, I applied the colors that I selected for OpenRPN. They are the end result of my research on human optics and included sources such as NASA's guidelines for man-machine-interfaces.

If anyone from HP wants any information from me on these colors I will be more than happy to furnish them with everything they could want to know. I can also suggest a better typeset if desired.

Feedback from the community is welcome.

[Edit: Far left- My first set of modifications, Middle- My modifications plus suggested dark cursor keys, Right- Unedited HP image -HDE]

Edited: 31 May 2007, 4:00 p.m. after one or more responses were posted

[Egan Ford]

Get rid of kg/lb, mile/kg, etc...

Add Matrix ops, Floor, Ceiling, Mod, Round, String manipulation, P<>R. Restore STO.

[Hugh Evans]

My intention is to make modifications that are minor enough for HP to implement without too much effort prior to mass production.

Save the other ideas for the modification community.

[Jürgen (CH)]

For those using SI units (some of them use also this strange umlaut characters) these conversion functions are not very useful. I would put them into a menu and use the keys for other (more generally useful) stuff.
Personally, I also dislike the light grey of the cursor keys; the light color is too attracting and disturbs the otherwise very nice design.
Anyway, it's by far the most interesting calculator HP presented in the last few years. I definitely would buy one.

Cheers, Jürgen

[Jürgen (CH)]

Ignore my previous message, it went into the wrong thread. Sorry

[BruceH]

Quote:

---

My intention is to make modifications that are minor enough for HP to implement without too much effort prior to mass production.

---

How about changing the shift keys to have arrows that point up and down rather than left and right, as someone pointed out before?

[Walter B]

OK, let's try:

What is modified?

• there is an ALPHA key
  
• STO is unshifted
  
• we would have the opportunity to ASSIGN CATalog functions to keys
  
• IP and FP are visible
  
• a MATRIX menu is provided
  
• an I/O menu is provided
  
• LBL, RTN, ISG, and DSE are collected in a menu FLOW
  
• an unshifted -> is introduced to allow double use of mode keys also for conversions (e.g. blue-shift 6 sets hexadecimal mode, while -> blue-shift 6 converts to hex display); this makes the menu BASE obsolete
  
• the 4 basic logic operations are on the keyboard
  
• unit conversions are collected in a UNITS menu
  
• there is a MODulo operation on the keyboard
  
• nPr, nCr, x!, and SEED are collected in PROB
  
• x?y and x?0 are merged in TEST
  
• INPUT and PSE are collected in X.FCN, where more special operations may be hosted
  
• I cleaned the key plate; all yellow print there is for menus now (not so sure for ARG); the blue print on keys 1, 2, 3 is for menus, too – everything else are just functions
  
• etc.

You are invited to criticize 8)

Best regards, Walter

Edited to include the HP35s's published keyboard for direct comparison (thanks, Hugh). Edited to correct the picture address.

Edited: 10 June 2007, 1:43 a.m. after one or more responses were posted

[Wayne Brown]

Quote:

---

You are invited to criticize 8)

---

OK: It still has the awful cursor keys. :-)

[Walter B]

Wayne, you are perfectly right :-)

Please consider: if we change this, we will need at least a new punching tool for the key plate and a new PCB design. By keeping this feature we save this money for whatever good. Please decide where you want to spend the bucks - and remember you can do so only once d:-)

[DaveJ]

Quote:

---

OK: It still has the awful cursor keys. :-)

---

And the redundant backspace key!
There is already a left arrow key that can do the job just admirably.

Dave.

[Walter B]

Quote:

---

And the redundant backspace key! There is already a left arrow key that can do the job just admirably.

---

The cursor keys are for moving, the backspace is for clearing. Look at your keyboard, please, and think.

[Jeff O.]

Quote:

---

OK: It still has the awful cursor keys.

---

Wayne,

Would you buy the 35s if it had this arrangement for the cursor keys?:





Or would it take this one?:

Edited: 5 June 2007, 8:31 a.m.

[Gene]

Why cater to him at all? It still isn't shaped like a brick with edges sharp enough to peel an orange.

Partial :-) there, but not much of one.

[Jeff O.]

Gene,

I wasn't necessary trying to or suggesting that hp cater to Wayne. I decided to create the images with the revised keyboards just to see how they might look. Having done so, I figured I'd see if that might be enough to please Wayne, or if another deal-breaker would come up. It will be just fine with me if the 35s is produced with the cursor keys exactly the way they were presented originally.

[Donald]

looks superb - much better than HP's attempt.

The first is probably better - fewer accidental hits of the MODE key.

The 'i' complex key is moving rather far away from the other numeric keys - how about swapping the, redundant in RPN, '( )' with 'i' .
Even in algebraic the <> would be used in conjunction with ( ).

[John]

You shouldn't call the parentheses keys redundant. They are used heavily in the equation mode on the 33s.

And, if you don't make the calculator friendly to use in algebraic mode, sales will be hurt. Sure, none of us may use the 33s in algebraic mode, but you can't make algebraic extra difficult or sales won't be good.

[Jeff O.]

Quote:

---

The first is probably better - fewer accidental hits of the MODE key.

The 'i' complex key is moving rather far away from the other numeric keys - how about....

---

Thanks for the compliment on the looks. I mostly did it just to see what it might look like. I restrained myself from trying to optimize the keyboard.

[Wayne Brown]

I'd prefer the second arrangement, but the first would be OK too. In fact, I wouldn't mind an arrangement like < > v ^ as I use the h j k l keys on my computer keyboards all the time in exactly that way for cursor movement. The main point is to avoid anything reminiscent of keys on a cell phone, game, TV remote, or other non-technical "consumer" device.

[John]

Where did that picture come from? Much more detailed that any previous picture.

[Hugh Evans]

It came from HP's PDF. My guess is that it looks better to your eyes now that the labels have much better contrast... Which is exactly the point I'm trying to get across to HP.

Edited: 31 May 2007, 2:56 p.m.

[John]

No, that wasn't my point at all. The green gets lost next to the blue, so the color looks worse.

The resolution looked higher than I have extracted from the PDF, so I wondered where you got it. Looking at the original PDF now and it is clearly different.

[Hugh Evans]

Well, the PDF is my source. I updated my original post for a side-by-side comparison.

The red alpha labels are nearly impossible to see, and the green color I selected has a good degree of difference from the nearby blue (90° difference in lab coordinates). The only other logical alternative would be to make the alpha labels white.

-Hugh

Edited: 31 May 2007, 3:34 p.m.

[John]

The red are perfectly visible.

How about you start a new thread asking for a vote?

Red vs. Green?

[Hugh Evans]

Maybe to your eyes. The red color HP has chosen has a much lower luminance score, 20-30 points lower than my green. That just means *much* better contrast. As far as I can tell HP did not put any thought into their color selection aside from approximating colors from the voyager series (which weren't perfect either).

Red is a lousy color to work with against a dark background anyways. I'm sticking with green, you're welcome to your opinion... But my solution is correct.

[Dennis Trafananko]

Another color possibility for the Alpha labels is a magenta shade (diametrically opposed to the green), with a brightness (value in HSV) to be visible against the dark background. The green appears to clash with the other colors in the pictures, it just looks out of place.

[Hugh Evans]

Yeah, I spec'd a color like but would prefer not to use it. Here's a copy of the optimal color palette I defined. HP was very close to perfect on early pioneer models such as the 48sx, they clearly did their homework. The green and purple colors I defined are what the should have used on the later 48g.

[Bram]

Quote:

---

Red is a lousy color to work with ...

---

I agree with this.

That's why my HP-28S is practically useless to me. Too difficult to read. Even on not so dark background.

[Steve Borowsky]

Wow, that's much improved. Good job.

[GE]

Green looks much better than red IMHO. I hope it makes it to the production model, but it is very probably too late.

[Bob]

I would love to see some basic TVM/financial functions since so much of engineering, project management, and science require some level of financial justification or evaluation on top of the technical work.

The financial solver on the 48GX, or similar, would work fine. I don't even care if it is buried in a menu somewhere.

[Chuck]

One equation in the solver can calculate all the needed TVM's, including annuities, loan paymens, future values, present values, etc. I have a version on most of my programmable calcs that don't have a built in TVM solver. But a built in TVM shouldn't be that hard to include.

[Chuck]

My eyes don't spot an "ALPHA" key. I wonder how one would store a value into a lettered register (unless it automatically switches mode, a feature I don't like.)

[Hugh Evans]

I'm confused about that exact problem myself.

[John]

If this is like the HP33s, then you press STO and the key a letter is on.

Hugh, have you even owned an HP32s, HP32sII, or an HP33s? That's the series of machines since 1988.

That's how HP has done this in that time period.

Your yellow on the images is different, so your not comparing apples to apples. If the yellow contrast/color is different, then you can't know what reality would be.

[Hugh Evans]

I know my colors are different. They are also better tuned to the human eye. I'm not comparing apples to apples, I'm comparing my solution to HP's. Sure, my renderings are not under photographic conditions but tweaking the color scheme for natural light isn't much of a challenge.

[Norris]

On the 33S, pressing STO, RCL, or LBL automatically toggles alpha mode. This mode only lasts for a single keystroke, because the variables and labels on the 33S are restricted to a single letter.

If you are entering equations, such as "A = B + C", then you have to hit STO or RCL before entering each letter. When you enter equations, the STO and RCL commands don't do anything except toggle the alpha mode. You can store brief text strings as dummy "equations", but you have to press STO or RCL before every letter; there is no "alpha lock" mode.

I believe the 32S and 32SII are similar, and the 35S probably is too. It sounds like the 35S may recognize two-letter variables and labels, but even in this case, there might not be a need for a dedicated alpha key.

[John]

Of course, this is hardly fair, given the green you used wasn't actually photographed under real lighting.

[Patrice]

Hi all,

The pictures on top are showing miswritings.

The problem is with metric units writing, they don't follow the rules.

kilogram is Kg, kg is wrong !
kilometer is Km, KM is wrong !
centimeter is cm, which is right !

As I already said, I don't like spending so much place on keyboard for conversion functions that I will almost never use, and not having others like FP, IP and modulus.

If they let them on keyboard, they sould at least write them right.

Patrice from France

[Maximilian Hohmann]

Hello!

Quote:

---

kilogram is Kg, kg is wrong !
kilometer is Km, KM is wrong !
centimeter is cm, which is right !

---

Not quite: In the international system of units (SI) (*), lowercase "k" stands for kilo or thousands and uppercase "K" for Kelvin.

So "kg" is indeed the correct way to abbreviate kilograms, but kilometers are neither "Km" nor "KM", but "km" instead.


And like you, I also think that these conversions are quite useless on a general-purpose scientific calculator. I would rather like user-defineable conversions (labelled maybe as "C1" ... "C5") that can be used for whatever the individual user needs to convert (from currencies to nanoAngstroems)


Greetings, Max



(*) see here: http://www.bipm.org/en/si/

[cfh]

It is spelled Ångström :-)
No umlauts, no pluralis s...

cheers
cfh

[Walter B]

Reminds me of my all time favourite unit: Potatoes per Ångström ...

[Dominic Richens]

Quote:

---

Reminds me of my all time favourite unit: Potatoes per Ångström ...

---

Isn't that a constant?

My favourite unit is furlongs per fortnight (0.000166309524 m/s according to Google)

[Walter B]

Quote:

---

> Reminds me of my all time favourite unit: Potatoes per Ångström ...

Isn't that a constant?

---

No, it's a unit for an area. A standard potatoe represents a volume of 187.0815 cm³ = 187.0815*10^-6 m³, an Ångström equals 10^-10 m, so a P/Å equals 187.0815*10^4 m² = 1.870815*10^6 m² = 1.870815 km². Enjoy! d;-)

[Dave Shaffer (Arizona)]

This reminds me of my favorite (?) unit: inverse acres

Useful for the mileage that you get with your car: miles/gallon, which is length/length^3, or 1/length^2 which has the same dimensionality as inverse acres. (Determining the actual conversion factor is "left to the student" and his/her favorite HP calculator.)