We could also drop the data manager in-flight restart type. What type of
data will ever need to persist across power on restarts, but not in-flight
restarts. From the datamanager perspective it seems to me that in-flight
restarts should be treated as though they never happened. Here's what I
propose for now:

I'll add a restart parameter to the datamanager command (as per your
suggestion) and we can work out the details of how to handle these in a
script later.

Do all versions of PX4FMU have FRAM?

Jean


On Thu, Jan 30, 2014 at 9:21 AM, Lorenz Meier <notifications@github.com>wrote:

> In src/drivers/px4io/px4io.cpp:
>
> > @@ -720,6 +722,8 @@ class PX4IO : public device::CDev
> >  			/* keep waiting for state change for 2 s */
> >  		} while (!safety.armed);
> >
> > +		dm_restart(DM_INIT_REASON_IN_FLIGHT); /* clear the volatile data manager entries */
>
> Pixhawk uses FMU and IO to enable all outputs. The in-flight restart
> restore has to be fleshed out, yes - If you like I could give you pointers.
> We could start by using the FRAM on FMU to store a flight status flag and
> evaluate that on reboots.
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/PX4/Firmware/pull/619/files#r9306236>
> .
>