About a year ago I decided to develop a new altimeter, with the very deliberate mission of answering the "how high did it go?" question in as easy-to-use a way as possible. In a lot of ways, the AltimeterOne is not an altimeter for me (an engineer) or perhaps some of you, but for my kids and their friends. Their joyous moments aren't spent in front of a computer studying pressure and acceleration curves, but rather in those moments right before launch when we banter about "how high this one's going," and then the laughter and chase of recovery.
We needed one altimeter that would work for all of our rockets, not need a lot of care and feeding, and "just work." That was the impetus for what you see today, the AltimeterOne.
I'll try to address a couple of points that you've collectively raised in this thread. I'll also post my email (or you can comment on my site) so that you can ask me more if you feel like it.
Issue #1: Rides in the fuselage. Really? C'mon. Really??
Yep. We've been field testing this thing for months. If you try hard, you can mess it up. But you have to *really* try hard. It's rugged, and as for over-pressure, it can handle 10x atmospheric. (In general, when your electronics can handle more than most fuselages, you're in good shape.)
Issue #2: I still can't get over that it rides with the chute. What about false readings?
Probably 80% of what we worked on in flight testing could be roughly termed as "filtering," though it has less to do with Nyquist limits and Kalman filters than it does with handling sporadic events. It takes a lot of work to discover all of the little corner cases, combinations of conditions, and odd "once every ten launches" type events that can make software look stupid when they crop up. The list is long: breezes, popping open the rocket to take a peek right before launch, mach shock sweeping across a vent hole, delays between loading and launch (thus the 60 minutes), etc. Every time something like this cropped up, we figured out a way to filter it. You do need to be aware that you need to let it breathe to get a reading (whether in a payload or a fuselage). I'm a big fan of "more venting is better," and I think in practice it's hard to over-vent, a symptom of which might be difficulty with proper ejection. Hmmm. There's a joke there somewhere...
It wasn't discussed much yet, but the fact that you can use this in a rocket, plane, or kite is pretty cool, and somewhat unique.
Issue #3: How good is this thing? Is it just all show?
Don't let the "pretty face" fool you. This thing has some really advanced components, and is wicked accurate. I have a photo I still keep of the first four prototypes, along with a competing altimeter, as viewed through the window of my pressure chamber in its maiden run. All four altimeters read 14,390 feet. All four. The same. In a world where most common pressure sensors and analog to digital conversions occur with AT BEST 1.5-2.5% accuracy (including noise), this is a pretty cool result.
Issue #4: Why does it cost $49.95? I was hoping for $30...
Well, mostly see Issue #3. This is not "the cheapest way to make an altimeter." Instead, it is the cheapest way that I know to make it right. For me, that's tiny, rugged, accurate, and simple. "Easy" may be different for all of us, but for me, it also includes never having to buy and keep a spare set of odd $5 batteries on hand. And--though I realize that this is highly subjective--I think the flash and beep counting is kind of kludgey.
All of that having been said, it is reasonable to expect that the altimeter will come down in price over time, though I hope you agree that this is a pretty good value already.
Issue #5: I wish it had data logging and staging outputs.
I hear you, I'm like that, too. But that's not who this was for. There are some fine units out there that do those things now, as you know.
Feel free to ping me. I love to hear suggestions, comments.
Have fun,
--John
John Beans
President, Jolly Logic
[email protected]
www.jollylogic.com