[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[paparazzi-commits] [paparazzi/paparazzi] 47a826: [flight_plan] add bind
From: |
GitHub |
Subject: |
[paparazzi-commits] [paparazzi/paparazzi] 47a826: [flight_plan] add binding to ABI messages from fli... |
Date: |
Mon, 21 Aug 2017 09:19:11 -0700 |
Branch: refs/heads/abi_fp_bindings
Home: https://github.com/paparazzi/paparazzi
Commit: 47a8269ee85b23b3243e79fb114cf78924939380
https://github.com/paparazzi/paparazzi/commit/47a8269ee85b23b3243e79fb114cf78924939380
Author: Gautier Hattenberger <address@hidden>
Date: 2017-08-21 (Mon, 21 Aug 2017)
Changed paths:
M conf/flight_plans/flight_plan.dtd
M sw/airborne/firmwares/fixedwing/nav.c
M sw/airborne/firmwares/rotorcraft/navigation.c
M sw/tools/generators/gen_flight_plan.ml
Log Message:
-----------
[flight_plan] add binding to ABI messages from flight plan
This feature allows to create an automatic binding to a ABI message
while specifying the list of variable names ('_' are ignored).
A local (static) variable is updated to the latest value each time a new
message is received and it can be read in any flight plan instruction.
Example of usage:
<variables>
<abi_binding name="VELOCITY_ESTIMATE" vars="_, vx, vy, vz, _"/>
</variables>
please not the in this example, the first and the last variable are
ignored but the number of variable must match the number of fields in
ABI messages description (conf/abi.xml).
An extra attribute 'id' allows to set a specific sender ID (by default
ABI_BROADCAST).
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [paparazzi-commits] [paparazzi/paparazzi] 47a826: [flight_plan] add binding to ABI messages from fli...,
GitHub <=