I do high altitude mountain climbing and will be ascending to 5895
meters (19,340 ft) in December. I'd love to log this climb, but the
homepage states that the maximum altitude is 4500 meters. I looked up
the sensor and its rated to 9000 meters. Is this a software issue or
does it actually work to the higher altitude?
From http://code.google.com/p/backwoods-logger/
"Altitude (calculated from air pressure) measurements in 2 ft steps,
from -1384 ft to 14999 ft (-300 to 4500 meters)"
From http://www.bosch-sensortec.com/content/language1/downloads/BST-BMP085-DS000-05.pdf
"Pressure range: 300...1100hPa (+9000m ... -500m above sea level)"
Many thanks!
Derek
Good question. That's a software issue-- 14999 feet was chosen because it covers all the mountains in the continental United States. There's a total of 4 bytes (32 bits) for each sample, which are allocated 13 bits to altitude, 11 to pressure, 8 to temperature. You could double the altitude range with a small code change, but you'd have to decrease the resolution (4 ft steps instead of 2 ft steps), or steal a resolution bit from the temperature or pressure scales.
Does that make sense?
Steve
I'll take a look at the code tonight and see if it can be altered to
work for me. Altitude is a derived quantity from temperature and
pressure right? So if the limiting factor is storing the data it could
be recalculated on demand and use the free'd space to store greater
resolution data on the other two fields. For now though I think
decreasing the resolution is a reasonable fast fix for my problem.
Derek
One possible hurdle is that the formula for calculating altitude from pressure and temperature is fairly complex, and involves the exp() function. It's not a big deal when you're only doing it once a minute when a sample is taken, but if it had to be calculated on the fly 128 times in order to draw a graph, it might be noticeably slow and make the user interface chug. Or it might be fine.
I'd say it's definitely worth investigating further.
Steve
Steve
If we are seriously discussing reworking that section of the code is it
possible to have options to either get maximum precision of the devices
(which I could actually use with the work I want to play with) and a
full range option? Derek's original problem really only uses 1/2 of the
device range, while someone else might want to put the logger in an
areal UAV and fly it 25,00+ ft. Do I hear 100,000 ft weather baloon
launches anyone???
EBo --