Altus Metrum announces AltOS 1.8.6
Announcing AltOS 1.8.6
AltOS 1.8.6 contains ground station software bug fixes for configuring
flight computers and firmware bug fixes for controlling TeleMega and
EasyMega additional pyro channels. People with multi-staged projects
using EasyMega or TeleMega, or using Antenna Down configuration should
update to this version immediately.
AltOS Fixes
* Use maximum of 64 previous tilt values in pyro tilt tests. This
ensures that an unstable airframe will correctly inhibit pyro
charges even if it happens to be pointing up when the pyro test is
performed.
* Eliminate 100m height requirement for coast detection. This ensures
that multi-stage rockets with short burning boosters will sequence
to coast phase as soon as the motor burns out instead of waiting to
reach 100m.
* Change After Motor pyro check to be >= instead of ==. For flights
with more than two stages, this makes motor tests succeed even if
additional motors have been burned.
* Change Time since boost to be Time since launch. This changes the
interpretation of the Time values configured for additional pyro
channels and the Apogee Timeout values configured for the apogee
igniter channel to use total flight time instead of time since the
last motor started burning. If you're using Time Since Boost or
Apogee Timeout on a multi-staged project, you'll want to change
your configuration.
Ground Station Fixes
* Clarify pyro test phrasing. The UI now tries to describe what the
various pyro channel tests do a bit better
* Remove ascending/descending from pyro config UI. These are
redundant with the flight state values and serve only to confuse
people.
* Fix accel calibration in Antenna Down mode. If you are running a
flight computer in Antenna Down mode, you'll want to re-calibrate
your accelerometer using 1.8.6 ground software, even if you don't
update the flight firmware.
* Fix radio parameter saving at 2400 bps telemetry rate. If you had
set your TeleMini to 2400 bps you wouldn't have been able to reset
it to 38400 baud. This fixes that.
MicroPeak Fixes
* Report altimeter-recorded maximum height value. The MicroPeak
application was re-computing this value on the ground using a
simple peak detector instead of using the carefully filtered value
computed in flight. This now reports the in-flight value in the UI.
_______________________________________________
altusmetrum mailing list
[email protected]
http://lists.gag.com/mailman/listinfo/altusmetrum
