“I’m Not Dead Yet!” Reverse Polish Notation Calculators You Can Still Buy

If you used a scientific calculator in the 1970s or 1980s, there was a fair chance that it worked differently from almost every calculator you see today. Instead of typing:

2 + 3 =

you entered:

2 ENTER 3 +

There wasn’t even an equals key. Hewlett-Packard made this system — Reverse Polish Notation, or RPN — practically synonymous with serious scientific calculators until other players like TI and Casio got serious. Once you got used to it, ordinary algebraic calculators could feel annoyingly clumsy.

Today, RPN calculators look like a nearly extinct species. HP left the calculator market, licensing the HP calculator line to Moravia Consulting. Old HP-15Cs, 16Cs, 32Ss, 42Ss, and 48s have become collectibles. But RPN isn’t dead. You can still buy new hardware, build your own, or turn almost any computer or phone into a very capable RPN machine. There are reasons some of us still want to.

But Why Polish?

The name goes back to Polish logician [Jan Łukasiewicz], who devised a notation in which operators precede their operands. Instead of writing:

A + B

you can write:

+ A B

The big advantage is that parentheses aren’t required. The structure of the expression tells you exactly what operates on what. Reverse Polish notation simply puts the operator at the other end:

A B +

[Łukasiewicz] wasn’t designing calculators, of course, but the same idea turned out to be extremely convenient for computers and calculators. Your software doesn’t have to remember what operation is in progress. Each operator is ready to go and can simply work on the operands that you’ve already read.

RPN isn’t exactly the way people calculate with pencil and paper, and it certainly wasn’t derived from the slide rule, but there is a similarity in the way you work. With a slide rule, you generally establish some value, operate on it, and continue from the result. When doing a long-hand calculation, you often calculate a subexpression, write down the answer, and use that answer in the next step. You will probably start with the inner parenthesis and work outward, just like someone with an RPN calculator does. RPN formalizes that process with a stack.

Suppose you want:

(3 + 4) × (5 + 6)

On a conventional calculator, you either need parentheses, or you have to calculate one result and remember it. On an RPN calculator:

3 ENTER

4 +

5 ENTER

6 +

×

The first + leaves 7 on the stack. The second leaves 11 above it. The multiply consumes both and leaves 77.

Notice what’s missing: parentheses, an equals key, and any need to tell the calculator about precedence. This isn’t much of a win for a five-key calculation. It becomes more apparent with something like computing the value of a bunch of parallel resistors:

R=1/(1/R1+1/R2+1/R3…)

An RPN user can calculate each reciprocal, add it to the running result on the stack, and finally take the reciprocal. Intermediate answers stay in the calculator naturally instead of being stuffed into memory registers or enclosed in increasingly impressive collections of parentheses.

Is RPN better? Calculator users have been arguing about that for half a century. But once RPN gets wired into your fingers, it can be surprisingly hard to give up.

Continue reading ““I’m Not Dead Yet!” Reverse Polish Notation Calculators You Can Still Buy”

Calculator UI Is More Complex Than You Might Think

Calculators are so ubiquitous and so familiar that they are easy to take for granted in many different ways. [lcamtuf] points out one that has probably never occurred to many of us: the user interface for a calculator is an unexpectedly complex thing.

The internal logic to support sequential inputs and multiple operators in a way that feels intuitive is a complex thing.

Resolving something like 1 + 2 = is pretty straightforward but complexity compounds rapidly after that, with numerous special cases. Let’s imagine one decides to program a simple calculator UI as a weekend project. The development process might look a little like this:

  1. User types in 1 + 2 = and the calculator displays 3. What happens if the user immediately presses -?
  2. No problem, just consider the result of the previous operation as an already-there input. So we’ll have 3 - for this next operation, and wait for more.
  3. Unless we should have treated that - as a negative sign for whatever number is coming next, making it a negative number? No, ignore that. Just treat whatever results from pressing equals as a pre-typed input.
  4. Unless the user hits a number. Because if they hit 2 (for example) then we’ll have a 32 and not a 2 which they probably, definitely don’t expect. So that’s a special case and we should insert a clear if that happens.
  5. Oh, better clear if the user enters a decimal, too.
  6. I’m going to need a coffee…

And that’s just the tip of the iceberg. Imagine trying to figure all this out for the very first time, without the benefits of habit and history to fall back on.

The fact is that supporting the apparently trivial behavior of a simple calculator requires an underlying complex state machine that deals with all kinds of special cases in order to make the UI feel intuitive. And that’s just for a basic four-function calculator; we haven’t even touched on how special keys like % should behave.

We know [lcamtuf] speaks from experience, not just because of their deep knowledge of calculator history but because they rolled their own calculator that uses voltmeters as digit displays and there’s nothing like actually implementing something to make one appreciate it.

Voltmeter-Based Floating Point Calculator Does It In Style

[lcamtuf] is not just a calculator superfan, but also a skilled builder. That much is evident in the fabulous  design of Calcumator 2000, an electromechanical calculator that uses voltmeter readouts as digits (plus one at the bottom to represent decimal place). There are plenty of high-quality build images, so give it a look!

Meters like the one on the right (numbered 0 to 9) act as digit displays. The meter on the left indicates decimal position.

Calcumator 2000 is a bit of a love letter to a time when display technology hadn’t quite yet produced anything suitable for calculator use. This resulted in calculator designs that are generally unrecognizable compared to the 7-segment display based devices we see today. The Calcumator 2000, in all its electromechanical glory, would have fit right in that era.

The Calcumator 2000 has all the usual buttons one would expect from a simple calculator and drives a total of seven readouts, one of which acts as the decimal point. The idea of using voltmeters as digit displays came from [lcamtuf]’s voltmeter clock, an earlier work with a similar attention to detail in its design and assembly.

We want to take a moment to admire how clean the blue panel is. [lcamtuf] made it by painting one side of an acrylic panel, cutting the letters and design out on a CNC mill, then filling with white paint. The depth of the cuts gives the white elements a nifty multi-layer effect that really complements the design.

Want to see it work? Oh yes, you do. Check out the video, embedded just below.

Continue reading “Voltmeter-Based Floating Point Calculator Does It In Style”

Ask Hackaday: Do We Need A 21st Century Calculator?

The HP-41C analog on my phone gives the right answer.

Three resistors in parallel: 4.7 k,Ω 22 kΩ, and 3.3 kΩ. Quick! What’s the equivalent value? You can estimate it, of course, but if you want the actual 1.8 kΩ (approximately) answer, you probably reached for some kind of calculating aid. I have two slide rules on my desk, and plenty more a few steps away, but I don’t use them much, honestly. I have a very old HP-41C — arguably the best calculator ever made — but I am usually afraid to use it as it is almost 50 years old and difficult to repair. I also have an HP-28S on my desk, a replica HP-41C, and a few others in desk drawers. There are also dozens of calculators on my desktop computer, my phone –including the official HP Prime app — and the web browser.

I often see newer calculators from HP, like the Prime G2, or “new” HP-like calculators like the ones from SwissMicros, and think I should pick one up. Well, technically, HP licensed their calculators to Moravia, so even a “real” HP calculator isn’t from HP anymore. But, in the end, I always realize that my need for a physical calculator is so diminished that I can’t justify buying anything new, and I can barely even spring for a $10 one at the thrift store unless it is a real collectible.

Mind you, I’m not talking about RPN versus algebraic. I could say the same thing for TI, Casio, or Sharp calculators. I just don’t know why I need one anymore, even though I still, for some strange reason, want them.

The Prime seems impressive, if I could ever find time to finish reading the manual.

For the record, I did use an HP-41C to check the resistor math, but it was in the form of an app on my phone, not a real calculator. On the same computer I’m writing this on, I have HP-41C emulators, the Prime emulator, and a bunch of other calculators. Yet I still pick up my phone and use the familiar key layout of the HP-41C. I don’t know why. The replica 41C, unfortunately, has a landscape-oriented keyboard, so while I like it, it doesn’t satisfy my finger’s muscle memory.

Which leads to this Ask Hackaday. Do you use a calculator? Why? If you don’t, do you use a fake calculator on your phone or computer? Or do you just send your math to Google or Wolfram? I suspect some of the answer will be generational. I was in high school before calculators started showing up in schools, but they took over quickly.

There is something satisfying about having a purpose-built device to do your math. No long boot sequence. No switching apps. No messages coming in while you are typing in numbers. For the ultimate convenience, you could wear it on your wrist. The Apollo mission that docked with a Russian spacecraft carried an HP-65, and nine early Space Shuttle missions used an HP-41C. But even astronauts now don’t have a standard-issue calculator. Pilots sometimes use electronic E6Bs, but many still use the mechanical version.

Of course, I do collect slide rules, so maybe I just need to accept that calculators are yet another tech relic to collect. But someone is still buying them. I’d like to be one of them.

Continue reading “Ask Hackaday: Do We Need A 21st Century Calculator?”

Build The CPU, Then Build The Calculator

It’s possible that among Hackaday readers are the largest community of people who have designed their own CPU in the world. We have featured many here, but it’s possible that not so many of them have gone on to power an everyday project. Step forward [Baltazar Studios] then, with a scientific calculator sporting a self-designed CPU on an FPGA.

The calculator itself is nice enough, with a smart 3D printed case, an OLED display which almost evokes a VFD, and very well made buttons. But it’s the CPU which is of most interest, because while it follows a conventional Harvard architecture with a 12-bit instruction set, it works with 4-bit nibbles. This choice follows one used by HP in their calculator designs, seemingly because it can be optimised for the binary coded decimal which the calculator uses.

With calculators being yet another app on our spartphones or comnputers, there seems to be less use of calculators outside of education in 2026. But if you are a calculator user there’s nothing like a calculator you made yourself, and with a CPU of your own design it has few equals. We like this project almost as much as we like the Flapulator!

A 3D-printed, split-flap display-having calculator with a Raspberry Pi Pico inside.

By Our Calculations, You’ll Love The Flapulator

Oh sure, you’ve got calculators. There’s that phone program of course, and the one that comes with your OS, and the TI-86 and possibly RPN numbers you’ve had since high school.

But what you don’t have is a Flapulator, at least not until you build one. Possibly the be-all, end-all of physical calculating devices, the Flapulator does its calculating live on a split-flap display. It’s kind of slow and the accuracy is questionable, but the tactility is oh, so good.

This baby boasts a 6-digit display, where the decimal point and negative sign each require one digit. Inside is a Raspberry Pi Pico, which can calculate for around 4 hours on a full charge. But the coolest part (aside from the split-flap display, naturally) has got to be the 24-key, hand-wired mechanical keyboard. There’s also a couple of LEDs that light up to keep track of the current mathematical operation.

The story behind this one is kind of interesting. [Applepie1928] found out that one of their favorite mathematician-comedian-pi-lovers who is known for signing calculators was coming to town. With four weeks to whip something up, this was, amazingly, the result. Check it out in  action after the break.

Need something that’s a whole other kind of fancy? Here’s an open-source graphing calculator.

Continue reading “By Our Calculations, You’ll Love The Flapulator”

Build This Open-Source Graphics Calculator

Graphics calculators are one of those strange technological cul-de-sacs. They rely on outdated technology and should not be nearly as expensive as they are, but market effects somehow keep prices well over $100 to this day. Given that fact, you might like to check out an open-source solution instead.

NumOS comes to us from [El-EnderJ]. It’s a scientific and graphic calculator system built to run on the ESP32-S3 with an ILI9341 screen. It’s intended to rival calculators like the Casio fx-991EX ClassWiz and the TI-84 Plus CE in terms of functionality. To that end, it has a full computer algebra system and a custom math engine to do all the heavy lifting a graphic calculator is expected to do, like symbolic differentiation and integration. It also has a Natural V.P.A.M-like display—if you’re unfamiliar with Casio’s terminology, it basically means things like fractions and integrals are rendered as you’d write them on paper rather than in uglier simplified symbology.

If you’ve ever wanted a graphics calculator that you could really tinker with down to the nuts and bolts, this is probably a great place to start. With that said, don’t expect your local school or university to let you take this thing into an exam hall. They’re pretty strict on that kind of thing these days.

We’ve seen some neat hacks on graphics calculators before, like this TI-83 running CircuitPython. If you’re doing your own magic with these mathematical machines, don’t hesitate to notify the tips line.