On Tue, 19 Apr 2011 20:57:12 +1000, Blake Nikolic <blake(a)nikoplus.com> wrote:
> On another note, how can I tell the difference between these 200G
> units that have just arrived and standard units?
That's a great question! CC'ing our mailing list with my answer so
it'll be archived. And given that, I'll throw in a few other thoughts
about the accelerometers on our boards while I'm typing.
The only visible difference would be the markings on the Freescale
accelerometer part itself, which is U3:
MMA2201 is 40G
MMA2202 is 50G (default)
MMA2204 is 100G
MMA2301 is 200G
The way the firmware works is that we do a cal to determine the ADC
output at +1 and -1 G, so it's "self calibrating" to the different
ranges and offsets due to actual resistor values in the divider, etc.
Thus the firmware doesn't actually know or care what part is loaded, it
just knows what numbers correspond to +/- 1G.
You can view these cal values by connecting to the board over USB or RF
and typing 'c s'. That display includes the current accelerometer cal
as stored in the config block of the on-board flash memory.
Note that a 200G accel has 1/4 the resolution of a 50G accel, because we
have the same number of ADC bits covering 4 times the range. Any errors
in the +/- 1G cal are also amplified 4 times more with a 200G part than
they are with a 50G part for the same reason. The fact that we log raw
ADC samples and the cal values means that you can always play around in
a spreadsheet to post-process the data if you really need to.
Those cal values become part of the flight data recorded in the on board
flash, and are part of the data sent to the ground over radio. So the
ground software also doesn't know what part is loaded, it just knows how
to take the raw ADC output numbers that are logged and convert them into
G numbers using the cal values received alongside the raw data.
The other way to know which accel range a board covers is that I keep a
"production log" that has notes about things like which boards got
custom accelerometer choices, so in the worst case, I can always tell
you what a given serial number shipped with.
I launched my TeleMetrum (s/n 324) for the first time yesterday, and I think
my flight data is incomplete.
My setup was very simple - just the Telemetrum in a payloader w/E engine to
test things out.
I've attached the telem and eeprom data, perhaps some kind soul could take a
look and see if they agree that the data seems to just stop mid-flight?
Also, I wanted to confirm that multiple flights can live happily in the
eeprom and that you don't have to download them/delete in between flights?