Re: [altusmetrum] AltOS 1.3.1 released

[Keith Packard]

David Abmayr dwabmay...@gmail.com writes:

 Keith,

 When I try to connect the TeleMega to my computer via the USB, AltOS sees
 the Telemega on COM 10, but when I try to configure altimeter I get an
 error (The system cannot find the path specified (3)). I am running AltOS
 1.3.1 and Windows 7 Home Premium, and I have no trouble communicating with
 my TeleMetrum. Any idea what's wrong?

Ok, I took my TeleMega board and reflashed it with a preliminary version
of 1.3.2 (a trivial bug-fix past 1.3.1) using my HP machine running
a corporatized Windows 7 (so, not HP's Windows 7 version, but something
that Intel built themselves). During reflashing, it had to install
device drivers for the boot loader, and that confused things enough that
I had to flash it again and carefully select the correct .ihx file. I
may see if I can't make this a bit cleaner, but the end result was that
TeleMega got reflashed and seems to work fine for me at least. I know,
that's small consolation for you, but I was slightly worried that the
Windows USB support could have been broken somehow.

As usual, if you have another machine to test with, that could eliminate
various system configuration issues, but I'm confident that TeleMega can
talk to Windows 7 and that what we've got is a system configuration
issue and not a software problem.

Is your TeleMega running version 1.3.1?

-keith


pgpoK3uhyHb9f.pgp
Description: PGP signature
___
altusmetrum mailing list
altusmetrum@lists.gag.com
http://lists.gag.com/mailman/listinfo/altusmetrum

Re: [altusmetrum] AltOS 1.3.1 released

[David Abmayr]

Keith,

When I try to connect the TeleMega to my computer via the USB, AltOS sees
the Telemega on COM 10, but when I try to configure altimeter I get an
error (The system cannot find the path specified (3)). I am running AltOS
1.3.1 and Windows 7 Home Premium, and I have no trouble communicating with
my TeleMetrum. Any idea what's wrong?

Regards,
David Abmayr


On Wed, Jan 22, 2014 at 10:43 PM, Keith Packard kei...@keithp.com wrote:


 Version 1.3.1 is a minor release. It improves support for TeleMega,
 TeleMetrum v2.0, TeleMini v2.0 and EasyMini.

 http://altusmetrum.org/AltOS/releases/1.3.1.html

 AltOS Firmware Changes

  * Improve sensor boot code. If sensors fail to self-test, the device
will still boot up and check for pad/idle modes. If in idle mode, the
device will warn the user with a distinct beep, if in Pad mode, the
unit will operate as best it can. Also, the Z-axis accelerometer now
uses the factory calibration values instead of re-calibrating on the
pad each time. This avoids accidental boost detect when moving the
device around while in Pad mode.

  * Fix antenna-down mode accelerometer configuration. Antenna down mode
wasn't working because the accelerometer calibration values were
getting re-computed incorrectly in inverted mode.

  * Improved APRS mode. Now uses compressed position format for smaller
data size, improved precision and to include altitude data as well as
latitude and longitude. Also added battery and pyro voltage reports
in the APRS comment field so you can confirm that the unit is ready
for launch.

 AltosUI changes

  * Display additional TeleMega sensor values in real units. Make all of
these values available for plotting. Display TeleMega orientation
value in the Ascent and Table tabs.

  * Support additional TeleMega pyro channels in the Fire Igniter
dialog. This lets you do remote testing of all of the channels,
rather than just Apogee and Main.

  * Limit data rate when downloading satellite images from Google to make
sure we stay within their limits so that all of the map tiles
download successfully.

 --
 keith.pack...@intel.com

 ___
 altusmetrum mailing list
 altusmetrum@lists.gag.com
 http://lists.gag.com/mailman/listinfo/altusmetrum


___
altusmetrum mailing list
altusmetrum@lists.gag.com
http://lists.gag.com/mailman/listinfo/altusmetrum