Difference between revisions of "DevGuide/BoozDesign"
From PaparazziUAV
m (→Use Cases) |
|||
| Line 1: | Line 1: | ||
Here we want to collect our thoughts on the re-design of the booz airborne code. | Here we want to collect our thoughts on the re-design of the booz airborne code. | ||
| + | |||
| + | === Use Cases === | ||
| + | |||
| + | * Interface on Navigation, Guidance, Stabilization and Supervision level | ||
| + | * Priority system | ||
| + | ** priority of RC to switch to manual | ||
| + | * Overlay of different inputs | ||
| + | ** RC over Guidance | ||
| + | ** FMS over RC (e.g. test signal) | ||
| + | * Limit max. throttle with RC | ||
| + | |||
| + | |||
| + | === Requirements === | ||
| + | |||
| + | === Autopilot === | ||
| + | Describe modules (nav, guidance, stabilization, etc.) as xml with in and outputs. A mode is a specific connection of modules. | ||
| + | Events can change the mode. | ||
| + | |||
| + | Events: | ||
| + | * Mode change from RC | ||
| + | * RC lost | ||
| + | * GPS lost | ||
| + | * outside zone | ||
| + | * battery low | ||
| + | |||
| + | possible priority systems: | ||
| + | #Every mode belongs to a certain priority level. If an event requests a new mode with a higher priority than the current mode it is switched to the new mode. | ||
| + | #:Better suited for a lot of different modes which can be grouped into priority levels. | ||
| + | #Every event has a condition (current mode) and associated requested mode (or multiple conditions). If the condition matches the current mode the autopilot will switch to the new mode.<br> | ||
| + | #:e.g. '''Event:''' GPS lost '''Condition:''' Nav mode '''ReqMode:''' Failsafe | ||
| + | #:This will get tedious with a lot of modes.... | ||
== Current Status == | == Current Status == | ||
| Line 67: | Line 98: | ||
} | } | ||
</graphviz> | </graphviz> | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
Revision as of 07:50, 21 September 2009
Here we want to collect our thoughts on the re-design of the booz airborne code.
Use Cases
- Interface on Navigation, Guidance, Stabilization and Supervision level
- Priority system
- priority of RC to switch to manual
- Overlay of different inputs
- RC over Guidance
- FMS over RC (e.g. test signal)
- Limit max. throttle with RC
Requirements
Autopilot
Describe modules (nav, guidance, stabilization, etc.) as xml with in and outputs. A mode is a specific connection of modules. Events can change the mode.
Events:
- Mode change from RC
- RC lost
- GPS lost
- outside zone
- battery low
possible priority systems:
- Every mode belongs to a certain priority level. If an event requests a new mode with a higher priority than the current mode it is switched to the new mode.
- Better suited for a lot of different modes which can be grouped into priority levels.
- Every event has a condition (current mode) and associated requested mode (or multiple conditions). If the condition matches the current mode the autopilot will switch to the new mode.
- e.g. Event: GPS lost Condition: Nav mode ReqMode: Failsafe
- This will get tedious with a lot of modes....
Current Status
The ImageMap extension is not installed.
ReDesign
input and control loops
The ImageMap extension is not installed.
