For those nay familiar with t' MaxTrax, it is a new starter kit from Estes with an onboard "Electronic Altimeter". This uses a capsule which drops at a fixed descent rate. Begad! Ya scallywag! Blimey! T' capsule physically senses ejection (apogee), ya bilge rat, ya bilge rat, me bucko, times t' interval until it detects landing, matey, then outputs calculated altitude in feet and meters. Avast, me proud beauty! Blimey! Promising...

I had a chance t' fly t' MaxTrax yesterday (Sat.), me bucko, which be a disappointin' experience. Tonight, matey, I did some analysis o' t' data, shiver me timbers, me hearties, which was equalin' disappointing. Avast, me proud beauty! Blimey! Ahoy! Blimey! For those nay interested in readin' further, matey, t' short form is that this is a toy that doesn't work (at least me sample didn't), arrr, arrr, and, even if it did work, it wouldn't be very accurate.

First, a couple o' bits o' foreshadowing. Ya scallywag! T' Estes instructions read: "NOT INTENDED FOR PRECISE MEASUREMENT". Avast, me proud beauty! Begad! Take them at their word.

Also, t' MaxTrax includes a snippet o' paper t' inform you: "IMPORTANT NOTICE! "Occasionally, shiver me timbers, t' MaxTrax Electronic Capsule will nay display t' altitude after a launch. Blimey! If this happens, thar be an internal electronic error durin' t' launch or descent. Begad! T' capsule is NOT DEFECTIVE! Switch t' capsule "OFF" and prepare another launch followin' t' directions. Begad! "If after t' second launch, t' capsule still does nay display t' altitude, thar be still an internal electronic error that can be fixed by t' factory. Begad! RETURN just t' CAPSULE t' Estes for resettin' or new replacement. Avast! Well, blow me down! DO NOT RETURN t' place o' purchase."

As I mentioned in a previous post, I had some trouble gettin' readings from me unit in ground testin' -- at times under four seconds and around eight seconds. For that reason, I also hand-timed t' descent o' t' MaxTrax capsule (ejection t' landing) in me test flights, me hearties, so I could extrapolate t' value it would have returned if it chose t' nay give an altitude reading.

I made nine flights with a scratchbuilt model (18" BT-56 tube). Blimey! T' weather conditions were hot but calm at Mt. Begad! ASTRE. Ya scallywag! wRASP gave approximate altitudes o' 220' (for Bs) and 560' (for Cs) for a Cd o' 0.6. Here's data from t' flights:

Several things were noticed from t' start. Begad! Well, blow me down! T' B flights were nay givin' any data, me bucko, me hearties, but I wondered if that might be related t' t' "no data around eight seconds" glitch previously noted. That's why I went t' t' C motors early (I had intended three B6 flights and three C6 flights [and maybe C11 flights] for NARTREK Gold data). Perhaps I should have dropped it into t' nearest mailbox at that point.

Another thin' noted was that t' capsule had a tendency t' tumble on descent. Aye aye! It has a factory-installed drogue streamer that you are explicitly told nay t' alter. Ahoy! However, me hearties, shiver me timbers, it seems like it isn't long enough / draggy enough t' stabilize t' capsule in a vertical descent. Ahoy! My hunch is that t' shock sensor that detects landin' requires a decceleration along t' vertical axis -- if it lands at an angle, it may fail t' trigger t' capsule, resultin' in no data.

Things got more interestin' when I moved up t' C power. Blimey! T' unit gave readings (usually), but they were wacky. Begad! T' highest value given may have been "close" t' (within 33% of) t' achieved altitude, me bucko, but t' other three readings were *way* off (>= 75% error). Blimey! T' capsule was still tumblin' on descent, so I can only hypothesize t' t' low altitude readings were t' result o' it experiencin' sufficient decceleration from t' tumblin' t' prematurely trigger t' landin' sensor.

On a bright note, me hardware worked fine. Avast! Ya scallywag! T' model made nine stable and successful flights with no damage aside from normal wear and tear (singed but still quite usable shock cord and mylar streamer).

While t' raw data be discouraging, me hearties, I had some hope that t' capsule descent times that I had recorded would salvage t' effort. I could use those times and t' values observed in ground testin' t' come up with an altitude figure that t' capsule would have reported if it had fallen that length o' time. Tonight, shiver me timbers, arrr, I did that calculation, ya bilge rat, ya bilge rat, and t' other shoe dropped. Avast! Blimey! Avast, arrr, me proud beauty! Blimey! Here's t' data:

Those altitudes are too high (from 13% for t' B flights t' 36% - 44% for t' C flights). Begad! Avast, me proud beauty! Blimey! Even worse, me bucko, t' backtracked Cds are way too low (from 72% for t' B t' 75% - 83% for t' Cs). Well, blow me down! My estimates may nay be perfect, but t' Estes data is just plain wrong.

I plan t' contact Estes about repair/replacement and any further info they can give on t' unit, but I don't expect it t' change me opinion o' its usability. Avast, me proud beauty! If you are lookin' for an altimeter you have two choices: spend t' loot on a real barometric unit or go t' cheap route with a hand-timed drop-streamer (you'll have t' calibrate such a streamer yourself in drop testin' from a known height and calculate altitude from descent times, but your efforts will yield a cheap, reliable, shiver me timbers, ya bilge rat, replaceable method o' altitude determination).

by Jeff Vincent - Rocket Cynic™