On Thu, 28 Jul 2011 19:10:09 -0700, DK Duncan <[email protected]> wrote:

> I made two changes to 0.9.4.3.  I bumped AO_MAX_VERSION to 9 in ao.h to
> allow the inclusion of an additional identifier to the version string
> and made this change to ao_sample.c:

I wouldn't do that -- it will change the telemetry frames so that the
ao_telemetry_configuration frame isn't the same size as the other ones,
so the ground station will not be able to receive it. 8 bytes should be
plenty for 0.9.4.3; I had made that 0.9.4.99 and that was one byte too
long.

You'll have to reflash your teledongle to receive the new telemetry
frames (which have been standardized at 32 bytes each), and update the
altosui bits to parse the new data of course. I've flown this new stuff
a couple of times and it seems to work great, but it is all quite new.

If you want to add a configuration variable to support upside down
mounting of the telemetrum, that would be even more awesome as you could
then fly the same firmware with just a different configuration setting.


>       ao_sample_accel = 0x7fff - ao_adc->accel;
> 
> According to the comments if I understand them correctly, the ADC is
> programmed to 11 bits resolution and the results are shifted to the MSB
> of the word.  The range is 0 - 32767.  Upon recalibration I get values
> as follows:

Good analysis; I think you're exactly right.

> > c s
> Config version: 1.4
> Main deploy: 200 meters (656 feet)
> Apogee delay: 1 seconds
> Radio channel: 1 (434.650MHz)
> Callsign: "k7dkd"
> Accel cal +1g: 8452 -1g: 8719
> Radio cal: 1186652
> Max flight log: 192 kB
> 
> > v
> manufacturer     altusmetrum.org
> product          TeleMetrum-v1.1
> serial-number    331
> software-version 0.9.4.3i
> 
> It enters pad mode correctly.

And your analysis appears to also yield positive results. You should be
able to test this further by swinging the TM around in Pad mode, antenna
down, and it should detect a launch.

Oh. 0.9.4.3i -- as above, if you just made this configurable we could
stick it into the stock firmware and then you'd just set each unit as
appropriate.

Feel free to change the version number to something else if you like
too, that way you can keep track of which version you've flown.


> Does all this seem sane to you?

Nicely done! This seems like a useful enough addition to stick in the
stock firmware in our next release; let me know if you want to try to
add the configuration stuff on your own, or if you want help with that.

-keith

Attachment: pgpN5SSQibTcf.pgp
Description: PGP signature

_______________________________________________
altusmetrum mailing list
[email protected]
http://lists.gag.com/mailman/listinfo/altusmetrum

Reply via email to