Felix Ruess

Done for rotorcrafts with #1065

This could be done for some of the onboard loggers, but I don't really see how it would be possible to start/stop the log created by server on the ground_segment....

Just keep in mind that server logs all aircrafts, not just one... So automatically splitting logs when one starts the engine is not a good default.

If this is important, you could also add a new message that instructs the server to create a new log file. You could send this message either from some ground...

You can't really run multiple instances of the same module. Instead one would have to do something like: - create an array of the opticflow struct to hold the parameters...

can you be a bit more specific here? Otherwise it is not really helpful...

Currently the servo `no` has to be an int so the gen_airframe can determine the highest number for the generated SERVOS_driver_NB defines (e.g. `SERVOS_DUALPWM_NB`). Looking at it, it actually seems...

One possibility to tackle both problems would be to create a `PositionReps` struct and accessors analogous to the `OrientationReps` that were factored out from the state interface so we can...

If we choose that solution, that would be the case, yes... it would probably be even a bit more, a `Waypoint` struct with some flags (i.e. relative or absolute) with...

In the mission module a `_mission_wp` is currently a struct with fixed and floating point ENU coordinates in a union...