Project

General

Profile

Modes of operation » History » Version 2

Rafael Bailon-Ruiz, 2020-09-09 17:00

1 1 Rafael Bailon-Ruiz
h1. Modes of operation
2
3 2 Rafael Bailon-Ruiz
CAMS is designed to work under several modes of operation fulfilling user needs in various use cases:
4 1 Rafael Bailon-Ruiz
* [[Modes of operation#Field operation|Field operation]]
5
* [[Modes of operation#Virtual operation|Virtual operation]]
6
* [[Modes of operation#Mixed-reality operation|Field operation]]
7
* [[Modes of operation#Mission replay|Mission replay]]
8
9
h2. Virtual operation
10
11
In a simulation scenario, the full stack of LAAS software is used. The simulated UAVs fly into simulated wind and their Liquid Water Content (LWC) sensor is also simulated. Both data come from a MesoNH database.
12
13
!https://redmine.laas.fr/attachments/download/1629/functional_diagram_simulation.svg!
14
15
16
h2. Field operation
17
18
In a real flight scenario, none of the MesoNH modules are required. The rest of the modules should work exactly the same thanks to the Paparazzi framework abstraction level.
19
20
!https://redmine.laas.fr/attachments/download/1628/functional_diagram_real_flight.svg!
21
22
23
h2. Mixed-reality operation
24
25
The hybrid scenario is meant to test the adaptive flight patterns without having to fly into a cloud. Real UAV are flying but the LWC data is read from a MesoNH database. It is then sent to the UAVs to emulate the LWC embedded sensor.
26
27
!https://redmine.laas.fr/attachments/download/1627/functional_diagram_hybrid.svg!
28
29
h2. Mission replay