Keith and I both hope to be able to attend "Thunda Down Under"[1] in
2015, and I've sent the organizers email requesting information on what
it takes to be treated as an on-site vendor.
Of course, it's always more fun to be at a launch when you have something
interesting to fly! Thus, while Keith and I might each show up with a
modest "travel rocket" of some sort... I've started pondering possible
larger "Altus Metrum" group projects. Since transporting a large
airframe to Australia would be a hassle, I wonder if a group project to
build an airframe in-country makes more sense? To that end, I'd be
pleased to know if any of our friends and customers in Australia want to
sign up to help with such a project?
My thoughts would be to engage in some group-think about project scope
and goals, then hope friends in-country would take on the sourcing and
preparation of suitable airframe materials. Depending on who wants to
participate and how tasks get taken up, we might plan to arrive a bit
early to help with any final assembly or other preparations,
installation of suitably fresh Altus Metrum electronics, etc.
So, to all our Aussie friends... does this sound like fun? If so,
please chime in with a reply. I don't expect the email associated with
such a project to be too heavy a load for this list to carry, but we can
always spawn a dedicated lists.gag.com list if I'm wrong.
Regards,
Bdale
[1] http://thunda.com.au/
I just received a TeleGPS unit and am starting to do some tests before
flying it. Most everything has worked great except I seem to be unable to
change the maximum log size. It shows as configured for 1984 kB (1 flight).
It records flights (simulated by putting in my pocket while going on a run
around the neighborhood. I can download the flight and mark it for
deletion. Once I've done this, further attempts to download are met with a
dialog "No flights available on serial_num".
At this point I still can't change the maximum log size. I'm using the
TeleGPS app 1.6.5 and I've updated firmware to telegps-v1.0-1.6.5.
-Tim
>From what I can tell from browsing the code repos, the current programming
scripts are dependent on a modified version of OpenOCD v0.6.0 that contains
Jared Boone's lpc11u config files.
Has anyone tried using the latest v0.9.0 of OpenOCD with default configs?
>From what I can tell it already contains the config files for lpc11u. I
haven't finished building my EasyMini's yet so I can't test and confirm
they work yet, perhaps someone else has tried or is willing to try it out?
It looks like -f target/lpc11u14.cfg can be replaced with -f
target/lpc11xx.cfg in the ao-flash-lpc script.
Xenial ships with v0.9.0, and it looks like Jessie ships with v0.8.0.
>From what I can tell the lpc11xx.cfg config file was introduced in v0.8.0.
http://repo.or.cz/openocd.git/commit/b5a6ba46aaed530a4b1397b9617de0ff316f6e…
Are there any plans to transition to a newer release of OpenOCD?
Can the 850 mAh battery support the following in a Telemega
- sit on the launch pad for up to 20 minutes
- fire a second stage engine
- fire the drogue charge
- fire the main charge
- continuously transmit for the entire flight
Thanks,
Tim
Altus Metrum releases AltOS 1.6.5
AltOS fixes:
* Fix hardware SPI driver on TeleMetrum v2.0, TeleMega v1.0 and
TeleMega v2.0 where devices were observed to stop logging data and
transmitting telemetry in flight. All TeleMega v1.0, v2.0 and
TeleMetrum v2.0 users should update their flight firmware.
AltosUI fixes:
* Deliver firmware for TeleMega v2.0 and TeleBT v3.0 with
Windows package.
Find more information on all Altus Metrum products at http://altusmetrum.org
