... | ... | @@ -41,7 +41,7 @@ By connecting two well-known-in-literature simulation suites (FL-AIR for |
|
|
UAVs**, and analyze the impact of the radio propagation phenomena and
|
|
|
packet level simulation on the fleet mobility algorithms.
|
|
|
|
|
|
![Cuscus Screenshot](wikis/images/cuscus1.png)
|
|
|
![Cuscus Screenshot](images/cuscus1.png)
|
|
|
|
|
|
|
|
|
## Standard Introduction<a id="standard_introduction" name="standard_introduction"></a>
|
... | ... | @@ -102,7 +102,7 @@ test them on a simulated control environment before the actual |
|
|
deployment, since the same code can also be **plugged in real
|
|
|
drones**.
|
|
|
|
|
|
![Cuscus Screenshot 2](wiki/images/simulator.jpg)
|
|
|
![Cuscus Screenshot 2](images/simulator.jpg)
|
|
|
|
|
|
In CUSCUS (and FLAIR), each virtual drone application is responsible to
|
|
|
simulate its flight model and control and then socket-out the data to a
|
... | ... | @@ -111,7 +111,7 @@ simulate its flight model and control and then socket-out the data to a |
|
|
**This means that it is always possible to connect *a real drone* to the
|
|
|
engine and run it alongside its virtual fellows.**
|
|
|
|
|
|
![FLAIR Structure](wiki/images/archi_simu.pdf.png)
|
|
|
![FLAIR Structure](images/archi_simu.pdf.png)
|
|
|
|
|
|
To make the simulation even more realistic and make a step towards the
|
|
|
usage of fleets of UAVs in Smart city scenarios, we just finished
|
... | ... | @@ -131,7 +131,7 @@ ourselves (for the moment, then it will be public domain, maybe…). |
|
|
In the meantime, here's a
|
|
|
**[neat video](https://drive.google.com/open?id=0B-0NRj4-P-qVcUg2YUNlX19jQ0k)** of it:
|
|
|
|
|
|
[![neat video](wiki/images/videoscreenshot.png)](https://drive.google.com/open?id=0B-0NRj4-P-qVcUg2YUNlX19jQ0k "CUSCUS VIDEO OPERATION")
|
|
|
[![neat video](images/videoscreenshot.png)](https://drive.google.com/open?id=0B-0NRj4-P-qVcUg2YUNlX19jQ0k "CUSCUS VIDEO OPERATION")
|
|
|
|
|
|
### Highlights<a id="highlights" name="highlights"></a>
|
|
|
|
... | ... | |