[paparazzi-commits] [paparazzi/paparazzi] 3cca37: [mission] add support for custom mission patterns ...

[GitHub]

  Branch: refs/heads/mission_register_nav
  Home:   https://github.com/paparazzi/paparazzi
  Commit: 3cca37a47d73e4c1b1668408e0939bbf701a7af0
      
https://github.com/paparazzi/paparazzi/commit/3cca37a47d73e4c1b1668408e0939bbf701a7af0
  Author: Gautier Hattenberger <address@hidden>
  Date:   2018-08-24 (Fri, 24 Aug 2018)

  Changed paths:
    M conf/Makefile.sim
    M conf/modules/mission_fw.xml
    M conf/modules/mission_rotorcraft.xml
    M conf/modules/nav_flower.xml
    M sw/airborne/modules/mission/mission_common.c
    M sw/airborne/modules/mission/mission_common.h
    M sw/airborne/modules/mission/mission_fw_nav.c
    M sw/airborne/modules/mission/mission_rotorcraft_nav.c
    M sw/airborne/modules/nav/nav_flower.c
    M sw/airborne/modules/nav/nav_flower.h
    M sw/ext/pprzlink

  Log Message:
  -----------
  [mission] add support for custom mission patterns or actions

Specific navigation functions or even payload actions can be registered
in the mission module in order to be called from the mission controller
like the built-in navigation patterns.
Each custom element (callback function) is registered/called with an
unique string identifier of 5 char max.
A maximum of 12 parameters can be passed to the callback function.
An example is provided with the nav_flower navigation function.



      **NOTE:** This service has been marked for deprecation: 
https://developer.github.com/changes/2018-04-25-github-services-deprecation/

      Functionality will be removed from GitHub.com on January 31st, 2019.