X-Git-Url: https://git.gag.com/?a=blobdiff_plain;ds=sidebyside;f=doc%2Fsystem-operation.inc;h=1e130976bcfc38ce33d88b1dd1e3ba529fd34744;hb=refs%2Fheads%2Fmaster;hp=17dfdf89106f43d33edb1391b05fdf8951c9d4d1;hpb=c57a5c018e4bd0a0033c8759132a648977bf45f7;p=fw%2Faltos diff --git a/doc/system-operation.inc b/doc/system-operation.inc index 17dfdf89..656ed8e4 100644 --- a/doc/system-operation.inc +++ b/doc/system-operation.inc @@ -7,9 +7,9 @@ fundamental modes, “idle” and “flight”. Which of these modes the firmware operates in is determined at start up time. - ifdef::telemetrum,telemega,easymega[] + ifdef::telemetrum,telemega,easymega,easytimer[] For - TeleMetrum, TeleMega and EasyMega, which have accelerometers, the mode is + TeleMetrum, TeleMega, EasyMega and EasyTimer, which have accelerometers, the mode is controlled by the orientation of the rocket (well, actually the board, of course...) at the time power is switched on. If the rocket is “nose up”, then @@ -17,13 +17,16 @@ launch, so the firmware chooses flight mode. However, if the rocket is more or less horizontal, the firmware instead enters idle mode. - endif::telemetrum,telemega,easymega[] + endif::telemetrum,telemega,easymega,easytimer[] Since EasyMini doesn't have an accelerometer we can use to determine orientation, “idle” mode is selected if the board is connected via USB to a computer, - otherwise the board enters “flight” mode. + otherwise the board enters “flight” mode. This is also how + EasyMotor works, since even though it has an accelerometer, + it detects the motor burn it is meant to record by detecting a rise in chamber pressure, and board orientation doesn't + matter. ifdef::telemini[] TeleMini selects “idle” mode if it receives a command packet @@ -295,9 +298,9 @@ endif::radio[] ifdef::gps+radio[] - :aprsdevices: TeleMetrum v2.0 and TeleMega + :aprsdevices: TeleMetrum v2 and newer and TeleMega :configure_section: _configure_altimeter - include::aprs-operation.raw[] + include::aprs-operation.adoc[] endif::gps+radio[] === Configurable Parameters