diff options
| author | Keith Packard <keithp@keithp.com> | 2018-08-05 11:09:34 +0800 |
|---|---|---|
| committer | Keith Packard <keithp@keithp.com> | 2018-08-05 11:13:42 +0800 |
| commit | 0d57c78dde3c6e61576a4769b0e0fae7e88c107d (patch) | |
| tree | 55b15b996575fe8c934ebfb16426c8e95425e2cf /doc/config-device.inc | |
| parent | 9dfbf0103a649816e98d5511b1d6bbbfc93f6632 (diff) | |
altos: Add separate 'ao_launch_tick'. Use in pyro and lockout.
Prior to this, there was only ao_boost_tick, which got reset at each
motor burn start. That meant there wasn't any way to measure total
flight time for pyro channels and 'apogee lockout' was based on time
since most recent motor start instead of total flight time.
Now pyro channels and apogee lockout both use total flight time, while
motor burn length still uses time since most recent motor burn start
(as it should).
Docs and UI updated to use 'launch' instead of 'boost' to try and make
the change clear.
Signed-off-by: Keith Packard <keithp@keithp.com>
Diffstat (limited to 'doc/config-device.inc')
| -rw-r--r-- | doc/config-device.inc | 8 |
1 files changed, 7 insertions, 1 deletions
diff --git a/doc/config-device.inc b/doc/config-device.inc index 99d5c008..0ca6afff 100644 --- a/doc/config-device.inc +++ b/doc/config-device.inc @@ -23,7 +23,7 @@ ifdef::altusmetrum[] ==== Apogee Lockout - Apogee lockout is the number of seconds after boost + Apogee lockout is the number of seconds after launch where the flight computer will not fire the apogee charge, even if the rocket appears to be at apogee. This is often called 'Mach Delay', as it is @@ -35,6 +35,12 @@ ifdef::altusmetrum[] pressure increase, and so this setting should be left at the default value of zero to disable it. + [WARNING] + Firmware versions older than 1.8.6 have a + bug which resets the time since launch to zero each + time a motor starts burning. Update firmware to get + the correct behavior. + endif::altusmetrum[] ifdef::radio[] |